Book Image

Oracle SOA Suite 11g Administrator's Handbook

By : Arun Pareek, Ahmed Aboulnaga
Book Image

Oracle SOA Suite 11g Administrator's Handbook

By: Arun Pareek, Ahmed Aboulnaga

Overview of this book

Oracle SOA Suite 11g is the backbone of messaging and application integration in a service-oriented architecture. An application administrator is responsible for an end-to-end administration and management of the infrastructure. Understanding the underlying components, services, and configuration and their relations to each other is necessary to effectively administer the Oracle SOA Suite 11g environment. Due to its sheer size, administering Oracle SOA Suite 11g is a daunting task.This book provides detailed explanations of all the core administrative and management activities around Oracle SOA Suite. It includes compact information for end-to-end administration of Oracle SOA Suite 11g. It delves into advanced topics such as silent installs, cloning, backup and recovery and high availability installations.Using this book, you will be able to administer and secure your Oracle SOA Suite services and applications. You will follow examples that you can use in your everyday life as a SOA Suite administrator. The book begins with managing composite applications, their deployments and lifecycles and then moves on to monitoring instances, service engines, Weblogic Server and composite applications. With a detailed coverage of topics like the administration of individual service components as well as configuring MBeans using both Oracle Enterprise Manager Fusion Middleware Control and WLST-based scripts, you will be equipped to work with any services and applications.Towards the end, you will be taken through identifying faults & exceptions, troubleshooting approaches, and securing various components.
Table of Contents (16 chapters)
Oracle SOA Suite 11g Administrator's Handbook
About the Authors
About the Reviewers

Purging metadata version history

As the metadata repository is usually backed by a database, it would be necessary to purge unnecessary and archaic customizations made to composites that are no longer applicable. Purging is only required for database-based MDS repositories as file-based repositories do not maintain composite version histories. Purging metadata version history from a partition deletes all unlabeled documents from it, leaving only the tip version (the latest version), even if it is unlabeled. Purging metadata version history on a regular basis is a necessary maintenance activity to prevent the database from running out of space or when its performance starts to degrade. Purging an MDS repository is performance intensive and hence should either be attempted in a maintenance window or when the system is not busy. To use Oracle Enterprise Manager Fusion Middleware Control to purge the metadata version history, perform the following:

  1. 1. Log in to Oracle Enterprise Manager Fusion...