Oracle SOA Service Infrastructure Application Characteristics Oracle SOA Service Infrastructure Startup and Shutdown Lifecyle

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-5 them. For more details of the different components in an SCA system, refer to the Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite. Figure 5–3 Basic Single-Node SOA Service Infrastructure Architecture

5.2.1.1 Oracle SOA Service Infrastructure Application Characteristics

Oracle SOA Service Infrastructure Services are contained in the soa-infra-wls.ear file. None of the services provided by the Oracle SOA Service Infrastructure system are singletons, therefore, the Oracle SOA Service Infrastructure can run in full active-active mode. The SOA Service Infrastructure Java EE application contains a Web module that provides browsing of the deployed composites and links to the test pages for these composites. This Web module uses soa-infra as the associated URL context. This Web module is stateless and does not have any specific session replication requirements. Other modules in the Oracle SOA Service Infrastructure application provide task control for process instantiation and process tracking, and client services for accessing User Messaging System UMS. A task service controls instantiating and tracking processes asynchronously. In addition, there are multiple EJBs used by the Oracle SOA Service Infrastructure system. However, all of the EJBs are stateless, and there are no requirements for stateful session bean replication in an Oracle SOA cluster. The processing of transactions by these EJBs relies on Oracle WebLogic Server transaction control service. Configure the appropriate transaction stores as recommended in the basic Oracle WebLogic Server guidelines to guarantee recovery across failures in Oracle WebLogic Server container.

5.2.1.2 Oracle SOA Service Infrastructure Startup and Shutdown Lifecyle

An Oracle SOA composite consists of the following: SOA Infrastructure Java EE application Oracle WebLogic Server Composite Deployment Composite Metadata Management Service Engines Mediator, BPEL, Workflow... Composite Management instantiation, targeting to BPEL, Mediator etc... Task Control Services: thread assignment, processing of requests Deploying clients UDDI Registry SOA Db jdbcSOADataSource SOA MDS jdbcmdsMDS_LocalTxDataSource Coherence infrastructure for deployment across cluster 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