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.
The values for the Runtime State and Action History columns against your specific application reveal whether your deployment has failed or succeeded.
Typical failure values for the Runtime State include CONFIGURED_FAILED, Start Failed, Partially Deployed, and Not Deployed. The typical failure value for Action History is Deploy with Start Failed. Combined, these values indicate a failure occurred during deployment.
Deployments are usually successful if the Runtime State shows Running and the Action History shows either In Progress (Deploy with Start) or In Progress(number).
In Progress means that the older version is being phased-out gracefully (that is, waiting for process instances to complete in their natural course).
In Progress(number) usually indicates that there are multiple upgrades being performed for the application and many of them are waiting for the older versions to complete. When the older version completes, the Action History changes to Deploy with Start Successful, but this may take a long time.
To understand why the upgrade/deployment failure occurred, preserve all the log files, such as SystemNode.log, BPMNode.log, tibcohost.log. These logs will help you investigate the cause of the failure at a later time. You should investigate and understand the cause of the failure so that you can address it before re-attempting the deployment.