Oracle SOA Service Infrastructure Protection from Failures and Expected Behavior

5-12 Oracle Fusion Middleware High Availability Guide The Metadata store is configured in an Oracle RAC database to protect from database failures. Similarly, the SOA process state information is also stored in an Oracle RAC database. In this example, both Oracle RAC databases are the same. About Oracle SOA Service Infrastructure Components These high availability characteristics apply to most of Oracle SOA components contained in the composite applications deployed across the cluster. For specific two-node high availability characteristics of the individual components, see the specific component sections that follow in this chapter.

5.2.2.1 Oracle SOA Service Infrastructure Protection from Failures and Expected Behavior

This section describes how an Oracle SOA high availability cluster deployment protects components from failure and the expected behavior if component failure occurs. The WebLogic Server infrastructure protects the SOA Service Infrastructure system from all process failures.

5.2.2.1.1 WebLogic Server Crash If a WLS_SOAx server crashes, Node Manager

attempts to restart it locally. If repeated restarts fail, the WebLogic Server infrastructure attempts to perform a server migration of the WLS_SOAx server to the other node in the cluster. While the failover takes place, the other SOA Service Infrastructure instance becomes the leader for deployments and composite updates and provides the basic services required by the service engines in the system. Ongoing requests from the HTTP Server time out and new requests are directed to the other WLS_SOAx server. Once the servers restart completes on the other node, Oracle HTTP Server resumes routing any incoming requests to the server. The migrated server reads MDS repository for any updates that might have taken place during restart, and joins the deployment coordinator cluster to listen for new updates. The migrated server also resumes any pending transactions from the transaction logs in shared storage. In the server migration scenario, the service engines, such as Oracle BPEL PM and Oracle Mediator, are failed over together with the SOA Service Infrastructure. They do not re-issue any requests to the other SOA Service Infrastructure instances by themselves. They resume operations together with the SOA Service Infrastructure once failover is complete. The Oracle SOA Service Infrastructure application may be down due to failure in accessing resources, errors caused by the deployment coordinator infrastructure, or other issues unrelated to whether the managed server is running. Therefore, Oracle recommends administrators monitoring the soa-infra application for errors caused by the application in the managed server logs. For information about log file locations, see Section 5.2.1.6, Oracle SOA Service Infrastructure Log File Locations .

5.2.2.1.2 Node Failure If node failure occurs, server migration is triggered after the

available server verifies the time stamp in the database leasing system. If the failed server was the deployment coordinator cluster master, the available server becomes the new master and the SOA Service Infrastructure remains available for deployment and for composite lifecycle. After the time stamp for leasing is verified, the Node Manager in the node that still remains available attempts to migrate the VIP used by the failed managed server, and restarts it locally. This effectively results in the SOA Service Infrastructure application having two instances running in the same node. For more information on the failover process, see Section 3.9, Whole Server Migration . 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