A Sample Migration Environment
Machine 1 : DMGR + AppServer profile (V7.0)
Machine 2 : AppServer profile (V7.0)Preparation
1) Define the production deployment setup. You could probably create deployment diagrams for the existing and the new environments.
2) Ensure required infrastructure like disk space requirements are available.
3) Identify and create a list of dmgr configurations to be verified post migration.
4) Identify and create a list of application server configurations to be verified post migration.
5) Clearly define the list of hardening requirements and other process to be implemented on the new environment.
6) Keep a list of learning's from previous migration testing exercises that has to be applied on the migrated dmgr and application server profiles.
7) Identify all of the scripts that are being used on the existing environment.
8) Identify all the dependencies of the existing environment like the databases , webservers etc.
9) Define Profile Migration sequence.
a)Migrate DMGR profile to WAS8.0 on Machine 1
b)Migrate application server profile to WAS8.0 on Machine 1
c)Migrate application server profile to WAS8.0 on Machine 2
10. Define Rollback plan also to handle any unforeseen issues that arises out of the migration activity
Eg : In case of any issues in using the new WAS 8.0 (functionality/performance), the mitigation plan is to shutdown WAS 8.0 server instances and run all WAS 7.0 instances as in before the migration.Execution :
1) Download and copy the necessary installable for WebSphere Application Server on the target machines.
2) Perform the installation of WebSphere Application Server and upgrade to the required fixpack level on all the nodes.
Note that the installation tools have changed in V8.0 to use the IBM Installation Manager.
3) Migrate the WAS V7.0 DMgr profile to create a new WAS 8.0 DMgr profile.
a) Take a backup of the existing WAS7.0 deployment manager
b) Use the IBM Migration tool to migrate the WAS V7.0 DMgr profile to create a new WAS 8.0 DMgr profile.
During the migration consider these parameters like Target Profile name, Target Node name , Cell name
You may choose to : Backup the configuration of the WAS 7.0 profile, Migrate and install the applications, Install the applications in the default directory of the target WAS instance
Not to disable the previous Deployment Manager (WAS 7.0), create new set of ports, Migrate to support script compatibility
c) Verify and validate the migration log for any errors.
d) Apply any learning’s from the earlier UAT testing process
e) Review the WAS 8.0 DMgr profile to ensure the all of the WAS 7.0 configurations are carried forward
f) Go through the hardening process for the new Dmgr profile
4) Again on Machine 1 migrate the WAS 7.0 App Server profile to create a new WAS 8.0 App Server profile by repeating the the steps outlined in point 3.
5) On Machine 2 migrate the WAS 7.0 App Server profile to create a new WAS 8.0 App Server profile by repeating the the steps outlined in point 3.
6) Update the set of monitoring scripts wrt the new set of servers in this new profile
7) You may consider to create a Database instance for Session DB usage for the new WAS 8.0 environment. It should have same configuration/parameter settings of the existing production DB.
8) Update the DataSource configuration for Session DB on the Deployment Manager
9) Perform some sanity test to the application.
10. Test the application for functionality, performance and other other criterias you may wish to.
11. Tune the environment.
12. The environment has to be monitored for any issues before being put to production
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions."