You can enable or disable the self-described
agent capability through a monitoring agent environment configuration
variable.
Disable the self-describing feature any time
you do not want automatic update and propagation of self-described
agent application metadata for one or more individual agents. Then,
the application support for the agent must be manually installed and
activated at the monitoring server and portal server. By default the self-describing
capability for agents is turned on.
Procedure
- On the computer where the monitoring agent is installed,
in the Manage Tivoli Enterprise Monitoring Services application,
right-click the agent and select Advanced→ Edit ENV file.
- Edit the existing environment variable: TEMA_SDA=Y
| N
-
- On the computer where the monitoring agent is installed,
change to the <install_dir>/config/ directory.
- Open the coordinating file:
For single-instance
agents: <pc>.ini
For
multi-instance agents: <pc>_<instance>.ini file
Where pc is
the two-character product code.
- Edit the existing environment variable: TEMA_SDA=Y
| N
- Open /qautotmp/kmsparm.kbbenv.
- Edit the existing environment variable: TEMA_SDA=Y
| N
- See TEMA_SDA in
the IBM Tivoli OMEGAMON XE and Tivoli Management Services
on z/OS: Common Planning and Configuration Guide.
What to do next
Restart the monitoring server.
You can review
the agent support versions in the following ways:
- Review the agent and monitoring server operations logs to determine
if the agent is operating in the standard or the self-described agent
mode. The Managed System Status workspace
has a link to the operations log for each monitoring agent.
- The tacmd listappinstallrecs command
returns the application support installation records and the tacmd
listSdaStatus command displays the current self-describing
agent operational status for all monitoring servers in the environment.
Remember that these commands are not available when the monitoring
server is not running. See Self-describing agent installation.