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

Access Protocols

Access Protocols

You can use one of the following access protocols for the SIF request and response interactions:
  • Tightly coupled Java remote procedure calls based on Enterprise JavaBeans (EJB) in a Java development environment.
  • Loosely coupled web services that use SOAP protocol. Use Web Services Description Language (WSDL) to define the request and response XML. The development environment can be Eclipse, Microsoft Visual Studio, or other web service client tools.
  • XML over HTTP protocol, which is similar to web services but without the SOAP envelope.
  • Asynchronous JMS-based messages that use the XML over HTTP protocol.
The access protocol runs on top of the native MDM Hub protocol, which accepts request in the XML or EJB format and returns responses in the same format.
You can use a SiperianClient proxy in a Java development environment to manage the communication protocol for the SIF requests.
The following image shows how SIF processes the request and response interactions:
When you cannot or do not want to use the SiperianClient Java classes, you can use other access protocols to directly interact with SIF. This guide does not include information about how to directly use EJB or JMS protocols. You can use these protocols through SiperianClient if you perform any of the following tasks:
  • Use an appropriately configured
    AsynchronousOptions
    object with a SIF request.
  • Place the request directly onto the
    siperian.sif.jms.queue
    message queue.

0 COMMENTS

We’d like to hear from you!