IBM Support

NUGGETS: How to know when the TEMS and TEPS have fully started

Technical Blog Post


Abstract

NUGGETS: How to know when the TEMS and TEPS have fully started

Body

 

 

 
image

 

As normal, I like to blog about areas of ITM that I cover when working with you, either through PMRs or direct on customer site.

Today's series topics is on how to check that the core ITM components have fully started and are operational

 

Many of you have downtime for maintenance, or perform DR testing and need a way to check that components have fully started after the work item is completed.

The below steps will show you how to check the core components logs and verify the component is fully operational again.

 

 

 

 

How to check the TEPS has started


To check the TEPS has started and is fully initialised you need to check the TEPS RAS1 logs. 

The TEPS writes the following message to its RAS1 log to indicate that initialization is complete:


KFW1020I ********* Waiting for requests. Startup complete ********

 

 

Which log should you check? 

On Windows, UNIX, and Linux systems, the filename is of the form hostname_pc_tttttttt-nn.log

 

pc is the product code,

tttttttt is the Unix time, or POSIX time in hexadecimal when the component opened the log file

nn is the log file sequence number.

 
 

​For the TEPS the product code is "cq"

 
An example of the TEPS log naming convention would be the fllowing for a machine with the hostname GIGGS.
 
GIGGS_cq_472649ef-02.log

 

Log Locations:

Windows:  Install_Dir\logs

Unix/Linux:  Install_Dir/logs

 

NOTE: The default paths for install_dir are C:\Program Files\IBM on Windows and /opt/ibm/ on Linux of UNIX

 

 

 

 

How to check the TEMS has started


To check the TEMS has started and is fully initialised, you need to check the TEMS MSG2 logs (also known as the TEMS operations log). 



The TEMS writes the following message to its MSG2 log to indicate that initialization is complete.

 
KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.

 

 

Which log should you check? 

 
Windows: The TEMS operational log file is named KDSMAIN.MSG

 

UNIX/Linux: The filename is of the form hostname_pc_tttttttttt.log where pc is the product code, tttttttt is the Unix time, or POSIX time in decimal when the component opened the log file.

 
The product code for the TEMS is "ms"
 
 
 
 

 

What Can you use this for beyond a manual check?

I have seen customers set up log file agents to scrape the logs for this message, as part of a self built checking system when they bring up the core components.

 
This can be a really good way to help your operations teams out when they see a component restart. If they don't see a situation with this message being scanned they can tell that component has not fully initialised yet and may need further investigation. 

 

As normal if you have any questions, feel free to reach out to me on the below channels and in the comments box below

 

Thanks!

 

 

 

 

 

Let's connect!

To follow my social updates on IBM software, please feel free to connect with me by clicking on the images below:

 

imageimageimage

 

Find all my other blogs here:

LINK ------------>   Full Index of My Blogs   <------------ LINK

 

 

 

Tutorials Point

 

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

 

 

image

 

image

 

image

 

 

  

Check out all our other posts and updates:

Academy Blogs:https://goo.gl/U7cYYY
Academy Videos:https://goo.gl/FE7F59
Academy Google+:https://goo.gl/Kj2mvZ
Academy Twitter :https://goo.gl/GsVecH


image

 


 

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

UID

ibm11082793