ConfigFile policy Data tab

Use the Data tab to modify the configuration file that is written to the node when the corresponding ConfigFile policy is deployed. The ConfigFile text appears in the ConfigFile Content edit field.

Syntax and keywords

The syntax and keywords used in configuration files is determined by the SPIs and described in the SPI documentation.

The following generic keywords can be used at the beginning of all configuration files to notify external applications, for example HP Performance Agent Software, when a ConfigFile policy is added to or removed from a directory that is of particular interest to that application.

Keyword Description

#$Installcommand=<command>
#$Deinstallcommand=<command> <command> contains the command to be run, including all required parameters. If necessary, use quotation marks to handle all platforms.

Keyword	Description
`#$Installcommand=<command>` `#$Deinstallcommand=<command>`	`<command>` contains the command to be run, including all required parameters. If necessary, use quotation marks to handle all platforms.
`#$Commandtype=<value>`	`<value>` specifies the type of command to be used: 1 Executable (default) If you do not specify the command type, the ConfigFile 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. HPOM automatically appends the appropriate extension so that a single policy can be run on both Windows and UNIX nodes. 3 Perl script

#$Commandtype=<value>

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

1: Executable (default)
If you do not specify the command type, the ConfigFile 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. HPOM automatically appends the appropriate extension so that a single policy can be run on both Windows and UNIX nodes.
3: Perl script

NOTE:
Although the ConfigFile policy editor supports non-ASCII characters, you will receive an error message when you deploy such policies to DCE agents. Only HTTPS agents accept ConfigFile policies with non-ASCII characters.

Template files

SPIs can install one template file for each ConfigFile variety. If a template is present, the Load Template and Save as Template buttons are available.

To load a template

Click Load Template to load a template into the edit field.
If the edit field already contains text, you are asked if you want to replace the data with the template or cancel. Click Yes to replace the data in the edit field with the template information. You can modify the existing template and save your changes.
Click Save as Template to save the data to the template file. You are asked if you want to replace the existing template.
Click OK to replace the original template with the modified template.

Syntax validation

SPIs can install a validation mechanism that lets you verify the text in the ConfigFile Content field to ensure the syntax used is correct. Click Check Syntax to start the validation tool.

Help information

SPIs install help information with each ConfigFile variety. The help topic usually provides information about configuration options and syntax. Click Help on ConfigFile to view the help topic.

TIP:
You can split the text area vertically and horizontally by dragging the split controls. (The split controls are at the top of the vertical scroll bar and at the left of the horizontal scroll bar.)

Related Topics: