This post will cover some of the same ground as a series I published last year. Those postings went into depth on setting up a new WebSphere Application server, database server, and setting up application server security with LDAP, but didn't go into much depth about doing the WebSphere application server "migration". using the term migration is misleading--I am recreating the Maximo application server on a new server.
I decided recently that I need to re-image the Windows server that hosts four of my Maximo/Control Desk instances with Windows Server 2012. That means I need to move the WebSphere host to another server. Fortunately, I have another server with the capacity to handle 4 JVMs.
I broke it down the process into four sections, with several tasks per section.
Environment information (first server)
The database is on my Oracle server that I created last year.
The administrative workstation is not the server I am reimaging. I will not have to move the SMP directory. I will have modify parameters on its administrative workstation's install.properties to reflect the WAS server switch.
1. WebSphere Application Server on new server
a. Already installed
b. Install latest WAS Fix Packs
2. WAS maintenance: Create new Maximo application server
a. Create new WebSphere Application Server for Maximo; make note of ports for WC_adminhost, WC_adminhost_secure, WC_defaulthost and WC_defaulthost_secure
b. Modify Java Virtual Machine settings to match existing server: Initial heap size, Maximum heap size , and Generic JVM arguments
c. Create new Virtual Host with port 80 and WC_adminhost, WC_adminhost_secure, WC_defaulthost and WC_defaulthost_secure.
d. Modify logging settings on new Maximo applicaton server to increase number and size of SystemOut.log files. This can be found under Troubleshooting > Logs and trace > <servername> > JVM Logs, changing the Maximum Size to 5 and the Maximum Number of Historical Log Files to 24.
e. Save to master configuration.
f. From administrative workstation, deploy maximo.ear
g. Deploy maximoiehs.ear
h. Set security role to user/group mapping on maximo.ear (if necessary)
3. Maximo maintenance
a. Start up new Maximo server
b. Log into Maximo as maxadmin (or equivalent)
c. In System Properties application, update properties to reflect new WebSphere host.
Because changing WAS.WebServerHostName cannot be done as a live refresh, restart the Maximo server after completing these tasks.
4. Administrative Workstation maintenance
a. Update install.properties to reflect new WebSphere host.
* WAS.SOAPConnectorPort (if necessary)
* WAS.RemoteAccessUserName (if necessary)
* WAS.WebServerName (if necessary)
* WAS.AdminUserName (if necessary)
* WAS.NodeName (if necessary)
* WAS.CellName (if necessary)
* WAS.AdminPassword (if necessary)
* WAS.VirtualHost (if necessary)
* WAS.VirtualHostPort (if necessary)
I don't need to rebuild and redeploy the maximo.ear file, because I didn't move the database (hence requiring modifying maximo.properties).