TAFC R17 on JDK1.8 & JBoss 7.

2 EAP
Technical Approval 1.0 Oct 2019
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

Contents
1 About this Technical Approval ................................................................. 4
1.1 Scope ............................................................................................................................................. 4
1.2 Audience ........................................................................................................................................ 4
1.3 Skills and knowledge ...................................................................................................................... 5
1.4 Legal .............................................................................................................................................. 6
1.5 History ............................................................................................................................................ 6

2 Introduction .............................................................................................. 7
3 Prerequisites and Assumptions ............................................................... 8
3.1 OS Details ...................................................................................................................................... 8
3.2 Software Details ............................................................................................................................. 8
3.2.1 Third Party Software ............................................................................................................... 8
3.2.2 Temenos Software ................................................................................................................. 9
3.3 Sanity Check DB access ................................................................................................................ 9
3.3.1 Connect to the R17 DB using instant client ............................................................................ 9
3.3.2 Test DB connectivity using config.XMLORACLE .................................................................. 10
3.3.3 Accessing T24 classic .......................................................................................................... 10
3.3.4 Accessing BrowserWeb........................................................................................................ 10
3.4 Download EB_BrowserClient from T24 UPDATES ...................................................................... 11

4 TAFC R17 with JDK.18 and JBoss 7.2 EAP .......................................... 13

4.1 Updating the bash_profile ............................................................................................................ 14
4.2 Updating the .profile in bnk.run .................................................................................................... 14
4.3 Link TAFC Library libclntshcore to Instant Client 19c libclntshcore .............................................. 15
4.4 Sanity Check – DB access ........................................................................................................... 15
4.4.1 Connect to the R17 DB using instant client .......................................................................... 15
4.4.2 Test DB connectivity using config.XMLORACLE .................................................................. 16
4.4.3 Accessing T24 classic .......................................................................................................... 16
4.5 Deploying BrowserWeb, TOCFEE and ResourceAdapter on JBoss 7.2 EAP .............................. 17
4.5.1 Configuring the Standalone-full.xml ...................................................................................... 17
4.6 Accessing BrowserWeb 17 .......................................................................................................... 18

5 Deploying the Latest R17 BrowserWeb from T24 UPDATES ............... 21

5.1 Preparing the latest BrowserWeb for deployment ........................................................................ 21
5.2 Accessing BrowserWeb49 ........................................................................................................... 23

6 Technical Approval................................................................................. 25
6.1 Test Environment ......................................................................................................................... 25
6.1.1 Architecture .......................................................................................................................... 25
6.1.2 Hardware specifications ....................................................................................................... 25
6.1.3 Software specifications ......................................................................................................... 26
6.1.4 Testing.................................................................................................................................. 26
6.1.5 T24 transactions using JMeter ............................................................................................. 27
6.1.6 Time taken for data injection ................................................................................................ 28

2
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

6.1.7 Close of Business (COB)...................................................................................................... 28

6.1.8 Browser navigation ............................................................................................................... 29
6.1.9 Conclusion............................................................................................................................ 29

3
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

1 About this Technical Approval

This Technical Approval document explains the necessary software components and
configurations required to run R17 T24-TAFC on JDK 1.8, JBoss 7.2 EAP and Oracle 19C. The
document mainly focuses on the key configuration settings you need to get BrowserWeb
working.

This document does not tell you how to install third-party software. For more information,
see the relevant vendor's documentation.

1.1 Scope
This document covers:

 Software artefacts used to create the R17 TAFC environment.

 Deploying the T24 artefacts and a detailed focus on configuring and deploying the
BrowserWeb.

 Switching from JDK.1.7 to JDK 1.8.

 Switching from JBoss 6.4 EAP to JBoss 7.2 EAP.

 Switching from Oracle 12.2C to Oracle 19.2.

 Technical approval.

This document does not cover:

 Installing Oracle database.

 Installing Oracle instant client.

 Installing TAFC and T24.

1.2 Audience
This document is aimed at those who are interested and involved in deploying R17 TAFC-T24
on JDK 1.8, JBoss 7.2 and with Oracle 19C database.

4
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

1.3 Skills and knowledge

Readers with a basic understanding of the following will find the steps contained in this guide
much easier to follow.

 T24

 TAFC

 JBoss

 Oracle

5
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

1.4 Legal
© Copyright 2019 Temenos Headquarters SA. All rights reserved.

