1.1 Inbound Application Integration

This topic describes the inbound application integration.

Inbound Application Integration

Oracle Flexcube Investor Servicing 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 Investor Servicing and the external systems will be in the form of XML messages. These XML messages are defined in FCIS in the form of XML Schema Documents (XSD) and are referred to as FCIS formats.

FCIS 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 Investor Servicing EJB Based Synchronous Inbound Application Integration Deployment Pattern
  • Oracle Flexcube Investor Servicing Web Services Based Synchronous Inbound Application Integration Deployment Pattern
  • Oracle Flexcube Investor Servicing HTTP Servlet Based Synchronous Inbound Application Integration Deployment Pattern
The Asynchronous Deployment Pattern is:
  • Oracle Flexcube Investor Servicing MDB Based Asynchronous Inbound Application Integration Deployment Patten

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 Flexcube Investor Servicing is EJB literate, i.e., the external system is capable of interacting with Oracle Flexcube Investor Servicing based upon the EJB interface. In this deployment pattern, the external system will use the RMI/IIOP protocol to communicate with the Oracle Flexcube Investor Servicing EJB.

In this deployment pattern the EJB displayed by Oracle Flexcube Investor Servicing will be a stateless session bean. The actual request will be in the form of an XML message. After the necessary processing is done in Oracle Flexcube Investor Servicing based on the request, the response is returned to the external system as an XML message. The transaction control for the processing will stay with the Oracle Flexcube Investor Servicing 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 Flexcube Investor Servicing wants to connect using standards-based, interoperable web services.

This deployment pattern is especially applicable to systems which meet the following broad guidelines:
  • Systems that are not EJB literate, i.e., such systems are not capable of establishing connections with Oracle Flexcube Investor Servicing based upon the EJB interface; and/or
  • Systems that prefer to use a standards-based approach

In this deployment pattern, the external system will use the SOAP (Simple Object Access Protocol) messages to communicate to the Oracle Flexcube Investor Servicing web services.

The services displayed by Oracle Flexcube Investor Servicing are of a message based style, i.e., the actual request will be in the form of an XML message, but the request will be a payload within the SOAP message. After the necessary processing is done in Oracle Flexcube Investor Servicing based on the request, the response is returned to the external system as an XML message which will be a payload within the response SOAP message. The transaction control for the processing will stay with the Oracle Flexcube Investor Servicing.

HTTP Servlet Based Synchronous Deployment Pattern

The HTTP servlet deployment pattern will be used in integration scenarios where the external system connecting toOracle Flexcube Investor Servicing wants to connect to Oracle Flexcube Investor Servicing using simple HTTP messages.

This is especially applicable to systems such as the following:
  • Systems that are not EJB literate, i.e., are not capable establishing a connections withOracle Flexcube Investor Servicing based upon the EJB interface; and/or
  • Systems that prefer to use a simple http message based approach without wanting to use SOAP as the standard

In this deployment pattern, the external system will make an HTTP request to the Oracle Flexcube Investor Servicing servlet.

For this deployment pattern, Oracle Flexcube Investor Servicing will display a single servlet. The actual request will be in the form of an XML message. This XML message is embedded into the body of the HTTP request sent to the Oracle Flexcube Investor Servicing servlet. After the necessary processing is done in Oracle Flexcube Investor Servicing based on the request, the response is returned to the external system as an XML message which is once again embedded within the body of the response HTTP message. The transaction control for the processing will stay with the Oracle Flexcube Investor Servicing.

MDB Based Asynchronous Deployment Pattern

The MDB deployment pattern is used in integration scenarios where the external system connecting to Oracle Flexcube Investor Servicing wants to connect to Oracle Flexcube Investor Servicing using JMS queues.

This is especially applicable to systems such as the following:
  • Systems that prefer to use JMS queues based approach without wanting to wait for the reply

Here external system sends messages in XML format to request queue on which an MDB is listening. When a message arrives on the queue, it is picked up for processing. After the necessary processing is done in Oracle Flexcube Investor Servicing, based on the request, the response is sent to the response queue as an XML message.

Parent topic: Gateway Functions - An Overview