Updates

Updates
Release: R19 AMR

May 2019
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.
© 2019 Temenos Headquarters SA - all rights reserved.

Updates
Table of Contents
Introduction 3
Purpose of this Guide 3
Intended Audience 3
T24 Updates Client 4
Introduction 5
Application Overview 7
Overview and Processing 19
T24 Updater 37
Updates 38
What the Updater does for you 39
Prerequisites 40
Installing Updater 41
Configuring Updater 43
Running the Updater 48
Appendices 55
Improvement to Product(s) Deployment to suit Enterprise Architecture –
T24 Updates 61
Overview 62
Setup 63
Deal Processing 65
2
Updates
Introduction
Purpose of this Guide
Temenos provides maintenance support to T24 in the form of fixes that are release
daily. These fixes (aka Updates) are available for download from the Temenos Cus-
tomer Support site (tcsp.temenos.com).
This document details the Updates process and utilities that are used to download
the updates and install them at a customer environment.
Intended Audience
This User Guide is intended for the use of System Administrators who maintain and
update Temenos systems
3 Introduction
Updates
T24 Updates Client

l Introduction
l Application Overview
l Overview and Processing

Updates
Introduction
T24 Updates is a software support mechanism for T24. The Updates system allows
the user to search the T24 Updates Repository for relevant fixes for their T24 envir-
onments. These can then be downloaded and installed onto the T24 server system.
5 T24 Updates Client

Updates

Updates
Application Overview
System Update
System Update is a ToolBox plugin that is used to extract system details and create
a file which can be uploaded to the T24 Updates site as required.
A mechanism is provided by which a client can produce an XML file containing the
SPF details required by the T24 Updates Browser system to identify their system and
currently installed updates.
The XML file produced will then be uploaded to the T24 Updates system using the
Upload mechanism provided.
As part of the T24 Updates system end users are required to register system details
on the T24 Updates site. The system details hold information about a particular T24
environment that will be used by the T24 Updates system to list updates that are
necessary for the system. A client can register multiple systems, e.g. LIVE, TEST,
UAT, etc.
The system details contain information on the products and components that are
installed, the Operating System that is being used, and previous updates that have
been installed.
When a client wishes to register a system on the T24 Updates site they will login to
the required T24 environment via ToolBox. Once logged on they can run the ‘Sys-
tem Update’ plugin and extract the necessary details and create a file ready for
upload.
Every time that the T24 environment has been updated with a new update the cli-
ent can simply repeat this procedure to create a new definition file and upload it.
This will ensure that the details held on the T24 Updates site about that system are
kept up to date and in sync.

Updates
.
ToolBox showing the System Update option
System Update contains two options, namely:
Extract System Information and Temenos Update Website.

Updates
ToolBox showing the System Update screen
Extract System Information Option

Choosing the Extract System Information option presents a number of further
options.
System Settings Option

Updates
When System Settings is chosen the T24 System Parameters are presented as
extracted from the system parameter file of the connected system.
System Settings
Products & Components Option
When Products and Components option is chosen the current products and com-
ponents installed are listed.

Updates
Products and Components

Installed Updates Option
When the Installed Updates option is chosen any installed updates will be shown.

Updates
Installed Updates
Environment variable Option
When the Environment Variables option is chosen the system’s environment vari-
ables are shown

Updates
Environment Variables
The screen above is a result of the jDiag output extracted from the T24 application
server.
Create System Definition File Option
The final option is to Create System Definition File.

Updates
Create Export File

The field showing the ARC-IB URL should have the ARC-IB url entered only if you
use the product. The url can also be recorded in User Options and is taken from
there initially.
Clicking on the link ‘What will be exported’ produces the following help:

Updates
Export Information Help

To create the system definition file a description of the system is required. This will
be the name of the system used to identify that system on the T24 Updates site.
(The COMPANY record name)

Updates
Register this System

Clicking the <Create System Definition File> button creates the system definition
file and is saved as an XML file.
The created file is used to add or update a system on the T24 Updates site.

Updates
System Definition XML save
Temenos Update Website

Choose the Temenos Update Website option. This launches an internet browser ses-
sion loading up the Temenos.com website. From here there is an option to login and
access the T24 Updates site.
Temenos Web site
Logging in as a Client
After logging in to the Temenos web site, click Customer Support menu. This takes
you to the Temenos Customer Support Portal (TCSP). You need to have valid cre-
dentials to log in (users with access to the Temenos network automatically get
access, others such as clients and partners need to obtain credentials)
Temenos Customer Support Portal page

Click on Menu>T24>T24 Updates to load the T24 Updates portal page. You
will be presented with a link to login to “T24 Updates”.
T24 Updates

Updates
Click on the link to the Updates portal to gain access to the T24 Updates site.

Updates
Overview and Processing

Client Functions
There are a number of tasks available to the user via the Client Functions part of
the T24 Updates mechanism.
This system provides access to external clients only for the following actions:
Message management of an inbox via a Secure Messaging System. Messages will
arrive to the inbox from the Temenos Updates Team. Once read the messages can
be deleted when no longer useful.
Systems registration management for adding systems, uploading, selecting, view-
ing, and deletion.
Available System Updates management.
Search facilities for available updates via a valid Id or with the selection of attrib-
utes such as GA.RELEASE, Components, Platforms, and Products.
Upon selecting T24 Updates the client is presented with a screen similar to one
shown below.
Register a System
R09 and Above System Registration
The following screen is displayed for the Add System option. The add option can be
used to take the updates to a specific environment, for example a UAT environment
rather than taking the update to the live area. Once the system has been added the
user then has the option to select which environment to be used from the select sys-
tem option.

Updates
Clicking the <Browse> button opens a choose file dialog. Once the correct system
definition file is selected and the <Open> button is clicked the dialog will close and
the file will be automatically uploaded.
The T24 system has been registered
Clicking the Systems link the newly registered system is showing

Updates
R08 and Below System Registration

The following screen is displayed for the Add System option. To register a pre-R09
system the client will select the <Add a GA Release R08 and below (T24 Service
Packs)> link
The R08 and below system registration screen is shown. The Ga Release and OS
Platform are selected and a description of the system added.

Updates
The system is registered and showing in the Systems list.
Update the System Definition

R09 and Above
To update the system definition, choose “Update System” from the dropdown
against the system.
The re-enter a new T24 Updates system file screen is displayed.

Updates
Clicking the <Browse> button opens a choose file dialog. Once the correct system
definition file is selected and the <Open> button is clicked the dialog will close and
the file will be automatically uploaded.
The T24 system definition has been updated.

Updates
Clicking the Systems link the newly updated system is showing with the date and
time of the last registration.
R08 and Below

To update the system definition, choose “Update System” from the dropdown
against the system.
The re-enter a new T24 Updates system file screen is displayed. Enter the required
changes

Updates
The T24 system information has been updated.
Clicking the Systems link the newly updated system is showing with the date and
time of the last registration.
Delete a System Definition

In the next screen an attempt is being made to delete a system’s details from the
repository.
Confirmation of delete is shown

Updates
The system is deleted; this is the deletion of the system definition file only on the
T24 Updates site.
Select and Download Updates

R09 and Above
To select a system to find updates for, click the “Select System” hyperlink.

Updates
A list of current components the system has installed is displayed.

Available updates can be viewed in two ways:
1. Available updates by product.
2. Available updates by release date.
Enter some criteria to perform a search in the search text box.
All update files will be searched. It will look to match any word entered in the
phrase to any word used in the problem or symptom fields of the update.

Updates
Updates details can be downloadable as CSV format for clicking the Save as CSV
link.

Updates
Each row returned by a search can be selected by clicking on it. By clicking a row
you are also choosing the associated update file and any other update that is
required by it. The selected updates are remembered until you choose a different
system or log out.
Clicking the <Available Updates> link, the previously chosen updates are selected.
Each item can be deselected or new ones selected.

Updates
Any selected updates will be remembered between search results and available
updates.
Closing the browser window or selecting a different system from the Systems menu
will clear the remembered updates.
Alternatively clicking the <Available Updates> link will return all available updates
for your current system

Updates
The update content can be viewed prior to being taken.
All fixes in the update with symptom and problem are shown. As with the search res-
ults the update can be selected here by clicking on any row and will be
remembered in the available updates menu.

Updates
Individual updates can be taken by choosing each one or choosing all. The impact
will show the level of importance.
The selected updates can be downloaded by clicking the tick icon

A confirmation of updates to download are shown

Updates
When the selected updates are correct click the <Download Updates> link. A zip file
containing the updates files can be downloaded and saved to the preferred location.
The downloaded file will contain files as listed under the Update Reference column
on the download confirmation page.
l Browser and ARC-IB war files should be installed on the web server(s) to
replace older versions.
l Toolbox should be installed on the Windows PC’s as required.

Updates
l T24 component archive files (.tar extension) should be placed in the T24
Updater and the Updater service run to install them.
R08 and Below

Service Pack files are not available for download from the updates site. Information
on fixes in a Service Pack is available
To select a system to find service pack details for, choose “Select System” from the
dropdown against the system.
The “Available Service packs” screen is shown. This shows a list of all service packs
available for the T24 release of the system.
Click the <Service Pack contents> link shows the content of the service pack in
terms of problem and solution.

Updates
Service pack files are available by contacting Temenos who will provide the ftp site
address.
Install the Updates

