I need advise on how Consumer application of our MdM-CDI eco-system should use our multiple Client KEY.
I our Mdm-CDI project we are implementing a Coexistance Pattern with Publish&Subscribe. Two systems, SAP-CRM and a legacy MainFrame, will be available to users in read&update mode and will be synchronized in near-realtime for all Client data information.
We have a Web Service that gives access to a Golden Record view (G.R.) of the Client Data, this data when through a process of survivorship, link/unlink, etc
When there is a match between a Client in SAP and the MainFrame, the merged data in the G.R. will includes the SAP-KEY, the MainFrame-KEY and a newly created GR KEY, that we call our Enteprise-KEY.
I am puzzled with this:
1. If other system outside the MdM ecosystem uses the Enteprise-Key, then when there is a Client Match/Unmatch ‘event’, they have to deal with this complexity and the side effects.
2. In the other hands, if they use any of the original system Keys (SAP or MainFrame) then, they will have to use a separate ‘Cross Reference’ service to convert from one system key to another.
I would like to know how people exposed Client Key to other systems and how they deal with the complexity of a Match/Unmatch Events on all system in the enterprise.
Any feedback on this matter will be helpful.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2012-04-01T14:53:40Z by SystemAdmin
Pinned topic Guidelines for dealing with Match/Unmatch on client Data.
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-04-01T14:53:40Z at 2012-04-01T14:53:40Z by SystemAdmin
SystemAdmin 110000D4XK345 PostsACCEPTED ANSWER
Re: Guidelines for dealing with Match/Unmatch on client Data.2012-04-01T14:53:40Z in response to TitoTremblayHi,
It depends on whether the plan is really circulated an enterprise master across the Organization.
If so then you would not want circulate the keys from other client systems and slowly try to dry them out.
You can try Created a GR Key (which doesn't change) and maintain cross ref in your system for match /UnMatch MDM keys generated, but with appropriate maintenance.Obviously you would need a system of cross system if you within your MDM. Any how technically you would have to have a system of cross ref.