IBM Support

ITM Agent Insights: ITM Application Support Installer (ITMASI) does not update "TEPB" / "tpw" application support

Technical Blog Post


Abstract

ITM Agent Insights: ITM Application Support Installer (ITMASI) does not update "TEPB" / "tpw" application support

Body

ITM / ITCAM agents ship "provisional fixes" and "interim fixes" as a "patch" install that does not contain full Common Installer components.

If the "patch" maintenance package requires application support updates, the installation instructions in the README may provide details on using ITM Application Support Installer (ITMASI) to update the application support on the ITM infrastructure.

 

ITMASI can be used to update TEMS / TEPS / TEP Desktop application support definitions, but will NOT update TEP Browser application support.

 

The instructions for launching ITMASI in the README are confusing when it indicates that the ITM Application Support Installer (itmasi) needs the JAVAHOME specified as the fully qualified directory to the "bin" directory under the Java install.  Specifying the full path to the "bin" directory will result in an error:

 

C:\ITM_extract\7.1.0-TIV-ITM_DB2-IF0005\CD-ROM>itmasi.bat -h C:\IBM\ITM -j C:\ITM_images\recreate\43160\JavaDownloads\Java1.6-32bit\install\bin

JAVAHOME is not a valid path to C:\ITM_images\recreate\43160\JavaDownloads\Java1.6-32bit\install\bin\bin\java.exe, the installation has been aborted...

 

Notice in the above that the error message indicating the installation aborted that there are two "bin" directories in the path. 

The command syntax must specify the fully qualified path to the directory that contains the "bin" subdirectory, not to the "bin" directory itself.

 

C:\ITM_extract\7.1.0-TIV-ITM_DB2-IF0005\CD-ROM>itmasi.bat -h C:\IBM\ITM -j C:\ITM_images\recreate\43160\JavaDownloads\Java1.6-32bit\install
Are you sure you want to install the patch using JAVAHOME=C:\ITM_images\recreate\43160\JavaDownloads\Java1.6-32bit\install, enter (y/n):y
Executing: C:\ITM_images\recreate\43160\JavaDownloads\Java1.6-32bit\install\bin\java.exe -jar setup.jar

 

image

image

image

 

Notice that the ITMASI GUI only allows selections for TEMS / TEPS / TEPD application support install.

 

 

It is a permanent restriction of ITMASI that it will NOT update TEPB / tpw application support.

 

This limitation was previously documented in DCF technote:

DCF 1665375 - IBM Installing interim fix does not upgrade the version of TEPB application support

 

After applying a provisional or interim fix, customers may be prompted with a warning message when using the TEP Browser client indicating that application support is out of synch, or simply be concerned that "kincinfo -d" or "cinfo -i" didn't update all the application support items, leaving TEPB / tws component downlevel.

 

Example:

"UD","TEMS App Support/Monitoring Server for DB2 Support","WINNT","071000050","62221","KUDWICMS.ver"     (on UNIX / Linux this would be "tms")
"UD","TEPS App Support/Portal Server for DB2 Support","WINNT","071000050","62221","KUDWICNS.ver"             (on UNIX / Linux this would be "tps")
"UD","TEPB App Support/Portal Browser Client for DB2 Support","WINNT","071000000","31021","KUDWIXEB.ver"  (on UNIX / Linux this would be "tpw")
"UD","TEPD App Support/Portal Desktop Client for DB2 Support","WINNT","071000050","62221","KUDWIXEW.ver" (on UNIX / Linux this would be "tpd")

 

The TEPB / tpw package consists of files to support on-line help, and resources like fly-overs for attributes, and "expert advice" for situation definitions.  These resources are installed on the TEPS.
The TEPB / tpw version not being updated is expected, and does not impact any function. Both the TEP Desktop and the TEP Browser clients will still function normally for the agents updated with an interim / provisional fix.

 

The only way to update the TEPB / tpw package for application support for a "patch" install is to rely on Self Describing Agent (SDA) functionality.

 

ITM introduced SDA function starting at 6.23 release.

The ITM / ITCAM provisional / interim fix image must be built to include the application support files in the agent image so they can be sent to the ITM infrastructure when connecting.

<platform>/<product code>/support/K<pc>MSMAN.txt
<platform>/<product code>/support/K<pc>JSTMS.jar
<platform>/<product code>/support/K<pc>JSTPS.jar
<platform>/<product code>/support/K<pc>JSTPW.jar

 

In addition, SDA must be enabled on the systems where ITM components are installed.  By default SDA is disabled on the HUB TEMS, so it may require setting appropriate SDA environment variables on the ITM component systems.

 

TEMS:
<candlehome>\CMS\KBBENV  or ms.ini
KMS_SDA=Y

 

 

TEPS:
KFWENV or cq.ini
TEPS_SDA=Y

 

Agent:
K<pc>ENV or <pc>.ini
TEMA_SDA=Y

 

In addition, it may be necessary to run various "tacmd" commands to allow SDA for the specific type of agent being installed:

 

tacmd listSdaInstallOptions
tacmd listSdaOptions
tacmd deletesdainstalloptions -all
tacmd editsdainstalloptions -t DEFAULT -i ON

 

If a "patch" image is SDA capable, after installing the "patch" on the agent, you can confirm if SDA is sending the application support .jar files to the ITM infrastructure by reviewing the .LG0 file.

 

 

 

KRALOG000 New log file created.                                        CTIRA_create_probe_log()

KRAREG000 Connecting to CMS HUB_NC9053114043                            IRA_Manager
KRAA0001  Self-Describing Agent Installation started for PRODUCT "UD", with TEMS "HUB_NC9053114043", VERSION_INFO "product_vrmf=07100005;tms_package_vrmf=07100005;tps_package_vrmf=07100005 tpw_package_vrmf=07100005;".        SDA_Install
...
KT1V3021I Operation getfile started for UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDMSMAN.txt    kt1server
KT1V3022I Operation getfile executed by UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDMSMAN.txt completed with SUCCESS    kt1server
KT1V3021I Operation getfile started for UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDJSTMS.jar        kt1server
KT1V3022I Operation getfile executed by UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDJSTMS.jar completed with SUCCESS    kt1server
KT1V3021I Operation getfile started for UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDJSTPS.jar        kt1server
KT1V3022I Operation getfile executed by UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDJSTPS.jar completed with SUCCESS    kt1server
KT1V3021I Operation getfile started for UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDJSTPW.jar    kt1server
KT1V3022I Operation getfile executed by UNKNOWN on /opt/IBM/ITM-79394/aix526/ud/support/KUDJSTPW.jar completed with SUCCESS    kt1server

 

The K<pc>JSTPW.jar will update the TEPB / tws application support.


Reviewing the "kincinfo -d" on the ITM infrastructure shows the "TEBP" version updated:
"UD","TEMS App Support/Monitoring Server for DB2 Support","WINNT","071000050","62231","KUDWICMS.ver"
"UD","TEPS App Support/Portal Server for DB2 Support","WINNT","071000050","62221","KUDWICNS.ver"
"UD","TEPB App Support/Portal Browser Client for DB2 Support","WINNT","071000050","62231","KUDWIXEB.ver"
"UD","TEPD App Support/Portal Desktop Client for DB2 Support","WINNT","071000050","62221","KUDWIXEW.ver"
 

Keywords:
drd401709
5608A41CI
itmasi.bat
itmasi.sh

 

Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM Agent Insights: Introduction.

 

Tutorials Point

Subscribe and follow us for all the latest information directly on your social feeds:

 

imageimageimage

Check out all our other posts and updates:

Academy Blogs
Academy Videos
Academy Google+
Academy Twitter

image

 

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

UID

ibm11082979