Stack 6 for JBoss – Windows

Customer Runbook 2.0, September 2020

All post R20 AMR releases up to and including R21 AMR
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

Contents
1 About this Runbook 4
1.1 Stacks table 4
1.1.1 Scope 4
1.2 Audience 4
1.3 Skills and knowledge 4
1.4 Other stack runbooks 5
1.5 Legal 5
1.6 History 6
2 Introduction 7
2.1 Environment 7
2.2 UXP Browser Generate On Demand (GOD) mode 8
2.3 Components deployed in the GOD mode of UXP Browser 8
3 Prerequisites 10
3.1 Software prerequisites 10
3.1.1 Third-party software 10
3.1.2 Temenos artefacts 10
4 Before you start 12
4.1 Completing preinstallation tasks 12
4.2 Checking the operating system 12
4.3 Checking the disk space 13
4.4 Creating the directory structure 14
4.5 Configuring the environment variables 14
4.6 Verifying the system for third-party software 15
5 Installing TAFJ runtime 17
5.1 Extracting Transact 17
5.2 Installing TAFJ 17
5.3 Deploying the database driver 20
6 Configuring TAFJ 22
6.1 Configuring [Link] 22
6.2 Verifying the TAFJ installation 24
7 Sanity check 26
7.1 Accessing Transact Classic 26
7.2 Accessing DBTools 27
8 Configuring JBoss EAP 7.3 29
8.1 Configuration prerequisites 29

2
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

8.2 Configuring memory settings 29

8.3 Configuring JBoss modules 30
8.3.1 Deploying the MS SQL Server database driver module 30
8.3.2 Configuring the TAFJ module 31
8.3.3 Configuring the Transact module 32
8.3.4 Generating the Transact 33
9 Configuring a standalone profile on the application server 35
10 Extracting UXP Browser artefacts 38
11 Configuring and deploying Transact and TAFJ artefacts 39
11.1 Deploying TAFJJEE_EAR.ear and TAFJ Spooler plugins 39
11.2 Deploying BrowserWeb 39
11.3 Modifying [Link] 40
11.4 Modifying [Link] 40
11.5 Modifying [Link] 41
11.6 Embedding the database driver in [Link] 41
11.7 Modifying the required EJB JAR files 42
11.8 Configuring the SSOUSER1 user in JBoss 45
11.9 Configuring UXP Browser in the Generate On Demand (GOD) mode 47
11.10 Deploying UXP Browser artefacts in JBoss 49
11.11 Deploying the EJB JAR files in JBoss 49
12 Deploying Transact component services 51
12.1 Step 1: Packaging Axis2 archives 51
12.2 Step 2: Deploying Axis2 53
13 Sanity check - post deployment 55
13.1 Starting the application server 55
13.1.1 Mandatory command arguments 55
13.2 Accessing the TAFJEE servlet 56
13.3 Accessing BrowserWeb 58
13.4 Accessing UXP Browser 60
13.5 Using the Axis2 servlet 62
13.5.1 Accessing the Axis2 servlet 62
13.5.2 Testing Axis2 and Transact 64

3
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1 About this Runbook

The Stack 6 for JBoss - Windows Runbook shows how to configure TAFJ-Transact on JBoss EAP 7.3 with SQL
Server 2019 database. It also shows you how to deploy BrowserWeb and UXP Browser and access Transact using
these browsers. This runbook is relevant to all post R20 AMR releases up to and including R21 AMR.

Note:
This runbook doesn't 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.1.1 Scope

This runbook covers:

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

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

1 .3 Skills and knowledge

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

l Transact
l TAFJ

4
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

l JBoss
l MS SQL Server

1 .4 Other stack runbooks

To access all our stack runbooks, visit either the Temenos Customer Portal or the Temenos Partner Portal.

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.

5
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1 .6 History

Version Date Description Author

1.0 September 2020 Initial release of this runbook. Dominik Wietrzak

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

6
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

2 Introduction
This runbook helps you to set up the development or test environment for Transact and TAFJ on the Windows
operating system. It shows you how to install and configure TAFJ, Transact and JBoss and how to access Transact
through both BrowserWeb and UXP Browser. In this exercise, a two-tier architecture has been created which
consists of an application server and a database server.

2 .1 Environment
The application tier contains JBoss EAP (version 7.3) application server with TAFJ and Transact. The database tier
contains the MS SQL Server 2019 database that stores Transact data. For better understanding, the architecture is
given below.

7
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

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

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

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

2 .3 Components deployed in the GOD mode of UXP Browser

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

Authenticator ([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.).

Interaction Framework Resource Provider service ([Link])

This service processes requests and responses through the Resource Provider (RP) component apart from

8
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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 service ([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.

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)

9
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

3 Prerequisites

3 .1 Software prerequisites
You must first obtain all the required artefacts from your account manager. Before you start installing and configuring
the stack, you must install all third-party software.

3.1.1 Third-party software

Software Version

Windows server 2019

JDK 1.8

JBoss 7.3

Microsoft SQL server 2019

SQL Server Management Studio 2019

Axis2 1.6.2

3.1.2 Temenos artefacts

Artefacts Files Description

Database backup MB.202008.MSSQL_2014.WIN.TAFJ202008.30- Contains the database.

[Link]

Transact [Link] Contains the bnk

directory that holds the
Transact libraries.

TAFJ [Link] Contains the TAFJ

runtime JAR file, TAFJ
patch script and TAFJ
setup script.

10
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

Artefacts Files Description

Transact Browser [Link] Old browser

components.

UXP Browser [Link] New browser

components.
The following required files are embedded in the package:

l [Link]
l [Link]
l [Link]
l [Link]
l [Link]
l [Link]

Interaction [Link] Catalog services

Framework WAR file
Catalog services

Additional EJB t24-EB_AuthenticationService-[Link] EJB JAR files required

JAR files for deploying UXP
t24-EB_CatalogService-[Link] Browser in the Generate
On Demand (GOD)
t24-EB_ResourceProviderService-[Link] mode

These files are available in the subfolders under

T24\bnk\Extensions.

Temenos [Link] The utility for encrypting

Encryption Utility passwords. It is required
for configuring UXP in
GOD mode.

11
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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 Completing preinstallation tasks

Procedure

1. Load Transact data into the MS SQL Server from the .bak file.
2. Load TAFJ-related stored procedures and Java functions into the database. For more information, see the
database-specific installation document that is stored in %TAFJ_HOME%\doc.
3. Install the required third-party software such as JDK and JBoss. For more information about the installation
paths, see "Creating the directory structure" on page 14.
4. Prepare all Temenos artefacts in the chosen temporary directory on your machine.
5. If you are going to use a non-standard port on the application server, ensure that you open it in the Windows
firewall.

4 .2 Checking the operating system

Procedure

1. Display the Windows Control Panel.

2. Select System and Security.
3. Click System.

12
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

4. Check that the operating system is Windows Server 2019.

4 .3 Checking the disk space

Procedure

1. In the File Explorer, right-click the C drive.

2. Click Properties. The Properties dialog is displayed.
3. Check that there is enough free space on your disk drive to install the software. The minimum requirement is
20 GB.

13
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

4 .4 Creating the directory structure

In your user home directory, create the following directory structure with Temenos as the parent directory.

C:.
|
+---3rdParty
| +---AS
| +---JAVA
+---Install
+---T24
+---TAFJ
+---UXPBrowser

The following table shows the directory structure:

Folder Description

3rdParty All installed third-party software (e.g. JDK 1.8 and JBoss).

Install All installers required to set up TAFJ and Transact.

T24 All Transact-related libraries.

TAFJ TAFJ runtime libraries.

UXPBrowser Artefacts for the new UXP Browser.

4 .5 Configuring the environment variables

Procedure

1. In the File Explorer, right-click This PC.

2. Click Properties. A dialog box is displayed.
3. Click Advanced system settings. Another dialog box is displayed.
4. Click Environment Variables.
5. Use the New button to add the following to the system variables.
l BRP_HOME=%TEMENOS_HOME%
l JAVA_HOME=%TEMENOS_HOME%\3rdParty\JDK
l JBOSS_HOME=%TEMENOS_HOME%\3rdParty\AS\jboss-eap-7.3

14
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

l T24_HOME=%TEMENOS_HOME%\T24\bnk\UD
l TAFJ_HOME=%TEMENOS_HOME%\TAFJ
l TEMENOS_HOME=C:\Temenos
l UXPBROWSER=%TEMENOS_HOME%\UXPBrowser

4 .6 Verifying the system for third-party software

Procedure

1. To verify that JDK 1.8 is installed, at the command prompt enter java -version. Add the JAVA_HOME
variable and %JAVA_HOME%\bin to the %PATH% variable. You should see the Java version displayed.

2. To check that you can connect to the SQL database, use SQL Server Management Studio (SSMS) to
establish a connection.

15
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

3. To verify that JBoss EAP 7.3 is installed, and that JBOSS_HOME has been added as an environment
variable, check that the following folders are present in %JBOSS_HOME%.

16
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

5 Installing TAFJ runtime

5 .1 Extracting Transact
Procedure

1. Upload the Transact installation package ([Link]) from the

temporary folder on your machine to the %TEMENOS_HOME%\install folder on the application server.
2. Navigate to %TEMENOS_HOME%\install.
3. Extract the TAR file to the T24 directory (C:\Temenos\T24).

The file is extracted as a bnk folder.

5 .2 Installing TAFJ

Note:
Ensure that you have set the correct path for JAVA_HOME

Procedure

17
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1. Upload the TAFJ installation package ([Link]) from the temporary folder on
your machine to the %TEMENOS_HOME%\install folder on the application server.
2. In %TEMENOS_HOME%\install, extract [Link].

3. In the %TEMENOS_HOME%\install folder, open the command prompt.

4. Execute Setup_TAFJ.DEV.202008.1.

5. During the installation, when prompted for the installation directory, enter the path to %TAFJ_HOME%.

6. Specify y to allow the installer to create the TAFJ directory and press Enter.

18
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

7. Press Enter at the next prompt for Eclipse home directory.

8. Enter y to create the conf directory under %TAFJ_HOME%.

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

You should see the following folders in %TAFJ_HOME%:

10. In the File Explorer, open the command prompt from %TAFJ_HOME%\bin. Execute the tVersion
command to verify the TAFJ version.

19
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

11. In Windows Defender restore the quarantined [Link].

Note:
Machines with security policy enabled under Windows Defender or Norton Antivirus might face some
issues due to [Link], which is available as part of the TAFJ release. During the
installation, you may see a warning message.

5 .3 Deploying the database driver

TAFJ uses JDBC drivers to establish a connection with the database.

Database drivers are available in the %TAFJ_HOME%\dbdrivers folder. For your deployment, you must use
the latest version of the respective database driver downloaded from the database vendor’s portal.

Procedure

20
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1. Download the JDBC SQL driver from Microsoft portal.

2. Copy [Link] to the %TAFJ_HOME%\ext folder.

21
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

6 Configuring TAFJ
This chapter shows how to configure TAFJ runtime to set up Transact in standalone mode (i.e. outside an application
server). TAFJ does not use environment variables. Instead, it uses a properties file (*.properties) for its
internal configuration. Properties files are stored under the %TAFJ_HOME%\conf directory. The default property
file is [Link].

6 .1 Configuring [Link]

Note:
For more information on [Link], see the the guides in %TAFJ_HOME%\doc.

Procedure

1. Go to the %TAFJ_HOME%\conf folder.

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

4. Ensure that [Link] points to the Transact libraries.

22
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

5. Set up the database connection.

a. Under the Database setup header section, enter a value for [Link].
b. In [Link] change integratedSecurity to false.
c. Provide the relevant driver information in [Link].
d. Enter the database user name and password.
6. Ensure that [Link] points to the UD folder in %T24_
HOME%.

7. Set the value of [Link] and

[Link] to false (to improve database performance).

23
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

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

Note:
See the TAFJ-Lock Manager user guide (TAFJ-Lock [Link]) that is in %TAFJ_
HOME%\doc for information on creating and populating the TAFJ_HASHLOCKS table (which is
required for DATABASE locking mode).

6 .2 Verifying the TAFJ installation

Procedure

1. In %TAFJ_HOME%\bin, open the command prompt and enter [Link]. This will display the following
information.

24
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

l Where %TAFJ_HOME% is set to.

l The JDK version.
l The TAFJ version.
l The default project, and details of all the projects set in %TAFJ_HOME%\conf.
2. Check that these values are correct.
An example of tDiag output is illustrated below.

25
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

7 Sanity check
Before you deploy the application server, you must perform two sanity checks to verify that the Transact standalone
installation was successful.

7 .1 Accessing Transact Classic

Classic is one of the Transact user interfaces.

Procedure

1. In the File Explorer, open the command prompt from %TAFJ_HOME%\bin.

2. Enter tRun EX. The Classic command line interface is displayed.

26
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

3. Specify a valid Transact user name and password and press Enter.

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

7 .2 Accessing DBTools
DBTools is a TAFJ tool that provides a console to execute database commands. The console can only be accessed
by authenticated users.

Procedure

27
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1. In the File Explorer, go to %TAFJ_HOME%\bin.

2. Create a TAFJ user by passing username and password parameters to the [Link] utility.
tUserMgnt --Add -u tafjuser -p Temenos@123
The USER CREATION SUCCESSFUL message is displayed.
3. Launch DBTools, passing the TAFJ user credentials as parameters.
DBTools -u tafjuser -p Temenos@123
The DBTools console is launched.
4. View the database name, database user name and IP address displayed in the bottom left of the screen.

28
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

8 Configuring JBoss EAP 7.3

This section shows how to configure JBoss modules for TAFJ, Transact and the database.

8 .1 Configuration prerequisites
Before you start configuring JBoss with TAFJ and Transact, you need to make sure that:

1. TAFJ is installed (%TAFJ_HOME%).

2. Transact precompiled JAR files are in the correct location (%T24_HOME%\t24lib).
3. Your standalone mode (Classic) is working.

8 .2 Configuring memory settings

The default memory settings are as follows.

set "JAVA_OPTS=-Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m"

You need to consider refining your memory setting based on your application server load and system RAM.
Procedure

1. Change the memory setting in the [Link] file in %JBOSS_HOME%\bin.

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

2. Set the mandatory properties [Link] and [Link] in [Link]. Note

that TAFJ uses UTF-8 encoding.

29
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

8 .3 Configuring JBoss modules

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

Installing a module on JBoss EAP 7.3 requires creating a path under the %JBOSS_HOME%\modules folder.
Under this path, install the JAR libraries that are part of the module and a [Link] file that describes the
module itself and dependencies with other modules. You need to create three modules on your application server.

l MS SQL Server database driver module.

l TAFJ module.
l Transact module.

8.3.1 Deploying the MS SQL Server database driver module

For Transact to connect to a data source, this module must contain your data source vendors and JDBC drivers so
they can be used by JBoss.

Procedure

1. In the File Explorer, go to the modules folder in JBoss (%JBOSS_HOME%\modules).

2. In the modules folder, create the following directory structure.

mkdir com\microsoft\sqlserver\main

3. Copy [Link] from %TAFJ_HOME% to the main folder for the corresponding database.

copy %TAFJ_
HOME%\appserver\jboss\jboss7eap\modules\com\microsoft\sqlserver\main\modul
[Link] %JBOSS_HOME%\modules\com\microsoft\sqlserver\main

4. Copy the corresponding database driver to the main folder of SQL Server.

copy %TAFJ_HOME%\ext\[Link] %JBOSS_

HOME%\modules\com\microsoft\sqlserver\main

30
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

5. Open [Link] to verify that the driver JAR name matches the folder path for that module.

8.3.2 Configuring the TAFJ module

This module contains the TAFJ libraries in lib and ext folders and will have a dependency on the database driver
module.

Procedure

1. In the File Explorer, in the com folder, create the following directory structure.

mkdir temenos\tafj\main

2. Copy the TAFJ [Link] from %TAFJ_HOME% to the main folder to the %JBOSS_
HOME%\modules folder.

copy %TAFJ_
HOME%\appserver\jboss\jboss7eap\modules\com\temenos\tafj\main\[Link]
%JBOSS_HOME%\modules\com\temenos\tafj\main

3. In %JBOSS_HOME%\modules\com\temenos\tafj\main, open the command prompt.

31
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

4. Create a symbolic link to %TAFJ_HOME%\lib and %TAFJ_HOME%\ext.

mklink /D lib %TAFJ_HOME%\lib

mklink /D ext %TAFJ_HOME%\ext

5. Open [Link] and uncomment the SQL Server database driver module dependency in the
<dependencies> section.
The TAFJ module has dependencies on the Transact module that you need to create. It also contains the MS
SQL Server database driver module.

8.3.3 Configuring the Transact module

This module contains the Transact JAR files and has a dependency on the TAFJ module created above.

Procedure

1. In the File Explorer, in the temenos folder, create this directory structure.

mkdir t24\main

2. Open command prompt from %JBOSS_HOME%\modules\com\temenos\t24\main.

32
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

3. Create a symbolic link to %TEMENOS_HOME%\T24\bnk\t24lib.

mklink /D lib %TEMENOS_HOME%\T24\bnk\t24lib

8.3.4 Generating the Transact

Unlike the TAFJ [Link], the Transact [Link] must be generated. You can generate this module
using the JBossTools utility that is in %TAFJ_HOME%\bin.

Procedure

1. In %TAFJ_HOME%\bin, run the following command to create the [Link] file .

JBossTools module_name path_to_jars dest root_prefix -tafjdep

module_name
Name of the JBoss module. Must be the same as the folder path created for the module.

path_to_jars
The list of folders that you want to parse.

dest
The path to the folder where the [Link] will be generated.

root_prefix
Name of the link if [Link] is at the same level as the link.

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

An example is given below.

33
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

JBossTools [Link].t24 %TEMENOS_HOME%\T24\bnk\t24lib %JBOSS_

HOME%\modules\com\temenos\t24\main lib –tafjdep

2. Open [Link] and verify that the TAFJ module is added as a dependency in the <dependencies>
section.

34
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

9 Configuring a 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 the standalone installation.

To deploy Transact on TAFJ on EAP, you must configure the various subsystems in [Link]. TAFJ uses
the management Command Line Interface (CLI) interface tool to automate the process of configuring the J2EE
profiles.

Procedure

1. In the File Explorer, copy and paste [Link] into %JBOSS_

HOME%\standalone\configuration and rename it to [Link].
2. Start JBoss using the command given below.

%JBOSS_HOME%\bin\[Link] –b [Link] –bmanagement [Link] --server-

config=[Link]

Note:
As [Link] is being used, this command must use the option --server-config to
specify the configuration file.

3. Navigate to TAFJ_HOME%\appserver\jboss\jboss7eap\jboss-cli and open

[Link] in an editor.
4. In the Drivers section, uncomment the driver parameters according to the database used.

35
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

5. In the System Property section, comment out the [Link] property.

6. Open [Link].
7. Enter values for the TAFJ_HOME, DB_URL, DB_DRIVER, DB_USER, and DB_PWD parameters.

8. To resolve the user specific system properties in [Link] that will be passed as command
argument to JBoss CLI command, set the value of <resolve-parameter-values> to true in
%JBOSS_HOME%\bin\[Link]. Ensure that <validate-operation-requests>
is set to true.

36
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

9. To update the [Link] file, run the following command:

%JBOSS_HOME%\bin\[Link] --connect
--file=C:\Temenos\TAFJ\appserver\jboss\jboss7eap\jboss-cli\[Link]
--properties=C:\Temenos\TAFJ\appserver\jboss\jboss7eap\jboss-
cli\[Link]

You launch JBoss CLI from the %JBOSS_HOME%\bin folder by running the [Link] script.
The complete command takes two arguments, --file and --properties:
l The --file argument enables CLI commands to be provided from a text file. The %TAFJ_
HOME%\appserver\jboss\jboss7eap\jboss-cli folder has a CLI script file
[Link]. The script has commands to update the profiles specific for Transact deployment.
l The --properties argument enables passing user-specific properties to the script file from a
property file. In the same location you will find [Link].

On successful execution the command updates the required subsystems in [Link] (which was
used to start up JBoss). If this is successful, you will see text similar to the illustration below.

The scripts now add the following items to the standalone configuration file ([Link]):

l System properties
l Drivers
l Data sources
l Global modules (TAFJ and Transact)
l JMS Pools
l JMS Queues
10. Stop the JBoss instance.

The configuration of JBoss with Transact-TAFJ is now complete.

37
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

10 Extracting UXP Browser artefacts

Before you start installing UXP Browser, you need to prepare its installation packages. This section shows the
required steps before deploying Transact and TAFJ artefacts.

Procedure

1. Obtain [Link] from your account manager and upload it to the %TEMENOS_
HOME%\UXPBrowser folder on the application server.
2. In this folder, extract [Link].
3. Locate the IRISR18_CatalogServices_TAFJ_202008.[Link] file in your model bank
package on your local machine and extract it.
4. Upload the [Link] file to the %UXPBROWSER%
directory on your Transact server.
5. Optional: Rename the artefact file names in %UXPBROWSER% by removing the release version information:

Before After

l [Link] l [Link]
l [Link] l [Link]
l [Link] l [Link]
l irf-t24catalog-services- l irf-t24catalog-
[Link] [Link]
l [Link] l [Link]

Note:
You need to rename [Link] to [Link]

38
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

11 Configuring and deploying Transact and

TAFJ artefacts
The final step in this setup is to deploy the Transact UI components UXP Browser (UXPB) and BrowserWeb. UXP
Browser is the Temenos' latest user interface for working with Transact. BrowserWeb is its forerunner.

Note:
This runbook does not cover deployment of other product user interfaces such as Temenos Connect Internet
Banking (TCIB) and Mobile Banking (TCMB).

1 1 .1 Deploying TAFJJEE_EAR.ear and TAFJ Spooler plugins

Procedure

1. In the File Explorer, copy [Link] from %TAFJ_HOME%\appserver to the

%JBOSS_HOME%\standalone\deployments folder.

2. Copy TAFJJEE_EAR.ear from %TAFJ_HOME%\appserver\jboss\jboss7eap to the

%JBOSS_HOME%\standalone\deployments folder.

1 1 .2 Deploying BrowserWeb
Before you begin

You need to obtain the [Link] file from your account manager.

Procedure

1. Upload the [Link] file from the temporary folder on your machine to the
%TEMENOS_HOME%\Install folder on the application server.

2. Extract the [Link] file in the Install folder.

3. Copy the [Link] file to the %JBOSS_HOME%\standalone\deployments folder.

39
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1 1 .3 Modifying [Link]
Procedure

1. In Windows File Explorer, navigate to %UXPBROWSER% and open [Link] in a compression tool,
for example 7-zip.
2. Navigate to WEB-INF and open [Link] in an editor.
3. Provide the port number and IP address or host name of your application server where you will deploy
Authenticator. Use the actual host IP address and the HTTP [Link]:

[Link]=[Link]

Tip:
As an alternative, you can add the above line in the [Link] file.
This will act as an override and you will not need to modify the [Link] file.

4. Save the file and close the compression tool.

1 1 .4 Modifying [Link]
Procedure

1. In Windows File Explorer, navigate to %UXPBROWSER%.

2. Open the [Link] file in a compression tool, for example 7-zip and navigate to \WEB-
INF\classes.
3. Open [Link] in your text editor and provide the IP address or host name of your
application server, the port, user name and password. Example:

# Common EJB Remote Configurations

RemoteConnectionHosts=[Link]
RemoteConnectionPorts=9089
transportLayerUser=SSOUSER1
transportLayerCredential=123456

4. Save the file and exit the file compression tool.

40
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1 1 .5 Modifying [Link]
Procedure

1. In Windows File Explorer, navigate to %UXPBROWSER%.

2. Open the [Link] file in a compression tool, for example 7-zip, and
navigate to \WEB-INF\classes
3. Open [Link] in your text editor and provide the IP address or host name of your
application server, the port, Transact user name and password for that user. Example:

# Common EJB Remote Configurations

RemoteConnectionHosts=[Link]
RemoteConnectionPorts=9089
transportLayerUser=SSOUSER1
transportLayerCredential=123456

4. Save the file and exit the file compression tool.

1 1 .6 Embedding the database driver in [Link]

Procedure

1. In Windows File Explorer, change to %UXPBROWSER%

2. Open the [Link] file in a compression tool, for example 7-zip, and navigate to \WEB-
INF\lib.
3. Copy the database driver file ([Link]) to [Link]\WEB-INF\lib.

4. Save the file and exit the file compression tool.

41
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1 1 .7 Modifying the required EJB JAR files

Procedure

1. To prepare the required EJB JAR files, copy the following three files to the %UXPBROWSER% directory:
copy %TEMENOS_HOME%\T24\bnk\Extensions\EB_
AuthenticationService\t24ejb\t24-EB_AuthenticationService-[Link]
%UXPBROWSER%\
copy %TEMENOS_HOME%\T24\bnk\Extensions\EB_CatalogService\t24ejb\t24-
EB_CatalogService-[Link] %UXPBROWSER%\
copy %TEMENOS_HOME%\T24\bnk\Extensions\EB_
ResourceProviderService\t24ejb\t24-EB_ResourceProviderService-
[Link] %UXPBROWSER%\
2. Modify t24-EB_AuthenticationService-ejb.
a. Open the t24-EB_AuthenticationService-ejb file in a compression utility and navigate to
META-INF.
b. Open the [Link] file in an editor.
c. In <transaction-type>, specify Bean.

<session-type>Stateless</session-type>

<transaction-type>Bean</transaction-type>

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

<env-entry>
<description>Comma Separated Runtime Properties for TAFJ
Session</description>
<env-entry-name>runtimeProperties</env-entry-name>
<env-entry-type>[Link]</env-entry-type>
<env-entry-value>OFS_SOURCE=IRISPA</env-entry-value>
</env-entry>

e. Save the file.

42
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

f. Open [Link] file in an editor and ensure that the security domain is set to other.

<assembly-descriptor>
<s:security>
<ejb-name>AuthenticationServiceBeanTAFJ</ejb-name>
<s:security-domain>other</s:security-domain>
</s:security>
</assembly-descriptor>

g. Save the file and exit the file compression utility.

3. Modify t24-EB_CatalogService-[Link].
a. Open the t24-EB_CatalogService-[Link] file in a compression utility and navigate to
META-INF.
b. Open the [Link] file in an editor.
c. In <transaction-type>, specify Bean.

<session-type>Stateless</session-type>

<transaction-type>Bean</transaction-type>

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

<env-entry>
<description>Comma Separated Runtime Properties for TAFJ
Session</description>
<env-entry-name>runtimeProperties</env-entry-name>
<env-entry-type>[Link]</env-entry-type>
<env-entry-value>OFS_SOURCE=IRISPA</env-entry-value>
</env-entry>

e. Save the file.

f. Open [Link] file in an editor and ensure that the security domain is set to other.

<assembly-descriptor>
<s:security>
<ejb-name>CatalogServiceBeanTAFJ</ejb-name>
<s:security-domain>other</s:security-domain>

43
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

</s:security>
</assembly-descriptor>

g. Save the file and exit the file compression utility.

4. Perform the same steps as above to modify [Link] and [Link] in t24-EB_
[Link].
a. Open the t24-EB_ResourceProviderService-[Link] file in a compression utility and
navigate to META-INF.
b. Open the [Link] file in an editor.
c. In <transaction-type>, specify Bean.

<session-type>Stateless</session-type>

<transaction-type>Bean</transaction-type>

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

<env-entry>
<description>Comma Separated Runtime Properties for TAFJ
Session</description>
<env-entry-name>runtimeProperties</env-entry-name>
<env-entry-type>[Link]</env-entry-type>
<env-entry-value>OFS_SOURCE=IRISPA</env-entry-value>
</env-entry>

e. Save the file.

f. Open [Link] file in an editor and ensure that the security domain is set to other.

<assembly-descriptor>
<s:security>
<ejb-name>ResourceProviderServiceBeanTAFJ</ejb-name>
<s:security-domain>other</s:security-domain>
</s:security>
</assembly-descriptor>

g. Save the file and exit the file compression utility.

44
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

1 1 .8 Configuring the SSOUSER1 user in JBoss

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

Procedure

1. At the Windows command prompt, navigate to %JBOSS_HOME%\bin.

2. Run the [Link] script:
[Link]
3. Specify Application user (option b) as the type of user.

C:\Temenos\3rdParty\AS\jboss-eap-7.3\bin>[Link]

What type of user do you wish to add?

a) Management User ([Link])
b) Application User ([Link])
(a): b

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

