Enrichment Manager Overview

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)`

Enrichment rules can be used for several purposes:

Adding new CIs and relationships to the CMDB.

Deleting specific CI instances from the CMDB.

Updating the attribute values of specific CI instances in the CMDB.

Enrichment query nodes and relationships differ from other query nodes and relationships in that they are conceptual deductions that represent real relationships and CIs that cannot be discovered automatically by the discovery process.

Enrichment query nodes and relationships are created as part of a TQL query, whose other TQL query nodes are regular ones, meaning TQL query nodes that already exist in the CMDB. For more information about TQL queries, see Topology Query Language.

The following example displays a regular query node of type Node linked to a Websphere AS Enrichment query node by an Enrichment Composition relationship.

By placing an Enrichment query node within a TQL query context, the query receives data from its attributes, and uses it to insert new information into the CMDB.

When you create Enrichment rules, the following results can occur:

The CMDB is enlarged. Add Enrichment query nodes and relationships that are currently not included in the CMDB.

The following Enrichment rule example displays a regular Windows query node (that already exists in the CMDB) connected to a Log File Enrichment query node by an Enrichment Composition relationship.

This Enrichment rule states that for every Windows CI instance that is found in the CMDB, a new Log File CI instance is created, and linked to the Windows CI with a Composition relationship.

Specific CI instances are deleted from the CMDB . For an example, see How to Define an Enrichment Rule – Scenario.

The values of CI attributes are updated. Use an Enrichment rule to update the attributes of a CI that already exists in the CMDB.

The following Enrichment rule example illustrates that a regular Windows query node (that already exists in the CMDB) has been updated with an Enrichment rule.