Configuring BPEL Properties Inside a Composite

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

This section lists the config properties of some sections of the deployment descriptor. For each configuration property parameter, a description is given, and the expected behavior of the engine when it is changed. All the properties set in this section affect the behavior of the component containing the BPEL composite only. Each BPEL process can be created as a component of a composite. These properties are modified through WLST. inMemoryOptimization This property indicates to Oracle BPEL Server that this process is a transient process and dehydration of the instance is not required. When set to True, Oracle BPEL Server keeps the instances of this process in memory only during execution. This property can only be set to True for transient processes or processes that do not contain any Tuning Integration Flows 28-17 dehydration points such as receive, wait, onMessage and onAlarm activities. This property has the following values: ■ False default: instances are persisted completely and recorded in the dehydration store database. ■ True: Oracle BPEL Process Manager keeps instances in memory only. AIA recommends setting the value to True for transient BPEL processes. BPEL processes that have request-response pattern with no dehydration points should have this property set to True. completionPersistPolicy This property configures how much of instance data should be saved. It can only be set at the BPEL component level. AIA recommends setting the property to Off for transient services. In that situation, no instances of process are saved. It persists only the faulted instances. PayloadValidation This property is set at the partnerlink level. 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. When set to True the engine validates the XML message against the XML schema during receive and invoke for this partnerLink. If the XML message is invalid then bpelx:invalidVariables run time BPEL Fault is thrown. This overrides the domain level validateXML property. The default value is False. This value can be overridden to turn on schema validation based on business needs.

28.4.3 How to Monitor the BPEL Service Engine