Populating an agent depot with the tacmd addBundles command

Populating an agent depot with the tacmd addBundles command.

To add bundles for operating systems other than that used by your monitoring server, use the tacmd addBundles command.
Restriction: Only Tivoli-provided product agent bundles should be loaded into the IBM Tivoli Monitoring deployment depot. User-provided or customized bundles are not supported. Use only Tivoli® provided tacmd commands to process bundles and to execute agent deployments. Manual manipulation of the depot directory structure or the bundles and files in it is not supported and may void your warranty.
Important: Run the tacmd login command before executing commands from the tacmd library. Run the tacmd logoff command after you finish using the tacmd command library.
To populate the agent depot using the tacmd addBundles command, run the following command:
tacmd addBundles 
		[-i IMAGE_PATH] 
		[-t PRODUCT_CODE] 
		[-p OPERATING_SYSTEM] 
		[-v VERSION] 
		[-n] 
		[-f]
For the full syntax, including parameter descriptions, see IBM® Tivoli Monitoring Command Reference.

Examples:

By default, the agent depot is located in the %CANDLE_HOME%\CMS\depot_directory on Windows and $CANDLE_HOME/tables/tems_name/depot directory on UNIX. The tacmd addBundles command puts the agent bundle in that location unless another location is defined in the monitoring server configuration file for DEPOTHOME.

If you want to change this location, do the following before you run the tacmd addBundles command:
  1. Open the KBBENV monitoring server configuration file located in the %CANDLE_HOME%/CMS/ directory on Windows and the $CANDLE_HOME/tables/tems_name directory on Linux and UNIX.
  2. Locate the DEPOTHOME variable. If it does not exist, add it to the file.
  3. Type the path to the directory that you want to use for the agent depot.
  4. Save and close the file.
  5. On UNIX or Linux only, add the same variable and location to the kbbenv.ini file located in $CANDLE_HOME/config/kbbenv.ini.
    Note: If you do not add the variable to the kbbenv.ini file, it is deleted from the KBBENV file the next time the monitoring server is configured.