Configuration Files

Before you deploy Inflow_EE.ear, 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.

Configuration Files in Inflow_EE.ear\META-INF

The application.xml file defines the contents of the INFLOW_EE.ear file. The META-INF folder contains application server-specific files too. These configuration files should not be edited.

Configuration Files in Inflow_MDB.jar

The application server-specific configuration file needs to be edited to provide the JNDI name or the binding name for queue, queue connection factory, data source and the locking data source.

InflowMDB Configuration

The default queue that InflowMDB listens to is queue/inflow.

DispatcherMDB Configuration

The default queue that DispatcherMDB listens to is queue/inflowListener.

Configurable sections in ejb-jar.xml

The JNDI names for the resources are provided in the application server configuration file for both Inflow MDB and Dispatcher MDB.

Below are the common properties of InflowMDB and DispatcherMDB. These properties are configured in the application-con.properties file which is located in the inflow service jar.

• runtimeProperties

  This property is used to set the comma-separated runtime properties for the TAFJ session and OFS.SOURCE is the mandatory property for Inflow request.

• superTransaction

  This property is used to configure the transaction boundary and you need to set this property as true for Inflow.

• healthCheckMode

  This property is used to set the MDB to run in health check mode and you need to set this property as false to run the inflow request.

• userId

  This property is used to set the Transact user ID to authenticate in both the application server and Transact. The user should have the PREAUTHENTICATED attribute set and all the necessary permissions to run the required inflow in Transact.

• transactionMode

  This property is used to set the transaction mode for inflow and the default value is CONTAINER.

The following sample image shows common properties for MDB and Listener which are configured in the application-con.properties file.

Configuration Files in Inflow_REST.war

The REST-based web service in inflow reads details about the inflow. All the configuration files in Inflow_Rest.war are available in the WEB-INF directory.

The application server-specific configuration file needs to be edited to provide the JNDI name or the binding name for the queue, queue connection factory, data source and the locking data source.

springrest-servlet.xml

This is the REST service configuration file that has the information to connect to Transact.

The bean definition with the ID t24DataSource is used to provide the JNDI name of the data source that connects to Transact.

<bean id="t24DataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
   <property name="jndiName">
      <value>jdbc/t24DS</value>
   </property>
   <property name="resourceRef">
      <value>true</value>
   </property>
</bean>

The ban definition with the ID readFlow defines the properties to run requests:

• runtimeProperties

  This property is used to set the comma-separated runtime properties for TAFJ sessions. OFS.SOURCE is the mandatory property.

• superTransaction

  This property is used to configure the transaction boundary. For Inflow, this property is set to false as the purpose of this REST-based web service is to read inflow-related information in Transact.

• healthCheckMode

  This property specifies whether the MDB is running in health check mode. To run the inflow request, set this property to false.

• userId

  This property is used to set the Transact user ID that is used to authenticate in the application server and Transact. This user should have the PREAUTHENTICATED attribute set and should have all the necessary permissions to run the required request in Transact.

• transactionMode

  This property is used to set the transaction mode for inflow. The default value is CONTAINER.

  <bean id="readFlow" class="com.temenos.technology.inflow.queue.model.RuntimeProperty" scope="singleton">
     <property name="runtimeProperties">
        <value>OFS_SOURCE=IFPAOFS</value>
     </property>
     <property name="superTransaction">
        <value>false</value>
     </property>
     <property name="healthCheckMode">
        <value>false</value>
     </property>
     <property name="transactionMode">
        <value>CONTAINER</value>
     </property>
     <property name="userId">
        <value>SSOUSER1</value>
     </property>
  </bean>
  

Configuration Files in InflowListener.war

The Inflow Listener module is used to send inflow ids of staged inflow messages to the listener queue. All the configuration files in InflowListener are available in WEB-INF and META-INF folders.

The application server-specific configuration file (jboss-web.xml) needs to be edited to provide the JNDI name or the binding name for the queue, queue connection factory, data source and the locking data source.

The bean definition with the t24DataSource ID is used to provide the JNDI name of the data source that connects to Transact.

<resource-ref>
	<res-ref-name>jdbc/t24DataSource</res-ref-name>
	<res-type>javax.sql.DataSource</res-type>
	<jndi-name>java:/jdbc/t24DS</jndi-name>
</resource-ref>

Spring Beans Configuration

The InflowScheduler bean is used to configure the listener, which listens to the incoming message. It has a scheduled timer task to poll for an incoming message. By default, once every 30 seconds, the Listener listens to the incoming message.

The InflowFailureListener bean is used to configure the options, which are used to retry the failed messages. It has a scheduled timer task configuration to poll for failed messages. By default, once every 30 seconds, the InflowFailureListener retries a message.

A sample image of the Listener scheduler tasks is given below:

The link here shows the sample reference for configuring spring scheduler task.

Configuring app.properties

It is the configuration file, which has properties specific to the following listener spring beans:

• listener
• failureRecoveryListener

A sample of the app.properties configuration file is given below:

The below are the common properties of listener spring beans: