Transact [Web & App] preimage kit on TAFJ

Cloud Native Version

1
Transact TAFJ Cloud Native Version Delivery Note

1. About this note

History
Version Date Change Author

1.4 April 2020 Publication Cloud Technology Solutions

team

1.5 June 2020 Added building Cloud Technology Solutions

BrowserWeb and API team
container image section

2.0 January 2022 Added notes for TAFJ Cloud Technology Solutions
Upgrade

3.0 March 2022 Date Corrections on Cloud Technology Solutions

Delivery Note

4.0 October 2023 Details on the inclusion Cloud Technology Solutions

of Base Image Kit
adoption

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

The information in this guide relates to TEMENOSTM information, products and

services. It also includes information, data and keys developed by other parties.

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

There is no guarantee as to the completeness, accuracy, timeliness or the results

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

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

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.

3
Transact TAFJ Cloud Native Version Delivery Note

Base Image Kit Adoption

From 202310 Release Onwards Temenos is adopting Base Image Kits.
Along with Transact Image Kits user would be receiving a baseimages-docker-<release>.zip. This zip
consists of subfolders with Dockerfile. The subfolders are named in the format.
temn-<osversion>-<Application Server version>-<jdk version>.

Ex: temn-ubi9-wf26-jdk11

User consuming Transact Image kits are requested to Build the Base Container image by following the
documentation provided in the baseimages-docker-<release>.zip.
Consume this base image during the Transact Container image build by passing it as docker build
arguments.

The combination of temn-<osversion>-<Application Server version>-<jdk version> for Transact

Image Build is temn-ubi9-wf26-jdk11.

Examples for Building the base images.

Docker build -t <Image name>:<Tag>

[If Local build]: docker build -t temnubi9wf26jdk11:<Tag> <folder where Dockerfile Exists>

docker build -t temnubi9wf26jdk11:202310 temn-ubi9-wf26-jdk11

[If Repository/Registry build]: docker build -t <Repository/Registry>/temnubi9wf26jdk11:<Tag> . (Assuming the

base Dockerfile is available in the current directory)

docker build -t azurecr.io/temnubi9wf26jdk11:202310 temn-ubi9-wf26-jdk11

2. What your delivery contains

There are two preimage kits in this delivery.

 preimage-transact-web-<release>.zip - Transact Web preimage kit which is

generic for all environments.

For example: preimage-transact-web-R20.3.zip, where

R20 refers to the Transact release
.3 is the image kit release version.

 preimage-transact-app-<database type>-<release>.zip - Transact App

preimage kit built for a specific database.

4
 Transact TAFJ Cloud Native Version Delivery Note
For example: preimage-transact-app-sql-R20.4.3.zip were
sql in the name indicates that images built from this image kit will run
against SQL Server database,
R20.4 refers to the TAFJ release R20 SP4
.3 is the image kit release version.

Note: If there is a requirement to upgrade TAFJ release (Higher Release or SP). The
recommendation is to request from Distribution for a new image kit with updated version of TAFJ.

3. Purpose of Preimage kits

Temenos distributes preimage kits which you can customise and then build docker
images to deploy in the web and app layer of your Transact cloud deployment. The
preimage kits come with Temenos softwares and configuration files of open source
software that is used in the containers.

Docker images are immutable. However, the preimage kits delivered to you come
with customization capability. For example, TAFJ runtime parameterization can be
modified and new wildfly queue configuration can be added before you build your
finished Transact App docker images.

The preimage kits also come with extension capability. For example, you can
easily extend the Transact Web preimage kit to build a REST Api container image
or a Browser container image from it.

Note: Temenos does not distribute 3rd party and open source softwares like base
container OS, application server, JDK in its preimage kits. The base image and all
open source layers are pulled at build time from their respective registry.

5
Transact TAFJ Cloud Native Version Delivery Note

4. Contents of Transact Web

