Book Image

Oracle SOA Suite 11g Administrator's Handbook

Book Image

Oracle SOA Suite 11g Administrator's Handbook

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
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface

Transaction monitoring


When monitoring transactions, the goal is to achieve two purposes:

  • Identifying transactions that have not been completed successfully to determine further action

  • Ensuring that the transactions do not experience poor performance

When a payload is received by the SOA Infrastructure, it may pass through multiple components within your infrastructure and may even traverse multiple external systems as well. For example, a sales order may be received by a BPEL process, which in turns places it into a queue. Afterwards, it may be consumed by some third-party application that processes the sales order, before sending it back to another Mediator service, which routes it to the final order management application. If any one of the above steps in this particular integration fails, how can you identify where the message is? What would also be important to you is to know the time taken by each component to determine if it is inline with your predefined SLAs.

In this section, we will...