BPMUndeploy command
This command undeploys a process application snapshot from a server. It is available only if the snapshot contains Advanced Integration Services and has a corresponding business level application (BLA) deployed on the server.
Use the BPMUndeploy command in connected mode to undeploy a process application snapshot from a Process Center or Process Server.
Undeploying the snapshot removes any Service Component Architecture (SCA) modules, monitor models, and business level applications (BLAs) associated with the snapshot. If your process application contains BPEL processes, see the "Deactivating and stopping process applications" link at the end of this topic.
The BPMUndeploy command is run using the AdminTask object of the wsadmin scripting client.
Prerequisites
- Run the command in the connected mode, that is, do not use the wsadmin -conntype none option.
- 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.
Location
Start the wsadmin scripting client from the profile_root/bin directory.
Syntax
BPMUndeploy
-containerAcronym process_application_acronym
-containerSnapshotAcronym process_application_snapshot_acronym
-containerTrackAcronym track_acronym
Parameters
- -containerAcronym process_application_acronym
- A required parameter that identifies the process application acronym. For example, the BillingDispute process application might have an acronym of BILLDISP.
- -containerSnapshotAcronym process_application_snapshot_acronym
- 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. If an Advanced Integration service is used in the Process application, the Tip value triggers the deployment and start of the tip version of the BPEL application.
- -containerTrackAcronym track_acronym
- 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.
Example
The following example illustrates how to establish a SOAP connection to the Process Center server, and then undeploy a snapshot of the BillingDispute process application.
wsadmin -conntype SOAP -port 8880 -host ProcessCenterServer01.mycompany.com -user admin -password admin -lang jython
wsadmin>AdminTask.BPMUndeploy('[-containerAcronym -BILLDISP -containerSnapshotAcronym SS2.0.1]')