IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Deploy monitoring agents across your environment > Work with non-agent bundles
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Deploy a non-agent bundle
Complete the steps in this section to deploy a non-agent bundle.
- Run the tacmd listBundles command to view the agent bundles.
- Add the agent bundle to the depot using the tacmd addBundles command.
- Run the tacmd viewDepot command to display the contents of the agent depot. Verify the non-agent bundles were added to the depot.
- Run the tacmd addSystem command with appropriate configuration information. To specify an installation path, run this command with the KDY.installPath property set to CANDLEHOME/productcode if you want the location to be within the CANDLEHOME directory, or set to /productcode if you do not want the location to be within the CANDLEHOME directory, for example:
tacmd addSystem -p KDY.installPath=/IBM/ITM/Uxxx -n managed_os -t Uxxx
- Check to ensure the status of transactions is queued or InProgress.
What to do next
Monitor the workspace or use the tacmd getDeployStatus command to verify the result. When the deployment completes successfully, verify that the bundle was installed at the default location if you did not specify the installation path, or to the location that you chose if you did specify an installation path.
- The OS agent must already be installed on the system before deploying the non-agent bundle.
- The non-agent bundle must exist in the depot of the monitoring server to which the OS agent is connected.
- For more information about each of these commands, see the table below that links to a description of each command, including syntax and option information, along with examples.
Parent topic:
Work with non-agent bundles