Stack 1 Red Hat – JBoss

Customer Runbook 4.0 | October 2020

All post R20 AMR releases up to and including R21 AMR
Stack 1 Red Hat – JBoss runbook, version 4.0

Contents
1 About this runbook 5
1.1 Stack tables and other Stack runbooks 5
1.2 Scope 5
1.3 Audience 5
1.3.1 Skills and knowledge 5
1.4 Legal 6
1.5 History 7
2 Introduction 8
2.1 The architecture 8
2.2 UXP Browser Generate On Demand (GOD) mode 9
2.3 Components deployed in the GOD mode of UXP Browser 9
3 Prerequisites 11
3.1 Software prerequisites 11
3.1.1 Third-party software 11
3.1.2 Temenos artefacts 11
3.2 Hardware prerequisites 13
4 Before you start 14
4.1 Completing preinstallation tasks 14
4.2 Checking the system 15
4.3 Prerequisite directory structure 15
4.4 Setting the environment variables 16
4.5 Verifying the system for third-party software 17
5 Installing TAFJ runtime 19
5.1 Preparing the Transact and TAFJ installation files 19
5.2 Extracting Transact 19
5.3 Installing TAFJ 19
5.4 Deploying the database driver 23
5.4.1 Deploying the driver for MS SQL Server 23
5.4.2 Deploying the driver for NuoDB 23
5.4.3 Deploying the drivers for Oracle Database 23
5.4.4 Deploying the driver for PostgreSQL 24
6 Configuring TAFJ 25
6.1 Configuring tafj.properties 25
6.2 Verifying TAFJ installation 28

2
Stack 1 Red Hat – JBoss runbook, version 4.0

7 Sanity check 31
7.1 Accessing Classic 31
7.2 Launching DBTools 33
8 Configuring JBoss modules 34
8.1 Configuring the database driver module 34
8.1.1 Configuring the module for Microsoft SQL Server 34
8.1.2 Configuring the module for NuoDB 35
8.1.3 Configuring the module for Oracle Database 36
8.1.4 Configuring the module for PostgreSQL 37
8.2 Configuring the TAFJ module 38
8.3 Configuring the Transact module 40
8.4 Generating the Transact module.xml file 40
8.4.1 JBossTools command for generating module.xml 41
9 Configuring standalone profile on the application server 42
9.1 Starting JBoss with J2EE 8 full profile 42
9.2 Configuring the standalone full profile 43
10 Extracting UXP Browser artefacts 48
11 Configuring and deploying Transact and TAFJ artefacts 50
11.1 Deploying TAFJJEE_EAR.ear and TAFJ Spooler plugins 50
11.2 Deploying BrowserWeb 50
11.3 Modifying Browser.war 51
11.4 Modifying irf-rp-services.war 51
11.5 Modifying irf-t24catalog-services.war 52
11.6 Embedding the database driver in ResourceServer.war 53
11.7 Modifying the required EJB JAR files 54
11.8 Configuring the SSOUSER1 user in JBoss 58
11.9 Configuring UXP Browser in GOD mode 60
11.9.1 Resource Server database parameters for supported databases 62
11.10 Deploying UXP Browser artefacts in JBoss 63
11.11 Deploying the EJB JAR files in JBoss 63
11.12 Installing UXP Browser help text 64
12 Deploying Transact component services 65
12.1 Packaging Axis2 archives 65
12.2 Deploying Axis2 68
13 Sanity check (post deployment) 72
13.1 Starting the application server 72
13.1.1 Starting JBoss with BrowserWeb 72
13.1.2 Starting JBoss with UXP Browser 72

3
Stack 1 Red Hat – JBoss runbook, version 4.0

13.1.3 Mandatory command arguments 73

13.2 Accessing TAFJEE 73
13.3 Accessing BrowserWeb 76
13.4 Accessing UXP Browser 78
13.5 Accessing Axis2 servlet 80
13.6 Performing an integrated test of Axis2 and Transact 82

4
Stack 1 Red Hat – JBoss runbook, version 4.0

1 About this runbook

The Stack 1 Red Hat – JBoss runbook shows you how to install and configure TAFJ-Transact on JBoss EAP 7.3
with any of the following databases: Microsoft SQL Server 2019, NuoDB 4.x, Oracle 19c or PostgreSQL
11/12.When you complete the deployment, you will be able to perform business operations in Transact using UXP
Browser and BrowserWeb.

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

1.1 Stack tables and other Stack runbooks

To view the software that is supported as part of stack 1, together with our other stack runbooks, see the R21 stacks
table in either the Temenos customer or partner support portal.

1.2 Scope
This runbook covers:

l Installing TAFJ
l Installing Transact
l Configuring JBoss 7.3 EAP
l Deploying Transact and TAFJ artefacts in JBoss

1.3 Audience
This runbook has been written for consultants who are responsible for deploying TAFJ-Transact on JBoss
application server.

1.3.1 Skills and knowledge

To get the most from this runbook, you need to be familiar with the following technologies and products:

5
Stack 1 Red Hat – JBoss runbook, version 4.0

l TAFJ
l Transact
l JBoss
l The chosen database management system: Microsoft SQL Server, NuoDB, Oracle Database, or PostgreSQL

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

TM
The information in this guide relates to TEMENOS 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.

6
Stack 1 Red Hat – JBoss runbook, version 4.0

1.5 History

Version Date Description Author

1.0 September 2020 Initial release of this runbook. Dominik Wietrzak

2.0 September 2020 Updated "Modifying the required EJB JAR files" Dominik Wietrzak
on page 54.

3.0 October 2020 Added NuoDB-related information. Dominik Wietrzak

4.0 October 2020 Added "Installing UXP Browser help text" on Dominik Wietrzak
page 64.

7
Stack 1 Red Hat – JBoss runbook, version 4.0

2 Introduction
This runbook helps you set up a development or test environment for Transact and TAFJ on Red Hat Linux 8.2. It
shows you how to install and configure TAFJ, Transact and JBoss and how to access Transact through both
BrowserWeb and UXP Browser.

2.1 The architecture

In this exercise, a two-tier architecture has been created which consists of an application server and a database
server. The application tier contains JBoss EAP (version 7.3) application server with TAFJ and Transact. The
database tier contains one of the following DBMSes: MS SQL Server 2019, NuoDB 4.1.0.1, Oracle 19c, or
PostgreSQL 11/12. For better understanding, the architecture is given below.

8
Stack 1 Red Hat – JBoss runbook, version 4.0

2.2 UXP Browser Generate On Demand (GOD) mode

In releases prior to R20, there was a large directory in UXP Browser on the web server file system
(BRP/generated) which contained over 250,000 IRIS and Edge files. To manage such a large number of files
securely and keep the system scalable was difficult.

In R20 and later releases, model-derived artefacts are no longer pre-generated. Instead, they are generated on-
demand and saved in the Resource Server database. As a result, the start-up time of the system has been
significantly reduced.

The first time you access a screen, there is a one-off delay as the system generates the screen. Once this completes,
the screen is stored for all subsequent requests. The generated screens are stored in the database permanently until
the underlying definition changes in Transact.

2.3 Components deployed in the GOD mode of UXP Browser

You must configure and deploy the following components to deploy and run UXP Browser in the GOD mode.

Authenticator (Authenticator.war)

This component validates Transact user credentials. It authenticates user names and passwords against
Transact using the tComponent framework and ensures there is secure communication between Browser
and IRIS.

UXP Browser (Browser.war)

This component renders the new UXP Browser user interface. It communicates with the Resource Server to
render front end screens and with the IRIS layer to use Transact data from the database. Its main benefits
are: better scalability, the SaaS capability and support for multi tenancy.

Resource server (ResourceServer.war)

This component uses a database schema (within each per-tenant Transact database) providing an alternative
to the file system for the storage and retrieval of tenant-specific variants of resources that are external to
Browser.war, for example artefacts generated from models (projects, menus, templates etc.) and static
resources (CSS stylesheets, HTML files, etc.).

Interaction Framework Resource Provider service (irf-rp-services.war)

9
Stack 1 Red Hat – JBoss runbook, version 4.0

This service processes requests and responses through the Resource Provider (RP) component apart from
through traditional Open Financial Service (OFS).

Using the Interaction Framework Resource Provider service, you can communicate with Transact to perform
various Transact operations such as create, view, delete, update and so on, for any versions and
fetch any enquiry results without any hassle of metadata generation.

Interaction Framework Catalog services (irf-t24catalog-services.war)

This service was designed in a generic way to retrieve metadata information for any Transact artefact in an
XML formatted response. The Interaction Framework Catalog service is used by UXP Browser deployed in
the Generate On Demand mode as well as Design Studio on DSF Packager.

Enterprise Java Beans (EJB files)

The EJBs are packaged as JAR files and are deployed on the Transact application server to support remote
EJB connectivity. They enable APIs and Transact running on separate or remote application servers to
communicate with each other. The following EJBs are required:

l Authentication service EJB (t24-EB_AuthenticationService-ejb.jar)

l Catalog service EJB (t24-EB_CatalogService-ejb.jar)
l Resource Provider service EJB (t24-EB_ResourceProviderService-ejb)

10
Stack 1 Red Hat – JBoss runbook, version 4.0

3 Prerequisites
Ensure that your environment meets the requirements listed in this section before you install TAFJ and Transact.
This chapter lists the software prerequisites and the assumptions made regarding the installation requirements.

3.1 Software prerequisites

3.1.1 Third-party software

Software Version

OpenJDK 1.8

JBoss EAP 7.3

Microsoft SQL Server 2019

NuoDB 4.x

Oracle 19c 12.2.0.3

PostgreSQL 12.3

Axis2 1.6.2

3.1.2 Temenos artefacts

Artefacts File name Description

MS SQL Server MB.202008.MSSQL_2014.WIN.TAFJ202008.30- Contains the database.

bak file SEP-2021.bak.tar.gz

NuoDB Backup MB.202008.NuoDB_ Contains the database.

file 4.0.1.1.LINUX.TAFJ202008.30-SEP-
2021.backup.tar.gz

Oracle MB.202008.ORACLE12.2.UNIX.TAFJ202008.30- Contains the database.

database dump SEP-2021.dmp.tar.gz
file

11
Stack 1 Red Hat – JBoss runbook, version 4.0

Artefacts File name Description

PostgreSQL MB.202008.PostgresSQL_ Contains the database.

backup file 11.8.TAFJ202008.30-SEP-2021.sql.tar.gz

Transact MB.202008.TAFJ202008.bnk.tar.gz Contains the bnk directory

that holds the Transact
libraries.

TAFJ TAFJ.DEV.202008.1.tar.gz Contains the TAFJ runtime

.jar file, TAFJ patch script
and TAFJ setup script.

Transact BrowserWeb-202008.00.tar Old browser components.

Browser

UXP Browser UXP-Browser.202008.zip UXP Browser components

This installation package contains the following required

components:

l Authenticator-202008.0.1.war
l Browser-202008.0.1.war
l irf-rp-services-202008.0.1.war
l ResourceServerWar-202008.0.1.war

Additional EJB t24-EB_AuthenticationService-ejb.jar EJB JAR files required for

JAR files t24-EB_CatalogService-ejb.jar deploying UXP Browser in
the Generate On Demand
t24-EB_ResourceProviderService-ejb.jar (GOD) mode

These files are available in the subdirectories under

$TEMENOS_HOME/24/bnk/Extensions.

IRIS Catalog IRISR18_CatalogServices_TAFJ_ Contains catalog services.

Services 202008.0.1.zip

Temenos EncryptPassword.jar The utility for encrypting

Encryption passwords.
Utility

12
Stack 1 Red Hat – JBoss runbook, version 4.0

3.2 Hardware prerequisites

Ensure that you have at least 16 GB RAM available on the application server. UXP Browser requires at least 8 GB
RAM.

13
Stack 1 Red Hat – JBoss runbook, version 4.0

4 Before you start

Before you start installing and configuring the stack, verify that your technical infrastructure has been set up properly.

4.1 Completing preinstallation tasks

Procedure

1. Load Transact data from a file into the RDBMS of your choice. Use one of the following files:
l Microsoft SQL Server: MB.202008.MSSQL_2014.WIN.TAFJ202008.30-SEP-
2021.bak.tar.gz
l NuoDB: MB.202008.NuoDB_4.0.1.1.LINUX.TAFJ202008.30-SEP-
2021.backup.tar.gz
l Oracle Database: MB.202008.ORACLE12.2.UNIX.TAFJ202008.30-SEP-
2021.dmp.tar.gz
l PostgreSQL: MB.202008.PostgresSQL_11.8.TAFJ202008.30-SEP-
2021.sql.tar.gz

2. Load TAFJ-related stored procedures and Java functions into the database. For more information, see the
database-specific installation document that is stored in $TAFJ_HOME/doc.
3. Install the required third-party software. For more information about the installation paths, see "Prerequisite
directory structure" on the next page.
4. Copy all Temenos artefacts into the chosen installation directory. For more information about the installation
paths, see "Prerequisite directory structure" on the next page.
5. Install Korn shell – at the command line, issue the following command:
yum install ksh
6. If you are going to use a non-standard port on the application server, ensure that you open it in the Linux
firewall:
a. Add the port by running the following command:
firewall-cmd --zone=public --add-port=9089/tcp –permanent
b. Reload the new configuration:
firewall-cmd --reload
c. Check that the new rule is enabled:
firewall-cmd --list-all

14
Stack 1 Red Hat – JBoss runbook, version 4.0

4.2 Checking the system

Procedure

1. Check the version of the operating system: verify that your system is running on Red Hat Enterprise Linux
version 8.x. At the Linux command-line, execute the following command:
cat /etc/redhat-release

2. Check how much disk space is available. At the Linux command-line, execute the following command:
df -h
The minimum requirement is 20 GB of disk space.
3. Create the required directory structure.
a. At the Linux command-line, navigate to your installation directory and create the Temenos directory.
mkdir Temenos
b. Under the Temenos directory, create the following directories.

mkdir -p Temenos/TAFJ
mkdir -p Temenos/T24
mkdir -p Temenos/UXPBrowser
mkdir -p Temenos/3rdParty/Java
mkdir -p Temenos/3rdParty/AS
mkdir -p Temenos/inst
mkdir -p Temenos/inst/tafjinst
mkdir -p Temenos/inst/t24inst

4.3 Prerequisite directory structure

Directory Subdirectory Description

3rdParty The 3rdParty directory contains all installed third-party software, such
as JDK 1.8 and JBoss.

Java This directory contains the JDK binary files.

AS This is the JBoss application server installation directory.

15
Stack 1 Red Hat – JBoss runbook, version 4.0

Directory Subdirectory Description

inst The inst directory contains all installers to set up TAFJ-Transact.

t24inst t24inst is a subdirectory of inst, which contains Transact installation

files.

tafjinst tafjinst is a subdirectory of inst, which contains TAFJ installation

files.

T24 The T24 directory contains all Transact-related libraries.

TAFJ The TAFJ directory contains TAFJ runtime libraries.

UXPBrowser The UXPBrowser directory contains UXP browser artefacts (New

Browser).

4.4 Setting the environment variables

Before starting the Transact or TAFJ installation, you need to set up the system environment variables.

Procedure

1. In the Linux shell, navigate to the user directory.

cd /home/user_home_dir
2. Open the .bash_profile file in a text editor.
vi .bash_profile
3. Enter the system environment variables as shown below. The bnk directory does not yet exist in your
environment now but will be required later.

#TEMENOS_HOME
export TEMENOS_HOME=/srv/Temenos
echo $TEMENOS_HOME

#TAFJ_HOME
export TAFJ_HOME=$TEMENOS_HOME/TAFJ
echo $TAFJ_HOME

#T24_HOME

16
Stack 1 Red Hat – JBoss runbook, version 4.0

export T24_HOME=$TEMENOS_HOME/T24/bnk/UD
echo $T24_HOME

#UXPBROWSER
export UXPBROWSER=$TEMENOS_HOME/UXPBrowser
echo $UXPBROWSER

#BRP_HOME
export BRP_HOME=/srv/Temenos
echo $BRP_HOME

#JAVA_HOME
export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.265.b01-0.el8_
2.x86_64

#JBOSS_HOME
export JBOSS_HOME=/srv/Temenos/3rdParty/AS/jboss-eap-7.3
echo $JBOSS_HOME

#PATH
export PATH=$PATH:$JAVA_HOME/bin:$TAFJ_HOME/bin:$JBOSS_HOME/bin

4. Execute .bash_profile to export the variables.

4.5 Verifying the system for third-party software

Procedure

1. Verify that JDK 1.8 is installed by executing java –version in the Linux shell.

2. Add the JAVA_HOME environment variable and $JAVA_HOME/bin to the $PATH variable.
3. Check that you can connect to your database. Use the Oracle SQL Developer tool to connect to an Oracle
database or SQL Server Management Studio to connect to an SQL Server database.

17
Stack 1 Red Hat – JBoss runbook, version 4.0

4. Verify that JBoss EAP 7.3 is installed and JBOSS_HOME has been set as an environment variable. You
should see the following folders in $JBOSS_HOME.

18
Stack 1 Red Hat – JBoss runbook, version 4.0

5 Installing TAFJ runtime

This chapter shows how to set up the TAFJ runtime.

5.1 Preparing the Transact and TAFJ installation files

Procedure

1. Obtain the MB.202008.TAFJ202008.bnk.tar.gz and TAFJ.DEV.202008.1.tar.gz files

from your account manager.
2. Upload the Transact artefacts (MB.202008.TAFJ202008.bnk.tar.gz) from the temporary folder
on your machine to the $TEMENOS_HOME/inst/t24inst directory on the application server.
3. Copy the TAFJ artefacts (TAFJ.DEV.202008.1.tar.gz) from the temporary folder on your machine
to the $TEMENOS_HOME/inst/tafjinst directory on the application server.

5.2 Extracting Transact

Procedure

1. In the Linux shell, navigate to $TEMENOS_HOME/inst/t24inst.

2. Extract the gz file. It will be extracted as a bnk folder.
tar –xvf MB.202008.TAFJ202008.bnk.tar.gz
3. Move the bnk directory to the T24 directory.
mv bnk $TEMENOS_HOME/T24

5.3 Installing TAFJ

Before you begin

Ensure that you have set JAVA_HOME to the correct path.

Procedure

19
Stack 1 Red Hat – JBoss runbook, version 4.0

1. In the Linux shell, navigate to $TEMENOS_HOME/inst/tafjinst.

2. Extract the .gz file.
tar –xvf TAFJ.DEV.202008.1.tar.gz

3. Change the permissions on Setup_TAFJ.DEV.202008.1.sh and TAFJ.DEV.202008.1.jar

to execute.
chmod 755 Setup_TAFJ.DEV.202008.1.sh TAFJ.DEV.202008.1.jar
4. Execute Setup_TAFJ.DEV.202008.1.sh and press Enter..

5. When prompted to enter the installation directory, specify the path to $TAFJ_HOME and press Enter.

20
Stack 1 Red Hat – JBoss runbook, version 4.0

6. Optional: Specify the Eclipse home directory and press Enter.

7. Enter y to confirm the path to the conf directory and press Enter.

8. Press Enter to finish the installation of TAFJ runtime.

The following directories are available in $TAFJ_HOME.

21
Stack 1 Red Hat – JBoss runbook, version 4.0

9. Change the permissions on the $TAFJ_HOME/bin directory to execute.

chmod 755 $TAFJ_HOME/bin/*
10. Verify that the chmod command completed successfully.
cd bin
ls -ltr

22
Stack 1 Red Hat – JBoss runbook, version 4.0

11. Execute tVersion to verify the TAFJ version.

5.4 Deploying the database driver

TAFJ uses JDBC drivers to establish a connection with the Transact database. Database drivers are available in the
$TAFJ_HOME/dbdrivers directory. For your deployment you must use the latest version of the respective
database driver downloaded from the vendor’s web site.

5.4.1 Deploying the driver for MS SQL Server

Procedure

1. Download the JDBC SQL driver from Microsoft web site.

2. Copy the sqljdbc42.jar file to the $TAFJ_HOME/ext directory.

5.4.2 Deploying the driver for NuoDB

Copy the nuodb-jdbc-21.0.0.jar file to the $TAFJ_HOME/ext directory.

cp $TAFJ_HOME/dbdrivers/nuodb-jdbc-21.0.0/nuodb-jdbc-21.0.0.jar $TAFJ_
HOME/ext.

5.4.3 Deploying the drivers for Oracle Database

Procedure

23
Stack 1 Red Hat – JBoss runbook, version 4.0

1. Download the Oracle 19c drivers from the Oracle web site. The following are the required drivers:
l ojdbc8.jar
l oraclepki.jar
l orai18n.jar
l orai18n-collation.jar
l orai18n-mapping.jar
l ucp.jar
l xdb6.jar
l xmlparserv2_sans_jaxp_services.jar
2. Copy the JAR files to $TAFJ_HOME/ext directory.
cp -r $TAFJ_HOME/dbdrivers/oracle-12c $TAFJ_HOME/ext

5.4.4 Deploying the driver for PostgreSQL

Procedure

1. Download the JDBC SQL driver from the www.postgresql.org web site.
2. Copy the postgresql-42.2.6.jar file to the $TAFJ_HOME/ext directory.

24
Stack 1 Red Hat – JBoss runbook, version 4.0

6 Configuring TAFJ
This chapter shows how to configure TAFJ runtime to set up a standalone (outside an application server) Transact
instance.

TAFJ does not use environment variables. Instead, it uses a properties file (*.properties) for its internal
configuration. Properties files are stored under the $TAFJ_HOME/conf directory. The default property file is
tafj.properties.

6.1 Configuring tafj.properties

Procedure

1. In the Linux shell, navigate to $TAFJ_HOME/conf.

2. Open the tafj.properties file in a text editor.
3. Verify that tafj.home points to the correct location.

4. Set temn.tafj.directory.precompile to the path of Transact libraries.

5. Set the database connection parameters.

a. Under the Database setup header section, provide the relevant temn.tafj.jdbc.url.
b. Provide the relevant driver information in temn.tafj.jdbc.driver.
c. Provide database user name and password.

MS SQL Server
In temn.tafj.jdbc.url change integratedSecurity to false.

25
Stack 1 Red Hat – JBoss runbook, version 4.0

NuoDB

Oracle Database

PostgreSQL

26
Stack 1 Red Hat – JBoss runbook, version 4.0

6. Set the UD directory path.

7. Set the value of temn.tafj.jdbc.write.use.merge and

temn.tafj.jdbc.write.use.merge.no.xml to false to improve the database performance.

27
Stack 1 Red Hat – JBoss runbook, version 4.0

8. Set the value of temn.tafj.locking.mode to DATABASE.

Note:
l DATABASE locking mode is recommended for releases 201809 and higher. TAFJ locks records
using native database locks when this locking mode is used.
l For information on how to create and populate the TAFJ_HASHLOCKS table which is required for
DATABASE locking mode see the TAFJ Lock Manager guide (TAFJ-Lock Manager.pdf)
that is in $TAFJ_HOME/doc.

9. To enable SAMPLE to work with PostgreSQL, set the temn.tafj.jdbc.use.rownum.at.end

property to true.

6.2 Verifying TAFJ installation

Procedure

1. In the Linux shell, navigate to $TAFJ_HOME/bin.

2. Execute the tDiag command to verify that your TAFJ installation is successful and that the project properties
file is correctly set. This command shows you:
l What location $TAFJ_HOME is set to.
l JDK version.
l TAFJ version.

28
Stack 1 Red Hat – JBoss runbook, version 4.0

l The default project, and the details of all the projects that are set in $TAFJ_HOME/conf.

29
Stack 1 Red Hat – JBoss runbook, version 4.0

This completes the TAFJ runtime setup.

30
Stack 1 Red Hat – JBoss runbook, version 4.0

7 Sanity check
Verify that your Transact standalone installation is successful before you proceed to deploy the application server.
This chapter shows how to perform two sanity checks.

7.1 Accessing Classic

You can use Transact Classic, which is one of the Transact user interfaces, to access Transact.

Procedure

1. In the Linux shell, navigate to $TAFJ_HOME/bin.

2. Run the command tRun EX.

31
Stack 1 Red Hat – JBoss runbook, version 4.0

3. Log in using a valid Transact user name and password.

4. Launch any Transact application, for example SPF S SYSTEM.

32
Stack 1 Red Hat – JBoss runbook, version 4.0

7.2 Launching DBTools

DBTools is a TAFJ tool that provides a console to execute database commands. Only authenticated users can
access the console.

Procedure

1. In the Linux shell, navigate to $TAFJ_HOME/bin.

2. Create a TAFJ user by passing user name and password parameters to the tUserMgnt.sh utility.
./tUserMgnt --Add -u tafjuser -p Temenos@1234
The USER CREATION SUCCESSFUL message is displayed.
3. Launch DBTools passing the TAFJ user credentials as parameters.
./DBTools -u tafjuser -p Temenos@1234
The DBTools console is launched.
4. View the database name, database user name and IP address, which are displayed in the lower left part of the
screen.

33
Stack 1 Red Hat – JBoss runbook, version 4.0

8 Configuring JBoss modules

JBoss EAP 7.3 uses a modular class loading system for controlling the class paths of deployed applications. The
modular class loader separates all Java classes into logical groups called modules. Each module can define
dependencies on other modules.

To install a module on JBoss EAP 7.3, create a path under the $JBOSS_HOME/modules directory. Under this
path, install the JAR libraries that are part of the module and the module.xml file that describes the module and
the dependencies on other modules. You need to create three modules on your application server.

l Database driver module

l TAFJ module
l Transact module

8.1 Configuring the database driver module

For Transact to connect to a data source, a module should contain your data source vendor’s JDBC drivers for JBoss
to use.

8.1.1 Configuring the module for Microsoft SQL Server

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/modules.

2. Create the following directory structure under the modules directory.
mkdir -p com/microsoft/sqlserver/main
3. Copy module.xml from $TAFJ_HOME to the main directory.
cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/microsoft/sqlserver/main/
module.xml $JBOSS_HOME/modules/com/microsoft/sqlserver/jdbc/main
4. Copy the corresponding database driver to the main directory.
5. Verify that the copy was successful.

34
Stack 1 Red Hat – JBoss runbook, version 4.0

6. Open the copied module.xml file to check the name of driver JAR file. The module name should be same
as the folder path for that module.

8.1.2 Configuring the module for NuoDB

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/modules.

2. Create the following directory structure under the modules directory.
mkdir -p com/nuodb/jdbc/main
3. Copy module.xml from $TAFJ_HOME to the main directory.
cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/nuodb/jdbc/main/module.xm
l $JBOSS_HOME/modules/com/nuodb/jdbc/main
4. Copy the corresponding database driver to the main directory.
cp $TAFJ_HOME/ext/nuodb-jdbc-21.0.0.jar $JBOSS_
HOME/modules/com/nuodb/jdbc/main
5. Verify that the copy was successful.

6. Open the copied module.xml file to check the name of driver JAR file. The module name should be same

35
Stack 1 Red Hat – JBoss runbook, version 4.0

as the folder path for that module.

8.1.3 Configuring the module for Oracle Database

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/modules.

2. Create the following directory structure under the modules directory.
mkdir -p com/oracle/ora18c/main
3. Copy module.xml from $TAFJ_HOME to the main directory.
cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/oracle/ora12c/main/module
.xml $JBOSS_HOME/modules/com/oracle/ora18c/main
4. Copy the corresponding Oracle drivers from $TAFJ_HOME/ext to the $JBOSS_
HOME/modules/com/oracle/ora18c/main directory.
cp $TAFJ_HOME/dbdrivers/oracle-12c/* $JBOSS_
HOME/modules/com/oracle/ora18c/main

36
Stack 1 Red Hat – JBoss runbook, version 4.0

5. Check whether the copy was successful.

6. Open the copied module.xml file and change the module name to ora18c.

8.1.4 Configuring the module for PostgreSQL

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/modules.

2. Create the following directory structure under the modules directory.
mkdir -p com/postgres/jdbc/main
3. Copy module.xml from $TAFJ_HOME to the main directory.
cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/postgres/jdbc/main/module
.xml $JBOSS_HOME/modules/com/postgres/jdbc/main
4. Copy the corresponding Oracle drivers from $TAFJ_HOME/ext to the $JBOSS_
HOME/modules/com/postgres/jdbc/main directory.

37
Stack 1 Red Hat – JBoss runbook, version 4.0

5. Check whether the copy was successful.

6. Open the copied module.xml file and ensure the module name is set to com.postgres.jdbc.

8.2 Configuring the TAFJ module

This module contains the TAFJ libraries that are in the lib and ext directories. They have a dependency on the
database driver module.

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/modules/com.

2. Create the following directory structure under the com folder.
mkdir -p temenos/tafj/main
3. Copy the module.xml file from a directory under $TAFJ_HOME to the following directory structure under
$JBOSS_HOME/modules.
cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/temenos/tafj/main/module.
xml $JBOSS_HOME/modules/com/temenos/tafj/main
4. Change to $JBOSS_HOME/modules/com/temenos/tafj/main.
5. Create symbolic links to the $TAFJ_HOME/lib and $TAFJ_HOME/ext directories.
ln -s $TAFJ_HOME/lib lib
ln -s $TAFJ_HOME/ext ext

38
Stack 1 Red Hat – JBoss runbook, version 4.0

6. Open the copied module.xml file in a text editor, uncomment the database driver module dependency
under the <dependencies> section according to the database used.
l If you are using Microsoft SQL Server, uncomment the following dependency:

l If you are using NuoDB, uncomment the following dependency:

l If you are using Oracle Database, uncomment the following dependency:

39
Stack 1 Red Hat – JBoss runbook, version 4.0

l If you are using PostgreSQL, uncomment the following dependency:

8.3 Configuring the Transact module

This module contains the Transact JAR files and has a dependency on the TAFJ module that you created earlier.

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/modules/com/temenos.

2. Create the following directory structure under the temenos directory.
mkdir -p t24/main
3. Change to $JBOSS_HOME/modules/com/temenos/t24/main.
4. Create a symbolic link to $TEMENOS_HOME/T24/bnk/t24lib.
ln -s $TEMENOS_HOME/T24/bnk/t24lib lib

8.4 Generating the Transact module.xml file

You can use the JBossTools utility to generate the module.xml file. This utility is provided by Temenos and it is
available in the $TAFJ_HOME/bin directory.

Procedure

40
Stack 1 Red Hat – JBoss runbook, version 4.0

1. In the Linux shell, navigate to $TAFJ_HOME/bin.

2. Create the module.xml file by running the following command.
JBossTools com.temenos.t24 $TEMENOS_HOME/T24/bnk/t24lib $JBOSS_
HOME/modules/com/temenos/t24/main lib –tafjdep
The following screen capture shows the successful completion of executing the above command.

3. Open module.xml and verify that the TAFJ module is added as a dependency in the <dependencies>
section.

8.4.1 JBossTools command for generating module.xml

Command syntax
JBossTools module_name path_to_jars dest root_prefix -tafjdep

Options Description

module_name Name of the JBoss module. It must be the same as the directory path created for the
module.

path_to_jars The list of directories that you want to parse.

dest The path to the directory where the module.xml is to be generated.

root_prefix Name of the link if module.xml is at the same level as the link.

-tafjdep Option to add TAFJ module dependencies in the dependencies section.

41
Stack 1 Red Hat – JBoss runbook, version 4.0

9 Configuring standalone profile on the

application server
JBoss Enterprise Application Platform runs in one of two operating modes: as a standalone server or in a managed
domain. This runbook covers standalone installation.

9.1 Starting JBoss with J2EE 8 full profile

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/standalone/configuration.

There are several standalone profiles in JBoss. standalone-full.xml is a sample configuration file for
a standalone server that includes support for every possible subsystem except for those required for high
availability.
2. To start the application server using a full J2EE profile, copy and rename the standalone-full.xml
file that is in the configuration directory to name.xml (For example, Transact.xml).
cp standalone-full.xml Transact.xml
3. Change to $JBOSS_HOME/bin.
4. Open the standalone.conf file in a text editor and, on a new line, enter the following new JAVA_OPTS
definition.
JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF-8 -Dtafj.home=$TAFJ_HOME"
This definition adds mandatory system properties tafj.home and file.encoding. TAFJ uses UTF-8
encoding.
Example:

5. Refine your maximum heap size (-mx) based on your expected load on the application server.
Example:

42
Stack 1 Red Hat – JBoss runbook, version 4.0

Note:
When setting up the max heap size (-mx), set the initial heap size (-ms) to the same value as the max
heap size. This prevents the JVM from consuming cycles to expand the heap since Transact starts with a
large memory footprint.

6. Start JBoss using the following command. To use the configuration in Transact.xml, you must amend
the JBoss startup command and explicitly refer to this configuration file using the option --server-
config.
standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 --server-
config=Transact.xml

9.2 Configuring the standalone full profile

To deploy Transact on TAFJ in EAP, you must configure various subsystems in the Transact.xml file. TAFJ
uses the management command line interface tool to automate the process of configuring the J2EE profiles.

You can launch JBoss CLI from the $JBOSS_HOME/bin directory by running the jboss-cli.sh script. It
takes the following two arguments: --file and --properties

The --file argument enables CLI commands to be provided from a text file. The $TAFJ_
HOME/appserver/jboss/jboss7eap/jboss-cli directory has a CLI script file T24Setup.cli.
This script has commands to update the profiles specific for Transact deployment.

Procedure

1. In the Linux shell, navigate to $TAFJ_HOME/appserver/jboss/jboss7eap/jboss-cli and

open T24Setup.cli.

43
Stack 1 Red Hat – JBoss runbook, version 4.0

2. In the Drivers section, uncomment the driver parameters according to the database used.

Microsoft SQL Server

NuoDB

Oracle Database
Change the driver name to ora18c.

PostgreSQL

44
Stack 1 Red Hat – JBoss runbook, version 4.0

Note:
The --properties argument allows to pass user-specific properties to the script file from a property
file. You will find tafj.properties in the same location.

3. Open tafj.properties.
4. Provide the TAFJ_HOME, DB_URL, DB_DRIVER, DB_USER and DB_PWD parameters.

Microsoft SQL Server

NuoDB

Oracle Database

45
Stack 1 Red Hat – JBoss runbook, version 4.0

PostgreSQL

5. To resolve the user-specific system properties in tafj.properties that will be passed as command
argument to JBoss CLI command, set the value of resolve-parameter-values to true in
$JBOSS_HOME/bin/jboss-cli.xml. Check whether validate-operation-requests is
set to true.

46
Stack 1 Red Hat – JBoss runbook, version 4.0

6. In the Linux shell, navigate to $JBOSS_HOME/bin and run the jboss-cli command.
jboss-cli.sh --connect --file=$TAFJ_
HOME/appserver/jboss/jboss7eap/jboss-cli/T24Setup.cli --
properties=$TAFJ_HOME/appserver/jboss/jboss7eap/jboss-
cli/tafj.properties

On successful execution, the command updates the required subsystems in Transact.xml which start up
JBoss. The following screen capture shows the successful execution of the jboss-cli command.

The scripts will add the following to the standalone configuration file. (Transact.xml)
l System properties
l Drivers
l Data sources
l Global modules (TAFJ and Transact)
l JMS Pools
l JMS Queues
7. Stop the JBoss instance as the configuration of JBoss with Transact and TAFJ is now complete. The next step
is to deploy the artefacts.

47
Stack 1 Red Hat – JBoss runbook, version 4.0

10 Extracting UXP Browser artefacts

This chapter contains the steps that need to be done before deploying the Transact and TAFJ artefacts and are only
required if you are deploying UXP Browser.

Before you begin

You need to obtain the UXP-Browser.202008.zip and IIRISR18_CatalogServices_TAFJ_

202008.0.1.zip files from your account manager. Both packages are shipped in the Model Bank package.

Procedure

1. Upload the UXP-Browser.202008.zip file to the $UXPBROWSER directory on the application server.
2. In the Linux shell, navigate to $UXPBROWSER and extract the files from the UXP-
Browser.202008.zip file.
unzip UXP-Browser.202008.zip
The following files are extracted:
l Authenticator-202008.0.1.war
l Browser-202008.0.1.war
l browser-iris-202008.0.1.war
l browser-iris-tafc-202008.0.1.war
l irf-rp-services-202008.0.1.war
l ResourceServerWar-202008.0.1.war
l StaticFiles-202008.1.zip
l uxpb-god-properties-202008.0.1.zip
l UXPB-Tools-202008.0.1.zip
3. Locate the IRISR18_CatalogServices_TAFJ_202008.0.1.zip file in your Model Bank
package on your local machine and extract it.
4. Upload the extracted irf-t24catalog-services-202008.0.1.war file to the $UXPBROWSER
directory on your application server.
5. Optional: Rename the required artefact file names by removing the release version information:
mv Authenticator-202008.0.1.war Authenticator.war
mv Browser-202008.0.1.war Browser.war
mv irf-rp-services-202008.0.1.war irf-rp-services.war

48
Stack 1 Red Hat – JBoss runbook, version 4.0

mv irf-t24catalog-services-202008.0.1.war irf-t24catalog-
services.war
mv ResourceServerWar-202008.0.1.war ResourceServer.war

49
Stack 1 Red Hat – JBoss runbook, version 4.0

11 Configuring and deploying Transact and

TAFJ artefacts
The final step in this setup is to deploy the Transact UI components UXP Browser (UXPB) and BrowserWeb. UXPB
is the Temenos' latest user interface for working with Transact. BrowserWeb is its antecedent. This runbook does
not cover deployment of other product user interfaces such as Temenos Connect Internet Banking (TCIB) and
Mobile Banking (TCMB).

11.1 Deploying TAFJJEE_EAR.ear and TAFJ Spooler plugins

Procedure

1. In the Linux shell, navigate to $TAFJ_HOME/appserver.

2. Copy the TAFJSpoolerPlugins.rar file to the $JBOSS_HOME/standalone/deployments
directory.
cp TAFJSpoolerPlugins.rar $JBOSS_HOME/standalone/deployments
3. Change to $TAFJ_HOME/appserver/jboss/jboss7eap.
4. Copy TAFJJEE_EAR.ear to the $JBOSS_HOME/standalone/deployments directory.
cp TAFJJEE_EAR.ear $JBOSS_HOME/standalone/deployments

11.2 Deploying BrowserWeb

Before you begin

You need to obtain the BrowserWeb-202008.00.tar file from your account manager. BrowserWeb is not
shipped in the Model Bank package.

Procedure

1. Upload the BrowserWeb-202008.00.tar file to the $TEMENOS_HOME/inst directory.

2. At the Linux command line, navigate to $TEMENOS_HOME/inst and extract the TAR file.
tar -xvf BrowserWeb-202008.00.tar
3. Navigate to the extracted BrowserWeb-202008.00 directory and copy BrowserWeb.war to
$JBOSS_HOME/standalone/deployments.
cd BrowserWeb-202008.00

50
Stack 1 Red Hat – JBoss runbook, version 4.0

cp BrowserWeb.war $JBOSS_HOME/standalone/deployments

11.3 Modifying Browser.war

Procedure

1. At the Linux command line, navigate to $UXPBROWSER.

2. Extract Browser.war in a temporary directory under $UXPBROWSER, for example tmp-uxpb.
mkdir tmp-uxpb
cp Browser.war tmp-uxpb
cd tmp-uxpb
jar -xf Browser.war
3. Navigate to WEB-INF and open SSOAPI.properties in an editor.
cd WEB-INF
vi SSOAPI.properties
4. Provide the port number and IP address or host name of your application server. Example:

SSOAPI.T24REMOTE.URL=http://10.23.50.153:9089/Authenticator/auth

5. Save the file.

6. Delete the previous version of the WAR file.
cd ..
rm Browser.war
7. Re-package the WAR file and copy it back to the UXPBrowser directory.
jar cf Browser.war *
cp Browser.war $UXPBROWSER

11.4 Modifying irf-rp-services.war

Procedure

51
Stack 1 Red Hat – JBoss runbook, version 4.0

1. At the Linux command line, change to $UXPBROWSER.

2. Extract irf-rp-services.war to a temporary directory, for example tmp-irf-rp-srv.
mkdir tmp-irf-rp-srv
cp irf-rp-services.war tmp-irf-rp-srv
cd tmp-irf-rp-srv
jar -xf irf-rp-services.war
3. Navigate to WEB-INF/classes.
4. Open connection.properties in your text editor and provide the IP address or host name of your
application server and the port. Example:

# Common EJB Remote Configurations

RemoteConnectionHosts=10.23.50.153
RemoteConnectionPorts=9089
transportLayerUser=SSOUSER1
transportLayerCredential=123456

5. Delete the previous version of the WAR file.

cd ../../
rm irf-rp-services.war
6. Re-package the WAR file and copy it back to the $UXPBrowser directory.
jar cf irf-rp-services.war *
cp Browser.war $UXPBROWSER

11.5 Modifying irf-t24catalog-services.war

Procedure

1. At the Linux command line, change to $UXPBROWSER.

2. Extract irf-t24catalog-services.war to a temporary subdirectory in $UXP_BROWSER, for
example tmp-irf-cat-srv.
mkdir tmp-irf-cat-srv
cp irf-t24catalog-services.war tmp-irf-cat-srv
cd tmp-irf-cat-srv

52
Stack 1 Red Hat – JBoss runbook, version 4.0

jar -xf irf-t24catalog-services.war

3. Navigate to WEB-INF/classes.
4. Open connection.properties in your text editor and provide the IP address or host name of your
application server and the port. Example:

# Common EJB Remote Configurations

RemoteConnectionHosts=10.23.50.153
RemoteConnectionPorts=9089
transportLayerUser=SSOUSER1
transportLayerCredential=123456

5. Delete the previous version of the WAR file.

cd ../../
rm irf-t24catalog-services.war
6. Re-package the WAR file and copy it back to the UXPBrowser directory.
jar cf irf-t24catalog-services.war *
cp irf-t24catalog-services.war $UXPBROWSER

11.6 Embedding the database driver in ResourceServer.war

Procedure

1. At the Linux command line, change to $UXPBROWSER.

2. Extract ResourceServer.war to a temporary subdirectory in $UXP_BROWSER, for example tmp-
res-srv.
mkdir tmp-res-srv
cp ResourceServer.war tmp-res-srv
cd tmp-res-srv
jar -xf ResourceServer.war
3. Copy the database driver(s) to ResourceServerWar.war/WEB-INF/lib.

MS SQL Server
cp $TAFJ_HOME/ext/sqljdbc42.jar $UXPBROWSER/tmp-res-srv/WEB-
INF/lib

53
Stack 1 Red Hat – JBoss runbook, version 4.0

NuoDB
cp $TAFJ_HOME/ext/nuodb-jdbc-21.0.0.jar $UXPBROWSER/tmp-res-
srv/WEB-INF/lib

Oracle
cp $TAFJ_HOME/ext/ojdbc8.jar $UXPBROWSER/tmp-res-srv/WEB-INF/lib

PostgreSQL
cp $TAFJ_HOME/ext/postgresql-42.2.6.jar $UXPBROWSER/tmp-res-
srv/WEB-INF/lib

4. Delete the previous version of the WAR file.

rm ResourceServer.war
5. Re-package the WAR file and copy it back to the UXPBrowser directory.
jar cf ResourceServer.war *
mv ResourceServer.war $UXPBROWSER

11.7 Modifying the required EJB JAR files

Procedure

1. To prepare the required EJB JAR files, copy them to the $UXPBROWSER directory:
cd $TEMENOS_HOME/T24/bnk/Extensions/EB_AuthenticationService/t24ejb
cp t24-EB_AuthenticationService-ejb.jar $UXPBROWSER
cd $TEMENOS_HOME/T24/bnk/Extensions/EB_CatalogService/t24ejb
cp t24-EB_CatalogService-ejb.jar $UXPBROWSER
cd $TEMENOS_HOME/T24/bnk/Extensions/EB_
ResourceProviderService/t24ejb
cp t24-EB_ResourceProviderService-ejb.jar $UXPBROWSER
2. Modify t24-EB_AuthenticationService-ejb.jar.
a. Copy and extract the file and in a temporary subdirectory under $UXPBROWSER, for example tmp-
ejb-auth.
cd $UXPBROWSER

54
Stack 1 Red Hat – JBoss runbook, version 4.0

mv t24-EB_AuthenticationService-ejb.jar tmp-ejb-auth
cd tmp-ejb-auth
jar -xf t24-EB_AuthenticationService-ejb.jar
b. Navigate to META-INF and open the ejb-jar.xml file in an editor.
c. Change the <transactiontype> value from Container to Bean, as illustrated below.

d. In <env-entry-value>, specify either IRISPA or IFPA as the OFS_SOURCE.

e. Save the file.

f. Open jboss-ejb3.xml file in an editor and ensure that the security domain is set to other.

g. Save the file.

h. Re-package the JAR file and upload it to the UXPBrowser directory.
cd ..
rm t24-EB_AuthenticationService-ejb.jar
jar cf t24-EB_AuthenticationService-ejb.jar *
mv t24-EB_AuthenticationService-ejb.jar $UXPBROWSER

55
Stack 1 Red Hat – JBoss runbook, version 4.0

3. Modify t24-EB_CatalogService-ejb.jar.
a. Copy and extract the file and in a temporary subdirectory under $UXPBROWSER, for example tmp-
ejb-cat-srv.
cd $UXPBROWSER
mv t24-EB_CatalogService-ejb.jar tmp-ejb-cat-srv
cd tmp-ejb-cat-srv
jar -xf t24-EB_CatalogService-ejb.jar
b. Navigate to META-INF and open the ejb-jar.xml file in an editor.
c. Change the <transactiontype> value from Container to Bean, as illustrated below.

d. In <env-entry-value>, specify either IRISPA or IFPA as the OFS_SOURCE.

e. Save the file.

f. Open jboss-ejb3.xml file in an editor and ensure that the security domain is set to other.

g. Save the file.

56
Stack 1 Red Hat – JBoss runbook, version 4.0

h. Re-package the JAR file and upload it to the UXPBrowser directory.

cd ..
rm t24-EB_CatalogService-ejb.jar
jar cf t24-EB_CatalogService-ejb.jar *
mv t24-EB_CatalogService-ejb.jar $UXPBROWSER
4. Perform the same steps as above to modify ejb-jar.xml and jboss-ejb3.xml in t24-EB_
ResourceProviderService-ejb.jar:
a. Copy and extract the file and in a temporary subdirectory under $UXPBROWSER, for example tmp-
ejb-res-prov-srv.
cd $UXPBROWSER
mv t24-EB_ResourceProviderService-ejb.jar tmp-ejb-res-prov-srv
cd tmp-ejb-res-prov-srv
jar -xf t24-EB_ResourceProviderService-ejb.jar
b. Navigate to META-INF and open the ejb-jar.xml file in an editor.
c. Change the <transactiontype> value from Container to Bean, as illustrated below.

d. In <env-entry>, specify either IRISPA or IFPA as the OFS_SOURCE.

e. Save the file.

57
Stack 1 Red Hat – JBoss runbook, version 4.0

f. Open jboss-ejb3.xml file in an editor and ensure that the security domain is set to other.

g. Save the file.

h. Re-package the JAR file and upload it to the UXPBrowser directory.
cd ..
rm t24-EB_ResourceProviderService-ejb.jar
jar cf t24-EB_ResourceProviderService-ejb.jar *
mv t24-EB_ResourceProviderService-ejb.jar $UXPBROWSER

11.8 Configuring the SSOUSER1 user in JBoss

You need to create the SSOUSER1 user which will be used by the Resource Provider (irf-rp-
services.war) and Catalog (irf-t24catalog-services.war) services.

Procedure

1. At the Linux command line, navigate to $JBOSS_HOME/bin.

2. Run the add-user.sh script:
./add-user.sh
3. Specify Application user (option b) as the type of user.

What type of user do you wish to add?

a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a):b

4. Provide the SSOUSER1 user name and password (here 123456).

aEnter the details of the new user to add.

Using realm 'ApplicationRealm' as discovered from the existing property
files.
Username : SSOUSER1

58
Stack 1 Red Hat – JBoss runbook, version 4.0

Password recommendations are listed below. To modify these restrictions

edit the add-user.properties configuration file.
- The password should be different from the username
- The password should not be one of the following restricted values
{root, admin, administrator}
- The password should contain at least 8 characters, 1 alphabetic
character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
Password :

5. Confirm that you want to use the password and re-enter it.

WFLYDM0099: Password should have at least 8 characters!

Are you sure you want to use the password entered yes/no? yes
Re-enter Password :

6. Specify the group the user should belong to; here t24user.

What groups do you want this user to belong to? (Please enter a comma
separated list, or leave blank for none)[ ]: t24user

7. Confirm the addition of the user to the realm ApplicationRealm by providing the answer yes.

About to add user 'SSOUSER1' for realm 'ApplicationRealm'

Is this correct yes/no? yes

The user has been added to JBoss configuration files.

Added user 'SSOUSER1' to file '/srv/Temenos/3rdParty/AS/jboss-eap-

7.3/standalone/configuration/application-users.properties'
Added user 'SSOUSER1' to file '/srv/Temenos/3rdParty/AS/jboss-eap-
7.3/domain/configuration/application-users.properties'
Added user 'SSOUSER1' with groups t24user to file
'/srv/Temenos/3rdParty/AS/jboss-eap-
7.3/standalone/configuration/application-roles.properties'
Added user 'SSOUSER1' with groups t24user to file
'/srv/Temenos/3rdParty/AS/jboss-eap-7.3/domain/configuration/application-
roles.properties'

59
Stack 1 Red Hat – JBoss runbook, version 4.0

8. For the last question, provide the answer yes.

Is this new user going to be used for one AS process to connect to another
AS process?
e.g. for a slave host controller connecting to the master or for a
Remoting connection for server to server EJB calls.
yes/no? yes

The user has been created and the following message is displayed at the command line interface:
To represent the user add the following to the server-identities
definition
<secret value="MTIzNDU2" />
9. Open the Transact.xml file that is in /srv/Temenos/3rdParty/AS/jboss-eap-
7.2/standalone/configuration in a text editor and add under <server-identities> the
tag that you generated in the previous step:

<server-identities>
<ssl>
<keystore path="application.keystore" relative-
to="jboss.server.config.dir" keystore-password="password" alias="server"
key-password="password" generate-self-signed-certificate-
host="localhost"/>
</ssl>
<secret value="MTIzNDU2" />
</server-identities>

11.9 Configuring UXP Browser in GOD mode

Before you begin

You need to locate the encryption utility (EncryptPassword.jar) in your Model Bank package and then
upload it to the $UXPBROWSER directory on the application server. The JAR file is available at the following
location:
Model_Bank_package.zip/UXP-Browser.zip/UXPB-
Tools.zip/EncryptPassword.jar

Procedure

60
Stack 1 Red Hat – JBoss runbook, version 4.0

1. At the command line, change to $TEMENOS_HOME and create the properties directory.
cd $TEMENOS_HOME
mkdir properties
2. Change to the $UXPBROWSER directory and extract the uxpb-god-properties-
202008.0.1.zip file.
cd $UXPBROWSER
unzip uxpb-god-properties-202008.0.1.zip
3. Ccopy the two properties files to the directory where they will be stored permanently:
cp BRPRuntimeProperties.properties $TEMENOS_HOME/properties
cp RSDefaultProperties.properties $TEMENOS_HOME/properties
4. Encrypt the IRIS system and JDBC user passwords using the Temenos Encryption Utility
(EncryptPassword.jar) – run the following command:
java -jar EncryptPassword.jar pwd_to_be_encrypted
Example:
java -jar EncryptPassword.jar 123456
5. Save the encrypted password in a secure location.
6. Edit the BRPRuntimeProperties.properties file in a text editor - perform the following steps:
a. Provide the Transact user name and the encrypted password (here 123456):

browser.options.irisSystemUser=AUTHOR
browser.options.irisSystemPassword=vSd3/5UdSJc=

b. Uncomment the following lines and provide the Resource Provider, Catalog services, Resource Server
and Authenticator URLs with the IP address or host name of your application server server:

browser.options.dynamicIRIS.rpService=http://10.23.50.153:9089/irf-rp-
services
browser.options.god.catalogService=http://10.23.50.153:9089/irf-
t24catalog-services

browser.options.resourceServer.url=
http://10.23.50.153:9089/ResourceServer
browser.options.remoteAuth.url=
http://10.23.50.153:9089/Authenticator/auth/logon

61
Stack 1 Red Hat – JBoss runbook, version 4.0

c. Save the file.

7. Edit the RSDefaultProperties.properties file in a text editor – provide the following and save
the file:
l Database URL
l Database user name
l The encrypted password for the database user
l Blob type
l Long type

Example:

aresource.server.options.tenant.jdbc.url.1=
jdbc:oracle:thin:@10.23.50.151:1521/MB202008
resource.server.options.tenant.jdbc.username.1=t24
resource.server.options.tenant.jdbc.password.1=g7nVhB+BoUY=
resource.server.options.tenant.jdbc.driver.1=oracle.jdbc.OracleDriver
resource.server.options.tenant.ddl.blobType.1=blob
resource.server.options.tenant.ddl.longType.1=number(19)

11.9.1 Resource Server database parameters for supported databases

Microsoft SQL Server

resource.server.options.tenant.jdbc.driver.1=
com.microsoft.sqlserver.jdbc.SQLServerDriver
resource.server.options.tenant.ddl.blobType.1=varbinary(max)
resource.server.options.tenant.ddl.longType.1=bigint

NuoDB

resource.server.options.tenant.jdbc.driver.1=com.nuodb.jdbc.Driver
resource.server.options.tenant.ddl.blobType.1=blob
resource.server.options.tenant.ddl.longType.1=bigint

Oracle Database

62
Stack 1 Red Hat – JBoss runbook, version 4.0

resource.server.options.tenant.jdbc.driver.1=oracle.jdbc.OracleDriver
resource.server.options.tenant.ddl.blobType.1=blob
resource.server.options.tenant.ddl.longType.1=number(19)

PostgreSQL

resource.server.options.tenant.jdbc.driver.1=org.postgresql.Driver
resource.server.options.tenant.ddl.blobType.1=bytea
resource.server.options.tenant.ddl.longType.1=bigint

11.10 Deploying UXP Browser artefacts in JBoss

The UXP Browser artefact is Browser.war. UXP Browser requests are routed through Interaction Framework.
Therefore, along with the Browser, you must also deploy the Authenticator application , Resource Provider and
Interaction Framework catalog services and also Resource server. This section is not applicable if you have skipped
"Extracting UXP Browser artefacts" on page 48.

Procedure

1. At the Linux command line, change to $UXPBROWSER.

2. Deploy the Authenticator component.
cp Authenticator.war $JBOSS_HOME/standalone/deployments
3. Deploy Browser.war.
cp Browser.war $JBOSS_HOME/standalone/deployments
4. Deploy Interaction Framework Resource Provider services.
cp irf-rp-services.war $JBOSS_HOME/standalone/deployments
5. Deploy Interaction Framework Catalog services.
cp irf-t24catalog-services.war $JBOSS_HOME/standalone/deployments
6. Deploy Resource Server.
cp ResourceServer.war $JBOSS_HOME/standalone/deployments

11.11 Deploying the EJB JAR files in JBoss

Procedure

63
Stack 1 Red Hat – JBoss runbook, version 4.0

1. Deploy the Authentication service.

cd $UXPBROWSER
cp t24-EB_AuthenticationService-ejb.jar $JBOSS_
HOME/standalone/deployments
2. Deploy the Catalog Service component.
cp t24-EB_CatalogService-ejb.jar $JBOSS_HOME/standalone/deployments
3. Deploy the Resource Provider service.
cp t24-EB_ResourceProviderService-ejb.jar $JBOSS_
HOME/standalone/deployments

11.12 Installing UXP Browser help text

Procedure

1. Upload T24.202008.HELPTEXT.zip to a temporary directory on the application server.

2. Extract the T24.202008.HELPTEXT.zip file to $TEMENOS_HOME.
unzip T24.202008.HELPTEXT.zip -d $TEMENOS_HOME
The help text XML files are extracted to the HELP.TEXT directory.

3. Add the help text directory path argument to your JBoss startup script.

$JBOSS_HOME/bin/standalone.sh --server-config=Transact.xml -
Djboss.http.port=9089 -Djboss.node.name=node1 -b 0.0.0.0 -
DedgeSystemPropertyFolder=/home/temenos/Temenos/properties -
DedgeSystemPropertyUpdaters=com.temenos.connect.system.GODSystemTestProper
ties -DBRP_HOME=/home/temenos/Temenos -
Dt24.helptext.xml.directory=/srv/Temenos/HELP.TEXT/HelpText

4. Restart the application server.

5. Verify that the text is displayed correctly in the Transact user interface:
a. Log in to UXP Browser interface and open an application, for example DATES.
b. Double-click a label in the UI.
The context sensitive help is displayed.

64
Stack 1 Red Hat – JBoss runbook, version 4.0

12 Deploying Transact component services

You will find the Transact component service APIs as Axis2 archives (t24-component_service-
jws.aar) in the extensions folder of the Transact distribution pack you have received. Deploy the archives
into the Apache Axis2 web archive file. The release version of Apache Axis2 used in this runbook is 1.6.2. The topics
in this chapter show you how to deploy axis2.war on your JBoss application server.

12.1 Packaging Axis2 archives

Procedure

1. Download axis2-1.6.2-war.zip from the Apache website to a directory on your computer.

2. Extract the contents of the compressed file.
3. Upload axis2.war to the $UXPBROWSER directory.
4. In the Linux shell, change to the $UXPBROWSER directory and create a new temporary directory, for example
tmp-axis2.
mkdir tmp-axis2
5. Copy axis2.war to the tmp-axis2 directory.
cp axis2.war tmp-axis2
6. In the tmp8 directory, extract the contents of the axis2.war file and navigate to WEB-INF/lib.
cd tmp-axis2
jar -xf axis2.war
cd WEB-INF/lib
7. Add the following dependency JAR files to the lib directory.
l commons-pool-1.5.5.jar
l spring-2.5.6.jar
8. Copy the component service archives from $T24_HOME/bnk/Extensions into the /WEB-
INF/services directory of the axis2.war file.

cp $TEMENOS_HOME/T24/bnk/Extensions/DS_
DesignStudioInstallerService/t24ws/t24-DS_
DesignStudioInstallerService-tafj-jws.aar $UXPBROWSER/tmp-axis2/WEB-
INF/services

65
Stack 1 Red Hat – JBoss runbook, version 4.0

cp $TEMENOS_HOME/T24/bnk/Extensions/EB_CatalogService/t24ws/t24-EB_
CatalogService-tafj-jws.aar $UXPBROWSER/tmp-axis2/WEB-INF/services

cp $TEMENOS_HOME/T24/bnk/Extensions/EB_
OFSConnectorService/t24ws/t24-EB_OFSConnectorService-tafj-jws.aar
$UXPBROWSER/tmp-axis2/WEB-INF/services

cp $TEMENOS_HOME/T24/bnk/Extensions/EB_
ResourceProviderService/t24ws/t24-EB_ResourceProviderService-tafj-
jws.aar $UXPBROWSER/tmp-axis2/WEB-INF/services

cp $TEMENOS_HOME/T24/bnk/Extensions/IF_
IntegrationFlowService/t24ws/t24-IF_IntegrationFlowService-tafj-
jws.aar $UXPBROWSER/tmp-axis2/WEB-INF/services

cp $TEMENOS_HOME/T24/bnk/Extensions/IF_
IntegrationFrameworkService/t24ws/t24-IF_
IntegrationFrameworkService-tafj-jws.aar $UXPBROWSER/tmp-axis2/WEB-
INF/services

cp $TEMENOS_HOME/T24/bnk/Extensions/IF_
IntegrationLandscapeService/t24ws/t24-IF_
IntegrationLandscapeService-tafj-jws.aar $UXPBROWSER/tmp-axis2/WEB-
INF/services

9. Open the /WEB-INF/services/services.list file and add the names of the component service
archives that you added to the services directory.

66
Stack 1 Red Hat – JBoss runbook, version 4.0

10. Open /WEB-INF/web.xml in an editor and configure database connectivity by adding a data source.

<!-- Temenos T24 Service Provider Specific Settings -->

<resource-ref id="ResourceRef_t24DataSource">
<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 id="ResourceRef_t24LockingDataSource">
<description>Used to get connections from T24 jdbc pool</description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

11. Add the JBoss-specific deployment descriptor jboss-web.xml under the WEB-INF directory and
configure database connectivity by adding data sources.

67
Stack 1 Red Hat – JBoss runbook, version 4.0

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

<jboss-web>
<resource-ref>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24Axis2DS</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24LockingDS</jndi-name>
</resource-ref>
</jboss-web>

12. Repackage axis2.war and place it in the UXPBrowser directory.

cd $UXPBROWSER/tmp-axis2
rm –rf axis2.war
jar cf axis2.war *
cp axis2.war $UXPBROWSER

12.2 Deploying Axis2

Procedure

68
Stack 1 Red Hat – JBoss runbook, version 4.0

1. In the Linux shell, navigate to $JBOSS_HOME/standalone/configuration.

2. Open Transact.xml in an editor and add Axis2 data source under the datasource subsystem for
axis2.war to get it deployed.

Microsoft SQL Server

<datasource jta="true" jndi-name="java:/jdbc/t24Axis2DS" pool-

name="Axis2DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:sqlserver://10.23.50.XXX:
1433;databaseName=xxxx;integratedSecurity=false</connection-url>
<connection-property name="defaultRowPrefetch">100</connection-
property>
<driver>sqljdbc</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
</datasource>

NuoDB

<datasource jta="true" jndi-name="java:/jdbc/t24Axis2DS" pool-

name="Axis2DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-
url>
jdbc:com.nuodb://10.23.50.138:48004/MB202008?SCHEMA=USER</connection-
url>
<connection-property name="defaultRowPrefetch">100</connection-
property>
<driver>nuodb-jdbc</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>

69
Stack 1 Red Hat – JBoss runbook, version 4.0

<user-name>dba</user-name>
<password>dba</password>
</security>
</datasource>

Oracle Database

<datasource jta="true" jndi-name="java:/jdbc/t24Axis2DS" pool-

name="Axis2DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>
jdbc:oracle:thin:@10.23.50.151:1521/MB202008</connection-url>
<connection-property name="defaultRowPrefetch">100</connection-
property>
<driver>ora18c</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
</datasource>

PostgreSQL

<datasource jta="true" jndi-name="java:/jdbc/t24Axis2DS" poolname="

Axis2DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>
jdbc:postgresql://192.168.0.2:5432/XXXXXX?autosave=always</connection-
url>
<connection-property
name="defaultRowPrefetch">100</connectionproperty>
<driver>postgres-jdbc</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>

70
Stack 1 Red Hat – JBoss runbook, version 4.0

<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
</datasource>

3. Copy axis2.war from the UXPBrowser directory to $JBOSS_

HOME/standalone/deployments.
cp axis2.war $JBOSS_HOME/standalone/deployments

71
Stack 1 Red Hat – JBoss runbook, version 4.0

13 Sanity check (post deployment)

You need to log in to Transact using the product user interfaces to verify your application server deployment. This
chapter shows how to log in using UXPB and BrowserWeb.

13.1 Starting the application server

Use the standalone.sh script that is in $JBOSS_HOME/bin to start JBoss. The script requires several
parameters depending on what needs to be deployed.

13.1.1 Starting JBoss with BrowserWeb

Use the following command to access BrowserWeb.

standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 --server-config=Transact.xml -

Djboss.http.port=9089

13.1.2 Starting JBoss with UXP Browser

To access UXP Browser use the following command. (Each command argument has been placed in a new line for
brevity.)

$JBOSS_HOME/bin/standalone.sh
--server-config=Transact.xml
-Djboss.http.port=9089
-Djboss.node.name=node1
-b 0.0.0.0
-DedgeSystemPropertyFolder=/srv/Temenos/properties
-DedgeSystemPropertyUpdaters=com.temenos.connect.system.GODSystemTestProperties
-DBRP_HOME=/srv/Temenos

Tip:
Optionally, you may set JBoss HTTP port (-Djboss.http.port=9089) to start JBoss at a user-defined
port instead of the default HTTP port 8080.

When the server is started, go to the JBoss deployments directory to see all the deployed artefacts.

72
Stack 1 Red Hat – JBoss runbook, version 4.0

13.1.3 Mandatory command arguments

Arguments Explanations

--server-config Indicates standalone profile configuration file (for example

Transact.xml) to use at JBoss startup.

-Djboss.http.port Port number of the application server.

-Djboss.node.name Unique identifier for the application server instance.

- This argument is used to set the required properties to be loaded. For

DedgeSystemPropertyUpdat GOD mode, use the value below:
ers
com.temenos.connect.system.GODSystemTestPrope
rties

13.2 Accessing TAFJEE

TAFJJEE_EAR.ear file also contains a WAR file, which is a helper servlet for configuration, diagnostic, execution
and troubleshooting TAFJ-related functions on the application server. You can access this helper servlet at
http://hostname_or_ipaddress:9089/TAFJEE. TAFJEE has protected access and is subject to
BASIC authentication.

Procedure

1. In the Linux shell, navigate to $JBOSS_HOME/bin. Create an application user by executing add-
user.sh.

73
Stack 1 Red Hat – JBoss runbook, version 4.0

2. Give the user TAFJAdmin role.

a. Specify the type of user, here Application user.
b. Provide the preferred user name and password (here the user is jumpstart and the password is
Temenos@123456).
c. Specify the groups the user should belong to; here TAFJAdmin.
d. Confirm the addition of the user to the realm ApplicationRealm by providing the answer yes.
e. For the last question, provide the answer no.

3. Access the TAFJEE servlet by using the following URL:

http://hostname_or_ipaddress:9089/TAFJEE

74
Stack 1 Red Hat – JBoss runbook, version 4.0

4. Supply the application user credentials. You can get access to all the functions in TAFJEE.

Note:
Some of the tools are protected and require TAFJ user credentials.

5. Click the tShow servlet to view the compilation details of a Transact routine on the application server.

75
Stack 1 Red Hat – JBoss runbook, version 4.0

13.3 Accessing BrowserWeb

Procedure

1. Access BrowserWeb using the following URL:

http://hostname_or_ipaddress:9089/BrowserWeb.

76
Stack 1 Red Hat – JBoss runbook, version 4.0

2. Log in using a valid Transact user name and password.

After a successful login, the landing page is displayed.

77
Stack 1 Red Hat – JBoss runbook, version 4.0

3. Launch any Transact application. For example, SPF S SYSTEM.

13.4 Accessing UXP Browser

Procedure

1. Access UXP Browser using the following URL:

http://hostname_or_ipaddress:9089/Browser/

78
Stack 1 Red Hat – JBoss runbook, version 4.0

2. Log in using a valid Transact user ID and password.

On successful login the landing page is displayed.

79
Stack 1 Red Hat – JBoss runbook, version 4.0

3. Launch a Transact application, for example, SPF S SYSTEM.

13.5 Accessing Axis2 servlet

Procedure

1. Access the Axis2 servlet using the following URL:

http://hostname_or_ipaddress:9089/axis2

80
Stack 1 Red Hat – JBoss runbook, version 4.0

2. Click Validate.

A page is displayed that confirms whether the web services are working properly.

81
Stack 1 Red Hat – JBoss runbook, version 4.0

3. On the main page, click Services to check the available web services.

13.6 Performing an integrated test of Axis2 and Transact

Procedure

1. In Axis2 servlet, go to Services and click the chosen service to get the WSDL file. For example, here the
WSDL is of IntegrationFlowService.

82
Stack 1 Red Hat – JBoss runbook, version 4.0

2. Create a new SOAP project using WSDL in a third-party tool such as SOAPUI.

83
Stack 1 Red Hat – JBoss runbook, version 4.0

3. Create a new read flow request passing the necessary parameters.

The SOAP response indicates that IntegrationFlowService of Axis2 can communicate with Transact.

You have now completed the deployment of TAFJ-Transact on JBoss EAP 7.3 with a supported database (MS SQL
Server 2019, Oracle 19c or PostgreSQL 11/12). You will now be able to perform business operations in Transact
using UXP Browser (or BrowserWeb).

84