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 the SOM Integration
This section contains useful information for troubleshooting the SOM-UCMDB Integration.
-
Log files
-
Integration errors and exceptions are logged in the
RemoteProcesses.log
file, which is located in the following directory:<DataFlowProbeInstallDir>\runtime\log
The default
<DataFlowProbeInstallDir>
is<Drive>:\UCMDB\DataFlowProbe
. -
You can also view the log information from the UCMDB console. To view the log for an integration point, in the Integration Studio, select an integration point. In the integration jobs list, right click a job, and then click View Communication Log.
-
-
Differences in identifiers
The data type of the FC port identifiers and the storage pool identifiers differs between SOM and UCMDB. For this reason, the SOM IDs cannot be stored directly in the UCMDB database.
The integration assigns a new identifier to each FC port and each storage pool. The integration maintains a mapping file of the new UCMDB IDs to the existing SOM IDs. This mapping file must be present on the UCMDB server for CI reconciliation to occur during the SOM data collection cycle.
The mapping file is maintained in the following location:
<DataFlowProbeInstallDir>\runtime\probeManager\
discoveryResources\som\cache
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: