IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > Centralized Configuration > Centralized Configuration startup > Initiating Centralized Configuration with a load list file
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Initiating with remote deployment of non-agent bundles
If your environment contains a large number of existing agents that are connected to a Tivoli Enterprise Monitoring Server, you might prefer to use remote deployment to distribute the configuration load list to the agents. You can use the Agent Builderto build non-agent deployment bundles.
Procedure
- Use Agent Builder to create a non-agent deploy bundle. See the IBM Tivoli Monitoring Agent Builder User's Guide for details.
- Add the common bootstrap configuration load list confglist.xml file to the bundle.
- Create your own copy command that copies the file to the correct location for the agent that you plan to deploy to. Here is an example of an installation command for the Linux OS agent:
cp |DEPLOYDIR|/cnfglist.xml |CANDLEHOME|/localconfig/lz/lz_cnfglist.xml
- Recycle the agent to start using the new configuration load list after it is deployed.
- Optionally, create a post-installation command that uses the Agent Management Services watchdog to recycle the agent. Create a command for each platform that you plan to support because specify the fully qualified path to the pasctrl utility located in the agent's binary architecture directory.
- Here are some post-installation commands that could be used:
install_dir\TMAITM6[_x64]\kcapasctrl.exe recycle nt
install_dir/lx8266/lz/bin/pasctrl.sh recycle lz
install_dir/aix526/ux/bin/pasctrl.sh recycle ux
- Non-OS agents still use the watchdog from the OS agent. A multi-instance DB2 agent on Windows, for example, that is managed by Agent Management Services requires that you specify the instance name in the post-installation command. Therefore, including the restart in the deploy bundle might not be the best method but can be done if standard instance names are used.
install_dir\tmaitm6\kcapasctrl.exe recycle –o db2inst1 ud
- You could also include a script in the deploy bundle that contains more advanced logic to recycle agent instances and call that script in a post-installation command.
Deploy_dir/afterscript.sh
- Generate the remote deployment bundle.
- If the agent was not restarted using a post-installation command in the deploy bundle, recycle the agent to activate the configuration load list.
- See Start, stopping, and recycling an agent through the Tivoli Enterprise Portal.
- OS agents can be recycled in the portal client using the AMS Recycle Agent Instance TakeAction
- The AMS Recycle Agent Instance Take Action command can also be run using the CLI tacmd executeAction. Here are some examples for the OS agents:
tacmd executeaction -n "AMS Recycle Agent Instance" -t nt –m Primary:winhost:NT -c value="Monitoring Agent for Windows OS, kntcma.exe,,"
tacmd executeaction -n "AMS Recycle Agent Instance" -t lz –m linuxhost:LZ -c value="Monitoring Agent for Linux OS,klzagent,,"
tacmd executeaction -n "AMS Recycle Agent Instance" -t ux –m unixhost:KUX -c value="Monitoring Agent for Unix OS,kuxagent,,"
- Add the bundle to your depot using the CLI tacmd addBundles.
- Deploy the bundle to the agents using Add Managed System in the portal client (see Add an agent through the Tivoli Enterprise Portal) or through the CLI using tacmd addSystem from the monitoring server (see IBM Tivoli Monitoring Command Reference.
- If the agent was not restarted using a post-installation command in the deploy bundle, recycle the agent to activate the configuration load list as described in step 1.e.
Parent topic:
Initiating Centralized Configuration with a load list file