Configuring BPEL Process Service Engine Properties

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

To disable HTTP logging from Weblogic Console for Admin, SOA and BAM servers 1. Login to Weblogic Console 2. Environments - Servers - Admin Server - Logging - HTTP - Uncheck HTTP access log file enabled option To change log level to error From Oracle Enterprise Manager EM: 1. Login to EM

2. SOA Infrastructure - Logs - Log Configuration

28.4 BPEL - General Performance Recommendations

This section includes the following topics: ■ Section 28.4.1, Configuring BPEL Process Service Engine Properties ■ Section 28.4.2, Configuring BPEL Properties Inside a Composite ■ Section 28.4.3, How to Monitor the BPEL Service Engine

28.4.1 Configuring BPEL Process Service Engine Properties

The basic BPEL Process Manager performance tuning properties can be configured using WLST or Enterprise Manager. These properties must be configured: 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. instanceKeyBlockSize This property controls the instance ID range size. Oracle BPEL Server creates instance keys a range of process instance IDs in batches using the value specified. After creating this range of in-memory IDs, the next range is updated and saved in the ci_ id_range table. For example, if instanceKeyBlockSize is set to 100, Oracle BPEL Server creates a range of instance keys in-memory 100 keys, which are later inserted into the Tuning Integration Flows 28-15 cube_ instance table as cikey. To maintain optimal performance, ensure that the block size is larger than the number of updates to the ci_id_range table. The default value is 10000. AIA recommends the default value to be used as is. auditDetailThreshold This property sets the maximum size in kilobytes of an audit trail details string before it is stored separately from the audit trail. If an audit trail details string is larger than the threshold setting, it is not immediately loaded when the audit trail is initially retrieved; a link is displayed with the size of the details string. Strings larger than the threshold setting are stored in the audit_details table, instead of the audit_trail table. The details string typically contains the contents of a BPEL variable. In cases where the variable is very large, performance can be severely impacted by logging it to the audit trail. The default value is 50000 50 kilobytes. AIA recommends retaining the default value. LargeDocumentThreshold This property sets the large XML document persistence threshold. This is the maximum size in kilobytes of a BPEL variable before it is stored in a separate location from the rest of the instance scope data. This property is applicable to both durable and transient processes. Large XML documents impact the performance of the entire Oracle BPEL Server if they are constantly read in and written out whenever processing on an instance must be performed. The default value is 10000 100 kilobytes. AIA recommends changing the value to 50000. PayloadValidation This property validates incoming and outgoing XML documents. If set to True, the Oracle BPEL Process Manager 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. DispatcherInvokeThreads dspInvokeThreads in 10g This property specifies the total number of threads allocated to process invocation dispatcher messages. Invocation dispatcher messages are generated for each payload received and are meant to instantiate a new instance. If the majority of requests processed by the engine are instance invocations as opposed to instance callbacks, greater performance may be achieved by increasing the number of invocation threads. Higher thread counts may cause greater CPU utilization due to higher context switching costs. The default value is 20. AIA recommends this value as the starting point. This parameter can be used throttle the requests to avoid overloading the mid-tier, database tier, and participating application systems and tune for best performance. DispatcherEngineThreads dspEngineThreads in 10g This property specifies the total number of threads allocated to process engine dispatcher messages. Engine dispatcher messages are generated whenever an activity must be processed asynchronously. If the majority of processes deployed are durable with a large number of dehydration points mid-process receive, onMessage, onAlarm, 28-16 Developers Guide for Oracle Application Integration Architecture Foundation Pack and wait activities, greater performance may be achieved by increasing the number of engine threads. Note that higher thread counts can cause greater CPU utilization due to higher context switching costs. The default value is 30. Since the majority of AIA flows do not have dehydration points, AIA recommends the value to be set to 20. This parameter can be used to throttle the requests to avoid overloading the mid-tier, database tier, and participating application systems and tune for best performance. DispatcherSystemThreads dspSystemThreads in 10g This property specifies the total number of threads allocated to process system dispatcher messages. System dispatcher messages are general clean-up tasks that are typically processed quickly by the server for example, releasing stateful message beans back to the pool. Typically, only a small number of threads are required to handle the number of system dispatch messages generated during run time. The default value is 2. AIA recommends the default value is kept as is. Disable BPEL Monitors and Sensors Select this check box to disable all BPEL monitors and sensors defined for all BPEL components across all deployed SOA composite applications. syncMaxWaittime This property sets the maximum time the process result receiver waits for a result before returning. Results from asynchronous BPEL processes are retrieved synchronously by a receiver that waits for a result from Oracle BPEL Server. This property is applicable to transient processes. The default value is 45. Value of syncMaxWaittime parameter mainly depends on the scenario and the number of concurrent processes. StatsLastN This property sets the size of the most-recently processed request list. After each request is finished, statistics for the request are kept in a list. A value less than or equal to 0 disables statistics gathering. This property is applicable to both durable and transient processes. For more information, see Configuring BPEL Process Service Engine Properties in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite.

28.4.2 Configuring BPEL Properties Inside a Composite