Fix Readme
Abstract
IBM InfoSphere MDM for Version 11.6, including installation-related instructions, prerequisites and co-requisites, and a description of the enhancements.
readme file for: IBM InfoSphere Master Data Management Standard and Advanced Editions version 11.6.0.11 interim fix 6
Product/Component Release: 11.6.0.11
Update Name:11.6.0.11-MDM-SAE-IF006
Fix ID: 11.6.0.11-MDM-SAE-IF006
Content
IBM InfoSphere Master Data Management Standard and Advanced Editions v11.6.0.11 interim fix 1 readme
Download location:
http://www-933.ibm.com/support/fixcentral/
Prerequisites and co-requisites:
Before installing this interim fix, you must make sure that you install InfoSphere MDM version 11.6.0.11 Feature Pack 11.
Extract the content of the archive file to a temporary location. For example: temp/11.6.0.11-MDM-SE-AE-IF006
Installation Information:
Installing and configuring the fix for InfoSphere MDM Standard and Advanced Editions:
Contacting IBM Software support
IBM Software Support provides assistance with product defects.
Before you submit your problem to IBM Software Support, ensure that your company has an active IBM software maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have.
Product support can be obtained through the following methods.
Download location:
Use IBM Installation Manager to download and extract the fix pack artifacts.
Alternately, you can download the fix pack artifacts from IBM Fix Central:http://www-933.ibm.com/support/fixcentral/
Select Information Management → InfoSphere Master Data Management → v11.6
| Product/Component Name: | File name: |
| InfoSphere MDM Standard Advanced 11.6.0.11 | 11.6.0.11-MDM-SE-AE-IF006.zip |
Prerequisites and co-requisites:
Before installing this interim fix, you must make sure that you install InfoSphere MDM version 11.6.0.11 Feature Pack 11.
Extract the content of the archive file to a temporary location. For example: temp/11.6.0.11-MDM-SE-AE-IF006
Installation Information:
Installing and configuring the fix for InfoSphere MDM Standard and Advanced Editions:
1) Take a backup of .jar file <MDM_INSTALLATION_PATH>/KafkaProcessor/lib/com.ibm.mdm.kafka.connector.jar
2) Replace the new .jar file at location <MDM_INSTALLATION_PATH>/KafkaProcessor/lib/com.ibm.mdm.kafka.connector.jar
3) Add the following content to Log4j.properties at the end:
log4j.appender.performance=org.apache.log4j.RollingFileAppender
log4j.appender.performance.File=../logs/textsearchstats.log
log4j.appender.performance.layout=org.apache.log4j.PatternLayout
log4j.appender.performance.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %m%n
log4j.appender.performance.MaxFileSize=10MB
log4j.appender.performance.MaxBackupIndex=5
log4j.appender.performance.append=true
log4j.logger.com.ibm.mdm.kafka.graph.elasticsearch.logging=INFO,performance
4) Also in kafkaruntimeForES.properties/kafkaruntime.properties(whichever is used) update following :
message.size=<No of Messages to be processed in kafka at one time>
connection.timeout=<Timeout value to be set while making call to ES>
bypass.exceptions=<Exception to be bypassed and not hang the container. Setting to "ANY" will bypass all the exceptions>
isDirectSyncToES=<This will skip the GET call to ES and will not verify if the record exists in ES or not>
retry.count=<Number of time retry should be performed>
retry.interval=30000 <Interval after which retry should be performed.Value should be in milliseconds>
retry.exceptions=ConnectException <Exceptions on which retry should be performed>
2) Replace the new .jar file at location <MDM_INSTALLATION_PATH>/KafkaProcessor/lib/com.ibm.mdm.kafka.connector.jar
3) Add the following content to Log4j.properties at the end:
log4j.appender.performance=org.apache.log4j.RollingFileAppender
log4j.appender.performance.File=../logs/textsearchstats.log
log4j.appender.performance.layout=org.apache.log4j.PatternLayout
log4j.appender.performance.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %m%n
log4j.appender.performance.MaxFileSize=10MB
log4j.appender.performance.MaxBackupIndex=5
log4j.appender.performance.append=true
log4j.logger.com.ibm.mdm.kafka.graph.elasticsearch.logging=INFO,performance
4) Also in kafkaruntimeForES.properties/kafkaruntime.properties(whichever is used) update following :
message.size=<No of Messages to be processed in kafka at one time>
connection.timeout=<Timeout value to be set while making call to ES>
bypass.exceptions=<Exception to be bypassed and not hang the container. Setting to "ANY" will bypass all the exceptions>
isDirectSyncToES=<This will skip the GET call to ES and will not verify if the record exists in ES or not>
retry.count=<Number of time retry should be performed>
retry.interval=30000 <Interval after which retry should be performed.Value should be in milliseconds>
retry.exceptions=ConnectException <Exceptions on which retry should be performed>
5) Restart stream processor for elastic search
To enable sample batch stream application to export the changed entities, follow these steps:
--------------------------------------------------------------------------------------------------------
a) Copy getPersonBatch.xml and getOrganizationBatch.xml to the folder <MDM_INSTALLATION_PATH>/KafkaProcessor/templates
b) Modify the kafkabatch.properties in the folder <MDM_INSTALLATION_PATH>/KafkaProcessor/properties for the following keys to refer to new request template file.
#Template for getPerson request
Person.template=getPersonBatch.xml
--------------------------------------------------------------------------------------------------------
a) Copy getPersonBatch.xml and getOrganizationBatch.xml to the folder <MDM_INSTALLATION_PATH>/KafkaProcessor/templates
b) Modify the kafkabatch.properties in the folder <MDM_INSTALLATION_PATH>/KafkaProcessor/properties for the following keys to refer to new request template file.
#Template for getPerson request
Person.template=getPersonBatch.xml
#Template for getOrganization request
Organization.template=getOrganizationBatch.xml
c) Replace the file PublisherBatchStreamProcessor.xml in <MDM_INSTALLATION_PATH>/KafkaProcessor/properties
d) Restart stream processor for Sample batch runKafkaBatchStreams.sh if its running.
Organization.template=getOrganizationBatch.xml
c) Replace the file PublisherBatchStreamProcessor.xml in <MDM_INSTALLATION_PATH>/KafkaProcessor/properties
d) Restart stream processor for Sample batch runKafkaBatchStreams.sh if its running.
The following is a list of functional fixes:
| APAR Number: | APAR Description: |
| IT38062 | Pods restarting due to connection Exception when making ES call |
| IT38061 | Allow configuration of encoding instead of requiring UTF-8 |
| IT38063 | Allow configuration of message size |
| IT38315 | Record processing skipped during connection interruptions |
| IT38369 | Batch kafka stream processor fails due to TransformResponseProcessor exception |
Contacting IBM Software support
IBM Software Support provides assistance with product defects.
Before you submit your problem to IBM Software Support, ensure that your company has an active IBM software maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have.
Product support can be obtained through the following methods.
|
|
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"11.6","Edition":"Advanced;Standard","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
27 April 2022
UID
ibm16491123