Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,

for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2018 Temenos Headquarters SA - all rights reserved.

R21 Release
Temenos Application Framework Java (TAFJ)
Release Notes

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,

for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2018 Temenos Headquarters SA - all rights reserved.

TAFJ_R21_Release_Notes

Table of Contents

Table of Contents 2
Document History 3
IMPORTANT RELEASE INFORMATION 4
Release Highlights................................................................................................................................... 4
PostgreSQL JSONB support................................................................................................................ 4
Breaking change 5
201902..................................................................................................................................................... 5
201904 (R19 AMR).................................................................................................................................. 5
201910..................................................................................................................................................... 5
System Component Requirements 8
INSTALLATION OF THE SOFTWARE9
Upgrading TAFJ....................................................................................................................................... 9
Upgrade Summary............................................................................................................................... 9
Upgrading T24 on TAFJ........................................................................................................................... 9
Upgrade Summary............................................................................................................................... 9

3 TAFJ Team Technology

TAFJ_R21_Release_Notes

Document History

Author Version Date

JN. Charpin 202004 24 March 2020

M. Kumar 202104 12th April 2021

Comments:

R21 AMR notes

4 TAFJ Team Technology

TAFJ_R21_Release_Notes

IMPORTANT RELEASE INFORMATION

This section outlines new features in TAFJ R21 and contains important information for upgrading clients.
If you are upgrading from an earlier release of TAFJ, please read and understand all the release
information details for each release before starting the installation.

Release Highlights
This section provides an overview of any new TAFJ components or features and advice regarding any
component, which have been replaced, deprecated or modified.

PostgreSQL JSONB support

PostgreSQL is a powerful, open source object-relational database system with over 30 years of active
development that has earned it a strong reputation for reliability, feature robustness, and performance.
TAFJ has extended support for PostgreSQL database to deploy and run T24-Transact starting R20AMR
release. This includes the famous move from java stored procedures functions loading to native
PL/PGSQL function support inside the database for better performance.

Refer to TAFJ-PostgresSQLInstall documentation for more details.

5 TAFJ Team Technology

TAFJ_R21_Release_Notes

Breaking change
201902
 Addition of the following queues,
 TPS Instant In Queues [t24TPSInstInQueue, t24TPSInstInReplyQueue]
 IRISINT [t24IRISIntQueue, t24IRISIntReplyQueue]
 IRISEXT [t24IRISExtQueue, t24IRISExtReplyQueue]
 Management Topic [t24ManagementTopic]

201904 (R19 AMR)

 Multitenant support
 Message Integrity
 Transact Service using queues (Table in RDBMS)
 Warm up

201910
 New TAFJEE Micro EE component see related documentation in TAFJ-AS and TAFJ-MicroEE
documentation provided within the release.
 Some components have been renamed in TAFJEE_EAR file:
o TAFJJEE_WAR_TAFJ.war becomes TAFJEE.war
o TAFJConfigurationWeb.war becomes TAFJConfiguration.war
o Java melody configuration is moved from TAFJJEE_WAR_TAFJ/WEB-INF/web.xml to
TAFJJEEMonitoring.war/WEB-INF/web.xml

202101
A new folder has been introduced part of the TAFJHome directory structure called
libMonitor
This is in sync with the monitoring solution delivered involving common components
The change includes an updated T24Setup.cli script part of the TAFJHome\appserver\
jboss\jboss7eap\jboss-cli folder
Execute this script to generate a new standalone.xml for the new module reference

Breaking change

EJBs and MDBs configuration within TAFJEE_EAR, ejb-jar.xml deployment descriptors is unified and
follow same model.
Please refer to TAFJ-AS TAFJ documentation for the comprehensive list of properties.
e.g.
Former configuration model, some properties were prefixed with the ejb class.

<env-entry>
<description>OFS OFS Source</description>

6 TAFJ Team Technology

TAFJ_R21_Release_Notes

<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsSource</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>GCS</env-entry-value>
</env-entry>

Is changed to new configuration model with no property prefix.

<env-entry>
<description>OFS OFS Source</description>
<env-entry-name>ofsSource</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>GCS</env-entry-value>
</env-entry>

The following properties have also been renamed besides the prefix removal.

<env-entry-name>com.temenos.tafj.mdb.PhantomListener/jTATimeout</env-entry-
name>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/jTATimeout </env-entry-
name>
<env-entry-name>com.temenos.tafj.sb.TRunProcessingBean jTATimeout </env-entry-
name>
<env-entry-name>jtaTimeout</env-entry-name>

<env-entry-name>com.temenos.tafj.mdb.PhantomListener/jTA</env-entry-name>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/jTA</env-entry-name>
<env-entry-name>com.temenos.tafj.sb.TRunProcessingBean/jTA</env-entry-name>
<env-entry-name>isJTA</env-entry-name>

It is now possible to override EJBs and MDBs environment entries configuration without having to change
the ejb-jar.xml deployment descriptors.
It can be done through any TAFJ configuration property source: System property, environment variable or
tafj property.
To be able to inject the configuration within the appropriate EJB / MDB a service classifier is used.
Except for online processing where the classifier can be defined at ejb-jar level through property
channelName, other classifier are fixed.

Service type EJB Service name

Online processing OFSProcessingBean / channelName=ejb prefix to

7 TAFJ Team Technology

TAFJ_R21_Release_Notes

CallAtProcessingBean lowercase

Phantom processing PhantomListener phantom

tRun processing TRunProcessingBean trun

Management activities TAFJManagementBean management

e.g. to set the property ofsSource to the EJB OFSProcessingBean and the ignoreRedeliveredMessage to
the MDB OFSTransactedMDB.

Given the channelName property defined for the MDB and EJB
<message-driven>
<display-name>Transacted Listener MDB for OFS</display-name>
<ejb-name>OFSTransactedMDB</ejb-name>
<ejb-class>com.temenos.tafj.mdb.TransactedMDB</ejb-class>
..
<env-entry>
<description>service name for property injection set by default to EJB prefix to
lower case</description>
<env-entry-name>channelName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ofs</env-entry-value>
</env-entry>

<enterprise-beans>
<!-- T24 Processing EJBs -->
<session>
<!-- Bean for OFS request processing used by TransactedBean -->
<description>TAFJ OFS Bean</description>
<display-name>TAFJ OFS Bean</display-name>
<ejb-name>OFSProcessingBean</ejb-name>
…
<env-entry>
<description>service name for property injection set by default to EJB prefix to
lower case</description>
<env-entry-name>channelName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ofs</env-entry-value>
</env-entry>

It is possible to override the ejb-jar.xml OFSProcessingBean and OFSTransactedMDB configuration by

setting in the configuration:
ofs.ofsSource=GCS.OVERRIDE
ofs.ignoreRedeliveredMessage=false

8 TAFJ Team Technology

TAFJ_R21_Release_Notes

System Component Requirements

The following table shows the minimum recommended Temenos components and release numbers,
which is designed to run with TAFJ.

Component Release JDK

Temenos Application Framework Java R21 Supported JDK

TAFJ JDK 1.8.x

Application Server Version

WebSphere 9.x.x

WebLogic 12c (12.2.x)

jBoss 7.x EAP

DataBase Server Version

DB2 DB2 v11.1 / DB2 v10 zOS

Oracle 12c

MS-SQL 2017

NuoDB 4.x

PostgreSQL 13.x

Broker (JMS) Server Version

WebSphere MQ 8.x / 9.x

9 TAFJ Team Technology

TAFJ_R21_Release_Notes

INSTALLATION OF THE SOFTWARE

Transfer the archive to the target machine and unzip the archive to a suitable directory.
Execute the scripts Setup_TAFJ.Rxx_Y.

Upgrading TAFJ
If you have an earlier version of TAFJ installed you should stop all TAFJ processes, services, and save
any system configuration files before proceeding with the installation of TAFJ.

Upgrade Summary
Transfer the archive to the target machine and unzip the archive to a suitable directory.
Setup environment variable JAVA_HOME to path where java is installed.
Setup environment variable TAFJ_HOME to path where TAFJ is already installed.
Setup environment variable ECLIPSE_HOME to the folder %TAFJ_HOME%\eclipse
Execute Patch_TAFJ.Rxx_Y.

Upgrading T24 on TAFJ

If you have an earlier version of T24 on TAFJ installed you should stop all TAFJ processes, services, and
save any system configuration files before proceeding with the installation of TAFJ.

Upgrade Summary
From DBTools under TAFJ_HOME/bin execute the TEMP-RELEASE option with valid parameters as
below.
Ex: DBTools - TEMP.RELEASE <path_to_temp_release> <path_to_precompiled> -bp
{path_to_BP_folder} -i {path_to_inserts_folder}
Where in –bp and –i are option parameters.
Check that the TEMP.RELEASE is pointing to the correct upgrade path under
SYSTEM>TEMP.RELEASE file.
Run T24.PRE.RELEASE(logout and login with a new session)

You are now ready to follow any pre-release procedures described below:
 Respond to the Model Bank question appropriately.
 Provide a USER id as requested.
 Once this is complete you are ready to sign on to T24 to initiate the upgrade service.
 Start the TSA.SERVICE record BNK/T24.UPGRADE.
 Authorise any CONVERSION.PGMS records.
 Initiate the service RUN.CONVERSION (TSM must also be run)
 Recompile any local code (New inserts provided by the release and or TAFJ upgrades require
this)
 Once this is finished the record review and authorisation process can start.

10 TAFJ Team Technology