Stack 1 JBoss – Red Hat

Customer Runbook 1.0, July 2023

All post R22 AMR releases up to and including R23 AMR
Stack 1 JBoss – Red Hat, version 1.0

Contents 8.2 Configuring the TAFJ module 27

8.3 Configuring the Transact module 28
1 About this runbook 3
8.3.1 Step 1: Creating the directory structure 29
1.1 Stack tables and other stack runbooks 3 8.3.2 Step 2: Generating the Transact module.xml file 29
1.2 Scope 3 8.3.3 JBossTools command for generating
module.xml 30
1.3 Audience 3
8.4 Configuring the Temenos Monitor module 30
1.4 Legal 3
8.5 Configuring the validation module 30
1.5 History 4
1.6 Conventions 4 9 Configuring standalone profile on the application
server 31
2 Introduction 6 9.1 Starting JBoss with J2EE 8 full profile 31
2.1 The architecture 6 9.2 Configuring the standalone full profile 32
3 Prerequisites 7 9.2.1 Sample standalone profile configuration file with
3.1 Software prerequisites 7 Oracle Database configuration 36
3.1.1 Third-party software 7
System properties 36
Data sources and drivers 36
3.1.2 Temenos artefacts 7
Global modules 38
3.2 Hardware prerequisites 8 JMS pools 38
4 Before you start 9 JMS queues 39
4.1 Completing preinstallation tasks 9 Temenos Kafka 43
4.2 Checking the system 9 HTTP listener 43
4.3 Prerequisite directory structure 10 10 Deploying Transact and TAFJ artefacts 45
4.4 Setting the environment variables 10 10.1 Deploying Transact artefacts 45
4.5 Verifying the system for third-party software 11 10.2 Deploying Transact Explorer 45
5 Installing Transact 13 11 Deploying Transact component services 46
5.1 Installing Transact 13 11.1 Re-packaging the Axis2 archive 46
5.2 Installing TAFJ 13 11.2 Deploying Axis2 48
5.3 Deploying the database driver 16
12 Performing a post deployment sanity check 51
5.3.1 Deploying the driver for MS SQL Server 16 12.1 Starting the application server 51
5.3.2 Deploying the drivers for Oracle Database 16 12.2 Accessing TAFJEE 51
5.3.3 Deploying the driver for PostgreSQL 16 12.3 Accessing Transact Explorer 53
6 Configuring TAFJ 17 12.4 Accessing Axis2 servlet 55
6.1 Configuring tafj.properties 17 12.5 Performing an integrated test of Axis2 and Transact 57
6.2 Verifying TAFJ installation 20

7 Sanity check 22
7.1 Accessing Classic 22
7.2 Launching DBTools 23

8 Configuring JBoss modules 25

8.1 Configuring the database driver module 25
8.1.1 Option 1: Configuring the module for Microsoft
SQL Server 25
8.1.2 Option 2: Configuring the module for Oracle
Database 26
8.1.3 Option 3: Configuring the module for
PostgreSQL 26

2
Stack 1 JBoss – Red Hat, version 1.0

1 About this runbook

The Stack 1 JBoss – Red Hat runbook shows you how to install and configure Temenos Transact, TAFJ and JBoss EAP 7.4 with
any of the following databases: Microsoft SQL Server 2019, Oracle 19c or PostgreSQL 15.

When you complete the deployment, you will be able to perform business operations in Transact using Transact Explorer.

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.4 EAP
l Deploying Transact and TAFJ artefacts in JBoss

1.3 Audience
This guide is intended for Temenos consultants, IT professionals and system administrators who support the installation of
Temenos Transact.The following skills are required:

l Red Hat Enterprise Linux administration

l JBoss application server administration and application deployment in JBoss
l Management of the chosen RDBMS: either Microsoft SQL Server, or Oracle Database, or PostgreSQL

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

3
Stack 1 JBoss – Red Hat, version 1.0

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

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

There is no guarantee as to the completeness, accuracy, timeliness or the results obtained from the use of this information. No
warranty of any kind is given, expressed or implied, including, but not limited to warranties of performance, merchantability and
fitness for a particular purpose.

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

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

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

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

1.5 History

Version Date Description Author

1.0 July 2023 Initial version Jumpstart

1.6 Conventions

Convention Description

Bold typeface Indicates GUI elements that are associated with an action and terms used in the body of the text or
in Glossary (if available).

Italic typeface Indicates placeholder variables and publication titles.

4
Stack 1 JBoss – Red Hat, version 1.0

Convention Description

Monospace typeface Indicates the following textual content:

l Commands
l Variables
l Code blocks and snippets
l Text that you enter (user input)
l URLs

5
Stack 1 JBoss – Red Hat, version 1.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, JBoss and ransact Explorer and how to access Transact through Transact Explorer.

2.1 The architecture

In this exercise, a two-tier architecture has been created which consists of an application server tier and a database server tier. The
application tier contains JBoss EAP (version 7.4) application server, TAFJ, Transact Online and the Transact Explorer. The
database tier contains one of the following RDBMSes: MS SQL Server 2019, or Oracle 19c, or PostgreSQL 15.

Transact Explorer
Transact Explorer is the new browser that has been released as part of R23 AMR and it replaces UXP Browser. Transact
Explorer has a modern layout engine, generates GUI screens faster, and consumes less hardware resources than its
predecessors.

Temenos Browser (TB) server.

TB server is the new module that exposes Transact APIs to Transact Explorer. TB server accepts Transact Explorer requests
in JSON format, sends them to Transact in XML format and then sends the returned responses back to Explorer in JSON
format.

6
Stack 1 JBoss – Red Hat, version 1.0

3 Prerequisites
Ensure that your environment meets the requirements listed in this chapter before you install TAFJ, Transact and Transact
Explorer.

3.1 Software prerequisites

3.1.1 Third-party software

Software Version

OpenJDK 11

JBoss EAP 7.4

Microsoft SQL Server 2019

Oracle Database 19c (19.19.0.0.0)

PostgreSQL 15

Axis2 1.8.2

3.1.2 Temenos artefacts

You need to obtain the following installation packages from your account manager.

Artefacts File name Description

MS SQL Server bak MB.R23.MSSQL_2014.WIN.TAFJR23.30- Contains the Model Bank database records.
file SEP-2024.bak.tar.gz

Oracle database MB.R23.ORACLE19.3.UNIX.TAFJR23.30- Contains the Model Bank database records.

dump file SEP-2024.dmp.tar.gz

PostgreSQL backup MB.R23.PostgreSQL_13.9.TAFJR23.30- Contains the Model Bank database records.

file SEP-2024.sql.tar.gz

Transact MB.R23.TAFJR23.bnk.tar.gz Contains the bnk directory that holds the Transact
libraries.

TAFJ TAFJ.R23.AMR.0.tar.gz Contains the TAFJ runtime .jar file, TAFJ patch
script and TAFJ setup script.

7
Stack 1 JBoss – Red Hat, version 1.0

Artefacts File name Description

Transact Explorer transact-explorer-wa-23.0.0.war Transact Explorer - the new Transact GUI released
with R23.

TB server tb-server-23.0.0.war Temenos Browser server is the API server for

Transact Explorer.

3.2 Hardware prerequisites

Ensure that you have at least 16 GB RAM available on the application server tier VM.

