1. Customer Hub (UCM) Master Data Management Reference
  2. About Publish and Subscribe Functionality

About Publish and Subscribe Functionality

Publish and Subscribe functionality consists of two parts:

  1. System Registrations view, an administration UI view, where external systems that want to receive customer data updates from Oracle Customer Hub (UCM) are registered (subscribed). Example of the information provided in this view are the connecting information and preferred message format (e.g., SOAP or JSON) from each external system.
  2. UCM Publish/Subscribe Service, a business service that orchestrates and determines the details on how external systems receive customer data updates from Oracle Customer Hub (UCM).

Oracle Customer Hub (UCM) can connect to external systems in two difference modes:

  1. Stand-alone mode: In this mode, UCM publishes the messages directly to the subscribed systems, using the transport information provided during the system registration using point-to-point integration strategy.
  2. Middleware mode: In this mode, Oracle Customer Hub (UCM) is connected to subscribed systems via middleware. Oracle Customer Hub (UCM) publishes only one message to middleware with cross reference information of subscribed systems. Cross-reference information is then used by middleware to broadcast messages to the respective subscribed systems.

Starting with release 26.3, Oracle Customer Hub (UCM) provides support for multiple middleware and publishes the messages in hybrid mode in that, UCM can publish the messages to multiple middleware systems, with cross reference information for its own set of subscribed child systems. In addition, UCM publishes the messages directly to each subscribed stand-alone system.

Relevant Features of Hybrid Mode:

  1. Each external system can connect to UCM either through a middleware or directly as a stand-alone system.
  2. Since this mode supports multiple middleware, each system connecting to UCM through a middleware must specify which parent middleware it belongs to in the System Registration view.
  3. All systems connecting to a middleware, will have the same default Message Type and transport information specified in parent middleware. The Message Type specified in the child system will be ignored.
  4. Middleware systems must connect directly to UCM. In other words, middleware systems cannot be daisy chained.