Deleting snapshots on workflow servers

You can delete an inactive process application snapshot on any test or production workflow server. The process that you use varies depending on whether you are using the IBM® Business Automation Workflow Advanced deployment environment or the Standard deployment environment. You might want to delete snapshots and their dependencies if you no longer need them or if you have concerns about space on your system.

Before you begin

To delete snapshots on workflow servers, ensure that you meet the following prerequisites:

You have administrative access to the snapshot.
There are no running instances
There are no running BPEL instances.

If you need more information on how to complete these prerequisites, see the related links.

Procedure

Use one of the following sequences of wsadmin commands to delete a snapshot.

Option	Description
Advanced deployment environment	Run the BPMShowProcessApplication command to determine whether the snapshot exists for the process application. Run the BPMShowSnapshot command to determine the status of the snapshot, including whether it is the default snapshot and whether it is active with running instances. If the capability of the snapshot is Standard, then you should skip the remainder of the steps for the Advanced option and instead use the following instructions for the Standard option. Use the -showDependents parameter to display a list of toolkit and process application snapshots that have dependencies on the snapshot. Run the BPMDeactivate command to deactivate the snapshot. Run the BPMStop command to stop the snapshot and its running instances. Run the BPMUndeploy to undeploy the snapshot from the server. This command also uninstalls any business-level applications that are related to the snapshot. Run the BPMDeleteSnapshot command to delete the process application snapshot from the server. If you are deleting the default snapshot, you must use the -force parameter. When the default snapshot of a process application is deleted, the process application is removed. Toolkits that the process application depended on remain. There might be other toolkits and process applications depending on those remaining toolkits. The toolkits cannot be deleted while those dependencies exist. To delete toolkits, complete the following steps: Deactivate the toolkit snapshot of the dependency with the BPMDeactivate command. Stop the toolkit snapshot with the BPMStop command. Get a list of toolkits and process applications that have dependencies on the toolkit snapshot with the following command: `BPMShowSnapshot -showDependents snapshot_name`. Starting with the root of the list of reported dependencies, remove each dependency. For each dependency that you want to remove, delete the snapshot of the toolkit or process application. After you resolve all of the dependencies, delete the snapshot with the BPMDeleteSnapshot command.
Standard deployment environment	Run the BPMShowProcessApplication command to determine whether the snapshot exists for the process application. Run the BPMShowSnapshot command to determine the status of the snapshot, including whether it is the default snapshot and whether it is active, with running instances. Use the -showDependents parameter to display a list of toolkit and process application snapshots that have dependencies on the snapshot. Run the BPMDeactivate command to deactivate the snapshot. Run the BPMDeleteSnapshot command to delete the process application snapshot from the server. If you are deleting the default snapshot, you must use the -force parameter. When the default snapshot of a process application is deleted, the process application is removed. Toolkits that the process application depended on remain. There might be other toolkits and process applications depending on those remaining toolkits. The toolkits cannot be deleted while those dependencies exist. To delete toolkits, complete the following steps: Deactivate the toolkit snapshot of the dependency with the BPMDeactivate command. Stop the toolkit snapshot with the BPMStop command. Get a list of toolkits and process applications that have dependencies on the toolkit snapshot with the following command: `BPMShowSnapshot -showDependents snapshot_name`. Starting with the root of the list of reported dependencies, remove each dependency. For each dependency that you want to remove, delete the snapshot of the toolkit or process application. After you resolve all of the dependencies, delete the snapshot with the BPMDeleteSnapshot command.

Option

Description

Advanced deployment environment

Run the BPMShowProcessApplication command to determine whether the snapshot exists for the process application.
Run the BPMShowSnapshot command to determine the status of the snapshot, including whether it is the default snapshot and whether it is active with running instances. If the capability of the snapshot is Standard, then you should skip the remainder of the steps for the Advanced option and instead use the following instructions for the Standard option. Use the -showDependents parameter to display a list of toolkit and process application snapshots that have dependencies on the snapshot.
Run the BPMDeactivate command to deactivate the snapshot.
Run the BPMStop command to stop the snapshot and its running instances.
Run the BPMUndeploy to undeploy the snapshot from the server. This command also uninstalls any business-level applications that are related to the snapshot.
Run the BPMDeleteSnapshot command to delete the process application snapshot from the server. If you are deleting the default snapshot, you must use the -force parameter.
When the default snapshot of a process application is deleted, the process application is removed. Toolkits that the process application depended on remain. There might be other toolkits and process applications depending on those remaining toolkits. The toolkits cannot be deleted while those dependencies exist. To delete toolkits, complete the following steps:
1. Deactivate the toolkit snapshot of the dependency with the BPMDeactivate command.
2. Stop the toolkit snapshot with the BPMStop command.
3. Get a list of toolkits and process applications that have dependencies on the toolkit snapshot with the following command: BPMShowSnapshot -showDependents snapshot_name.
4. Starting with the root of the list of reported dependencies, remove each dependency. For each dependency that you want to remove, delete the snapshot of the toolkit or process application.
5. After you resolve all of the dependencies, delete the snapshot with the BPMDeleteSnapshot command.

Standard deployment environment

Run the BPMShowProcessApplication command to determine whether the snapshot exists for the process application.
Run the BPMShowSnapshot command to determine the status of the snapshot, including whether it is the default snapshot and whether it is active, with running instances. Use the -showDependents parameter to display a list of toolkit and process application snapshots that have dependencies on the snapshot.
Run the BPMDeactivate command to deactivate the snapshot.
Run the BPMDeleteSnapshot command to delete the process application snapshot from the server. If you are deleting the default snapshot, you must use the -force parameter.
When the default snapshot of a process application is deleted, the process application is removed. Toolkits that the process application depended on remain. There might be other toolkits and process applications depending on those remaining toolkits. The toolkits cannot be deleted while those dependencies exist. To delete toolkits, complete the following steps:
1. Deactivate the toolkit snapshot of the dependency with the BPMDeactivate command.
2. Stop the toolkit snapshot with the BPMStop command.
3. Get a list of toolkits and process applications that have dependencies on the toolkit snapshot with the following command: BPMShowSnapshot -showDependents snapshot_name.
4. Starting with the root of the list of reported dependencies, remove each dependency. For each dependency that you want to remove, delete the snapshot of the toolkit or process application.
5. After you resolve all of the dependencies, delete the snapshot with the BPMDeleteSnapshot command.