By default in a BusinessWorks 5.X environment when you deploy an application the previous deployment is kept and it is possible to easily revert to that deployment or an older one if needed. The historization of a deployment includes both the application archive and the deployment configuration.
This is an interesting feature but after time the number of such historized deployments can be large and may slow down new deployments.
This article explains how to truncate the deployment history. This can be done using TIBCO Administrator or using AppManage.
Truncating the deployment history from TIBCO Administrator
By default the deployment history is kept without limit (Max Deployment Revision = -1).
![1*yEZvb4dIt11HdrNnldHlmA.png](https://miro.medium.com/v2/resize:fit:391/1*yEZvb4dIt11HdrNnldHlmA.png)
Which may lead to have a deep deployment history:
![1*xtEG6b78tzHeTVN_7Vbmlg.png](https://miro.medium.com/v2/resize:fit:327/1*xtEG6b78tzHeTVN_7Vbmlg.png)
![1*EuKu8G_KfcTrDSBPMSXNfQ.png](https://miro.medium.com/v2/resize:fit:564/1*EuKu8G_KfcTrDSBPMSXNfQ.png)
It is possible to truncate the deployment history from TIBCO Adminitrator with the following:
. Open the Configuration panel at the application level (the top level)
. Update the Max Deployment Revision parameter to a limited value (for example 5) and Save
![1*LSr7-7dsdUWiQULo3yI3Hg.png](https://miro.medium.com/v2/resize:fit:375/1*LSr7-7dsdUWiQULo3yI3Hg.png)
. Truncate the deployment history
![1*GzPGPB2GV9buaUVLkYWYXA.png](https://miro.medium.com/v2/resize:fit:427/1*GzPGPB2GV9buaUVLkYWYXA.png)
. The history is now limited to the 5 most recent deployments
![1*AMxmvVXkCn0shoW5QyyI6A.png](https://miro.medium.com/v2/resize:fit:605/1*AMxmvVXkCn0shoW5QyyI6A.png)
Truncating the deployment history using AppManage
Using AppManage the same can be achieved by using the following approach:
. Edit the deployment .xml file to update the following tag:
<maxdeploymentrevision>5</maxdeploymentrevision>
. Redeploy the application
Note also that the default value of the ‘Max Deployment Revision’ parameter can be set when a domain is created or by updating an existing domain configuration.
At creation time just set the value of the MaxDeploymentRevision tag in the CreateDomain.xml file:
<MaxDeploymentRevision>5</MaxDeploymentRevision>
To update an existing domain configuration you can use the DomainUtilitycmd tool with the Miscellaneous.xml file template.
![1*2YKBuOGY_Ld0DGyGElU5vw.png](https://miro.medium.com/v2/resize:fit:605/1*2YKBuOGY_Ld0DGyGElU5vw.png)
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now