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

Asynchronous SIF Requests Overview

Asynchronous SIF Requests Overview

SIF uses a message-driven bean (MDB) on a Java Message Service (JMS) queue to process the asynchronous SIF requests from an external application. JMS queues are embedded message queues that use the JMS providers of the application servers. An embedded message queue uses the Java Naming and Directory Interface (JNDI) name of the connection factory and the queue name to connect with the JMS queue. The application server sets up the JNDI name of the connection factory.
The MDM Hub installer automatically sets up the following components for the specific application server that you use in your environment:
  • Inbound message queue.
    siperian.sif.jms.queue
  • Connection factory.
    siperian.mrm.jms.xaconnectionfactory
You must create an outbound message queue in the application server that has the MDM Hub installed. The MDM Hub processes the asynchronous SIF request and posts the response to the outbound message queue. The MDM Hub does not manage the outbound message queue. The external application retrieves the message from the outbound queue and processes it.
The
siperian.sif.jms.queue
queue name is reserved for the MDM Hub. You cannot use reserved names when you create message queues.

0 COMMENTS

We’d like to hear from you!