Release Notes

Release R09
T24 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,

Electronic or mechanical, for any purpose, without the express written permission of TEMENOS
Temenos Page 1 of 1 Holdings NV.

Copyright 2002-2006 TEMENOS Holdings NV. All rights reserved

Release Notes
Table of Contents

PRE-RELEASE INFORMATION .................................................................................................... 4

Important Information ................................................................................................................. 4
Release Number Standardisation ........................................................................................... 4
New Component Structure ..................................................................................................... 4
Upgrade and Conversion Services ......................................................................................... 4
T24 Connectivity and JCA - Java Connector Architecture ..................................................... 5
System Component Requirements ............................................................................................ 5
Database Requirements ............................................................................................................. 6
Disk Space Requirements .......................................................................................................... 6
Data Changes ............................................................................................................................. 6
INSTALLATION OF THE SOFTWARE .......................................................................................... 6
Upgrading T24’s (TAFC) ............................................................................................................ 6
Upgrade Summary .................................................................................................................. 7
Important..................................................................................................................................... 9
TCS Adapter changes .............................................................................................................. 10
tcserver.xml ........................................................................................................................... 10
environment.vars .................................................................................................................. 10
Upgrading Browser / ARC-IB ................................................................................................... 11
Before Upgrading .................................................................................................................. 11
After Upgrading ..................................................................................................................... 11
CONVERSION ROUTINES ......................................................................................................... 12
Overview ................................................................................................................................... 12
Conversion Routines ................................................................................................................ 12
POST CONVERSION ACTIONS ................................................................................................. 12
Authorise Standard Selections ................................................................................................. 12
Authorising / Modifying new and changed records .................................................................. 12
Record Authorisation ............................................................................................................ 12
Batch Record Authorisation .................................................................................................. 12
Batch records HELD ............................................................................................................. 13
Batch record LIVE ................................................................................................................. 13
Sequence of authorisation .................................................................................................... 13
REPGEN recompile .............................................................................................................. 14
Application/Module Specific ......................................................................................................... 15
Arrangement Architecture ..................................................................................................... 15
Accounting ............................................................................................................................ 15
Bills........................................................................................................................................ 16
Browser ................................................................................................................................. 16

Temenos Page 2 of 2
Release Notes
Core ...................................................................................................................................... 16
Derivatives ............................................................................................................................ 17
Forward Rate Agreement ..................................................................................................... 17
Fiduciary................................................................................................................................ 17
Securities .............................................................................................................................. 17
Structured Products (SY) ...................................................................................................... 18
Structured Products Builder (SB).......................................................................................... 18
SPECIAL ROUTINES .................................................................................................................. 18

Temenos Page 3 of 3
Release Notes

PRE-RELEASE INFORMATION

Important Information
This section outlines actions that must be made BEFORE installing a T24Server 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.
The T24 Technical Highlights documentation should also be referenced. This will highlight any
changes of a technical nature that may impact local development.
Please read this entire document before commencing on any of the steps in the upgrade.

Release Number Standardisation

In the past release numbers for jbase, T24,Browser etc had different formats, making it harder for
the user to insure that compatible components were installed. From R09 all components will use a
standardised Component numbering.
Due to this it will be mandatory to install the new R09 versions of each Component. Further details
can be seen below.

New Component Structure

Prior to R09 object code was stored in a centralised library. From R09 a new Update process
allows users to take smaller ‘upgrades’ and as such the object code has now been split into
multiple Component libraries. Further in this document instructions will guide you in converting
your system.

Upgrade and Conversion Services

From R09 RUN.CONVERSION.PGMS is no longer allowed, you must now use the TSA.SERVICE
process RUN.CONVERSION.
Additionally GLOBUS.RELEASE can only be used to install a new product. Upgrades must also
now use the TSA.SERVICE process T24.UPGRADE. Service packs and patches are now
replaced with the new customer updates functionality.
Please reference the T24 Updates User Guide for more details.

Temenos Page 4 of 4
Release Notes

T24 Connectivity and JCA - Java Connector Architecture

From R09 T24 is able to be deployed in an Application Server and uses a JCA 1.5 compliant
resource adapter to connect to the Temenos Application Framework C Version (TAFC). The Java
Connector Architecture (JCA) is the Java EE standard for Application Server connectivity to
external systems.
Currently this connection option does not support Secure Document Download, Branch
Resilience, or T24 user impersonation (LDAP). These features will be supported in the near future.
The Temenos Connector Server (TCS) is still supported for upgrading clients, but the JCA is the
preferred connectivity choice from R09.
Please reference the TAFC JCA User Guide for more details or “Connectivity” section on the
Knowledge Base.

System Component Requirements

The following table shows the minimum components and release numbers which are designed to
run with T24.
T24 Component Release Platform
Browser / ARC IB R09.000 I.E. 7 and Firefox 2
Toolbox R09.000 Windows 2000, XP and VISTA
Desktop 1.5.001 Windows 2000 and XP
1.5.032 VISTA
Temenos Application R09.000 Operating systems (Minimums)
Framework C Version
Windows Server 2003(64 bit Only)
TAFC
RedHat Linux AS5
AIX5.3
Solaris 10
HPUX Itanium V3
Oracle Direct Connect R09.000 Minimum and recommended 11gR1
DB2 Direct Connect R09.000 Minimum version 9.5
MSSQL Direct Connect R09.000 Minimum and recommended SQL Server
2008
Temenos Open R09.000 JBoss 4.2.3
Connectivity Framework
Websphere 7
TOCF (EE)
Weblogic 10.3

Sun Java SDK 1.5.0(5.0)

Temenos Page 5 of 5
Release Notes

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.

INSTALLATION OF THE SOFTWARE

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

Upgrading T24’s (TAFC)

If you are not already running Temenos Application Framework C Version (TAFC) R09, previously
known as jBASE, you should install it.
Ensure no one else is logged in to the T24 account.
Now, to upgrade your T24 to your new TAFC release -

Temenos Page 6 of 6
Release Notes

Upgrade Summary

• Amend your .profile

Change the “export JBCRELEASEDIR=” statement in the .profile file to point to the TAFC_R09
release.
For example
export JBCRELEASEDIR=/usr/jbcxxxx (where your TAFC_R09 resides)

NOTE: Your profile will have another environment variable, JBCGLOBALDIR, this should be as
follows:
export JBCGLOBALDIR=$JBCRELEASEDIR
If it is not as above then make it so.
Replace all occurrences of globusbin and globuslib with t24bin and t24lib respectively from
JBCOBJECTLIST and PATH

Add the following new environment variables, JBASE_PATH & JBASE_OBJECTLIST_DIR as

shown below.
These can be added at any place in the .profile but sensibly should be grouped with the other
jBASE environment variables.
0154 export JBCDEV_BIN=$HOME/bin
0155 export JBCDEV_LIB=$HOME/lib
0156 # set the jBASE path
0157 export JBASE_PATH=$HOME/t24bin
0158 # the following variable tells jbase how deep to look in the t24lib
0159 export JBASE_JBCOBJECTLIST_DIR=1

You must also not use the existing “START GLOBUS Y/N” construct in the profile as this has been
superceded.
The following lines (in red) must be commented or removed (i.e. add the # at the beginning of the
line) and the last line (in red) must be added.
#echo "\nSTART GLOBUS Y/N=\c"
#read answer
#
# If we want to start GLOBUS, do so and then exit. This prevents:
# a) Too many processes being spawned and
# b) Processes being left "hanging"
#
#if [ "$answer" = Y -o "$answer" = y ]; then
# start GLOBUS here!
# DATE.FORMAT
# EBS.TERMINAL.SELECT
# EX
# exit
#fi

#--------------- End of Profile.Ksh -----------------

# Now enter the jsh to complete the login..>

#exec $JBCRELEASEDIR/bin/jsh -s jsh -

exec $JBCRELEASEDIR/bin/jpqn $JEDIFILENAME_MD/loginproc

Temenos Page 7 of 7
Release Notes
An example of a loginproc can be seen below.
0001 PQN
0002 OSTART GLOBUS Y/N +
0003 IP 1
0004 IF %1 # "Y" IF %1 # "y" GO 99
0005 HEBS.TERMINAL.SELECT
0006 P
0007 HEX
0008 PX
0009 99 Hjsh -s jsh
0010 PX

Logout and login again.

When logging in for the first time type:
UpdateMD

• Executing programs from shell

With the component based account, all the T24 binaries are placed one level down to t24bin (i.e.
within their component directories). Therefore if we wish to run any T24 programs from the Unix
shell prompt. Its component path within t24bin needs to be specified in the PATH variable in
.profile. For example to run the tSS executable you must specify its component location in the
PATH, i.e. t24bin/eb_interface. This can be specified as a full path or reference other environment
variables.
export PATH=$JAVA_HOME/bin:$HOME/t24bin/eb_interface:/usr/vac/bin

• Check that the TEMP.RELEASE is pointing to the correct upgrade path. For example;
TEMP.RELEASE
001 D
002 /T24/R09/temp.release

• Run T24.BUILD.LIBRARIES (logout and login with a new session). You must specify the
full path of the executable when running this command. It is located within the T24
temp.release area supplied by distribution in the t24bin. For example;
/T24/R09/temp.release/t24bin/eb_upgrade/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.

Temenos Page 8 of 8
Release Notes
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)

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

Important
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.

Temenos Page 9 of 9
Release Notes

TCS Adapter changes

tcserver.xml

TCS by default tries to start the binary of tSS (i.e. the name of the Program specified in the
<PROGRAM> tag) from the globusbin.

• Similar to the way we specify the TAFC installation path in the .profile the new TAFC
installation path has to be specified in the tag <JBASEPATH>.

• Now we have the binary of tSS in t24bin/eb_interface directory. Therefore we need to

force TCS to start the program from the new component structure by specifying the exact
path of the executable in the tag <PROGRAM/> in tcserver.xml

environment.vars

You should also check if the TAFC installation path mentioned in .profile [for JBCRELEASEDIR
and JBCGLOBALDIR] and in the environment.vars file matches [<TC Installation
path>/config/TCServer/environment.vars]. If not, you can try repopulating this file.

sh ~-> env > <TC Installation path>/config/TCServer/environment.vars

Note: Replace ‘<TC Installation path>’ with the path where TCServer is installed.

Temenos Page 10 of 10
Release Notes

Upgrading Browser / ARC-IB

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

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 web server.
2. Re-instate the changes to the backed-up files to the released versions.
3. Restart the web server.
4. Clear your browser’s cache of any old JavaScript files and images. To do this perform the
following :-
− Internet Explorer
o Tools -> Internet Options -> Browsing History -> Delete ->
Temporary Internet Files -> Delete Files
− Firefox
o Tools -> Clear Private Data -> Clear Private Data Now

Temenos Page 11 of 11
Release Notes

CONVERSION ROUTINES

Overview
This section outlines the conversion and other related routines to be run for this release. 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

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

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.

Temenos Page 12 of 12
Release Notes

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

Temenos Page 13 of 13
Release Notes

EB.COMPARISON.TYPE
AA.PROPERTY.CLASS
AA.PRODUCT.LINE
AA.ACTIVITY.CLASS
AA.PROPERTY
AA.PRODUCT.GROUP
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.

Temenos Page 14 of 14
Release Notes

Application/Module Specific

Arrangement Architecture

The following are the changes at the field level for different files and the actions to be taken with
respect to the same:
• The field FINAL.RES.AMOUNT has been removed from the PAYMENT.SCHEDULE property to
the TERM.AMOUNT property and renamed as ON.MATURITY. Any PAYMENT.SCHEDULE or
TERM.AMOUNT conditions, which previously used these fields should be modified for the
functionality to take effect.
• Field BASE.DATE has been made a NOINPUT field in PAYMENT.SCHEDULE property and
does not require any User input at the Product condition level. Conversions already exist to
nullify the value to NULL at product conditions.
• The existing field DRAWDOWN.DATE has been renamed as START.DATE in the
AA.ACCOUNT.DETAILS file.
• The field DEFAULT.ATTR.OPTION has been introduced in all property conditions and will
have options RESETTING and NON-RESETTING. Also, NR.OPTIONS field will have these
two options additionally and should be viewed in conjunction with DEFAULT.ATTR.OPTION
value.

Accounting

Interest and charges

The field WRITE.ACCR.ACCT in ACCOUNT.ACCRUAL controls the creation of the
ACCR.ACCT.CR, ACCR.ACCT.DR and ACCR.ACCT.CH files. The default is no which
means that these records will not be maintained.
Should you require updates to these files, you will need to set this field to Yes.

If using an oracle database it is recommended that the session number is used as part of the key
to consolidated entries. This is set using the field USE.SESSION.NUMBER in
ACCOUNT.PARAMETER and set it to ‘YES’.

Removal of EOD.PRE.ACCT.ACTIVITY from COB

As a result of the changes made in this release the field PREV.OPEN.BAL in the ACCOUNT
application has been made obsolete. The conversion CONV.ACCOUNT.200809 should be run to
clear this field.

All routines that rely on this field have been changed to use EB.GET.ACCT.BALANCE as shown
in the example below.
Any local development that relies on this field should be changed in the same way.

BALANCE.DATE = TODAY
CALL CDT("", BALANCE.DATE, "-2W")

Temenos Page 15 of 15
Release Notes
CALL EB.GET.ACCT.BALANCE(ID.ACCOUNT, R.ACCOUNT, "BOOKING", BALANCE.DATE, "",
PREV.OPEN.BAL, "", "", ERR.MSG)

Removal of ACCT.ACCT.ACTIVITY
The file ACCT.ACCT.ACTIVITY has been removed and the information that was held there has
been moved to EB.CONTRACT.BALANCES.
The conversion CONV.AAA.R09 should be run to make this change.

Bills

Updates to EB.CONTRACT.BALANCES
It should be ensured that Close of Business is run without any new transaction after upgrading.
During EB.CONTRACT.BALANCES
upgrade, file for each contract and
RE.CONSOL.CONTRACT will be built only after the Close of Business.

Browser

Browser – Maximized Windows

For this functionality the minimum WAR file requirement must be the 200808 build project build.
In addition to installing the WAR file due to caching your “Temporary Internet Files” and JavaScript
files need to be cleared from your browser.
The following procedures need to be completed.
For Internet Explorer: -
Tools -> Internet Options -> Browsing History -> Delete -> Temporary Internet Files -> Delete Files

For Firefox :-
Tools -> Clear Private Data -> Clear Private Data Now

Core

The EB.COMPONENT application has been re-named to SEAT.COMPONENT.

Once the RUN.CONVERSION service has completed the service CONV.EB.COMPONENT.R09
should be started and run. This will copy all existing records in EB.COMPONENT to
SEAT.COMPONENT.
EB.COMPONENT should no longer be used for SEAT component testing.

Temenos Page 16 of 16
Release Notes

Derivatives

Updates to EB.CONTRACT.BALANCES
It should be ensured that a Close of Business is run without any new transaction after upgrading.
During upgrade, EB.CONTRACT.BALANCES file for each contract and
RE.CONSOL.CONTRACT will be built only after the Close of Business.

Forward Rate Agreement

Updates to EB.CONTRACT.BALANCES
It should be ensured that a Close of Business is run without any new transaction after upgrading.
During upgrade, EB.CONTRACT.BALANCES file for each contract and
RE.CONSOL.CONTRACT will be built only after the Close of Business.

Fiduciary

Updates to EB.CONTRACT.BALANCES
It should be ensured that a Close of Business is run without any new transaction after upgrading.
During upgrade, EB.CONTRACT.BALANCES file for each contract and
RE.CONSOL.CONTRACT will be built only after the Close of Business.

Securities

The file SC.HOLD.POS has been redesigned to prevent lock contention and performance issues.
The file is now keyed by value date and transaction reference separated by a dot, for example
20090102.SCTRSC0900200001.
The record layout consists of two fields, value date and transaction reference. If any local
developments use this file heavily then users should consider adding secondary indices to the
required fields.

Once the RUN.CONVERSION service has completed the service CONV.SC.HOLD.POS.R08 should
be started and run.

Temenos Page 17 of 17
Release Notes

Structured Products (SY)

The following considerations need to be taken into account when installing the Structured
Products (SY) module.
A prerequisite of installing the Structured Product (SY) product is to have both the Arrangement
Architecture (AA) and Non Stop Processing (NS) modules installed already.

Before all items in the exception queue relating to SY and ancillary application are authorised the
following records need to be created: -
SY.PARAMETER record with id – SYSTEM
ACCOUNT.CLASS record with id – SYFUND
Please see the SY User Guide for full details.

Exceptions relating to the Structured Products (SY) installation should be authorised in the
following sequence: -
EB.TABLE.DEFINITION
AUTO.ID.START
VERSION
EB.FORMAT.ENTRY
STMT.NARR.FORMAT
CUS.POS.ENQ.PARAM
SY.PRODUCT.DESCRIPTION
SY.EVENT.DEFINITION
SY.UNIT.DEFINITION
SY.PRODUCT.INTERFACE

Structured Products Builder (SB)

Installation of the Structured Products Builder (SB) is dependent upon the Structured Products
(SY) modules already being installed.

SPECIAL ROUTINES
There are no special routines for this release.

Temenos Page 18 of 18