Define common configuration parameters: accessing centralized configuration information

IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Monitor your operating system via a System Monitor Agent
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Define common configuration parameters: accessing centralized configuration information

System Monitor Agents are started at the end of their silent installation. Unless private configuration files exist for them, these agents run but do not analyze situations or send events. Centralized configuration allows an agent to retrieve these files from the centralized configuration server and to begin using them immediately.
You define these parameters in the pc_silent_install.txt silent response file that is used when installing a System Monitor Agent.
The System Monitor Agent installation process uses entries in the silent response file to create entries in the agent's environment file, based on statements of this form: SETENV_parameter=value statements create parameter=value statements in the agent's environment file, whereas SETENCR_parameter=value create parameter={AES256:keyfile:a}encryptedvalue statements.
Example: These silent response file entries connect to a centralized configuration server running on the node named linuxhost:
SETENV_IRA_CONFIG_SERVER_URL= http://linuxhost:1920///linuxhost_lz/linuxhost_lz/
SETENV_IRA_CONFIG_SERVER_USERID=itmuser
SETENCR_IRA_CONFIG_SERVER_PASSWORD=password
SETENV_IRA_CONFIG_SERVER_FILE_PATH=initloadlist/@PRODUCT@
SETENV_IRA_CONFIG_SERVER_FILE_NAME=cnfglist.xml
Agents recognize the following keywords and substitute for them runtime values retrieved from the client:

@PRODUCT@

Agent's lowercase, two-letter product code. Example: For a Windows OS agent, @PRODUCT@_trapcnfg.xml resolves to nt_trapcnfg.xml.

@ITMHOME@

IBM Tivoli Monitoring installation path. Example: If this is a Linux system and the default installation path is used, @ITMHOME@ resolves to /opt/IBM/ITM/.

@MSN@

Agent's managed system name (not the subnode name). Example: If the agent's managed system name is primary:icvw3d62:nt, @MSN@ resolves to primary-icvw3d62-nt.

@TASKNAME@

Agent's process name. Examples: klzagent; kntcma.

@VERSION@

Agent's product version string. Example: If the agent's version is Tivoli Monitoring 6.2.2 fix pack 2, @VERSION@ resolves to 06-22-02.

@HOSTNAME@

Computer host name. Example: myhost.

@IPADDRESS@

Computer network interface IP address. Example: If the agent's IP address is 9.42.38.333, @IPADDRESS@ resolves to 9-42-38-333.

@OSTYPE@

Operating system type. Examples: linux; win2003.

@OSVERSION@

Operating system version. Examples: Red Hat Enterprise Linux Version 5 (64 bit) resolves to 2-6-18-128-el5; Windows 2003 (32 bit) with Service Pack 2 resolves to 5-2-sp2

@SYSTEMID@

Computer system identifier. Example: System ID icvr4a04.mylab.mycity.ibm.com resolves to icvr4a04-mylab-mycity-ibm-com.

For detailed information on using the centralized configuration facility, see the IBM Tivoli Monitoring Administrator's Guide.

All special characters in the parameter values for all keywords other than @ITMHOME@ are converted to dashes (-). For example, if the IP address is 9.42.38.233, keyword @IPADDRESS@ resolves to 9-42-38-233.
The value for @ITMHOME@, however, remains unchanged.

The value of SETENCR_IRA_CONFIG_SERVER_PASSWORD may be either plain text or encrypted when saved in the pc_silent_install.txt silent response file. Plain-text values are encrypted when created in the agent environment file. Encrypted values are created as specified. The itmpwdsnmp utility is used interactively on another system to encrypt the password string if desired; see the IBM Tivoli Monitoring Administrator's Guide.

Parent topic:
Monitor your operating system via a System Monitor Agent

+
Search Tips | Advanced Search