IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure Agent Management Services on Tivoli System Monitor Agent
Configure the Agent Management Services for Tivoli System Monitor Agents if you want to use the services to monitor and control agent availability.
Agent Management Services is configured differently in a system monitor agent environment:
- System monitor agents are managed by Agent Management Services by default. You suspend management using the disarmWatchdog command, which disables the Agent Management Services watchdog for the system monitor agent and any agents created with Tivoli Monitoring Agent Builder on the same system. You resume management by the Agent Management Services using the rearmWatchdog command, which enables the watchdog for the autonomous agents that are managed by the Agent Management Services. These commands are described in the agent user's guide.
- Agent Builder agents that are installed in a system monitor agent environment are not managed by the Agent Management Services watchdog by default. You can change whether the agent is managed by the watchdog.
After installing an Agent Builder agent in a system monitor agent environment, take these steps to start or stop Agent Management Services management.
Procedure
- While the watchdog process is running, move the common agent package (CAP) file named kpc_default.xml (where pc is the two-character product code) out of the CAP directory to a temporary location. The file is located in the KCA_CAP_DIR directory.
install_dir\TMAITM6[_x64]\CAP\
install_dir/config/CAP
Removing the file from the CAP directory renders the agent invisible to the Agent Management Services.
- Modify all instances of <managerType> in the CAP file to enable or disable management:
- <managerType>ProxyAgentServices</managerType> to enable management.
- <managerType>NotManaged</managerType> to disable management.
A best practice is to rename the modified file to kpc.xml (where pc is the two-character product code). All CAP files located in the KCA_CAP_DIR are processed by Agent Management Services. If two or more CAP files share the same "subagent ID" value, they are processed in sorted order. For example, kca.xml is used before kca_default.xml. Also, renaming the CAP file to kpc.xml ensures that your changes do not get overwritten during a future upgrade.
- Save the updated file.
- While the watchdog process (kcawd) is running, move or copy the updated CAP file back to KCA_CAP_DIR.
Results
The updated Agent Management Services settings are processed after the CAP file is placed in KCA_CAP_DIR.
Parent topic:
Agent-based services