Oracle SOA Service Infrastructure External Dependencies Oracle SOA Service Infrastructure Startup and Shut Down of Processes

5-6 Oracle Fusion Middleware High Availability Guide ■ Components such as a BPEL process, Human Workflow task, a Mediator routing rule or Business Rules. ■ Services and References for connecting Oracle SOA composite applications to external services, applications, and technologies. These components are assembled together into an Oracle SOA composite application. This application is a single unit of deployment that simplifies the management and lifecycle of Oracle SOA applications. When the Oracle SOA Service Infrastructure application starts, it initializes the different service engines and loads the present composites from the MDS repository. It targets the individual components to their specific engines. Once the composite is loaded, the system is available to receive requests. At runtime, the Oracle SOA Service Infrastructure manages all communication across service components. These calls between service engines are in-process calls. The following diagram reflects the sequence for the Oracle SOA Service Infrastructure startup and processing of work: Figure 5–4 Oracle SOA Service Infrastructure Application Startup and Shutdown Lifecyle

5.2.1.3 Oracle SOA Service Infrastructure External Dependencies

As described in the previous sections, the Oracle SOA Service Infrastructure system depends on the following components: ■ Instance manager service depends on the runtime SOA database schema soa-infra. ■ Composite metadata is stored in the MDS database schema which acts as a repository. ■ In a clustered environment, the deployment coordinator service depends on the underlying Coherence cluster for signal propagation. All three of these components must be available for the Oracle SOA Service Infrastructure to start and run properly. Read SOA service Infrastructure Configuration Start SOA Service Infrastructure basic services Start Service Engines BPEL Mediator and activate binding components Access MDS and load Composites Target Composites to Corresponding service engines Join Coherence Cluster for new deployments and update notifications Wait for requests to Composites Manage Composite Lifecycle Route request to Service Engines and binding components Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-7

5.2.1.4 Oracle SOA Service Infrastructure Startup and Shut Down of Processes

The Oracle SOA Service Infrastructure application is started by default whenever any Oracle WebLogic Managed Server to which the Oracle SOA Service Infrastructure has been deployed is started. Normally, you should not need to stop the Oracle SOA Service Infrastructure or any of its components by themselves. Some operations may require Oracle WebLogic Managed Server where the SOA Service Infrastructure runs to be rebooted. Only some patching scenarios could require stopping the application. You can use Oracle WebLogic Server Administration Console to verify status and to start and stop Oracle WebLogic Server. You can also use the WebLogic Server WLST command line to control the application. Oracle Enterprise Manager Fusion Middleware Control also allows multiple operations and configuration of the Oracle SOA Service Infrastructure application as well as monitoring its status. See the Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite for details on monitoring and controlling the Oracle SOA Service Infrastructure application. Figure 5–5 Monitoring and Controlling the Oracle SOA Service Infrastructure Application

5.2.1.5 Oracle SOA Service Infrastructure Configuration Artifacts