You must configure the means by which an authorized user can invoke the custom control action.

To do so, you configure it as a platform service of FileServer File Service type on each platform where the action will be used.


Browse to the platform in the Resource Hub.


Select Tools > New Platform Service.


Name the service.

Including the platform name in the name for the new service will help you distinguish it from other services of the same type.


(Optional) In the Description field, describe the functionality of the control action.


Select FileServer File from the Service Type pulldown.


Click OK.

The Inventory page for the new platform service appears.


Click Edit in the Configuration Properties section of the Inventory page.

The Configuration Properties page for the new platform service appears.


On the Configuration Properties page, provide the following information:

Configuration Properties




Enter the path to the executable in the path field in the Shared section, including the name of the file itself. This can be a relative path if the executable is in the vCenter Hyperic agent directory structure. A better practice is to store the script external to the agent directory structure, and specify the full path to the executable, for example, /opt/hyperic/control_scripts/


Check the value in the timeout field in the Control section. This is the time in seconds HQ will wait for a response from the control before declaring it as a failed action. The default is 30 seconds, and under most circumstances should be adequate.


If the executable requires higher privileges than those available to the account running the Hyperic Agent, you can use the "prefix" field in the "Control" section to specify the sudo command. In this case, the local sudoers file has an entry for the user to run the script with a NOPASSWD directive.


Click Ok.