IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > Centralized Configuration > Configuration load list XML specification
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Bootstrap configuration load list
When placing the initial configuration load list, you can place a file that immediately identifies all the components that the monitoring agent needs to collect from the central configuration server. However, this means that you must place a unique configuration load list file on every agent. One of the items that a central configuration client should always collect from the configuration server is the load list. This allows the load list to be modified from the configuration server.
Because you will be identifying the complete configuration load list anyway, to initialize Centralized Configuration operations, you only need to tell the agent where to connect to get the first configuration load list. A simple configuration load list that contains one ConfigServer element and one ConfigFile element to define the DISP=CNFGLIST file can be used to bootstrap Centralized Configuration operations.
In this example, the ConfigServer URL identifies the central configuration server location and the user name and password to gain access to that server. The ConfigFile element points to the server named in the ConfigServer element and identifies the configuration load list file as cnfglist.xml, which is in the path for the product.
<ConfigurationArtifact> <ConfigServer Name="CENTRAL-CONFIG-SERVER" URL="http://winhost:1920///primary.winhost_nt/primary.winhost_nt/" User="Administrator" Password="{AES256:keyfile:a}vHBiEqmmvylNPs90Dw1AhQ==" /> <ConfigFile Server="CENTRAL-CONFIG-SERVER" Name="cnfglist.xml" Path="@PRODUCT@" Disp="CNFGLIST" Activate="YES" /> </ConfigurationArtifact>After creating a bootstrap configuration load list that identifies the correct load list for the agent, place the file and restart the agent.
Parent topic:
Configuration load list XML specification