Stack 3 Red Hat -

WebLogic
Customer Runbook 2.1 November 2020
All post R19 AMR releases up to and including R20 AMR
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

Contents
1 About this runbook 4
1.1 Stacks table 4
1.2 Scope 4
1.3 Audience 4
1.4 Skills and knowledge 5
1.5 Legal 6
1.6 History 7
2 Introduction 8
2.1 UXP Browser Generate On Demand (GOD) mode 8
2.1.1 Components deployed in GOD mode 9
2.1.2 Enterprise Java Beans (EJB files) 10
2.2 Recommended heap size requirement 10
3 Prerequisites and assumptions 11
3.1 Prerequisites 11
3.1.1 Third party software 11
3.1.2 Temenos artefacts 11
3.2 Assumptions 13
4 Before you start 14
4.1 Checking the operating system 14
4.2 Checking the disk space 14
4.3 Creating the directory structure 14
4.4 Configuring the environment variables 15
4.5 Checking the JDK 16
4.6 Checking the database connection 16
4.7 Checking the WebLogic installation 17
5 Installing Transact and TAFJ 18
5.1 Installing Transact 18
5.2 Installing TAFJ 19
5.3 Deploying the Oracle 19c database driver 22
6 Configuring TAFJ 24
6.1 Configuring the properties file 24
6.2 Verifying the TAFJ installation 26
7 Sanity checks 28
7.1 Accessing Temenos Classic 28

2
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7.2 Running DBTools 29

8 Configuring TAFJ and Transact in WebLogic 31
8.1 Starting WebLogic Server 31
8.2 Configuring WebLogic class paths 38
8.3 Configuring the [Link] file 39
8.4 Running the T24Setup script 41
8.4.1 Testing the database connection 44
8.5 Accessing the TAFJEE servlet 45
8.6 Accessing BrowserWeb 48
9 Configuring UXPBrowser in Generate on Demand (GOD) mode 50
9.1 Extracting the UXPBrowser artefacts 50
9.2 Generating the keystore files 54
9.3 Adding JVM arguments for UXP Browser 57
9.4 Configuring [Link] 57
9.5 Configuring [Link] 58
9.6 Installing [Link] 59
9.7 Installing [Link] 63
9.8 Installing [Link] 67
9.9 Installing [Link] 70
9.10 Installing [Link] 74
9.11 Installing t24-EB_CatalogService-[Link] 77
9.12 Installing t24-EB_ResourceProviderService-[Link] 80
9.13 Installing t24-EB_AuthenticationService-[Link] 84
9.14 Configuring [Link] for UXP Browser 88
9.15 Accessing the UXP Browser 89
10 Configuring and deploying Axis2 91
10.1 Configuring the Axis2 war 91
10.2 Installing [Link] 93
10.3 Accessing the Axis2 servlet 96
10.4 Integrated testing of axis2 and Transact 97

3
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

1 About this runbook

The Stack 3 Red Hat - WebLogic Runbook describes how to configure TAFJ-T24 on an Oracle
WebLogic application server ([Link].0) with an Oracle 19c database. When you have completed the
deployment, you will be able to perform business operations in Transact using BrowserWeb and UXP
Browser in Generate of Demand (GOD) mode.

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 Oracle WebLogic ([Link].0).
l Deploying Transact and TAFJ artefacts in Oracle WebLogic.

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

4
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

1 .4 Skills and knowledge

To use this runbook, you need a basic understanding of the following:

l Transact
l TAFJ
l WebLogic
l Oracle database

5
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

1 .5 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 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

1 .6 History

Version Date Description

1.0 July 2019 Initial release of this runbook.

1.1 November 2019 Added modifications from 201910.

Corrected the T24_HOME path. Added the BNK_HOME variable

2.0 August 2020 and Configuring and Deploying UXP Browser in Generate On
Demand (GOD) Mode

2.1 November 2020 Added section on help text.

7
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

2 Introduction
This runbook helps you to set up the development/ test environment for Transact-TAFJ on a Red Hat
Linux server v7 operating system. It guides you through the installation and configuration of TAFJ,
Transact and Oracle WebLogic to access the Transact browser.

This runbook uses a 2-tier architecture with an application server and a database [Link] application
tier contains the WebLogic (version [Link].0) application server with Transact/TAFJ. The database
tier contains the Oracle 19c database that stores Transact data.

2 .1 UXP Browser Generate On Demand (GOD) mode

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

8
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

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

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

2.1.1 Com ponents deployed in G O D m ode

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

Authenticator ([Link])

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

UXP Browser ([Link])

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

Resource server ([Link])

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

9
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

Interaction Framework Resource Provider service ([Link])

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

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

Interaction Framework Catalog services ([Link])

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

2.1.2 Enterprise Java Beans (EJB files)

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

l Authentication service EJB (t24-EB_AuthenticationService-[Link]).

l Catalog service EJB (t24-EB_CatalogService-[Link]).

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

2 .2 Recommended heap size requirement

Initial heap size Maximum heap size

8G 18G

Note: For testing environments, 5-8G RAM is sufficient.

10
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3 Prerequisites and assumptions

The following sections describe the technical prerequisites and assumptions for installing and
configuring the Red Hat - WebLogic stack.

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

3.1.1 Third party software

Software Version

Oracle WebLogic Application Server [Link].0

JDK 1.8

Oracle 19c [Link].0

SQL Developer

3.1.2 Tem enos artefacts

Note: Temenos artefacts are available from the Distribution team (distribution@[Link]).

Artefacts File Contents

[Link].TAFJR20.30-
Oracle dump file Contains the database.
[Link]

The bnk directory that

Transact [Link]
holds the Transact libraries.

The TAFJ runtime .jar

TAFJ [Link] file, TAFJ patch script and
TAFJ setup script.

Transact Browser [Link] Older browser components.

11
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

Artefacts File Contents

Transact HelpText
HELP-TEXT [Link]
documentation

UXP browser components:

[Link]

[Link]
UXPBrowser [Link]
[Link]

[Link]

[Link]

t24-EB_AuthenticationService-
[Link]
EJB Jars required for
deploying the UXP Browser
T24/bnk/Extensions t24-EB_CatalogService-[Link]
in Generate On Demand
mode
t24-EB_ResourceProviderService-
[Link]

Catalog services war:

IRIS18 Catalog Services IRISR18_CatalogServices_TAFJ_20.0.1

irf-t24catalog-
[Link]

Axis2 [Link] Apache web services tool

Required for configuring

Password Encryption Tool [Link]
UXP in GOD mode

12
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3 .2 Assumptions
Note: See the for the installation paths followed in this runbook.

The following assumptions are made for this runbook.

l Transact data has been loaded into the Oracle 19c database from the .dmp file.

l The database has been loaded with TAFJ related stored procedures or Java functions.

Note: See the database specific installation document in $TAFJ_HOME/doc.

l All third party software has been installed.

l All Temenos artefacts have been copied to the desired installation path.

13
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

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 Checking the operating system

To check that your system is running on Red Hat Enterprise Linux Version 7, execute the following
command in the Linux shell.

cat /etc/redhat-release

The following information should be displayed.

4 .2 Checking the disk space

The installation requires a minimum of 30 GB disk space. To check there is sufficient space, execute this
command in the Linux shell.

df -h

4 .3 Creating the directory structure

In the Linux shell, navigate to your user home directory and create the following directory structure.

mkdir Temenos
mkdir -p Temenos/TAFJ
mkdir -p Temenos/T24
mkdir -p Temenos/UXPBrowser
mkdir -p Temenos/3rdParty/AS
mkdir -p Temenos/install

14
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

The following table describes the directory structure.

Folder Contents

3rdParty Third party software (for example, JDK 1.8 and WebLogic).

Installers required to setup TAFJ-Transact. It contains sub-folders t24inst

Install (containing Transact installation files) and tafjinst (containing TAFJ installation
files).

T24 Transact related libraries.

TAFJ TAFJ runtime libraries.

UXPBrowser The UXP browser artefacts.

4 .4 Configuring the environment variables

Before installing Transact-TAFJ, you must configure the environment variables.

Procedure

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

cd /srv/Temenos

2. Open the .bash_profile file.

vi .bash_profile

3. Enter the variables as illustrated below.

#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
echo $T24_HOME

15
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

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

#BRP_HOME
export BRP_HOME=$TEMENOS_HOME/
echo $BRP_HOME

#ORACLE_HOME
export ORACLE_HOME= /srv/Temenos/3rdParty/AS/Oracle/Middleware/Oracle_Home

4. Execute .bash_profile to export the variables.

4 .5 Checking the JDK

You must ensure that JDK 8 is installed. TAFJ R20 runs only on JDK version 1.8 or higher.

Procedure

1. In the Linux shell, verify that JDK 1.8 is installed to the Temenos/3rdParty/Java directory.

java -version

2. Add the JAVA_HOME environment variable and $JAVA_HOME/bin to the $PATH variable.

4 .6 Checking the database connection

Check that you can connect to your database, using a tool such as the Oracle SQL Developer.

16
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4 .7 Checking the WebLogic installation

Check that WebLogic is installed and WEBLOGIC_HOME has been set as an environment variable. You
should see the following folders in $WEBLOGIC_HOME.

17
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5 Installing Transact and TAFJ

The following sections describe how to install Temenos Transact and TAFJ.

5 .1 Installing Transact
Procedure

1. Copy the Transact artefacts ([Link]) from Distribution to the

$TEMENOS_HOME/install folder.

2. In the Linux shell, extract Transact.

a. Navigate to $TEMENOS_HOME/install and extract the

[Link] file.

tar –xvf [Link] -C /srv/Temenos/T24

b. The file is extracted as a bnk folder (BNK_HOME) under T24. List the bnk directory
contents.

ls -ltr $BNK_HOME

18
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5 .2 Installing TAFJ
Procedure

1. Copy the TAFJ artefacts ([Link]) from Distribution to the $TEMENOS_

HOME/install folder.

2. In the Linux shell, install TAFJ.

Note: The only prerequisite for TAFJ installation is to have JAVA_HOME set to the correct
path.

a. Navigate to $TEMENOS_HOME/install and extract the [Link]

file.

tar –xvf [Link]

b. Change the permissions on Setup_TAFJ.[Link] and

[Link] to execute.

chmod 755 Setup_TAFJ.[Link] [Link]

c. Execute Setup_TAFJ.[Link]. When prompted to enter the installation

directory, specify the path of $TAFJ_HOME and then press Enter.

19
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

a. Enter the TAFJ_HOME directory then press Enter.

b. Press Enter to accept the default conf directory under the TAFJ_HOME directory.

c. Enter y to create the conf directory under TAFJ_HOME.

d. Press Enter to terminate. This completes the TAFJ runtime installation.

20
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

You should see the following folders in $TAFJ_HOME.

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

chmod 755 $TAFJ_HOME/bin/*

f. Open .bash_profile and add $TAFJ_HOME/bin to PATH as shown below.

PATH=$PATH:/etc/alternatives/jre_1.8.0_openjdk/bin:$TAFJ_HOME/bin:$PATH

g. Start a new shell and execute tVersion to verify the TAFJ version.

21
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5 .3 Deploying the Oracle 19c database driver

TAFJ uses JDBC drivers to establish a connection with the database. Database drivers are available in
the $TAFJ_HOME/dbdrivers folder. Use the latest version of the respective database driver,
downloaded from the vendor’s portal, for your deployment.

Procedure

1. Create a folder oracle-19c under $TAFJ_HOME/dbdrivers. This folder is required for the
later part of the setup while running the T24Setup script.

2. Download the Oracle 19c drivers from the Oracle website or copy them from the database
installation path. The required drivers are:

l ojdbc8

l oraclepki

l orai18n

l orai18n-collation

l orai18n-mapping

l ucp

22
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

l xdb

l xmlparserv2_sans_jaxp_services

[Link], [Link] and xmlparserv2_sans_

jaxp_services.jar files are not available in the Oracle Database 19c (19.3) JDBC Driver &
UCP Downloads. If you need one of these jar files, you will need to install the Oracle Database
client, the Administrator package client installation.

In the environment used to create this runbook, the jars were located as follows:

l $ORABASE/dbhome_1/dmu/jlib/[Link]

l $ORABASE/dbhome_1/lib/xmlparserv2_sans_jaxp_services.jar

l $ORABASE/dbhome_1/jlib/[Link]

3. Copy the oracle-19c folder to $TAFJ_HOME/ext directory.

cp –r $TAFJ_HOME/dbdrivers/oracle-19c $TAFJ_HOME/ext/

23
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6 Configuring TAFJ
The following sections tell you how to configure TAFJ runtime to setup Transact in standalone mode
(that is, outside an application server).

Instead of using environment variables for its internal configuration, TAFJ uses a properties file
(*.properties). The properties files are stored in the TAFJ_HOME/conf directory. The default file is
[Link].

6 .1 Configuring the properties file

Procedure

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

2. Open [Link].

3. Ensure that [Link] points to the correct location.

4. Set [Link] to the path to the Transact libraries.

5. In the Database header section, set the database connection parameters.

a. Set [Link] to the connection URL.

b. Set [Link] to the name of the driver.

c. Set the database username and password.

24
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

d. Set the UD directory path.

e. Set the value of [Link] and

[Link] to false to improve database
performance.

f. Set the value of [Link] to DATABASE.

In this runbook the DATABASE locking mode is used. This is recommended for releases 201809
onwards. TAFJ locks records using the native database locks when this locking mode is used.

Note: To find out more about creating and populating the TAFJ_HASHLOCKS table, which is required for
DATABASE locking mode, in $TAFJ_HOME/doc see TAFJ-Lock [Link].

25
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6 .2 Verifying the TAFJ installation

Procedure

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

2. To check that the TAFJ installation was successful and that the properties file has been correctly
set, execute tDiag. This command displays:

l The $TAFJ_HOME value.

l The JDK version.

l The TAFJ version.

l The default project.

l The details of all projects set in $TAFJ_HOME/conf.

26
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

TAFJ runtime configuration is now complete.

27
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7 Sanity checks
Before proceeding to application server deployment, you need to confirm that Transact installation was
successful by performing two sanity checks.

7 .1 Accessing Temenos Classic

Transact Classic is one of the user interfaces used to access Transact.

Procedure

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

2. Execute tRun EX.

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

28
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Launch any application (for example SPF).

7 .2 Running DBTools
DBTools is a TAFJ tool that provides a console to execute database commands. The console can only
be accessed by authenticated users. Create a TAFJ user using the [Link] utility.

Procedure

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

2. Create a user by passing username and password parameters to the [Link] utility.

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

3. Launch DBTools, passing the TAFJ user credentials as parameters.

./DBTools -u tafjuser -p Temenos@123

29
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. The DBTools console is launched. View the database name, database username and IP address
in the bottom left of the screen.

30
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8 Configuring TAFJ and Transact in

WebLogic
This section tells you how to automate the configuration of Transact and TAFJ on the WebLogic server.

The configuration of WebLogic application server for TAFJ-Transact deployment is automated using the
WLST scripting tool in WebLogic. You need to manually update two TAFJ files ([Link] and
the [Link] script) to automate the configuration.

8 .1 Starting WebLogic Server

Procedure

1. In the Linux shell, navigate to $WEBLOGIC_HOME/bin and execute [Link].

nohup ./[Link]. &

2. Open the WebLogic admin console with the following url

[Link]

3. Login to the console with the credentials you defined when installing WebLogic.

The main page of the console is displayed.

31
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. In the console, select Domain Structure > Environment > Servers.

On the configuration page, you can see AdminServer (admin).

32
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5. Click New to create a new server.

6. Enter the Server Name and Server Listen Port. For Should this server belong to a
cluster? select No, this is a stand-alone server.

33
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7. Click Finish.

8. In the console, select Domain Structure > Environment > Machines.

9. Click New. Enter the machine name and select Unix as the Machine OS.

10. Click Next.

34
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

11. Under Configuration click the Node Manager sub-menu. Change Type to Plain if it is SSL and
click Save. Plain means that the communication with this Java-based node manager is not
encrypted.

12. In the console, select Domain Structure > Environment > Servers then click Server-1.

13. Select Machine-1, which you created in a previous step, and click Save.

14. Log out of the console.

35
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

15. Restart the server for the new changes to take effect. Go to $WEBLOGIC_HOME/bin and stop
the WebLogic server by executing [Link]. Start it again by executing
[Link].

./[Link]
nohup ./[Link]

16. Go to $WEBLOGIC_HOME/nodemanager.

17. Open the [Link] file.

18. Change AuthenticationEnabled and SecureListener to false (since we are using a

node manager of type plain).

19. Go to $WEBLOGIC_HOME/bin and execute [Link].

nohup ./[Link] &

20. Login to the WebLogic admin console. To start the server in the console, select Domain
Structure > Environment > Servers section and click the Control tab.

36
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

21. Select the managed server and click Start.

22. The server takes a few minutes to start. You should see the server state displayed as
STARTING. When the server state becomes RUNNING, the WebLogic managed server has
successfully started.

37
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8 .2 Configuring WebLogic class paths

Procedure

1. In the console, select Domain Structure > Environment > Servers.

2. Ensure that the server is up and running.

3. Select Server-1 and, under Configuration, click Server Start.

4. Add TAFJ/lib, TAFJ/ext, dbdrivers for the database and the Transact-precomplied jar files path
to Class Path area.

5. In the Arguments section set the JVM parameter [Link] to $TAFJ_HOME, the hostname
to the name of your managed server and [Link] to utf8 (TAFJ requires utf8

38
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

encoding).

8 .3 Configuring the [Link] file

Procedure

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

2. Open [Link].

3. Enter the WebLogic username and password (these are used to access the WebLogic admin
console).

4. Enter the host name and port where WebLogic is installed.

5. Enter the name of the Admin server, the managed server and the OS of the system.

39
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6. Create a temporary folder (for example, tmp) for the persistence store file and enter the path to
this folder for weblo_store_path.

7. Set tafjHome and t24Home to the values for $TAFJ_HOME and $T24_HOME respectively.

8. In the database details section, enter the database details.

40
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9. Specify the path to [Link] in browserWebHome. Alternatively, BrowserWeb can be

installed from the WebLogic console.

8 .4 Running the T24Setup script

[Link] script file contains WLST commands to automate WebLogic server configuration and
deployment of the following:

l Environment variables and shared libraries (TAFJ and Transact libraries).

l JMS resources (communication channels between applications).

l JDBC data sources (database connectivity).

l Applications deployment (TAFJ ear file and BrowserWeb).

Procedure

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

2. Open [Link]

3. In the TAFJ JDBC drivers section change oracle-12c to oracle-19c (because we are
configuring WebLogic with Oracle 19c).

4. Click Save.

5. Give execute permissions to *.sh and *.py scripts.

41
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

chmod 777 *.sh

chmod 777 *.py

6. Execute the following command to invoke WLST and execute the specified [Link]
loading properties from [Link].

$ORACLE_HOME/wlserver/common/bin/[Link] -loadProperties [Link] [Link]

The output from WLST is shown below.

[jumpstart@R20-Stack-1-scratch-39 weblogic]$ echo $ORACLE_HOME

/srv/Temenos/3rdParty/AS/ Oracle/Middleware/Middleware/Oracle_Home
[jumpstat@R20-Stack3 weblogic]$ $ORACLE_HOME/wlserver/common/bin/[Link] -
loadProperties [Link] [Link]
WARNING: This is a deprecated script. Please invoke the [Link] script under oracle_
common/common/bin.

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

---------------------------------------------------------------------
Start T24/TAFJ configuration in Weblogic
---------------------------------------------------------------------
Server Environment
Connecting to t3://[Link] with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "base_
domain".

Starting an edit session ...

Started edit session, be sure to save and activate your changes once you are done.
---------------------------------------------------------------------
Deploy BrowserWeb for Server-1
---------------------------------------------------------------------
Deploying application from /srv/Temenos/install/ BrowserWeb-R20.00/[Link] to
targets Server-1 (upload=false) ...
<Jul 19, 2020 6:32:35 AM UTC> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating
deploy operation for application, BrowserWeb [archive:
/srv/Temenos/install/BrowserWeb-R20.00/[Link]], to Server-1 .>

42
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

You have an edit session in progress, hence WLST will not block for your deployment
to complete.
Started the Deployment of Application. Please refer to the returned WLSTProgress
object or variable LAST to track the status.
Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is
completed.
Activation completed
Disconnected from weblogic server: AdminServer
---------------------------------------------------------------------
T24/TAFJ configuration in Weblogic is done !
---------------------------------------------------------------------

7. After the script has run succesfully, login to the WebLogic Console.

8. You must now verify that TAFJJEE_EAR.ear and [Link] have been deployed. Go
to Domain Structure > Environment > Servers.

9. Select Server-1 and, under Configuration, click the Server start tab.

10. Under Class Path you may see the TAFJ path being repeated at the beginning.

11. Delete the repeated path and click Save.

43
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8.4.1 Testing the database connection

Procedure

1. In the console, select Domain Structure > Environment > Services > Data Sources >
Monitoring.

2. Select T24 and click Testing.

3. Select Server-1 and click Test Data Source.

44
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Repeat steps 2 and 3 for the remaining data sources.

8 .5 Accessing the TAFJEE servlet

The TAFJJEE_EAR.ear file contains a war file, which is a helper servlet for configuration, diagnostic,
execution and troubleshooting related TAFJ functions on the application server. TAFJEE has protected
access and is subject to BASIC authentication.

You need to create a user to login to the TAFJEE servlet.

Procedure

1. In the WebLogic console, select Domain Structure > Security Realms.

2. In Realms select myrealm.

3. In Settings for myrealm, select the Users and Groups and Users tabs.

45
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Click New to create a new user.

5. In Name, enter TAFJAdmin. Then enter a Description and a Password.

6. Access the TAFJEE servlet using the URL [Link]

(or)ipaddress:7003/TAFJEE.

46
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7. Enter the application user credentials.

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

47
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8 .6 Accessing BrowserWeb
Procedure

1. Access BrowserWeb using the URL [Link]

(or)ipaddress:7003/BrowserWeb.

2. Log into BrowserWeb by using a valid Transact Username and Password. The landing page is
displayed.

48
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

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

49
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 Configuring UXPBrowser in Generate

on Demand (GOD) mode
The final part of the setup is to deploy the Transact Product UI components, UXP Browser (UXPB).
UXPB is our latest user interface for Transact.

Note: This runbook does not cover deployment of our other product user interfaces such as Temenos
Connect Internet Banking (TCIB) and Mobile Banking (TCMB). The following sections are only required if
you are deploying UXP Browser.

9 .1 Extracting the UXPBrowser artefacts

Procedure

1. In the Unix shell, copy the [Link] file from Distribution to the $TEMENOS_
HOME/UXPBrowser folder.

2. Unzip [Link] in the $TEMENOS_HOME/UXPBrowser folder.

unzip [Link]

50
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

The zip file contains the following files.

l [Link]

l [Link]

l [Link]

l [Link]

l [Link]

l [Link]

l [Link]

l [Link]

l [Link]

l [Link]

51
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3. Rename the [Link], [Link], irf-rp-

[Link] and [Link] to
[Link], Browser. war, [Link] and
[Link].

mv [Link] [Link]
mv [Link] [Link]
mv [Link] [Link]
mv [Link] [Link]

4. Unzip IRISR18_CatalogServices_TAFJ_20.[Link].

unzip IRISR18_CatalogServices_TAFJ_20.[Link]

5. Rename [Link].

mv [Link] $UXPBROWSER/[Link]

52
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6. Move [Link] to $UXPBROWSER.

mv [Link] $UXPBROWSER

7. Unzip [Link].

unzip [Link]

The following properties files are now output.

l [Link]
l [Link]

8. In $TEMENOS_HOME create a properties directory.

mkdir $TEMENOS_HOME/properties

9. Copy [Link] and

[Link] to the $TEMENOS_HOME/properties directory.

cp [Link] $TEMENOS_HOME/properties
cp [Link] $TEMENOS_HOME/properties

53
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .2 Generating the keystore files

JWT token-based authentication is used with UXPB. When a request comes from UXPB, the request
will first be authenticated. User credential is sent to the authentication service first (that is,
[Link]) to verify the credentials. The authentication service on successful
authentication generates and sends back a signed JWT token that contains the user information.

To do this, we need a pair of keys (either RSA private keys or RSA public keys). Follow the steps below
to generate a keystore file and then export the public key into a certificate file.

Procedure

1. In the Unix shell, navigate to the $WAS_HOME/java/8.0/bin directory.

2. Create a .jks keystore file by running the following command.

./keytool -genkey -alias temenos_uxpb -keyalg RSA -keystore [Link] -keysize 2048

The command creates a keystore file called [Link] with one RSA key in it. The alias of the
key is called temenos_uxpb. The algorithm that is used to create the key is RSA. The size of the
key is 2048 bits and the default format of the keystore is JKS.

3. Enter the following information when prompted.

a. The password for the keystore. You can find the password value of the keystore in
[Link]/WEB-INF/classes/[Link] .

54
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

b. The password again.

c. First name and last name.

d. The name of the organisation.

e. The name of the organization again.

f. The name of the city.

g. The name of the state or province.

h. The two character country code for the country.

i. In the last field, enter yes.

j. When you see the prompt Enter key password for <temenos_uxpb>, just press
Enter.

./keytool -genkey -alias temenos_uxpb -keyalg RSA -keystore [Link] -keysize

2048
Enter keystore password:
Re-enter new password:
What is your first and last name?
[Unknown]: temenos_uxpb
What is the name of your organizational unit?
[Unknown]: temenos
What is the name of your organization?
[Unknown]: temenos
What is the name of your City or Locality?
[Unknown]: hemel
What is the name of your State or Province?
[Unknown]: herts

55
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

What is the two-letter country code for this unit?

[Unknown]: gb
Is CN=temenos_uxpb, OU=temenos, O=temenos, L=hemel, ST=herts, C=gb correct?
(type "yes" or "no")
[no]: yes

Enter key password for <temenos_uxpb>:

(RETURN if same as keystore password):

4. Now that you have a keystore file, the next step is to export the public key as a separate entity.
Create a .cer keystore file using the following command.

./keytool -export -keystore [Link] -alias temenos_uxpb -file temenos_uxpb.cer

The command specifies the jks file, the alias of the key, and the output file temenos_uxpb.cer.
Enter the password (from [Link], that is, Temen0s). The .cer file will
be created successfully.

You should see .jks and .cer files generated in $WAS_HOME/java/8.0/bin directory.

5. Create a directory to store the keystore and certificate. You can create the directory anywhere you
want to and give it any name you choose. In this example, we created a uxpb_weblogic_keys
directory under TEMENOS_HOME. Move or copy the created .jks and .cer files to this directory.

mkdir $TEMENOS_HOME/uxpb_weblogic_keys
mv $JAVA_HOME//bin/temenos_uxpb.cer $TEMENOS_HOME/ uxpb_weblogic_keys/
mv $WAS_HOME /bin/[Link] $TEMENOS_HOME/ uxpb_weblogic_keys/

6. Move to $TEMENOS_HOME/uxpb_weblogic_keys and give execute permissions to the

certificate and keystore files.

cd $TEMENOS_HOME/ux uxpb_weblogic_keys
chmod 755 *

56
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .3 Adding JVM arguments for UXP Browser

Procedure

1. In the WebLogic console, select Domain Structure > Environment > Servers.

2. Select Server-1 and click the Server Start tab.

3. In the Arguments section add the following arguments.

-DBRP_HOME=/srv/Temenos -DedgeSystemPropertyFolder=/srv/Temenos/properties
-DedgeSystemPropertyUpdaters=[Link]
-DedgeSystemDebug=Y
-[Link]=jms/ConnectionFactory

9 .4 Configuring [Link]
Procedure

1. In the Unix shell, move to the $TEMENOS_HOME/properties directory.

2. Edit [Link] as shown below.

57
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

Note that the [Link] value is the encrypted output of

the Transact AUTHOR user password. For example, if the password is 123456, you use
[Link] to encrypt the password.

#java -jar [Link] 123456

vSd3/5UdSJc=

3. Save and exit.

9 .5 Configuring [Link]
Procedure

1. In the Linux shell, move to the $TEMENOS_HOME/properties directory.

2. Edit [Link] as shown below.

Note that the [Link].1 value is the

encrypted output of the Transact database password. For example, if the password is t24, you
use the [Link] to encrypt the password.

58
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

#java -jar [Link] t24

g7nVhB+BoUY=

3. Save and exit.

9 .6 Installing [Link]
Procedure

1. Enable the below highlighted TAFJ resource references in [Link]\WEB-

INF\[Link].

2. Specify the file path of the keystore and certificate files, and the keystore password and alias
details in [Link]\WEB-INF\classes\[Link].

3. Delete the default Temenos-supplied [Link] and temenos_uxpb.cer files from

[Link]\WEB-INF\classes\.

59
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Create or replace the [Link]\WEB-INF\[Link] as follows.

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

<weblogic-web-app xmlns="[Link]
<context-root>Authenticator</context-root>
<!-- TAFJ Resource Settings -->
<resource-description>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<jndi-name>jdbc/t24DS</jndi-name>
</resource-description>
<resource-description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<jndi-name>jdbc/t24LockingDS</jndi-name>
</resource-description>
<container-descriptor>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
<prefer-application-packages>
<package-name>[Link].*</package-name>
</prefer-application-packages>
</container-descriptor>
</weblogic-web-app>

5. Install the [Link].

60
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6. Select Install this deployment as an application and click Next.

7. Select Server-1 and then click Next.

61
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8. Click Next, Finish and then Save.

9. Click Domain Structure > Deployment in the left menu to view the deployments summary.

62
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .7 Installing [Link]
Procedure

1. In [Link]\WEB-INF\[Link] change the Authenticator remote URL.

Use the actual host IP address and the WebLogic http port.

2. Specify the file path of keystore and certificate files, keystore password and Alias details in
[Link]\WEB-INF\lib\ Authenticator-
[Link]\[Link].

3. Create or replace [Link]\WEB-INF\[Link] as follows.

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

<weblogic-web-app xmlns="[Link]
<context-root>Browser</context-root>
<container-descriptor>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
<prefer-application-packages>
<package-name>[Link].*</package-name>
<package-name>[Link].*</package-name>
</prefer-application-packages>
</container-descriptor>
</weblogic-web-app>

63
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Delete the default Temenos supplied [Link] and temenos_uxpb.cer files from
[Link]\WEB-INF\lib\[Link]\.

5. Install [Link]. Browse to $UXPBROWSER and click Next.

6. Select Install this deployment as an application and click Next.

64
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7. Select Server-1 and click Next.

8. Click Next, Finish and then Save.

65
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9. Click .

10. Click Domain Structure > Deployment in the left menu to view the deployments summary.

66
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .8 Installing [Link]
Procedure

1. Edit the [Link]/WEB-INF/classes/[Link].

a. Set RemoteConnectionHosts to the host machine IP address and

RemoteConnectionPort to the Server-1 port.

b. Enter the user and password details you created in myrealms earlier for the
transportLayerUser and transportLayerCredential.

c. Set [Link] to ResourceProviderServiceBeanRemote

and [Link] to
AuthenticationServiceBeanRemote.

2. Specify the certificate file path in [Link]\WEB-INF\classes\META-

INF\[Link] and remove the pkCertEncoded value.

67
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3. Edit [Link]/WEB-INF/[Link]. Add the <url-pattern> tag into all

<filter-mapping> tags as shown below.

Old entries

<filter-mapping>
<filter-name>request-context</filter-name>
<servlet-name>CamelServlet</servlet-name>
</filter-mapping>

Updated entries

<filter-mapping>
<filter-name>request-context</filter-name>
<servlet-name>CamelServlet</servlet-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

4. Install [Link].

5. Browse to $UXPBROWSER, select [Link], and click Next.

68
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6. Select Install this deployment as an application and click Next.

7. Select Server-1 and then click Next.

8. Click Next, Finish and then Save.

69
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9. Click Domain Structure > Deployment in the left menu to view the deployments summary.

9 .9 Installing [Link]
Procedure

1. Edit [Link] /WEB-

INF/classes/[Link].

70
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

a. Set RemoteConnectionHosts to the host machine IP address and

RemoteConnectionPort to the Server-1 port.

b. Enter the user and password details you created in myrealms earlier for the
transportLayerUser and transportLayerCredential.

c. Set [Link] to ResourceProviderServiceBeanRemote

and [Link] to
AuthenticationServiceBeanRemote.

2. Specify the certificate file path in [Link]\WEB-

INF\classes\META-INF\[Link] and remove the
pkCertEncoded value.

3. Edit [Link]/WEB-INF/[Link]. Add the <url-pattern> tag into all

<filter-mapping> tags as shown below.

Old entries

<filter-mapping>
<filter-name>request-context</filter-name>

71
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

<servlet-name>CamelServlet</servlet-name>
</filter-mapping>

Updated entries

<filter-mapping>
<filter-name>request-context</filter-name>
<servlet-name>CamelServlet</servlet-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

4. Install [Link].

5. Browse to $UXPBROWSER, select [Link] and click Next.

6. Select Install this deployment as an application and click Next.

72
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7. Select Server-1 and then click Next.

8. Click Next, Finish and then Save.

9. Click Domain Structure > Deployment in the left menu to view the deployments summary.

73
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .1 0 Installing [Link]
Procedure

1. Copy the [Link] from $TEMENOS_HOME/dbdrivers/oracle-19c to

[Link]/WEB-INF/lib.

2. Create or replace [Link]\WEB-INF\[Link] as follows.

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

<weblogic-web-app xmlns="[Link]

74
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

<context-root>ResourceServer</context-root>
<container-descriptor>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
<prefer-application-packages>
<package-name>[Link].*</package-name>
</prefer-application-packages>
</container-descriptor>
</weblogic-web-app>

3. Install [Link].

4. Browse to $UXPBROWSER, select [Link] and then Next.

5. Select Install this deployment as an application and click Next.

6. Select Server-1 and then click Next.

75
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7. Click Next, Finish and then Save.

8. Click Domain Structure > Deployment in the left menu to view the deployments summary.

76
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .1 1 Installing t24-EB_CatalogService-[Link]
The t24-EB_CatalogService-[Link] is located in $BNK_HOME/T24/bnk/Extensions/
EB_CatalogService /t24ejb.

Procedure

1. Edit t24-EB_CatalogService-[Link] \META-INF\[Link]. Under session_

typeStateless/session-type entry, change the transaction-type value from
Container to Bean as illustrated below.

2. Change OFS_SOURCE from GCS to IRISPA.

77
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3. Edit t24-EB_CatalogService-[Link]\META-INF\[Link]. Under

the </wls:weblogic-enterprise-bean> tag, paste the following entries.

<security-role-assignment>
<role-name>t24user</role-name>
<principal-name>SSOUSER1</principal-name>
<principal-name>SSOUSER2</principal-name>
</security-role-assignment>

4. Install t24-EB_CatalogService-[Link].

78
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5. Select Install this deployment as an application and click Next.

6. Select Server-1 and then click Next.

7. Click Next, Finish and then Save.

79
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8. Click Domain Structure > Deployment in the left menu to view the deployments summary.

9 .1 2 Installing t24-EB_ResourceProviderService-[Link]
t24-EB_ResourceProviderService-[Link] is located in $BNK_
HOME/T24/bnk/Extensions/EB_ResourceProviderService/t24ejb.

Procedure

1. Edit t24-EB_ResourceProviderService-[Link]\META-INF\[Link]. Under session_

typeStateless/session_type entry, change the <transaction-type> value from
Container to Bean as illustrated below.

80
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

2. Change OFS_SOURCE from GCS to IRISPA.

3. Insert a new line after the </session> tag.

81
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Install t24-EB_ResourceProviderService-[Link].

5. Select Install this deployment as an application and click Next.

6. Select Server-1 and then click Next.

82
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

7. Click Next, Finish and then Save.

8. Click Domain Structure > Deployment in the left menu to view the deployments summary.

83
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

9 .1 3 Installing t24-EB_AuthenticationService-[Link]
The t24-EB_AuthenticationService-[Link] is located in $BNK_
HOME/T24/bnk/Extensions/ EB_AuthenticationService/t24ejb.

Procedure

1. Edit t24-EB_AuthenticationService-[Link]\META-INF\[Link]. Under

<session_type>Stateless/session-type entry, change the <transaction-type>
value from Container to Bean as illustrated below.

2. Change OFS_SOURCE from GCS to IRISPA.

84
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3. Install t24-EB_AuthenticationService-[Link].

4. Select Install this deployment as an application and click Next.

85
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5. Select Server-1 and then click Next.

6. Click Next, Finish and then Save.

7. Click Domain Structure > Deployment in the left menu to view the deployments summary.

86
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8. Restart the application server.

cd $WEBLOGIC_HOME/bin
./[Link]
./ [Link]

87
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

nohup ./[Link] &

nohup ./[Link] &

9 .1 4 Configuring [Link] for UXP Browser

Procedure

1. Extract the [Link] to $TEMENOS_HOME.

unzip [Link] -d $TEMENOS_HOME

This will output the [Link] folder, HelpText, and other xml files.

2. In the Weblogic console, in the Arguments section, set the JVM parameter -
[Link]=/srv/Temenos/[Link]/HelpText.

88
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

-[Link]=/srv/Temenos/[Link]/HelpText

3. Restart the application server.

9 .1 5 Accessing the UXP Browser

Procedure

1. Use URL [Link] to access the UXP

Browser.

2. Log in using a valid User ID and Password.

The landing page is now displayed.

89
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3. Launch any Transact application (for example SPF).

90
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

10 Configuring and deploying Axis2

The Transact component service APIs comprise Axis2 archives (t24-ComponentService-
[Link]) in the extensions folder of the Transact distribution pack. You deploy these archives into
the Apache Axis2 web archive file.

Note: The release version of Apache Axis2 used here is 1.6.2.

1 0 .1 Configuring the Axis2 war

Procedure

1. Download [Link] from the Apache website and extract the zip file.

2. In the Unix shell, navigate to any directory and create a new temporary folder (for example, tmp in
$TEMENOS_HOME/install).

3. Copy [Link] to the $TEMENOS_HOME/install/tmp folder.

4. In the tmp3 folder, unpack [Link] and navigate to WEB-INF/lib

cd $TEMENOS_HOME/install/tmp
jar -xf [Link]
cd $TEMENOS_HOME/install/tmp /WEB-INF/lib

5. Add the following dependency JARs to the lib folder.

l [Link]

l [Link]

6. Copy the component service archives from $BNK_HOME/bnk/Extensions into the/WEB-

INF/services directory of [Link].

7. Open /WEB-INF/services/[Link] and add the names of the component service

archives that you added to the services directory.

91
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

t24-EB_CatalogService-[Link]
t24-IF_IntegrationLandscapeService-[Link]
t24-DS_DesignStudioInstallerService-[Link]
t24-EB_OFSConnectorService-[Link]
t24-EB_ResourceProviderService-[Link]
t24-IF_IntegrationFlowService-[Link]
t24-IF_IntegrationFrameworkService-[Link]
t24-IF_InflowService-[Link]
[Link]

8. Open /WEB-INF/[Link] and configure database connectivity by adding the data source.

<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>[Link]</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24LockingDataSource">
<description>Used to get connections from T24 jdbc pool
</description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>[Link]</res-type>
<res-auth>Container</res-auth>
</resource-ref>

9. Navigate to WEB-INF/conf and delete [Link]. This removes the local [Link],
causing WebLogic to use its own [Link].

92
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

rm –rf [Link]

10. Repack [Link] and place it in the UXPBrowser directory.

cd $TEMENOS_HOME/install/tmp
rm –rf [Link]
jar cf [Link] *
cp [Link] $TEMENOS_HOME/install

1 0 .2 Installing [Link]
Procedure

1. In the WebLogic console, select Domain Structure > Deployments.

2. In the Deployments summary, click Install.

3. Select [Link] and click Next.

4. Select Install this deployment as an application and click Next.

93
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

5. Select Server-1 and then click Next.

6. In Install Application Assistant, click Next.

7. In Additional Configuration select the following option and click Finish.

94
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

8. Click Save.

9. Restart the application server.

cd $WEBLOGIC_HOME/bin
./[Link]
./ [Link]

95
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

nohup ./[Link] &

nohup ./[Link] &

1 0 .3 Accessing the Axis2 servlet

Procedure

1. Access Axis2 servlet using URL [Link]

2. Select Validate. The display will indicate whether the web services are working properly.

96
 S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

3. Select Services. This will list out the services deployed in Axis2.

1 0 .4 Integrated testing of axis2 and Transact

Procedure

1. In the axis2 servlet, go to services and click any service to get the wsdl. For example, the wsdl
here is for IntegrationFlowService.

97
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

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

Enter the Project Name and the Initial WSDL, for example:

Project
axis_test
Name
Initial [Link]
WSDL address:9080/axis2/services/IntegrationFlowServiceWS?wsdl

3. Create a new read flow request by expanding the readFlow menu.

98
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

4. Double-click Request1.

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

<int:flowName> and delete the ? place holders for the other parameters.

Note: The flowName value can be any of the flows you see in
[Link].

99
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

6. Click the green play button to execute.

100
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

101
S ta c k 3 R e d H a t - W e b L o g i c R u n b o o k 2 .1

The SOAP response in the right pane indicates that IntegrationFlowService of Axis2 can
communicate with Transact.

You have now completed your deployment of Transact on TAFJ on WebLogic with an Oracle 19c
database. You can now carry out business operations in Transact using BrowserWeb and
UXPBrowser.

102