Environment variables in the configuration load list

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

Environment variables in the configuration load list

You can reference an environment variable in the configuration load list instead of entering a fixed value for an attribute. Variable substitution enables you to apply the same load list definition in different environments.
Enclose environment variables in percent signs (%) when you reference them in a configuration load list. You might expect this requirement is for Windows only, because environment variables are delimited with percent signs on that operating system, but the percent sign delimiters are used to identify environment variables within the configuration load list on all platforms.
Environment variables in the configuration load list are resolved at the central configuration server or at the central configuration client, depending on whether a monitoring agent or a web server is acting as the central configuration server:

When a monitoring agent is acting as the central configuration server, environment variables in the configuration load list are resolved using the environment at the central configuration server.

When a web server is acting as the central configuration server, environment variables in the configuration load list are resolved using the environment at the central configuration client (the monitoring agent making the request).

To illustrate how variable substitution might be used in the configuration load list, consider an environment with two monitoring agents acting as central configuration servers. The environment variable SALES_CNFG_FILES is used to identify the directory that contains configuration files for use by systems that belong to the Sales Department of our company. The Primary central configuration server is a windows OS agent on a server called winhost
IRA_SERVICE_INTERFACE_CONFIG_HOME=C:\IBM\ITM\ConfigFiles
and the configuration for the sales department are in a directory called C:\IBM\ITM\ConfigFiles\Sales, so we set
SALES_CNFG_FILES=Sales
The Development Department also has a central configuration server configured on a Linux OS agent on their server linuxhost. They keep a current copy of the configuration files for the sales systems too; their agent is used as an alternate central configuration server if any new agents are deployed while winhost is unavailable. Their Linux OS agent uses the default value for IRA_SERVICE_INTERFACE_CONFIG_HOME, which is /opt/IBM/ITM/localconfig.
They locate the configuration files for the sales department in /opt/IBM/ITM/localconfig/eastcoast/sales, so they set:
SALES_CNFG_FILES=eastcoast/sales
This is the bootstrap configuration load list for the Sales Department:
<ConfigurationArtifact>
 <ConfigServer Name="BACKUP-CONFIG-SERVER"
  URL="http://linuxhost:1920///linuxhost_lz/linuxhost_lz/"
  User="itmuser"
  Password="{AES256:keyfile:a}8wNnAEj6uLMTTOeaC+2rfQ==" />
 <ConfigServer Name="CENTRAL-CONFIG-SERVER"
  URL="http://winhost:1920///primary.winhost_nt/primary.winhost_nt/"
  User="itmuser"
  Password="{AES256:keyfile:a}8wNnAEj6uLMTTOeaC+2rfQ=="
  AltServer="BACKUP-CONFIG-SERVER" />
  <ConfigFile Server="CENTRAL-CONFIG-SERVER"
   Name="cnfglist.xml"
   Path="%SALES_CNFG_FILES%"
   Disp="CNFGLIST"
   Activate="YES" />
</ConfigurationArtifact>
When agents connect to winhost, they collect C:\ibm\ITM\ConfigFiles\Sales\cnfglist.xml. If winhost is unavailable, agents connect to linuxhost and collect /opt/IBM/ITM/localconfig/eastcoast/sales/cnfglist.xml. By using the environment variable in the specification, additional customization is possible on the individual central configuration servers.

Parent topic:
Configuration load list XML specification

+
Search Tips | Advanced Search