Debug

An indicator of whether the Business Process Debugger is enabled. This is not recommended for production environments because it impacts performance. 

Debug Port

The port on which the Business Process Debugger starts. 

Application Mode

An indicator of whether you are balancing processes across multiple BPM Engines. Select from the following options: 

• Single Engine: All processes are handled by one BPM Engine.

• Multiple Engine: Processes are distributed across multiple engines. Persistence must also be enabled; for the Persistance Mode property, select Persist to Database - Multiple Engines.

Receive Timeout (milliseconds)

The number of milliseconds to wait to process a message that has been placed in waiting. Messages are placed in waiting for various reasons, such as when the maximum number of concurrent instances is reached. 

Persistance Mode

An indicator of whether instance data is persisted to the monitoring and recovery database. 

• False: Data is not saved to the monitoring and recovery database.

• Persist to Database - Single Engine: Data is saved to the database and processing is handled by one engine.

• Persist to Database - Multiple Engines: Data is saved to the database and processing is distributed across multiple engines. If you select this, you must set the Application Mode property to Multiple Engine.

Recovery Enabled

An indicator of whether data can be recovered to a previous state in case of failure. Persistence must be enabled in the Persistance Mode and Application Mode properties for recovery to be enabled.

Engine Expiry Interval (seconds)

The number of seconds for the BPM Engine to wait to register itself as alive. For more information, see Configuring Failover.

Failover Grace Period (seconds

The elapsed time period before moving running Business Process instances from an unavailable engine to an available engine. This is used in conjunction with the Engine Expiry Interval property for configuring failover. 

Recovery Batch Size

The number of records to recover at one time. Sun does not recommend setting this higher than 100. 

Database

The type and version of database you are using for monitoring and recovery. If you are using an Oracle 10g database, select Oracle 9i.

Database Host

The name of the machine on which the database resides. 

Database Port

The port number on which the database is listening. 

Oracle Net Service Name

The name for the connect descriptor (for Oracle databases only). This is the TNS name of the database, and is required to access the database using the OCI driver to access the database. If you are not using the OCI driver, leave this property blank. 

Database Instance/Schema

The name of the database. For Oracle, this is the SID name. 

Database User

The login ID for the monitoring and recovery database owner. The user name is defined in the database scripts you ran when creating the database tables (by default, bpm6user).

Database Password

The password for the monitoring and recovery database owner. The password is defined in the database scripts you ran when creating the database tables (by default, bpm6user).

Database Connection Pool Size

The maximum number of physical connections the pool should keep available at all times. 0 (zero) indicates that there is no maximum. The pool size depends on the transaction volume and response time. If the pool size is too big, you may end up with too many connections with the database. Sun recommends setting this no higher than 60. 

Database Connection Retries

The number of retries to establish a connection with the database. 

Database Connection Retry Interval (milliseconds)

The number of milliseconds to wait between each attempt to access the database. This property is used in conjunction with Database Connection Retries.

Database Connection Steady Pool Size

The initial and minimum number of physical connections the pool should keep available at all times. 0 (zero) indicates that there should be no physical connections in the pool and the new connections should be created as needed. If the pool size is too small, you might experience longer connection times due to the existing number of physical connections. 

Database Connection Max Idle Time (Seconds)

The maximum number of seconds that a physical connection will remain unused before it is closed. 0 (zero) indicates that there is no limit. 

Enable Monitoring

Enables monitoring of Business Processes through the Enterprise Manager Monitor. If monitoring is enabled, persistence must also be enabled in the Application Mode and Persistence Mode properties.

Reporting Thread Sleep Time (milliseconds)

The time in milliseconds between transfers of data from the monitoring and recovery database tables to the Business Process reporting tables. 

Monitoring Thread Buffer Size

The number of records at which the buffer contents is transferred to the database (if the thread buffer time lag is not expired). Monitoring data is collected in a memory buffer and is transferred to the monitoring tables based on either the buffer size or the buffer time lag, whichever occurs first. 

Monitoring Thread Buffer Time Lag (seconds)

The time in seconds between transfers of data from the buffer to the monitoring table (if the buffer has not reached the thread buffer size). 

Monitoring Thread Sleep Time (milliseconds)

The time in milliseconds between transfers of data from the buffer to activity monitoring table. 

Work Item Submit Limit

The maximum number of work items the BPM Engine can submit to the integration server at a given time for execution. A work item is an activity or group of activities in a Business Process submitted as a single unit of work to be run on an integration server thread. 

Invocation Allocation Ratio (%)

Specifies the percentage of the total Work Item Submit Limit threads that can be used for invoke activities, as opposed to other types of activities. Setting this ratio to 100% can cause a deadlock.

Automatic Execution of Database Scripts

Specifies whether database scripts will be run automatically.