ITM Agent Insights: ITM Application Support Installer (ITMASI) does not update "TEPB" / "tpw" application support
DougDoering 120000E6GG Comment (1) Visits (7679)
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:
JAVAHOME is not a valid path to C:\I
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.
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.
"UD","TEMS App Support/Monitoring Server for DB2 Supp
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 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.
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.
In addition, it may be necessary to run various "tacmd" commands to allow SDA for the specific type of agent being installed:
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. CTI
KRAREG000 Connecting to CMS HUB_NC9053114043 IRA_Manager
The K<pc>JSTPW.jar will update the TEPB / tws application support.
Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM
Subscribe and follow us for all the latest information directly on your social feeds: