IBM Support

Using the WebSphere 9 Migration Tool with Maximo 7.6, part 2

Technical Blog Post


Abstract

Using the WebSphere 9 Migration Tool with Maximo 7.6, part 2

Body

Continuing from Using the WebSphere 9 Migration Tool with Maximo 7.6, part 1.

Post-Migration Tasks

For the following post, the original (WAS 8.5.5) installation is at C:\IBM\WebSphere. The new (WAS 9.0.0) installation is at C:\Program Files\WebSphere.

At this point in the migration, the profiles are:

WebSphere 8.5.5.11: Deployment manager (dmgr): C:\IBM\WebSphere\AppServer\profiles\ctgDmgr01 and nodeagent: C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 (nodeagent, MXServer, webserver1).

WebSphere 9.0.0.6: Deployment manager (dmgr): C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01 (migrated), C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr02 (deployment manager used for migration) and nodeagent: C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 (nodeagent, MXServer, webserver1). ctgDmgr01 and ctgAppSrv01 are both migrated from (recreated) WAS 8.5.5.

 

First Things First: Start the Cell Manager and the Node Agent

Start an administrative command prompt at <APPSRV9>\profiles\ctgDmgr01\bin
> startManager.bat

C:\Program Files\IBM\WebSphere\AppServer\\profiles\ctgDmgr01\bin>startManager.bat
ADMU0116I: Tool information is being logged in file <APPSRV9>\profiles\ctgDmgr01\logs\dmgr\startServer.log
ADMU0128I: Starting tool with the ctgDmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 4388

Change directory to <APPSRV9>\profiles\ctgDmgr01\bin : cd ..\..\ctgAppSrv01\bin

> startNode.bat

C:\Program Files\IBM\WebSphere\AppServer\\profiles\ctgAppSrv01\bin>startNode.bat
ADMU0116I: Tool information is being logged in file <APPSRV9>\profiles\ctgAppSrv01\logs\nodeagent\startServer.log
ADMU0128I: Starting tool with the ctgAppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 1928

 

1. Remove the WebSphere 8.5 Plug-In Configuration and Web server

From the Start Page, under IBM WebSphere, launch WebSphere Plug-In Configuration Toolbox.

WAS Plug-In Configuration Toolbox

In the Web Server Plug-in Configurations panel, select the webserver1 Web Server Definition.

Click Delete, and confirm the deletion. In the Web Server Plug-in Runtime Locations section, select webserver1.

Click Remove, and confirm the removal.

Exit WebSphere Customization Toolbox V8.5.

Log into the WebSphere console.

Go to Server Types > Web servers.

New webserver1

Tick the button next to webserver1, and click Delete.

Log out of the WebSphere console.

 

2. Configure WebSphere 9 Web Server Plug-In

Go the Start page. Under WebSphere Customization Toolbox V9.0, click on WebSphere Plug-In Configuration.

Web Server Plug-In Configuration

Click on Add... and enter your environment information. The default installation location for the Plugins directory is at C:\Program Files\IBM\WebSphere\Plugins.

Web Server Plug-In Location

Click Finish.

On the Web Server Plug-In Configurations tab, click on Create...

Web Server Plug-In Configurations

Click Create...

Web Server Selection

Click Next >.

Note: Be careful on these pages. As with the Maximo Configuration Tool, WebSphere Configuration Toolbox (WCT) does not pull values from IBM Installation Manager's product installation database. The populated values are suggested only.

Web Server Configuration File Selection

Confirm that this is the correct location and click Next >.

Setup IBM HTTP Server Administration Server

Uncheck Setup IBM HTTP Server Administration Server and click Next >.

In this case, because the web server instance will be in the same cell and node as the web application server, it is not necessary to set up IBM HTTP Server Administration Server or create a Windows service.

Web Server Definition Name

Enter webserver1 and click Next >.

Configuration Scenario Selection

Select Local and enter the location of the WAS 9 installation directory. Click Next >.

WebSphere Application Server Profile Selection

Select ctgAppSrv01 and click Next >.

Plug-in Configuration Result

Click Finish.

 

4. Recreate webserver1 and Generate Plug-In

Log into the WebSphere console. Go to Server Types > Web servers.

Create a new Web server. Out-of-the-box Maximo are Node ctgNode01, Name webserver1, Type IBM HTTP Server.

New web server Step 1

Click Next.

new wev server Step 2

Click Next.