Once the Updater is installed alongside the T24 system (please refer to the
“Updater User Documentation” guide for installation and configuration) updates
can be installed.
Please refer to section 4 “Run the Updater” in the “Updater User Documentation”
guide on how to install updates
Update the System Definition, Post Update Installation

Once the T24 components have been successfully installed a new system definition
file should be generated from Toolbox then uploaded on the Updates Service site
against your system.
Please refer to the section titled “Update the System” in this guide on how to do
this.
How to Update an R08 System Definition to a T24 Updates System

If a system is on an R08 release and it is being upgraded to an R09 release or above
then the system definition on the T24 Updates site must be updated in the following
manner.
Log on to the T24 Updates site. Find the system that has been upgraded and choose
“Delete System” from the drop down. Follow the prompts to delete the system defin-
ition.
In Toolbox generate a system definition file (See the section titled “Create System
Definition File Option” in this guide for information in generating this file).
Back to the T24 Updates site; Click the “Add System” link. Click the <Browse> but-
ton to open a choose file dialog. Select the correct system definition file and click
the <Open> button to automatically upload the file

Updates
A message will be displayed saying “The T24 system has been registered”.
This system is now compatible with updates and can no longer take service packs.

Updates
T24 Updater
l Overview
l What the Updater does for you
l Prerequisites
l Installation
l Running the Updater - basics
l Appendices
37 T24 Updater
Updates
Updates
Overview
The purpose of this document is to provide the user instructions for the T24 Updater
tool. The Updater provides a simple mechanism to service T24 components with
smaller updates as opposed to the more comprehensive patches and service packs.
This will provide the customer with a faster response time with regard to fixes.
It is useful to be familiar with the way the updates are created; this information can
be found in the T24 Updates Client. In short this is a web based front end where cli-
ents search for fixes for their installed products and select which ones to take. The
system identifies any dependencies they have and packages the updates into a zip
file for them to download. It is this zip file that forms the input for The T24 Updater
tool.
T24 Updater 38
Updates
What the Updater does for you

The T24 family of products, T24 itself; TAFC; TAFJ; TAGJ; T24 Browser; ARC-IB and
T24 Toolbox can be updated, either fully automatically or guided semi-auto-
matic/manual installations.
For example an update to the T24 server code can be fully installed, together with
any associated data, in a matter of minutes utilising the power and stability of the
T24 release infrastructure but in bite size portions rather than full releases.
Although the dependency between the updates is made at the front end when the
client selects any fixes the T24 Updater will also verify any dependencies and pre-
vent any installation which has any errors.
A new version of browser together with server code can be provided in an update,
the server code will install automatically and the setup files for the browser are
extracted for you to install. The T24 Updater will also verify the current version you
are using and advise if the one supplied is not a valid update.
Whilst it is possible that an update could contain several products (TAFC, T24
Browser, ARC-IB etc) you are more likely to keep your system updated with smaller
updates so you can self-manage the impact of taking changes.
In summary, T24 Updater has built in version checking for the T24 products and a
dependency checker that will safeguard the installation of your selected updates.
Who should use the Updater

The updating of any part of the T24 infrastructure is a role for the Administrators of
the system and only to be undertaken by users with the required levels of pro-
ficiency.
Updates should not be done until the appropriate levels of backups have been made
according to what parts are being updated.
What products can you update

The following Temenos products can be updated with the Updater.
T24
TAFC
TAFJ
TAGJ
T24 BROWSER
ARC-IB
T24 Toolbox
39 T24 Updater
Updates
Prerequisites
l Java JRE 1.5 or Java JRE 1.6
l One or more of the T24 products (T24, TAFC or TAFJ etc) at R09 or above
l The appropriate version of gtar for both Unix and Windows (depending upon
the platform).
Note1: The gtar utility is similar to tar but can handle the longer
file/path names that can occur.
Note2: This utility is not supplied as standard in Windows or Unix but

commercial, open source or free versions are available. You may need
to amend your path to ensure the command is usable in the T24 home
directory.
T24 Updater 40
Updates
Installing Updater
Note : This is already pre-installed in Internal Model Bank areas
Extract the files

Obtain the T24ProductUpdater_<<Platform>>.tarfile
Untar it to the run directory of your T24 installation. If you are installing to a
machine without T24 on it, install to a directory which you will reference as $T24_
HOME.
Note: The updater must be run from the run directory ($T24_HOME) if
T24 is a product specified in the updater.xml file.
Example. tar -xvf T24ProductUpdater_Unix.tar
Extracting the updater components from the provided tar file
Updater Directory structure

When extracted the T24 Updater creates a master directory and a set of sub-dir-
ectories.
updater
41 T24 Updater
Updates
bin
config
lib
processed
setup_files
updates
The directory names are fairly self-explanatory. Of note are updates where the
downloaded zip files are placed for processing; processed where they are moved to
after being processed; and setup_files for when the downloaded zip files contain
new releases for T24 Browser, ARC-IB and T24 Toolbox, the setup files are moved
there
Set file permissions

Set the directory permissions on the installed updater directory. Ensure that the
updater file in the updater/bin has execute permission.
Installation of gtar
Like tar, gtar is a utility which helps in doing tar and un-tar operations. T24 Updates
functionality makes use of gtar. Please check whether gtar is installed in your
server by running the command
a. “which gtar” as shown below in UNIX:
b. "tar --help" in Windows:
If it is not installed, kindly download the utility suitable to your platform and specify
the PATH of the bin directory in the environment variable PATH in the .pro-
file/remote.cmd
UNIX (.profile):
Windows (remote.cmd):
T24 Updater 42
Updates
Configuring Updater
Set the following Environment Variables
The Updater relies on several environmental variables being set. So ensure that the
following are set in the .profile (T24_HOME is the only one that is mandatory, but
either TAFJ_HOME or JBCRELEASEDIR is required depending on which framework is
used):
Variables
T24_HOME this is the run directory of your system for example the
bnk.run directory
TAFJ_HOME this is the install directory for TAFJ (Temenos Application
Framework Java)
JBCRELEASEDIR this is your TAFC (Temenos Application Framework C) install
directory
JEDIFILENAME_SYSTEM this points to the SYSTEM file in TAFC i.e. it must be set =
SYSTEM
Path
Add $T24_HOME/updater/bin to your PATH environment variable.
Set the following properties(TAFJ only)

Check that the following properties are set in your dot properties file
Ensure that the .current property points to the same location as the T24_Home
environment variable
tem-
n.tafj.runtime.-
directory.current=<tafj.home>/../../../Data/T24/UD
Ensure that the updates property points to the location where the processed
updates files should be placed
temn.tafj.directory.updates=<tafj.home>/updates
Set the system file properties
JEDIFILENAME_SYSTEM = SYSTEM
Set path to a temp.release area

Part of the process of the updater involves the routines of the release procedure so
it is necessary to have access to a temp.release area; the update process uses the
same build lists as a normal release and the infrastructure for these are readily
available in a temp.release area.
43 T24 Updater
Updates
This is achieved by creating a TEMP.RELEASE record in the systemfile, as ref-

erenced by the environment variable JEDIFILENAME_SYSTEM.
[TAFC]
At the jShell
Type jDiag to run the TAFC diagnostic that shows the JEDIFILENAME_SYSTEM vari-
able
To create system file and temp.release record, use the following commands in the
jShell prompt
CREATE.FILE DATA SYSTEM TYPE=UD
JED SYSTEM TEMP.RELEASE
TEMP.RELEASE record should have two entries. Line 1 - D and Line 2 - path of the
temp.release directory.
[TAFJ]
At the TAFJ shell, type tDiag to verify the presence of the JEDIFILENAME_SYSTEM
property
From the JQL-SQL Editor in Design Studio
CREATE-FILE SYSTEM TYPE=UD
JED SYSTEM TEMP.RELEASE
Alternatively, you could use DBTools instead of Design Studio. At the TAFJ shell
prompt enter
DBTools -s -u admin -p Temenos@123 JQL CREATE-FILE SYSTEM TYPE=UD
DBTools -s -u admin -p Temenos@123 JED SYSTEM TEMP.RELEASE
Updater Configuration file

The updater.xml file contains the products you can update together with the install-
ation and storage directories used by the Updater.
The file is located under the $T24_HOME/updater/config directory.
T24 Updater 44
Updates
It will be validated against the updater.xsd schema file that is located in the same
directory. It contains a default for each T24 product that can be updated with the
Updater but needs to be configured by the user to meets their system require-
ments.
The <updatesdir> tag is the path reference to where you must put your updates.
<updatesdir>
C:\Temenos\R19\T24\Env\Slot1\Data\T24\UD\updater\updates
</updatesdir>
There is a default set when you install.

While the [TAFJ_HOME], [JBCRELEASEDIR], [T24_HOME] variables are used in the
supplied updater.xml you may also provide the full path of these environment vari-
ables if you do not have them set. If you have them set, you can leave this file as is.
An example is shown below in TAFC
Example of the updater.xml configuration

An example is shown below of a typical configuration in TAFJ
<service name="T24" pathType="EXEC" updateType="AUTO">
<path>C:\Te-
menos\R19\Env\Slot01\Products\TAFJ\Default\bin\tRun.bat
T24Version</path>
45 T24 Updater
Updates
<install-
path>C:\Te-
men-
os\R19\En-
v\Slot1\Data\T24\UD\updater\updates\tmp</installpath>
<install-
pro-
gram>C:\Te-
men-
os\R19\En-
v\Slot01\Product-
s\TAFJ\Default\bin\t24Updater.bat</installprogram>
</service>
Each product has a <path> section which defines the version check routine for the
product; an <installpath> section for the product install location and an <install-
program> section for the routine used to update the product.
These should all be checked and can either use the full path and name or a com-
bination of the appropriate environment variable and path/name.
Move any products that aren’t in use inside the comment section that starts “Ser-
vices not in use go here”
Valid updateTypes are AUTO and MANUAL.
If MANUAL, the Updater will validate the update but not perform the update.
Manual updates will be moved to the setup_files directory after the updater
terminates. If AUTO, the <installpath> and <installprogram> tags are mandatory as
the Updater will try to perform the update after it is validated. The Updater will
call the program specified within the <installprogram> tag to actually do the
update.
Valid pathType attributes are EXEC, URL, and FILE.
If URL is specified, the update will be MANUAL. Applications such as TAGJ and T24
BROWSER might have multiple installations or servers that need to be updated (and
also might have different versions of the product for each client). For this reason,
updates are manual. With the EXEC pathType, the updater will try executing the
program in the <path> tag, and with the FILE pathType, the updater will simply read
the file from the <path> tag.
Ensure that each program under the <path> and <installprogram> works. An
example for TAFJ is shown. If these programs do not work, the Updater will not
work and will report an error.
Example of TAFJ reporting it’s version information.
j24test@chdsk-j24dev:~/j24_development/bin$ tVersion
<ivy-module version="1.0">
<info organisation="Temenos" module="TAFJ" branch="R09_ALL"/>
<dependencies>
T24 Updater 46
Updates
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJCore" rev-

v="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJDBIm-
port" rev="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJLocking"
rev="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJMan-
agement" rev="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJPack-
ager" rev="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJTelnetD"
rev="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_TAFJVersion"
rev="0" />
<dependency org="Temenos" branch="R09_ALL" name="FJ_
com.temenos.tafj.bridge" rev="0" />
com.temenos.tafj.builder" rev="0" />
com.temenos.tafj.database" rev="0" />
com.temenos.tafj.launcher" rev="0" />
</dependencies>
</ivy-module>
j24test@chdsk-j24dev:~/j24_development/bin$ TAFJUpdater
Fail:Incorrect arguments
Using Updater on Multi-Tenant System

Additional parameters to the updater utility have been added for Multi-Tenant
updates; these parameters should only be used in that context and are listed here
purely to direct the reader to the correct MT information.
DataOnly – used by the MT owner to provide data updates to a shared object envir-
onment
ObjOnly – used by the MT owner to update shared object libraries
For updates to MT server systems only, refer to the MT User Guide(s).
47 T24 Updater
Updates
Running the Updater

1. Place any updates in the updates directory without unzipping them.
Updates in standard form are in zipped format with a name such as T24Up-
date200904011433.zip, (being T24UpdateYYYYMMDDHHMM.zip format).
2. Setting the shell
(refer to the configuration section for a complete list of configuration)
[For TAFC]
If the updater is used to keep the T24 product updated, it must be run from the run
(home) directory of the T24 database, as defined in the T24_HOME variable if set .
a. Open the jShell
b. Ensure that your PATH is set correctly to the $T24_HOME/updater/bin dir-
ectory
[for TAFJ]
a. Open TAFJ Shell
b. Navigate to the updater directory using cd
3. Type “updater” at the jsh prompt or standard command prompt to run the par-
ent installer. Refer Stage 1: Updater below
After processing an update, the T24Updates.zip file will be moved to the processed
directory. If by chance any old files remain in the updates directory, remove them
before running any new update as they could conflict with a newer update for the
same product.
For TAFJ, you need to copy the new jars into the relevant folders under the
t24/JBoss folder structure. Refer libraries section below
4. Finally, run the T24 Updates service to release the data records. Refer Stage 2:
T24 Updates below.
Updater - Processing a T24 update

T24 Updater is a two stage process:
1. The First stage copies the libraries and binaries.
2. The Second stage is the running of the T24.UPDATES Service to release the
data records
Stage 1: Updater
Run the Parent Installer program (updater). In this part, the following will be accom-
plished for T24 Update in the .zip file:
T24 Updater 48
Updates
l The libraries and binaries of the T24 Updates will be copied from the Updates
pack to respective component folders inside t24lib and t24bin in the run dir-
ectories.
l All modified Insert routines in the T24 Updates pack will get copied in to the
directory T24.BP (previously GLOBUS.BP)
l The T24.UPDATE.RELEASE record from the T24 Updates pack will get copied
into the application T24.UPDATE.RELEASE.
The screenshot below shows Updater running in a TAFC environment
Updater running
As a control for the T24 server code a record is created in the &COMO& file, as you
will see it’s very much like a release upgrade output.
COMO of the update session
Result after running Updater

