Tafc R17 On Jdk1.8, Jboss 7.2 Eap and Oracle 19C: Technical Guide 1.2 July 2020

TAFC R17 on JDK1.8, JBoss 7.
2 EAP
and Oracle 19c
Technical Guide 1.2 July 2020
T24 TAFC R17 on JDK 1.8 and JBoss 7.2 EAP – Oracle 19C Technical Guide
Contents
1 About this Technical Guide ...................................................................... 4

1.1 Scope ............................................................................................................................................. 4
1.2 Audience ........................................................................................................................................ 4
1.3 Skills and knowledge ...................................................................................................................... 5
1.4 Legal .............................................................................................................................................. 5
1.5 History ............................................................................................................................................ 6
2 Introduction .............................................................................................. 7
3 Prerequisites and assumptions ................................................................ 8
3.1 Operating system details ................................................................................................................ 8
3.2 Software details.............................................................................................................................. 8
3.2.1 Third-party software................................................................................................................ 9
3.2.2 Temenos software .................................................................................................................. 9
3.3 Deployment .................................................................................................................................... 9
3.3.1 Editing the R15 BrowserWeb.war artefacts ............................................................................ 9
3.3.2 Deploying the tocfee.ear and tocfT24ra-ra.rar files .............................................................. 13
3.3.3 Configuring the standalone-full.xml file ................................................................................. 13
4 Upgrading from R15 to R17 ................................................................... 16

4.1 T24 AUTHORISE job error during T24 Upgrade .......................................................................... 16
4.1.1 Running the T24.UPDATE service ....................................................................................... 16
4.2 Editing the R17 BrowserWeb.war artefacts .................................................................................. 18
4.3 Deploying the tocfee.ear and tocfT24ra-ra.rar files ...................................................................... 21
4.4 Configuring the Standalone-full.xml file ........................................................................................ 22
4.4.1 Adding the Browser queues ................................................................................................. 22
4.5 Performing a sanity check for database access ........................................................................... 22
4.6 Close of Business ........................................................................................................................ 24
5 TAFC R17 with JDK.18 and JBoss 7.2 EAP .......................................... 27

5.1 Updated .bash_profile file............................................................................................................. 28
5.2 Updating the .profile file in bnk.run ............................................................................................... 28
5.3 Linking TAFC library libclntshcore to Instant Client 19c libclntshcore .......................................... 29
5.4 Performing a sanity check for database access ........................................................................... 29
5.5 Deploying BrowserWeb, TOCFEE and ResourceAdapter on JBoss 7.2 EAP .............................. 30
5.5.1 Configuring the Standalone-full.xml file ................................................................................ 30
5.6 Accessing BrowserWeb 17 .......................................................................................................... 32
6 Deploying the latest R17 BrowserWeb from T24 UPDATES ................. 34

6.1 Preparing the latest BrowserWeb for deployment ........................................................................ 34
6.2 Accessing BrowserWeb49 ........................................................................................................... 36
6.3 Running a Close of Business ....................................................................................................... 37
7 Technical Approval................................................................................. 39
2
7.1 Test environment ......................................................................................................................... 39

7.1.1 Architecture .......................................................................................................................... 39
7.1.2 Hardware specifications ....................................................................................................... 39
7.1.3 Software specifications ......................................................................................................... 39
7.1.4 Testing.................................................................................................................................. 40
7.1.5 T24 transactions using JMeter ............................................................................................. 40
7.1.6 Time taken for data injection ................................................................................................ 41
7.1.7 Close of Business (COB)...................................................................................................... 42
7.1.8 Browser navigation ............................................................................................................... 42
7.1.9 Conclusion............................................................................................................................ 43
3
1 About this Technical Guide

