Oracle SOA Service Infrastructure Configuration Artifacts Oracle SOA Service Infrastructure Log File Locations

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

Starting with Oracle Fusion Middleware 11g Release 1 11.1.1.2, the configuration parameters for Oracle Service Infrastructure are stored in the SOA MDS database. The main controls of the Oracle SOA Service Infrastructure can be configured using Oracle Enterprise Manager Fusion Middleware Control. ■ The data source JNDI name for process dehydration. ■ The server and callback URL A CallBack URL is the address that asynchronous services specify to be notified of a response to the service they invoked. Note: Once the JNDI names are read from this file, the databases used by the system are determined by the data sources that matched those JNDI names in WebLogic Server JDBS resources configuration. 5-8 Oracle Fusion Middleware High Availability Guide ■ The audit level of information to be collected by the message tracking infrastructure. Other configuration options at the container level, such as data sources, JTA configuration, and persistent stores, are maintained as part of the WebLogic Server Domain configuration, and are synchronized across a cluster of Oracle WebLogic Servers by the Oracle WebLogic Server core infrastructure.

5.2.1.6 Oracle SOA Service Infrastructure Log File Locations

The operations performed by the Oracle SOA Service Infrastructure and its components are logged by Oracle WebLogic Managed Server where the Oracle SOA Service Infrastructure is running. You can find these logs at the following location: DOMAIN_HOME serversWLS_ServerNamelogsWLS_ServerName.log The log files for the different Oracle WebLogic Server managed servers are also available from Oracle WebLogic Server Administration Console. To verify the logs, access Oracle WebLogic Server Administration Console using the following URL: admin_server_host:portconsole. Click Diagnostics-Log Files. It is also important to verify the output of the Oracle WebLogic Managed Server where the Oracle SOA Service Infrastructure is running. This information is stored at the following location: DOMAIN_HOME serversWLS_ServerNamelogsWLS_ServerName.out Additionally, a diagnostic log is produced in the log directory for the managed server. This logs granularity and logging properties can be changed through the domain_ dir configfmwconfigserversWLS_ServerNamelogging.xml file. The properties in this file can also be modified from Oracle Enterprise Manager Fusion Middleware Control by selecting Farm, SOA, SOA Server. Right-click, and select Logs , and then Log Configuration. Note: If a request to an external or internal asynchronous service originates from SOA, the callback URL is determined using the following in decreasing order of preference: ■ Use callbackServerURL specified as a binding property for the specific reference. You can set this when modeling the composite or at runtime using the MBeans. This allows different service calls to have different callback URLs. At runtime this property is set using the System MBean Browser, through the corresponding binding Mbean. To add a specific URL add a callbackServerURL property to its Properties attribute, then invoke the save operation. ■ Use the callback URL as specified in the SOA Database. In this case, only one address can be specified and an address that works well for all possible services must be used. ■ Use the callback URL as the frontend host specified in WebLogic Server for the SOA_Cluster. In this case as well, only one address can be specified, and the recommendation is the same as for the SOA Database configuration option. ■ Use the local host name as provided by WebLogic Server MBean APIs. This is not recommended in high availability environments. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-9 Oracle Enterprise Manager Fusion Middleware Control allows performing selective searches in all the logs in the SOA domain. To do a selective search, access Oracle Fusion Middleware Control and click on Farm-Logs and enter the search criteria that pertain to soa-infra or deployed composites. See the Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite for more details on the logs and information reported for a SOA System in Oracle Enterprise Manager Fusion Middleware Control.

5.2.2 Oracle SOA Service Infrastructure High Availability Architecture and Failover Considerations