Enter the details of the new user to add.

Using realm 'ApplicationRealm' as discovered from the existing property
files.
Username : SSOUSER1
Password recommendations are listed below. To modify these restrictions
edit the [Link] configuration file.
- The password should be different from the username
- The password should not be one of the following restricted values
{root, admin, administrator}
- The password should contain at least 8 characters, 1 alphabetic
character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
Password :

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

WFLYDM0099: Password should have at least 8 characters!

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

45
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

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

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

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

Is this correct yes/no? yes

The user has been added to JBoss configuration files.

Added user 'SSOUSER1' to file 'C:\Temenos\3rdParty\AS\jboss-eap-

7.3\standalone\configuration\[Link]'
Added user 'SSOUSER1' to file 'C:\Temenos\3rdParty\AS\jboss-eap-
7.3\domain\configuration\[Link]'
Added user 'SSOUSER1' with groups t24user to file
'C:\Temenos\3rdParty\AS\jboss-eap-
7.3\standalone\configuration\[Link]'
Added user 'SSOUSER1' with groups t24user to file
'C:\Temenos\3rdParty\AS\jboss-eap-7.3\domain\configuration\application-
[Link]'

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

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

The user has been created and the following message is displayed at the command prompt:

To represent the user add the following to the server-identities

definition <secret value="MTIzNDU2" />

