This command activates a process application snapshot on
the Process Center server or Process Server.
Purpose
Use the BPMActivate command
in connected mode to activate a snapshot that has been deactivated,
stopped, or undeployed. Activated snapshots can receive and process
requests.
In a network deployment environment,
an application cluster member runs the Process Server and Process
Center applications. Therefore, you must run this command on the node
that contains that application cluster member. Do not run the command
from the deployment manager profile.
Note that only the business
process definition (BPD) is activated when you activate a process
application. If the process application uses BPEL processes and the
templates were stopped (as described in "Administering BPEL process
and task templates"), follow the instructions in that section to
start the templates.
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.
- -containerTrackAcronym containerTrackAcronym
- On a Process Center server, a required parameter that identifies
the acronym of the track associated with the process application.
Snapshots can have a track if track development is enabled in the
Process Center and is applied for playback on the Process Center server;
by default, the value is Main. Snapshots installed
on a Process Server do not have tracks.
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 activate a snapshot of the BillingDispute process application.
The snapshot is part of the Main track. In the example, the user establishes
a SOAP connection to the Process Center server.
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 and find the value for
SOAP_CONNECTOR_ADDRESS).
- Jython example
wsadmin -conntype SOAP -port 8880 -host ProcessCenterServer01.mycompany.com -user admin -password admin -lang jython
AdminTask.BPMActivate('[-containerAcronym BILLDISP -containerSnapshotAcronym SS2.0.1 -containerTrackAcronym Main]')
- Jacl example
wsadmin -conntype SOAP -port 8880 -host ProcessCenterServer01.mycompany.com -user admin -password admin
$AdminTask BPMActivate {-containerAcronym BILLDISP -containerSnapshotAcronym SS2.0.1 -containerTrackAcronym Main}