Sometimes I Like To Pretend: Install Maximo 7.5.0.5 fixpack on 7.5.0.4

Goal:
Install Fixpack 7.5.0.5 on Maximo 7.5.0.4.

Example:
In order to use the Maximo Scheduler 7.5.2 we need to install Fixpack 7.5.0.5. What are the best practices for doing this.

Resources:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Maximo%20Scheduler%207.5.2%20System%20Requirements

How to:

Some information before we start.

The installer will look at the following file for the information needed to update the system;

D:\ibm\SMP\etc\install.properties

If, for example, the servername/IP has changed since the last update or installation you need to update the install.properies accordingly.

In the screenshot below I pointed out the WebServerHostName, on my VM i used a fixed IP. On a productionserver you would generally have a domain name here.

For this upgrade nothing is changed, so we leave the install.properties as it is.

Backup the Deployment Engine

Make a copy of the ‘D:\ibm\SMP\CTG_DE’ folder to another location. This folder contains the Deployment Engine database. If the installation goes wrong, we can use this backup to restore.

Stop MXServer

We use Websphere in this example.

In the Integrated Solutions Console go to Servers -> Server Types -> Websphere application servers. Select the MXServer and stop the MXServer.

Run the installer

We will now start the installer. Right click on the install.exe (or the install_win64.exe if you upgrade a 64 bit installation) and run the .exe as administrator.

Wait until the installation is decompressed and ready to be installed;

Choose the language and click [OK]

Click [Next]

Check if the installation location is correct and click [Next]

Now we see a summary of the currently installed packages, review these.

Click [Next]

The installer will perform the pre-installation processing. Wait until these are done.

When done, the installer quits on me. It closes without any warning…

Troubleshooting time...

First we look in the directory D:\ibm\SMP\logs and check the logs

The CTGError00.log states the following;

3-okt-2013 15:24:08 SEVERE: NOTE No JDBC Connection to DB established.
3-okt-2013 15:24:08 SEVERE: NOTE Creating with

We go to Websphere to test the JDBC connection.

In the menu on the left go to: Resources -> JDBC -> Data Sources. Select the resource en click the [Test connection] button.

I got a message about the Node not being in Sync. When trying to Sync the node an error occurs.

So i went to a console, and got to D:\ibm\Websphere\AppSever\bin and ran the command ‘stopNode.bat’

Run the command ‘startNode.bat’

Now, go back to Websphere and test the JDBC connection again. This time it is successful.

We run the taskrunner to see if there is any unfinished business set during the installation that stopped on us...

Try the installation again.

We repeat the steps we did until the pre-installation processing.

Same error…

I went to check to log on a different location: C:\Documents and Settings\Administrator

There the CTGError00.log show more information (because I ran it as Administrator?)

FINE: ENTERjava.lang.IllegalArgumentException: Database.SQL.ServerHostName

at com.ibm.tivoli.ccmdb.install.common.CmnAssert.badAssertion(CmnAssert.java:196)

at com.ibm.tivoli.ccmdb.install.common.CmnAssert.notNull(CmnAssert.java:114)

at com.ibm.tivoli.ccmdb.install.common.config.database.SQLServer.updateObjectProperties(SQLServer.java:180)

at com.ibm.tivoli.ccmdb.install.common.config.database.SQLServer.<init>(SQLServer.java:334)

at com.ibm.tivoli.ccmdb.install.common.config.database.SQLServer.getInstance(SQLServer.java:148)

at com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndSetInstallType.updateDatabaseProperties(FndSetInstallType.java:1304)

at com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndSetInstallType.handleInstall(FndSetInstallType.java:539)

at com.ibm.tivoli.ccmdb.install.foundation.ccmdb.AFndCustomCodeAction.install(AFndCustomCodeAction.java:127)

at com.zerog.ia.installer.actions.CustomAction.installSelf(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.a(DashoA10*..)

at com.zerog.ia.installer.AAMgr.a(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.e(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.n(DashoA10*..)

at com.zerog.ia.installer.AAMgr.a(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.e(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.n(DashoA10*..)

at com.zerog.ia.installer.AAMgr.a(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.e(DashoA10*..)

at com.zerog.ia.installer.AAMgrBase.n(DashoA10*..)

at com.zerog.ia.installer.AAMgr.g(DashoA10*..)

at ZeroGs8.goNext(DashoA10*..)

at com.ibm.tivoli.ccmdb.install.ps.ia.panel.PsiaPidProgressPanel.drivePreInstallDirector(PsiaPidProgressPanel.java:482)

at com.ibm.tivoli.ccmdb.install.ps.ia.panel.PsiaPidProgressPanel.run(PsiaPidProgressPanel.java:316)

at java.lang.Thread.run(Thread.java:736)

Database.SQL.ServerHostName

Throwable occurred: java.lang.IllegalArgumentException: Database.SQL.ServerHostName