IBM Support

All in a week's work: upgrades, updates, moves and installs

Technical Blog Post


All in a week's work: upgrades, updates, moves and installs


I've been doing a few upgrades (major and minor) this week. See below for my current VM setup. The one with nothing extra on it is serving as an Active Directory server only (and contains all maxdemo users).


I upgraded a maxdemo Maximo to This instance has Scheduler and Calibration enabled, and I installed the Maximo 7.5 versions to maximo 7.6, since the 7.6 versions of those products are not yet available were not available at the time I installed it (Calibration 7.6 was released last Friday, and Fix Pack updates Scheduler to

I upgraded nc20019's Windows Server 2012 to Windows Server 2012 R2.



My move-and-upgrade today was updating my SCCD (now IBM Control Desk) from to, prompted by a PMR concerning problems applying Fix Pack

In the process, I moved the application server from an overloaded one to an underutilized one. The old one had ten (now nine) JVMs. The VM has "only" 16 GB RAM, which means I can run two or three at a time. Running the cluster on it takes everything. All of my JVMs now have 16 GB, so I can spread out the JVMs.

Adventures upgrading SCCD to - time to hunt down the cause of the CTGIN2076E error.


In the CtgTrace00 log the error is

SEVERE: CTGIN0024E: An unexpected exception was encountered during processing of a process solution installation service request. The exception is Remote system cannot be reached using Supported RXA Protocols., "CTGIN2076E - WASThinClient exception upgrading to Smart Cloud Control Desk 7.5.1"


I added add WAS.ThinClientLocalKeystore=C:\\IBM\\SMP/wasclient/etc/trust.p12 to That fixed the CTGIN0024E error, but I was sill getting the following error


CTGIN2076E: Exception Running WASThinClient method for task runConfigurationStep.




Since I am using a different WAS server than before, I needed to copy the trust.p12 file from the Deployment Manager of the new server to the c:\ibm\smp\wasclient\etc directory of the administrative system, overwriting the existing file. I also had to make sure the wasadmin password (WAS.AdminPassword) was correct in

Finally, I had to modify C:\ibm\SMP\wasclient\ThinWsadmin.bat to point to the "new" WAS server and the C:\ibm\SMP\wasclient\properties\soap.client.props file and add the wasadmin username and password to the parameters.


Applied a Fix Pack to another server. It looks like I applied it months ago but never updated the database or build and deployed the ear files. Ah, I see now. I started the Fix Pack install on December 8... four days before Maximo 7.6 was released. I guess I was busy.


Installed WebSphere and Maximo in preparation for installation Maximo Anywhere and Worklight server.

Also, finally deployed the EAR files for the SCCD server I upraded on Tuesday. In so doing, I discovered that the webserver on that instance was still pointing to the old directory structure, which I had deleted. I created a new webserver and mapped the enterprise applications to it.

Trying to get my cluster on another server to work on port 80.


Maximo cluster is still not available on port 80. I got it to work by changing the Virtual Host entry */80 to <FQDN host name>/80.

Maximo Fix Pack came out today! Among other things, it offers the new feature that you will be able to reduce downtime when running updatedb. For more details, see

In the new release department, Calibration 7.6 and Life Sciences 7.6 are now available, as is Maximo Anywhere A change in the third number of a version indicates a new full installer package (Passport Advantage), not a fix pack installer (Fix Central). I will be using that when I install Anywhere to my brand new Maximo


So, following, I installed the fix pack but did not use the config tool to update the database and rebuild and redeploy the EAR files.

Everything's on the same server, so I don't expect the updatedb time to be superlong, but let me just go ahead. I do have anti-virus software running on this server.

  1. Run updatedblitepreprocessor.bat - 1 minute
  2. Build maximo.ear using buildmaximoearwas8.cmd - 15 minutes
  3. Build maximoiehs.ear using buildmxiehsear.cmd - 2 minutes
  4. Stop MXServer - 15 minutes
  5. Run updatedblite.bat - 2 minutes
  6. Uninstall MAXIMO and MXIEHS enterprise applications - 2 minutes
  7. Deploy maximo.ear - 12 minutes
  8. Deploy maximoehs.ear - 4 minutes
  9. Clear cache files - 5 minutes
  10. Start MXServer - 5 minutes

Total time: 62 minutes. Total downtime: 45 minutes. Time saved: 17 minutes. Put another way, using UpdateDB Lite pre-processor reduced downtime by 27%.

After a week, this is what my VMs look like:



Next time - installing Maximo 7.6 on Red Hat Enterprise Linux server 6.6.


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