Dehydration Properties in SOA 11G

Below properties if we add in composite.xml then instances will be dehydrated

By setting these properties we can achieve lot of performance

...
<component name="myBPELServiceComponent">
....
<property name="bpel.config.inMemoryOptimization">true</property>
<property name="bpel.config.completionPersistPolicy">faulted</property>
</component>

bpel.config.inMemoryOptimization

Default value is false. This property can only be set to true if it does not have
dehydration points. Activities like wait, receive, onMessage, and onAlarm create
dehydration points in the process

bpel.config.completionPersistPolicy

This property configures how the instance data is saved. It can only be set at the
BPEL service component level. The following values are available:

■ on (default): The completed instance is saved normally.
■ deferred: The completed instance is saved, but with a different thread and
in another transaction.
■ faulted: Only the faulted instances are saved.
■ off: No instances of this process are saved.

OutOfMemoryError in SOA

If OutOfMemoryError occurs frequently, then there should be need to increase java

Heap Size memory.

To increase Heap size memory do the following steps

Step1: Make a backup for setSOADomainEnv.sh (/user_projects/domain/<soa_domain_name>/bin/setSOADomainEnv.sh

Step2. In the file called setSOADomainEnv.sh

- replace

DEFAULT_MEM_ARGS="-Xms512m -Xmx1024m"
PORT_MEM_ARGS="-Xms768m -Xmx1536m"

- with

if [ "${SERVER_NAME}" = "SERVERNAME" ]; then
DEFAULT_MEM_ARGS="-Xms2048m -Xmx2048m"
PORT_MEM_ARGS="-Xms2048m -Xmx2048m"
else
DEFAULT_MEM_ARGS="-Xms512m -Xmx1024m"
PORT_MEM_ARGS="-Xms768m -Xmx1536m"
fi

Step3. restart the servers