DronaBlog

Thursday, August 16, 2018

How to enable DEBUG mode match process in Informatica MDM?

Are you facing any issues while running the match process in Informatica MDM? Are you looking for information about how to analyze the issue in the match process? Would you also be interested in knowing how to enable DEBUG mode for match process such as searchMatch API, Match jobs, IDD Extended Search? If so, then this article provides detailed information about it.

Introduction

The match process is one of the critical processes in the MDM hub. Any issue in this process, will impact the business. So to analyze the issue, we need logs in DEBUG mode for the match process. Configure your log4j.xml file to generate a separate match log file. This log file can be used to analyze match issues in the Master Data Management (MDM) Hub and Informatica Data Director (IDD). Match can occur during execution of the searchMatch API, the Match jobs and the IDD Extended Search. 

After making the changes mentioned below in log4j.xml file, it will generate match.log file. It will have details about the matches comparing with each of the match rules separately. It will be helpful to understand the behavior of the match rule configuration. Based on the log file analysis we can fine tune the match rules.  

How to make log4j.xml changes for the match process?

We need to make the configuration changes below in log4j.xml file. This file presents at <Install directory>/hub/cleanse/conf directory.

Add the entry below in the log4j.xml file to generate the  'matchprocess.log' file:

<appender name="MATCH" class="org.apache.log4j.RollingFileAppender">
   <errorHandler class="org.apache.log4j.helpers.OnlyOnceErrorHandler"/>
   <param name="File" value="/data/user/infamdm/hub/cleanse/logs/matchprocess.log"/>
   <param name="Append" value="true"/>
    <param name="MaxFileSize" value="10MB"/>
    <param name="MaxBackupIndex" value="10"/>
    <param name="Threshold" value="DEBUG"/>
    <layout class="org.apache.log4j.PatternLayout">
    <!-- The default pattern: Date Priority [Category] Thread Message -->
     <param name="ConversionPattern" value="[%d{ISO8601}] [%t] [%-5p] %c: %m%n"/>
  </layout>
 </appender>
 <category name="com.siperian.mrm.util" additivity="false">
        <priority value="ON"/>
        <appender-ref ref="MATCH"/>
  </category>
 <category name="com.siperian.mrm.match" additivity="false">
        <priority value="ON"/>
        <appender-ref ref="MATCH"/>
  </category>


The video below provides information about how the match process works in the MDM hub.


No comments:

Post a Comment

Please do not enter any spam link in the comment box.

Revolutionizing Healthcare Delivery with Parachute Health

  In the rapidly evolving landscape of healthcare technology, innovations continually emerge to streamline processes and enhance patient car...