Libraries
[TAFC]
49 T24 Updater
Updates
The new code libraries will be copied into the t24lib folder
[TAFJ]
In a TAFJ environment, after running updates the jars will be unzipped into the
updates folder (the folder pointed to by the temn.tafj.directory.updates
property).
Copy these jars to the precompiled folder or the relevant folder in your App server
(this is usually JBoss\Default\modules\com\slot01\temenos\t24\main
for a standard model bank installation)
SPF
The field T24.UPDATES in SPF will not be updated at this juncture. The SPF will be
updated after the second stage.
SPF before updates
T24.UPDATE.RELEASE
The field DATA.RELEASED in T24.UPDATE.RELEASE will hold the value “N” to signify
that Data record(s) (if any) for this T24 Update has not been released yet.
T24 Updater 50
Updates
Flag indicates data not released yet.
Stage 2:T24.UPDATES Service

The Service XXX/T24.UPDATES has to be run to release the data records of the T24
Updates. The co-responding Batch record XXX/T24.UPDATES should have
“T24.UPDATES” entered in the DATA field.
BATCH record has DATA field populated
Note: XXX is the Master Company mnemonic for a Multi Company

environment. For a Single Company environment the TSA.SERVICE &
BATCH record would be available without the mnemonic.
Start the service XXX/T24.UPDATES by marking the SERVICE.CONTROL field of

T24.UPDATES Service record to “START”.
51 T24 Updater
Updates
Starting the T24.UPDATES service

Start the TSM.
Starting the TSM

Launch the Agent
T24 Updater 52
Updates
Service running
After the service is complete, check the field T24.UPDATES in SPF “SYSTEM” record.
Now the SPF will have been updated with all the installed Updates name(s).
SPF updated
A data record of the updates R09_SC_OverrideCodes_1 is released.
Data item released to authorise

Once the T24 Update is picked up for releasing the Data Record(s) and after releas-
ing them successfully ,then the co-responding update is marked as Completed by
setting the value as “C” to the field DATA.RELEASE in T24.UPDATE.RELEASE record
as shown:
53 T24 Updater
Updates
Updated T24.UPDATE.RELEASE record

COMO record of this T24.UPDATES service tn04af4485 krn 260902981
Updates COMO
T24 Updater 54
Updates
Appendices
Troubleshooting
Working Directory
If you receive an error saying something like:
Working Directory
/storage1/globus.accounts/globus.acc.3/deva/deva.run/updater
not the same as T24_HOME
This is because you are not running updater from the correct location, you should
be in the directory specified as T24_HOME.
Updater did not work

The Updater didn’t process anything. What happened?
Is there a zip file in the updates directory?
Updater hangs
My update hangs. What’s happened?
Most likely the program that is referenced by the <installprogram> tag in updater-
.xml is not working. Try running this program by itself on the command line to see
if it works.
XML error
I get a [org.xml.sax.SAXParseException: The processing instruction target match-
ing "[xX][mM][lL]" is not allowed.] error
This is most likely due to the fact that the updater.xml is not correct. In particular,
you do not have the <?xml version="1.0" encoding="UTF-8" ?> as the first line in the
file. Or the encoding is incorrect.
Try running the unix tool:
$ xmlwf ../config/updater.xml
../config/updater.xml:1:30: encoding specified in XML declaration is incorrect
A message similar to the one below should appear if you are getting this error. To
correct this, correct the updater.xml file such that it is valid.
SEVERE: Caught UnmarshalExceptionnull
javax.xml.bind.UnmarshalException
- with linked exception:
[org.xml.sax.SAXParseException: The processing instruc-
tion target matching "[xX][mM][lL]" is not allowed.]
55 T24 Updater
Updates
at javax.xm-
l.bind.help-
ers.AbstractUnmarshallerImpl.createUnmarshalException
(AbstractUnmarshallerImpl.java:
328)
at com.sun-
.xm-
l.bind.v2.runtime.un-
marshaller.UnmarshallerImpl.createUnmarshalException
(UnmarshallerImpl.jav
a:476)
at com.sun-
.xm-
marshaller.UnmarshallerImpl.unmarshal0
(UnmarshallerImpl.java:198)
at com.sun-
.xm-
marshaller.UnmarshallerImpl.unmarshal
(UnmarshallerImpl.java:167)
at javax.xm-
l.bind.helpers.AbstractUnmarshallerImpl.unmarshal
(AbstractUnmarshallerImpl.java:150)
at javax.xm-
l.bind.helpers.AbstractUnmarshallerImpl.unmarshal
(AbstractUnmarshallerImpl.java:197)
at com.temenos.upgrader.jaxb.JaxbUtil.load
(JaxbUtil.java:31)
at com.temenos.upgrader.Upgrader.doReport
(Upgrader.java:127)
at com.temenos.upgrader.Upgrader.main(Upgrader-
.java:108)
Caused by: org.xml.sax.SAXParseException: The pro-
cessing instruction target matching "[xX][mM][lL]" is
not allowed
at org.a-
pache.x-
erces.util.ErrorHandlerWrapper.createSAXParseException
(Unknown Source)
T24 Updater 56
Updates
at org.a-
pache.xerces.util.ErrorHandlerWrapper.fatalError
(Unknown Source)
at org.a-
pache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.a-
pache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.a-
pache.xerces.impl.XMLScanner.reportFatalError(Unknown
Source)
at org.a-
pache.xerces.impl.XMLScanner.scanPIData(Unknown
Source)
at org.a-
pache.x-
erces.impl.XMLDocumentFragmentScannerImpl.scanPIData
(Unknown Source)
at org.apache.xerces.impl.XMLScanner.scanPI
(Unknown Source)
Dependency Errors
The updates files downloaded will have been created based on the system details
uploaded. Any updates that have a dependency will be checked against your system
settings and where required the dependent update will have been included in your
download.
T24 Updater will perform a separate dependency check against your system as a
safeguard. If any dependency errors occur the update will not continue and you
should contact Temenos Helpdesk for assistance.
Procedure for testing whether the environment is set up correctly

Setting up the environment correctly has shown up as the most common problem
on site. AIX for example, requires LIBPATH to be set. If it is not, one will normally
xml parse errors as the java program cannot communicate with child C programs
through the Runtime.exec() function in java. The program below tests whether java
and C programs are communicating correctly.
l Copy the below code into TestProcess2.java.
l Compile it (javac TestProcess2)
l export CLASSPATH=.
l Build a simple shell program in the same directory called HELLOWORLD.sh
57 T24 Updater
Updates
l In HELLOWORLD.sh, put the line echo “HELLOWORLD”

l chmod 700 HELLOWORLD.sh
l java TestProcess2 HELLOWORLD.sh
l You should see the output below.
$ java TestProcess2 HELLOWORLD
Exit Value 0
Input stream:java.io.BufferedInputStream@1260126
InputStreamReader:java.io.InputStreamReader@5c505c5
BufferedReader:java.io.BufferedReader@ac80ac8
HELLOWORLD
l Now try the same with T24Version. You should see the xml being outputted
from the T24Version program. If you do, your environment is set up
correctly. If not, something is probably wrong with LIBPATH or
JBCOBJECTLIST. Try creating a simple BASIC program that does a CRT and
run it with the TestProcess2 program. If it still fails, do a jshow on that basic
program. Is the shared library included in the LIBPATH or JBCOBJECT list?
import java.io.*;
public class TestProcess2
{
public TestProcess2()
{
}
public static void main(String args[])
{
String process = args[0];
Process p = null;
int exitVal = 0;
try
{
p = Runtime.getRuntime().exec(process);
exitVal = p.waitFor();
}
catch(IOException e1)
{
e1.printStackTrace();
}
catch(InterruptedException e)
{
e.printStackTrace();
}
System.out.println((new StringBuilder("Exit
Value ")).append(exitVal).toString());
if(p.getInputStream() == null)
System.out.println("Input stream null");
T24 Updater 58
Updates
java.io.InputStream input = new BufferedIn-

putStream(p.getInputStream());
System.out.println((new StringBuilder("Input
stream:")).append(input).toString());
String line = null;
InputStreamReader isr = new InputStreamReader
(input);
System.out.println((new StringBuilder
("InputStreamReader:")).append(isr).toString());
BufferedReader reader = new BufferedReader
(isr);
System.out.println((new StringBuilder
("BufferedReader:")).append(reader).toString());
char cbuf[] = new char[500000];
try
{
int len = reader.read(cbuf);
if(len == -1)
{
System.out.println("len is -1");
System.exit(1);
}
System.out.println(new String(cbuf, 0,
len));
}
catch(IOException e)
{
e.printStackTrace();
}
}
}
Logging with the Updater

Extra output is available to track what the updater is doing. Logging in the updater
is handled by the standard jdk logger. The properties for this are usually located in:
$JAVA_HOME/jre/lib/logging.properties.
To display to the console the following properties must be set:
handlers= java.util.logging.ConsoleHandler
.level= FINE
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
To display to a file the following properties must be set:
handlers= java.util.logging.FileHandler
59 T24 Updater
Updates
.level= FINE
# default file output is in user's home directory.
java.util.logging.FileHandler.pattern = %h/java%u.log
java.util.logging.FileHandler.limit = 3000000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
java.util.logging.FileHandler.level = FINE
Note: Windows the user’s home directory is C:\Documents and Settings

\<<User>>. The log will appear here as java0.log if the above FileHand-
ler.pattern is used. As well the .level defines the global log level, so if
you have .level set to INFO, but java.util.logging.ConsoleHandler.level =
FINE, then you will only see INFO level messages. Valid levels are
SEVERE, WARNING, INFO, and FINE.
T24 Updater 60
Updates
Improvement to Product(s) Deployment

to suit Enterprise Architecture – T24
Updates
This section covers the following topics.
61 Improvement to Product(s) Deployment to suit Enterprise Architecture – T24

Updates
Updates
Overview
T24Updates can be installed via application server.
The Resource Cache Server (RCS) provides a virtual filesystem in a database. This
service is used to retrieve the resources from the database that the application
needs for providing the functionality. It enables pooling of resources and ensures
centralized storage for all applications. It allows content to be partitioned by
domain and within domain, it is separated by version and directory.
Improvement to Product(s) Deployment to suit Enterprise Architecture – T24 62

Updates
Updates
Setup
1. Prepare a T24Updates.war with the T24updates.zip which must be installed into
the target environment.
2. Deploy the package into the appserver and ensure that the deployment is suc-
cess.
3. Create a staging area, which will create TAFJ.PACKAGE and
TAFJ.PACKAGE.RECORD table,

Updates
Updates
4. Write the package content into the staging area, which will feed records into the
table TAFJ.PACKAGE and TAFJ.PACKAGE.RECORD

Updates
Updates
Deal Processing
Run UpdatesInstallerDeployment, to deploy the updates records which are written
to TAFJ.PACKAGE.RECORD
Sample updates,
Update contents for deployment,
F.DSL.MODEL.SOURCE>SYSTEM.USER.UXP.enquiry
F.STANDARD.SELECTION>NOFILE.SYSTEM.USER.UXP
F.ENQUIRY>SYSTE.USER.UXP
Running UpdatesInstallerDeployment,
The &COMO& file are created with the name of the updater under como directory.

Updates
Updates
Appropriate log update in T24.log,
The T24.UPDATE.RELEASE record for 201802_EB_ModelBank_1 with

DATA.RELEASED set to N after completing the UpdatesInstallerDeployment,
The &SAVEDLISTS& with the ID list updated,

Updates
Updates
Set the DATA field of BATCH record BNK/T24.UPGRADE to T24.UPDATES
START TSM and BNK/T24.UPGRADE,

Updates
Updates
Launch tRun START.TSM,
&SAVEDLISTS& gets updated with DATA details,
The records get released to the environment,

F.DSL.MODEL.SOURCE>SYSTEM.USER.UXP.enquiry

Updates
Updates
F.ENQUIRY>SYSTE.USER.UXP

Updates
Updates

Updates
Updates
F.STANDARD.SELECTION>NOFILE.SYSTEM.USER.UXP

Updates
Updates
The T24.UPDATE.RELEASE after running service with DATA.RELEASED updated with

‘C’ (completed),

Updates
Updates
The SPF record after the updates gets completed,

Updates
Updates

Updates

Updates

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Updates

Uploaded by

Copyright:

Available Formats

Updates

Release: R19 AMR

Information in this document is subject to change without notice.

© 2019 Temenos Headquarters SA - all rights reserved.

T24 Updates Client

T24 Updates Client 4

5 T24 Updates Client

T24 Updates Client 6

7 T24 Updates Client

T24 Updates Client 8

ToolBox showing the System Update screen

Extract System Information Option

9 T24 Updates Client

T24 Updates Client 10

Products and Components

11 T24 Updates Client

T24 Updates Client 12

The final option is to Create System Definition File.

13 T24 Updates Client

Create Export File

T24 Updates Client 14

Export Information Help

15 T24 Updates Client

Register this System

T24 Updates Client 16

System Definition XML save

Temenos Update Website

Temenos Web site

Temenos Customer Support Portal page

17 T24 Updates Client

T24 Updates Client 18

Overview and Processing

19 T24 Updates Client

The T24 system has been registered

Clicking the Systems link the newly registered system is showing

T24 Updates Client 20

R08 and Below System Registration

21 T24 Updates Client

The system is registered and showing in the Systems list.

Update the System Definition

The re-enter a new T24 Updates system file screen is displayed.

T24 Updates Client 22

The T24 system definition has been updated.

23 T24 Updates Client

R08 and Below

T24 Updates Client 24

The T24 system information has been updated.

Delete a System Definition

Confirmation of delete is shown

25 T24 Updates Client

Select and Download Updates

T24 Updates Client 26

A list of current components the system has installed is displayed.

Enter some criteria to perform a search in the search text box.

27 T24 Updates Client

T24 Updates Client 28

29 T24 Updates Client

T24 Updates Client 30

The update content can be viewed prior to being taken.

31 T24 Updates Client

The selected updates can be downloaded by clicking the tick icon

T24 Updates Client 32

33 T24 Updates Client

R08 and Below