Configure tool details

Use the Details tab of the Tool Properties dialog box to record information about the new tool. You must separately configure details for each new tool you create.

To configure tool details

Open the Tool Configuration Editor, if it is not already open.
Right-click the tool you want to configure to open the shortcut menu.
Select Properties to open the Tool Properties dialog box.
Select the Details tab.
In the Command Type list box, select a tool type. A tool type can be an executable, a URL, a VB script, a Jscript, Perl script, or a Windows Scripting Host (WSH) script.
NOTE:
VB scripts, Jscripts, Perl scripts, and WSHscripts run only on the management server or on a managed node. If .vbs has already been associated with the scripting engine, you can run the executable without a preface. For example: filename.vbs.
Your selection of a command type determines the options available within the rest of the dialog box. Click the down arrows for details on configuring each command type.
Executable Command Type
1. Check the Command Generates Output check box to see the results of your tool or command in the Tool Status dialog box. The results are shown as standard output. Error messages always appear in the text box, even if Command Generates Output is not checked.
  NOTE:
  A tool applied from the console is local and does not communicate with the action server.
2. If you want operators to be able to change the parameters you set, check the Allow operator to change parameters box.
3. If you want operators to be able to change the login you specify, check the Allow operator to change the login box. If the tool executes on the console, this option is unavailable and appears dimmed.
4. Check the Password Required box if you want users to have to enter a password to run the tool.
5. In the Command box, enter the executable for the tool. For example, type:
  cmd.exe /k DIR.
  
  If you configure a tool which has directory names containing spaces in the path, you must place the command within quotation marks, as shown in this example:
  
  "c:\Program Files\Hewlett-Packard\Examples\filename.exe"
  
  Use Browse if needed to locate the executable syntax.
  
  NOTE:
  Internal DOS commands such as copy, rename, and dir use a command interpreter that must be launched before the command can be executed. For commands of this type, precede the command with cmd/k, followed by any other parameters required.
  For example, for the executable dir, you could have the parameter: cmd/k dir C:\temp\*, in which cmd/k opens the command interpreter. For more details, see the Microsoft Windows documentation for cmd.
6. In the Parameters box, enter any parameters that apply to the executable.
  You can apply several variables here, if desired. Separate parameters using the syntax required by the executable you entered in the Command box.
URL Command Type
1. The Command generates output, Allow operator to change parameters, Allow operator to change the login, and Password Required options appear dimmed because they are unavailable for the URL command type.
2. In the URL box, type the URL you want to launch or use Browse to locate it. For example, type:
  http://www.hp.com
  You can enter any URL type, as shown in these examples:
  
  files://c:\openmail.log
  
  mailto:firstname_lastname@hp.com
  
  ftp://ftp.hp.com
  
  The only time http: is required is if you do not put any delimiter at the start of the command. For example, www.rose.hp.com would be changed to http://www.rose.hp.com.
VB script, JScript, Perl script, or WSHscript Command Type
1. Check the Command generates output check box to see the results of your tool or command in the Tool Status dialog box. The results are shown as standard output. Error messages always appear in the text box, even if Command generates output is not checked.
  NOTE:
  A tool applied from the console is local and does not communicate with the action server.
2. The Allow operator to change parameters box appears dimmed because it is unavailable for the VB Script, JScript, and WSHscript command types.
3. If you want operators to be able to change the login you specify, check the Allow operator to change the login box. If you configured the tool to execute on the console, this option is unavailable and appears dimmed.
4. Check the Password Required box if you want users to have to enter a password to run the tool.
5. Click Edit Script to open a resizable editing window in which to work.
  The following perl script example raises two questions:
  Is there a need to exit from embedded or external scripts?Is the exit 0; line needed?
  
  #!/usr/bin/perl
  print "hello";
  exit 0;
  
  If you are writing scripts that will be used by the Operations agent, then do not use "exit" to end the script if the script is embedded inside the policy for this reason:
  
  Whenever a VB or Perl script is embedded (Task type=VB Script or Perl Script) in a Monitor/Scheduled Task policy such as the example above, script execution is handled by the Advanced Monitor Agent. This agent gives the embedded script to the embedded "VB/Perl Script Engine" for processing. Because this happens in the same process as the monitor agent, any "exit" call from the script causes the process itself (opcmona) to abort.
  
  If the script is called by a Scheduled Task policy (Task type=Command) or Monitor policy (source type=Program), then the action agent (or monitor agent) creates a separate process for the external script. In this case, the exit which is called inside the external script is not propagated to the calling process, because the script runs in a different process, not in a thread in the same process.
  
  Consequently, exit should only be used when the script is called externally, not when the script is embedded inside a policy.
Click Apply to apply your changes.
Click OK to apply your changes and close the Tools Properties dialog box.
Click Cancel to close this dialog box without saving your changes.
Select the Target tab to continue configuring this tool.

Related Topics: