Stack 1 Red Hat - JBoss

Customer Runbook 1.5 August 2020

All post R17 AMR releases up to and including R18 AMR
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

Contents
1 About this Runbook 4
1.1 Stacks table 4
1.2 Scope 4
1.3 Audience 4
1.4 Skills and knowledge 4
1.5 Other stack runbooks 5
1.6 Legal 6
1.7 History 7
2 Introduction 8
3 Prerequisites and assumptions 9
3.1 Prerequisites 9
3.2 Creating the target directory structure 9
3.3 Directory structure diagram 10
3.4 Setting the environment variables 10
4 Before you start 11
4.1 Supporting documentation 11
4.2 Verifying the system 11
5 Installing TAFJ 14
6 Installing and configuring Transact 16
6.1 Installing Transact 16
6.2 Configuring Transact 16
7 Configuring the database 17
7.1 Improving database performance 18
8 Verifying the installation of Transact 19
8.1 Starting Transact in Classic view 19
8.2 Running DBTools 20
9 Configuring JBoss modules 22
9.1 Configuring a TAFJ module 22
9.2 Configuring the Transact modules 23
9.3 JBossTools 24
9.3.1 Command syntax 24
9.3.2 Options 24
9.4 Using JBossTools 24
9.5 Configuring the Oracle database driver module 25

2
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

9.6 Editing configuration files 26

9.6.1 Editing the standalone.conf file 26
9.6.2 Configuring a new profile 27
9.6.3 Configuring Transact and TAFJ in the application server 28

10 Installing and configuring UXP Browser 31

11 Deploying applications 32
11.1 Starting the application server 32
11.1.1 Default http port 32
11.2 Deploying TAFJEE 33
11.3 Deploying BrowserWeb 34
11.4 Deploying Axis2 35
11.5 Deploying UXP Browser 36
12 Glossary 38

3
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

1 About this Runbook

The Stack 1 Red Hat - JBoss Runbook describes how to configure TAFJ-Transact on a JBoss
application server. It also shows you how to deploy a Temenos browser and access Transact using that
browser. This runbook is relevant to all 18.x releases up to and including R18.

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

1 .1 Stacks table
For the latest version of the stacks table, see either the Temenos Customer Portal or the Temenos
Partner Portal.

1 .2 Scope
This runbook covers:

l Installing TAFJ.
l Installing Transact.
l Configuring JBoss 7.2 EAP.
l Transact and TAFJ artefacts in JBoss.

1 .3 Audience
This runbook is designed for technical consultants who want to deploy TAFJ-Transact on a JBoss
application server EAP 7 and access it through a browser.

1 .4 Skills and knowledge

To use this runbook, you need a basic understanding of both TAFJ-Transact and JBoss application
servers.

4
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

1 .5 Other stack runbooks

For all stack runbooks, customers should see https://tcsp.temenos.com/sv/SitePages/Home.aspx and
partners should see https://tpsp.temenos.com/StackVerification/SitePages/Home.aspx.

5
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

1 .6 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
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

1 .7 History

Version Date Description Author

1.0 July 2017 Initial release of this runbook Surender Padakanti

Reorganised, added the standalone

1.1 August 2017 Kudakwashe Dzvuke
xml file configuration steps.

1.2 September 2017 Technical author edits and formatting Dominik Wietrzak

Updated the Stacks table. Various

1.3 May 2018 Jonathan Page
text edits.

1.4 May 2018 Updated Deploying TAFJEE Aidan Pasquale

1.5 August 2020 Rebranding changes. Robert Norledge

7
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

2 Introduction
This Stack 1 Red Hat - JBoss Runbook describes how to install and configure TAFJ-Transact on a
Red Hat Linux server v7 Operating System.

After TAFJ-Transact is installed on the Linux server, the stack is deployed using a JBoss application
server. You access the system through a Temenos browser.

8
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

3 Prerequisites and assumptions

The following chapter describes the technical prerequisites and assumptions for installing and
configuring the Red Hat - JBoss stack.

3 .1 Prerequisites
Before you start to install and configure the stack, you must have installed all 3rd party software,
including:

l JDK 1.8
l Oracle 12c database
l JBoss 7 EAP

