Undeploying BPEL process and human task applications, using the administrative console
You can use the administrative console to undeploy applications that contain BPEL processes or human tasks.
Before you begin
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 deployment manager 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 deployment manager and the managed server must be running. The server must have access to the Business Process Choreographer database.
- Either there are no instances of BPEL process or human task templates present in any state, or 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.
- Make sure that no other modules depend on the services exported by the application that you want to undeploy.
About this task
Procedure
Results
The application is undeployed.