Centralized Configuration provides the ability to update local configuration files on many monitoring agents without connection to a Tivoli® Enterprise Monitoring Server.
Centralized Configuration is a Tivoli monitoring agent or (preferably) web server acting as a repository of agent configuration files that are pulled by monitoring agents on the same or different computers using their local configuration load list. The repository can contain such files as the configuration XML for SNMP alerts and EIF events, automation scripts, and any other pertinent agent operational files. The configuration load list specifies the central server location and the configuration files to get.
The central configuration server can be a Tivoli Monitoring agent at version 6.2.2 Fix Pack 2 or later, or it can be any web server, such as WebSphere®, IBM® HTTP, Microsoft IIS, or Apache. For security reasons, IBM recommends you choose a web server.
You can have multiple central configuration servers and logically arrange them as a hierarchy of central configuration servers.
After Centralized Configuration has been initiated by the agent, the default behavior is to pull any file updates from the designated central configuration server every hour. You can also get updates on-demand by entering the load list as an Agent Service Interface request.
Agents dynamically activate newly downloaded well-known configuration files, such as private situations and configuration load lists, without agent restart. Other configuration changes that require the agent to restart to enable the new changes to take effect can include an agent restart specification so that these configuration updates take effect immediately without intervention.
The basic tasks for implementing Centralized Configuration for existing agents are: