Oracle Banking Trade Finance Inbound Application Gateway provides XML based interfaces thus enhancing the need to communicate and integrate with the external systems. The data exchanged between Oracle Banking Trade Finance and the external systems will be in the form of XML messages. These XML messages are defined in OBTF in the form of XML Schema Documents (XSD) and are referred to as ‘OBTF formats’

For more information on OBTF formats refer the Message Formats chapter in this User Manual.

OBTF Inbound Application Integration Gateway uses the Synchronous and Asynchronous Deployment Pattern for addressing the integration needs.

• EJB Based Synchronous Deployment Pattern
  The Enterprise Java Beans (EJB) deployment pattern will be used in integration scenarios where the external system connecting to Oracle Banking Trade Finance is ‘EJB literate’, i.e., the external system is capable of interacting with Oracle Banking Trade Finance based upon the EJB interface. In this deployment pattern, the external system will use the RMI/IIOP protocol to communicate with the Oracle Banking Trade Finance EJB.
• Web Services Based Synchronous Deployment Pattern
  The web services deployment pattern will be used in integration scenarios where the external system connecting to Oracle Banking Trade Finance wants to connect using standards- based, inter- operable web services.
• HTTP Servlet Based Synchronous Deployment Pattern
  The HTTP servlet deployment pattern will be used in integration scenarios where the external system connecting to Oracle Banking Trade Finance wants to connect to Oracle Banking Trade Finance using simple HTTP messages.
• MDB Based Asynchronous Deployment Pattern
  The MDB deployment pattern is used in integration scenarios where the external system connecting to Oracle Banking Trade Finance wants to connect to Oracle Banking Trade Finance using JMS queues.