Undeploying BPEL process and human task applications, using an administrative command

Using the bpcTemplates.jacl script provides an alternative to the administrative console for undeploying applications that contain BPEL processes or human tasks.

To undeploy an application that contains BPEL processes or human tasks, the following conditions must apply:

• If the application is deployed on a stand-alone server, the server must be running and have access to the Business Process Choreographer database.

• If the application is deployed on a cluster, the dmgr and at least one cluster member must be running. The cluster member must have access to the Business Process Choreographer database.

• If the application is deployed on a managed server, the dmgr and the managed server must be running. The server must have access to the Business Process Choreographer database.
• Ensure that the server process to which the administrative client connects is running. To ensure that the administrative client automatically connects to the server process, do not use the -conntype NONE option as a command option.

• If WebSphere administrative security is enabled, and your user ID does not have operator or administrator authority, include the wsadmin -user and -password options to specify a user ID that has operator or administrator authority. The -uninstall option requires operator authority and the -force option requires administrator authority.

• One or more of the following is true:

  • There are no instances of BPEL process or human task templates present in any state.

  • You intend to use the -force option.
  • You have a stand-alone server that is running in development mode.

• If a process instance was migrated to a newer version of the process but it is waiting for a service invocation to reply, the application that contains the previous version cannot be undeployed until the reply is received. In all other cases, instances that have been migrated are considered to be instances of the new version, and the application that contains the older version of the process can be undeployed.
• Verify that no other modules depend on the services exported by the application that you want to undeploy.

The following steps describe how to use the bpcTemplates.jacl script to undeploy applications that contain BPEL process templates or human task templates.

Procedure

1. If there are still process instances or task instances associated with the templates in the application that you want to undeploy perform one or both of the following:

   • Use the Business Process Choreographer Explorer to delete the instances.

   • In cases where you are sure that no other BPEL processes depend on the process templates that are defined in the application you want to undeploy, you can use the -force option.

     CAUTION:

     If you use the script with this option, it deletes any instances that are associated with the templates, all of the data that is associated with any running instances, stops the templates, and undeploys the application in one step. Use this option with extreme care.

2. Change to the Business Process Choreographer subdirectory where the administrative script is located.
   

   cd  INSTALL_ROOT/ProcessChoreographer/admin

   cd INSTALL_ROOT/ProcessChoreographer/admin

   cd INSTALL_ROOT\ProcessChoreographer\admin

3. Stop the templates and undeploy the corresponding application.

   On Windows platforms, enter:

    INSTALL_ROOT\bin\wsadmin -f bpcTemplates.jacl 
                                 -uninstall  application_name
                                [-force]

   

   On Linux and UNIX platforms, enter:

    INSTALL_ROOT/bin/wsadmin -f bpcTemplates.jacl 
                                 -uninstall  application_name
                                [-force]                             

   

    INSTALL_ROOT/bin/wsadmin.sh -f bpcTemplates.jacl 
                                 -uninstall  application_name]
                                [-force]

   Where:

   -uninstall application_name

   This specifies the name of the application to be undeployed. Do not use this option for applications that were deployed using the Process Center.

   -force

   This option causes any running instances to be stopped and deleted before the application is undeployed. Use this option with care because it also deletes all of the data associated with the running instances.

Results

The application is undeployed.

Deploying BPEL process and human task applications

Related tasks:
Undeploying BPEL process and human task applications, using the administrative console