Make sure your webhook has been configured properly and all the necessary systems, system authentication details, endpoints, mappings, and webhook configuration have been set up.
If everything has been setup correctly, once you've made a change to a record in your application, it will send a webhook to the MDM API's /sync endpoint and sync to other applications.
Viewing the MDM Application
An application user interface for the Master Data Management application has been included with the Package that uses each operation from the API. The user interface was created using Martini Templates. To access the application:
In the Navigator, right-click the file \\master-data-management\code\webpage_templates\Index and click Run. Leave the values in the modal window at their defaults and click Run. The application will open in a tab within Martini.
Experiment with the application by clicking menu items and adding new Companies, Contacts, and Deals.
Implementation Overview
Services:
MdmSubscriberListener Service: When syncing via JMS, the target system's Martini Package should have an MdmSubscriberListener service. This service gets invoked whenever there is a new message in the Mdm Subscriber Topic.
HttpReceiver Service: When starting the syncing process via Webhook, an application sends a webhook to the MDM API's /sync endpoint. From here, the HttpReceiver service gets invoked.
WebhookParser Utility Service: The WebhookParser parses a received Webhook payload to extract the values that need to be published in the MdmJmsQueue using a system's Webhook Configuration.
MdmJmsListener Service: This is the service that gets invoked every time a JMS Queue receives a message from a system.
CDM Mapping Service/MapSystemModelandCDM Service: This service is used to map payloads to and from the Common Data Model (CDM) based on the mappings set up.