8
Stack 1 JBoss – Red Hat, version 1.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.R23.MSSQL_2014.WIN.TAFJR23.30-SEP-2024.bak.tar.gz
l Oracle Database: MB.R23.ORACLE19.3.UNIX.TAFJR23.30-SEP-2024.dmp.tar.gz
l PostgreSQL: MB.R23.PostgreSQL_13.9.TAFJR23.30-SEP-2024.sql.tar.gz

2. Load PL SQL 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. 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

4.2 Checking the system

Procedure

1. Check the version of the operating system: ensure that your application server operating system is 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 free disk space.

9
Stack 1 JBoss – Red Hat, version 1.0

3. Create the required directory structure.

a. At the Linux command-line, navigate to /srv 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/3rdParty/AS
mkdir -p Temenos/inst
mkdir -p Temenos/inst/tafj-inst
mkdir -p Temenos/inst/t24-inst

4.3 Prerequisite directory structure

Directory Subdirectory Description

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

AS This is the JBoss application server installation directory.

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

t24-inst t24inst is a subdirectory of inst and it contains Transact installation files.

tafj-inst tafjinst is a subdirectory of inst and it contains TAFJ installation files.

T24 The T24 directory contains all installed Transact-related libraries.

TAFJ The TAFJ directory contains installed TAFJ runtime libraries.

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 your home 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 created later.

10
Stack 1 JBoss – Red Hat, version 1.0

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

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

#T24_HOME
export T24_HOME=$TEMENOS_HOME/T24/bnk/lib
echo $T24_HOME

#JAVA_HOME
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.19.0.7-4.el8.x86_64

#JBOSS_HOME
export JBOSS_HOME=/srv/Temenos/3rdParty/AS/jboss-eap-7.4
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 version 11 is installed by executing java –version in the Linux shell.

2. Verify that you have added the JAVA_HOME environment variable and that you have added $JAVA_HOME/bin to the $PATH
variable.

11
Stack 1 JBoss – Red Hat, version 1.0

3. Check that you can connect to your database. You can use one of the following tools to connect to your database:
l Oracle SQL Developer (Oracle Database)

l SQL Server Management Studio (SQL Server)

l pgAdmin (PostgreSQL).
4. Verify that JBoss EAP 7.4 is installed and JBOSS_HOME has been set as an environment variable. You should see the
following directories and files in $JBOSS_HOME.

12
Stack 1 JBoss – Red Hat, version 1.0

5 Installing Transact
To install Transact, you need to extract the Transact libraries, install TAFJ and deploy the database driver for your chosen RDBMS
system.

5.1 Installing Transact

Procedure

1. Upload the MB.R23.TAFJR23.bnk.tar.gz file to the $TEMENOS_HOME/inst/transact-inst directory on your

application server.
2. Navigate to $TEMENOS_HOME/inst/transact-inst.
3. Extract the MB.R23.TAFJR23.bnk.tar.gz file.
tar –xvf MB.R23.TAFJR23.bnk.tar.gz

It is extracted as a bnk folder.

4. Move the bnk directory to the T24 directory.
mv bnk $TEMENOS_HOME/T24

5.2 Installing TAFJ

Before you begin

Ensure that you have set JAVA_HOME to the correct path.

Procedure

1. Upload the TAFJ.R23.AMR.0.tar.gz file to the $TEMENOS_HOME/inst/tafj-inst directory.

2. In the Linux shell, navigate to $TEMENOS_HOME/inst/tafj-inst.
3. Extract the .gz file.
tar –xvf TAFJ.R23.AMR.0.tar.gz

The following files are extracted:

4. Change the permissions on Setup_TAFJ.R23.AMR.0.sh and TAFJ.R23.AMR.0.jar to execute.

chmod 755 Setup_TAFJ.R23.AMR.0.sh TAFJ.R23.AMR.0.jar

13
Stack 1 JBoss – Red Hat, version 1.0

5. Execute Setup_TAFJ.R23.AMR.0.sh and press Enter..

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

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

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

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

14
Stack 1 JBoss – Red Hat, version 1.0

The following directories are available in $TAFJ_HOME.

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

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

12. Execute tVersion to verify the TAFJ version.

15
Stack 1 JBoss – Red Hat, version 1.0

5.3 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 drivers downloaded
from the vendor’s web site.

5.3.1 Deploying the driver for MS SQL Server

Procedure

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

2. Copy the mssql-jdbc-12.2.0.jre11.jar file to the $TAFJ_HOME/ext directory.

5.3.2 Deploying the drivers for Oracle Database

Procedure

1. Log on to the database server.

2. On your Oracle Database server, copy the following drivers to a temporary location.
l $ORACLE_HOME/jdbc/lib/ojdbc8.jar
l $ORACLE_HOME/jlib/oraclepki.jar
l $ORACLE_HOME/jlib/orai18n.jar
l $ORACLE_HOME/jlib/orai18n-collation.jar
l $ORACLE_HOME/jlib/orai18n-mapping.jar
l $ORACLE_HOME/ucp/lib/ucp.jar
l $ORACLE_HOME/rdbms/jlib/xdb6.jar
l $ORACLE_HOME/lib/xmlparserv2_sans_jaxp_services.jar
3. Using the scp command, copy the driver JAR files to the $TAFJ_HOME/ext/oracle-12c directory on your application
server.

5.3.3 Deploying the driver for PostgreSQL

Procedure

1. Download the JDBC SQL driver from the https://jdbc.postgresql.org/ web site.
2. Copy the postgresql-42.6.0.jar file to the $TAFJ_HOME/ext directory.

16
Stack 1 JBoss – Red Hat, version 1.0

6 Configuring TAFJ
This chapter shows how to configure TAFJ runtime to set up a standalone Transact instance.

TAFJ does not use environment variables. Instead, it uses a properties file (tafj.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.

#********************************************************************
#
# Directories
#
#********************************************************************
tafj.home =/srv/Temenos/TAFJ

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

# Specify the Precompile classes directories

# You can specify multiple directory, separated by
# ':' or ';' (eg /home/t24/lib;/home/t24/FT)
#
temn.tafj.directory.precompile=/srv/Temenos/T24/bnk/t24lib

5. Set the database connection parameters.

a. Under the Database setup header section, provide the relevant database URL (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.

temn.tafj.jdbc.url=
jdbc:sqlserver://10.23.50.XXX:1433;databaseName=MBR23;integratedSecurity=false;encrypt
=true;trustServerCertificate=true

# Class that describes the specific Driver for a database,

# ex. oracle: oracle.jdbc.driver.OracleDriver
# ex. db2: com.ibm.db2.jcc.DB2Driver
# ex. ms-sql: com.microsoft.sqlserver.jdbc.SQLServerDriver

17
Stack 1 JBoss – Red Hat, version 1.0

# ex. H2: org.h2.Driver

# ex. postgresql: org.postgresql.Driver
#
temn.tafj.jdbc.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

temn.tafj.jdbc.username=T24
temn.tafj.jdbc.password=T24

Oracle Database:

temn.tafj.jdbc.url=jdbc:oracle:thin:@10.23.50.149:1521/ORCLPDB3

# Class that describes the specific Driver for a database,

# ex. oracle: oracle.jdbc.driver.OracleDriver
# ex. db2: com.ibm.db2.jcc.DB2Driver
# ex. ms-sql: com.microsoft.sqlserver.jdbc.SQLServerDriver
# ex. H2: org.h2.Driver
# ex. postgresql: org.postgresql.Driver
#
temn.tafj.jdbc.driver=oracle.jdbc.driver.OracleDriver

temn.tafj.jdbc.username=T24
temn.tafj.jdbc.password=T24

PostgreSQL:

temn.tafj.jdbc.url=jdbc:postgresql://10.23.50.XX:5432/R23AMR?idle_in_transaction_
session_timeout=2000&tcpKeepAlive=true&cleanupSavepoints=true

# Class that describes the specific Driver for a database,

# ex. oracle: oracle.jdbc.driver.OracleDriver
# ex. db2: com.ibm.db2.jcc.DB2Driver
# ex. ms-sql: com.microsoft.sqlserver.jdbc.SQLServerDriver
# ex. H2: org.h2.Driver
# ex. postgresql: org.postgresql.Driver
#
temn.tafj.jdbc.driver=org.postgresql.Driver

temn.tafj.jdbc.username=T24
temn.tafj.jdbc.password=T24

6. Set the UD directory path.

# Specify what will be considered as the "current" directory (eg in an OPEN "." ...)
#
temn.tafj.runtime.directory.current=/srv/Temenos/T24/bnk/UD

18
Stack 1 JBoss – Red Hat, version 1.0

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.

#********************************************************************
#
# Database Specific setup
#
#********************************************************************

# Use the MERGE statement instead of UPDATE/INSERT for XML Schema

#
temn.tafj.jdbc.write.use.merge=false

# Use the MERGE statement instead of UPDATE/INSERT for NO XML Schema and NO XML Schema work
#
temn.tafj.jdbc.write.use.merge.no.xml=false

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

#********************************************************************
#
# TAFJ Locking mechanism
#
#********************************************************************

# Tafj locking mode

# Available options : JDBC | DATABASE
# JDBC : locks managed in database uses TAFJ_LOCKS table.(Only for DEV environments)
# DATABASE : Use database locks of the underlying database (Recommended for live
implementations.)
#
temn.tafj.locking.mode=DATABASE

Note:
DATABASE locking mode is recommended for releases 201809 and higher. TAFJ locks records using native database
locks when this locking mode is used. There are two supported modes:

l Mode 1 (default) uses an internal technical number table TAFJ_NONEXISTING_ROWS for handling the locks of
non-existing records from the application. This table is created on the fly in the runtime environment when the
DATABASE locking mode is set.
l Mode 2 uses an internal technical number table TAFJ_HASHLOCKS which contains values ranging from 0 to
2147483647 (maximum integer value).

19
Stack 1 JBoss – Red Hat, version 1.0

To use mode 2, you need to perform the following steps:

1. Populate the TAFJ_HASHLOCKS table by running the TAFJ_HOME/dbscripts/your_chosen_DB_
flavour/tafj_hashlock_tab_prepare.sql script. It can take up to two hours for the script to
complete.
2. Enable mode 2 by adding the following property in the tafj.properties file:
temn.tafj.jdbc.db.locking.insert.rows.on.demand = false

For more information, 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.

temn.tafj.jdbc.use.rownum.at.end=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.
l The default project, and the details of all the projects that are set in $TAFJ_HOME/conf.

20
Stack 1 JBoss – Red Hat, version 1.0

This completes the TAFJ runtime setup.

21
Stack 1 JBoss – Red Hat, version 1.0

7 Sanity check
Verify that your Transact standalone installation is successful before you proceed to deploy the application server.

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.

22
Stack 1 JBoss – Red Hat, version 1.0

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

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

5. To exit the SPF application, press the CTRL and U buttons and press Enter.
6. To exit the Classic command line interface, press the Shift, B and K buttons and press Enter.

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

23
Stack 1 JBoss – Red Hat, version 1.0

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

2. Create a TAFJ user by passing the 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.

5. To exit DBTools, pres the x button and then press Enter.

24
Stack 1 JBoss – Red Hat, version 1.0

8 Configuring JBoss modules

JBoss EAP 7.4 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.4, 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 five modules on your application server.

l Database driver module

l TAFJ module
l Transact module
l Temenos Monitor module
l Validation 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 Option 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 a directory under $TAFJ_HOME to the new main directory.
cp $TAFJ_HOME/appserver/jboss/jboss7eap/modules/com/microsoft/sqlserver/main/module.xml
$JBOSS_HOME/modules/com/microsoft/sqlserver/main
4. Copy the corresponding database driver to the main directory.
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 as the folder path
for that module.

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

<module xmlns="urn:jboss:module:1.1" name="com.microsoft.sqlserver">

<resources>
<resource-root path="mssql-jdbc-12.2.0.jre11.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>

25
Stack 1 JBoss – Red Hat, version 1.0

<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
<module name="javax.xml.bind.api"/>
</dependencies>

</module>

8.1.2 Option 2: 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/ora19c/main
3. Copy module.xml from a directory under $TAFJ_HOME to the new main directory.
cp $TAFJ_HOME/appserver/jboss/jboss7eap/modules/com/oracle/ora12c/main/module.xml $JBOSS_
HOME/modules/com/oracle/ora19c/main
4. Copy the corresponding Oracle drivers from $TAFJ_HOME/ext to the $JBOSS_
HOME/modules/com/oracle/ora19c/main directory.
cp $TAFJ_HOME/ext/oracle-12c/ojdbc8.jar $JBOSS_HOME/modules/com/oracle/ora19c/main
cp $TAFJ_HOME/ext/oracle-12c/xdb6.jar $JBOSS_HOME/modules/com/oracle/ora19c/main
cp $TAFJ_HOME/ext/oracle-12c/xmlparserv2_sans_jaxp_services.jar $JBOSS_
HOME/modules/com/oracle/ora19c/main
5. Check whether the copy was successful.

8.1.3 Option 3: 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

26
Stack 1 JBoss – Red Hat, version 1.0

3. Copy module.xml from a directory under $TAFJ_HOME to the new 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 PostgreSQL driver from $TAFJ_HOME/ext to the $JBOSS_
HOME/modules/com/postgres/jdbc/main directory.
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.

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

<module xmlns="urn:jboss:module:1.1" name="com.postgres.jdbc">

<resources>
<resource-root path="postgresql-42.5.1.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
<module name="javax.xml.bind.api"/>
</dependencies>

</module>

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, $TAFJ_HOME/ext and $TAFJ_HOME/RulesEngine directories.
ln -s $TAFJ_HOME/lib lib
ln -s $TAFJ_HOME/ext ext
ln -s $TAFJ_HOME/RulesEngine RulesEngine

27
Stack 1 JBoss – Red Hat, version 1.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:

<dependencies>
<module name="com.temenos.monitor" />
<module name="com.temenos.t24" />
<module name="com.microsoft.sqlserver"/>
<module name="com.temenos.validation"/>
<module name="javax.api" />
...
(shortened for brevity)

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

<dependencies>
<module name="com.temenos.monitor" />
<module name="com.temenos.t24" />
<module name="com.oracle.ora19c" />
<module name="com.temenos.validation"/>
<module name="javax.api" />
...
(shortened for brevity)

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

<dependencies>
<module name="com.temenos.monitor" />
<module name="com.temenos.t24" />
<module name="com.postgres.jdbc"/>
<module name="com.temenos.validation"/>
<module name="javax.api" />
...
(shortened for brevity)

7. In the same module.xml file, add the following line as the last element under <resources>.

<resource-root path="./ext/jtpm/jTPM-2.0.0.jar" />

<resource-root path="./ext/restclient/Rest-client-2.0.0.jar" />
<resource-root path="./RulesEngine/RulesEngine.jar" />
</resources>
<dependencies>

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.

28
Stack 1 JBoss – Red Hat, version 1.0

8.3.1 Step 1: Creating the directory structure

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.3.2 Step 2: 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

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 the above command.

3. Open module.xml and add the TAFJ module as a dependency in the <dependencies> section.

<resource-root path="./lib/t24-RR_ReplicationService-Data.jar" />

<resource-root path="./lib/t24-RR_ReplicationService-t24service.jar" />
<resource-root path="./lib/t24-ST_CustomerService-Data.jar" />
<resource-root path="./lib/t24-ST_CustomerService-t24service.jar" />
</resources>
<dependencies>
<module name="com.temenos.tafj"/>
</dependencies>
</module>

29
Stack 1 JBoss – Red Hat, version 1.0

8.3.3 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.

8.4 Configuring the Temenos Monitor module

Procedure

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

2. Create the following directory structure under the modules directory.
mkdir -p monitor/main
3. Copy module.xml from $TAFJ_HOME to the main directory.
cp $TAFJ_HOME/appserver/jboss/jboss7eap/modules/com/temenos/monitor/main/module.xml
$JBOSS_HOME/modules/com/temenos/monitor/main
4. In the monitor/main directory, create a symbolic link to the $TAFJ_HOME/libMonitor directory.
ln -s $TAFJ_HOME/libMonitor lib

8.5 Configuring the validation module

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 validation/main
3. Copy module.xml from $TAFJ_HOME to the main directory.
cp $TAFJ_HOME/appserver/jboss/jboss7eap/modules/com/temenos/validation/main/module.xml
$JBOSS_HOME/modules/com/temenos/validation/main
4. In the monitor/main directory, create a symbolic link to $TAFJ_HOME/libValidation.
ln -s $TAFJ_HOME/libValidation lib

30
Stack 1 JBoss – Red Hat, version 1.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 your_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:

# Uncomment the following line to prevent manipulation of JVM options

# by shell scripts.
#
#PRESERVE_JAVA_OPTS=true
JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF-8 -Dtafj.home=$TAFJ_HOME"

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

# Specify options to pass to the Java VM.

#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms6G -Xmx6G -XX:MetaspaceSize=256M -XX:MaxMetaspaceSize=512m -
Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -
Djava.awt.headless=true"
else
echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_
OPTS"
fi

31
Stack 1 JBoss – Red Hat, version 1.0

Note:
When setting up the max heap size (-mx), set the initial heap size (-ms) to the same value as the maximum 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.

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

Microsoft SQL Server:

#Drivers
#define the driver corresponding to your database - H2 driver is already existing by
default - uncomment one of the following to create the driver corresponding to your
database
#please note that you have to create the module for the driver first
/subsystem=datasources/jdbc-driver=ora12c:add(driver-name=ora12c,driver-module-
name=com.oracle.ora12c,driver-xa-datasource-class-
name=oracle.jdbc.xa.client.OracleXADataSource)
/subsystem=datasources/jdbc-driver=sqljdbc:add(driver-name=sqljdbc,driver-module-
name=com.microsoft.sqlserver,driver-xa-datasource-class-
name=com.microsoft.sqlserver.jdbc.SQLServerXADataSource)
#/subsystem=datasources/jdbc-driver=db2jdbc:add(driver-name=db2jdbc,driver-module-
name=com.ibm.db2v11,driver-xa-datasource-class-name=com.ibm.db2.jcc.DB2XADataSource)

Oracle Database:

32
Stack 1 JBoss – Red Hat, version 1.0

#Drivers
#define the driver corresponding to your database - H2 driver is already existing by
default - uncomment one of the following to create the driver corresponding to your
database
#please note that you have to create the module for the driver first
/subsystem=datasources/jdbc-driver=ora19c:add(driver-name=ora19c,driver-module-
name=com.oracle.ora19c,driver-xa-datasource-class-
name=oracle.jdbc.xa.client.OracleXADataSource)
#/subsystem=datasources/jdbc-driver=sqljdbc:add(driver-name=sqljdbc,driver-module-
name=com.microsoft.sqlserver,driver-xa-datasource-class-
name=com.microsoft.sqlserver.jdbc.SQLServerXADataSource)

PostgreSQL:

/subsystem=datasources/jdbc-driver=postgres-jdbc:add(driver-name=postgres-jdbc,driver-
module-name=com.postgres.jdbc,driver-xa-datasource-class-
name=org.postgresql.xa.PGXADataSource)
#/subsystem=datasources/jdbc-driver=jdbc-yugabytedb:add(driver-name=jdbc-
yugabytedb,driver-module-name=com.yugabyte.Driver,driver-xa-datasource-class-
name=com.yugabyte.xa.PGXADataSource)

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 the tafj.properties that is in the same directory ($TAFJ_HOME/appserver/jboss/jboss7eap/jboss-cli)

in a text editor.
4. Provide the TAFJ_HOME, DB_URL, DB_DRIVER, DB_USER and DB_PWD parameters.

Microsoft SQL Server:

############################################################
# Path details
#
# For windows use C:/
#
TAFJ_HOME=/srv/Temenos/TAFJ
############################################################
# database details
#
#DB_URL doesn't apply for DB2 XA DRIVER
jdbc:sqlserver://10.23.50.XXX:1433;databaseName=MBR23;integratedSecurity=false;encrypt=tru
e;trustServerCertificate=true
DB_DRIVER=sqljdbc
DB_DRIVER_XA=[h2,ora12cXA,db2jdbc,sqljdbc,nuodb-jdbc,postgres-jdbc]
DB_USER=T24

33
Stack 1 JBoss – Red Hat, version 1.0

DB_PWD=T24
#DB2 XA DRIVER in replacement of DB_URL
DB_HOST=[hostname]
DB_NAME=[instance name]
DB_PORT=[port]

Oracle Database:

############################################################
# Path details
#
# For windows use C:/
#
TAFJ_HOME=/srv/Temenos/TAFJ
############################################################
# database details
#
#DB_URL doesn't apply for DB2 XA DRIVER
DB_URL=jdbc:oracle:thin:@10.23.50.149:1521/ORCLPDB3
DB_DRIVER=ora19c
DB_DRIVER_XA=[h2,ora12cXA,db2jdbc,sqljdbc,nuodb-jdbc,postgres-jdbc]
DB_USER=T24
DB_PWD=T24
#DB2 XA DRIVER in replacement of DB_URL
DB_HOST=[hostname]
DB_NAME=[instance name]
DB_PORT=[port]

PostgreSQL:

############################################################
# Path details
#
# For windows use C:/
#
TAFJ_HOME=/srv/Temenos/TAFJ
############################################################
# database details
#
#DB_URL doesn't apply for DB2 XA DRIVER
jdbc:postgresql://10.23.50.XX:5432/R23AMR?idle_in_transaction_session_
timeout=2000&tcpKeepAlive=true&cleanupSavepoints=true
DB_DRIVER=org.postgresql.Driver
DB_DRIVER_XA=[h2,ora12cXA,db2jdbc,sqljdbc,nuodb-jdbc,postgres-jdbc]
DB_USER=T24
DB_PWD=T24

34
Stack 1 JBoss – Red Hat, version 1.0

#DB2 XA DRIVER in replacement of DB_URL

DB_HOST=[hostname]
DB_NAME=[instance name]
DB_PORT=[port]

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.

<validate-operation-requests>true</validate-operation-requests>

<!-- Command and operation history log configuration -->

<history>
<enabled>true</enabled>
<file-name>.jboss-cli-history</file-name>
<file-dir>${user.home}</file-dir>
<max-size>500</max-size>
</history>

<!-- whether to resolve system properties specified as command argument or operation

parameter values
in the CLI VM before sending the operation requests to the controller -->
<resolve-parameter-values>true</resolve-parameter-values>

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 message shows the successful execution of the jboss-cli command.

The batch executed successfully

process-state: reload-required

The scripts adds the following to the standalone configuration file. (Transact.xml)
l "System properties" on the next page
l "Data sources and drivers" on the next page
l "Global modules" on page 38
l "JMS pools" on page 38
l "JMS queues" on page 39
l "Temenos Kafka" on page 43
l "HTTP listener" on page 43
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.

35
Stack 1 JBoss – Red Hat, version 1.0

9.2.1 Sample standalone profile configuration file with Oracle Database

configuration

This topic shows the selected snippets from the JBoss standalone configuration file, which means that a lot of contents have been
omitted for brevity. The content highlighted with bold font has been generated during during the running of the jboss-cli.sh
script.

System properties
<extension module="org.wildfly.extension.undertow"/>
<extension module="org.wildfly.iiop-openjdk"/>
</extensions>
system-properties
<property name="tafj.home" value="/srv/Temenos/TAFJ"/>
<property name="file.encoding" value="UTF-8"/>
</system-properties>
<management>
<security-realms>

Data sources and drivers

<subsystem xmlns="urn:jboss:domain:datasources:6.0">
<datasources>
<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS"
enabled="true" use-java-context="true" statistics-enabled="${wildfly.datasources.statistics-
enabled:${wildfly.statistics-enabled:false}}">
<connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_
EXIT=FALSE</connection-url>
<driver>h2</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
<datasource jta="true" jndi-name="java:/jdbc/t24DS" pool-name="t24DS" enabled="true"
use-java-context="true" use-ccm="true">
<connection-url>jdbc:oracle:thin:@10.23.50.149:1521/ORCLPDB3</connection-url>
<connection-property name="defaultRowPrefetch">
100
</connection-property>
<driver>ora19c</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>

36
Stack 1 JBoss – Red Hat, version 1.0

</pool>
<security>
<user-name>T24</user-name>
<password>T24</password>
</security>
</datasource>
<datasource jta="false" jndi-name="java:/jdbc/t24LockingDS" pool-name="t24LockingDS"
enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:oracle:thin:@10.23.50.149:1521/ORCLPDB3</connection-url>
<driver>ora19c</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>
<datasource jta="false" jndi-name="java:/jdbc/t24RODS" pool-name="t24RODS"
enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:oracle:thin:@10.23.50.149:1521/ORCLPDB3</connection-url>
<driver>ora19c</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>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="ora19c" module="com.oracle.ora19c">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-
datasource-class>
</driver>
</drivers>
</datasources>

37
Stack 1 JBoss – Red Hat, version 1.0

Global modules
<subsystem xmlns="urn:jboss:domain:ee:6.0">
<global-modules>
<module name="com.temenos.tafj" slot="main"/>
<module name="com.temenos.t24" slot="main"/>
<module name="com.temenos.monitor" slot="main"/>
<module name="com.temenos.validation" slot="main"/>
</global-modules>
<spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>

JMS pools
<pools>
<bean-instance-pools>
<strict-max-pool name="mdb-strict-max-pool" derive-size="from-cpu-count"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="slsb-strict-max-pool" derive-size="from-worker-pools"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="ofs-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="browser-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="arcmob-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tws-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tcib-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tcibcorp-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tcibwealth-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="callat-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="aml-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tps-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="seat-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="phantom-mdb-strict-max-pool" max-pool-size="20" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="swf-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="aaint-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>

38
Stack 1 JBoss – Red Hat, version 1.0

<strict-max-pool name="aaext-mdb-strict-max-pool" max-pool-size="10" instance-

acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="irisint-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="irisext-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="inst-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="dsfpackage-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="irismetadata-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="dd-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="ms-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="rf-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tph-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="cmbinterface-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tpsstandalone-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="tpsnonsla-mdb-strict-max-pool" max-pool-size="10"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="xmlofs-mdb-strict-max-pool" max-pool-size="10" instance-
acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
<strict-max-pool name="management-mdb-strict-max-pool" max-pool-size="1"
instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
</bean-instance-pools>
</pools>

JMS queues
<subsystem xmlns="urn:jboss:domain:messaging-activemq:13.0">
<server name="default">
<statistics enabled="${wildfly.messaging-activemq.statistics-
enabled:${wildfly.statistics-enabled:false}}"/>
<security-setting name="#">
<role name="guest" send="true" consume="true" create-non-durable-queue="true"
delete-non-durable-queue="true"/>
</security-setting>
<address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-
address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-
history-day-limit="10"/>
<http-connector name="http-connector" socket-binding="http" endpoint="http-

39
Stack 1 JBoss – Red Hat, version 1.0

acceptor"/>
<http-connector name="http-connector-throughput" socket-binding="http"
endpoint="http-acceptor-throughput">
<param name="batch-delay" value="50"/>
</http-connector>
<in-vm-connector name="in-vm" server-id="0">
<param name="buffer-pooling" value="false"/>
</in-vm-connector>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0">
<param name="buffer-pooling" value="false"/>
</in-vm-acceptor>
<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
java:jboss/exported/jms/queue/t24OFSQueue"/>
<jms-queue name="t24OFSReplyQueue" entries="queue/t24OFSReplyQueue
java:jboss/exported/jms/queue/t24OFSReplyQueue"/>
<jms-queue name="t24BROWSERQueue" entries="queue/t24BROWSERQueue
java:jboss/exported/jms/queue/t24BROWSERQueue"/>
<jms-queue name="t24BROWSERReplyQueue" entries="queue/t24BROWSERReplyQueue
java:jboss/exported/jms/queue/t24BROWSERReplyQueue"/>
<jms-queue name="t24ARCMOBQueue" entries="queue/t24ARCMOBQueue
java:jboss/exported/jms/queue/t24ARCMOBQueue"/>
<jms-queue name="t24ARCMOBReplyQueue" entries="queue/t24ARCMOBReplyQueue
java:jboss/exported/jms/queue/t24ARCMOBReplyQueue"/>
<jms-queue name="t24TWSQueue" entries="queue/t24TWSQueue
java:jboss/exported/jms/queue/t24TWSQueue"/>
<jms-queue name="t24TWSReplyQueue" entries="queue/t24TWSReplyQueue
java:jboss/exported/jms/queue/t24TWSReplyQueue"/>
<jms-queue name="t24TCIBQueue" entries="queue/t24TCIBQueue
java:jboss/exported/jms/queue/t24TCIBQueue"/>
<jms-queue name="t24TCIBReplyQueue" entries="queue/t24TCIBReplyQueue
java:jboss/exported/jms/queue/t24TCIBReplyQueue"/>
<jms-queue name="t24TCIBCORPQueue" entries="queue/t24TCIBCORPQueue
java:jboss/exported/jms/queue/t24TCIBCORPQueue"/>
<jms-queue name="t24TCIBCORPReplyQueue" entries="queue/t24TCIBCORPReplyQueue
java:jboss/exported/jms/queue/t24TCIBCORPReplyQueue"/>
<jms-queue name="t24TCIBWEALTHQueue" entries="queue/t24TCIBWEALTHQueue
java:jboss/exported/jms/queue/t24TCIBWEALTHQueue"/>
<jms-queue name="t24TCIBWEALTHReplyQueue" entries="queue/t24TCIBWEALTHReplyQueue
java:jboss/exported/jms/queue/t24TCIBWEALTHReplyQueue"/>
<jms-queue name="t24CALLATQueue" entries="queue/t24CALLATQueue

40
Stack 1 JBoss – Red Hat, version 1.0

java:jboss/exported/jms/queue/t24CALLATQueue"/>
<jms-queue name="t24CALLATReplyQueue" entries="queue/t24CALLATReplyQueue
java:jboss/exported/jms/queue/t24CALLATReplyQueue"/>
<jms-queue name="t24AMLQueue" entries="queue/t24AMLQueue
java:jboss/exported/jms/queue/t24AMLQueue"/>
<jms-queue name="t24AMLReplyQueue" entries="queue/t24AMLReplyQueue
java:jboss/exported/jms/queue/t24AMLReplyQueue"/>
<jms-queue name="t24TPSQueue" entries="queue/t24TPSQueue
java:jboss/exported/jms/queue/t24TPSQueue"/>
<jms-queue name="t24TPSReplyQueue" entries="queue/t24TPSReplyQueue
java:jboss/exported/jms/queue/t24TPSReplyQueue"/>
<jms-queue name="t24TPSInstInQueue" entries="queue/t24TPSInstInQueue
java:jboss/exported/jms/queue/t24TPSInstInQueue"/>
<jms-queue name="t24TPSInstInReplyQueue" entries="queue/t24TPSInstInReplyQueue
java:jboss/exported/jms/queue/t24TPSInstInReplyQueue"/>
<jms-queue name="t24SEATQueue" entries="queue/t24SEATQueue
java:jboss/exported/jms/queue/t24SEATQueue"/>
<jms-queue name="t24SEATReplyQueue" entries="queue/t24SEATReplyQueue
java:jboss/exported/jms/queue/t24SEATReplyQueue"/>
<jms-queue name="t24IFInboundQueue" entries="queue/t24IFInboundQueue
java:jboss/exported/jms/queue/t24IFInboundQueue"/>
<jms-queue name="t24IFOutboundQueue" entries="queue/t24IFOutboundQueue
java:jboss/exported/jms/queue/t24IFOutboundQueue"/>
<jms-queue name="t24SWFQueue" entries="queue/t24SWFQueue
java:jboss/exported/jms/queue/t24SWFQueue"/>
<jms-queue name="t24SWFReplyQueue" entries="queue/t24SWFReplyQueue
java:jboss/exported/jms/queue/t24SWFReplyQueue"/>
<jms-queue name="t24AAIntQueue" entries="queue/t24AAIntQueue
java:jboss/exported/jms/queue/t24AAIntQueue"/>
<jms-queue name="t24AAIntReplyQueue" entries="queue/t24AAIntReplyQueue
java:jboss/exported/jms/queue/t24AAIntReplyQueue"/>
<jms-queue name="t24AAExtQueue" entries="queue/t24AAExtQueue
java:jboss/exported/jms/queue/t24AAExtQueue"/>
<jms-queue name="t24AAExtReplyQueue" entries="queue/t24AAExtReplyQueue
java:jboss/exported/jms/queue/t24AAExtReplyQueue"/>
<jms-queue name="t24IRISIntQueue" entries="queue/t24IRISIntQueue
java:jboss/exported/jms/queue/t24IRISIntQueue"/>
<jms-queue name="t24IRISIntReplyQueue" entries="queue/t24IRISIntReplyQueue
java:jboss/exported/jms/queue/t24IRISIntReplyQueue"/>
<jms-queue name="t24IRISExtQueue" entries="queue/t24IRISExtQueue
java:jboss/exported/jms/queue/t24IRISExtQueue"/>
<jms-queue name="t24IRISExtReplyQueue" entries="queue/t24IRISExtReplyQueue
java:jboss/exported/jms/queue/t24IRISExtReplyQueue"/>
<jms-queue name="t24DSFPACKAGERQueue" entries="queue/t24DSFPACKAGERQueue
java:jboss/exported/jms/queue/t24DSFPACKAGERQueue"/>
<jms-queue name="t24DSFPACKAGERReplyQueue" entries="queue/t24DSFPACKAGERReplyQueue
java:jboss/exported/jms/queue/t24DSFPACKAGERReplyQueue"/>

41
Stack 1 JBoss – Red Hat, version 1.0

<jms-queue name="t24IRISMetaDataQueue" entries="queue/t24IRISMetaDataQueue

java:jboss/exported/jms/queue/t24IRISMetaDataQueue"/>
<jms-queue name="t24IRISMetaDataReplyQueue" entries="queue/t24IRISMetaDataReplyQueue
java:jboss/exported/jms/queue/t24IRISMetaDataReplyQueue"/>
<jms-queue name="t24DDQueue" entries="queue/t24DDQueue
java:jboss/exported/jms/queue/t24DDQueue"/>
<jms-queue name="t24DDReplyQueue" entries="queue/t24DDReplyQueue
java:jboss/exported/jms/queue/t24DDReplyQueue"/>
<jms-queue name="t24MSOFSQueue" entries="queue/t24MSOFSQueue
java:jboss/exported/jms/queue/t24MSOFSQueue"/>
<jms-queue name="t24MSOFSReplyQueue" entries="queue/t24MSOFSReplyQueue
java:jboss/exported/jms/queue/t24MSOFSReplyQueue"/>
<jms-queue name="t24RFOFSQueue" entries="queue/t24RFOFSQueue
java:jboss/exported/jms/queue/t24RFOFSQueue"/>
<jms-queue name="t24RFOFSReplyQueue" entries="queue/t24RFOFSReplyQueue
java:jboss/exported/jms/queue/t24RFOFSReplyQueue"/>
<jms-queue name="t24IFRTPInQueue" entries="queue/t24IFRTPInQueue
java:jboss/exported/jms/queue/t24IFRTPInQueue"/>
<jms-queue name="t24IFRTPOutQueue" entries="queue/t24IFRTPOutQueue
java:jboss/exported/jms/queue/t24IFRTPOutQueue"/>
<jms-queue name="t24TPHAckNackQueue" entries="queue/t24TPHAckNackQueue
java:jboss/exported/jms/queue/t24TPHAckNackQueue"/>
<jms-queue name="t24TPHAckNackReplyQueue" entries="queue/t24TPHAckNackReplyQueue
java:jboss/exported/jms/queue/t24TPHAckNackReplyQueue"/>
<jms-queue name="t24CMBInterfaceQueue" entries="queue/t24CMBInterfaceQueue
java:jboss/exported/jms/queue/t24CMBInterfaceQueue"/>
<jms-queue name="t24CMBInterfaceReplyQueue" entries="queue/t24CMBInterfaceReplyQueue
java:jboss/exported/jms/queue/t24CMBInterfaceReplyQueue"/>
<jms-queue name="t24TPSStalResp" entries="queue/t24TPSStalResp
java:jboss/exported/jms/queue/t24TPSStalResp"/>
<jms-queue name="t24TPSStalRespReplyQueue" entries="queue/t24TPSStalRespReplyQueue
java:jboss/exported/jms/queue/t24TPSStalRespReplyQueue"/>
<jms-queue name="t24TPSNIClrQueue" entries="queue/t24TPSNIClrQueue
java:jboss/exported/jms/queue/t24TPSNIClrQueue"/>
<jms-queue name="t24TPSNIClrReplyQueue" entries="queue/t24TPSNIClrReplyQueue
java:jboss/exported/jms/queue/t24TPSNIClrReplyQueue"/>
<jms-queue name="t24XmlOfsQueue" entries="queue/t24XmlOfsQueue
java:jboss/exported/jms/queue/t24XmlOfsQueue"/>
<jms-queue name="t24XmlOfsReplyQueue" entries="queue/t24XmlOfsReplyQueue
java:jboss/exported/jms/queue/t24XmlOfsReplyQueue"/>
<jms-queue name="t24EXECQueue" entries="queue/t24EXECQueue
java:jboss/exported/jms/queue/t24EXECQueue"/>
<jms-queue name="tafj-outboxIdQueue" entries="queue/tafj-outboxIdQueue
java:jboss/exported/jms/queue/tafj-outboxIdQueue"/>
<jms-topic name="tecEventsTopic" entries="topic/tecEventsTopic
java:jboss/exported/jms/topic/tecEventsTopic"/>
<jms-topic name="t24ManagementTopic" entries="topic/t24ManagementTopic

42
Stack 1 JBoss – Red Hat, version 1.0

java:jboss/exported/jms/topic/t24ManagementTopic"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory"
connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory"
entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" entries="java:/JmsXA
java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
</server>
</subsystem>

Temenos Kafka
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<http-connector name="http-remoting-connector" connector-ref="default" security-
realm="ApplicationRealm"/>
</subsystem>
<subsystem xmlns="urn:jboss:domain:request-controller:1.0"/>
<subsystem xmlns="urn:jboss:domain:resource-adapters:6.0">
<resource-adapters>
<resource-adapter id="TemnKafkaRAR">
<archive>
TemnKafka.rar
</archive>
<transaction-support>XATransaction</transaction-support>
<connection-definitions>
<connection-definition class-
name="com.temenos.technology.kafka.outbound.TemnKafkaManagedConnectionFactory" jndi-
name="java:/eis/KafkaConnectionFactory" enabled="true" pool-name="ConnectionFactory">
<xa-pool>
<min-pool-size>1</min-pool-size>
<max-pool-size>20</max-pool-size>
<prefill>false</prefill>
<is-same-rm-override>false</is-same-rm-override>
</xa-pool>
</connection-definition>
</connection-definitions>
</resource-adapter>
</resource-adapters>
</subsystem>
<subsystem xmlns="urn:jboss:domain:sar:1.0"/>

HTTP listener
<subsystem xmlns="urn:jboss:domain:undertow:12.0" default-server="default-server" default-
virtual-host="default-host" default-servlet-container="default" default-security-domain="other"
statistics-enabled="${wildfly.undertow.statistics-enabled:${wildfly.statistics-enabled:false}}">

43
Stack 1 JBoss – Red Hat, version 1.0

<buffer-cache name="default"/>
<server name="default-server">
<http-listener name="default" socket-binding="http" max-parameters="5000" redirect-
socket="https" enable-http2="true"/>
<https-listener name="https" socket-binding="https" security-
realm="ApplicationRealm" enable-http2="true"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<http-invoker security-realm="ApplicationRealm"/>
</host>
</server>

44
Stack 1 JBoss – Red Hat, version 1.0

10 Deploying Transact and TAFJ artefacts

The final step in this setup is to deploy the Transact UI component called Transact Explorer, the latest user interface for working
with Transact. This runbook does not cover deployment of other product user interfaces such as Temenos Connect Internet
Banking (TCIB) and Mobile Banking (TCMB).

10.1 Deploying Transact artefacts

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. Copy TemnKafka.rar to the $JBOSS_HOME/standalone/deployments directory.
cp TemnKafka.rar $JBOSS_HOME/standalone/deployments
4. Change to $TAFJ_HOME/appserver/jboss/jboss7eap.
5. Copy TAFJJEE_EAR.ear to the $JBOSS_HOME/standalone/deployments directory.
cp TAFJJEE_EAR.ear $JBOSS_HOME/standalone/deployments

10.2 Deploying Transact Explorer

Procedure

1. Upload the transact-explorer-wa-23.0.0.war and tb-server-23.0.0.war files to the $TEMENOS_HOME/inst

directory on your application server.
2. At the Linux command line, navigate to the $TEMENOS_HOME/inst and rename the files truncating the version part of the
file names. Result:
l transact-explorer-wa.war
l tb-server.war
3. Copy both files to $JBOSS_HOME/standalone/deployments.
cp tb-server.war $JBOSS_HOME/standalone/deployments
cp transact-explorer-wa.war $JBOSS_HOME/standalone/deployments

45
Stack 1 JBoss – Red Hat, version 1.0

11 Deploying Transact component services

You will find the Transact component service APIs as Axis2 archives (t24-component_service-jws.aar) in the extensions
directory of the Transact package 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.8.2. The topics in this chapter show you how to deploy axis2.war in your JBoss
application server.

11.1 Re-packaging the Axis2 archive

Procedure

1. Download the artefacts:

a. From the Apache website download the axis2-1.8.2-war.zip file ans extract axis2.war from it.
b. Download the following dependencies:
l commons-pool2-2.9.0.jar
l spring-beans-5.3.22.jar
l spring-context-5.3.22.jar
l spring-core-5.3.22.jar
You can use the following download web site: https://mvnrepository.com.
2. In the Linux shell, change to the $TEMENOS_HOME/install directory and create a new temporary directory, for example
axis2.
3. Upload axis2.war and all the four dependencies to the $TEMENOS_HOME/install/axis2 directory.
4. In the Linux shell, extract the contents of the axis2.war file and navigate to WEB-INF/lib.
cd $TEMENOS_HOME/install/axis2
jar -xf axis2.war

The following files are extracted:

5. Copy the dependency JAR files to the lib directory.

mv commons-pool2-2.9.0.jar WEB-INF/lib
mv spring-beans-5.3.22.jar WEB-INF/lib
mv spring-context-5.3.22.jar WEB-INF/lib
mv spring-core-5.3.22.jar WEB-INF/lib
6. 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 WEB-INF/services

46
Stack 1 JBoss – Red Hat, version 1.0

