Answers to a set of frequently asked questions about administering business processes.
If a currently valid process template is in the started state, but the application is in the stopped state, no new process instances are created from the template. Existing process instances cannot be navigated while the application is in the stopped state.
Using the administrative console, select a process template, and click Stop. This action put the process template into the stopped state, and no more instances are created from the template. After the template stops, any attempts to create a process instance from the template result in an EngineProcessModelStoppedException error.
If a process template is no longer valid, this fact has no effect on running instances that were instantiated from the template. Existing process instances continue to run to completion. Old and new instances run in parallel until all of the old instances have finished, or until they have been terminated.
Changing the state of a process template to 'stopped' only stops new instances being created. Existing process instances continue running until completion in an orderly way.
Log on to the Business Process Choreographer Explorer as a process administrator, and go to the Process Instances Administered By Me page, this displays any running process instances. If necessary, you can terminate and delete these process instances.
For a process instance to run, its corresponding application must also be running. If the application is stopped, the navigation of the process instance cannot continue. For this reason, you can only stop a business process application if it has no process instances.
Last updated: Tue Dec 06 04:14:40 2005
(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)