Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

CMS UI2018.08

Attributes Assignment Editor Dialog Box

Enables you to define a regular expression that discovers specific running software according to a CIT's attribute value.

To access	In the Software Identification Rule Editor dialog box, click .
Relevant tasks	How to Discover Running Software – Scenario
See also	Software Identification Rule Editor Dialog Box

User interface elements are described below:

UI Element (A–Z) Description

UI Element (A–Z)	Description
Attribute assignments for Type	Enables you to manage rules that discover a CIT according to an attribute. The attribute is defined according to a regular expression. //. Enable you to add/edit/remove an attribute assignment. Name. Choose from the list of attributes of the CIT selected in the editor. This attribute name is replaced by the value found by the regular expression. To find an attribute, start typing the name. Type. The type of operation defined for the attribute, for example, Boolean, string, date, and so on. Value. The value that replaces the name in the Rule ID field in the Parse Rule Editor dialog box (see Parsing Rules below). Use the following syntax for the value: `${<rule ID name>(<group number>)}` For example, ${DB_SID(1)} means that DFM should search for the Rule ID with the name DB_SID and retrieve its regular expression. DFM should then retrieve the code for the first group (1). For example, in the regular expression .+\s+(\w+)$, the first group is (\w+)$, that is, a word or words that appear at the end of the line.
Parsing Rules	Enables you to manage parsing rules that match attribute to process-related information. Note Only users with a knowledge of regular expressions should make changes to a parse rule. //. Enable you to add/edit/remove a parsing rule. Rule ID. The name of the rule. The Rule ID must be unique. It is needed to identify the rule in the Attributes Assignment Editor pane. Process Attribute. The rule is invoked on the selected process-related attribute. Regular Expression. Enables you to create a dynamic expression that finds at least one process that defines this running software. The regular expression is invoked on the value in the Process Attribute field. For example, a command line process includes the following regular expression: .+\s+(\w+)$ This expression searches for any character, followed by a space or spaces, followed by a word or words (a-z or A-Z or 0-9) that appear at the end of the line. The following command line matches this regular expression: c:\ora10\bin\oracle.exe UCMDB

Attribute assignments for Type

Enables you to manage rules that discover a CIT according to an attribute. The attribute is defined according to a regular expression.

//. Enable you to add/edit/remove an attribute assignment.
Name. Choose from the list of attributes of the CIT selected in the editor. This attribute name is replaced by the value found by the regular expression. To find an attribute, start typing the name.
Type. The type of operation defined for the attribute, for example, Boolean, string, date, and so on.
Value. The value that replaces the name in the Rule ID field in the Parse Rule Editor dialog box (see Parsing Rules below).

Use the following syntax for the value:

${<rule ID name>(<group number>)}

For example, ${DB_SID(1)} means that DFM should search for the Rule ID with the name DB_SID and retrieve its regular expression.

DFM should then retrieve the code for the first group (1). For example, in the regular expression .+\s+(\w+)$, the first group is (\w+)$, that is, a word or words that appear at the end of the line.

Parsing Rules

Enables you to manage parsing rules that match attribute to process-related information.

Note Only users with a knowledge of regular expressions should make changes to a parse rule.

//. Enable you to add/edit/remove a parsing rule.
Rule ID. The name of the rule. The Rule ID must be unique. It is needed to identify the rule in the Attributes Assignment Editor pane.
Process Attribute. The rule is invoked on the selected process-related attribute.
Regular Expression. Enables you to create a dynamic expression that finds at least one process that defines this running software. The regular expression is invoked on the value in the Process Attribute field.

For example, a command line process includes the following regular expression:

.+\s+(\w+)$

This expression searches for any character, followed by a space or spaces, followed by a word or words (a-z or A-Z or 0-9) that appear at the end of the line.

The following command line matches this regular expression:

c:\ora10\bin\oracle.exe UCMDB

Send Help Center feedback