ITM Application Support - Behind the Scenes

Body

There are several parts to applying application support and understanding what is happening in each part will help you determine where the issue is and lead to faster resolution.

TEMS

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.

If the situations are not displaying within the GUI you can run the tacmd listsit or you can run the following SQL using kdstsns:

SELECT SITNAME, SITINFO, LSTDATE,
     SOURCE, TEXT
   FROM O4SRV.TSITDESC;

If you wanted to just check on one situation or commonly named situations, you can further qualify the SQL like this:

SELECT SITNAME, SITINFO, LSTDATE,
     SOURCE, TEXT
   FROM O4SRV.TSITDESC
WHERE SITNAME = "My_Test_Situation";

SELECT SITNAME, SITINFO, LSTDATE,
     SOURCE, TEXT
   FROM O4SRV.TSITDESC
WHERE SITNAME LIKE "My_Test*";

kdstsns can be run interactively or just as one command: 

        kdstsns FILE.SQL *HUB  
        or
        kdstsns   and hit enter

It is located:

        Windows - $CANDLEHOME\cms
        UNIX = $CANDLEHOME/<arch>/ms/bin
       

You need to make sure to set SQLLIB to the location where the SQL you want to run is located:
    
        Windows:   set SQLLIB=c:\ibm\itm\cms
        UNIX:      export SQLLIB=\tmp\sql
       

You can pipe the output to a file which will allow you to easily review the results.

If the situations are not there you should try re-running the TEMS support.  If this fails you can check the logs as well as try to manually run the SQL using kdstsns.  The SQL is located in the SQLLIB directory under the CMS directory.

It is important to seed situations not only on the HUB but also your RTEMS.  This is because some of the historical situaitons do not automatically get distributed.  Also attribute and catalog files must reside on all TEMS.

You can use the self managed workspaces to see if any of the catalog/attribute files are missing or if different versions are present throughout the environment.  If there are different version you want to place the latest version out across your infrastructure.  The files are backward compatible.

TEPS

The TEPS has several application support files for each agent.  There is data which must be imported into the TEPS database and there is the ODI file.

If you are missing workspaces or queries verify the agents SQL files reside in the SQLLIB directory under the TEPS directory.  If they are not present re-install the agents application support.  If they are there try reconfiguring the TEPS.  You can also run SQL against the TEPS database to see if the data is present.

Here is an example of the SQL you can run against a DB2 database:

SELECT * FROM KFWQUERY WHERE APPL='KNT'

This will show you what queries exist for the Windows agent.

You can use the KfwSQLClient executable or run it directly in DB2 where you may need to qualify the table with userid.

If the ODI file is not present you will not see a main navigator item in the situation editor or the query editor.  You can
check for the file in the following location:

Windows:   %CANDLEHOME%\CNPS
UNIX:      $CANDLEHOME/<arch>/cq/data

The naming convention for the file is dockPC where PC is the product code.  So for Windows application support the file would be docknt.

There are also XML files that should be present in the sqllib directory.  These files provide extensions to the agent.  In the UNIX environment there will be matching named files with "processed" added as an extension.  If there is no corresponding "processed" file check the logs for errors.

TEP

If you do not see name resolution for child navigator items or titles on views within a workspace you need to check the
application support for the client.  There should be jar files and a corresponding inf file located in the following directory:
 
 Windows:  $CANDLEHOME\CNB\classes
 UNIX:         $CANDLEHOME/<arch>/cw  for inf files
                    $CANDLEHOME/<arch>/cw/classes  for jar files
          
If they are present then try clearing out the caches to see if the jar files will get downloaded.

If you are using the java web start client there also needs to be a corresponding jnlp file for the client.  That is located in the cnb/cw directory and is generated during the configuration of the TEPS as is the applet.html file.  The jnlp files are used by the java web start client and the applet.html file is used by the browser client. 

Support files for the desktop client are installed directly into the desktop client directory.  There should be a jar file as well
as an inf file per agent support installed.