AppManage is deploying the same BW engine despite being the same version already deployed.
Article ID: KB0093031
Updated On:
| Products | Versions |
|---|---|
| TIBCO Administrator | - |
| Not Applicable | - |
Description
Description:
In certain cases, AppManage is not able to recognize that same
version of a service does not need to be redeployed when there is nothing changed in those apps. The
service deployment should be "skipped" with an error noting that, "not able
to deploy application <name> due to being in deployment status
Synchronized". Because of that, the exact same service gets redeployed.This
is leading to some inefficiencies in the deployment process, when AppManage believes versions of deployed services are different when they
are not.
Symptoms:
Redeployment of existing application services although nothing has been changed. The status of the services shows "deployed". However, when clicking on the application .par, the status shows as "deployable".
Cause:
One of the cause is that the xml used by deployment has empty value. Most of the time it is happening when users have introduce a new element in the binding or making changes into the element value.
For example:
<prepandClassPath></prepandClassPath> (space between start and end tag)
<appendClassPath></appendClassPath> (space between start and end tag)
Resolution
Enter a value between those XML element tags. The value can simply be a "space" when no value should be entered.
Issue/Introduction
AppManage is deploying the same BW engine despite being the same version already deployed.
Feedback
Yes
No
Powered by