Preimage Kit
The Transact Web Preimage kit is configured to run Temenos presentation layer
artefacts in Wildfly 20.0.0 against Apache ActiveMQ/Amazon MQ message broker.
You will use this preimage kit to build UXP Browser, Browser classic, IRIS 18
Experience and Enterprise API’s, TCxB (Retail/Corporate/UA) docker images etc.

The Web preimage kit is a generic kit. Images built from this kit are independent of
the database and deployed in the web layer of a Transact deployment on the cloud.

The Zip archive delivered to you, extracts to a directory with the same name as the
Preimage zip filename and has the following contents.

File Name Description

Dockerfile Instructions to build Browser classic web image.

The RedhatUBI, OpenJDK and Wildfly 20.0.0 layers
are pulled from their registry at build time.

preimage.tar Docker entrypoint and script files

deployment_extras Folder to add J2EE deployments. For example: an

IRIS Enterprise API war. At build time the contents
from this folder are added to Wildfly deployments

user_config_files Wildfly profile T24AppStd01.xml with

transact specific configuration for queues

preimage.tar/opt/jboss/wildfly docker-entrypoint files

prop Folder to add property files for UXPB deployment

tphartefacts Folder to add TPH property files specific to each

flow

6
Transact TAFJ Cloud Native Version Delivery Note

tphppdir Folder to add UD/PP folder from Transact archive

Additionally, the Zip archive contains a README.txt which gives the steps to build
the container images.

To extend the web preimage kit, visit the section Customising your Web Preimage.

4. Contents of Transact App

Preimage Kit
The Transact App Preimage kit is a Temenos version of TAFJ configured to run in
Wildfly 20.0.0 against Apache ActiveMQ/Amazon MQ message broker and a
specific database. The App preimage kit: preimage-transact-app-sql-R20.4.3 is the
R20 SP4 version of TAFJ for SQL Server database. You will use this preimage kit
to build the Transact App docker container image. The docker image built from this
image kit is deployed in the App layer of a Transact deployment on the cloud.

The Zip archive delivered to you, extracts to a directory with the same name as the
Preimage zip filename and has the following contents.

File Name Description

Dockerfile Instructions to build Transact App image. The

Redhat UBI, OpenJDK and Wildfly 20.0.0 layers are
pulled from the respective registry at build time.

preimage.tar TAFJ runtime, docker entrypoint and startup scripts.

app Folder to add t24 libraries and UD files from your

Model Bank/ISB package delivered from distribution.
L3 code jars are also added to this folder.

deployment_extras Folder to add J2EE deployments. The contents are

added to Wildfly deployments at build time. By

7
Transact TAFJ Cloud Native Version Delivery Note

default the folder contains activemq rar and

TAFJJEE_EAR.ear and TAFJSpoolerPlugins.rar

user_config_files T24Appstd01.xml and tafj.properties files in this

folder are used to make Wildfly and tafj
changes.

db_driver_config The latest database drivers downloaded from the

database vendor will be placed in this folder.

t24updates_extras Folder to add updates downloaded from TCSP

portal.

preimage.tar/opt/jboss/wildfly docker-entrypoint files

preimage.tar/srv/Temenos Has the TAFJ runtime and the TAFJ configuration

file TAFJTrace.properties.k8s

prop Folder to add property files for UXPB deployment

channels_corp Folder to add the Channels generated zip file

required to deploy Channels-iris war

Additionally, the Zip archive contains a README.txt which gives the steps to build
the container images.

The Section on Customising your App Preimage will identify the steps to add the
Transact libraries from your Model bank package and adding other J2EE
deployments.

8
Transact TAFJ Cloud Native Version Delivery Note

5. Customising your Web Preimage

Extend your Transact Web Preimages before moving to the next step to build
container images from them.

5.1Building Browser classic container

Image
1. Unzip the Transact Web preimage kit zip file.
2. Modify the BrowserWeb.war that you received from distribution. Open
helpParameters.xml.
3. Set the path of viewLocation and editLocation to /opt/HELP.TEXT/HelpText/.
4. Set the path of imagesDir to /opt/HELP.TEXT/HelpText/HelpImages/.