9. Open the [Link] file that is in %JBOSS_HOME%\standalone\configuration in a text

editor and add under <server-identities> the tag that you generated in the previous step:

<server-identities>
<ssl>

46
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

<keystore path="[Link]" relative-

to="[Link]" keystore-password="password" alias="server"
key-password="password" generate-self-signed-certificate-
host="localhost"/>
</ssl>
<secret value="MTIzNDU2" />
</server-identities>

1 1 .9 Configuring UXP Browser in the Generate On Demand (GOD) mode

Before you begin

You need to locate the encryption utility ([Link]) in your Model Bank package and then
upload it to the $UXPBROWSER directory on the application server. The JAR file is available at the following
location:
Model_Bank_package.zip\[Link]\UXPB-
[Link]\[Link]

Procedure

1. At the command line, navigate to %TEMENOS_HOME% and create the properties directory.
2. Go to the %UXPBROWSER% directory and extract the [Link]
file.
3. Copy the two properties files to the properties directory where they will be stored permanently:
4. Encrypt the IRIS system and JDBC user passwords using the Temenos encryption utility
[Link] – run the following command:
java -jar [Link] pwd_to_be_encrypted
Example:

5. Save the encrypted password in a file in a secure location.

47
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

6. Edit the [Link] file in a text editor - perform the following steps:
a. Provide the Transact user name and the encrypted password (here 123456):

