1 person found this helpful
This is expected that WebLogic Server appends an Archive Version Number to the Application Name.
Please, see the note below :
As a test, you can use the -appversion option from the commandline too. It will work the same way.
Using side by side deployment strategy, you can experience how to use the WebLogic server to re-deploy
a new version of production application with out interrupting the availability of the application to new client request.
The way the new client gets connected to the new version of the application and the previous version
of the application is still in use by the older clients and gets retrived after the client disconnects.
1) Copy benefits.war in new folder and deploy
3) java WebLogic.Deployer –adminurl t3://localhost:7001 –username <your_username> –password <your_password> –name benefits –source <app_location>/benefits.war –nostage –targets ms1,ms2 –deploy -appversion version1
4) Copy benefits.war into another folder(new_war) and extract it
jar –xvf benefits.war
5) Modify your application, for example :
Edit the welcome file, find the string of "Color:navy" and replace it with "Color:green" .
7) jar –cvf benefits.war *(or) jar –cvf benefits.war “.”
8) Delete all files except benefits.war
9) Now deploy benefits.war :
java WebLogic.Deployer –adminurl t3://localhost:7001 –username <your_username> –password <your_password> –name benefits –source <New_app_location>/benefits.war –nostage –targets ms1,ms2 –deploy -appversion version1
10) Test the application version1 before version2 deploy. After version2 gets deployed, test the application to see the difference.
The version1 application is in retired state.
The version string specified with -appversion is applied only when the deployment source files do not specify a version string in MANIFEST.MF.
Do not use -appversion to deploy or redeploy in a production environment unless you are certain
the application follows Oracle's programming conventions for production redeployment.
See Section 8.3.3, "Requirements and Restrictions for Production Redeployment".
Using production redeployment with an application that does not follow the programming conventions can cause corruption of global resources
or other undesirable application behavior.
I believe this information should help you too.