The information in this guide relates to TEMENOSTM information, products and services. It
also includes information, data and keys developed by other parties.

While all reasonable attempts have been made to ensure accuracy, currency and reliability of
the content in this guide, all information is provided "as is".

There is no guarantee as to the completeness, accuracy, timeliness or the results obtained

from the use of this information. No warranty of any kind is given, expressed or implied,
including, but not limited to warranties of performance, merchantability and fitness for a
particular purpose.

In no event will TEMENOS be liable to you or anyone else for any decision made or action
taken in reliance on the information in this document or for any consequential, special or similar
damages, even if advised of the possibility of such damages.

TEMENOS does not accept any responsibility for any errors or omissions, or for the results
obtained from the use of this information. Information obtained from this guide should not be
used as a substitute for consultation with TEMENOS.

References and links to external sites and documentation are provided as a service.
TEMENOS is not endorsing any provider of products or services by facilitating access to these
sites or documentation from this guide.

The content of this guide is protected by copyright and trademark law. Apart from fair dealing
for the purposes of private study, research, criticism or review, as permitted under copyright
law, no part may be reproduced or reused for any commercial purposes whatsoever without the
prior written permission of the copyright owner. All trademarks, logos and other marks shown in
this guide are the property of their respective owners.

1.5 History
Version Date Change Author

1.0 October 2019 First release Kaydee Dzvuke

(Technical signoff: Nanda Badrappan)

6
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

2 Introduction
This document helps you migrate your existing R17 T24/TAFC environment to JDK8, JBoss 7.2
and Oracle 19C It guides you through the process of configuring BrowserWeb and JBoss to
access T24 browser. In this exercise, we created a 2-tier architecture that comprises the
application and database server.

The application tier contains the application server with TAFC and T24. The database tier
contains the database that stores T24 data.

7
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

3 Prerequisites and Assumptions

This chapter describes the technical prerequisites and assumptions for upgrading TAFC R17
on JDK 1.7, JBoss 6.4 and Oracle 12C to JDK 1.8, JBoss 7.2 and Oracle 19C.

