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.
Words and Phrases
| 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. |
Using Boolean Operators
| 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 |
|
Queries for Push
For the push feature, the integration uses a collection of queries to gather CI attribute information from Universal CMDB and send it to the Service Manager system.
To access the out-of-the-box data push queries, navigate to Modeling > Modeling Studio, select Queries for Resource Type, and then navigate to the Root > Integration > SM Sync > 9.xx folder.
If you want to change what CI/Relationship types or attributes are part of the integration, you must also edit the integration queries to support your updated CI/CI Relationship types and attributes.
| Query name | Description |
|---|---|
| SM Running Software Push | This query gathers CI attributes from Running Software CIs. |
| SM Business Service Push | This query gathers CI attributes from business service CIs. |
| SM Business Service Relations Push |
This query gathers relationships between the following components:
The query includes compound relationships because the relationships can extend through a group. |
| SM Computer Push |
This query gathers CI attributes from the node CI type with NodeRole containing “desktop”, “server”, “virtualized_system” or not set. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Switch Push |
This query gathers CI attributes from the node CI type with NodeRole containing “atm_switch”, “frame_relay_switch”, or “lan_switch”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Storage Push |
This query gathers CI attributes from the node CI type with NodeRole containing “san_switch”, “san_gateway”, “san_router” or exact CI type equal to “storage Array”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Net Printer Push |
This query gathers CI attributes from the node CI type with NodeRole containing “printer”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Mainframe Push |
This query gathers CI attributes from the node CI type with exact CI type equal to “Mainframe Logical Partition”, or “Mainframe CPC”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Mobile Device Push |
This query gathers CI attributes from the node CI type with NodeRole containing “pda_handheld”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Network Component Push |
This query gathers CI attributes from the node CI type with NodeRole containing “router”, “adsl_modem”, “appletalk_gateway”, “bandwith_manager”, “cable_model”, “csu_dsu”, “ethernet”, “fddi”, “firewall”, “hub”, “kvm_switch”, “load_balancer”, “multicast_enabled_router”, “nat_router”, “token_ring”, “undefined_network_component”, “voice_gateway”, “voice_switch”, or “vpn_gateway”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, and Location. |
| SM Cluster Push |
This query gathers CI attributes from the node CI type with exact CI type equal to “ClusterResourceGroup”. It also gathers related CI attributes from the following CI types through containers and links: IPAddress, Interface, CPU, FileSystem, DiskDevice, Location, and Cluster. |
| SM Node Relations Push |
This query gathers relationships between the following components:
The root class of the relationship is composition. |
| SM CRG Relations Push |
This query gathers relationships between the following components: Node and Cluster Resource Group CIs. The query includes compound relationships because the relationships can extend through a group. |
| SM Layer2 Topology Relations Push |
This query gathers relationships between the following components: Two or more nodes. The query includes compound relationships because the relationships can extend through a group. |
| SM Local Printer Push |
This query gathers CI attributes from printer CIs. It also gathers related CI attributes from the Node CI type. |
| SM ASM Relations Push |
This query gathers ASM discovered consumer-provider relationships that point from a Business Element CI to a Running Software CI. Note This query does not support consumer-provider relationships between a Business Element CI and a Cluster CI. Note To work correctly, this query requires the ASM Enhanced package to be deployed in UCMDB. This package is already included in UCMDB Content Pack (CP) 17. |
