Configuring SOA Infrastructure Properties

Tuning Integration Flows 28-13 cache-config max-size-kb200000max-size-kb cache-config mds-config For more information about tuning the MDS and the database, see Optimizing Instance Performance in Oracle Database Performance Tuning Guide, and Oracle Metadata Service MDS Performance Tuning in Oracle Fusion Middleware Performance and Tuning Guide.

28.3 Configuring the Common SOA Infrastructure

This section discusses properties that impact the entire SOA infrastructure.

28.3.1 Configuring SOA Infrastructure Properties

These settings apply to all SOA Composite applications running in the SOA infrastructure. The properties set at this level impact all deployed SOA composite applications, except those composites for which you explicitly set different audit level values at the composite application or service engine levels. AIA recommends configuring at least the following properties. auditLevel This property sets the audit trail logging level. This property controls the amount of audit events that are logged by a process. AIA recommends the following value to be set to this property: ■ Production: The BPEL service engine does not capture the payload. The payload details are not available in the flow audit trails. Payload details for other BPEL activities are collected, except for assign activities. This level is optimal for most normal operations and testing. captureCompositeInstanceState Enabling this option may result in additional run time overhead during instance processing. This option provides for 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, where it shows the counts of running instances versus total instances. You can also limit the view to running instances only Valid states are Running, Completed, Faulted, Recovery Needed, Stale, Terminated, Suspended, and State Not Available. The Running and Completed states are captured only if this check box is selected. Otherwise, the state is set to Unknown. The conditional capturing of these states is done mainly to reduce the performance overhead on SOA Infrastructure run time. Note: If this property is disabled and you create a new instance of a SOA composite application, a new instance is created, but the instance does not display as running, faulted, stale, suspended, terminated, completed, or requiring recovery in the table of the Dashboard page of the composite application. This is because capturing the composite state of instances is a performance-intensive process. AIA recommends disabling this property. 28-14 Developers Guide for Oracle Application Integration Architecture Foundation Pack PayloadValidation This property validates incoming and outgoing XML documents. If set to True, the SOA Infrastructure applies schema validation for incoming and outgoing XML documents. This property is applicable to both durable and transient processes. The default value is False. This value can be overridden to turn on schema validation based on business needs. Turning on schema validation both at SOA Infrastructure and at the BPEL Process Service engine causes the schema validation to be done twice.

28.3.2 Disabling HTTP Logging