IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Deploy monitoring agents across your environment > Self-describing agent installation
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Manage your self-describing agent installations
You can use tacmd commands to exercise more control over the self-describing agent products that are installed by the self-describing agent process.
As of IBM Tivoli Monitoring V6.3, the hub monitoring server does not allow the automatic installation of a self-describing agent enabled product. First specify the products and versions that can be installed, or change the default self-describing agent installation behavior to permit installations for all products and versions.
The following table describes the administration commands for managing your self-describing agent installations:
tacmd commands to manage your self-describing agent installations
tacmd Command Description tacmd addsdainstalloptions Specify the products and versions that can be installed by the self-describing agent facility. tacmd editsdainstalloptions Modify an existing product version configuration, or change the default self-describing agent installation behavior. tacmd listsdainstalloptions Display the existing self-describing agent installation configurations from the hub monitoring server. tacmd deletesdainstalloptions Remove a specific version configuration, or remove all versions for a product. Beginning with V6.3, if you want to permit self-describing agent installations for all products and versions without any blocking, you must perform the following steps:
- Ensure that there are no products configured for self-describing agent installation by issuing the command tacmd deletesdainstalloptions -all.
This will remove any previous self-describing agent product versions and configurations that were added.
- Issue the command tacmd editsdainstalloptions -t DEFAULT -i ON.
Self-describing agent installations for all products and versions without any blocking is essentially the default behavior in V6.2.3 and V6.2.3 FP1. To use the V6.3 default behavior and block automatic installations, you can issue the command tacmd editsdainstalloptions –t DEFAULT –i OFF. You can then permit the installation of specified products and versions using the tacmd addsdainstalloptions command.
For the full syntax, including parameter descriptions, see the Command Reference.
The following IBM Tivoli Monitoring components are not updated by self-describing agent installations:
- The Tivoli Enterprise Monitoring Automation Server component contains the Open Services Lifecycle Collaboration Performance Monitoring (OSLC-PM) service provider. The Performance Monitoring server provider does not support the dynamic refresh of application support files. This means that the Tivoli Enterprise Monitoring Automation Server must be recycled when new application support is added to a system, regardless of whether the support was added through a self-describing agent, a regular installation, or a manual copy. However, if the monitoring agent does not provide OSLC support, then the Automation Server does not need to be recycled. Operating system agents before IBM Tivoli Monitoring V6.3 do not provide OSLC support. For other types of monitoring agents, refer to the agent documentation to determine if they provide OSLC support.
- The Tivoli Enterprise Portal desktop client
- Specify what products and versions are installed on your monitoring server and portal server by the automatic self-describing agent process
Follow the steps in this section to specify what products and versions are installed on your monitoring server and portal server by the automatic self-describing agent process.
Parent topic:
Self-describing agent installationRelated concepts:
Dynamically controlling the hub monitoring server self-describing agent capability