Documente Academic
Documente Profesional
Documente Cultură
Riswana
1.0 Reviewed and Baselined 17-Jan-2018
Table of Contents
This section outlines new features in TAFC R10 and contains important information for
upgrading clients. If you are upgrading from an earlier release of jBASE, please read and
understand all the release information details for each release before starting the installation.
jBASE - TAFC is the new name for jBASE. This name has been introduced to ease client
understanding and avoid questions such as "I run an Oracle database, why do I need a jBASE
database". The Temenos Application Framework C Version or TAFC is the new name for the
runtime part of the jBASE product; the database portion will continue to be called jBASE.
From R10 SP23 a new component called TAFC logger is introduced. A new jBC API is
introduced which jBC programs can use to log messages in TAFC. The log files would be
created under” $TAFC_HOME/log/default” if default TAFC instance is used.
e.g.
Logger( <<LABEL>>, <<LEVEL>>, <<MESSAGE>>)
Logger("ACCOUNTS", TAFC_LOG_INFO, "Bad Number")
Transfer the archive to the target machine and untar the archive to a suitable directory.
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.
Change the “export TAFC_HOME=” statement in the .profile file to point to the TAFC_R10
release.
For example
export TAFC_HOME=/usr/tafcRxx (where your TAFC_R10 resides)
NOTE: Your profile will have 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.
The following table shows the minimum recommended Temenos components and release
numbers which are designed to run with TAFC.
RedHat Enterprise Linux 5 gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-54)
XML library
Xerces 3.0.1 and Xalan 1.11.0 are required for XML transformation within TAFC.
Java Runtime Environment (JRE) 1.6.0 is used for Java support and CALLJ functionality within
TAFC.
T24 data is separated into volatile and non-volatile and are being stored in different databases.
The non-volatile tables are used for analytical and reporting purposes and the volatile tables are
actually the transactional tables. Hence Direct Connect Drivers are enhanced to connect to
multiple databases. Config-XMLxxx utility is also enhanced to configure multiple databases. Up
to 10 databases can be configured and connected. It allows creating tables in different databases,
creating READ-ONLY tables, and configures ASSOCIATE property to the volatile table of the
database.
Before upgrading you TAFC installation please ensure you have sufficient disk space available.
If you have deployed an earlier version of the jRemote Resource Adapter (artefact jremote-ra.rar)
on a JEE application server it will be necessary to update the connection factories configured for
the resource adapter.
Connection properties host port used to specify the server hosting jAgent are not to be used
anymore and have been replaced by the following properties: hosts ports loadBalancing
These properties specify a comma-separated list of server names and port number, and also
whether connections should be load-balanced among the list of available servers.
E.g. t24-ds.xml on JBOSS:
Change
10.44.1.70
20002
to
10.44.1.70, 10.44.1.80
20002, 20003
true
Solaris Caveat regarding malloc change R10_RUNTIME_RTC123948
This change requires taking the whole TAFC R10 SP8 because this update changes to use a
better malloc subsystem in the libc library, whereas the rest of the libraries will still be linked
with the older malloc library. Using there incompatible malloc systems is a known problematic
area and is likely to cause memory issues and segmentation violations. The recommended option
is to take the full TAFC R10 SP8.
A possible workaround is to add "LD_PRELOAD=/usr/lib64/libc.so" before running TAFC
programs.
All indexes will need to be dropped and recreated due to RTC298350 when applying SP15 and
above.
In Windows platform, this change expects the directory type as “UD” while using FILEINFO to
get the statistics of a directory. For existing directory use the jchmod to convert a normal
directory to a jBASE type [UD type] directory.
TAFC logger component has multiple component dependencies. So clients are recommended to
take full pack instead of updates for R10 SP23.
The jODBC installer provided from this release need latest VS 2005 runtime installed.
http://msdn.microsoft.com/en-us/library/ms235317(v=vs.80).aspx
3. Incidents addressed in the TAFC R10 SP54 patch release
Runtime Incidents
R10_ORACLEDF_RTC2402301
4. Patches incorporated in the TAFC R10 SP54 patch release
R10_ORACLEDF_RTC2402301
Before Fix:
Type = XMLORACLE
DATABASE INFO : -
Server = Oracle
User Schema = schema1
FILE INFO : Key = VARCHAR(255) Record = XML
Table = ARCF, File = ./ARCF
AFTER FIX:
testsrv-~/cust/RTC2385186: CREATE-FILE ARCF TYPE=XMLORACLE DATABASE=DB1
SCHEMA=schema2
[ 417 ] File ARCF]D created , type = XMLORACLE
[ 417 ] File ARCF created , type = XMLORACLE
testsrv-~/cust/RTC2385186: jstat -c ARCF
Type = XMLORACLE
DATABASE INFO : -
Server = Oracle
User Schema = schema2
FILE INFO : Key = VARCHAR(255) Record = XML
Table = ARCF, File = ./ARCF