$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('

'); $("#ic-homepage__feed-tips").wrapInner('

'); });

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Create Non-agent file bundles IBM Tivoli Monitoring, Version 6.3


Add commands to the bundle

You can specify more commands to run during the deployment.


You can specify more commands to run during the deployment using the Remote Deploy Bundle Editor.


Procedure

  1. To specify more commands to run during the deployment, click Add in the Commands section of the Remote Deploy Bundle Editor.

  2. In the Command window, select the type of command Preinstall, Install, Post-Install, or Uninstalland then specify the command to run.

    Figure 1. Command window

    You must specify the fully qualified path to the command you want to run. For convenience, remote deployment provides a set of predefined variables. To reference the variable for a command, surround the variable with vertical bars, for example, |DEPLOYDIR|. For more information about predefined variables for commands, see (Table 1).


    Predefined Variables for Commands

    Variable Description
    DEPLOYDIR The temporary directory on the endpoint where the bundle is stored during the deployment. For instance, if you want to run myscript.sh, a script that is included in your bundle, you specify the following command: |DEPLOYDIR|/myscript.sh
    INSTALLDIR Either CANDLEHOME or the value of KDY.INSTALLDIRif specified on the addSystemcommand.
    CANDLEHOME The Tivoli Monitoring installation directory.

  3. Finally, select the Operating Systems on which the command is to run.


Parent topic:

Create Non-agent file bundles

+

Search Tips   |   Advanced Search