This Technical Guide describes the necessary software components and configurations you
need to run R17 T24-TAFC on JDK 1.8, JBoss 7.2 EAP and Oracle 19C. This guide chiefly
focuses on the key configuration settings you need to get BrowserWeb working.
This guide 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 that are used to create the R17 TAFC environment
 Deploying the T24 artefacts and a detailed focus on configuring and deploying
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 an Oracle database
 Installing an Oracle instant client
 Installing TAFC and T24
 The T24 upgrade procedure
 The T24 update procedure
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 with Oracle 19C database.
4
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
1.4 Legal
© Copyright 2020 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.
5
1.5 History
Version Date Change Author
1.0 October 2019 Initial release Kaydee Dzvuke
1.1 March 2020 Technical author edits Dominik Wietrzak
2.0 July 2020 Customer version created Jonathan Page
6
2 Introduction
This Technical Guide helps you migrate your existing R17 T24/TAFC environment to JDK 8,
JBoss 7.2 and Oracle 19C. It helps you configure BrowserWeb and JBoss to access the
Temenos browser. In this exercise, a 2-tier architecture was created that consists of the
application and database server.
The application tier contains the application server with TAFC and T24. In this exercise, JBoss
Enterprise Application Platform version 7.2 and Oracle 12.2 C database are used. The
database tier contains the database that stores T24 data. For better understanding, the
architecture is provided below.
To produce this guide, we first configured a T24-TAFC R15 environment with JDK 1.7, JBoss 6.4
and Oracle 12.2.1 and then upgraded T24 to R17.
7
3 Prerequisites and assumptions

This chapter lists the technical prerequisites and assumptions for upgrading TAFC R17 on JDK
1.7, JBoss 6.4 and Oracle 12C to the environment built on JDK 1.8, JBoss 7.2 and Oracle 19C.
As we did not have an existing TAFC R17 environment available, we started off with an R15
TAFC environment. This document does not focus on TAFC installation but only on the key
configuration settings required for BrowserWeb to work.
3.1 Operating system details

Red Hat 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 the R17 TAFC
environment.
8
3.2.1 Third-party software

Component Version
Java Development Kit jdk1.7.0_79
JBoss EAP 6.4
Oracle instant client instant-client 12102
Oracle Database 12c
3.2.2 Temenos software

Artefact File Description
R15 TAFC TAFC_R15_LINUX_ELF_AS6_130361.tar.gz

runtime
R15 T24 MB.R15.ORACLE12c.LINUXAS6.TAFCR15.bnk.tar.gz
R15 Oracle MB.R15.ORACLE12c.UNIX.TAFCR15.30-SEP-

dump 2020.dmp.tar.gz
TOCFEE TOCF(EE)-R15.0.0.2.zip Contains

TOCFEE.EAR and
the T24 Resource
Adapter
R15 BrowserWeb-R15.tar R15 BrowserWeb

BrowserWeb
3.3 Deployment
This section provides configuration steps required on R15 BrowserWeb.
3.3.1 Editing the R15 BrowserWeb.war artefacts

Procedure
1. Extract the BrowserWeb-R15.tar file.
tar xvf BrowserWeb-R15.tar
9
2. Change to the BrowserWeb-15 directory.
cd BrowserWeb-15
3. Create a tmp directory.
mkdir tmp
4. Change to the tmp directory.
cd tmp
5. Explode the BrowserWeb.war file.
jar -xvf ../BrowserWeb.war
6. In your text editor, open the browserParameters.xml file and verify that Server
Connection Method is set to JMS as highlighted in yellow.
7. Save and quit.
8. Change into the WEB-INF directory.
cd WEB-INF/
9. Open jboss-web.xml in your text editor.
10
10. As instructed in the file, comment out the following lines
<jndi-name>java:jca/t24ConnectionFactory</jndi-name>
<jndi-name>queue/t24OFSQueue</jndi-name>
<jndi-name>queue/t24OFSReplyQueue</jndi-name>
11. Uncomment the following lines.
<jndi-name>java:/jca/t24ConnectionFactory</jndi-name>
<jndi-name>java:/queue/t24OFSQueue</jndi-name>
<jndi-name>java:/queue/t24OFSReplyQueue</jndi-name>
This change is for JBoss 6 and 7. The change includes adding a forward slash
(/) before jca and adding java:/.
12. Save and quit.
13. Open jboss-deployment-structure.xml.
14. Uncomment the dependencies block so that it looks like as shown below
<dependencies>
<module name="deployment.tocfT24ra-ra.rar" />
</dependencies>
15. Save and quit.
16. Open the jboss-classloading.xml file.
17. Add the following entries inside the classloading block: parent-
first="false" and export-all="NON_EMPTY" so that it looks like the fragment
shown below.
11
<?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>
18. Save and quit.
19. Change to the lib directory.
cd lib
20. Remove the following JAR files: commons-collections-3.2.1.jar,

xschema.jar and xmlparserv2.jar.
rm -f xschema.jar xmlparserv2.jar commons-collections-3.2.1.jar
21. Change back to the tmp directory.
cd ../..
22. Remove the BrowserWeb.war file in the current tmp directory.
rm –f BrowserWeb.war
23. Repack the BrowserWeb.war file with the newly added configuration.
jar -cvf ../BrowserWeb.war *
12
24. Copy the BrowserWeb.war file to the JBoss deployments directory.
cp BrowserWeb.war $JBOSS_HOME/standalone/deployments
3.3.2 Deploying the tocfee.ear and tocfT24ra-ra.rar files

Procedure
1. Unzip the TOCF(EE)-R15.0.0.2.zip file.
unzip TOCF(EE)-R15.0.0.2.zip
2. Copy tocfee.ear to the JBoss deployments directory.
cp tocfee.ear $JBOSS_HOME/standalone/deployments
3. Copy tocfT24ra-ra.rar to the JBoss deployments directory.
cp tocfT24ra-ra.rar $JBOSS_HOME/standalone/deployments
3.3.3 Configuring the standalone-full.xml file

You need to define the queues and add the resource adapter settings in the standalone-
full.xml file.
Procedure
1. Change to the standalone directory.
cd $JBOSS_HOME/standalone
13
2. Copy the contents of standalone-full.xml to a new file.
cp standalone-full.xml T24.xml
3. Open T24.xml in a text editor.
4. Locate the <jms-destinations> tag and add the following queues as highlighted
below.
<jms-destinations>
<jms-queue name="ExpiryQueue">
<entry name="java:/jms/queue/ExpiryQueue"/>
</jms-queue>
<jms-queue name="DLQ">
<entry name="java:/jms/queue/DLQ"/>
</jms-queue>
<jms-queue name="t24OFSQueue">
<entry name="queue/t24OFSQueue"/>
</jms-queue>
<jms-queue name="t24OFSReplyQueue">
<entry name="queue/t24OFSReplyQueue"/>
</jms-queue>
<jms-queue name="requestQueue">
<entry name="queue/requestQueue"/>
</jms-queue>
<jms-queue name="responseQueue">
<entry name="queue/responseQueue"/>
</jms-queue>
</jms-destinations>
5. Locate the urn:jboss:domain:resource-adapters:1.1 subsystem section

and modify it to look as shown below.
<subsystem xmlns="urn:jboss:domain:resource-adapters:1.1">
<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="ports">
21001
</config-property>
<config-property name="actionTimeout">
30
14
</config-property>
<config-property name="allowInput">
false
</config-property>
<config-property name="debugPort">
30097
</config-property>
<config-property name="envVariables">
OFS_SOURCE=GCS
</config-property>
<config-property name="compressionThreshold">
2048
</config-property>
<config-property name="hosts">
127.0.0.1
</config-property>
<config-property name="charset">
ISO-8859-1
</config-property>
<config-property name="compression">
true
</config-property>
<config-property name="loadBalancing">
false
</config-property>
</connection-definition>
</connection-definitions>
</resource-adapter>
</resource-adapters>
</subsystem>
6. Save and quit.
7. Start JBase agent.
jbase_agent –p 21001
8. Start JBoss.
$JBOSS_HOME/bin/standalone.sh --server-config=T24.xml -
Djboss.node.name=node1 -b 0.0.0.0 -bmanagement 0.0.0.0
15
4 Upgrading from R15 to R17

With the R15 up and running, our next step was to upgrade to R17 using the artefacts from
Temenos Distribution. We still maintained JDK1.7, JBoss 6.4 and Oracle 12.C setup.
Artefact File Description
TAFC TAFC_R17_LINUX_ELF_AS7_132415.tar.gz R17 TAFC

runtime
TEMP.RELEASE R17.LINUXAS7.20190331.temp.release.tar.gz R17

temp.release
TOCFEE TOCF(EE)-R17.0.11.zip
BrowserWeb BrowserWeb-R17.00.tar
4.1 T24 AUTHORISE job error during T24 Upgrade

At the stage of running T24.AUTHORISE BATCH job, we experienced the following error.
job name = T10:50:22RISE> 00

AUTHORISED 0_BNK/T24.AUTHORISE_T24.AUTHORISE_3_17 OCT
2019_10:50:22:347_Fatal error in OPF error NO FILE.CONTROL RECORD -
EB.USAGE.STATISTICS - F.EB.USAGE.STATISTICS , MNEMONIC = ,
IN.PARAMETER = F.EB.USAGE.STATISTICS , COMPANY = GB0010001 ,
CALL.ROUTINE = OPF.b,OPF.b,LOG.WRITE.b
_BNK/T24.AUTHORISE_T24.AUTHORISE_3_17 OCT 2019_10:50:22:395_SELECT
F.RECORD.LOCK WITH K.USER EQ "" Selected=0 time=0secs
This issue is logged in PACS Ticket 3295890. The solution is to apply the update
eb_utility_xx, which contains the FILE.CONTROL of EB.USAGE.STATISTICS. When
you install this update by running the T24.UPDATES service the reported problem is resolved.
4.1.1 Running the T24.UPDATE service

Procedure
1. Using the T24 ToolBox, connect to the R17 system and download the System Definition
file.
2. Connect to Temenos Customer Support Portal and add the system by uploading the
SysDef.xml file.
16
3. Go to system and click Select system.
A new page opens.
4. Select EB_Utility and download it.
5. Select, download and save EB_BrowserClient with a unique file name. You will need
this later when you move to JDK8 and JBoss 7.2.
6. Apply the EB_Utility using the usual T24.UPDATE procedure.
7. Resume the T24.AUTHORISE job after the T24.UPDATE is complete.
17
The following sections explain the configurations required to get the R17 BrowserWeb working.
4.2 Editing the R17 BrowserWeb.war artefacts

Procedure
1. Unpack the BrowserWeb-R17.00.tar file.
tar xvf BrowserWeb-R17.00.tar
2. Change to the BrowserWeb-17.00 directory.
cd BrowserWeb-17.00
mkdir tmp
4. Change into the tmp directory.
cd tmp
6. In a text editor, open the browserParameters.xml file and verify that the Server
Connection Method is set to JMS as highlighted in yellow.
18
7. Save and quit.
8. Change to the WEB-INF directory.
cd WEB-INF/
9. Open jboss-web.xml in your text editor.
10. Modify the t24BROWSERQueue and t24BROWSERReplyQueue entries.
From:
<jndi-name>java:/queue/t24BROWSERQueue</jndi-name>
<jndi-name>java:/queue/t24BROWSERReplyQueue</jndi-name>
To:
<jndi-name>java:/queue/t24OFSQueue</jndi-name>
<jndi-name>java:/queue/t24OFSReplyQueue</jndi-name>
This change is for JBoss 6 and 7. It replaces Browser with OFS.
11. Save and quit the editor.
12. Open jboss-deployment-structure.xml in your editor.
19
13. Uncomment the dependencies block so that it looks as shown below.
<dependencies>
</dependencies>
first="false" and export-all="NON_EMPTY" so that it looks as shown
below.

import-all="true"
</classloading>
18. Open web.xml.
19. Search for resource-ref id="ResourceRef_t24OFSQueue" and

uncomment it.
<resource-ref id="ResourceRef_t24OFSQueue">
<description>OFS queue</description>
<res-ref-name>queue/t24OFSQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
20
cd ../..
21. Remove the BrowserWeb.war file that is in the current tmp folder.
22. Repack the BrowserWeb.war with the newly added configuration.
jar -cvf ../BrowserWeb.war *
23. Copy the BrowserWeb.war to the JBoss deployments directory.
cp BrowserWeb.war $JBOSS_HOME/standalone/deployments
4.3 Deploying the tocfee.ear and tocfT24ra-ra.rar files

Procedure
1. Extract the TOCF(EE)-R17.0.11.zip file.
unzip TOCF(EE)-R17.0.11.zip
2. Copy tocfee.ear to the JBoss deployments directory.
cp tocfee.ear $JBOSS_HOME/standalone/deployment
3. Copy tocfT24ra-ra.rar to the JBoss deployments directory.
cp tocfT24ra-ra.rar $JBOSS_HOME/standalone/deployment
21
4.4 Configuring the Standalone-full.xml file

You need to add the queues and the T24 resource adapter settings.
4.4.1 Adding the Browser queues

Procedure
1. Open the T24.xml file in a text editor.
2. Navigate to the <subsystem xmlns="urn:jboss:domain:messaging-

activemq:4.0> section.
3. Add the following queues just under <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.5 Performing a sanity check for database access

Procedure
1. Connect to the R17 database using an instant client.
sqlplus t24/t24@R17AMR19
22
2. Test database connectivity using config.XMLORACLE.
config.XMLORACLE and select 4
3. Access T24 classic.
23
4. Access BrowserWeb:
a. Start JBASE agent.
b. Start JBoss.
Take note of the BrowserWeb details as highlighted in the following screen

captures.
4.6 Close of Business

As a rule of thumb, following the upgrade, COB was initiated and it ran smoothly but there was
REVALUATION error in the F.EB.EOD.ERROR table.
24
According to PACS ticket 204631, this error happens whenever there is a position difference in
the system. Hence, if the difference has been cleared, then revaluation error will not occur.
The system raises the error SYSTEM LOCAL CCY EXCEPTION if the fields
POSITION.ENTRY (35) and CONTRACT.RECON (36) are set to ACCOUNT and Y
respectively in CONSOLIDATE.COND and if there is any amount presented in the field
EXCEPT.AMT.LCY(22) of the EB.SYSTEM.SUMMARY record (nothing but a GL difference).
The system raises the error FOREIGN CCY NOT NETTING TO ZERO if there is any
position difference.
25
26
5 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 JDK.1.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 instantclient-sdk-linux.x64-

19C 19.3.0.0.0dbru.zip
The following steps have been completed on the existing R17 environment.
1. JDK 1.8 has been installed.
2. JBoss 7.2 EAP has been installed.
3. Oracle DB 19C has been installed.
4. Oracle instant client 19c has been installed.
5. An R17 Oracle dump has been taken from Oracle 12c and restored on Oracle 19c.
27
5.1 Updated .bash_profile file

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
5.2 Updating the .profile file in bnk.run

You must update the T24 .profile file as well. The file is automatically executed upon
logging in.
Procedure
1. Update the .profile file that is stored in bnk.run.
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
2. Start a new shell session and verify the new JDK and ORACLE environment variables.
echo $JAVA_HOME
echo $ORACLE_HOME
28
5.3 Linking TAFC library libclntshcore to Instant Client 19c

libclntshcore
Procedure
1. Change 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
5.4 Performing a sanity check for database access

Procedure
1. Connect to the R17 database using instant client.
sqlplus t24/t24@R17AMR19
2. Test database connectivity using config.XMLORACLE.
config.XMLORACLE
select 4
29
3. Access T24 classic.
5.5 Deploying BrowserWeb, TOCFEE and ResourceAdapter

on JBoss 7.2 EAP
There are several pre-configuration steps that are required to prepare the artefacts for the
actual deployment.
5.5.1 Configuring the Standalone-full.xml file

You need to add the required OFS queues and T24 resource adapter for BrowserWeb to work.
30
Procedure
1. Copy and rename the Standalone-full.xml file that is in the

$JBOSS_HOME/standalone/configuration directory. The file is T24.xml in
this document.
2. Open the file in a text editor and navigate to the <subsystem

xmlns="urn:jboss:domain:messaging-activemq:4.0> section.
3. Add the following queues just under the <jms-queue name="DLQ"

entries="java:/jms/queue/DLQ"/> entry.
<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"> entry 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>
<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>
31
6. Save and quit.
5.6 Accessing BrowserWeb 17

To access BrowserWeb 17 we first need to redeploy the same BrowserWeb 17 we used with
JBoss 6.4 EAP and JDK 1.7.
Procedure
1. Ensure that you are using JDK 1.8 and JBoss 7.2.
echo $JAVA_HOME
echo $ORACLE_HOME
2. Copy BrowserWeb from $JBOSS_6.4/standalone/deployments to

$JBOSS_7.2/standalone/deployments.
3. Start JBase agent.
4. Start JBoss 7.2.
32
5. Access BrowserWeb using Chrome.
6. Access BrowserWeb using Firefox.
7. Access BrowserWeb using Edge.
The results show that the official BrowserWeb 17 does not work with JBoss 7.2 and
JDK 1.8. In the next section, you will deploy the latest BrowserWeb packaged inside the
Browser Client from the T24 updates. This is the Browser that you downloaded earlier
from the Temenos Customer Support Portal (TCSP).
33
6 Deploying the latest R17 BrowserWeb

from T24 UPDATES
6.1 Preparing the latest BrowserWeb for deployment

You are going to deploy the BrowserWeb which you have downloaded from the Temenos
Customer Support Portal (TCSP) R17_EB_BrowserClient update.
Procedure
1. Extract the R17_EB_BrowserClient_49_ALL.tar file.
tar xvf R17_EB_BrowserClient_49_ALL.tar
2. Change into the R17_EB_BrowserClient_49_ALL directory.
cd R17_EB_BrowserClient_49_ALL
mkdir tmp
4. Change into the tmp directory.
cd tmp
6. In a text editor, open the browserParameters.xml file and verify that the
>Server Connection Method is set to JMS as highlighted in yellow.
34
7. Save and quit.
8. Go into the WEB-INF directory.
cd WEB-INF/
9. Open jboss-web.xml in a text editor.
10. Edit the t24BROWSERQueue and t24BROWSERReplyQueue and make the

following changes.
Before:
<jndi-name>java:/queue/t24BROWSERQueue</jndi-name>
<jndi-name>java:/queue/t24BROWSERReplyQueue</jndi-name>
After:
<jndi-name>java:/queue/t24OFSRQueue</jndi-name>
<jndi-name>java:/queue/t24OFSRReplyQueue</jndi-name>
This change is for JBoss 6 and 7. It replaces Browser with OFS.
11. Save and quit.
12. Open jboss-deployment-structure.xml in a text editor.
13. Uncomment the dependencies block so that it looks like the block shown below.
<dependencies>
</dependencies>
14. Save and quit.
35
first="false" and export-all="NON_EMPTY" so that it looks like the block
shown below.

import-all="true"
</classloading>
17. Save and quit.
cd ../..
19. Remove the BrowserWeb.war from the current tmp folder.
20. Repack the BrowserWeb.war with newly added configuration. Give the WAR file a
new name.
jar -cvf ../BrowserWeb.war49 *
21. Copy the BrowserWeb49.war file to the JBoss deployments directory.
cp BrowserWeb49.war $JBOSS_HOME/standalone/deployments
6.2 Accessing BrowserWeb49

Procedure
1. To access BrowserWeb, open the following URL in your web browser:

https://server_name:8080/BrowserWeb49
36
2. Access the About T24 Browser page: click Help > About T24 Browser.
3. Confirm the T24 release by running the command SPF S SYSTEM.
6.3 Running a Close of Business

You need to start COB in servlet mode.
37
38
7 Technical Approval
This section provides the results from the approval and validation of R17 T24/TAFC with JDK 8
and JBoss 7.2 using Oracle 19C database edition.
The following topics are covered:
 Test environment specifications
 Testing
 T24 browser navigation
7.1 Test environment
7.1.1 Architecture
The R17 TAFC environment where validation and approval were performed has a 2-tier
architecture: application server and database server.
The application tier contains the application server with TAFC/T24. In this environment, a
JBoss EAP (version 7.2.0) instance is used. The database tier contains the database that
stores T24 data. In this environment, an Oracle 19c database is used.
7.1.2 Hardware specifications

The following table shows 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 15 GB
7.1.3 Software specifications

The following table shows all the software details used to configure the R17 TAFC technical
approval environment.
39
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)
7.1.4 Testing
After configuring the system and performing sanity check (T24, TAFJ, BrowserWeb and UXP
Browser), testing was performed in four stages:
 Close of Business.
 Automated data injection using Apache JMeter.
 Browser navigation and manual T24 transactions in both BrowserWeb and UXP
Browser using the supported browsers: Chrome and Microsoft Edge.
 Close of Business.
All tests were performed on development servers that were in constant use. The
timings quoted below should not be considered comparable with results from an
optimised performance test.
7.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.
40
Example:
Application/ENQUIRY Operation
CUSTOMER Create Customer
ACCOUNT Local
Foreign
TELLER Create Teller
Local Cash Deposit
Foreign Cash Deposit
FUNDS.TRANSFER Local Account to Foreign Account
ACCT.BAL.TODAY Current balance
STMT.ENT.BOOK Statement
7.1.6 Time taken for data injection

The following table summarizes the total transaction time taken by JMeter to inject data into
T24 for each application.
Example:
Application/ENQUIRY Operation Number of Records Time Taken
CUSTOMER Create 5000 2 hrs 45 mins

Customer
ACCOUNT Local 5000 2 hrs 20 mins
Foreign 5000 2 hrs 25 mins
TELLER Create Teller 10 3 hrs 30 mins
Local Cash 5000

Deposit
Foreign Cash 5000

Deposit
41
FUNDS.TRANSFER Local Account 5000 2 hrs 55 mins

to Foreign
Account
ACCT.BAL.TODAY Current balance 5000 2 hrs 15 min
STMT.ENT.BOOK Statement 5000 2 hr 25 min
7.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 COB. The
following table shows the COB running time.
Example:
COB No of TSM No of COB COB Time COB time after data

agents agents taken before injection
data injection
1 4 34 mins 33 50 mins
secs
There were some fatal errors reported during COB due to data issues. Jobs reporting fatal
errors were skipped.
7.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.
42
7.1.9 Conclusion
This technical approval exercise showed that R17 T24/TAFC worked well with JDK 8, JBoss
7.2 EAP and Oracle 19C.
We strongly recommend that you apply all T24 updates to ensure that no errors are
experienced, especially when executing batch jobs.
43

Tafc R17 On Jdk1.8, Jboss 7.2 Eap and Oracle 19C: Technical Guide 1.2 July 2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tafc R17 On Jdk1.8, Jboss 7.2 Eap and Oracle 19C: Technical Guide 1.2 July 2020

Uploaded by

Copyright:

Available Formats

TAFC R17 on JDK1.8, JBoss 7.

1 About this Technical Guide ...................................................................... 4

4 Upgrading from R15 to R17 ................................................................... 16

5 TAFC R17 with JDK.18 and JBoss 7.2 EAP .......................................... 27

6 Deploying the latest R17 BrowserWeb from T24 UPDATES ................. 34

7.1 Test environment ......................................................................................................................... 39

1 About this Technical Guide

 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

This document does not cover:

 Installing an Oracle database

 Installing an Oracle instant client

 Installing TAFC and T24

 The T24 upgrade procedure

 The T24 update procedure

1.3 Skills and knowledge

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

Version Date Change Author

1.0 October 2019 Initial release Kaydee Dzvuke

1.1 March 2020 Technical author edits Dominik Wietrzak

2.0 July 2020 Customer version created Jonathan Page

3 Prerequisites and assumptions

3.1 Operating system details

Linux-/srv/Temenos/R17/bnk/bnk.run: cat /etc/*release*

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"

3.2 Software details

3.2.1 Third-party software

Java Development Kit jdk1.7.0_79

JBoss EAP 6.4

Oracle instant client instant-client 12102

Oracle Database 12c

3.2.2 Temenos software

R15 TAFC TAFC_R15_LINUX_ELF_AS6_130361.tar.gz

R15 T24 MB.R15.ORACLE12c.LINUXAS6.TAFCR15.bnk.tar.gz

R15 Oracle MB.R15.ORACLE12c.UNIX.TAFCR15.30-SEP-

TOCFEE TOCF(EE)-R15.0.0.2.zip Contains

R15 BrowserWeb-R15.tar R15 BrowserWeb

3.3.1 Editing the R15 BrowserWeb.war artefacts

1. Extract the BrowserWeb-R15.tar file.

tar xvf BrowserWeb-R15.tar

2. Change to the BrowserWeb-15 directory.

3. Create a tmp directory.

4. Change to the tmp directory.

5. Explode the BrowserWeb.war file.

jar -xvf ../BrowserWeb.war

7. Save and quit.

8. Change into the WEB-INF directory.

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

10. As instructed in the file, comment out the following lines

11. Uncomment the following lines.

12. Save and quit.

13. Open jboss-deployment-structure.xml.

15. Save and quit.

16. Open the jboss-classloading.xml file.

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

18. Save and quit.

19. Change to the lib directory.

20. Remove the following JAR files: commons-collections-3.2.1.jar,

rm -f xschema.jar xmlparserv2.jar commons-collections-3.2.1.jar

21. Change back to the tmp directory.

22. Remove the BrowserWeb.war file in the current tmp directory.

jar -cvf ../BrowserWeb.war *

Linux-/srv/Temenos/R17/bnk/bnk.run: cat /etc/release