cp $TEMENOS_HOME/T24/bnk/Extensions/EB_CatalogService/t24ws/t24-EB_CatalogService-tafj-
jws.aar WEB-INF/services
cp $TEMENOS_HOME/T24/bnk/Extensions/EB_OFSConnectorService/t24ws/t24-EB_
OFSConnectorService-tafj-jws.aar WEB-INF/services
cp $TEMENOS_HOME/T24/bnk/Extensions/EB_ResourceProviderService/t24ws/t24-EB_
ResourceProviderService-tafj-jws.aar WEB-INF/services
cp $TEMENOS_HOME/T24/bnk/Extensions/IF_InflowService/t24ws/t24-IF_InflowService-tafj-
jws.aar WEB-INF/services
cp $TEMENOS_HOME/T24/bnk/Extensions/IF_IntegrationFlowService/t24ws/t24-IF_
IntegrationFlowService-tafj-jws.aar WEB-INF/services
cp $TEMENOS_HOME/T24/bnk/Extensions/IF_IntegrationFrameworkService/t24ws/t24-IF_
IntegrationFrameworkService-tafj-jws.aar WEB-INF/services
cp $TEMENOS_HOME/T24/bnk/Extensions/IF_IntegrationLandscapeService/t24ws/t24-IF_
IntegrationLandscapeService-tafj-jws.aar WEB-INF/services
7. Open the /WEB-INF/services/services.list file in a text editor of your choice and add the names of the component
service archives that you have copied to the services directory.

t24-EB_CatalogService-tafj-jws.aar
t24-IF_IntegrationLandscapeService-tafj-jws.aar
t24-DS_DesignStudioInstallerService-tafj-jws.aar
t24-EB_OFSConnectorService-tafj-jws.aar
t24-EB_ResourceProviderService-tafj-jws.aar
t24-IF_IntegrationFlowService-tafj-jws.aar
t24-IF_IntegrationFrameworkService-tafj-jws.aar
t24-IF_InflowService-tafj-jws.aar
version-1.8.2.aar

8. Open /WEB-INF/web.xml in an editor and configure database connectivity by adding the Transact data sources at the end
of the web.xml file.

<error-page>
<error-code>500</error-code>
<location>/axis2-web/Error/error500.jsp</location>
</error-page>

<!-- 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">

47
Stack 1 JBoss – Red Hat, version 1.0

<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>
</web-app>

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

<?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>
<resource-ref>
<res-ref-name>jdbc/t24RODataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24RODS</jndi-name>
</resource-ref>
</jboss-web>

10. Delete the previous axis2.war file and create the new version of it.

rm –rf axis2.war
jar cf axis2.war *

11.2 Deploying Axis2

Procedure

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>

48
Stack 1 JBoss – Red Hat, version 1.0

jdbc:sqlserver://10.23.50.XXX:1433;databaseName=MBR23;integratedSecurity=false;encrypt=tru
e;trustServerCertificate=true</connection-url>
<connection-property name="defaultRowPrefetch">
100
</connection-property>
<driver>com.microsoft.sqlserver.jdbc.SQLServerDriver</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>

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.149:1521/ORCLPDB3</connection-url>
<connection-property name="defaultRowPrefetch">
100
</connection-property>
<driver>ora19c<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:

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

enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:postgresql://10.23.50.XX:5432/R23AMR?idle_in_transaction_session_
timeout=2000&tcpKeepAlive=true&cleanupSavepoints=true</connection-url>
<connection-property name="defaultRowPrefetch">
100
</connection-property>

49
Stack 1 JBoss – Red Hat, version 1.0

<driver>org.postgresql.Driver</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>

3. Copy axis2.war from the inst directory to $JBOSS_HOME/standalone/deployments.

cp axis2.war $JBOSS_HOME/standalone/deployments

50
Stack 1 JBoss – Red Hat, version 1.0

12 Performing a post deployment sanity check

You need to log in to Transact using Transact Explorer to verify your application server deployment.

12.1 Starting the application server

As the first verification step, start the application server with all deployed artefacts. Your startup command uses the
standalone.sh shell script that is in $JBOSS_HOME/bin.

To start JBoss with all the artefacts deployed, run the following command:
./standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 --server-config=Transact.xml -
Djboss.http.port=9089

12.2 Accessing TAFJEE

The TAFJJEE_EAR.ear file contains a WAR file that is a helper servlet for configuring, running software diagnostics, executing
commands 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.

2. Create an application user by executing add-user.sh.
3. Give the user TAFJAdmin role.
a. Specify the type of user, here Application user.

./add-user.sh
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): b

b. Provide the preferred user name: here the user is jumpstart.

Enter the details of the new user to add.

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

c. Provide the password (here Temenos@1234) and then enter it again.

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}

51
Stack 1 JBoss – Red Hat, version 1.0

- The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s),

1 non-alphanumeric symbol(s)
Password :
Re-enter Password :

d. Specify the groups the user should belong to; here TAFJAdmin.

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

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

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

Is this correct yes/no? yes

f. For the last question, provide the answer no.

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

7.4/standalone/configuration/application-users.properties'
Added user 'jumpstart' to file '/srv/Temenos/3rdParty/AS/jboss-eap-
7.4/domain/configuration/application-users.properties'
Added user 'jumpstart' with groups TAFJAdmin to file '/srv/Temenos/3rdParty/AS/jboss-eap-
7.4/standalone/configuration/application-roles.properties'
Added user 'jumpstart' with groups TAFJAdmin to file '/srv/Temenos/3rdParty/AS/jboss-eap-
7.4/domain/configuration/application-roles.properties'
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 Jakarta Enterprise Beans calls.
yes/no? no

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

http://hostname_or_ip_address:9089/TAFJEE
5. Supply the application user credentials and click Sign in (Chromium-based web browsers). The TAFJEE web page is
displayed.

52
Stack 1 JBoss – Red Hat, version 1.0

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

6. To perform a quick test, click the tShow servlet and in the Routine name field, enter EX to view the compilation details of a
Transact routine on the application server.

12.3 Accessing Transact Explorer

Procedure

1. Access BrowserWeb using the following URL:

http://hostname_or_ipaddress:9089/transact-explorer-wa.

53
Stack 1 JBoss – Red Hat, version 1.0

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

After a successful login, the landing page is displayed.

54
Stack 1 JBoss – Red Hat, version 1.0

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

12.4 Accessing Axis2 servlet

Procedure

1. Access the Axis2 servlet using the following URL:

http://hostname_or_ipaddress:9089/axis2

2. Click Validate.

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

55
Stack 1 JBoss – Red Hat, version 1.0

3. Go back to the home page.

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

56
Stack 1 JBoss – Red Hat, version 1.0

12.5 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.

2. Create a new SOAP project using WSDL in a third-party tool such as SOAPUI: Click File > New SOAP Project. The initial
window opens.
3. Specify the project name and the URL of the initial WSDL file, for example
http://10.23.50.153:9089/axis2/services/IntegrationFlowServiceWS?wsdl, and then click OK.

4. Issue a flow request passing the necessary parameters: In the first binding, expand readFlow and double click Request 1.

57
Stack 1 JBoss – Red Hat, version 1.0

5. Enter the requested parameter values for <xsd:password>, <xsd:user> and <int:flowName>.

Tip: The flowName value can be any of the flows you see in IF.INTEGRATION.FLOW.CATALOG.

58
Stack 1 JBoss – Red Hat, version 1.0

6. In the upper-left corner of the request window, click the green triangle button to execute the query.

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

Results:You have now completed the deployment of TAFJ, Transact and Transact Explorer on JBoss EAP 7.4 with a supported
database (MS SQL Server 2019, Oracle 19c or PostgreSQL 15). You are now able to perform business operations in Transact
using Transact Explorer.

59