Troubleshooting
Problem
IBM MDM Publisher can encounter issues connecting to the MDM ongoing synchronization server if the node changes.
During installation of the MDM ongoing synchronization server, you provide the fully qualified domain name (FQDN). When MDM Publisher is connecting to the ongoing synchronization server, it uses the same FQDN to connect and certificate verification happens on the same FQDN.
However, a problem arises if the ongoing synchronization pod gets deployed on a different node.
For example:
- During installation, the FQDN is defined as workernode1.example.ibm.com.
- During deployment or when the pod is restarted, the ongoing synchronization pod gets deployed to workernode2.example.ibm.com.
- If you provide workernode2.example.ibm.com in the MDM Publisher endpoint, then the service call will fail during certification validation.
- If you provide workernode1.example.ibm.com in the MDM Publisher endpoint, then the service call will fail due to an invalid host.
Resolving The Problem
To resolve this issue:
- During installation of the MDM ongoing synchronization server, provide any node as the FQDN.
- Run the following command to create a route for the service:
oc expose svc/jetty-client-server --hostname=FQDN -n mdm-ongoing - When defining the MDM ongoing synchronization server in the MDM Publisher configuration, use the route name and svc port instead of the FQDN.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"ARM Category":[{"code":"a8m3p000000LPMoAAO","label":"Product-Related->Publisher"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0.0"}]
Was this topic helpful?
Document Information
Modified date:
27 April 2022
UID
ibm16479483