PRODUCT - Country Model Bank Development

ATMFRM
WEBSPHERE CONFIGURATION

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2016 Temenos Headquarters SA - all rights reserved.

 Installation Guide

Document History

Version Date Author Status Description

0.1 02 Aug 17 Srisailesan Initial ATMFRM-Configuration

Confidential use

2 Click here to view template history Temenos Confidential

 Installation Guide

Table of Contents

1. About this Document .......................................................................................................... 4

2. Scope ................................................................................................................................. 4
3. System Requirements ........................................................................................................ 4
4. Configuring the System ...................................................................................................... 4
4.1 TOCFEE configuration ............................................................................................ 4
4.1.1 TCS Plugin Configuration .................................................................................... 4
4.1.2 Creation of message-driven bean (tocflistener-ejb.jar) ........................................ 7
4.2 Configuration in TAFJEE_EAR.ear: ........................................................................ 9
4.2.1 TAFJJEE_MDB.jar ............................................................................................... 9
4.2.2 TAFJJEE_EJB.jar .............................................................................................. 10
4.2.3 JMS > Queues ................................................................................................... 12
4.3 JMS Configuration in WebSphere ......................................................................... 14
4.3.1 JMS > Queues ................................................................................................... 14
4.3.2 JMS > Activation Specification ........................................................................... 16
4.3.3 JMS > Queue Connection Factories .................................................................. 18
4.4 Deployments: ......................................................................................................... 19
4.4.1 Additional Settings ............................................................................................. 19
5. Special Instructions (if any) .............................................................................................. 20

Confidential use

3 Click here to view template history Temenos Confidential

 Installation Guide

1. About this Document

This document aims at explaining the installation procedures about the WebSphere
configuration for the ATMFRM

2. Scope

The Scope of the document is to cover the WebSphere configuration.

3. System Requirements
The following are the pre-requisites for installing this package.
 WebSphere 8.0 or above
 R15 TAFJ or above
 TAFJEE_EAR
 TOCFEE_EAR
 isolistener.jar
 atmlogger.jar

4. Configuring the System

4.1 TOCFEE configuration
4.1.1 TCS Plugin Configuration
tocfplugin-ra.rar:
This is the file which contains the tcserver as plug-in. we have to deploy our local listeners
inside this rar file.
Place isolistner.jar file and atmlogger.jar inside tocfee.ear\tocfplugin-ra.rar.

Confidential use

4 Click here to view template history Temenos Confidential

 Installation Guide

Amend the MANIFEST.MF file under tocfee.ear>tocfplugin-ra.rar>META-INF to include the

name “isolistener.jar” and “atmlogger.jar” (without quotes)

Similarly amend the MANIFEST.MF under file tocfee.ear>tocfplugin-

ra.rar>tocfplugin.jar>META-INF to include the name “isolistener.jar” and “atmlogger.jar”
(without quotes)

Amend the tcserver.xml file as shown below which will be available under
tocfee.ear>tocfplugin-ra.rar

Create the Adapters for ATM inside the ADAPTERS tag as shown below.
<ADAPTER id="ATM" type="TOCF" active="true">
<MAX_SESSION>5</MAX_SESSION>
<MIN_SESSION>5</MIN_SESSION>
<TIMEOUT>60</TIMEOUT>
</ADAPTER>
<ADAPTER id="MONITOR" type="TOCF" active="true">
<MAX_SESSION>5</MAX_SESSION>
<MIN_SESSION>5</MIN_SESSION>
<TIMEOUT>60</TIMEOUT>
</ADAPTER>

Confidential use

5 Click here to view template history Temenos Confidential

 Installation Guide

Create the Listeners for ATM inside the LISTENERS tag as shown below.
ATM:
<LISTENER id="ATM" type="isolistener" active="true">
<ADAPTERID>ATM</ADAPTERID>
<PORT>7044</PORT>
<HEADERTYPE>DECIMAL</HEADERTYPE>
<HEADERLENGTH>4</HEADERLENGTH>
<IGNORENEXTHEADERBYTE>0</IGNORENEXTHEADERBYTE>
<CONSTHEADERLEN>0</CONSTHEADERLEN>
Path provided here should be
<BITMAPTYPE>HEXA</BITMAPTYPE> same as path mentioned in the
field LOG.PATH in the
</LISTENER> ATM.PARAMETER>SYSTEM

