ITM Application support at HUB

Steps

Overview:

Situations along with the matching attribute and catalog file(s) reside on the TEMS.  The step of adding the situations to the TEMS and placing the attribute and catalog files in their proper location is known as seeding.  When this step has not been done or has not worked properly the most common visual errors are situations not displaying in the Situation Editor GUI as well as status codes within the views such as 209, 202, 806, etc.

For UNIX and Linux systems, application support must be manually enabled (this is alsocalled activating application support). The TEMS must be started before applicationsupport can be added. To start a TEMS, use the following command:

• itm_installdir/bin/itmcmd server start tems_name 

After the TEMS is started, you can add application support using the following command:

• itm_installdir/bin/itmcmd support -t tems_name product_code1 product_code2 product code3...

If your UNIX or Linux TEMS has X-Windows configured, you can use the Manage Tivoli Enterprise Monitoring Services application to add application support. To start MTMS on
UNIX or Linux, use these commands:

• itm_installdir/bin/itmcmd/itmcmd manage -h itm_installdir

Restart the TEMS after activating application support.

Locations of CAT and ATR files for the monitoring server:

• .cat     <itm_install_dir>/tables/cicatrsq/RKDSCATL
• .atr     <itm_install_dir>/tables/cicatrsq/ATTRIB

In the next paragraph, two examples explain what the TEP navigator view displays when no IBM ITM application support is installed (Case A) and when the IBM ITM application support is installed on the HUB tems. (Case B)As a example I used the Agentbuilder agent. (K47)

Case A: The K47 agentbuilder agent has been installed and it has started but  no HUB/RTEMS tems IBM ITM application support has installed:

• The RAS1 log of agent show , the connection to the HUB has established.

...,692,"IRA_OutputLogMsg") Connecting to CMS BCKHTEMSN
... ,1087,"ConnectToProxy") Successfully connected to CMS BCKHTEMSN using ip.pipe:#172.17.1.4[1928]

• The MTEM confirm the agent has started by succ
• But the command tacmd listsystems and tep client doesn't show any k47 agent connection

ase B: The K47 agentbuilder agent has been installed and it has started, the IBM ITM application support has installed on the HUB:

• The RAS1 log of agent show , the connection to the HUB has established, The output of the command tacmd listsystems show the agent as online. 

• The command cinfo -t 47confirm the  installation of IBM ITM  TEMS application support