1.3 HTTP Servlet Based Synchronous Deployment Pattern

This topic describes the HTTP servlet-based synchronous deployment pattern.

The HTTP servlet deployment pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE Universal Banking wants to connect to Oracle FLEXCUBE Universal Banking using simple HTTP messages.

This is especially applicable to systems such as the following:

• The systems that are not EJB literate are not capable of establishing connections with Oracle FLEXCUBE Universal Banking based upon the EJB interface. And/or
• The 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 Universal Banking servlet.

For this deployment pattern, Oracle FLEXCUBE Universal Banking 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 Universal Banking servlet. After the necessary processing is done in Oracle FLEXCUBE Universal Banking 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 Universal Banking.