FILE
<LISTENER id="FILE" type="atmlogger" active="true">
<ADAPTERID>MONITOR</ADAPTERID>
<REQUEST_PATH>D:\Temenos\ModelBank\T24\Env\MB\Data\UD\ATM.LOG</REQUES
T_PATH>
<RESPONSE_PATH>D:\Temenos\ModelBank\T24\Env\MB\Data\UD\ATM.LOG</RESPO
NSE_PATH>
<ERROR_PATH>D:\Temenos\ModelBank\T24\Env\MB\Data\UD\ATM.LOG</ERROR_PA
TH>
<PROPERTY_FILENAME>atmlog.properties</PROPERTY_FILENAME>
</LISTENER>
Note:
Please find the below explanation about additional parameters used in the isolistener and all
parameters are mandatory.

HEADERTYPE – DECIMAL
HEADERLENGTH – 4 (i.e. 0074 represents length of the message in decimal)
IGNORENEXTHEADERBYTE - Here no characters has to be ignored.
Assume that HEADERLENGTH is 8 i.e. 00740000 , Here IGNORENEXTHEADERBYTE is 4.

CONSTHEADERLEN - Here constant header length is 19 (i.e. 1204 120412040000 N)

BITMAP – message bitmap (Here it is a HEXA)

Create atmlog.properties file with the below properties under

IBM\WebSphere\AppServer\profiles\profile name folder

Confidential use

6 Click here to view template history Temenos Confidential

 Installation Guide

4.1.2 Creation of message-driven bean (tocflistener-ejb.jar)

4.1.2.1 Ejb-jar.xml

Edit the ejb-jar.xml present inside tocfee.ear\tocflistener-ejb.jar\META-INF\, as shown below

Copy the tags from <message-driven> to </message-driven> and edit the values as
highlighted below (Provide the appropriate listener name defined in the tcserver.xml)
EJB name can be set as required, but please note that the same ejb-name has to be
specified where is applicable.
<message-driven id="MessageDriven_ATMListenerMDB">
<display-name>ATMListener Bean</display-name>
<ejb-name>ATMListenerMDB</ejb-name>
<ejb-class>com.temenos.tocf.listener.mdb.TOCFListenerMDB</ejb-class>
<messaging-
type>com.temenos.tocf.common.jca.OFSMessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>listener</activation-config-
property-name>
<activation-config-property-value>ATM,FILE</activation-config-
property-value>
</activation-config-property>
</activation-config>
<resource-ref
id="ResourceRef_ATMListenerMDB_jmsQueueConnectionFactory">
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_ATMListenerMDB_t24OFSQueue">
<description>OFS queue</description>
Confidential use

7 Click here to view template history Temenos Confidential

 Installation Guide

<res-ref-name>queue/t24OFSQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_ATMListenerMDB_t24OFSReplyQueue">
<description>OFS reply queue</description>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>

4.1.2.2 Ibm-ejb-jar-bnd.xml

Edit the ibm-ejb-jar-bnd.xmi present inside tocfee.ear\tocflistener-ejb.jar\META-INF\, as

shown below
Copy the tags from <ejbBindings> to </ejbBindings> and edit the values as highlighted below
Apart from the Highlighted values, set the jndi names of connection factory and queues as
created in the web sphere.
Specify the same ejb name which is specified in ejb-jar.xml.
<ejbBindings
xmi:type="com.ibm.ejs.models.base.bindings.ejbbnd:MessageDrivenBeanBi
nding" xmi:id="MessageDrivenBeanBinding_ATMListenerMDB"
activationSpecJndiName=
"jca/t24PluginsResourceAdapter">
<enterpriseBean xmi:type="org.eclipse.jst.j2ee.ejb:MessageDriven"
href="META-INF/ejb-jar.xml#MessageDriven_ATMListenerMDB"/>
<resRefBindings
xmi:id="ResourceRefBinding_ATMListenerMDB_jmsQueueConnectionFactory"
jndiName="jms/t24ATMQueueCxFactory">
<bindingResourceRef href="META-INF/ejb-
jar.xml#ResourceRef_ATMListenerMDB_jmsQueueConnectionFactory"/>
</resRefBindings>
<resRefBindings
xmi:id="ResourceRefBinding_ATMListenerMDB_t24OFSQueue"
jndiName="jms/ATMQueue">
<bindingResourceRef href="META-INF/ejb-
jar.xml#ResourceRef_ATMListenerMDB_t24OFSQueue"/>
</resRefBindings>
<resRefBindings
xmi:id="ResourceRefBinding_ATMListenerMDB_t24OFSReplyQueue"
jndiName="jms/ATMReplyQueue">
<bindingResourceRef href="META-INF/ejb-
jar.xml#ResourceRef_ATMListenerMDB_t24OFSReplyQueue"/>
</resRefBindings>
</ejbBindings>

Confidential use

8 Click here to view template history Temenos Confidential

 Installation Guide

4.2 Configuration in TAFJEE_EAR.ear:

4.2.1 TAFJJEE_MDB.jar

4.2.1.1 Ejb-jar.xml

Edit the ejb-jar.xml present inside TAFJJEE_EAR.ear\TAFJJEE_MDB.jar\META-INF\, as

shown below
Copy the tags from <message-driven> to </message-driven> and edit the values as
highlighted below (if required or if multiple interfaces are available which should use different
environment variable like ofs source etc..),
Apart from the Highlighted values, set the jndi names of queues as created in the web sphere
in <message-destination-link> .
EJB name can be set as required, but please note that the same ejb-name has to be
specified wherever is applicable.
<message-driven>
<display-name>Transacted Listener MDB for ATM</display-name>
<ejb-name>ATMTransactedMDB</ejb-name>
<ejb-class>com.temenos.tafj.mdb.TransactedMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<ejb-local-ref>
<ejb-ref-name>ejb/OFSProcessingBeanLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>com.temenos.tafj.sb.OFSProcessingBeanLocal</local>
<ejb-link>ATMProcessingBean</ejb-link>
</ejb-local-ref>
<resource-ref>
<description>Used to get connections to JMS for OFS queues
</description>
<res-ref-name>jms/TAFJQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<message-destination-ref>
<description>ATM queue</description>
<message-destination-ref-name>jms/ReplyQueue</message-destination-
ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>Produces</message-destination-usage>
<message-destination-link>jms/ATMReplyQueue</message-destination-
link>

Confidential use

9 Click here to view template history Temenos Confidential

 Installation Guide

</message-destination-ref>
</message-driven>

4.2.1.2 Ibm-ejb-jar-bnd.xml
Edit the ibm-ejb-jar-bnd.xml present inside TAFJJEE_EAR.ear\TAFJJEE_MDB.jar\META-
INF\, as shown below
Copy the tags from <message-driven> to </message-driven> and edit the values as
highlighted below (if required or if multiple interfaces are available which should use different
environment variable like ofs source etc..),
Apart from the Highlighted values, set the jndi names of connection factory and queues as
created in the web sphere.
Specify the same ejb name which is specified in ejb-jar.xml.
<message-driven name="ATMTransactedMDB">
<jca-adapter activation-spec-binding-name="jms/ATMMessageMDB"
destination-binding-name="jms/ATMQueue" />
<resource-ref name="jms/TAFJQueueConnectionFactory"
binding-name="jms/t24ConnectionFactory" />
<message-destination-ref binding-name="jms/ATMReplyQueue"
name="jms/ReplyQueue" />
</message-driven>

4.2.2 TAFJJEE_EJB.jar

4.2.2.1 Ejb-jar.xml
Edit the ejb-jar.xml present inside TAFJJEE_EAR.ear\TAFJJEE_T24.jar\META-INF\, as
shown below
Copy the tags from <session> to </session> and edit the values as highlighted below (if
required or if multiple interfaces are available which should use different environment variable
like ofs source etc...),
EJB name can be set as required, but please note that the same ejb-name has to be
specified whichever is applicable.
<session>
<description>TAFJ ATM Bean</description>
<display-name>TAFJ ATM Bean</display-name>
<ejb-name>ATMProcessingBean</ejb-name>

<business-local>com.temenos.tafj.sb.OFSProcessingBeanLocal</business-
local>
<business-
remote>com.temenos.tafj.sb.OFSProcessingBeanRemote</business-remote>

<ejb-class>com.temenos.tafj.sb.OFSProcessingBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>

Confidential use

10 Click here to view template history Temenos Confidential

 Installation Guide

<!-- For tafj session -->

<env-entry>
<description>ATM OFS Source</description>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsSource</env-
entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ATM</env-entry-value>
</env-entry>
<env-entry>
<env-entry-
name>com.temenos.tafj.sb.OFSProcessingBean/ofsTimeout</env-entry-
name>
<env-entry-type>java.lang.Integer</env-entry-type>
<env-entry-value>300</env-entry-value>
</env-entry>
<!-- for T24 purpose -->
<resource-ref>
<description>Used to get connections from T24 jdbc pool</description>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>Used to get connections from jdbc locking
pool</description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>Used to get connections from T24 jdbc RO
pool</description>
<res-ref-name>jdbc/t24RODataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<!-- TEC feature -->
<resource-ref>
<description>Used to get connections to JMS for OFS
queues</description>
<res-ref-name>jms/TopicConnectionFactory</res-ref-name>

Confidential use

11 Click here to view template history Temenos Confidential

 Installation Guide

<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>topic queue</description>
<res-ref-name>jms/tecEventsTopic</res-ref-name>
<res-type>javax.jms.Topic</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>

4.2.2.2 Ibm-ejb-jar-bnd.xml

Edit the ibm-ejb-jar-bnd.xml present inside TAFJJEE_EAR.ear\TAFJJEE_T24.jar\META-INF\,

as shown below
Copy the tags from <session> to </session> and edit the values as highlighted below (if
required or if multiple interfaces are available which should use different environment variable
like ofs source etc..),
Apart from the Highlighted values, set the binding-name as created in the web sphere.
Specify the same ejb name which is specified in ejb-jar.xml
<session name="ATMProcessingBean">
<resource-ref name="jdbc/t24DataSource" binding-
name="jdbc/t24DataSource" />
<resource-ref name="jdbc/t24RODataSource" binding-
name="jdbc/t24RODataSource" />
<resource-ref name="jdbc/t24LockingDataSource"
binding-name="jdbc/t24LockingDataSource" />
<resource-ref name="jms/TopicConnectionFactory"
binding-name="jms/t24ConnectionFactory" />
<resource-ref name="jms/tecEventsTopic" binding-
name="jms/tecEventsTopic" />
</session>

4.2.3 JMS > Queues

 Create a new JMS Queue connection factory using e.g. the 'Default
Messaging Provider'
- NAME: ATM Queue
- JNDI NAME: jms/ATMQueue
- Bus: T24Bus
- Queue name: Create Service Bus Integration destination 
ATMQueue

Confidential use

12 Click here to view template history Temenos Confidential

 Installation Guide

 Create a new JMS Queue connection factory using e.g. the 'Default Messaging Provider'
- NAME: ATM Reply Queue
- JNDI NAME: jms/ATMReplyQueue
- Bus: T24Bus
- Queue name: Create Service Bus Integration destination 
ATMReplyQueue

Confidential use

13 Click here to view template history Temenos Confidential

 Installation Guide

4.3 JMS Configuration in WebSphere

4.3.1 JMS > Queues

 Create a new JMS Queue connection factory using e.g. the 'Default
Messaging Provider'
- NAME: ATM Queue
- JNDI NAME: jms/ATMQueue
- Bus: T24Bus
- Queue name: Create Service Bus Integration destination
ATMQueue

Confidential use

14 Click here to view template history Temenos Confidential

 Installation Guide

 Create a new JMS Queue connection factory using e.g. the 'Default Messaging Provider'
- NAME: ATM Reply Queue
- JNDI NAME: jms/ATMReplyQueue
- Bus: T24Bus
- Queue name: Create Service Bus Integration destination 
ATMReplyQueue

Confidential use

15 Click here to view template history Temenos Confidential

 Installation Guide

4.3.2 JMS > Activation Specification

 Create a new JMS activation specification using e.g. the 'Default Messaging Provider'
- NAME: T24 ATM MDB
- JNDI NAME: jms/ATMMessageMDB
- Destination JNDI Name: jms/ATMQueue

Confidential use

16 Click here to view template history Temenos Confidential

 Installation Guide

Confidential use

17 Click here to view template history Temenos Confidential

 Installation Guide

4.3.3 JMS > Queue Connection Factories

Create a new JMS Queue connection factory using e.g. the 'Default Messaging Provider'
- NAME: ATM Queue CX Factory
- JNDI NAME: jms/t24ATMQueueCXFactory

Confidential use

18 Click here to view template history Temenos Confidential

 Installation Guide

4.4 Deployments:
Deploy the applications TOCFEE_EAR and TAFJEE_EAR as below

4.4.1 Additional Settings

4.4.1.1 Add Shared libraries

Add the TAFJ and T24 shared library to TAFJEE_EAR component as below

Enterprise Applications > TAFJEE_EAR > Shared library references > Shared Library
Mapping

Confidential use

19 Click here to view template history Temenos Confidential

 Installation Guide

4.4.1.2 J2C Activation specfication – TOCFEE_EAR

Set the JNDI name as “jca/t24PluginsResourceAdapter”

5. Special Instructions (if any)

Confidential use

20 Click here to view template history Temenos Confidential