1.1.1 Inbound Application Integration
This topic describes the inbound application integration, EJB based synchronous deployment pattern, Web services based synchronous deployment pattern, HTTP servlet based synchronous deployment pattern, and MDB based asynchronous deployment pattern.
Oracle Banking Treasury Management 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 Treasury Management and the external systems will be in the form of XML messages. These XML messages are defined in OBTR in the form of XML Schema Documents (XSD) and are referred to as ‘OBTR formats’.
For more information on OBTR formats refer the Message Formats chapter in this User Manual.
OBTR Inbound Application Integration Gateway uses the Synchronous and Asynchronous Deployment Pattern for addressing the integration needs.
The Synchronous Deployment Pattern is classified into the following:
- Oracle Banking Treasury Management EJB Based Synchronous Inbound Application Integration Deployment Pattern.
- Oracle Banking Treasury Management Web Services Based Synchronous Inbound Application Integration Deployment Pattern.
- Oracle Banking Treasury Management HTTP Servlet Based Synchronous Inbound Application Integration Deployment Pattern.
Asynchronous Deployment Pattern is:
- Oracle Banking Treasury Management MDB Based Asynchronous Inbound Application Integration Deployment Patten.
This topic has the following sub-topics: