Oracle Service Bus Session State Oracle Service Bus External Dependencies

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-85 Figure 5–40 Oracle Service Bus Single Instance Architecture When Oracle Service Bus is deployed in a high availability configuration, the Aggregator and Alert Manager components are singletons that should be deployed only on one host in the cluster. Customers can write custom client applications using the Oracle Service Bus extensibility framework, such as the Transport SDK and reporting framework. For more information about the Oracle Service Bus architecture, see the Oracle Service Bus Architecture chapter in Oracle Fusion Middleware Concepts and Architecture for Oracle Service Bus.

5.12.1.1 Oracle Service Bus Session State

Oracle Service Bus is optimized for short-lived message processingmediation use cases. Thus, all message context state is kept in memory. For synchronous transports such as HTTP, EJB, and SB, the client must retry if the Oracle Service Bus server fails in the middle of processing the synchronous request. Oracle Service Bus supports requestresponse pattern for asynchronous transports such as JMS and WS WS-RM. In these cases correlation information, which maps the request to its corresponding response destination, is kept in memory. If the Oracle Service Bus server fails before the response is sent, the correlation information is lost. Therefore, Oracle Service Bus will fail to send the response after server restart. For more details about JMS transports and WS transports, see the JMS Transport chapter and the WS Transport chapter in the Oracle Fusion Middleware Developers Guide for Oracle Service Bus.

5.12.1.2 Oracle Service Bus External Dependencies

Oracle Service Bus has the following external dependencies: ■ The JMS Reporting Provider uses a database to store the report data. ■ UDDI Oracle Service Registry is used to store Oracle Service Bus proxy services and to browse services to create Oracle Service Bus business services. ■ Oracle Enterprise Repository is used to browse and consume services. The result is generation of Oracle Service Bus business services. Oracle Service Bus proxy services are harvested into Oracle Enterprise Repository. ■ Oracle Service Bus implements an Oracle Web Services Manager OWSM agent that enforces OWSM security policies attached to Oracle Service Bus proxy and business services. Oracle WebLogic Server Runtime Configuration Framework Reporting Framework Statistics Collector Aggregator JMS Messages OSB Database Default JMS Provider HTTP Messages DB Messages Alert Manager 5-86 Oracle Fusion Middleware High Availability Guide ■ Oracle Service Bus depends on JCA Adapter implementations JCA Adapters for HTTP, FTP, and so on and the JCA framework from SOA Suite. ■ Oracle Service Bus depends on the Coherence infrastructure for Service Result Caching caching of results from services invoked by Oracle Service Bus. Oracle Service Bus message flows are short lived in general. Message flow state is always in memory. Oracle Service Bus provides various out of box transports. For example, the HTTP transport supports HTTP 1.1 persistent connections. Oracle Service Bus supports the following transports: HTTP, JMS, Email, File, FTP, SFTP, JCA - DB, AQ, Oracle Applications, Peoplesoft, Siebel, SAP, JD Edwards, File, FTP, JEJB, EJB outbound only, Local within same JVM, MQ, SB RMI based, between two OSB serversdomains, Tuxedo, Web Services Reliable Messaging WS-RM, SOA-Direct RMI based, BPEL 10g RMI based. Oracle Service Bus uses JTA for some transport types, including JMS, File, FTP, Email, SFTP, WS-RM, JCA - DB, AQ, SB, JEJB, EJB, SOA-DIRECT, and BPEL 10g.

5.12.1.3 Oracle Service Bus Configuration Artifacts