[Link]=INPUTT
[Link]=vSd3/5UdSJc=

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

[Link]=[Link]
services
[Link]=[Link]
t24catalog-services

[Link]=
[Link]

[Link]=
[Link]

c. Save the file.

7. Edit the [Link] file in a text editor – provide the following and save
the file:
a. Database URL
b. Database user name
c. The encrypted password for the database user
d. JDBC driver name for MS SQL Server
e. Blob type
f. Long type

Example:

[Link].1=
jdbc:sqlserver://[Link];databaseName=MB202008;integratedSecu
rity=false
[Link].1=tafj
[Link].1=DySX79VV3rQ=

48
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

[Link].1=
[Link]
[Link].1=varbinary(max)
[Link].1=bigint

1 1 .1 0 Deploying UXP Browser artefacts in JBoss

[Link] is the main UXP Browser artefact. UXP Browser requests are routed through Interaction
Framework, so along with the Browser, you must also deploy the Authenticator application , the Resource Provider
and Interaction Framework catalog services and also Resource server. This section is not applicable if you have
skipped "Extracting UXP Browser artefacts" on page 38.

Procedure

1. At the Windows command prompt, change to %UXPBROWSER%.

2. Deploy the Authenticator component.
copy [Link] %JBOSS_HOME%\standalone\deployments
3. Deploy [Link].
copy [Link] %JBOSS_HOME%\standalone\deployments
4. Deploy Interaction Framework Resource Provider services.
copy [Link] %JBOSS_HOME%\standalone\deployments
5. Deploy Interaction Framework Catalog services.
copy [Link] %JBOSS_HOME%\standalone\deployments
6. Deploy Resource Server.
copy [Link] %JBOSS_HOME%\standalone\deployments

