11 Cross Component Tuning for SOA Suite

This chapter describes tuning configurations that can apply to multiple SOA Suite applications.

For more information on any of the SOA Suite Applications, see Section 10, "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 Administrator's 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 Administrator's Guide for Oracle SOA Suite.

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.

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.

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 Administrator's 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.config/oracle.as.soainfra.config:name=Component,type=ComponentConfig,Application=soa-infra,ApplicationVersion=11.1.1

The Component names for the SOA Suite configuration parameters are: soainfra, mediator and bpel.

To use custom WLST commands, you must invoke WLST from the Oracle home in which the component has been installed. See "Using Custom WLST Commands" in the Oracle Fusion Middleware Administrator's Guide for more information.

11.4 JVM Tuning Parameters

JVM parameters can have an impact on SOA performance. The major factors that impact a SOA component's performance relate to the heap size. For more information on tuning the JVM for performance, see Section 2.4, "Tune Java Virtual Machines (JVMs)".

11.5 Database Settings

Tuning your database configurations may be useful with the SOA Suite of applications. Configurations and specific settings may vary for different use cases. See your database-specific administration manuals for more information on tuning database properties.

For additional basic database tuning guidelines, see Section 2.6, "Tune Database Parameters".

11.5.1 Configuring Data Sources for SOA

SOA obtains database connections using an application server managed data source. You can use the WebLogic Server Console to configure SOA data source. For more information on using the WebLogic Server Console, seethe Oracle Fusion Middleware Administrator's Guide.

Consider the following data source configurations when performance is an issue:

  • When configuring the data source, ensure that the connection pool has enough free connections.

  • Statement caching can eliminate potential performance impacts caused by repeated cursor creation and repeated statement parsing and creation. Statement caching also reduces the performance impact of communication between the application server and the database server

  • Disable unnecessary connection testing and profiling.

For more information, see "Tuning JDBC Stores" in Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.

11.5.2 Weblogic Server Performance Tuning

For complete performance tuning of Weblogic Server, refer to Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server.