Use the tacmd configureSystem command to edit configuration options of an existing managed system. By default, the managed system monitoring agent is restarted so the new configuration parameters can take effect. When using this command to set or modify an environment variable, ensure that the value you assign to the variable is correct. An incorrect value assignment might impact the agent behavior and possibly prevent the agent from starting. Note that you can use this command with the -e|--environment option to specify environment variables for an OS agent. However, in the case of an OS agent, you cannot use the -p (properties) option to update the OS agent connection properties. To configure OS agent connection properties, use the tacmd setAgentConnection command.
Specify the configuration data through the parameter pair SECTION.NAME=VALUE. If an optional parameter is specified with an equal sign but without a value, the specified parameter is removed from the agent configuration. By using the bulk deployment option, the agents specified in the bundle group are configured on the managed systems specified in the deployment group.
The environment option is supported for both individual configuration and group configuration where there are environment variables that need to be changed or defined at the target node for the agent to work properly. Only those environment variables should be set or updated that are incorrect or not set and are required for the agent. You can query deployment workspaces if you are using the Tivoli Enterprise Portal or run the tacmd getDeployStatus command to determine the result for the tacmd configureSystem command.
The -x|--noexecute option is intended to allow you to determine which configuration properties are used to configure which managed systems.
If you specify the -n|--noagentrestart option instead of the default, the managed system monitoring agent is reconfigured, but the agent is not restarted after the configuration.
tacmd configureSystem
{-m|--system} SYSTEM
{-p|--property|--properties} SECTION.NAME=VALUE ...
[{-e|--environment} NAME=VALUE ...]
[{-n|--noagentrestart}]
[{-f|--force}]
tacmd configureSystem
{-h|--host} HOST[:PORT]
[{-c|--configfile|--configfiles} CONFIG_LIST]
[{-l|--filelist} FILE_LIST]
[{-p|--property|--properties}] SECTION.NAME=VALUE ...
[{-r|--reboot}]
[{-f|--force}]
tacmd configureSystem
{-g|--deploygroup DEPLOY_GROUP_NAME}
{-b|--bundlegroup BUNDLE_GROUP_NAME}
[{-e|--environment} NAME=VALUE ...]
[{-x|--noexecute}]
[-n|--noagentrestart]
[{-f|--force}]
tacmd configureSystem
{-stdin|--stdin}
-e CTIRA_HOSTNAME=aixnode CTIRA_HEARTBEAT=8
Refer
to the "Agent configuration and environment variables" appendix of
the IBM Tivoli Monitoring: Installation and Setup Guide for
a list of supported variables. tacmd configureSystem -m stone:UA -p UA.CONFIG="file_unix.mdl"
tacmd configureSystem -g UnixGroup -b ULBundle
tacmd createGroup -g UnixGroup -d "unix deploy group" -t DEPLOY
-p KDY.SERVER=IP.PIPE:\\s108o001.tivlab.raleigh.ibm.com:1918
KDYRXA.TIMEOUT=300 KDYRXA. CONNECT_TIMEOUT =100 KDYRXA. RXAPORT =4230
tacmd createGroup -g ULBundle -d "unix log Bundle group" -t BUNDLE
tacmd addGroupMember -g UnixGroup -t DEPLOY -m f50pa2d.tivlab.raleigh.ibm.com
-p KDYRXA.installDir=/data/aut/s108o001 KDYRXA.RXAUSERNAME=root
KDYRXA.RXAPASSWORD=**** KDYRXA.RXAPROTOCOL =ssh KDYRXA. RXAPORT=22
tacmd addGroupMember -g UnixGroup -t DEPLOY -m amssol19.tivlab.raleigh.ibm.com
-p KDYRXA.installDir=/data/aut/s108o001 KDYRXA.RXAUSERNAME=root
KDYRXA.RXAPASSWORD=**** KDYRXA.RXAPROTOCOL =ssh KDYRXA. RXAPORT=22
tacmd addGroupMember -g ULBundle –m linuxULBundle -t BUNDLE -y UL
–v 062100000 –i li6263
tacmd configureSystem -m stone:UX -e CTIRA_HOSTNAME=stoneUNIX CTIRA_HEARTBEAT=9
See Table 1.