Users Guide

Actions Portlet | Actions and Adaptive CLI
OMNM 6.5.3 User Guide 577
Parse Expression—
Enter a regular expression for Parse Expression and the Parse Algorithm
(Extract or Match) used when evaluating the device output on a given script execution.
OpenManage Network Manager matches the regular expression for sub-strings, so no need to
provide a leading and trailing “match all” regular expression. (.*).
See
Regular Expressions on page 508 for more information about what is these expressions can do.
You can also click the icon in the upper right corner to test the expression. See
Testing Regular
Expressions
on page 605.
Click
Apply to accept your edits, or Cancel to abandon them. Click Add new attribute extraction to
add more such patterns to your script.
Attribute Appearance and Validation
Invalid schema attribute names appear in the script in red italics. This indicates that you cannot
use such attributes in the script.
Valid attribute names contain alphanumeric characters and underscore (_). They must begin with
either an underscore or a letter [A-Za-z].
All blank space characters in the schema attribute name are converted to underscore (_) by default.
A schema attribute name that is invalid in Adaptive CLI may still be valid in other entities, so you
can specify them in the schema but they are not usable by Adaptive CLI.
Click
Apply to accept your edits for the script, or Cancel to abandon them.
Config File Template Generation
This feature lets you create configuration file templates with the Config File Generation Action.
Like other Actions, you can associate these with a particular type of device in the initial panel of the
editor.
You can use the
Adaptive CLI Script Language Syntax within the configuration template you
create. Optionally you can add two lines concealed in the generated script at the beginning of the
file you create in the
Scripts editor that determine some features of the configuration file itself:
filename=[myfilename] ; This is a sample comment
label=[mylabel]
You can also separate these from comments with a semicolon.
You cannot enter encrypted passwords in a config file template if it contains an attribute delimiter
or optional attribute tag. You can however create string variables as you would for other scripts, and
enter special characters when prompted for that variable as you execute the Action.
These specifications appear in the
Preview and Result screens, but do not appear in the final
configuration file produced.
filename determines how to name the generated configuration file,
and
label applies the designated label, or creates a new label and applies it if it does not yet exist.
When you
Execute this action, it requires you to select a target device, which can either be a
database entry generated by right-clicking in the Managed Resources portlet (select
New and a
device type), or an actual discovered device.