Verifying that Tivoli Enterprise Monitoring Agent starts correctly

Before you install Tivoli® Enterprise Portal, check that the Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Monitoring Agent are configured correctly and that they connect to the other components correctly.

About this task

To verify that Tivoli Enterprise Monitoring Agent starts successfully, perform the following steps:

Procedure

Start the OMEGAMON Collector.
Start the Tivoli Enterprise Monitoring Server.
Start the Tivoli Enterprise Monitoring Agent.
Check the Tivoli Enterprise Monitoring Agent startup messages.
1. Verify that the Tivoli Enterprise Monitoring Server that is configured is correct.
  This information is found in the RKLVLOG in the following message:
```
(000B-DA3327CB:kbbssge.c,52,"BSS1_GetEnv") CT_CMSLIST="<protocol>:<TEMS>;"
```
  where <protocol> is the communication protocol and <TEMS> is the name of the Tivoli Enterprise Monitoring Server.
2. Verify that the Tivoli Enterprise Monitoring Agent connected to the Tivoli Enterprise Monitoring Server.
  You can verify the connection with message RKLVLOG:
```
(0001-DA300D6B:kraaulog.cpp,442,"ctira_insert_log") KRAREG000, 
		Connecting to CMS MMRTE:CMS., Producer(IRA Manager)
```
  where MMRTE:CMS is the name of the Tivoli Enterprise Monitoring Server, and with the following message indicating a successful connection:
```
021.225 08:44:19.95 (0026-B56DC853:kraaulog.cpp,692,"IRA_OutputLogMsg") Connecting to CMS MMRTE:CMS                                 
021.225 08:44:19.95 (0027-B56DC853:kraaulog.cpp,475,"ctira_insert_log") KRAREG000, Connecting to CMS MMRTE:CMS, Producer(IRA_Manage 
021.225 08:44:19.95 r)                                                                                                             
021.225 08:44:19.95 (0028-B56DC853:kraarreg.cpp,1087,"ConnectToProxy") Successfully connected to CMS MMRTE:CMS using ip.pipe:#192.1 
021.225 08:44:19.95 68.54.83.16500.
```
3. Verify that the Tivoli Enterprise Monitoring Agent connected to the OMEGAMON® Collector.
  This information is in the JESMSGLG in the following message:
```
08.43.12 S0660303  KO2I0189I AGENT Agent STC   ATTEMPTING CONNECTION TO Agent STC   VERSION V540 BY REQUEST - DB2 DB2SSID (D5CONN)   
08.43.13 S0660303  KO2I0193I AGENT Agent STC   CONNECTED TO Agent STC   - DB2 DB2SSID (D5CONN)
```
  where:
  - Agent STC is the name of the Tivoli Enterprise Monitoring Agent started task.
  - OM Server STC is the started task ID of server.
  - DB2SSID is the DB2 subsystem ID.
  If you do not see this message, verify that the OMEGAMON Collector started task name specified for the KD5_AGT_STC parameter.
4. Verify that the Tivoli Enterprise Monitoring Agent connected to the OMEGAMON Collector.
  This information is in the JESYSMSG of the OMEGAMON Collector in the following message:
```
KO2I0154I D5API COLLECTOR IS CONNECTING TO DB2 DB2SSID 
ON BEHALF OF AGENT Agent STC
```
  where:
  - DB2SSID is the DB2 subsystem ID.
  - Agent STC is the name of the Tivoli Enterprise Monitoring Agent started task.
  If you do not see this message, verify on the SPECIFY CONFIGURATION PARAMETERS panel that the OMEGAMON Collector started task name specified in the KD5_AGT_STC parameter is correct.