1 1 .1 1 Deploying the EJB JAR files in JBoss

Procedure

1. Deploy the Authentication service.

cd %UXPBROWSER%

49
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

copy t24-EB_AuthenticationService-[Link] %JBOSS_

HOME%\standalone\deployments
2. Deploy the Catalog Service component.
copy t24-EB_CatalogService-[Link] %JBOSS_
HOME%\standalone\deployments
3. Deploy the Resource Provider service.
copy t24-EB_ResourceProviderService-[Link] %JBOSS_
HOME%\standalone\deployments

50
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

12 Deploying Transact component services

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

1 2 .1 Step 1: Packaging Axis2 archives

Procedure

1. From the Apache website download [Link].

2. Extract the zip file.
3. In File Explorer, copy [Link] to any directory (e.g. UXPBrowser).
4. Open [Link] in a file compression tool, for example 7-zip, and navigate to WEB-INF\lib.
5. Add the following dependency JAR files to the lib folder.
l [Link]
l [Link]

6. Copy the following component service archives from the subdirectories under %TEMENOS_
HOME%\T24\bnk\Extensions into the WEB-INF\services directory of [Link].

51
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

l t24-DS_DesignStudioInstallerService-[Link]
l t24-EB_CatalogService-[Link]
l t24-EB_OFSConnectorService-[Link]
l t24-EB_ResourceProviderService-[Link]
l t24-IF_IntegrationFlowService-[Link]
l t24-IF_IntegrationFrameworkService-[Link]
l t24-IF_IntegrationLandscapeService-[Link]
7. Open WEB-INF\services\[Link] and add the names of the component service archives
that you added to the services directory.

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

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