5. Open browserParameters.xml and change the IP ADDRESS CHECK

parameter value to NO.

6. Place the modified BrowserWeb.war in the

${EXTRACT_DIR}/deployments_extras directory.
7. Build a docker image from this preimage kit which creates a new container
image with BrowserWeb.

9
Transact TAFJ Cloud Native Version Delivery Note

For example:

$ unzip ${DOWNLOAD_DIR}/preimage-transact-web-R20.x.zip
$ docker build -t transact-web:R20.x preimage-transact-web-R20.x

Using base Image, the build options are as below

If the base image is in a repository user need to pass the build arguments BASE_REPO and
BASE_TAG. Example below
docker build -t transact-web:Rnn.x --build-arg
BASE_REPO="artifactory.shs.saas.temenos.cloud/temenosbaseimages/" --build-arg BASE_TAG="Rnn"
preimage-transact-web-Rnn.x

In the above example the repo "artifactory.shs.saas.temenos.cloud/temenosbaseimages/" would

contain “temnubi9wf26jdk11” with a tag “Rnn”

If the base image is built locally, user need to pass the BASE_REPO argument as null and BASE_TAG
with the value used to build the base image. Example below

docker build -t transact-web:Rnn.x --build-arg BASE_REPO="" --build-arg BASE_TAG="Rnn" preimage-

transact-web-Rnn.x

8. Push the new web container image to your Container Registry.

5.2 Building API container Image

1. Unzip the Transact Web preimage kit zip file, and user could the web image kit preimage-
transact-web-R20.x as preimage-transact-api-R20.x.

2. Some of the application files that you can add to the deployments_extras
directory to build an API image are listed below:

 PSD2 payments APIs - irf-psd2-BG-LUXHUB-PX.war and irf-psd2-BG-

LUXHUB-PZ.war

 Channels IRIS 18 API - tc-channels-api.war

 Temenos public APIs – irf-provider-container.war

 Temenos test APIs – irf-test-web.war

3. Place the required API war files in the deployments_extras directory.

4. Build a docker image from this preimage kit which creates a new container
image.

10
Transact TAFJ Cloud Native Version Delivery Note

For example:

$ unzip ${DOWNLOAD_DIR}/preimage-transact-api-R20.x.zip
$ docker build -t transact-api:R20.x preimage-transact-api-R20.x

Using base Image, the build options are as below

If the base image is in a repository user need to pass the build arguments BASE_REPO and
BASE_TAG. Example below
docker build -t transact-api:Rnn.x --build-arg
BASE_REPO="artifactory.shs.saas.temenos.cloud/temenosbaseimages/" --build-arg BASE_TAG="Rnn"
preimage-transact-api-Rnn.x

In the above example the repo "artifactory.shs.saas.temenos.cloud/temenosbaseimages/" would

contain “temnubi9wf26jdk11” with a tag “Rnn”

If the base image is built locally, user need to pass the BASE_REPO argument as null and BASE_TAG
with the value used to build the base image. Example below

docker build -t transact-api:Rnn.x --build-arg BASE_REPO="" --build-arg BASE_TAG="Rnn" preimage-

transact-api-Rnn.x

5. Push the new api container image to your Container Registry.

Follow the same procedure for adding other UXP user interface deployments like
Retail war, IRIS API workbench irf-web-client.war etc. Build container images after
adding the deployments and push the image to your container registry.

11
Transact TAFJ Cloud Native Version Delivery Note

6. Customising your App Preimage

You need to add Transact libraries in the App Preimage kit before moving to the
next step to build container images.

 Unzip the Transact App preimage kit zip file.

 Navigate to ${EXTRACT_DIR}/app.

 Unpack the Transact archive you received from distribution.

 Your unpacked archive should have several directories including "t24lib"

and "UD". These should be directly placed in the "app" directory.

 If your archive has a different structure, you need to move the t24lib
