Controlling Execution of TIBCO BW services

• 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.
• Use TIBCO admin to control execution of TIBCO BW process instances. Useful if system has limited resources & memory or to restrict process instances to run sequentially.

Go to --> Application Mgmt --> Application configuration --> click proccess service -> Advanced Tab

• Max Jobs : Specifies the maximum number of process instances that can concurrently be loaded into memory. Any process instances created once the maximum is reached must be paged out to disk.
• Activation Limit : Specifies that once a process instance is loaded, it must remain in memory until it completes. useful if you wish to specify sequential processing of incoming events, or if you want to enforce limited concurrent execution of process instances.
• Max Jobs (FLow Limit) : Specifies the maximum number of currently running process instance to start before suspending the process starter. Max Jobs (Flow Limit) field limits the number of process instances created by a process starter. This allows you to control the flow of processing so that incoming events are no longer accepted when the limit is reached. This is useful in protocols like TIBCO RVCM, JMS Durables TOpic, JMS Queue, Recceive Mail etc.