Technical Blog Post
Using the WebSphere 9 Migration Tool with Maximo 7.6, part 1
In this blog post, I will go step by step on a simple migration: out-of-the-box Maximo Asset Management 22.214.171.124 from WebSphere Application Server 126.96.36.199 to WebSphere Application Server traditional 188.8.131.52.
Existing WebSphere Application Server 184.108.40.206 or later server, preferably installed using the Maximo Launchpad and Configuration Tool.
Have already downloaded WebSphere Application Server traditional 220.127.116.11 and installed it to this server. Applied WAS V9.0 Fix Pack 3 or later.
Have not yet run WebSphere Customization Toolbox Version 9.0.
One or Maximo Asset Management instances installed to the current WebSphere instance. All Maximo instances on the server must be at version 18.104.22.168 or later, or will be updated right after migrating profiles from WAS 8.5.5 to WAS 9.0.0.
Configuration Migration Tool - what is it? It is one of several WebSphere wizards. It uses a graphical interface to generate and execute WebSphere administration commands that perform complex operations on WebSphere Application Server.
Why use the tool? Because WebSphere Application Server 8.5.5 cannot be upgraded to version WAS 9.0.0 in the traditional sense. All profiles, including servers and applications, must be recreated and migrated from WAS 8.5.5 by the Migration Tool. The goal of migration is to reconstruct your current profiles in a new WAS 9.0.0 environment.
1. Create Deployment manager (Dmgr) profile
This new Deployment manager will execute all of the commands for Migration Tool.
Launch the WebSphere 9 Profile Management Tool by going to the start screen and clicking on IBM WebSphere Application Server 9.0 > Profile Management Tool.
Select Custom Profile and click Next.
Select Advanced profile creation and click Next.
Enter a new Profile name. It should not be the same as existing WAS 8.5.5 profile. In this example, I named it ctgDmgr02. I also changed the profile directory to match it. Click Next.
Enter a new Node name. It should not be the same as an existing WAS 8.5.5 Node. In this example, I named it ctgNode02.
Check that Host name is correct and click Next.
5. This node will not be federated, because this profile is being used to migratectgNode01 from WAS 8.5.5. So, select the check box next to Federate this node later. [We will be deleting ctgNode02 when we delete the ctgDMgr02 profile later on.]
Accept the defaults (change the password if you wish, but this profile will be deleted), and click Next
Once it has completed, uncheck Launch the First steps console. Close the profile Management Tool window, and close WebSphere Customization Toolbox 9.0.
2. Migrate WAS 8.5.5 Deployment manager (Dmgr01) profile
Shut down the IBM HTTP Server V8.5, IBM WebSphere Application Server V8.5 - ctgCellManager01 and IBM WebSphere Application Server V8.5 - ctgNode01 services, and change their startup Type to Manual. Then, restart the server.
Once you are at the back at the desktop, even though you will be given a chance to back up your profiles in the Migration Tool, back them up now.
Start an administrative command prompt and navigate to the new Deployment Manager profile (default C:\Program Files\ibm\WebSphere\AppServer\profiles\ctgDmgr02\bin\).
Run backupConfig.bat to back up the Version 9.0 deployment manager configuration.
Once completed, navigate to the existing WebSphere 8.5.5 Node Agent directory (default C:\Program Files (x86)\ibm\WebSphere\AppServer\profiles\ctgAppSrv01\bin\).
Run backupConfig.bat to back up the Version 8.5.5 node configuration. If you have more than one or two Maximo servers, this may take some time.
Configuration Migration Tool
On the Migration Sources tab, click New....
5. The Tool will search for installed versions of WAS. Select existing installations.
Here, there is just one eligible version. Select it and click Next.
Source Profile. Here we will be migrating two profiles. Start with ctgDmgr01. Since we backed up configuration before, there is no need to back it up again. If you do need to keep both servers running, check Clone migration (which is not covered in this blog entry).
Enter the WebSphere username (wasadmin default) and password and click Next.
Deployment Manager Disablement. Keep "Disable the source deployment manager after migration" checked, unless both WAS environments need to run on this server. Click Next.
Profile Migration Output. When you accept the defaults note that the new WAS 9 Deployment Manager will have the same name as the WAS 8.0 Dmgr. The new Deployment Manager profile we created earlier is required to run the Migration Tool, but is not used in the final product.
Keep "Migrate to a New Profile" selected, and click Next.
You can migrate to an existing profile but it must have been created earlier. Remember that when we created ctgDmgr02 we did not federate it (pair it with a node).
Profile Creation Parameters. You can give it any name you want. I decided to give it the same name as is used in OOB Maximo. This is okay because the profile name is unique to the set of product binaries (WAS 9.0.0) where it is created. The other ctgDMgr01 profile is unique to WAS 8.5.5.
Check that the Host name is correct, and click Next.
Application Migration. Accept the default values. The application installed is Deployment Manager, not MXServer. MXServer will be migrated later, in the second run of Configuration Migration Tool.
Port value. Since we will be shutting down WebSphere 8.5.5, you can use the port values assigned to the source profile (Deployment Manager). If you were to keep the older WAS version running, there is an option to increment the port numbers by one.
Additional Migration Options.
Migration Summary. Click Migrate... and watch it go.
Migrating Deployment Manager does not take that long to complete. When it completes, you will see a full listing of the output from the migration tool.
You don't see anything in the Target Profile column because none of the values have changed.
Migrating the Node
Migrating the Node and nodeagent (also known as ctgAppSrv1), which includes the Maximo application server and the webserver1 definition, step by step.
From a command prompt, start Deployment Manager. The new Dmgr 01 profile is located (using default values) in C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin
Type in startmanager and press Enter.
Launch the Configuration Migration Tool by going to the start screen and clicking on IBM WebSphere Application Server 9.0 > Configuration Migration Tool.
Click New... on the upper right. There should only be a single existing installation. Make sure it is selected, and click Next.
From the Source profile menu, select your application Server profile (ctgAppSrv01 by default).
Check the box next to create a backup of the source profile as part of this Migration. Click Next.
Note the warning. Since the associated Deployment Manager (the migrated Dmgr01) is the same release level, this is not a problem.
Deployment Manager Verification. Enter the Administrative user name (wasadmin by default) and password. Test the connection first.
On the Profile Migration Output screen, check over the provided values. It should not be necessary to change them.
On the Target Profile screen, accept the default, to migrate to a new profile.
On the Profile Creation Parameters screen, if you want to change the Profile name from appSrv01 to something else (ctgAppSrv01, for example), change it here.
Port Value. If you will be deactivating WebSphere 8.5.5, as I will be, use the port values assigned to the source profile.
Additional Migration Options. Out of the box Maximo does not use WebSphere database connections to connect to Maximo. It's not running, either.
In this example, the Migration Tool migrated the ctgAppSrv01 profile, which contains the nodeagent, webserver1, the RMIRegistry, and four Maximo servers. Click Next.
Once it has completed, click Exit.
Whew! That was a lot. But we have some cleanup work to do.
Next up: Post-migration tasks!
Modified 21 May 2019 (formatting)