Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Topology Query Language
- Topology Query Language (TQL) Overview
- Creating TQL Queries in the RTSM Managers
- Viewing TQL Query Results
- Compound Relationship
- Join Relationship
- Query Node Conditions
- Complex Type Condition
- Subgraph Definition
- The Use Update Value Policy Qualifier
- How to Define a TQL Query
- How to Add Query Nodes and Relationships to a TQL Query
- How to Define a Compound Relationship – Scenario
- How to Define a Join Relationship – Scenario
- How to Define an Attribute Condition – Scenario
- How to Define a Complex Type Condition - Scenario
- How to Create a Subgraph Definition – Scenario
- Shortcut Menu Options
- Attribute Operator Definitions
- TQL Logs
- Topology Query Language User Interface
- Troubleshooting and Limitations
Viewing TQL Query Results
You view the resulting data in a visual representation in IT Universe Manager. The queries define the structure of the resulting topology map. The view displays only those CIs and relationships that meet the query definition. You can also view the results of a query by clicking the Preview button on the toolbar to open a preview display identical to IT Universe Manager. For more details about IT Universe Manager, see IT Universe Manager.
When you define a TQL query, you define the type of the TQL query in the Type field of the Query Definition Properties dialog box. The following query types are available:
-
View. TQL queries used as the basis for pattern views.
-
Integration. TQL queries used for integrations.
-
Discovery. TQL queries used as the basis for Data Flow Management (DFM) patterns.
-
Template. TQL queries used as the basis for templates.
-
Perspective. TQL queries used as the basis for perspectives.
-
Impact Analysis. TQL queries used as the basis for Impact rules. This is the default type for queries created in Impact Analysis Manager.
-
Enrichment. TQL queries used as the basis for Enrichment rules. This is the default type for queries created in Enrichment Manager.
You cannot change the type of an existing TQL query if it has dependencies (such as views, templates, and so on).
If a query imported though an integration is not assigned a type, it is considered a hidden query and does not appear in the query list in the Modeling Studio. To display hidden queries in the query list, change the setting for hidden queries under General in the User Preferences dialog box. For details, see User Preferences Dialog Box.
You can also set the priority level of a TQL query, which determines how often the query is rerun automatically to include updated information. The following priorities are available:
-
Low. The TQL query is refreshed every 2 minutes.
-
Medium. The TQL query is refreshed every 30 seconds.
-
High. The TQL query is refreshed every 10 seconds.
-
Express. The TQL query is refreshed continuously.
-
Not Active. The TQL query is inactive.
Note The above refresh times are average values.
If you set the priority of a TQL query to Not Active, the query becomes inactive and is not run automatically; however, it can be used for manually building a view.
You can select a base query for a TQL query in the Query Definition Properties dialog box. In this case, the base query is first applied to the entire IT Universe, generating results. The new query is then applied to that subset of the universe, further refining the results. Selecting a base query enables you to filter the query results more finely and generate results more quickly in certain cases.
The base query you select must be both active and persistent for your new query to be active. If the base query is not active and persistent, the new query is automatically assigned a priority of Not Active.
Each TQL query is calculated in a separate thread, taken from a thread pool. If there are many TQL queries being calculated, you can increase the thread pool size to improve performance. Edit the TQL Threads Pool Size setting in the Infrastructure Settings Manager. The pool size can be any integer value between 1 and 64. If no value is entered, the pool size is automatically set to be the number of CPU cores divided by the number of customers (if this number is smaller than 4, it is set to a minimum of 4 threads).
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: