Increasing Cache Hit Rates

The SOA Suite Components are documented in the following chapters: ■ Chapter 11, Cross Component Tuning for SOA Suite ■ Chapter 12, Oracle Business Rules Performance Tuning ■ Chapter 13, Oracle BPEL Process Manager Performance Tuning ■ Chapter 14, Oracle Mediator Performance Tuning ■ Chapter 15, Oracle Business Process Management Tuning ■ Chapter 16, Oracle Human Workflow Performance Tuning ■ Chapter 17, Oracle Adapters Performance Tuning ■ Chapter 18, Oracle Business Activity Monitoring Performance Tuning ■ Chapter 19, User Messaging Service Performance Tuning ■ Chapter 20, Oracle B2B Performance Tuning 11 Cross Component Tuning for SOA Suite 11-1 11 Cross Component Tuning for SOA Suite This chapter describes tuning configurations that can apply to multiple SOA Suite applications. ■ Section 11.1, About SOA Suite Configuration Properties ■ Section 11.2, SOA Infrastructure Configurations ■ Section 11.3, Modifying SOA Configuration Parameters ■ Section 11.4, JVM Tuning Parameters ■ Section 11.5, Database Settings For more information on any of the SOA Suite Applications, see Section IV, SOA Suite Components for a list of the application-specific documentation provided in this guide.

11.1 About SOA Suite Configuration Properties

Refer to the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more information on configuring the SOA Applications.

11.2 SOA Infrastructure Configurations

SOA Infrastructure configuration parameters impact the entire SOA Infrastructure. The following configurations are modified through the SOA-INFRA component: ■ Viewing and setting the SOA Infrastructure audit level ■ Capturing the state of the SOA composite application instance ■ Enabling the payload validation of incoming messages ■ Specifying the callback server and server URLs ■ Setting UDDI registry properties ■ Viewing the data source JNDI locations ■ Setting the non-fatal connection retry count ■ Setting Web service binding properties For more information on SOA configuration, see Configuring SOA Infrastructure Properties in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite. 11-2 Oracle Fusion Middleware Performance and Tuning Guide

11.2.1 Audit Level

The Audit Level property enables you to select the level of information to be collected by the message tracking infrastructure. This information is collected in the instance data store database associated with the SOA Infrastructure. This setting has no impact on what is written to log files.

11.2.2 Composite Instance State

You can use the CompositeInstanceStateEnabled property to configure the SOA composite application instance state. Note, however, that enabling this option may impact performance during instance processing. This option enables separate tracking of the running instances. All instances are captured as either running or not running. This information displays later in the State column of the composite instances tables for the SOA Infrastructure and SOA composite application. The valid states are running, completed, faulted, recovery needed, stale, terminated, suspended, and state not available.

11.2.3 Logging Level

The default logging level is NOTIFICATION. For stress testing and production environments, consider using the lowest acceptable logging level, such as ERROR or WARNING whenever possible. For more information on setting the logging levels for your applications, see Configuring Log File in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite.

11.3 Modifying SOA Configuration Parameters

SOA and SOA-INFRA configurations are modifiable either through WLST or Oracle Enterprise Manager. To use WLST, use the following location: WLST_ ROOT oracle.as.soainfra.configoracle.as.soainfra.config:name=Component,type=Component Config,Application=soa-infra,ApplicationVersion=11.1.1 The Component names for the SOA Suite configuration parameters are: soainfra, mediator and bpel. Value Description Off No composite instance tracking and payload tracking information is collected. No more composite instances can be created. No logging is performed. Note that no logging and display of instances in Oracle Enterprise Manager Fusion Middleware Control Console can result in a slight performance increase for processing instances. Instances are created, but are not displayed. Production Composite instance tracking is collected, but the Oracle Mediator service engine does not collect payload details and the process service engine does not collect payload details for assign activities payload details for other activities are collected. This level is optimal for most normal production operations. Development Enables both composite instance tracking and payload detail tracking. However, this setting may impact performance. This level is useful largely for testing and debugging purposes.