Parse command output
- UpdatedAug 3, 2023
- 5 minutes to read
- Vancouver
- Service Mapping
As part of creating or modifying a discovery pattern, you can use the Parse command output operation to extract information from the command output and to save the operation result in a variable. You can also save the whole of command output as a variable.
Before you begin
Role required: pd_admin
Navigate to the relevant pattern step:
- Select the relevant pattern step or click
to add a step.
Basic knowledge of programming is desirable.
Procedure
Example
In this example, the Tibco parser script contained in the $TibcoParser variable runs on the target host. The parsing method is delimited text with the ‘=‘ delimiter. The result of the parsing is the path to the directory containing all configuration files for Tibco Business Works and Tibco Business Works Process. This step creates a temporary variable to hold the result of the parsing.

What to do next
- Continue editing the pattern by adding a new step and defining its operation or
- Finalize the pattern.
Related Content
- Enter values and variables in patterns
There are several ways to enter values in Pattern Designer. You can use the following types of values in patterns: strings, variables, concatenated variables, and eval() functions. Do not use GlideRecords in patterns.
- Activate pattern Debug mode
Working in Debug mode, Pattern Designer performs all operations as you configure them. It allows you to see results immediately.
- Make a step conditional
If necessary, create a precondition that defines how Discovery and Service Mapping execute a pattern step.
- Pattern variables
You use variables in discovery patterns to refer to parameters or attributes of the CI that the pattern discovers.