Page Comparison

This document provides MDM developers the background needed to publish new notification event types to the JMS message broker so that clients can subscribe to topics and receive real-time updates to MDM events. In JMS, a topic implements publish and subscribe semantics. When you publish a message it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. Only subscribers who had an active subscription at the time the broker receives the message will get a copy of the message.

...

This notification flow describes the interaction between the core YOUnite MDM service, the JMS service and client that subscribe to YOUnite MDM events (e.g. the YOUnite UI).  This notification flow is separate from the YOUnite MDM Router/Adaptor flow that will be published in a separate document.

Image RemovedImage Added

Notification Payloads

...

1. Add the new notification topic name  to the topic enum in: open-mdm/src/main/resources/raml/schemas/topicPref.json. This is a RAML file so the source needs to be built for the change to take effect.
   
   
2. Typically the notification is generated triggered at the resource layer (e.g. impl.resource/DomainsResource.java) after the service layer has successfully completed the event. Use the static method createEvent() in the NotificationService class.
   

   NotificationService.createEvent(Enum EventType, String message, Map<String, String> map)

   ;

   Trigger a notification of a given event type.  
   key
   value
   uuid
   Zone uuid of target resource
   name
   Zone display name of target resource
   description
   Description of event
   date
   Timestamp of when event occurred (TBD)
   
   
   

3. 
   

4. The notification deliver scope y for an event by default is ALL but you can override this by TBD:

   
   

   1. 
      

...