directory and other directories into the ${EXTRACT_DIR}/app directory.

You can customise your Transact App Preimages with J2EE deployments from
distribution and your own applications.

 Navigate to ${EXTRACT_DIR}/deployments_extras and add J2EE

deployments. The docker build adds the extra deployments to the container
image.
 Navigate to $EXTRACT DIR/user_config_files and, if any more
modifications are needed, modify the configuration files and save them to
the user config files directory.
 Go to $EXTRACT DIR/db_driver_config and, if the user wants to use the
latest driver, replace it and update the tafj-module.xml and jboss-
module.xml files.

6.1 Building Transact App Container Image

The steps to build a Transact App container Image from the Transact App
Preimage Kit are:

 Unzip the Transact App Preimage Kit zip file.

 Customise your App Preimage as described in the section Customising

your App Preimage to add your Transact libraries.

 Run docker build against the directory it creates.

12
Transact TAFJ Cloud Native Version Delivery Note
For example:

$ unzip ${DOWNLOAD_DIR}/preimage-t24-app-sql-R20.x.x.zip
$ docker build -t t24-app-sql:R20.x preimage-t24-app-sql-R20.x.x

Using base Image, the build options are as below.

If the base image is in a repository user need to pass the build arguments BASE_REPO and
BASE_TAG. Example below
docker build -t transact-app-sql:Rnn.x --build-arg
BASE_REPO="artifactory.shs.saas.temenos.cloud/temenosbaseimages/" --build-arg BASE_TAG="Rnn"
preimage-transact-app-sql-Rnn.x

In the above example the repo "artifactory.shs.saas.temenos.cloud/temenosbaseimages/" would

contain “temnubi9wf26jdk11” with a tag “Rnn”

If the base image is built locally, user need to pass the BASE_REPO argument as null and
BASE_TAG with the value used to build the base image. Example below

docker build -t transact-app-sql:Rnn.x --build-arg BASE_REPO="" --build-arg BASE_TAG="Rnn"

preimage-transact-app-sql-Rnn.x

13
Transact TAFJ Cloud Native Version Delivery Note

The -t repository:tag option to docker build is optional. It applies a tag to the

output image that you can refer to in later commands.

The Dockerfile in the Image Kit will download the required open source
dependencies from the internet and install the Temenos software to create a
finished image.

14
Transact TAFJ Cloud Native Version Delivery Note

7. UXP Browser configuration

This section gives the minimum configuration changes to UXPB artefacts required
for building container images.
[Note: Refer to product documentation for detailed configuration details of UXPB
artefacts. Information given in this document is subject to change for each
release]

7.1 App Container Configuration

1. Unzip the Transact App preimage kit zip file.

2. Navigate to ${EXTRACT_DIR}/app. Unpack your Transact archive that you
received from distribution in the app directory.
3. Your unpacked archive should have several directories including "t24lib"
and "UD". These should be directly placed in the "app" directory.
4. If your archive has a different structure, you need to move the t24lib
directory and other directories into the ${EXTRACT_DIR}/app directory.
5. Deployment of EJB jar provide interface list of rp and catalog services
available in T24. Ensure the OFS_SOURCE as well as the security domain
related configuration in these jars.
6. Modify the t24-EB_CatalogService-ejb.jar that you received from
distribution. Navigate to META-INF/ and open ejb-jar.xml. Use either
“IRISPA/IFPA” or any pre-authenticated OFS_SOURCE.

7. Modify the transaction type from Container to Bean.

8. Open jboss-ejb3.xml and ensure the security domain is set as other as

defined in WildFly security domain.

15
Transact TAFJ Cloud Native Version Delivery Note

9. Ensure that the above configurations are made in t24-

EB_ResourceProviderService-ejb.jar and t24-
EB_AuthenticationService-ejb.jars.
10. Place the modified t24-EB_CatalogService-ejb.jar, t24-
EB_ResourceProviderService-ejb.jar and t24-
EB_AuthenticationService-ejb.jar in the deployments_extras directory.
11. Modify the irf-t24catalog-services.war that you received from distribution.
Navigate to WEB-INF/classes and open connection.properties.
 The default transportLayerUser and transportLayerCredential is
(SSOUSER1/123456). Verify this user exists in Transact.
 If you wish to change the default transportLayerUser &
transportLayerCredential then follow Transact guidelines to create
a new user similar to SSOUSER1 and update the
connection.properties file.
 To authenticate the services you need a WildFly application user for
the Transact user added to the t24user role. The user creation is
done automatically by passing the user credentials as environment
variables APP_USER & APP_PWD respectively while deploying the
app yaml.

 Modify the RemoteConnectionPorts to point to the WildFly port.

12. Ensure that the above configurations are made in irf-rp-services.war.
13. Place the modified irf-t24catalog-services.war and irf-rp-services.war in
the deployments_extras directory.
14. Place the Authenticator.war that you received from distribution in the
deployments_extras directory.

16
Transact TAFJ Cloud Native Version Delivery Note

15. Modify the ResourceServer.war that you received from distribution.

Navigate to WEB-INF/lib and add the drivers specific to your database. The
H2 driver is present by default.
16. Place the modified ResourceServer.war in the deployments_extras
directory.
17. Modify the RSDefaultProperties file that you received from distribution. Set
the below properties

 resource.server.options.tenant.jdbc.url.1 - Database URL. This DB

can either be the T24 database or any existing database. If the
database is H2 you can provide a new DB name which gets created
dynamically on deployment of ResourceServer war.
 resource.server.options.tenant.jdbc.username.1 – Database
username
 resource.server.options.tenant.jdbc.password.1 - Database
password encrypted using Encryption Utility received from
Distribution. The below screenshot shows the encryption value for
‘t24’.

 Based on the database that you use, supply these property values
[Note: Refer to product documentation for configuration details as they are subject to
change for each release]
SQL
resource.server.options.tenant.jdbc.driver.1=com.microsoft.sqlserver.j
dbc.SQLServerDriver
resource.server.options.tenant.ddl.blobType.1=varbinary(max)
resource.server.options.tenant.ddl.longType.1=bigint

17
Transact TAFJ Cloud Native Version Delivery Note

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

18
Transact TAFJ Cloud Native Version Delivery Note

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

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

18. Place the modified RSDefaultProperties file in the ${EXTRACT_DIR}/prop

directory.
19. Build a docker image from this preimage kit which creates a new container
image.
For example:

$ unzip ${DOWNLOAD_DIR}/preimage-transact-app-sql-R20.x.x.zip
$ docker build -t transact-app-sql:R20.x preimage-transact-app-sql-R20.x.x

Using base Image, the build options are as below.

If the base image is in a repository user need to pass the build arguments BASE_REPO
and BASE_TAG. Example below
docker build -t transact-app-sql:Rnn.x --build-arg
BASE_REPO="artifactory.shs.saas.temenos.cloud/temenosbaseimages/" --build-arg
BASE_TAG="Rnn" preimage-transact-app-sql-Rnn.x

In the above example the repo "artifactory.shs.saas.temenos.cloud/temenosbaseimages/"

would contain “temnubi9wf26jdk11” with a tag “Rnn”

If the base image is built locally, user need to pass the BASE_REPO argument as null
and BASE_TAG with the value used to build the base image. Example below

docker build -t transact-app-sql:Rnn.x --build-arg BASE_REPO="" --build-arg

BASE_TAG="Rnn" preimage-transact-app-sql-Rnn.x

Result: The Dockerfile in the Image Kit will consume the jar files placed in
the app/t24lib directory and drops it into the WildFly modules directory.
module.xml for T24 module is generated for all the jars in the app folder.
17. Push the new app container image to your Container Registry.

7.2 Web Container Configuration

