TAFJ Updater
TAFJ Updater
R23
Revisio
Date Amended Name Description
n
1 1st April 2011 TAFJ team Initial version
2 7st February 2012 H. Aubert R12GA review
13th February
4 R. Vincent R14GA review
2014
Vigneshwara
11 02nd June 2022 Updated property for cloud environment
n
Copyright
Please include your name, company, address, and telephone and fax numbers, and email
address if applicable. [email protected]
Table of Contents
Document History................................................................................................................... 2
Copyright................................................................................................................................ 3
Errata and Comments............................................................................................................. 3
Install the Parent Installer....................................................................................................... 5
Add the T24 TAFJ Child Installer Service to the ParentInstaller................................................5
What the Child Installer Does........................................................................................................... 6
Showing Version of TAFJ Components.....................................................................................7
Logging for the TAFJ Child Installer.......................................................................................... 7
A T24 TAFJ Update Example.................................................................................................... 8
This section assumes you have already installed the ModelBank pack / working TAFJ
Environment.
Create a directory (ex: UD/T24UD) and make use the same runtime directory by setting the
directory path as T24_HOME.
Specify the created directory path in property temn.tafj.runtime.directory.current in the
TAFJProperties and install the Parent Installer under it.
Set JEDIFILENAME_SYSTEM=SYSTEM in TAFJProperties in order to release the records.
You obtain the ParentInstaller kit from Distribution. The ParentInstaller program delegates work
(the actual updating process) to a child installer for TAFJ, TAFC, T24, etc. Each child installer is
defined as a service to the ParentInstaller.
The key in the TAFj properties file is temn.tafj.runtime.directory.current
Note: Assume runtime path as temn.tafj.runtime.directory.current=
/glodev1/tafj/tafjx01/TAFJ/T24UD
Add the service for T24 TAFJ as shown below in the T24_HOME/updater/config/updater.xml file.
Comment out other services defined that are not used.
<service name="T24" pathType="EXEC" updateType="AUTO">
<path>[TAFJ_HOME]\bin\tRun.bat t24Version</path>
<installpath>[T24_HOME]\updater\updates\tmp</installpath>
<installprogram>[TAFJ_HOME]\bin\t24Updater.bat</installprogram>
</service>
Note: If the updater is executed on a cloud environment, then set the environmental variable
temn_cloud_updater to true.
Test the ParentInstaller by showing the T24 component versions as shown below.
$export T24_HOME = /glodev1/tafj/tafjx01/TAFJ/T24UD
$export PATH=%PATH%;%T24_HOME%/updater/bin
temn.tafj.runtime.directory.current = /glodev1/tafj/tafjx01/TAFJ/T24UD
Place an update in the T24_HOME/updater/updates directory and launch the updater from
T24_HOME.
Update successful for R12_DE_Inward_1_java1.6.tar : Message: Upgrade successful!
Update successful for R12_DM_Foundation_1_java1.6.tar : Message: Upgrade successful!
Update failed for R12_DW_BiExport_12_java1.6.tar : Message: Cannot open file.
Skipping F.DW.EXPORT$NAU
Output Summary:
20 files processed.
Updates not successful.
Exiting Updater...
1) Calls the TAFJRuntime API and invokes the program T24.UPDATE.INSTALLER with
arguments –installpath (directory where update lives) and –updatefile (the actual update)
2) Copies jars from the T24 component update to the directory defined in property
temn.tafj.directory.updates in tafj.properties
3) Deletes temporary directory where update was unzipped.
If one wants to bypass the Parent Installer (not suggested), one can do so by running:
t24Updater –installpath <path> -updatefile <absolute path to update>
It is possible to show the version of all TAFJ components by running the tVersion utility (under
TAFJ_HOME/bin) as shown below.
tVersion
<ivy-module version="1.0">
<info organisation="Temenos" module="TAFJ" branch="R12_ALL"/>
<dependencies>
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJCommon" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJCompiler" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJConfHelper" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJCore" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJDBImport" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJLocking" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJPackager" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJTelnetD" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJIODeamon" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJCommon" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJCore" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJIODeamon" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJTelnetD" rev="0" />
<dependency org="Temenos" branch="R12_ALL" name="FJ_TAFJBASIC" rev="0" />
</dependencies>
</ivy-module>
Afterwards, we can see how many updates processed by the TAFJ Child Installer by doing the
following in DBTools in SQL mode
The Service BNK/T24.UPDATES has to be run to release the data records of the T24 Updates.
The co-responding Batch record BNK/T24.UPDATES should have “T24.UPDATES” entered in the
DATA field.
Run the service T24.UPDATES to complete the data record updates, authorization, and other
processing that needs to take place.