Sie sind auf Seite 1von 14

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.


R19 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_R19_Release_Notes

3
TAFJ Team Technology
TAFJ_R19_Release_Notes

Table of Contents

1
Table of Contents 2
Document History 4
IMPORTANT RELEASE INFORMATION 5
Release Highlights................................................................................................................................... 5
Configuration Enhancement................................................................................................................. 5
Database Enhancements..................................................................................................................... 5
NuoDB Support.................................................................................................................................... 5
Multi-column support............................................................................................................................ 5
Locking................................................................................................................................................. 6
DBTools............................................................................................................................................... 6
Dictionary Cache.................................................................................................................................. 6
TAFJEE Enhancements....................................................................................................................... 6
TAFJConfigurationWeb........................................................................................................................ 6
TAFJRestServices................................................................................................................................ 7
Sanity check......................................................................................................................................... 7
Execute servlet..................................................................................................................................... 7
Runtime Enhancements....................................................................................................................... 7
Multitenant............................................................................................................................................ 7
Message Integrity component.............................................................................................................. 7
Warm Up.............................................................................................................................................. 7
Breaking change 8
201502..................................................................................................................................................... 8
201612..................................................................................................................................................... 8
Webservices components:................................................................................................................... 8
TAFJEE client:...................................................................................................................................... 8
201606..................................................................................................................................................... 9
201607..................................................................................................................................................... 9
201708..................................................................................................................................................... 9
201710..................................................................................................................................................... 9
201712..................................................................................................................................................... 9
201801................................................................................................................................................... 10
201808................................................................................................................................................... 10
201809................................................................................................................................................... 10
201902................................................................................................................................................... 10

4
TAFJ Team Technology
TAFJ_R19_Release_Notes

201904 (R19 AMR)................................................................................................................................ 10


System Component Requirements 11
INSTALLATION OF THE SOFTWARE12
Upgrading TAFJ..................................................................................................................................... 12
Upgrade Summary............................................................................................................................. 12
Upgrading T24 on TAFJ......................................................................................................................... 12
Upgrade Summary............................................................................................................................. 12

5
TAFJ Team Technology
TAFJ_R19_Release_Notes

Document History

Author Version Date

H. Aubert 201904 23 March 2019

Comments:

R19 AMR notes + new template

6
TAFJ Team Technology
TAFJ_R19_Release_Notes

IMPORTANT RELEASE INFORMATION


This section outlines new features in TAFJ R18 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
components which have been replaced, deprecated or modified.

Configuration Enhancement
Properties, usually stored in the TAFJ properties file, can now be stored at database level in a technical
table named “TAFJ_CONFIGURATION”. This table is automatically created on first use if it doesn’t
already exist.
The configuration service is making use of the same datasource than the one use for T24. No additional
setup is required from end user perspective. This mode is not available for standalone application.
To switch from a configuration stored on disk in the properties file, to a database configuration, the
system property ‘tafj.configuration’ has to be set at application start up. ‘tafj.configuration’ value
represents the configuration name (or configuration ID).
e.g.
-Dtafj.configuration=production

If the configuration identified by the ID ‘production’ doesn’t exist in the TAFJ_CONFIGURATION


configuration table, it will be automatically created by the configuration service. It can then be refine
through the properties management console in TAFJEE. Same as when using properties file, when
making change to a configuration, the application needs to be restarted.
Not making use of system property ‘tafj.configuration’ means using the properties file and unchanged
behaviour.
Refer to TAFJ setup and TAFJ As for more details.

Database Enhancements

NuoDB Support
TAFJ support for transact (T24). The Transact(T24) Dataset can be store in the storage manager of
NuoDB. The pesistant layer of TAFJ can connect to Transaction engine of NuoDB.

Multi-column support
For tables needing super-fast indexing, a table can be turned into a pseudo-relational table where multi-
values are stored in NVARCHAR columns.  While this approach provides worse performance in terms of

7
TAFJ Team Technology
TAFJ_R19_Release_Notes

reads due to the fact a dynamic array needs to be constructed out of all of the columns, it will provide
better indexing speed for single-value columns.

Locking
Now there is a hybrid locking mechanism implemented such that some locks can be taken at the
database by row locking.  Non-existant locks (locks on records that do not exist yet) are still locked by a
secondary lock manager.  For example, to set up database row level locking with ORCL locking handling
the non-existant records, the following properties would be set.

temn.tafj.locking.mode= DATABASE
temn.tafj.jdbc.db.locking.secondary.lockmanager = ORCL

DBTools
DBTools is now secured, you need to define user and password to be able to login into DBTools. Refer to
DBTools documentation for more details.
All DBTools actions are also being logged to keep trace of command used and user.

Dictionary Cache
Dictionary entries can now be cached by setting the key
temn.tafj.runtime.use.cache.dict.item=true
Note that this should be used in single server mode only.  Cluster configurations and multi-node server
configurations coming next year.
Documentation
A run book is now available covering T24 java configuration for all supported stack.
IDE, Variable Initialisation Check
Variable initialisation is enforced when using the IDE. Non initialised variables will be considered as a
compilation error. Option can (but should not) be turned off in the IDE.

TAFJEE Enhancements

TAFJConfigurationWeb
A new web application is available to manage Database stored configurations.
It is made of 2 components:
JSF - GUI based application to manage the current Database runtime configuration, to edit, add and
delete properties.
REST based API (JAXRS) to interact with the configuration service and manage Database configurations:
creation, copy, edition etc…
Refer to TAFJ AS documentation for more details.

8
TAFJ Team Technology
TAFJ_R19_Release_Notes

TAFJRestServices
A new JAX-RS based webservice component is available in TAFJJEE_EAR, it is intended to replace
former Axis2 based webservice component.
This new component could be secured through basic authentication and related TAFJJEE client is now
accepting user / password parameters. Refer to TAFJ AS documentation for more details.

Sanity check
A sanity check is available through TAFJEE servlet, this tool runs a validation of the application server
configuration by comparing what is expected at application level (TAFJEE) and what is effectively
configured at application server level in terms of resources and parameters. Refer to TAFJ AS
documentation for more details.

Execute servlet
Messages / actions posted to the EXEC queue for processing are being logged and reported to the
Execute servlet page. A notification is also reported on action completion.
It allows following tSA / command history and status.
T24 Features

LOGOFF has been fixed to time out tSA exceeding T24 time out value.

Runtime Enhancements

Multitenant
TAFJ is now fully multitenant. TAFJ can connect to multiple database (multitenant) with separate
properties. All entries points (API) need a TenantID. For Back compatibility, if TAFJ is not set in
Multitenant mode, the TenandID will be ignored.

Message Integrity component.


TAFJ deliver a component who is managing KeyStore on the file System or in the database and provide a
JBC and Java API for sign/verify a key.

Warm Up.
TAFJ have the capability at the start up to warm up the system calling JF.INITIALIZE to speed up the first
transaction for each channel
Queues functionality for Services.
TAFJ integrate 8 new function for TRANSACT for Elastic scale of Online Bachkground processing.

9
TAFJ Team Technology
TAFJ_R19_Release_Notes

Breaking change

201502
A new property is available at MDB level to configure the time to live for the responses sent.
Default behaviour is unchanged, time to live is unlimited, and doesn’t require any change.
To have a response expiration the following property has to be added at ejb-jar.xml level for the related
MDB.
<env-entry>
<description>the response time to live in milliseconds from its dispatch timdefault is zero is unlimited</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/responseTimeToLive</env-entry-name>
<env-entry-type>java.lang.Long</env-entry-type>
<env-entry-value>10000</env-entry-value>
</env-entry>

Refer to TAFJ-AS documentation for detailed explanation.

201612
Webservices components:
TAFJServices.war, axis2 based webservices component is deprecated. TAFJRestServices.war, JAX-RS
based webservices component is replacing it.
For back compatibility reason, both archives are packaged in TAFJJEE_EAR until R17-AMR and
TAFJServices.war removal.
Refer to TAFJ-AS documentation for more details.

TAFJEE client:
TAFJJEE client classes, e.g. TAFJJEEClientFactory, part of TAFJClient.jar have been re-factored to
match the new JEE services available, JAX-RS webservices, Websocket endpoint etc…

Client applications should migrate to make only use of classes which are part of
package com.temenos.tafj.jee.client;

instead of formerly
package com.temenos.tafj.j2ee.client.impl;
package com.temenos.tafj.j2ee.client.impl;

10
TAFJ Team Technology
TAFJ_R19_Release_Notes

201606
TAFJ is using SLF4J as logging API and is shipped with a default logger configuration for log4j
(TAFJTrace.properties).
This won’t make any difference from end user perspective since SLF4J-API and SLF4J-LOG4J12 are
part of the application classpath.
These libraries are part of standard TAFJ_HOME/lib distribution.
For application server setup, please refer to the related TAFJ documentation.

201607
Following above mentioned 201606 migrations to SLF4J logging API, the class loading setup required in
weblogic stack might be a concern for some.
Hence 201607 gives the ability to use either SLF4J or log4j2 as the main logging API.
The default API being used is now log4j2 with a provided default logger configuration,
TAFJTrace.properties. Log4j 2 properties format is not compatible with former log4j 1.2 configuration.
When upgrading to 201607, existing TAFJTrace.properties will be overridden to match log4j2
requirement.
Log4j2 libraries are part of standard TAFJ_HOME/lib distribution, SLF4J libraries introduced in 201606
have been removed of the default lib directory.
For application server setup, please refer to the related TAFJ documentation.
To preserve backward compatibility please note this is still well possible to keep using former log4j 1.2
setup but this is not recommended as further logging enhancements are not going to be supported when
using log4j 1.2.
It could be either behind SLF4J as in 201606 or natively with little configuration change.
See TAFJ standalone documentation for more details.

201708
 Numeric comparisons on Multi-value numeric fields is handled. A new parameter to indicate the
field type is added at the 5th position of tafjexistsCol(), tafjexistsColClob() and tafjexistsColBlob()
functions. This parameter is set to 1 for numeric type field and 0 for string type field.

 The functions should be properly reloaded for the changes to get reflected.
o Refer to the documents TAFJ-H2Install.pdf, TAFJ-MSSQLInstall.pdf, TAFJ-Oracle Install
12c.pdf, TAFJ-DB2 Install.pdf to reload the functions in the respective database.

201710
 TAFJRestServices GET request support is removed.

11
TAFJ Team Technology
TAFJ_R19_Release_Notes

201712
 Adding Stored Functions tafjsplice, tafjupcase and tafjlowcase. These functions are now
supported

201801
 Database stored configuration. Properties file is still available but properties can be stored in
database (does not apply to standalone mode).

201808
 Native lock

201809
 Deployment of TAFJSpoolerPlugins.rar is mandatory.
 Addition of the following queues,
o SWF [t24SWFQueue, t24SWFReplyQueue]
o AAINT [t24AAIntQueue, t24AAIntReplyQueue]
o AAEXT [t24AAExtQueue, t24AAExtReplyQueue]

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

12
TAFJ Team Technology
TAFJ_R19_Release_Notes

System Component Requirements


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

Component Release JDK

Temenos Application Framework Java R19 Supported JDK


TAFJ JDK 1.8.x

Application Server Version

WebSphere 9.x.x

WebLogic 12c (12.2.x)

jBoss 7.1.x EAP

DataBase Server Version

DB2 DB2 v11.1 / DB2 v10 zOS

Oracle 12c

MS-SQL 2015

NuoDB 3.4.x

Broker (JMS) Server Version

WebSphere MQ 8.x / 9.x

13
TAFJ Team Technology
TAFJ_R19_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.

14
TAFJ Team Technology

Das könnte Ihnen auch gefallen