Oracle SOA Service Infrastructure Cluster-Wide Deployment Online Redeployment of Oracle SOA Service Infrastructure Composites in a Cluster

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-13 Service engines are deployed to the container as a part of the Service Infrastructure application. These service engines contain all of the ear files and library calls.

5.2.2.1.3 Database Failure The SOA Service Infrastructure system is protected against

failures in the database by using multi data sources. These multi data sources are typically configured during the initial set up of the system Oracle Fusion Middleware Configuration Wizard allows you to define these multi-pools directly at installation time and guarantee that when an Oracle RAC database instance fails, the connections are reestablished with available database instances. The multi data source allows you to configure connections to multiple instances in an Oracle RAC database. For information about multi data source configuration with Oracle RAC and the MDS repository, see Section 4.1.2, Using Multi Data Sources with Oracle RAC.

5.2.2.2 Oracle SOA Service Infrastructure Cluster-Wide Deployment

As explained in previous sections, composite deployments are stored centrally by the SOA Service Infrastructure in the MDS repository. Each time the SOA Service Infrastructure is started, it synchronizes itself with the MDS repository and SOA store to get the deployment and process state. The deployment coordinator infrastructure orchestrates the notifications for composites deployments and updates. When a new deployment or update takes place, deployment coordinator notifies all members in the cluster. When all members in the cluster confirm that the deployment has succeeded, the master sends a notification to start the composite. If a deployment fails on any one of the nodes, it is rolled back to the rest of the cluster. An error message in the deployment coordinator master WebLogic Server managed server, indicates the node on which the deployment failed. Figure 5–7 explains this process: Figure 5–7 Cluster-Wide Deployment of Oracle SOA Composites

5.2.2.3 Online Redeployment of Oracle SOA Service Infrastructure Composites in a Cluster

When the Oracle SOA Service Infrastructure performs an update or redeployment of a composite, it can overwrite an existing version x or create a new version x+1. All composites are uniquely identified based on the composite name and revision. By default, clients accessing a composite use the version that is identified in the MDS repository as the default version also visible from Oracle Enterprise Manager Fusion Middleware Control. It is possible to manage the lifecycle of each version separately and perform online redeployments of composites, even with one single instance of SOA Service Infrastructure. The steps for performing this operation would be as follows: succeed fail SOA Infrastructure Start Synchronize with MDS Send notification to start composite New Deployment Notify all members in the cluster Wait for confirmation on deployment succeeded from members Roll Back All 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