Oracle B2B Component Characteristics Oracle B2B Startup and Shutdown Lifecycle

5-46 Oracle Fusion Middleware High Availability Guide

5.7.1.1 Oracle B2B Component Characteristics

Oracle B2B runs in-place with SOA Service Infrastructure Java EE application. The Oracle B2B user interface is a Web application that is deployed as a standalone war file on the same managed server as the SOA Service Infrastructure. Oracle B2B UI application is stateful and stores information in the HTTP Session. Oracle B2B stores state information within JMS queues and the SOA run-time database. Whole server migration is required for automatic JMS message and transaction recovery after a server failure. Oracle B2B uses JMS intensively. Oracle B2B uses the Oracle WebLogic Server migration feature for protecting Oracle B2B JMS resources against failures. Oracle B2B’s engine uses EJBs and Servlets, which are stateless. All state information is persisted in JMS queues and the database. High availability of B2B depends on the high availability of the run-time database. Hence, the SOA runtime data sources should be configured as multi data sources for high availability. 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. External Dependencies Oracle B2B depends on the following components: ■ Oracle SOA database for Oracle B2B message and message state persistence ■ MDS repository for Oracle B2B metadata store ■ FTP and email servers if the corresponding adapters are used The SOA database and the MDS repository must be available for Oracle B2B to start and run properly.

5.7.1.2 Oracle B2B Startup and Shutdown Lifecycle

When the Oracle SOA Service Infrastructure application starts, it initializes Oracle B2B’s engine. Oracle B2B metadata deployment should occur before composites are deployed to the Oracle SOA Service Infrastructure. Oracle B2B end-points are defined as channels which are started as part of the engine initialization. Based on the protocol, each configured channel has external dependencies, such as: ■ If FTP is used, the appropriate FTP server must be started. ■ If email is used, the appropriate email server must be started. ■ If HTTPHTTPS is used, the HTTP server front ending the B2B system must be started

5.7.1.3 Oracle B2B Request Flow