Inflow

Inflow is the Integration Framework component that allows you to send inward messages to Transact at high volumes.

Overview of Inflow

Inflow allows you to carry out business transactions. You can enrich the incoming data either with elements that are already known to Transact or with elements that belong to the same inward data set.

Assumptions and prerequisites

Before you can configure inflow, you need to check that your system meets the inflow system requirements. You also need to configure your environment and carry out a number of pre-configuration tasks.

Inflow requests

There are three types of inflow requests - requests with PW, requests without PW, and generic OFS requests.

Inflow Designer

Inflow Designer is used to publish Inflows to Transact.

Packaging and deploying inflows

The create inflow records in Transact through Inflow Packager you need to produce a package of designs and then deploy it.

Inflow Designer introspection

Inflow Designer allows you to create inflow designs and publish them into Temenos Transact. But, if you want to modify the already existing designs, you must recreate the Inflow Designer project and its corresponding design records and then modify the inflow design according to your needs.

Adding AA to Inflow

Inflow supports incoming messages for non-AA applications and versions. The following steps show how to support AA applications and versions for inflow with and without a PW process.

Imbricated Inflow

In order to use sub-flows, it is necessary to have imbricated (overlapping) inflows. The system supports up to three levels of sub-flows.

Inflow runtime

Inflow runtime is a part of Inflow that you use to post the requests that need to be executed by Transact. This section explains the runtime artefacts and shows how to deploy them. It also shows how to execute an inflow request.

Configuration files

Before you deploy Inflow_EE.ear a, make sure that the connection factory, queue connection factory and the queues are created in the application server and the required modifications are done in the configuration files.

Deploying Inflow_EE.ear

Inflow_EE.ear is the runtime artefact that contains the Inflow_REST.war, Inflow _EJB.jar and Inflow _MDB.jar files. Inflow_EE.ear needs to be deployed in an application server to process the inflow messages posted to a queue.

Executing an Inflow request

You can execute an Inflow request using ESB, JMS queues and REST API. The ESB solution is supported by IIB Adapter.

Inflow response

Inflow is asynchronous, which means that when you post an inflow request, a success or failure response will be written to the processed Inflow table.

Appendix

You may need this reference information when using the software.