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 |
|
- Typical Error Messages and Solutions
- No Query Configured in smPopConfFile.xml
- Nonexistent XSLT File Name Defined for a Query in smPopConfFile.xml
- No "Retrieve" Type Request Defined for a Query in smPopConfFile.xml
- Wrong Request Name of retrieveKeysQueryName Configured for a Query in smPopConfFile.xml
- Wrong Request Name of retrieveListQueryName Configured for a Query in smPopConfFile.xml
- XSLT File not Well Formed
- Wrong UCMDB Attribute Name in XSLT File
- Wrong Service Manager Field Name in XSLT File
- Wrong Universal CMDB Attribute Data Type in XSLT File
- UCMDB CI Attribute sm_id not Mapped to the Right Service Manager Field in XSLT
XSLT File not Well Formed
Sample configuration
The end tag of “ci” should be </ci>
, however you configured a wrong end tag </ci_wrong>
.
Error message
If you have not yet created your integration point, when you create it an error message similar to the following example will occur in the Universal CMDB studio or the log file, causing the creation to fail.
If you have already created your integration point, but not yet activated it, you can no longer activate it, because when you attempt to activate it you will get a detailed error message in the probe error log file (probe-error.log
), similar to the following example.
If you have created and activated your integration point, you will get a “Failed” status when you run the population job. In addition, from both the population log file (see How to Check the Population Log File) and the Universal CMDB studio (see How to Check the Error Message of a Failed Population Job), you will get an error message similar to the following example.
Solution
Search for text Got SAXException while parsing the XSLT file
to find the name of the problematic XSLT file, and then validate the file in an XML editor (for example, XMLSpy). You can easily find and fix any validation issues.