3.1 OS Details
RedHat Linux 7.7
Linux-/srv/Temenos/R17/bnk/bnk.run: cat /etc/*release*
NAME="Red Hat Enterprise Linux Server"
VERSION="7.7 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.7"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.7 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.7:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.7
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.7"
Red Hat Enterprise Linux Server release 7.7 (Maipo)
Red Hat Enterprise Linux Server release 7.7 (Maipo)
cpe:/o:redhat:enterprise_linux:7.7:ga:server

Linux-/srv/Temenos/R17/bnk/bnk.run:

3.2 Software Details

The next two sections show the software components that make up our R17 TAFC
environment.

3.2.1 Third Party Software

Component Version

Java Development Kit jdk1.7.0_79

JBoss EAP jboss-eap-6.4

Oracle instant client instant-client 12102

8
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

Oracle Database Oracle Database 12c

3.2.2 Temenos Software

Artefact Description

R17 TAFC runtime R17

R17 T24 R17

R17 Oracle R17

TOCFEE Contains TOCFEE.EAR and the T24

Resource Adapter

R17 BrowserWeb R17 BrowserWeb

3.3 Sanity Check DB access

3.3.1 Connect to the R17 DB using instant client

sqlplus t24/t24@R17AMR19

9
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

3.3.2 Test DB connectivity using config.XMLORACLE

config.XMLORACLE and select 4

3.3.3 Accessing T24 classic

3.3.4 Accessing BrowserWeb

Procedure

To access BrowserWeb, start JBoss and JBASW agent.

jbase_agent –p 21001

$JBOSS_HOME/bin/standalone.sh --server-config=T24.xml -
Djboss.node.name=node1 -b 0.0.0.0 -bmanagement 0.0.0.0

10
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

The relevant details for BrowserWeb are highlighted in the following screenshot.

3.4 Download EB_BrowserClient from T24 UPDATES

Procedure

1. Using the T24 ToolBox, connect to the R17 system and download the System Definition
file (SysDef.xml).

2. Connect to Temenos Customer Support Portal and add the system by uploading the
SysDef.xml file.

3. Go to Systems and select your system.

11
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

4. Select EB_BrowserClient and download it. We will need it later when we move to
JDK8 and JBoss 7.2.

12
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

4 TAFC R17 with JDK.18 and JBoss 7.2

EAP
The main goal for this exercise was to prove that we are able to run TAFC R17 with JDK1.8
and JBoss 7.2 EAP. The following table shows our existing R17 environment and the target
R17 environment software components.

Existing R17 R17 POC Environment

JBoss 6.4 EAP JBoss 7.2 EAP jboss-eap-7.2.0.zip

JDK 1.7 JDK 1.8 jdk-8u112-linux-x64.tar.gz

Oracle 12.2 Oracle 19C Oracle Database 19c Enterprise Edition

Release 19.0.0.0.0 - Production

Oracle Instant Oracle instant client 19C instantclient-sdk-linux.x64-

19.3.0.0.0dbru.zip

The following tasks were carried out on the existing R17 environment:

 Installed JDK 1.8

 Installed JBoss 7.2 EAP

 Installed Oracle DB 19C

 Installed oracle instant client 19c

 Took an R17 oracle dump from Oracle 12c and restored it on Oracle 19c.

13
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

4.1 Updating the bash_profile

The following table shows the updated bash_profile entries

export T24_HOME=/srv/Temenos/R17/bnk/bnk.run
export JBOSS_HOME=/srv/Temenos/3rdParty/AS/jboss-eap-7.2
export JAVA_HOME=/srv/Temenos/3rdParty/Java/jdk1.8.0_112
echo "JAVA_HOME is " $JAVA_HOME
export ORACLE_HOME=/srv/Temenos/instantclient_19_3
export LD_LIBRARY_PATH=/srv/Temenos/instantclient_19_3
export PATH=$PATH:$JAVA_HOME/bin:$ORACLE_HOME
cd $T24_HOME
. ./.profile

4.2 Updating the .profile in bnk.run

You must update the T24 .profile as well. As you have noticed from above, this is
automatically executed upon logging in.

export JAVA_HOME=/srv/Temenos/3rdParty/Java/jdk1.8.0_112
export ORACLE_HOME=/srv/Temenos/instantclient_19_3
export ORACLE_SID=R17AMR19
export TNS_ADMIN=$ORACLE_HOME/network/admin
export ORACLE_LD_LIBRARY_PATH=$ORACLE_HOME

Start a new shell session and verify the new JDK and ORACLE environment variables.

echo $JAVA_HOME

echo $ORACLE_HOME

14
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

4.3 Link TAFC Library libclntshcore to Instant Client 19c

libclntshcore
Procedure

1. Move to TAFC_HOME/lib

cd $TAFC_HOME/lib

2. Make a symbolic link.

ln -s $ORACLE_HOME/libclntsh.so.19.1 libclntshcore.so.12.1

4.4 Sanity Check – DB access

4.4.1 Connect to the R17 DB using instant client

sqlplus t24/t24@R17AMR19

15
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

4.4.2 Test DB connectivity using config.XMLORACLE

config.XMLORACLE

select 4

4.4.3 Accessing T24 classic

16
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

4.5 Deploying BrowserWeb, TOCFEE and ResourceAdapter

on JBoss 7.2 EAP
There are several pre-configuration steps required to prepare the artefacts for the actual
deployment. The following sub-sections cover them all one by one.

4.5.1 Configuring the Standalone-full.xml

In this section, we are going to add the required OFS queues and T24 resource adapter for
BrowserWeb to work.

Procedure

1. First copy and rename the standalone-full.xml in

$JBOSS_HOME/standalone/configuration directory. The file is T24.xml in this
document.

2. Navigate to the <subsystem xmlns="urn:jboss:domain:messaging-

activemq:4.0>

3. Add the following queues just under the <jms-queue name="DLQ"

entries="java:/jms/queue/DLQ"/>

<jms-queue name="ExpiryQueue"
entries="java:/jms/queue/ExpiryQueue"/>
<jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>
<jms-queue name="t24OFSQueue" entries="queue/t24OFSQueue"/>
<jms-queue name="t24OFSReplyQueue"
entries="queue/t24OFSReplyQueue"/>
<jms-queue name="requestQueue" entries="queue/requestQueue"/>
<jms-queue name="responseQueue" entries="queue/responseQueue"/>

4. Navigate to the <subsystem xmlns="urn:jboss:domain:resource-

adapters:5.0"> in T24.xml

5. Edit it to look like the following:

<subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
<resource-adapters>
<resource-adapter id="tocfT24ra-ra.rar">
<archive>tocfT24ra-ra.rar</archive>
<transaction-support>XATransaction</transaction-support>
<connection-definitions>
<connection-definition class-
name="com.temenos.tocf.t24ra.outbound.T24ManagedConnectionFactory"
jndi-name="java:/jca/t24ConnectionFactory" pool-
name="T24ConnectionFactory">
<config-property name="charset">ISO-8859-1</config-
property>

17
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

<config-property name="actionTimeout">30</config-
property>
<config-property
name="compressionThreshold">2048</config-property>
<config-property
name="envVariables">OFS_SOURCE=GCS</config-property>
<config-property name="hosts">127.0.0.1</config-
property>
<config-property name="debugPort">30097</config-
property>
<config-property name="ports">21001</config-property>
<config-property name="compression"> true </config-
property>
<config-property name="loadBalancing"> false
</config-property>
<config-property name="allowInput"> false </config-
property>
</connection-definition>
</connection-definitions>
</resource-adapter>
</resource-adapters>

6. Save and quit.

4.6 Accessing BrowserWeb 17

Firstly, we are going to redeploy the same BrowserWeb 17 we used with JBoss 6.4 EAP and
JDK 1.7.

Procedure

1. Before we proceed, we need to make sure that we are using JDK 1.8 and JBoss 7.2.

echo $JAVA_HOME

echo $ORACLE_HOME

18
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

2. Copy BrowserWeb from $JBOSS_6.4/standalone/deployments to

$JBOSS_7.2/standalone/deployments.

3. Start JBoss 7.2 and JBase agent

jbase_agent –p 21001

$JBOSS_HOME/bin/standalone.sh --server-config=T24.xml -
Djboss.node.name=node1 -b 0.0.0.0 -bmanagement 0.0.0.0

4. Access BrowserWeb using Chrome.

5. Access BrowserWeb using Firefox.

6. Access BrowserWeb using Edge.

19
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

The results show that the official BrowserWeb 17 does not work with JBoss 7.2 and JDK 1.8.
The next section we will deploy the latest BrowserWeb packaged inside the Browser Client
from the T24 updates. This is the Browser we downloaded earlier from TCSP.

20
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

5 Deploying the Latest R17 BrowserWeb

from T24 UPDATES
5.1 Preparing the latest BrowserWeb for deployment
We are going to deploy the BrowserWeb which we downloaded from TCSP
R17_EB_BrowserClient update.

Procedure

1. Unpack the R17_EB_BrowserClient_49_ALL.tar

tar xvf R17_EB_BrowserClient_49_ALL.tar

2. Go into the R17_EB_BrowserClient_49_ALL directory.

cd R17_EB_BrowserClient_49_ALL

3. Create a tmp directory.

mkdir tmp

4. Go into the tmp directory.

cd tmp

5. Explode the BrowserWeb.war

jar -xvf ../BrowserWeb.war

6. In text editor, open the browserParameters.xml and verify that the Server
Connection Method is set to JMS as highlighted in yellow.

21
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

7. Save and quit.

8. Go into the WEB-INF directory.

cd WEB-INF/

9. Open jboss-web.xml in the text editor.

10. Edit the t24BROWSERQueue and t24BROWSERReplyQueue from:

<jndi-name>java:/queue/t24BROWSERQueue</jndi-name>

<jndi-name>java:/queue/t24BROWSERReplyQueue</jndi-name>

To:

<jndi-name>java:/queue/t24OFSRQueue</jndi-name>

<jndi-name>java:/queue/t24OFSRReplyQueue</jndi-name>

The difference here is that for JBoss 6 and 7, we are adding / in front of jca and
replacing Browser with OFS

11. Save and quit.

12. Open jboss-deployment-structure.xml

13. Uncomment the dependencies block so that it looks like as shown below

<dependencies>
<module name="deployment.tocfT24ra-ra.rar" />
</dependencies>

14. Save and quit.

15. Open the jboss-classloading.xml file

16. Add the following entries inside the classloading block: parent-first="false" and
export-all="NON_EMPTY" so that it looks as shown below.

22
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

<?xml version="1.0" encoding="UTF-8"?>

<classloading xmlns="urn:jboss:classloading:1.0"
name="BrowserWeb.war"
domain="DefaultDomain"
import-all="true"
parent-first="false"
export-all="NON_EMPTY">
</classloading>

17. Save and quit.

18. Move back to the tmp directory.

cd ../..

19. Remove the BrowserWeb.war in the current tmp folder.

rm –f BrowserWeb.war

20. Repack the BrowserWeb.war with the newly added configuration. Give the war file a
new name.

jar -cvf ../BrowserWeb.war49 *

21. Copy the BrowserWeb49.war to the Jboss deployments directory.

cp BrowserWeb49.war $JBOSS_HOMEL/standalone/deployments

5.2 Accessing BrowserWeb49

23
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

24
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

6 Technical Approval
This section provides the results from the approval/validation of R17 T24/TAFC with JDK8 and
JBoss 7.2 using Oracle 19C database edition. We cover:

• Test environment specifications.

• Testing.

• T24 browser navigation.

6.1 Test Environment

6.1.1 Architecture
The R17 TAFC environment where validation/approval was performed has a 2-tier architecture
– an application server and a database server.

The application tier contains the application server with TAFC/T24. In this environment, a
JBoss EAP (version 7.2.0) was used. The database tier contains the database that stores T24
data. In this environment, an Oracle 19c database is used.

6.1.2 Hardware specifications

Below is a table showing the specification details for the machine used during the R17 TAFC
technical approval exercise.

Hardware Details

Linux Red Hat Enterprise Linux Server 7.7 (Maipo)"

Processor Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz

Memory 15GB

25
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

6.1.3 Software specifications

Below is a table showing all the software details used to configure the R17 TAFC technical
approval environment.

Software Version

TAFC R17

T24 R17

BrowserWeb Browser Client 49

JDK 1.8

JBoss JBoss 7.2 EAP

Google Chrome Version 77.0.3865.120 (Official Build) (64-bit)

Microsoft Edge Microsoft Edge 42.17134.1.0

Firefox Version 77.0.3865.120 (Official Build) (64-bit)

6.1.4 Testing
After configuring the system and performing sanity check (T24, TAFC, BrowserWeb), testing
was performed in four stages:

 Close of Business.

 Automated data injection using Apache’s JMeter

 Browser navigation and manual t24 transactions in both BrowserWeb and UXP Browser
using the supported browser types: Chrome, Microsoft Edge.

 Close of Business.

26
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

All tests were performed on development servers that were in constant use.
Timings quoted below should not be considered comparable with results from an
optimised performance test.

6.1.5 T24 transactions using JMeter

The automated data injection was completed using parameterised JMeter scripts to load large
amounts of T24 data. Various transaction types were used to ensure core functionality was free
of significant errors. A standard transaction mix of 5000 records each were used. The following
table contains the T24 operations covered during this technical approval exercise.

For example:

Application/ENQUIRY Operation

CUSTOMER Create Customer

ACCOUNT Local

Foreign

Create Teller

TELLER
Local Cash Deposit

Foreign Cash Deposit

FUNDS.TRANSFER Local Account to Foreign Account

ACCT.BAL.TODAY Current balance

STMT.ENT.BOOK Statement

27
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

6.1.6 Time taken for data injection

The table below summarises the total transaction time taken by JMeter to inject data into T24
for each application. For example:

Application/ENQUIRY Operation Number of Records Time Taken

2 hrs 45 mins
CUSTOMER Create Customer 5000

2 hrs 20 mins
ACCOUNT Local 5000

2 hrs 25 mins
Foreign 5000

TELLER Create Teller 10

3 hrs 30 mins
Local Cash Deposit 5000

Foreign Cash 5000

Deposit

2 hrs 55 mins
FUNDS.TRANSFER Local Account to 5000
Foreign Account

2 hrs 15 min
ACCT.BAL.TODAY Current balance 5000

2 hr 25 min
STMT.ENT.BOOK Statement 5000

6.1.7 Close of Business (COB)

Finally, the testing was finished by running COB successfully from servlet mode before and
after the data injection phase. Only TSM and COB processes were running during the COB.
Below is a table showing the COB running time.

28
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP

For example:

No of TSM No of COB COB Time taken COB time after data

agents agents before data Injection
COB Injection

1 4 34 mins 33 secs 50 mins

6.1.8 Browser navigation

Both T24 Browser (BrowserWeb) and UXP browser were tested during this exercise. No
special modifications were required to make either browser working in the test environment. All
frequent T24 operations proved to be working as normal across all the following browsers.

Chrome v67.x

Microsoft Edge v40.x

In each case the latest available browser version was used.

6.1.9 Conclusion
During this technical approval exercise, R17 T24/TAFC was found working with fine with JDK8,
JBoss 7.2 EAP and Oracle 19C.

29