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 |
|
- Troubleshooting and Limitations – Integrations
- Troubleshooting and Limitations – APM Push Integration
- Troubleshooting and Limitations – Arxscan Arxview Integration
- Troubleshooting and Limitations – Atrium Integration
- Troubleshooting and Limitations – BMC Remedyforce Integration
- Troubleshooting and Limitations – CA CMDB Integration
- Troubleshooting and Limitations – DDMI Integration
- Troubleshooting and Limitations – Federating KPI Data
- Troubleshooting and Limitations – Federating Policy Data
- Troubleshooting and Limitations – Importing Data from External Sources
- Troubleshooting and Limitations – Import From Excel Workbook Discovery
- Troubleshooting and Limitations – Microsoft SCCM/SMS Integration
- Troubleshooting and Limitations – NetApp SANscreen Integration
- Troubleshooting and Limitations – NNMi Integration
- Troubleshooting and Limitations – OneView Pull Integration
- Troubleshooting and Limitations – SMA-X Push Integration
- Troubleshooting and Limitations – ServiceNow Integration
- Troubleshooting and Limitations – ServiceNow Integration Using Enhanced Generic Adapter
- Troubleshooting and Limitations – SE Integration
- Troubleshooting and Limitations – SIM Integration
- Troubleshooting and Limitations – UCMDB to XML Adapter
- Troubleshooting the SOM Integration
Troubleshooting and Limitations – Microsoft SCCM/SMS Integration
-
Queries that are used in population jobs should contain one CI type that is labeled with a Root prefix, or one or more relations that are labeled with a Root prefix.
-
The TQL graph must not have cycles.
-
A query that is used to synchronize relations should have the cardinality 1...* and an OR condition between the relations.
-
The adapter does not support compound relations.
-
Entities that are added in SCCM/SMS are sent as updates to UCMDB by the SMS Adapter during differential population.
-
ID conditions on the integration TQL query are not supported.
-
The TQL graph should contain only CI types and relations that are supported by the SCCM/SMS adapter.
The root node is the main CI that is synchronized; the other nodes are the contained CIs of the main CI. For example, when synchronizing the Node CI Type, that graph node is labeled as Root and the resources are not labeled Root.
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 cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: