BPM Application Deployment and Undeployment Issues

Deployment and undeployment of an application can be done from the Administrator UI, Administrator CLI scripts, or from TIBCO Business Studio. TIBCO Business Studio generates CLI scripts and runs them, so in some circumstances has the same effect as using Administrator CLI. The scripts report errors in case of failures.

Warning: Make sure that you have successfully undeployed a BPM application before trying to Delete it.

Do not use Force Delete Application to remove a BPM application, except in the situations described in Cleaning Up Undeployed BPM Applications. Doing so removes artifacts only from Administrator, and leaves Process Manager and other TIBCO ActiveMatrix BPM components out of sync, which can cause problems on restart.

Important: Do not perform the Undeploy nor Force Undeploy operation on the BPM product application, which is named "amx.bpm.app" by default. Performing either of those operations on the BPM product application can cause the system to become unstable and/or unrecoverable, possibly requiring a re-creation of the environment.

To diagnose problems from the Administrator UI:

  • Administrator should show the application in a failed running state. The wordings varies depending on whether the command was to deploy, deploy with start, or undeploy, and where the failure occurred.
  • Under column Action History, click the link to display a detailed view of all of the steps that are associated with the command. Since Administrator stops at the first failure, the last action should show the cause of the failure.
  • Click on a failed-action link to brings up a view of the full exception stack trace. The last “caused by” exception usually is the best indicator of where the source of the problem is. If it shows stack traces that include “com.tibco.bx” and/or “com.tibco.pvm”, the problem is most likely with process engine.
  • For more info, it is necessary to peruse the log files, looking for ERROR entries. If DEBUG logging is enabled, there may be more useful info that can help pinpoint the problem. For more information on logging, see BPM Logging.
  1. Tips for Successful BPM Application Deployment and Undeployment
    Deployment and undeployment of an application can be done from the Administrator UI, Administrator CLI scripts, or from TIBCO Business Studio.
  2. Deploying from TIBCO Business Studio
    You will not be able to deploy an application from TIBCO Business Studio if you cannot connect to the server.
  3. Deployment of Global Signal Definition Project and Process with Global Signal Events
    It is possible to deploy a process with global signal events without deploying the Global Signal Definition project. However, if you do this, then the process will halt with an error at runtime.
  4. Re-Deploy/Upgrade of a Global Signal Definition Run-time Application
    There are a number of issues you should be aware of when re-deploying/upgrading a Global Signal Definition Run-time Application.
  5. A Global Signal Audit Includes Expired Persistent Signals
    A Global Signal audit includes persistent signals after timeout. The signals have expired, but still appear in the Event Viewer. A background job runs periodically to purge expired signals.
  6. Undeploy Does Not Work On An Upgraded Global Signal Definition Application
    Undeploy does not work on an upgraded Global Signal Definition application, for example version 2, when a user application, for example version 1, references it. Use Force Undeploy to undeploy the Global Signal Definition application.
  7. Removing applications from a node
    After removing BPMNode from the amx.bpm.app distribution (and hence all user applications), all BDS Applications go to a 'Deploy with Start Failed' state.
  8. Derived Artifacts
    Visible artifacts (PIMs) are generated into deployment artifacts (PSMs). You can use the Customize View selection to decide whether to include or exclude certain ’dot’ folders (containing visible artifacts) in the Project Explorer project view.
  9. Cleaning Up Undeployed BPM Applications
    If you try to undeploy, or forced undeploy, an application using either the Administrator UI or the CLI, and the undeploy process does not remove all the components from the node runtime, so cleanup utilities are available from TIBCO Support.
  10. The bpm-db-cleanup Utility
    The bpm-db-cleanup utility uses scripts that you can run to clean up your deployed and undeployed applications.
  11. Troubleshooting Failed Deployments After Upgrade
    The handling of application deployment failures for TIBCO ActiveMatrix BPM user applications is managed by providing a workflow to clean up the failed deployment without affecting other dependent applications.
  12. Undeploying Dynamically Generated Organization Model Entities That Have Work Offered To Them
    When un-deploying an organization model that contains dynamically generated Positions, work items offered to those Positions will be moved to the 'un-delivered' queue.
  13. 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.
  14. Upgrading a Business Data Project That References Another Business Data Project Fails
  15. Cleaning Up the Software Repository
    After undeploying or cleaning up an application, sometimes related features remain in the software repository. These should be deleted, otherwise problems can occur during future redeployments.