Controlling Execution of TIBCO BusinessWorks Services
Process starters create process instances to handle incoming events. Process instances consume memory and CPU resources on your system. Depending on the available machine resources, you may only be able to run a limited number of process instances concurrently.
Process instances typically remain in memory as long as they are executing an activity. If the process instance is waiting for an incoming event (for example, a Wait for Adapter Message activity), the process instance can be paged out to disk and resumed later after the event arrives. New process instances are paged out to disk until there is available memory and resources to accommodate them.
You can use TIBCO Administrator to control the execution of TIBCO BusinessWorks process instances. This is useful if your system has limited memory or resources, or if you want to restrict process instances to run sequentially.
The TIBCO BusinessWorks Process Configurations dialog, accessed by selecting the process archive in the Configuration Builder, allows you to specify the following:
-
Max Jobs — Specifies the maximum number of process instances that can concurrently be loaded into memory.
-
Activation Limit — Specifies that once a process instance is loaded, it must remain in memory until it completes.
-
Max Jobs (Flow Limit) — Specifies the maximum number of currently running process instance to start before suspending the process starter.
The following sections describe these configuration settings and the relationship between the settings.
To Access the Process Configurations
- Procedure
-
Select the process archive (
.par) in the application’s Configuration Builder pane. -
Click the Advanced tab and the + next to the process archive’s name.