Configuring bps.xml

<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

This name is typically specified in <BPS_HOME>/repository/conf/datasources.properties file. 

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

        <tns:MaxAge value="0"/>

• True:
• False:

<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>

• True:
• False:

<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.

<tns:NodeId></tns:NodeId>

You can assign a unique id to identify each node in the cluster using this property.

<tns:ODESchedulerQueueLength>1000</tns:ODESchedulerQueueLength>

Maximum number of jobs that can have in the near future todo queue.

<tns:ODESchedulerImmediateInterval>30000</tns:ODESchedulerImmediateInterval>

Jobs scheduled with a time that is between now and until immediate interval specified here in milliseconds, will be assigned to the current node in the cluster and placed directly on the todo queue.

<tns:ODESchedulerNearFutureInterval>600000</tns:ODESchedulerNearFutureInterval>

Jobs scheduled with a time that is after immediate interval from now and up until near future interval specified here in milliseconds will be assigned to the current node, but will not be placed on the todo queue. The promoter will pick them up later.

<tns:ODESchedulerStaleInterval>10000</tns:ODESchedulerStaleInterval>

Stale nodes will be checked in this time interval specified in milliseconds.

<tns:ODESchedulerTransactionsPerSecond>100</tns:ODESchedulerTransactionsPerSecond>

Specify the estimated sustained transactions per second capacity of the system. This number is used to determine how many jobs to load from the database at once.

 e.g. 100 means the system can process 100 jobs per seconds, on average

<tns:ODESchedulerWarningDelay>300000</tns:ODESchedulerWarningDelay>

Duration used to log a warning if a job scheduled at a particular date time and it is queued to execute after a delay that is more than specified here in milliseconds.

<tns:ODESchedulerImmediateTransactionRetryLimit>3</tns:ODESchedulerImmediateTransactionRetryLimit>

Number of immediate retries, if a transaction failed.

<tns:ODESchedulerImmediateTransactionRetryInterval>1000</tns:ODESchedulerImmediateTransactionRetryInterval>

Interval between immediate retries if a transaction failed.

<tns:InstanceViewVariableLength>1000</tns:InstanceViewVariableLength>

Set the maximum size for a variable in a instance view in kilobytes. Higher sizes may slowdown the instance view rendering in the user interface. Default size is 1000KB. Please note that this only limits the displayed content size of the variable, not the actual size.

<tns:BpelInstanceDeletionLimit>1000</tns:BpelInstanceDeletionLimit>

This property specify the maximum number of BPEL process instances that can be deleted in a single delete instance request in a bulk delete. Increase this with caution. It may result in various timeout exceptions.

<tns:TransactionManagerTimeout></tns:TransactionManagerTimeout>

Timeout for the BPEL Transaction Manager in seconds. Default is 10 minutes.