Page Comparison

<tns:WSO2BPS>

The root element of bps.xml which does not have attributes defined. Each of its child elements and their configurations are described below.

Using the DataBaseConfig element you can configure the data sources used by the business process server for storing process/instance data. Check each of its sub elements for details of each configuration.

Database Configuration for WSO2 BPS BPEL Engine's Persistence Storage

<tns:ProcessDehydration maxCount="" value="">

        <tns:MaxAge value="0"/>

<tns:EventListeners>
        <tns:listener class=""/>
</tns:EventListeners> 

• When the BPEL server is invoked, before any attempt to route the message exchange to a process.
• When the BPEL server is invoked, after the message exchange has been routed to the process.
• When the BPEL server is invoked, after the message exchange has been routed to the process and it has been determined that a new instance needs to be created.
• When a partner link is invoked.

<tns:ExtensionBundles>
<tns:runtimes>
<tns:runtime class="org.wso2.bps.SampleExtensionRuntime"/>
</tns:runtimes>
<tns:filters>
<tns:filter class="org.wso2.bps.SampleCorrelationFilter"/>
</tns:filters>
</tns:ExtensionBundles>

<tns:ExternalServiceTimeOut value=""/>

<tns:MultithreadedHttpConnectionManagerConfig>
        <tns:maxConnectionsPerHost value=""/>
        <tns:maxTotalConnections value=""/>

<tns:Schedules>
        <tns:Schedule when="">
            <tns:cleanup>
                <tns:filter></tns:filter>
            </tns:cleanup>
        </tns:Schedule>
</tns:Schedules>

<tns:SyncWithRegistry>

By default all the BPEL packages are read from the file system. If you need to Synchronize the file system BPEL repository, set the <tns:SyncWithRegistry> element to true. This checks the timestamp of the BPEL packages in the file system against the BPEL packages in the registry. If they do not match then the BPEL package in the registry is copied to the file system.

<tns:InMemoryInstanceTimeToLive>

The property 'InMemoryInstanceTimeToLive' can be used to limit the time-to-live of in-memory instances. This setting is useful to avoid memory leaks related to in-memory processes that may get 'stuck' during execution and never terminate (time should be specified in milliseconds).

<tns:ODESchedulerThreadPoolSize>0</tns:ODESchedulerThreadPoolSize>

Configure this property to control the number of threads in the ode scheduler thread pool. This value should always be smaller than the maximum number of db connections configured for the bps persistance store data source. If you are using both human tasks and bpel with b4p extension activity configure this values to be less than half of maxActive database connections number.

ThreadPoolSize < maxActive Connections => Only using BPEL processes

ThreadPoolSize < (maxActive Connections) / 2 => Using both BPEL processes and Human Tasks

Always try to provide as much database connections as possible to BPS.

<tns:UseDistributedLock>true</tns:UseDistributedLock>

This property is used to enable hazelcast based synchronization mechanism to prevent instance state from being concurrently modified from multiple bps nodes.