by
Norman Krueger
ITM Self-Describing Agents (SDA) functionality:
- Overview
- The most important supported Agents
- Excluded Agents
- Enable/Disable od SDA function
- Monitor of SDA setting
Overview:
In this blog and in the subsequent blogs I would like to describe the SDA configuration.
The SDA functionality offers numerous advantages to the itm administrator:
The agents have the necessary installation packages by default.This ensures that
the correct version is always installed. Another advantage is the fact that no restart
is necessary. The application support is installed on the HUB / RTEMS / TEPS / TEP-Clients.
Summarize:
- Agents provide SDA support packages
- No recycling of TEMS or TEPS
- Supported for TEP Browser and Webstart clients
- Only highest available version of support installed
Reduce or eliminate manual installation of ITM product support files
A possible drawback might be the performance aspect. Therefore this point had to be clarified in advance.
How many agents use this function?
In what cycles do updates take place?
Is my network and the servers able to perform this task?
Is there time window for the installation?
Do new functions have a negative impact?
How is a new application support with regard to older agents?
The most important supported Agents:
- UNIX/LINUX/WINDOWS OS Agent
- Agent Builder Agent
- WPA/SPA
- Agentless Remote OS Agent (all platforms)
- Unix logfile Agent
Excluded Agents:
- ITPA
- Universal Agent
Enable/Disable od SDA function:
- ITM Agent => TEMA_SDA=Y ( by default ON)
- RTEMS => KMS_SDA=Y ( by default ON)
- HUB-TEMS => KMS_SDA=Y ( by default OFF)
Monitor of SDA setting:
There are different possibilities to see if the SDA is switched on
Monitor of switch on of agents
the kincinfo -e on Windows systems
the cinfo -e on Linux and UNIX systems
Example: cinfo -e
=========================================================================
..Application support propagation
PC PRODUCT DESC PLAT VER BUILD SDA STATUS
00 Monitoring Agent for AB_COMMAND lx8266 06.23.00.00 201602161516 Enabled
02 Monitoring Agent for HTTP_URL lx8266 06.23.00.00 201603100857 Enabled
09 Monitoring Agent for NORMI_A lx8266 06.23.00.00 201610041515 Enabled
32 Monitoring Agent for BEA_SAA_SNMP lx8266 06.23.00.00 201701110920 Enabled
75 Monitoring Agent for IT_DB_Oracle lx8266 06.31.00.00 201610121531 Enabled
as Tivoli Enterprise Monitoring Automation Server lx8266 06.30.07.00 d6350a Disabled
hd Warehouse Proxy lx8266 06.30.07.00 d6350a Enabled
lz Monitoring Agent for Linux OS lx8266 06.30.06.00 53181 Enabled
=========================================================================
Monitor of switch on of RTEMS/HUB
the tacmd listsdastatus on Linux/UNIX and Windows systems
Example:
=========================================================================
Hub/RTEMS State Status
CANDLE OFF 16
RTEMS_ALLN ON 0
RtemsRH OFF 16
SLESHUB63 ON 0
=========================================================================
The status 0 means enabled and the status 16 mean disabled
Monitor which support has installed by SDA
the tacmd listappinstallrecs on Linux/UNIX and Windows systems
Example:
=========================================================================
HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS
RTEMS_ALLN A4 06300200 5655 TMS 06300200 0
RTEMS_ALLN HD 06300200 5655 TMS 06300200 0
RTEMS_ALLN LZ 06300300 5655 TMS 06300300 Y IC 0
RTEMS_ALLN MS 06300200 5655 TMS 06300200 0
=========================================================================
The status 0 means installed by hand and the status IC mean installed by SDA