WebSphere

Business Flow Manager settings

Use this panel to manage a Business Flow Manager on a given server.

A Business Flow Manager provides services to run business processes within an application server. To view this administrative console page, click Servers > Clusters > cluster_name or Servers > Application servers > server_name, then under Business Integration, expand Business Process Choreographer, and click Business Flow Manager > Configuration.

Note: Changes made on this panel do not affect the server until after it is restarted.

Retry limit

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
Data type Integer
Default 5
Range 2 to 10 (recommended)

Retention queue message limit

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
Data type Integer
Default 20

Retention queue

The JNDI name of the queue that contains messages that cannot be processed currently, and that require a retry later.

Property Value
Data type Read-only string
Default jms/BPERetQueue

Hold queue

The JNDI name of the queue that holds any messages that failed processing more times than the retry limit.

Property Value
Data type Read-only string
Default jms/BPEHldQueue

Enable Common Event Infrastructure logging

Common Event Infrastructure logging (CEI) logging can be enabled or disabled.

Property Value
Data type Check box

Enable audit logging

Audit logging for this business flow manager can be enabled or disabled.

Property Value
Data type Check box

Cleanup service

This section contains the configuration parameters for the cleanup service, which you can setup to delete different types of instances.

Enable cleanup service

The cleanup service can be can be enabled or disabled. Select the check box to enable the service.

Property Value
Data type Check box
Default Disabled (clear)
Note: To specify the templates for which the cleanup service will deleted instances, you must Add one or more Cleanup Jobs.

Frequency

The schedule for running the cleanup jobs.

Type Value
Data type String
Format This field uses the WebSphere crontab format <Seconds> <Minute> <Hour> <Day_of_the_Month> <Month_of_the_Year> <Day_of_the_Week> according to com.ibm.websphere.scheduler.UserCalendar
Example To run the once per hour, use the schedule 0 0 * * * ?
Default 0 0 1 * * ? (every night at one o'clock)

Maximum duration

If the cleanup takes longer than the time specified here, the current transaction slice for the current cleanup job is completed, then the current cleanup job is stopped, and no more cleanup jobs are run before the next scheduled cleanup.

Type Value
Data type Integer
Default 120
Units Minutes

Transaction slice

The size of the transaction for the delete operation.

Type Value
Data type Integer
Default 10
Units Business process or human task instances per database transaction

Business Process Navigation Performance

This section allows you to enable navigation performance optimization.

Enable advanced performance optimizations

Allows you to enable optimizations for business process navigation.

Property Value
Data type Checkbox
Default Cleared. When this option is cleared, JMS navigation is used. When this option is selected, asynchronous Beans are used.

Message pool size

Either select the radio button to use the default, or specify a value.

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.

Property Value
Data type Radio button and integer input field
Units Message objects
Default Work manager thread pool size * 10

Maximum age for stalled messages

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
Data type Integer
Units Seconds
Default 240

Recovery interval for stalled messages

Specifies how often the Business Process Choreographer triggers tries to recover messages that have reached their maximum age.

Property Value
Data type A WebSphere Simple Arithmetic Calendar expression
Default 2minutes

Maximum process time on thread

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
Data type Integer
Units Seconds
Default 240

Intertransaction cache size

This specifies how many database objects, such as BPEL variables and process contexts are kept in the cache between transactions.

Use the checkbox to either enable the field so that you can specify a value, or to use the default value.

Property Value
Data type Integer
Units Number of database objects
Default The thread pool size of the navigation work manager.

topic Topic topic

Terms of use | Feedback


Timestamp icon Last updated: 26 July 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wbpmhelp.620.doc/com.ibm.ws.console.bpc.bpelflowmanager/ueac_flowcontainersettings.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).