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.

Runtime Artefacts

Inflow runtime artefacts are distributed as a zip file with the following naming convention: Inflow-Runtime-Release_Version.zip.

Example: Inflow-Runtime-DEV.0.0-SNAPSHOT.zip

The compressed file contains the following folders:

• scripts

  This folder contains SQLScripts.zip.

• artefact

  This folder contains the deployable artefact Inflow_EE.ear.

• manual

  This folder contains the user guide for inflows.

Database Scripts

The SQLScripts.zip file contains database scripts that are required to create the database tables for inflow to work. These database tables are to be created in the Transact database and they are not controlled by Transact.

The SQL scripts are named with the pattern database_nameScript.sql (example: H2Script.sql) and they must be executed only once.

The following tables are created by these scripts:

• IF_INFLOW_MESSAGE

  The inflow request that needs to be processed is saved in this table.

• IF_INFLOW_MESSAGE_PROCESSED

  This table holds the processed messages and can be purged based on the client requirements. This table makes sure the IF_INFLOW_MESSAGE table holds less data.

• IF_INFLOW_MESSAGE_FAILED

  This table holds the failed messages. These messages can be retried. It is advisable to check this table and purge the messages that cannot be retried.

• IF_INFLOW_DUPLICATE_CHECK

  This table is used in a retry scenario and ensures that the same message is not posted to the IF_INFLOW_MESSAGE table for processing.

Running Database Scripts

To create the Inflow database:

• In H2, run the H2Script.sql script.
• in Oracle Database, run the OracleScript.sql script.
• Microsoft SQL Server, run the SQLServerScript.sql script.
• IBM DB2, run the following scripts:
  1. DB2_IF_INFLOW_MESSAGE.sql
  2. DB2_IF_INFLOW_MESSAGE_PROCESSED.sql
  3. DB2_IF_INFLOW_DUPLICATE_CHECK.sql
  4. DB2_IF_INFLOW_MESSAGE_FAILED.sql

The script are named with the pattern Release_number_Database_nameScript.sql (for example R20.0.0.5_H2Script.sql) and must be run according to the sequence number of the release.

Inflow_EE.ear

This is the archive that has the components that execute the inflow request. This archive contains the following files:

• Inflow_REST.war

  This is a REST-based web service that is responsible to consume the inflow request as string (payload) to stage for processing the request.

• Inflow_Listener.jar

  The Inflow Listener module is used to send inflow IDs of the staged inflow messages to the listener queue.

• Inflow_MDB.jar

  This MDB is used to send the request to INFLOW_EJB to execute an inflow request when a non-ESB solution is used.

• Inflow_STREAM.jar

  Enables the inflow to ingest requests from either Kinesis, Eventhub or Kafka topics when enableInflowStream property is true.

• Inflow_EE.ear

  This ear files needs to be deployed in an application server. The following are the supported application servers:

  • JBoss EAP 7
  • WebLogic 14 C (JDK11)

For more information about the configuration files in this jar file, see the section Configuration files.