Undeployment of TIBCO ActiveMatrix BPM Business Data Services Applications

In TIBCO ActiveMatrix Administrator, while undeploying BDS applications and other dependent applications, always first undeploy the dependent applications, and then undeploy the BDS applications separately.

Avoid multi-selecting the BDS and other dependent applications and undeploying them together. Doing so will cause the undeploy never to complete even after all process instances and work items have been completed. The following state indicates that you have run into the issue of undeployment never completing: There are no open process instances or work items for the applications you undeployed. The Application State for the BDS application shows "Preparing for undeploy".

The Application State for the dependent user applications shows "Not Deployed". After using Force Undeploy on the BDS application, the dependent user application shows an Action History of Undeploy Failed and the BDS application shows an action history of Force Undeploy Failed.

If your undeployment action for the set of applications is stuck in this state, use the following steps to free it:

Remove the features used by the dependent user applications from all the BPM nodes as follows:

  • Identify the features used by each user application.
  • Using ActiveMatrix Administrator, remove the features from each BPM node.
To identify features used by an application:
  • DAA for a project that contains a BOM with Local Classes will have a custom feature named Studio Project LifeCycleID.model.bds.
  • DAA for a Business Data Project will have a custom feature named Studio Project LifeCycleID.model.bds Studio Project LifeCycleID.da.bds
To remove features from nodes using TIBCO ActiveMatrix Administrator:
  • In Administrator UI go to Infrastructure > Nodes > BPM Node > Configuration screen.
  • Select the features identified in the procedure above, and click on Remove.
  • Click Save, and after it completes, click Apply.
  • Refresh the screen and verify that the features you removed are no longer listed in list of features.

There may be additional software repository cleanup required (see Cleaning Up the Software Repository).

Next topic: Cleaning Up the Software Repository
Previous topic: Undeploying Dynamically Generated Organization Model Entities That Have Work Offered To Them