5.8

Parser Directives
When you create, edit, or clone a custom information type in VCM, you can select from a list of built-in
templates. For example, if you have a file that conforms to the structure of the krb5.conf template, you
enter an identification expression to identify the file, and select the krb5.conf template. Then, to populate
the parser directive code pane, you select an existing template.
The parser directive code begins with the parser type, such as tabular, wff, or ini. All other directives
describe how to parse the file.
For example, the code for several parser directives begins as follows:
n builtin:profile parser directive begins with PARSER=sh
n builtin:krb5.conf parser directive begins with PARSER=ini
n builtin:pamd parser directive begins with PARSER=tabular
n builtin:httpd_conf parser directive begins with PARSER=directive TYPE=apache
Parser Directives for Linux, UNIX, and Mac OS X
When VCM uses custom information types to parse files on Linux and UNIX machines, the directives that
you define for the custom information type must begin with the PARSER directive.
Each directive is separated by a delimiter, which is typically a space. In some cases, a space is not allowed.
View the Parser Directives for Linux, UNIX, and Mac OS X.
Parser Directive
Type
Parser Directive Mandatory
Description
SeparateDirective TYPEID Directive Yes Retrieves the unique identifier
for the custom information
type. This directive is not
specified with the other
directives. The TYPEID directive
should contain only alphabetic
and numeric characters, and no
white space.
General Directives
COMMENTSTRING (Optional) Sets the regular
expression used to identify lines
that are comments. You can
specify multiple regular
expressions separated by the /
character. This regular
expression is used to match
blank lines, invalid data, and
comments. You encode white
space as “[[:blank:]]”.
EXTPATH Path to the file being parsed.
Typically not specified.
vRealize Configuration Manager Administration Guide
140
VMware, Inc.