The TAFJ runtime, T24 libraries and BrowserWeb.war files are available from Distribution for copying
into the Linux server. UXP Browser related files are also provided by Distribution - these include the
UXP Browser folder, hothouse-iris.war and browser-iris.war.

Note:
Remember to set the corresponding environment variables for 3rd party software. For example, set
JAVA_HOME to the Java installed path.

3 .2 Creating the target directory structure

Create the following directory structure on the Linux server:

Procedure

1. In home directory, create the Temenos directory.

2. In the Temenos directory, create the following directories:

Directory Description

Install The Install directory contains all installers to setup TAFJ-Transact.

9
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

Directory Description

The 3rdParty directory contains all installed third-party software like JDK
3rdParty
1.8, JBoss 7 EAP etc.

TAFJ The TAFJ directory contains TAFJ runtime libraries.

T24 The T24 directory contains all Transact-related libraries.

3 .3 Directory structure diagram

Temenos
├───3rdParty
│ ├───As
│ │ ├───JBOSS
│ │ ├───WAS
│ │ └───Weblogic
│ ├───Java
│ └───Jms
├───Install
│ ├───t24inst
│ └───tafjinst
├───T24
│ ├───lib
│ │ ├───LocalDev
│ │ └───t24lib
│ └───Src
│ ├───LOCAL.BP
│ └───T24.BP
└───TAFJ
├───ext
├───lib
├───RulesEngine
├───T24Email
├───T24Sms
└───UD

3 .4 Setting the environment variables

Set the environment variables according to the above directory structure:

l TEMENOS_HOME = path_of_Temenos_directory
l JDK_HOME = path_of_JDK
l TAFJ_HOME = path_of_TAFJ
l T24_HOME = path_of_T24

10
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

4 Before you start

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

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

4 .1 Supporting documentation
The TAFJ runtime contains a doc directory, which contains various documents on TAFJ utilities. It also
contains installation guides for various databases and application servers.

4 .2 Verifying the system

Procedure

1. Check how much free disk space you have - run the following command:

df –h

2. To check if the required OS version is used, type uname –a in the command line and check the
platform and version.

