In production env the
deployments are usually script or autosys based.
This is to eliminate error while deployment and make the deployment faster
This is to eliminate error while deployment and make the deployment faster
If the deployment is
done graphically then procedure is the same as in other env
I.e. Install Application >> browse the ear >> next.. Next.. Next.. Finish :-) (Obviously you need to select the appropriate mapping, virtual host etc)
As a procedure per say it’s normally done this way
1) Take the backup of the old ear in both PROD and DR
2) Confirm with the AD where the ear staged is the latest one.
3) Network team flips the DNS to point to the DR
4) Do the deployment in DR
5) Check the logs and access the DR apps , test the application using the DR url
6) If the apps is working fine and its confirmed by the AD team then
7) Network Team to flip the PROD
8) Do the deployment in PROD
9) Check the logs and access the PROD apps , test the application using the PROD url
where AD = Application Development
DR = Disaster Recovery
I.e. Install Application >> browse the ear >> next.. Next.. Next.. Finish :-) (Obviously you need to select the appropriate mapping, virtual host etc)
As a procedure per say it’s normally done this way
1) Take the backup of the old ear in both PROD and DR
2) Confirm with the AD where the ear staged is the latest one.
3) Network team flips the DNS to point to the DR
4) Do the deployment in DR
5) Check the logs and access the DR apps , test the application using the DR url
6) If the apps is working fine and its confirmed by the AD team then
7) Network Team to flip the PROD
8) Do the deployment in PROD
9) Check the logs and access the PROD apps , test the application using the PROD url
where AD = Application Development
DR = Disaster Recovery
No comments:
Post a Comment