Configure ConfigFile Policies

1. Open the Policy Templates manager:

   Administration > Monitoring > Policy Templates

   Alternatively, click Policy Templates.

2. In the Policy Template Groups pane, expand Policy Management > Templates grouped by type > Configuration.

3. Click the ConfigFile folder, and then do one of the following:

   • To add a new policy template, in the Policy Templates pane, click the  New Item button, and then click the Add New Policy Template... or the Add New Policy Template (Raw Mode) button.

     The New ConfigFile Template Editor opens.

   • To edit an existing policy template, click the policy template in the Policy Templates pane, click the  Edit Item button, and then click the Edit Policy Template or the Edit Policy Template (Raw Mode) button.

     The Edit ConfigFile Template Editor opens.

The first part of a ConfigFile policy (also known as ConfigFile variety) defines the path and file name of the configuration file that is associated with the policy. The ConfigFile definition contains the following attributes:

Application

Specifies the name of the managed application. This is usually the name of the SPI (for example dbspi).

SubGroup

Additional grouping mechanism that helps the SPI to manage configuration files by grouping them according to custom categories. For example, dbspi has one subgroup for every supported database vendor.

Filename

Specifies the file name of the configuration file (for example, dbmon.cfg).

The data part of a ConfigFile policy contains the rules or instructions that configure the instrumentation on the node and begins with the following keyword:

Data:

The following generic keywords can be used after Data:

#$Installcommand=<command>
#$Deinstallcommand=<command>

<command> contains the command to be run, including any required parameters. If necessary, use quotation marks to handle all platforms. $Installcommand runs when the policy is deployed or enabled. $Deinstallcommand runs when the policy is removed or disabled.

#$Commandtype=<value>

<value> specifies the type of command to be used:

1—Executable (default)
If you do not specify the command type, the Config File policy assumes that the command is an executable.

2—VBScript or shell script
You do not need to add a .vbs or .sh extension to the command. OMi automatically appends the appropriate extension so that a single policy can be run on both Windows and UNIX nodes.

3—Perl script

When you deploy or enable the following example ConfigFile policy, the file acme.cfg is created, the last three lines are added to the file, and the file install.bat runs. When you remove or disable the policy, the file acme.cfg is removed and the file deinstall.bat runs.

Application=acme
SubGroup=acme_application
Filename=acme.cfg

Data:
#$Installcommand="C:\data\install.bat"
#$Deinstallcommand=C:\data\deinstall.bat"

AcmeSystemID = ACME
AcmeUserName = acme_root
AcmePassword = acme_password

1. In the ConfigFile Policy Editor, in the Properties page, type a Name for the policy.

   Optional. Provide a description of the policy (Description), select the instrumentation that will be deployed with the policy onto the host system where the agent is running (Instrumentation), and select the operating systems with which the policy is compatible (OS Types).

   For more information, see Properties Page.

2. In the Policy Data page, type the ConfigFile definition and data using the HPE Operations Agent ConfigFile policy syntax. If you are creating a new policy, copy and paste template data from an existing policy template. Alternatively, click the button to load policy data from a policy template file on your computer.

   For details, see ConfigFile Definition and ConfigFile Data.

   You can also use policy parameters. For more details, see Policy Parameters Tab.

3. Click Save and Close to save the policy template and exit the wizard.