3. You can also run the following command to get more user friendly information:
cat /etc/*-release

4. Check disk drive space by running the following command:

df –h

11
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

5. Check that you can connect to your database. To do that, you can use the Oracle SQL Developer
tool.

6. Verify that the required JDK is installed by checking the JAVA_HOME environment variable. To do
that, run the following command on the server:

java -version

12
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

Note:
Your Java development Kit needs to be installed in the Temenos/3rdParty/Java
directory.

13
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

5 Installing TAFJ
The following chapter describes how to install TAFJ. The TAFJ runtime is a tar file. The filename is
TAFJ.DEV.201705.0.tar.gz.

Procedure

1. Change to the Install directory:

cd $TEMENOS_HOME/Install

2. Create the tafjinst directory inside the Install directory:

mkdir tafjinst

3. Extract the contents of the tafj file into the tafjinst directory.

tar -C tafjinst -xvf TAFJ.DEV.201705.0.tar.gz

4. After extraction, navigate to the tafjinst directory.

cd $TEMENOS_HOME/Install/tafjinst

5. Execute the Setup_TAFJ.DEV.201705.0.sh file and provide the TAFJ directory path. TAFJ
is now installed.
6. To view the directories in TAFJ, enter the following commands:

cd $TAFJ_HOME

ls

14
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

7. Use tDiag to check that you've set your TAFJ variables properly:

8. After you've installed TAFJ, change the permissions on the bin directory. To do this, use the
command for executing TAFJ utilities:

chmod 755 $TAFJ_HOME/bin/*

9. Use tVersion to check that you've installed the right version of TAFJ:

Important:
Make sure that the JDK is installed before trying to install TAFJ. See Prerequisites.

15
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

6 Installing and configuring Transact

The following chapter describes how to install and configure Transact.

Ensure that you have created the T24 directory. For more information, see Prerequisites.

6 .1 Installing Transact
Procedure

1. In the T24 directory, create the Lib/T24Lib directory.

2. Copy the jar files from t24lib into the Lib/T24Lib directory. This directory contains all the
t24 jars.

6 .2 Configuring Transact
Procedure

1. In $TAFJ_HOME/conf directory, go to the properties file.

2. In the properties file, specify the path to the t24lib directory in the precompile Transact
directory. The path will look similar to the one below:

3. Specify the UD directory path, as shown below:

16
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

7 Configuring the database

This chapter describes how to add the database parameters in the properties file.

Procedure

1. Specify the URL of the Oracle database for the parameter temn.tafj.jdbc.url.
2. Specify the JDBC driver name for the Oracle database for the parameter
temn.tafj.jdbc.driver. In the example below, the driver name is
oracle.jdbc.driver.OracleDriver.
3. Specify a user name for accessing the database for the parameter
temn.tafj.jdbc.username. In the example below, the user name is t24.
4. Specify a password for accessing the database for the parameter
temn.tafj.jdbc.password. In the example below, the password is t24.

5. Add the database drivers to the $TAFJ_HOME\ext path. The oracle-12c directory is copied
across.
6. Copy the oracle-12c directory (with its contents) that is in $TAFJ_HOME/dbdrivers to the
ext directory:

17
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

The database drivers are provided in $TAFJ_HOME\dbdrivers path - however, this is only for
reference. You need to copy the drivers from the database installation directory.

7 .1 Improving database performance

For performance reasons, you need to change the value of the keys
temn.tafj.jdbc.write.use.merge and temn.tafj.jdbc.write.use.merge.no.xml
from true to false.

# 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

18
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

8 Verifying the installation of Transact

The following chapter describes how to check Transact, after you've installed and configured it for
standalone mode.

8 .1 Starting Transact in Classic view

Procedure

1. Change to $TAFJ_HOME/bin.
2. Execute tRun EX.
3. Log into the application using a valid Transact user name and password.

The home screen is displayed.

4. Run the following command:

SPF S SYSTEM

You can see that the current release in 201705 is R18.1.

19
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

8 .2 Running DBTools
To access DBTools, you need to create a user using the tUserMgnt utility. You use the same user
name and password to log into DBTools.

When you've accessed DBTools, you can verify database:

l Name
l IP address
l User name

Procedure

1. At the command line, change to TAFJ_HOME/bin.

2. Create a user for accessing the database:

tUserMgnt --Add -u TAFJ123 -p Temenos@123

3. Start DBTools:

DBTools -u TAFJ123 -p Temenos@123

20
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

The DBTools initial screen is displayed.

21
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

9 Configuring JBoss modules

This chapter describes how to configure the JBoss modules for TAFJ, Transact and the database.

9 .1 Configuring a TAFJ module

Procedure

1. Create a global module com/temenos/tafj/main under the $JBOSS_HOME/modules

directory.

cd $JBOSS_HOME/modules
mkdir com/temenos/tafj/main
cd $JBOSS_HOME/modules/com/temenos/tafj/main

2. Create a symbolic link to $TAFJ_HOME/lib:

ln -s $TAFJ_HOME/lib lib

3. Verify that the link has been created properly:

ls –ail

4. Copy the file module.xml from TAFJ:

cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/temenos/tafj/module.xml
$JBOSS_HOME/modules/com/temenos/tafj/main

5. Edit the file module.xml to add the Oracle 12c database dependency.

vi $JBOSS_HOME/modules/com/temenos/tafj/main/module.xml

22
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

The module.xml file that you need to use for TAFJ is present in the path $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/temenos/tafj. Remember to add the
dependency module for the database in the dependencies section.

9 .2 Configuring the Transact modules

Procedure

1. Create a global module com/temenos/t24/main under $JBOSS_HOME/modules.

cd $JBOSS_HOME/modules
mkdir com/temenos/t24/main
cd $JBOSS_HOME/modules/com/temenos/t24/main

2. Create a symbolic link to $T24_HOME/Lib.

ln -s $T24_HOME/Lib/T24Lib lib

3. Verify that the link has been created properly:

ls –ail

4. Generate the module.xmlfor Transact.

23
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

9 .3 JBossTools
Transact contains many libraries, which makes adding the jars into module.xml a lengthy process. To
make it easier, TAFJ provides a utility (JBossTools) to generate/update module.xml.

You need to run Module Generator (JBossTools.sh) from $TAFJ_HOME/bin with the required
arguments:

9.3.1 Com m and syntax

JBossTools module_name path_to_jars dest [root_prefix] [-tafjdep]

9.3.2 O ptions

Option Description

module_name Name of the JBoss module.

The list of directories that you want to parse. Use the operating system path
path_to_jars
separator between directories.

The directory - or path to the directory - where you want the file module.xml to
dest
be generated.

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

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

9 .4 Using JBossTools
Procedure

1. Create a Transact module.xml file - run the following command:

JBossTools com.temenos.t24 $T24_HOME/Lib/T24Lib $JBOSS_

HOME/modules/com/temenos/t24/main lib –tafjdep

2. Open module.xml in your text editor and verify if dependency module for tafj is present. Add

24
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

the dependency module if it is not present.

9 .5 Configuring the Oracle database driver module

Procedure

1. Create a global module com/oracle/ora12c/main under $JBOSS_HOME/modules

directory.

cd $JBOSS_HOME/modules
mkdir com/oracle/ora12c/main
cd $JBOSS_HOME/modules/com/oracle/ora12c/main

2. Copy module.xml from TAFJ:

cp $TAFJ_
HOME/appserver/jboss/jboss7eap/modules/com/oracle/ora12c/module.xml
$JBOSS_HOME/modules/com/oracle/ora12c/main

3. Finally, copy the dbdrivers directory from TAFJ:

cp $TAFJ_HOME/dbdrivers/oracle-12c/* $JBOSS_
HOME/modules/com/oracle/ora12c/main

25
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

9 .6 Editing configuration files

9.6.1 Editing the standalone.conf file

Procedure

You need to configure several parameters in the standalone.conf file that is in JBOSS_HOME/bin.

1. Open the standalone.conf file in your text editor.

2. Find the section with the options that you pass to the Java virtual machine.
3. On a new line, begin the new Java_OPTS definition:

JAVA_OPTS="%JAVA_OPTS%

4. If you are deploying the UXP Browser, increase your memory settings by adding the following
snippet at the end of the new line. Example:

JAVA_OPTS="-Xms1G –Xmx2G -XX:MaxPermSize=450m"

5. Add the TAFJ_HOME definition:

-Dtafj.home=$TAFJ_HOME

6. Optional: If you don’t want to run JBoss with the default port, specify the new port number:

-Djboss.socket.binding.port-offset=1009

7. Optional: Specify the encoding:

-Dfile.encoding=UTF-8

8. Optional: Specify the node name to use JBoss remoting lookup:

-Djboss.node.name=node1

26
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

9. Save the changes.

Result: You have provided the new configurations in the following snippet:

JAVA_OPTS="%JAVA_OPTS% -DARC_CONFIG_PATH=$JBOSS_HOME\BrowserSecurity\sso.config -DARC_

CONFIG_APP_NAME=SPNEGO -Dtafj.home=$TAFJ_HOME -Djboss.socket.binding.port-offset=1009 -
Dfile.encoding=UTF-8 -Djboss.node.name=node1"

9.6.2 Configuring a new profile

In this scenario, you are going to create a standalone server for Transact in the Application layer. The
standalone name will be T24AppStd.

In JBoss EAP 7, in standalone mode, the configuration files are present in the
standalone/configuration directory of JBoss. In domain mode, the configuration files are
present in domain/configuration directory of JBoss.

Before you begin

The following is the suggested nomenclature for profile naming.

Parameter Value Explanation

Transact

product_name AML

TAP

App Application layer

Business_
role Web layer or
Web
presentation layer

Std Standalone

type Mng Managed

Clu Cluster

number From 00 to 99

You can create a standalone server for Transact in the application layer. The profile name will be
T24AppStd01.

27
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

Follow the same nomenclature to specify the server name. The name will be T24AppSrv01. You can
have multiple profiles on one server, for example you can have profiles T24AppStd01, T24AppMgr01,
and T24AppMng01 on the same machine T24AppSrv01.

Procedure

Copy and save the standalone-full.xml file as T24AppStd01.xml in the configuration

directory.

9.6.3 Configuring Transact and TAFJ in the application server

Procedure

1. Open the tafj.properties file in your text editor. The file is in the following location:

$TAFJ_HOME/appserver/jboss/jboss6eap/jboss-cli

2. Provide the following parameters values: DB_URL, DB_DRIVER, DB_USER and DB_PWD.

3. Change to the $TAFJ_HOME/appserver/jboss/jboss6eap/jboss-cli directory and

open the T24Setup.cli file in your text editor.

28
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

4. Under the drivers section, uncomment the line SQLServer drivers parameters.

5. Move to the $JBOSS_HOME/bin directory and open the jboss-cli.xml file in your text editor.
6. Set the value of the following parameters to true:
l resolve-parameter-values
l validate-operation-requests

7. Start JBoss by running the following command:

$JBOSS_HOME/bin/standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 --
server-config=T24AppStd01.xml
8. Run the jboss-cli command:

$ jboss-cli.sh --connect --
file=/storage/hamsa/Temenos/TAFJ/appserver/jboss/jboss7eap/jboss-
cli/T24Setup.cli --
properties=/storage/hamsa/Temenos/TAFJ/appserver/jboss/jboss7eap/jb
oss-cli/tafj.properties

Do not copy and paste this command. Type it at the command-line.

9. Open the modified T24AppStd01.xml file in your editor to verify that the following parameters
have been configured:
l System properties
l Drivers
l Data sources

29
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

l Global modules (TAFJ and Transact)

l JMS Pools
10. Stop the JBoss instance.

30
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

10 Installing and configuring UXP

Browser
Procedure

1. Upload the UXPBrowser.war, browser-iris.war and the UXP Browser zip files to the
$TEMENOS_HOME/Install directory.
2. Create the UXPBrowser directory under $TEMENOS_HOME.
3. Extract the contents of the UXP Browser zip file to $TEMENOS_HOME/UXPBrowser. The
UXPBrowser directory contains the generated and manual directories.
4. Add the environment variable GENERATED with the value of the path to the generated directory

export GENERATED=$TEMENOS_HOME/UXPBrowser/generated

5. Add the environment variable MANUAL with the value of the path to the manual directory:

export MANUAL=$TEMENOS_HOME/Install/UXPBrowser/manual

31
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

11 Deploying applications
The following chapter describes how to deploy TAFJEE, BrowserWeb and Apache Axis 2. It also shows
you how to deploy the stack through the new browser, the UXP Browser.

After you have edited the standalone-full.xml file, restart the JBoss application server.

1 1 .1 Starting the application server

The standalone.sh script in $JBOSS_HOME\bin is used to start JBoss. It takes several parameters
depending on your needs.

To start JBoss with BrowserWeb, run the following command:

./standalone.sh -c T24AppStd01.xml -b 0.0.0.0

To start JBoss with UXP Browser, run the following command (with several parameters):

./standalone.sh -c T24AppStd01.xml -Djboss.node.name=node1 -b 0.0.0.0

-Dcom.edgeipk.librarypath=$GENERATED/edge
-Doverride.IRIS_MAP=$MANUAL/edge/data/HrefComponentManualMap.properties,
$GENERATED/edge/data/HrefComponentMap.properties -
Dcom.temenos.interaction.config.dir=$GENERATED/iris
-Djboss.as.management.blocking.timeout=1200 -Doverride.IRIS_
ROOT=http://localhost:8080/hothouse-iris/Hothouse.svc

Note:
You have to kill your JBoss process if you started it with the BrowserWeb parameter. You also have
to use the -Doverride.IRIS_ROOT parameter in non-UTP environments.

11.1.1 Default http port

The default http port is 8080, as set in the JBoss configuration file in the socket-binding section for http
name. You can access the deployed applications such as Transact browser and axis2 with this port.

32
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

1 1 .2 Deploying TAFJEE
You need to deploy TAFJEE_EAR.ear in the $JBOSS_HOME/standalone/deployments
directory.

Procedure:

1. Copy the TAFJEE_EAR.ear file into the deployments directory of JBoss:

cp –r $TAFJ_HOME/appserver/jboss/jboss7eap/TAFJJEE_EAR.ear $JBOSS_
HOME/standalone/deployments

2. Copy TAFJSpoolerPlugins.rar to the deployments folder:

cp –r $TAFJ_HOME/appserver/TAFJSpoolerPlugins.rar $JBOSS_
HOME/standalone/deployments

3. Check the server console messages for any deployment errors.

4. When the TAFJEE_EAR.ear file has been deployed, access the TAFJ services which are
available at the following URL in your web browser:

http://app_server_ip_address:port/TAFJEE

33
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

The following screen is displayed:

1 1 .3 Deploying BrowserWeb
You need to deploy the BrowserWeb application for your specific version of TAFJ-Transact in the
$JBOSS_HOME/standalone/deployments directory. For example, the BrowserWeb.war
located on the path $TEMENOS_HOME/Install/BrowserWeb-201705.00.tar.

Procedure

1. Upload the BrowserWeb.tar file for your specific version of TAFJ-Transact to the $TEMENOS_
HOME/Install/browserweb directory.
2. Create the directory BrowserWebwar then untar the tar file.
3. Copy the BrowserWebwar directory into the deployments directory of JBoss:

cp $TEMENOS_HOME/Install/browserwebwar/BrowserWeb-
201705.00/BrowserWeb.war $JBOSS_HOME/standalone/deployments

4. Check the server console messages for any deployment errors.

34
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

5. Access the web user interface by going to http://app_server_ip_

address:port/BrowserWeb.
6. Log on to the Transact application with a valid user name and password.

1 1 .4 Deploying Axis2
Installing axis2.war is only required for accessing Integration Framework services. You do not need
Axis2 as of now. It is just one of the prerequisites that you are installing.

Procedure

1. Upload the axis2.war to the $TEMENOS_HOME/Install directory.

2. Copy the axis2.war from the Install directory to the JBoss deployments directory:

cp –r $TEMENOS_HOME/Install/axis2.war $JBOSS_
HOME/standalone/deployments

3. Check the server console messages for any deployment errors.

35
 S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

4. Access the available web services by going to the following url:

http://app_server_ip_address:port/axis2

1 1 .5 Deploying UXP Browser

Before deploying the UXP Browser check that the TAFJ, Transact and database modules have been
deployed and configured. The configuration file needs to contain details of the database, tafj and
t24 modules.

For the UXP Browser to work, the minimum version of TAFJ-Transact required is DEV201705.

Procedure

1. Copy the UXPBrowser.war and browser-iris.war files into the deployments directory.

cp $TEMENOS_HOME/Install/UXPBrowser.war $JBOSS_
HOME/standalone/deployments

2. Copy the browser-iris.war into the deployments directory.

cp $TEMENOS_HOME/Install/browser-iris.war $JBOSS_
HOME/standalone/deployments

36
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

3. UXP Browser takes a little bit longer to get fully deployed, so wait and check the console
messages.
4. Access the UXP browser with the following URL:

http://app_server_ip_address:8080/Browser

5. Log in with your user ID and password.

37
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

12 Glossary
A

Axis2
Apache Axis2 is a core engine for Web services. Axis2 provides the capability to add Web services
interfaces to Web applications.

BrowserWeb
A Temenos browser, used for accessing the Transact application.

IIB v10
IBM Integration Bus version 10

Integration
Communication between two or more systems.

Interaction
Communication between an automated system and a human user.

JBoss
JBoss Application Server (JBoss AS) is an open-source, cross-platform Java application server
developed by JBoss, a division of Red Hat Inc. JBoss AS is an open-source implementation of Java 2
Enterprise Edition (J2EE) that is used for implementing Java applications and other Web-based
applications and software.

JDK
Java Development Kit

38
S ta c k 1 R e d H a t - J B o s s R u n b o o k 1 .5

JMS
Java Message Service (JMS) is an application program interface (API) from Sun Microsystems that
supports the formal communication known as messaging between computers in a network.

Oracle 12c
Oracle Database 12c is an enterprise-class database from Oracle. Its features include pluggable
databases and multitenant architecture.

SOAP
Simple Object Access Protocol. An XML-based messaging protocol that uses HTTP.

TAFJ
Temenos Application Framework Java

Transact
Transact is Temenos' core banking solution

UXP Browser
The new browser from Temenos, designed to access the Transact application

WebSphere MQ
Renamed IBM MQ in 2014. IBM's enterprise messaging solution. It allows independent and potentially
non-concurrent applications in a distributed system to communicate securely with each other.

39