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

Troubleshooting composite instances

This section is not about troubleshooting composite instance failures, but rather troubleshooting composite instances in general. Just because a composite is not reported as failed does not mean it does not warrant investigation. Take, for example, a scenario where there are asynchronous processes that are deployed to the service infrastructure. By their nature, whenever there is a dehydration point in the process, the threads running the process instances try to access the underlying database schemas for reading, retrieving, and writing instance information. In these cases, it is entirely possible that there might be synchronization issues between concurrent threads trying to access the database schema and, as such, the default server level thread locking mechanism could lead to a deadlock. This would leave the transaction in a pending state and not faulted. This behavior, though intermittent, may require further investigation.

Chapter 5, Configuring...