How to Check the Population Log File

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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

You can set the Development adapter log level to DEBUG to check the incoming CI XML file of Service Manager, and the XSLT-transformed XML file.

Tip You are recommended to enable the Development Mode for the integration point so that the above-mentioned two XML files are in a good format.

To set the adapter log level to DEBUG:

Navigate to the <UCMDB installation folder>\DataFlowProbe\conf\log\fcmdb.properties file. For example: C:\UCMDB\DataFlowProbe\conf\log\fcmdb.properties

Open the fcmdb.properties configuration file in a text editor.

Update the log4j.category.fcmdb.adapters log level to DEBUG:

Save the file.

Wait a while for the change to take effect.

To enable the Development Mode of the integration point:

To check the population log file:

Navigate to the <UCMDB installation folder>\DataFlowProbe\runtime\log\fcmdb.adapters.<integration_point_name>.log file. For example: C:\UCMDB\DataFlowProbe\runtime\log\fcmdb.adapters.SM Integration.log

Open the log file in a text editor.

Search for text strings Source SM CI XML, Transformed XML, Source tree XML for ID Pushback, Transformed XML for ID Pushback and Response message from SM For ID Pushback. The log looks like the following: