Table of Contents

Search

  1. Preface
  2. Introduction to Services Integration Framework
  3. Setting Up the SIF SDK
  4. Request and Response Objects
  5. Transactions and Exception Handling
  6. ORS-Specific SIF API
  7. Asynchronous SIF Requests
  8. ORS-Specific JMS Event Messages
  9. Using Security Access Manager
  10. Using Dynamic Data Masking
  11. SIF API Reference
  12. Troubleshooting
  13. Appendix A: Identifiers
  14. Appendix B: Frequently Asked Questions

Services Integration Framework Guide

Services Integration Framework Guide

ORS-Specific JMS Event Messages Overview

ORS-Specific JMS Event Messages Overview

Use the JMS Event Schema Manager tool that is part of the SIF Manager utility in the MDM Hub to generate and deploy ORS-specific JMS event messages for the current ORS. You can use the generated URL or download the XSD file to access the schema file for the JMS event messages. After you generate the schema file, you can configure the message triggers to identify the MDM Hub actions that you want to communicate to external applications and the message queue to publish the XML messages.
You must have at least one secure package to generate an ORS-specific JMS event message schema.
The ORS-specific XSD file uses elements from the common XSD file,
siperian-mrm-events.xsd
. The format of the ORS-specific XSD file name is
<ORS Name>-siperian-mrm-event.xsd
.
The ORS-specific JMS event message schema file contains the following objects for each package:
Object Name
Description
<Package Name>Event
A complex type element that contains the
EventMetadata
and
<Package Name>
element types.
<Package Name>Record
A complex type element that represents a package and its fields and includes the
SipMetadata
element type.
The complex type element resembles the package record structures defined in SIF.
If you have two databases that have the same schema such as
CMX_ORS
, use the unique database display name as the initial logical name instead of the database logical name. Otherwise, the logical name can be duplicated for the JMS events when you initially save the configuration.
If you want to use the legacy XML event message objects, you do not require the ORS-specific JMS event message schema.
For more information about the JMS event messages, see the
Multidomain MDM Configuration Guide
.

0 COMMENTS

We’d like to hear from you!