ADF Application Development Framework

BAM Business Activity Monitoring

BPM Business Process Management
BPMN Business Process Model and Notation
EJB Enterprise Java Beans
JDK Java Development Kit
JEE Java Enterprise Edition
JSF Java Server Faces
MDS Metadata Services
OSB Oracle Service Bus
SCA Service Component Architecture
SOA Service Oriented Architecture
UMS User Messaging Service
BPEL Business Process Execution Language

Memory and Disk Space Requirements

The software requires a minimum of 3 GB available memory to run, but more is recommended.
If you have less, separate the installation of the database, servers, and JDeveloper to different machines.
If you install SOA Suite without Oracle Service Bus, you need about 4.81 GB of disk space to download
the install files plus about 5.15 GB to install everything. Your database takes an additional 5 GB (or so,
depending on your configuration).

Oracle Service Bus will add about 1.2 GB of disk space.

5+5+5

5.4 Oracle BPM Suite and High Availability Concepts

Oracle Fusion Middleware BPM Suite provides a complete set of components for designing,
deploying, and managing Business Process Management (BPM) projects.

5.4.1 Oracle BPM Suite Single Instance Concepts

As shown in Figure 5-13, Oracle BPM Suite provides a comprehensive suite of products for
developing, managing and monitoring BPM Projects. Based on Oracle SOA Suite 11g, the
complete set of technologies and standards like SCA can be leveraged by the BPM Suite 11g.
The BPM runtime consists of service engines (BPMN Service Engine, BPEL Process Manager,
Human Workflow, Rules, Mediator) and binding components (JCA Adapters, B2B) that are
managed and interconnected by a common Service Infrastructure. The Service Infrastructure also
provides common services for lifecycle management and deployment of BPM projects.
5.12 Configuring High Availability for Oracle SOA Service
Infrastructure and Component Service Engines
The procedures described in this section include setting up the Service engines contained in the
Oracle SOA Service Infrastructure system, such as Oracle BPEL/Oracle PM, Oracle Mediator,
Oracle Human Workflow and Oracle Decision Services, as well as Oracle B2B and Oracle User
Messaging Service.

This section includes these topics:

Section 5.12.1, "Preparing the Environment: Prerequisite Steps Before Setting up a SOA
High Availability Configuration"
Section 5.12.2, "Installing Oracle Fusion Middleware Home"
Section 5.12.3, "Enabling VIP1 in SOAHOST1 and VIP2 SOAHOST2"
Section 5.12.4, "Running Oracle Fusion Middleware Configuration Wizard on
SOAHOST1 to Create the SOA Domain"
Section 5.12.5, "Creating boot.properties for the Administration Server on SOAHOST1"
Section 5.12.6, "Starting and Validating the Administration Server in SOAHOST1"
Section 5.12.7, "Disabling Host Name Verification for the Administration Server and the
WLS_SOAn Managed Servers"
Section 5.12.8, "Configuring Oracle Coherence for Deploying Composites"
Section 5.12.9, "Setting Connection Destination Identifiers for B2B Queues"
Section 5.12.10, "Starting the System in SOAHOST1"
Section 5.12.11, "Propagating the Domain Configuration to SOAHOST2 with
pack/unpack Utilities"
Section 5.12.12, "Extracting XEngine Files in the Second Node"
Section 5.12.13, "Starting the System in SOAHOST2"
Section 5.12.14, "Configuring Oracle HTTP Servers for the Administration Server and
the WLS_SOAn Managed Servers"
Section 5.12.15, "Validating Access Through Oracle HTTP Server"
Section 5.12.16, "Configuring JMS Persistence Store as Shared Across the Servers"
Section 5.12.17, "Configuring a Default Persistent Store for Transaction Recovery"
Section 5.12.18, "Setting the Front End HTTP Host and Port"
Section 5.12.19, "Setting the WLS Cluster Address for Direct Binding/RMI Invocations
to Composites"
Section 5.12.20, "Deploying Applications"
Section 5.12.21, "Configuring Server Migration for the WLS_SOA Servers"
Section 5.12.22, "Scaling the Topology"

igure 5-39 Oracle SOA Service Infrastructure High Availability Architecture

Description of "Figure 5-39 Oracle SOA Service Infrastructure High Availability Architecture"

Figure 5-39 describes a two-node SOA cluster running on two Oracle WebLogic Servers. The
Oracle WebLogic Servers are front ended by Oracle HTTP Servers, which load balance
incoming requests. A load balancer front ends the system and distributes incoming requests from
clients to the two Oracle HTTP Servers. A separate Oracle WebLogic Server (not shown in the
figure) is typically used for custom logic and application deployment. This configuration uses an
Oracle RAC database for storing metadata and SOA schemas, and shared storage for transaction
and JMS stores. Virtual IP addresses (VIPs) provide manual failover for the Administration
Server and for Oracle SOA Servers (for Server Migration). For more details about the
components contained in this architecture, see the individual component sections in this chapter.

For information about configuring virtual IPs for the Administration Server and configuring the
Administration Server for high availability, see Section 12.2.2.3, "Transforming the
Administration Server for Cold Failover Cluster."