Using buildtpmpatch script during RP01, IF01, IF02, IF03

Technote (troubleshooting)


Problem(Abstract)

The use of buildtpmpatch script - as indicated in our TPM 7202-RP01, TPM 721-IFIX1, TPM 721-IFIX2, and TPM 721-IFIX3 readme postinstall section for servers which are running MBS (Maximo Base Services) 7118 in an 'upgraded' environment - can cause files to be downgraded.

Symptom

BMXAA5476E BIRT Report Engine not initialized properly for this operation to work.

db2jcc drivers which had previously been upgraded are now at a lower level.
TPM engines mxe.name used to be MXServerlwi and now it is MXServer.



Diagnosing the problem

1. The TPM maximo.properties files can get overwritten with the default "source" maximo.properties file taken from SMP Maximo files. The TPM maximo.properties files are located at 2 locations and should be identical:

$TIO_HOME/eclipse/plugins/tpm_pmp/properties/maximo.properties

$TIO_HOME/lwi/runtime/tpm/eclipse/plugins/tpm_pmp/properties/maximo.properties

The default "source" version of the maximo.properties file is missing 3 entries:
mxe.crontask.donotrun=ALL
mxe.report.birt.disablequeuemanager=1
mxe.rmi.enabled=0

Also the mxe.name should indicate the MXServerlwi as this is the standard configuration for the TPM engines.


2. If you have upgraded db2jcc drivers TPM and WAS locations but not under the Maximo SMP location, then the original default db2jcc drivers taken from Maximo will overwrite the TPM db2jcc drivers. Please check all 3 locations to ensure you have consistent db2jcc driver levels in place.


Resolving the problem

If you have already completed your TPM 7202-RP01, TPM 721-IFIX1, TPM 721-IFIX2, and TPM 721-IFIX3 postinstall steps including the buildtpmpatch script, then the best solution is to verify the above 2 points and determine if any corrective actions need to be taken.

If you have not yet completed your TPM 7202-RP01, TPM 721-IFIX1, TPM 721-IFIX2, and TPM 721-IFIX3 postinstall steps including the buildtpmpatch script, then you can replace the buildtpmpatch.xml to correct the problem. To use the new file you must place it under /opt/IBM/SMP/maximo/deployment, prior to running the postinstall steps.

buildtpmpatch.xmlbuildtpmpatch.xml

The new buildtpmpatch.xml file will:
- exclude the db2jcc, db2jcc_licence_cu, j2ee jar files from the tpm_tpae_upgrade_patch.zip built.
- remove the maximo.properties and webclient.properties files copy since those could have been user customized under TIO_HOME.


Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli Service Automation Manager Windows, AIX, Linux 7.2.2.2, 7.2.3, 7.2.4
Systems and Asset Management IBM Service Delivery Manager Not Applicable AIX, Linux 7.2.2, 7.2.4

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Provisioning Manager

Software version:

7.2.0.2, 7.2.1

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

1619690

Modified date:

2013-11-01

Translate my page

Machine Translation

Content navigation