1. Common Core - Gateway User Guide
  2. Overview of Gateway Functions

1 Overview of Gateway Functions

Introduction

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 infrastructures need to be able to communicate and integrate seamlessly with Oracle FLEXCUBE Universal Banking in order to exchange data. The Oracle FLEXCUBE Universal Banking Integration Gateway (referred to as Gateway in the rest of the document) will cater to these integration needs.

The integration that needs to be 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 FLEXCUBE Universal Banking.
  • Outbound Application Integration - Used when any external system needs to be notified of the various events that occur within Oracle FLEXCUBE Universal Banking.

Inbound Application Integration

Oracle FLEXCUBE Universal Banking Inbound Application Gateway provides XML-based interfaces thus enhancing the need to communicate and integrate with the external systems. The data exchanged between Oracle FLEXCUBE Universal Banking and the external systems will be in the form of XML messages. These XML messages are defined in Oracle FLEXCUBE Universal Banking in the form of XML Schema Documents (XSD) are referred to as FCUBS Formats.

For more information on FCUBS formats refer to the topic unresolvable-reference.html#GUID-36F1A3D6-F558-48B3-902A-7F99C7E3C318.

FCUBS 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 FLEXCUBE Universal Banking EJB Based Synchronous Inbound Application Integration Deployment Pattern
  • Oracle FLEXCUBE Universal Banking Web Services Based Synchronous Inbound Application Integration Deployment Pattern
  • Oracle FLEXCUBE Universal Banking HTTP Servlet Based Synchronous Inbound Application Integration Deployment Pattern
Asynchronous Deployment Pattern is:
  • Oracle FLEXCUBE Universal Banking MDB Based Asynchronous Inbound Application Integration Deployment Patten
This topic contains the following sub-topics:
  1. unresolvable-reference.html#GUID-9F0E1640-9999-4724-BE45-042EC0ECE177
  2. unresolvable-reference.html#GUID-A97EC4E6-CE5F-42C9-80B8-0738B4882F86
  3. unresolvable-reference.html#GUID-DB9D6C27-03F2-4013-87C2-C3ED21D567C5
  4. unresolvable-reference.html#GUID-CF4A0B83-8834-416E-BEC5-8C3E852BC88E

Outbound Application Integration

The Outbound Application Integration is also called the Oracle FLEXCUBE Universal Banking Notify Application Integration layer. This application layer sends out notification messages to the external system whenever events occur in Oracle FLEXCUBE Universal Banking.

The notification messages generated by FCUBS on the occurrence of these events will be XML messages. These XML messages are defined in FCUBS in the form of XML Schema Documents (XSD) and are referred to as FCUBS Formats. For more information on FCUBS formats refer to the topic unresolvable-reference.html#GUID-B316DFB3-DC15-4CE5-A62E-CF8EF6B908A4.

Responsibilities of Integration Gateway

The primary responsibilities of Oracle FLEXCUBE Universal Banking Integration Gateway include the following:
  • Authentication
  • Duplicate recognition
  • Validation
  • Routing
  • Logging of messages

Deployment of Oracle FLEXCUBE Integration Gateway

Message communication - incoming or outgoing from/to an external system in Oracle FLEXCUBE Universal Banking will happen only through an Oracle FLEXCUBE Universal Banking Integration Gateway. Hence, it becomes the first point of contact or last point of contact with the database in message flow. The Oracle FLEXCUBE Universal Banking Integration Gateway can be deployed to support both the distributed and single schema deployments of Oracle FLEXCUBE Universal Banking:
  1. Distributed deployment of Oracle FLEXCUBE Universal Banking – In this situation the database components of the Gateway is deployed as two or more schemas.
    • The messaging schema as part of SMS schema in the SMS and/or HO instance
    • The business schema(s) in the various branch schemas in the branch instance(s)
  2. Single schema deployment of Oracle FLEXCUBE Universal Banking – In this situation the database components of the Gateway (messaging and business) are both deployed as part of the single Oracle FLEXCUBE Universal Banking schema.

Deployment Patterns for Application Integration

Table 1-1 Deployment Patterns for Application Integration

Business Integration Needs Nature of Integration Oracle FLEXCUBE Universal Banking Deployment Pattern Remarks
Inbound Transactions into Oracle FLEXCUBE Universal Banking Synchronous FLEXCUBE UBS EJB Recommended
Inbound Transactions into Oracle FLEXCUBE Universal Banking Synchronous FLEXCUBE UBS HTTP Servlet This can be used if the external system cannot communicate to Oracle FLEXCUBE Universal Banking using EJB.
Inbound Transactions into Oracle FLEXCUBE Universal Banking Synchronous FLEXCUBE UBS Web Services This can be used if the external system chooses to communicate only through Web Services.
Inbound Transactions into Oracle FLEXCUBE Universal Banking Asynchronous FLEXCUBE UBS MDB This can be used if the external system chooses to communicate only through JMS queues.
Inbound Queries into Oracle FLEXCUBE Universal Banking Synchronous FLEXCUBE UBS EJB Recommended
Inbound Queries into Oracle FLEXCUBE Universal Banking Synchronous FLEXCUBE UBS In Servlet This can be used if the external system cannot communicate to Oracle FLEXCUBE Universal Banking using EJB.
Inbound Queries into Oracle FLEXCUBE Universal Banking Synchronous FLEXCUBE UBS Web Services This can be used if the external system chooses to communicate only through Web Services.
Inbound Queries into Oracle FLEXCUBE Universal Banking Asynchronous FLEXCUBE UBS MDB This can be used if the external system chooses to communicate only through JMS queues.
Handoffs from Oracle FLEXCUBE Universal Banking Asynchronous FLEXCUBE UBS Notify Recommended