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

Universal CMDB

More > Configuration Manager > Working with Configuration Manager > Policies > Configuration Manager Topology Policy - Use Case

Configuration Manager Topology Policy - Use Case

This section describes a use case for a topology policy in Configuration Manager.

Background

A trader service owner needs to continually monitor the high-availability and/or resiliency of his service. The service is based on a J2EE Cluster that contains several Web Logic servers. Each server runs on a Windows host.

The service owner has determined that the cluster supporting this configuration requires a minimum of three physical hosts to provide sufficient coverage and responsiveness for the applications running. As a result, it is important to ensure that when changes occur, the proper level of resources is maintained to guarantee that the service continues to function in accordance with its agreed to requirements.

Toward this end, the service owner wants to define a Configuration Manager topology policy that monitors the number of hosts supporting the cluster. The owner would like to see an indication in the event that the number of hosts in the cluster supporting the service is less than three.

The service topology is modeled in a view in UCMDB and there is a corresponding managed view in Configuration Manager. The following image displays the service topology in Configuration Manager.
Create the Condition TQL Query in UCMDB
Open the UCMDB window (click the Launch UCMDB button, and log in).

Navigate to the Modeling Studio. Select Views as the resource in the Resources tab and locate the Trader view. Double-click the view to open it. This view contains the relationships that define the connection between the J2EE domain and the Windows hosts.

The following image displays the relevant portion of the view in UCMDB:

Using the relationship path between the J2EE domain and the Node CI, create a new query consisting of a compound relationship between the J2EE Domain and the host (Node CI).

To create a query containing a compound relationship:
1. Click the New button in the Modeling Studio and select Query.
2. Drag a J2EE Domain CI and a Node CI onto the modeling pane.
3. Select both CIs and add a new compound relationship (using the right-click context menu).
4. Edit the compound link to add the following path elements:
  - J2EE Domain - Composition - J2EE Cluster
  - J2EE Cluster - Membership - J2EE Server
  - J2EE Server - Composition - Windows
5. Edit the Node cardinality to be three at minimum. Right-click the Node CI, select Query Node Properties, select the Cardinality tab and enter 3 in the Min box:
6. When you are finished, save the query.
Define the Topology Policy in Configuration Manager
1. In Configuration Manager, navigate to the Policies module and create a new topology policy.
2. Set the name and description and assign the new policy to the Trader managed view.
3. Under Condition, select the query you have prepared in UCMDB and select positive as the condition type.
4. Save the new policy and preview it.
  
  Note that the new policy indicates a breach on the J2EE Domain if the number of nodes supporting the J2EE Cluster is less than three, as displayed in the following image: