Professional Documents
Culture Documents
Process Configurations
Process Configurations
TIBCO BUSINESSWORKS
IN
3/21/12
MAX
activation limit
maximum number of process instances that can concurrently be loaded into memory
maximum number of concurrently running process instance to start before suspending the process starter
3/21/12
3/21/12
3/21/12
FLOW_CONTROLLED state
WHEN?
When a process engine reaches the Flow Limit, it is placed in this state
The process engine can continue executing existing process instances, but new process instances are not allowed.
WHAT?
3/21/12
Leaving FLOW_CONTROLLED state A process engine leaves this state when the number of process instances completed is approximately half of the value specified for the Flow Limit
3/21/12
When Flow Limit is set on a process containing this starter, the maximum number of incoming requests is limited to FLOWLIMIT -1
3/21/12
Recommended Usage
Use minProcessors and maxProcessors to control the flow of incoming HTTP requests instead of using the Flow Limit property
3/21/12
DISK
MEMORY
3/21/12
3/21/12
3/21/12
Effects of configurations
Max Jobs
Flow Limit
Unlimited number of process instances can be created and can be concurrently loaded into the memory Use of Activation limit is ignored when Max Jobs is 0
3/21/12
Effects of configurations
Max Jobs
Flow Limit
Allows n process instances to be created before placing process starter in flow controlled state No paging of process instances Use of Activation limit is ignored when Max Jobs is 0
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
Allows n process instances to be created before placing process starter in flow controlled state One process instance is loaded into memory at a time and kept there until it completes its execution This guarantees incoming events are processed in the order in which they occur
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
There is no limit on the number of process instances that can be created One process instance is loaded into memory at a time and kept there until it completes its execution This guarantees incoming events are processed in the order in which they occur
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
Allows n process instances to be created before placing process starter in flow controlled state One process instance is loaded into memory at a time Incoming events can be processed in any order as process instances are not kept in memory until they complete execution
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
There is no limit on the number of process instances that can be created m process instances can be loaded into memory at a time and processed concurrently
Ensures limited amount of concurrent processing. Useful when you have limited resources like database connections. Set m to a small number, use activation limit. Each loaded process uses a resource until it completes. Once it completes, a new process is loaded and would use the same resource
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
Allows n process instances to be created before placing process starter in flow controlled state m process instances can be loaded into memory at a time and processed concurrently
Ensures limited amount of concurrent processing. Useful when you have limited resources like database connections. Set m to a small number, use activation limit. Each loaded process uses a resource until it completes. Once it completes, a new process is loaded and would use the same resource
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
There is no limit on the number of process instances that can be created m process instances can be loaded into memory at a time and processed concurrently
After m process instances are created, new process instances are paged to disk. There is no guarantee of the order in which the process instances are executed
3/21/12
Effects of configurations
Max Jobs Use Activation Limit Flow Limit
Allows n process instances to be created before placing process starter in flow controlled state m process instances can be loaded into memory at a time and processed concurrently
After m process instances are created, new process instances are paged to disk. There is no guarantee of the order in which the process instances are executed
3/21/12