Oracle Service Bus Configuration Artifacts Oracle Service Bus Deployment Artifacts

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

The main configuration files for Oracle Service Bus are: ■ DOMAIN_HOMEconfigconfig.xml: has all applications and libraries, JMS system resources, JDBC system resources, work manager, startupshutdown classes, SAF agent, security configuration. ■ DOMAIN_ HOMEconfigosbcoherenceosb-coherence-override.xml: This Oracle Coherence override file specifies Oracle Coherence unicastmulticast listener information. This file is propagated by the Administration Server from the Administration Server domain directory to the domain directory for other managed servers. ■ DOMAIN_ HOMEconfigosbcoherenceosb-coherence-cache-config.xml: This Coherence cache configuration file defines the cache used by the Oracle Service Bus service result caching feature. ■ DOMAIN_HOMEconfigosbtransportssftpknown_hosts: This file is used by the SFTP transport. It contains information about remote SFTP servers. See Oracle Fusion Middleware Developers Guide for Oracle Service Bus for information about creating the known_hosts file. Note that virtual host names can be used in the known_hosts file.

5.12.1.4 Oracle Service Bus Deployment Artifacts

You can use Eclipse IDE or the Oracle Service Bus web console to export your Oracle Service Bus artifacts resources, such as proxy service, business service, wsdl, xsd, and xslt resources, to a jar file with a name that you choose. The jar file contains all the Oracle Service Bus resources that were exported. You have two ways to import the configuration jar file and the Oracle Service Bus resources inside it into an Oracle Service Bus server: ■ WLSTANT scripts using public Oracle Service Bus APIs ■ Oracle Service Bus web console: Using the Import from Configuration Jar option Oracle Service Bus resources are managed by the configuration framework component. The configuration framework stores all its data in DOMAIN_ HOMEosbconfig CONFIG_HOME on each managed server and admin server. Each resource is stored in its own file in CONFIG_HOMEcore. The Oracle Service Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-87 Bus configuration framework automatically assigns unique file names to the file used for each resource to ensure that no name collisions occur among these files. The CONFIG_HOMEcore directory is the master view of all the resources and configuration data. The runtime works off of this data. It changes only when changes made in a session are activated. Each managed server has a copy of the resources in CONFIG_HOMEcore. Depending on the location of the managed server, this directory could be mounted on a separate system.

5.12.1.5 Oracle Service Bus Startup and Shutdown