<resource-ref id="ResourceRef_t24DataSource">
<description>Used to get connections from T24 jdbc pool</description>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<res-type>[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. In WEB-INF add the the JBoss-specific deployment descriptor ([Link]).

10. Configure database connectivity by adding the data sources.

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

<jboss-web>

52
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

11. Save the changes to [Link].

1 2 .2 Step 2: Deploying Axis2

Procedure

1. In the Windows File Explorer, navigate to %JBOSS_HOME%\standalone\configuration.

2. Open [Link].
3. In datasource, add the data source for [Link] deployment.

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

name="Axis2DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>
jdbc:sqlserver://[Link];databaseName=MBR20;integratedSecurity=f
alse</connection-url>
<connection-property name="defaultRowPrefetch">100</connection-
property>
<driver>sqljdbc</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>tafj</user-name>
<password>xxxx</password>

53
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

</security>
</datasource>

4. Copy [Link] from the UXPBrowser folder to %JBOSS_

HOME%\standalone\deployments.
copy [Link] %JBOSS_HOME%\standalone\deployments

Result: You have now deployed all the required components.

54
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

13 Sanity check - post deployment

Log in to Transact through the product user interfaces to verify your application server deployment. This section
shows the steps to login using UXP Browser and BrowserWeb.

1 3 .1 Starting the application server

Procedure

1. In %JBOSS_HOME%\bin, run [Link] to start JBoss.

If you are not deploying UXP Browser, the following are sufficient.

%JBOSS_HOME%\bin\[Link] --server-config=[Link] –b [Link] -

[Link]=9089

If you are deploying UXP Browser, the following are required. (Each command argument has been placed in a
new line for brevity.)

%JBOSS_HOME%/bin/[Link]
--server-config=[Link]
-[Link]=9089
-[Link]=node1
-b [Link]
-DedgeSystemPropertyFolder=%TEMENOS_HOME%\properties
-DedgeSystemPropertyUpdaters=
[Link]
-DBRP_HOME=%TEMENOS_HOME%

Note:
Optionally you may set JBoss HTTP port (-[Link]=9089) to start JBoss at a user-
defined port instead of the default HTTP port 8080.

2. When the server is started, in the %JBOSS_HOME%\standalone\deployments folder check that all
the artefacts listed have been deployed.

13.1.1 Mandatory command arguments

--server-config

55
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

Indicates standalone profile configuration file (for example [Link]) to use at JBoss startup.

-[Link]
Port number of the application server.

-[Link]
Unique identifier for the application server instance.

-DedgeSystemPropertyUpdaters
This argument is used to set the required properties to be loaded. For GOD mode, use the value below:

[Link]

1 3 .2 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.

Procedure

1. Open the command prompt in %JBOSS_HOME%\bin.

2. Run [Link] to create an application user.
2. Give the user TAFJAdmin role.
a. Specify the type of user, here Application user.
b. Provide the preferred user name and password.
c. Specify the groups the user should belong to; here TAFJAdmin.
d. Confirm the addition of the user to the realm ApplicationRealm by providing the answer yes.
e. For the last question, provide the answer no.

3. Use URL [Link] to access the TAFJEE servlet.

56
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

4. Enter the application user credentials.

This gives you access to all the functions in TAFJEE.

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

57
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

1 3 .3 Accessing BrowserWeb
Procedure

1. Access BrowserWeb using the following URL:

[Link]
.

58
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

The landing page is displayed.

59
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

1 3 .4 Accessing UXP Browser

Procedure

1. Use the following URL to access UXP Browser.

[Link]

60
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

2. Log in to Browser using a valid Transact user name and password. The landing page is now displayed.

61
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

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

1 3 .5 Using the Axis2 servlet

13.5.1 Accessing the Axis2 servlet

Procedure

1. Use the following URL to access the Axis2 servlet.

[Link]

62
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

2. Click Validate. A new page opens.

3. Check whether the web services are working correctly.

63
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

4. Go back to the main page and click Services. The services deployed in Axis2 are displayed.

13.5.2 Testing Axis2 and Transact

Procedure

1. In the Axis2 servlet, select Services.

2. Select a service to display the WSDL file (the example illustrated below is for IntegrationFlowService).

64
Stack 6 for JBoss - Windows Runbook runbook, version 2.0

3. Using a third-party tool, such as SOAPUI, create a new SOAP project using WSDL.

4. Create a new read flow.

This completes the deployment of Transact on TAFJ on JBoss EAP 7.3 with the SQL Server 2019 database.
You will now be able to perform business operations in Transact using BrowserWeb and UXP Browser.

65