create web server Step 3

Confirm that the file locations are correct and click Next.

Create new web server Step 4

Click Finish.

Web server created

Click on Save directly to the master configuration.

 

Generate Plug-In

Click on webserver1.

generate plug-in

Under Additional Properties, click on Plug-in properties.

plug-in properties

Confirm locations are correct. Click OK. Save changes to the Master Configuration.

Select webserver1.

Click on Start.

After started, select webserver1.

Click on Generate Plug-in.

webserver1 created

Log out of WebSphere console and close browser.

 

3. Remove WebSphere Application Server 8.5.5

a. Using wasservicehelper.bat in old installation location, remove both WAS 855 Windows services using wasservicehelper.bat

C:\IBM\WebSphere\AppServer\bin>wasservicehelper.bat

-------------------
Menu Options :
-------------------

1  Add new or update existing WebSphere service (minimum parameters required)
2  Add new or update existing WebSphere service (all parameters)
3  Remove WebSphere service
4  Status of WebSphere service
5  Tracing WASServices

Select number next to the options
(default 1)[q to Quit]:3

-------------------
Remove Service:
-------------------
1 IBMWAS85Service - ctgCellManager01
2 IBMWAS85Service - ctgNode01

Select the number next to the service to remove:1

You selected ctgCellManager01 to be deleted.
cmd : WASService.exe -remove "ctgCellManager01"

Execute command now? [Y/N][q to Quit]:y


Success.
 WASServiceCmd.rep contains additional details.

Remove Another? (default Y)[Y/N][q to Quit]:y
1 IBMWAS85Service - ctgNode01

Select the number next to the service to remove:1

You selected ctgNode01 to be deleted.
cmd : WASService.exe -remove "ctgNode01"

Execute command now? [Y/N][q to Quit]:y


Success.
 WASServiceCmd.rep contains additional details.

Remove Another? (default Y)[Y/N][q to Quit]:q

-------------------
Menu Options :
-------------------

1  Add new or update existing WebSphere service (minimum parameters required)
2  Add new or update existing WebSphere service (all parameters)
3  Remove WebSphere service
4  Status of WebSphere service
5  Tracing WASServices

Select number next to the options
(default 1)[q to Quit]:q

C:\IBM\WebSphere\AppServer\bin>

Using the shortcut for WebSphere [8.5] Plug-In Configuration Toolbox, remove WebSphere Plug-In Runtime Locations. It will also delete the Plug-In configuration.
Exit WebSphere 8.5 Customization Toolbox.

Launch IBM Installation Manager

IBM installation manager

Uninstall WebSphere Customization Toolbox V8.5, Web Server Plug-Ins for IBM WebSphere Application Server V8.5, IBM WebSphere Application Server 8.5, and IBM HTTP Server V8.5.

image

Make sure that all WebSphere IFPIs and IBM WebSphere SDK Java Technology Edition versions 6.x and 7.x are selected for uninstallation.

Manually delete the original WebSphere and HTTPServer folders.

 

5. Create new Windows services for dmgr and nodeagent

Restart the server.

Start a command prompt. Navigate to AppServer\bin directory.

Run wasservicehelper.bat and create services for ctgNode01 (ctgAppSrv01) and ctgCellManager01 (ctgDmgr01)

 

6. Remove the ctgDmgr02 profile

Since migration is complete, the ctgDmgr02 profile is no longer necessary.

Start a command prompt. Navigate to AppServer\bin directory.

C:\Program Files\IBM\WebSphere\AppServer\bin>manageprofiles.bat -delete -profileName ctgDmgr02
INSTCONFSUCCESS: Success: The profile no longer exists.

Manually delete the <APPSRV9>\profiles\ctgDmgr02 directory.


NOTE: If IBM HTTP Server V9.0 service does not startup, try starting it up manually
C:\Program Files\IBM\HTTPServer\bin>httpd -k start
AH00526: Syntax error on line 309 of C:/Program Files/IBM/HTTPServer/conf/httpd.conf: Multiple <DirectoryMatch> arguments not (yet) supported.

If HTTPServer does not start up, edit httpd.conf, change
C:\Program Files\
to
C:\Progra~1\

and save the file, then start up the Windows service again.

 

Let me know how it goes with these steps, and as always post questions and corrections.

 

Updated 30 Jan 2018
Modified 21 May 2019 (formatting)

Modified 29 May 2019 (path)

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11111461