BPMStop command

This command stops a process application snapshot that has already been deactivated on a process server. It is available only for snapshots that have Advanced Integration Services.

Purpose

Use the BPMstop command in connected mode to stop a deactivated snapshot on a process server. In a network deployment environment, you must run this command on the node containing the application cluster member that handles Process Server applications. Do not run this command from the deployment manager profile.

This command does not stop any running process and task templates that belong to the process application. Use the bpcTemplates.jacl administrative script to stop these before you use the BPMStop command. If there are still running BPEL templates when you run the BPMStop command, it fails. For more information, see "bpcTemplates,jacl administrative script" at the end of this topic.

Note: If you are using a SOAP connection, the command can take longer to complete than the specified SOAP timeout value. Although the command continues to run until it is finished, you might see the exception java.net.SocketTimeoutException: Read timed out. To prevent this exception, set a higher value for the com.ibm.SOAP.requestTimeout property in the profile_root/properties/soap.client.props file.

Parameters

-containerAcronym containerAcronym: A required parameter that identifies the process application acronym. For example, the BillingDispute process application might have an acronym of BILLDISP.
-containerSnapshotAcronym containerSnapshotAcronym: A required parameter that identifies the process application snapshot acronym.
If you are not working with a snapshot, use Tip as the value for this parameter.

Tip: If you do not know the acronym for a required parameter, use the BPMShowProcessApplication command to list the details of a process application, including acronyms.

Example

The following example illustrates how to establish a SOAP connection to the Process Center server, and then stop a snapshot of the BillingDispute process application.

Important: In a network deployment environment, use the port configured for the application cluster member that runs the Process Server or Process Center applications. To determine the correct port number, see the WebSphere administrative console Ports collection page (click Servers > Server Types > WebSphere application servers > server_name > Communications > Ports and find the value for SOAP_CONNECTOR_ADDRESS).

Jython example

wsadmin -conntype SOAP -port 8880 -host ProcessServer01.mycompany.com -user admin -password admin -lang jython

AdminTask.BPMStop('[-containerAcronym BILLDISP -containerSnapshotAcronym SS2.0.1]')

Jacl example

wsadmin -conntype SOAP -port 8880 -host ProcessServer01.mycompany.com -user admin -password admin

$AdminTask BPMStop {-containerAcronym BILLDISP -containerSnapshotAcronym SS2.0.1}