Deactivating and stopping installed process applications

Use the Process Admin Console to deactivate and, if necessary, stop snapshots that are installed on a process server. All installed snapshots except the default version can be deactivated. However, you can stop only those snapshots that contain advanced content generated in IBM® Integration Designer (such as SCA modules or BPEL processes).

About this task

Deactivating a snapshot allows all existing business process definition process instances to complete, but no new process instances can be started.

Stopping a process application snapshot stops the associated business-level application (BLA). A BLA is a WebSphere® Application Server configuration artifact that is created only for a snapshot that has advanced content generated in IBM Integration Designer. Use the WebSphere Application Server administrative console to verify that the BLA is in the stopped state.

Note: In a network deployment environment, make sure that all the node agents are active before you stop a BLA. If a node is inactive, the BLA enters the UNKNOWN state instead of the STOPPED state and fails to stop, although the stop command runs asynchronously and completes without an error. The failure to stop along with the UNKNOWN state prevents you from undeploying the BLA.

Using the Deactivate Application action from the Process Admin Console does not stop a BPEL process. Unless you are running the server in development mode or you are running the process application on a Process Center server, you might need to perform additional actions for process applications that include BPEL processes:

If your process application uses a BPEL process as the main entry component, you must stop the corresponding BPEL template in the WebSphere administrative console. See "Administering BPEL process and task templates."
Additionally, if this BPEL process invokes a BPD, you must allow any existing instances to complete after you stop the template but before you deactivate the snapshot. See "Administering BPEL process and task templates."
In all cases, you must clean up the associated process instance data from the Business Process Choreographer database, as described in "Cleanup procedures for Business Process Choreographer."

You cannot deactivate the default snapshot if you have more than one snapshot of a process application installed on the server. In this case, you must first designate another snapshot as the default version. You can deactivate the snapshot only when it is no longer the default version. If the default snapshot is the only snapshot installed on the server, you can deactivate it with no further action.

Procedure

From the Process Admin Console Installed Apps page, select the installed snapshot.
Deactivate the snapshot by clicking Deactivate Application .
If the snapshot contains advanced content, stop it by clicking Stop Application.