• 1 reply
  • Latest Post - ‏2013-10-28T17:24:25Z by SJH
1 Post

Pinned topic Hybrid MDM transactions (v11)

‏2013-09-11T13:33:01Z | mdm-migration

From IBM documentation it appears that Hybrid MDM has only the following transactions:


A. Pure HMDM transactions: These are getPartyByEntityId and persistEntity.

B. Physical MDM transactions which can be used from HMDM: These are getParty, getPartyByAdminSysKey, getPerson, getOrganization.



  1. What happened to all the search transactions (e.g. searchPerson)? How do I search in an HMDM installation?
  2. I am assuming the persistEntity transaction is sufficiently flexible to encompass the functions of all the standard update functions (e.g. addPartyAlert). Is this correct?


PS. I am new to the concepts of hybrid and virtual MDM.

  • SJH
    5 Posts

    Re: Hybrid MDM transactions (v11)


    There are hundreds of physical MDM services/transactions available for use in a hybrid MDM solution.

    The ability to execute a physical MDM transaction (more correctly modify an object in pMDM)  is limited only by its data ownership definition in a hybrid MDM solution.  That is, if the choice has been made to manage an attribute virtually in vMDM (source systems are the system of record), you may not update that attribute in pMDM because the transactional hub is not the system of record for this information.  Anything mastered centrally may be added/updated using existing pMDM APIs.  Data ownership is defined when you construct the mapping between what attributes you want to manage in virtual MDM, but persist into physical MDM to create the single profile that centrally managed attributes will append to.  Anything in that mapping cannot be updated in physical MDM directly - changes are fed through virtual MDM as it is notified of changes made to any of these attributes in the participating source systems.
    The hybrid-enabled transactions you mentioned above (getParty, getPerson, getOrganization, getPartyByAdminSysKey)  facilitate the movement and retrieval of information that is being stored in both physical and virtual MDM.  All other physical MDM services continue to be available, however restrictions are imposed on physical MDM services only when the data ownership of an attribute has been defined as "virtually managed" -- not centrally managed.  Again as mentioned earlier, any information being pushed from virtual to physical is not centrally managed so these objects can't be updated using physical MDM transactions today and we have a check in place that prevents those services from executing.  This is defined at design time in the workbench when the virtual/physical mapping is defined for the project.


    What happened to search transactions?  How do you search in hybrid MDM solution? 

    Answer:  The search APIs remain as they always have.  Generally, using the virtual MDM search API would be used in the hybrid deployment as virtual MDM is managing the probabilistic searching/matching capabilities in that deployment style.


    2.  persistEntity will handle the standard update functions for objects listed in the transaction reference guide here: