R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

You are here: R13 Documentation > Pre-Release Information

1 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

R13 Release Notes

2 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

PRE-RELEASE INFORMATION

Important Information
This section outlines actions that must be made BEFORE installing a T24 Server release. If you are upgrading by two or more releases, then read and
understand all the release information details for each release before starting the installation.

R11 T24 Release Notes

R12 T24 Release Notes

The T24 Technical Highlights documentation should also be referenced. This will highlight any changes of a technical nature that may impact local
development.

R11 Technical Highlights

R12 Technical Highlights

Please read this entire document before commencing on any of the steps in the upgrade.

Upgrade and Conversion Services

From R09, RUN.CONVERSION.PGMS is no longer allowed. You must now use the TSA.SERVICE process RUN.CONVERSION.

The following changes have been done from R10;

Upgrades and installation of a new product should use the TSA.SERVICE process T24.UPGRADE.
Service packs and patches have been replaced with the new customer Updates functionality.

Please refer to the T24 Updates User Guide for more details.

3 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

New Products
Product Code Name Description

SF SWIFT
The SF module is required for
Swift messages to be formatted
during delivery.

IN IBAN
The IBAN module enables a
Bank to generate and validate
the International Bank Account
Number format. IBAN is an
internationally agreed means of
identifying bank accounts across
national borders, which has
been implemented by most
European and many other
countries.

VS Straight Through The VS module enables Banks to

Processing process SWIFT messages for
straight through processing
purposes. It converts
non-standard tag values in
messages to SWIFT standards,
thereby enabling faster
processing of SWIFT messages
and reduces the amount of
human intervention required.

VP AML Profile The VP module enables a Bank

to do offline profiling of
Customer operations. AML
profile periodically collects data
about transactions, customers,
accounts and analyses the data
for different patterns that are
considered suspicious.

VL AML Screen The VL module provides a

comprehensive customer and
transaction screening solution in
real time for Anti Money
Laundering compliance.

FA FATCA The FA module addresses Phase

I of the FATCA regulation, which
mandates Identification of US
accounts across borders.

RC Transaction Recycler The RC module enables a Bank

to create pre-defined sets of
rules which capture
transactions, so that they are
automatically retried at
pre-determined intervals for a
specific period of time.

System Component Requirements

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

T24 Release Requirements

Component

ARC IB R13.000 I.E. 7, Firefox 2, Apple Safari, Google Chrome,

Opera version 5.0

Browser R13.000 I.E. 7, Firefox 2

4 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

Toolbox R13.000 Windows 2000, XP and VISTA

Desktop (VB6) 1.7.437 Windows 2000, XP and VISTA

Temenos R13.000 Operating systems:

Application
Framework C - Windows Server 2008 64-bit
Version TAFC
- RedHat Enterprise Linux 5

- RedHat Enterprise Linux 6

- AIX v6.1

- AIX v7.1

- Solaris 10 SPARC

- Solaris 10 x86-64

- Solaris 11 SPARC

- Solaris 11 x86-64

- HP-UX Itanium2 11.31 V3

Oracle Direct R13.000 Minimum ORACLE 11gR1

Connect
Recommended ORACLE 11gR2

DB2 Direct R13.000 Minimum Version 9.7/PureScale 9.8

Connect
Recommended DB2 V10

MSSQL Direct R13.000 Minimum SQL Server 2008 R2

Connect
Recommended SQL 2012

TWS (EE) R13.000 plugin:

(developer tool) com.temenos.tws.plugin-1.0.0.201304221137-

R13.jar

Temenos dependencies:

- T24 WS product

Supported Eclipse IDEs (with JDK 1.6)

- 3.5 (Galileo)

- 3.6 (Helios)

- 3.7 (Indigo)

R13.000
TWS-WAR Supported application servers:

(deployed web - JBoss 4.2.3GA, 5.1.0GA

service )
- WebSphere 7 *

- WebLogic 10.3 and 11g

5 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

TWS-Project R13.000 Installer

Template
TWS(.NET)InstallKit_VS2010_13.0.0.0.zip
(developer tool)
.NET Framework:

- .NET Framework 4.0 (CLR v4.0.30319) or higher

Temenos dependencies

- T24 WS product R13

- TOCF(EE)

-TAFC

Supported IDEs for .net

- Visual Studio 2010

R13.000
TWS-WCF Supported application servers:
Project
IIS 5.1 & above
(deployed
project)

Integration R13.000
Studio(EE) plugin:

com.temenos.integration.plugin-
1.0.0.201304221627-R13.jar

Temenos dependencies:

- T24 IF product

- TOCF(EE)

Supported IDEs on java(with JDK 1.6)

- Eclipse 3.5 (Galileo)

- Eclipse 3.6 (Helios)

- Eclipse 3.7 (Indigo)

Integration R13.000
Studio(.net) .NET Framework:

- .NET Framework 4.0 (CLR v4.0.30319) or higher

Temenos dependencies:

- T24 IF product

Supported IDEs on .net

- Visual Studio 2010

Temenos Open R13.000 Supported Application servers:

Connectivity
Framework TOCF - JBoss 4.2.3GA, 5.1.0GA
(EE)
- WebSphere 7

- WebLogic 10.3 and 11g

Temenos Open R13 000 .NET Framework:

Connectivity
Framework - .NET Framework 4.0 (CLR v4.0.30319) or higher

TOCF(.NET)

6 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

T24 Monitor R13.000

Temenos dependencies:

TAFC R13 GA & TOCF(EE) R13 GA

TAFJ R13 GA

Supported application servers:

- JBoss 4.2.3GA, 5.1

- WebSphere 7

Java:

JRE 1.6 required

CBE Adapter R13.000 Temenos dependencies:

- T24 BM product

Supported application servers:

- JBoss 4.2.3GA, 5.1.0GA

- WebSphere 7

- WebLogic 10.3 and 11g

Java:

JRE 1.6 required

Temenos BizTalk R13.000 .NET Framework:

Custom Adapter
- .NET Framework 4.0 (CLR v4.0.30319) or higher

BizTalk:

- WCF LOB Adapter SDK 2010

- BizTalk Server 2010 (optional)

Supported IDEs on .net

- Visual Studio 2010

Temenos dependencies:

- T24 IF product R13

- T24 WS product R13

-TAFC R13

Temenos Fiorano R13.000

Custom Adapter Fiorano:

Fiorano 9.4.2

Temenos dependencies:

- T24 IF product R13

- T24 WS product R13

7 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

tOP (t24 R13.000

Operation Splunk:
Performance
Monitor) -Splunk for Windows 5.0.1 or later

-Splunk for UNIX 5.0.1 or later

Others:

-Sideview util for splunk

OS for Server:

-CentOS 5, 6 x86, x64

-Other Linux x86, x84

-Windows 2008 R2 x86 & x64,Windows 2008 x86

& x64,Windows 2003 x86 & x64, Windows 7 x86 &
x64

- MacOSX 10.6 x64, Other MacOSX

OS for SplunkWeb client:

-Windows 7 x64, Other Windows x86 or x64

-MacOSX 10.6 x64, Other MacOSX

Browsers:

-IE 7, 8, 9 or 10

-Firefox 3

-Google Chrome

-Safari 5

Insight Risk R13.000

Temenos Dependencies:

-T24 with DW export

Server:

-Windows Server 2003 Enterprise Edition or later

-.Net Framework 3.5

-Internet Information Services 6.0 or later

-MS SQL Server 2008 Enterprise Edition or higher

(with latest SP installed)

-MS SQL Server Reporting Services (SSRS) 2008

(component of SQL Server)

-Internet Explorer 7.0 or later

Client:

-Windows XP or later

-Internet Explorer 7.0 or later

*refer note on application servers

The table below lists the supported compilers for TAFC

Platform Compiler version

AIX v6.1 IBM XL C/C++ v9.0.0.15

AIX v7 IBM XL C/C++ v11.1.0.7

Windows Server 2008 Microsoft Visual Studio 2010 SP1

Redhat Enterprise Linux 5 gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-54)

8 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

Redhat Enterprise Linux 6 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)

HP Itanium2 11.31 V3 HP C/aCC++ B3910B A.06.22

Solaris 10 SPARC Solaris Studio 12.3

Solaris 10 x86-64 Solaris Studio 12.3

Solaris 11 SPARC Solaris Studio 12.3

Solaris 11 x64 Solaris Studio 12.3

Database Requirements
The database to be upgraded must be at the stage just before a close of business is set to run. Ensure all message queues have been cleared and phantoms
and services are stopped. The system must be in a fully recoverable state. No one should be signed on except the person upgrading.

Once the upgrade process is finished a complete backup or checkpoint should be taken to ensure recoverability.

Disk Space Requirements

When you upgrade a T24 database, the size of the database will increase, especially if you are installing new products. Please ensure you have sufficient
disk space available.

Data Changes
A few applications may still contain field numbers e.g. USER and others may be stored in USER.EXTERNAL.FIELD.Please review these applications
before beginning the upgrade to determine if any corrections to field numbers are required.

Do not make changes until the conversions have been run.

It is important that there are no unauthorised STANDARD.SELECTION records before you take the release and you do not authorise any released
STANDARD.SELECTION records before you run the conversions.

9 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

INSTALLATION OF THE SOFTWARE

Upgrading TAFC
If you have an earlier version of jBASE or TAFC installed you should stop all jBASE/TAFC processes, services, and save any system
configuration files before proceeding with the installation of TAFC.
Amend your .profile

Change the export TAFC_HOME= statement in the .profile file to point to the TAFC_R13 release.

For example,

export TAFC_HOME=/usr/tafcRxx (where your TAFC_R13 resides)

NOTE: Your profile has another environment variable, JBCGLOBALDIR, this should be as follows:

export JBCGLOBALDIR=$TAFC_HOME

NOTE: For installation or upgrade of Direct Connect Drivers (DCD) see separate Installation Guide document.

Upgrading T24
Instructions on the transfer of the release from distribution medium and the actual upgrade process are included in the T24 Installation User Guide.

Upgrade Summary
Check that the TEMP.RELEASE is pointing to the correct upgrade path. For example;
TEMP.RELEASE

001 D

002 /T24/R13_component/temp.release

Run T24.BUILD.LIBRARIES
Logout and login with a new session
Run T24.PRE.RELEASE

You are now ready to follow any pre-release procedures described below :

Respond to the Model Bank question appropriately. If your system is a model bank implementation, then you should respond Y, otherwise N. If
in doubt, contact your account manager.
Provide a USER id as requested.

Once these are complete you are then ready to sign on to T24 to initiate the upgrade service.

Start the TSA.SERVICE records, TSM & T24.UPGRADE. For multi-company setup the T24.UPGRADE id will be prefixed with a company
mnemonic.
Run the service agents until the upgrade is completed.
Authorise any CONVERSION.PGMS records.
Initiate the service RUN.CONVERSION (TSM must also be running still)
Once completed run any specific conversion services specified in the release notes (later in this document).
Recompile any local code (New inserts provided by the release and or TAFC upgrades require this)
Repgens

Once this has finished, the record review and authorisation process can commence.

Additional new products

The installation of a new product must not be done at the same time as a system upgrade.

The preferred procedure is to complete the upgrade first and only then change the SPF and COMPANY records to include the new product. A new
procedure is to update the BATCH record BNK/T24.UPGRADE and populate the new products to be installed in the DATA field.

Please reference the T24 Updates User Guide for more details.

Upgrading Browser / ARC-IB

If upgrading from a previous version of T24 Browser or ARC-IB the following steps should

be taken :-

10 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

Before Upgrading
1. Make a back-up of any altered files. For example :-
channels.xml
browserParameters.xml
custom.js
Any customised skin

After Upgrading
1. After the extract of the new WAR file stop the application/web server.
2. Re-instate the changes to the backed-up files to the released versions.
3. Restart the application/web server.
4. Clear your browsers cache of any old JavaScript files and images. To do this perform the following :-

Internet Explorer

Tools>Internet Options>Browsing History>Delete>Temporary Internet Files>Delete Files

Firefox

Tools>Clear Private Data>Clear Private Data Now

Google Chrome

Seetings>Advanced Settings>Clear Browsing Data>Empty the Cache

Browser features affected in this release are given below;

User Name Masked

User id was masked by default in previous releases of browser. Currently, user name in the login page is visible, i.e., unmasked , as the parameter 'Show
User Name' in browserParameters.xml is set to YES by default. User name maybe masked by changing this parameter to NO.

Single Busy Icon

A single busy icon is shown by default, as the parameter Show Single Busy in browserParameters.xml is set to YES. Multiple icons maybe displayed by
setting this parameter to NO.

Stylesheets
HelpText.css is inlcuded in the following path, ..\deploy\BrowserWeb.war\plaf\style\default. This stylesheet is required to support html based HelpText
. It is not required for standard xml based helptext.

Upgrading TOCF(EE)
1. Save any system configuration files before proceeding with the installation of the TOCF(EE) components.

Pay particular attention to the following:

TOCFplugin-ra.rar tcserver.xml

TOCFListener-ejb.jar ejb-jar.xml

Save any other deployment descriptors or configuration files which might have been modified.

Apply these changes to the deployment descriptors and configuration files which are located inside the new tocfee.ear archive.

2. Uninstall the existing TOCF(EE) components

- tocfee.ear (TOCF(EE) Enterprise Archive)

- tocfT24ra-ra.rar (T24 Resource Adapter) or jremote-ra.rar in case of TOCF(EE) versions prior to R10.1.1

- T24Utility.war

On Weblogic, if necessary remove the T24 RA client libraries from the domains shared library directory:

- <weblogic home>\user_projects\domains\<domain name>\lib\jremote.jar

- <weblogic home>\user_projects\domains\<domain name>\lib\tocfT24ra.jar

Note: To uninstall enterprise components in JBoss, you should stop the application server and delete the artifacts from the deploy directory.

11 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

3. Install the new TOCF(EE) components:

- tocfT24ra-ra.rar

- tocfee.ear

- T24Utility.war

- netty.jar (only required when enabling the inbound listener)

4. Restart the application server.

Upgrading application server Websphere 6.1 to 7

Delete the .xmi deployment descriptor in the TWS Eclipse projects before deploying TWS generated war files on WebSphere 7 .

Application/Module specific upgrade actions

Core - Account Balances

Account balances are moved from ACCOUNT to EB.CONTRACT.BALANCES from R12. When upgrading from a lower release prior to R12, there is a
provision to indicate if the ACCOUNT balances are to be maintained in the account as well as in EB.CONTRACT.BALANCES.

The field RETAIN.AC.BALANCES in the ACCOUNT.PARAMETER controls this. Set this field to either Null or Yes, to maintain the account balances in
the account record. This field is available only during the upgrade.

For new implementing clients, the balances are maintained only at EB.CONTRACT.BALANCES.

ARC Mobile
New database tables are added for the LBS configuration and a new tab named Anonymous appears for tiles configuration; they are included in the
upgrade SQL scripts. A new license file lbsRepository.license enables this functionality. During upgrade, add the new license file to the server and
execute the upgrade SQL script.

12 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

CONVERSION ACTIONS

Overview
This section outlines the conversion related activities to be carried out. Read through the whole chapter thoroughly before starting the conversion
process: you may be required to get information or data prior to starting the conversions.

Data, except where this document specifically states, must not be input, amended, or authorised until all the conversion routines have been successfully
completed.

Conversion Routines
Conversion routines are run automatically as part of the upgrade process. However, some conversion programs may need to be executed manually.

Follow the instructions in the System Administration Guide. All CONVERSION.PGMS records must be authorised first. Run conversion routines using
the service RUN.CONVERSION. Do not authorise any STANDARD.SELECTION records before running.

List of conversions to be executed manually;

Conversion Purpose Comments

CONV.SC.SOD.ACCR.R06 To raise entries from the file required for
SC.SOD.ACCR upgrading
from
releases
prior to R5,
if product
SC (ie -
Securities)
is installed

13 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

POST CONVERSION ACTIONS

Authorise Standard Selections

Authorise all STANDARD.SELECTION records for the release.

Authorising / Modifying new and changed records

Record Authorisation
If you have fully complied with the actions detailed in the pre-release information and release notes, you can now authorise all the unauthorised records
in all companies. Check the impact of changes as you authorise each record to prevent any overwriting of local modifications.

Batch Record Authorisation

All BATCH records must be reviewed. You may have local differences from the released records.

Batch records HELD

Some BATCH records may be in HLD status. These records contain information in the data fields that has been modified. You must review these records
to ensure that your local data specifications are not being overwritten.

Batch record LIVE

After initial installation, when running the next COB, the batch record TXN.JOURNAL.SORT must have the value held in FREQUENCY set to Daily.
Subsequent to this the record needs to be amended to set the FREQUENCY to Ad-hoc to reduce the processing overhead.

Should users wish to continue to utilise the existing TRANS.JOURNAL2 report they may do so by reinstating the report in the BATCH EB.PRINT, this
will, however, have an impact in the performance of COB processing.

Sequence of authorisation
Authorise these records in the following applications first because of later dependencies:

STANDARD.SELECTION
ENQUIRY(any % records)
EB.PRODUCT
EB.SYSTEM.ID
SYSTEM.RECORD
VERSION
DE.MESSAGE
TRANSACTION
STMT.NARR.FORMAT
RE.STAT.REPORT.HEAD
RE.STAT.RANGE
EB.MESSAGE.CLASS
EB.ACTIVITY
EB.ADVICES
BROWSER.TOOLS
TSA.WORKLOAD.PROFILE
EB.API
EB.ERROR
OVERRIDE
EB.COMPARISON.TYPE
AA.PROPERTY.CLASS
AA.PRODUCT.LINE
AA.ACTIVITY.CLASS
AA.PROPERTY
AA.PRODUCT.GROUP

14 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

EB.FORMAT.ENTRY
EB.LOOKUP
AA.MAPPING
EB.MAPPING.SOURCE
AA.PERIODIC.ATTRIBUTE.CLASS

Some TSA.SERVICE records may be HLD, as they need a user name entered.

REPGEN recompile
Use REPGEN.SOURCE to recompile all REPGENs or use RUN.REPGENS at the TAFC prompt as described in the user guide.

Application/Module specific Post conversion actions

Payments - Swift messaging

SWIFT is made as a Licensed Product . For Clients upgrading from previous releases, the module needs to be installed immediately after upgrade, to
enable formatting of SWIFT messages.

AA- Pre-notification Advices

Pre-notification activities are instances of core Scheduled activities itself. For the functionality to be used, flag REBUILD.ACTIVITIES field for all
AA.PRODUCT.GROUP entries and authorise them , so that PRE.NOTICE activities are rebuilt in the system.

15 of 16 6/13/17, 8:26 AM
R13 Release Notes file:///E:/From B.Chandy/T24 Lesson/997 ISB/997 ISB/int-usrr13/R13...

Additional Release Notes

Links to the release notes for supporting products are given below.

Business Intelligence
BizTalk Adapter
Fiorano Adapter
Integration Studio (.NET)
Integration Studio (EE)
TOCF (.NET)
TOCF (EE)
TWS (.NET)
TWS (EE)

Published on : 28/04/2013

16 of 16 6/13/17, 8:26 AM