1. Unzip the Transact Web preimage kit zip file.
2. Modify the Browser.war that you received from distribution. Navigate to
19
Transact TAFJ Cloud Native Version Delivery Note
WEB-INF/ and open SSOAPI.properties.
3. Modify the SSOAPI.T24REMOTE.URL. Replace the IP and port to app-
dns.kube.private.dns.com.

4. Place the modified Browser.war in the

${EXTRACT_DIR}/deployments_extras directory.
5. Modify the BRPRuntimeProperties file that you received from distribution.
Replace the IP and port to app-dns.kube.private.dns.com.

20
Transact TAFJ Cloud Native Version Delivery Note

6. Set the below properties.

 browser.options.irisSystemUser – Transact username.
 browser.options.irisSystemPassword – Transact user’s password
encrypted using Encryption Utility received from Distribution.

7. Place the modified BRPRuntimeProperties file in the

${EXTRACT_DIR}/prop directory.
8. Build a docker image from this preimage kit which creates a new container
image with Browser.
For example:

$ unzip ${DOWNLOAD_DIR}/preimage-transact-web-R20.x.zip
$ docker build -t transact-web:R20.x app preimage-transact-web-R20.x

Using base Image the build options are as below.

If the base image is in a repository user need to pass the build arguments BASE_REPO
and BASE_TAG. Example below
docker build -t transact-web:Rnn.x --build-arg
BASE_REPO="artifactory.shs.saas.temenos.cloud/temenosbaseimages/" --build-arg
BASE_TAG="Rnn" preimage-transact-web-Rnn.x

In the above example the repo "artifactory.shs.saas.temenos.cloud/temenosbaseimages/"

would contain “temnubi9wf26jdk11” with a tag “Rnn”

If the base image is built locally, user need to pass the BASE_REPO argument as null
and BASE_TAG with the value used to build the base image. Example below

docker build -t transact-web:Rnn.x --build-arg BASE_REPO="" --build-arg

BASE_TAG="Rnn" preimage-transact-web-Rnn.x

9. Push the new web container image to your Container Registry.

21
Transact TAFJ Cloud Native Version Delivery Note

8. App & Batch Pod Separation

From 202110 release of pre-image-kit for app and batch pod segregation there has been changes
made in TAFJJEE_EAR.ear. Using the switch added to the TAFJJEE_EAR.ear, Online traffic is
not routed to the batch pod, while at the same time, one image can be used for both app and
batch containers. .
Changes were made for the Pre-image-kit App build to modify the file TAFJJEE_EAR.ear\
TAFJJEE_MDB.jar\META-INF\jboss-ejb3.xml
to user environment variables OLTP_ACTIVE and SERVICE_ACTIVE so that there will be clear
segregation of traffic depending on the operation performed. Sample snippet below

<d:delivery>
<ejb-name>OFSTransactedMDB</ejb-name>
<d:active>${env.OLTP_ACTIVE}</d:active>
</d:delivery>
<d:delivery>
<ejb-name>BROWSERTransactedMDB</ejb-name>
<d:active>${env.OLTP_ACTIVE}</d:active>
</d:delivery>
…
…
…
…
<d:delivery>
<ejb-name>TAFJPhantomListenerMDB</ejb-name>
<d:active>${env.SERVICE_ACTIVE}</d:active>
</d:delivery>
<d:delivery>
<ejb-name>TafjManagementListener</ejb-name>
<d:active>${env.SERVICE_ACTIVE}</d:active>
</d:delivery>

22
Transact TAFJ Cloud Native Version Delivery Note
The changed TAFJJEE_EAR.ear file will be in the deployment_extras folder of pre-image-kit for
Transact app.
If the user is building the docker image with the modified TAFJEE_EAR.ear for their deployment,
then the recommendation would be to set pass this as environment variable during deployment.
An example of deployment using helm chart below
On the app deployment in values.yaml we set the below

OLTP_ACTIVE: "true"
SERVICE_ACTIVE: "false"

On the batch deployment in values.yaml we set the below

OLTP_ACTIVE: "false"

SERVICE_ACTIVE: "true"

23