Oracle SOA Service Infrastructure Cluster-Wide Configuration Changes

5-14 Oracle Fusion Middleware High Availability Guide 1. Deploy version x. 2. Mark version x as default. 3. Deploy a new version of the composite x+1 and mark version x as the default this is done to keep people from accessing the new version in default access. 4. Test the new version by accessing from a test client by specifying the version of the composite x+1 5. Once verifications are complete, mark x+1 as the default version 6. New clients are routed to version x+1, while old clients complete their work in version x. It is possible to leave the previous version deployed, or undeploy it. If you undeploy a composite which has in-flight instances, they become stale and do not complete. The un-deployment of a composite removes the composite from the MDS repository.

5.2.2.4 Oracle SOA Service Infrastructure Cluster-Wide Configuration Changes

The standard Java EE artifacts that the Oracle SOA Service Infrastructure uses are configured as part of Oracle WebLogic Domain in which SOA is installed. Oracle WebLogic Clusters provide automatic configuration synchronization for artifacts such as data sources, persistent stores, and JMS modules, across the WebLogic Server domain. At the same time, the WebLogic Server cluster controls synchronization of the deployments and libraries used by the SOA Service Infrastructure. As explained in Section 5.2.1, Oracle SOA Service Infrastructure Single-Instance Characteristics, SOA Service Infrastructure-specific configuration is stored in the SOA database. Changes are applied once per SOA server, but affect all SOA servers in the same SOA domain. For example, in the high availability topology described in this chapter, if you change the callback URL or audit level for server WLS_SOA1, the change also applies to WLS_SOA2.

5.3 Oracle BPEL Process Manager and High Availability Concepts

The information in this section guides you through the issues and considerations necessary for configuring Oracle BPEL PM for high availability.

5.3.1 Oracle BPEL Process Manager Single-Instance Characteristics

Service engines are containers that host the business logic of service components in a SOA composite application. Each service component, such as Oracle BPEL PM, Oracle Human Workflow, Decision Service, or Oracle Mediator, is executed in its own service engine Decision Service executes in the business rules service engine. A service engine plugs into the Oracle SOA Service Infrastructure. Oracle BPEL Process engine is the service engine running in the Oracle SOA Service Infrastructure that allows the execution of BPEL Processes. A BPEL process provides the standard for assembling a set of discrete services into an end-to-end process flow, and developing synchronous and asynchronous services into Note: Changes to properties of a Composite from the Oracle Enterprise Manager Fusion Middleware Control using the MBean browser are also reflected in all the nodes of a SOA cluster. For example, if you change the Mbean by selecting oracle.soa.config node , server:WLS_SOA1clustered node, SCAComposite, My Composite, this change propagates to the other servers in the cluster.