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

Structuring composite deployments with partitions


Prior to Oracle SOA Suite 11g PS2 (11.1.1.3), as hundreds of composites were deployed to the SOA server, they were all listed in alphabetical order on the console, which made it a burden to manage and was not very structured. Oracle recognized the lack of structure and, therefore, introduced the concept of partitions to help better organize where to deploy your composites. However, partitions are just logical separations to group your composites together. Domain libraries, extension modules, server Java Naming and Directory Interface (JNDI), and infrastructure properties are shared across all partitions.

Partitions do not have their own configuration or logging. They serve no purpose other than grouping composites into separate categories. Thus, for example, code for your Human Resources integrations can reside in a partition separate from your EBS integrations, offering better structuring and organization. There are a few bulk lifecycle...