1.1 Gateway Functions - An Overview

Integration of different applications and solutions is a key area in today’s systems. A variety of specialized applications deployed on disparate platforms and using different infrastructure need to be able to communicate and integrate seamlessly with Oracle Banking Treasury Management in order to exchange data. The Oracle Banking Treasury Management Integration Gateway (referred to as ‘Gateway’ in the rest of the document) will cater to these integration needs.

The integration needs supported by the Gateway can be broadly categorized from the perspective of the Gateway as follows:

• Inbound application integration – used when any external system needs to add, modify or query information within Oracle Banking Treasury Management.

• Outbound application integration – used when any external system needs to be notified of the various events that occur within Oracle Banking Treasury Management.

This topic has the following sub-topics:

• 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.
• Outbound Application Integration
  This topic describes the outbound application integration.
• Responsibilities of Integration Gateway
  This topic describes the primary responsibilities of Oracle Banking Treasury Management Integration Gateway .
• Deployment of Oracle Banking Treasury Management Integration Gateway
  This topic describes the deployment of Oracle Banking Treasury Management Integration Gateway.
• Deployment Patterns for Application Integration
  This topic describes the deployment patterns for application integration.