Use this panel to manage a Business Flow Manager on a given server.
A Business Flow Manager provides services to run BPEL processes within an application server. To view this administrative console page, click Configuration tab, in the Business Process Manager section, expand Business Process Choreographer, click , then on the Business Flow Manager and select the Configuration tab.
Links marked (online) require access to the Internet.
Check for updates to this topic (online)
Specifies the maximum number of times to try to process a message. When the limit is reached, the message is sent to the hold queue.
Property | Value |
---|---|
Field type | Integer |
Default | 5 |
Range | 2 to 10 (recommended) |
The maximum number of messages that can be stored in the retention queue. When the limit is reached, the messages are sent to the queue for internal messages again and the business flow manager switches into quiesce mode.
Property | Value |
---|---|
Field type | Integer |
Default | 20 |
The JNDI name of the queue that contains messages that cannot be processed currently, and that require a retry later.
Property | Value |
---|---|
Field type | Read-only string |
Default | jms/BPERetQueue |
The JNDI name of the queue that holds any messages that failed processing more times than the retry limit.
Property | Value |
---|---|
Field type | Read-only string |
Default | jms/BPEHldQueue |
Common Event Infrastructure logging (CEI) logging can be enabled or disabled.
Property | Value |
---|---|
Field type | Check box |
Audit logging for this Business Flow Manager can be enabled or disabled.
Property | Value |
---|---|
Field type | Check box |
This section allows you to enable navigation performance optimization.
Allows you to enable optimizations for BPEL process navigation.
Property | Value |
---|---|
Field type | Check box |
Default | Selected. When this option is selected, work-manager based navigation is used. When this option is cleared, JMS navigation is used. |
The message pool is used as a buffer when more messages are produced than consumed.
Messages are produced by navigation threads in the work manager, and by API and SCA requests coming into the system. Messages are consumed by the navigation threads in the work manager. If the message pool becomes full, further messages are sent directly to JMS and processed using JMS navigation.
Select this to use the default message pool size that is based on the work manager thread pool.
Property | Value |
---|---|
Field type | Selectable field |
Select the selectable field to specify a value.
Property | Value |
---|---|
Field type | Selectable field and integer input field |
Units | Message objects |
When a message that is handled by the work-manager reaches this age it becomes eligible for recovery or processing using JMS navigation.
Property | Value |
---|---|
Field type | Integer |
Units | Seconds |
Default | 240 |
Specifies how often the Business Process Choreographer triggers tries to recover messages that have reached their maximum age.
Property | Value |
---|---|
Field type | A WebSphere Simple Arithmetic Calendar expression |
Default | 2minutes |
The maximum time that a thread will process messages that navigate a process instance.
A thread will process messages for the same process instance as long as there are messages for this particular process instance available, or until this limit has been reached.
Property | Value |
---|---|
Field type | Integer |
Units | Seconds |
Default | 240 |
The intertransaction cache stores database objects such as BPEL variables and process contexts between transactions.
Either select Use work manager thread pool size to use the default size, or select Intertransaction cache size to enable the input field so that you can specify a value.
Property | Value |
---|---|
Field type | Selectable field and integer input field |
Units | Number of database objects |