Just a quick plug before we head off into the land of screen shots.
I attended a demo that showed off new user interface features coming in the next version of Maximo. Of great interest was the new interface, or skin. It's much cleaner than before, with larger type and just the right amount of white space. They've also hidden some elements that don't need always to be seen. (If you're worried about the new look causing problems for users used to the old look and feel, don't worry - everything is turned off when you upgrade from a previous version of Maximo, and can be introduced when it seems appropriate). If you are interested, go here to see a replay of the UI demo. It's about an hour long, and full of useful information (and good questions and answers, too).
Back to screen shots.
Migrating the Node
Migrating the Node and nodeagent (also known as ctgAppSrv1), which includes the Maximo application server and the webserver definition, step by step. As with the last blog post, I am doing this with out of the box Maximo 126.96.36.199.
1. From a command prompt, start Deployment Manager.
The new Dmgr is located in C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin
Enter startmanager and press return
2. From the Start Menu, launch the Configuration Migration Tool
3. Click New... on the upper right.
4. There should only be a single existing installation. Make sure it is selected, and click Next.
5. From the Source profile menu, select your application Server profile (ctgAppSrv01 by default). Check the box next toCreate a backup of the source profile as part of this Migration. Click Next.
6. Enter the Administrative user name (wasadmin by default) and password. Test the connection first.
7. On the Profile Migration Output screen, accept the provided values and click Next.
8. On the Target Profile screen, accept the default and click Next.
9. 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 and click next.
10. Port value. If you will be deactivatingWebSphere 7.0, use the port values assigned to the source profile. Click Next.
11. Click Migrate
12. Once it has completed, click exit.
Deploying the Maximo EAR
1. Deploying the Maximo ear. We can never emphasize enough how important it is to follow the lengthy steps we provide for deploying the maximo.ear. If you are WebSphere-savvy enough to use scripting to automate the process, we encourage you to continue to use it, as the scripting has not changed between WAS 7 and WAS 8.5 (aside from adding more options).
The migration tool has also migrated the MXServer application and the maximo.ear (MAXIMO) and maxiehs.ear (MXIEHS) applications.
Since the WebSphere Windows services have not yet been created, issue process commands stopnode and stopserver (from C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin) and stopmanager (from C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin).
1a. Delete cached files from temp, tranlog, wstemp and, optionally, logs directories:
(where the WebSphere location is c:\program files (x86)\ibm\websphere\appserver, the application server profile is called ctgAppSrv01, the node is called ctgNode01, and the Maximo server is called MXServer). *.* means contents of the named directory:
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\temp\ctgNode01\MXServer\*.*
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\tranlog\ctgCell01\ctgNode01\MXServer\*.*
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\wstemp\*.*
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer\*.*
2. Start the WAS processes back up again.
2a. To start Deployment Manager from command prompt
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgDmgr01\bin\startmanager
2b. To start Node Agent from command prompt
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin\startnode
2c. Launch administrative console. The default url is http://localhost:9060/ibm/console
2d. On the left side, expand Servers, then Server Types. Click on WebSphere application servers. Stop MXServer, if necessary.
2e. On the left side, expand Applications, then Application Types. Click on WebSphere enterprise applications. Remove the MAXIMO application. You do not need to remove the MXIEHS application.
3. Building the maximo ear for WebSphere 8 requires running a different buildear command file.
3a. Start a command line session at c:\ibm\smp\maximo\deployment.
3b. Run buildmaximoearwas8.cmd
4. Redeploy the Maximo application. Log back into the WebSphere console.
4a. On the left side, expand Applications, then Application Types. Click on WebSphere enterprise applications. Navigate to the click on the Add... button on the right side of the console.
4b. Click Install. Select the MAXIMO.ear file you just built.
4c. Click next, then next again.
4d. At Map modules to server, select both the webserver and the MXServer. Use CTRL to select both and map all modules. Click next.
4e. At Map virtual hosts for Web modules, select your host (in the case of out of the box Maximo, maximo_host. Click next.
4f. Click Finish.
Start MXServer, and log into Maximo.
Last step: how to create the Windows services for your new WAS 8.5.5 installation.