WebLogic Server Versioned Application Doesn't Use In-Place Redeployment as Expected
(Doc ID 1558237.1)
Last updated on NOVEMBER 14, 2022
Applies to:Oracle WebLogic Server - Version 9.2 and later
Information in this document applies to any platform.
We currently have three WebLogic clustering environments (Test/UAT/production) that host our Java applications. We are using the side-by-side deployment (production redeployment) technique in our application deployment process by adding a version identifier to the MANIFEST file in our application, following the directions at https://docs.oracle.com/cd/E23943_01/web.1111/e13702/redeploy.htm#i1023104. WebLogic Server allows a maximum of 2 application versions that can exist at the same time: one in Retired mode and one in Active mode. Before we redeploy a third version of the application, we have to undeploy the Retired one first. This process is fine in the production environment. However, it is unnecessary on our Test and UAT environments. Can we only keep one version of the application in our Test and UAT environment? If we redeploy a new version of the application, the previous one can be removed automatically. In other words, we would like to be able to undeploy and redeploy at the same time so we don't need to go through 2 steps (undeploy and redeploy).
We tried to use in-place redeployment as specified at https://docs.oracle.com/cd/E23943_01/web.1111/e13702/redeploy.htm#i1024682 but the deployment still kept the retired version of the app alongside the new version.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document