TAFC R09 Release Notes

Release Notes

Release R09 Temenos Application Framework C Version (TAFC) 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 Holdings NV.

Temenos

Page 1 of 8

Copyright 2002-2006 TEMENOS Holdings NV. All rights reserved

Release Notes Table of Contents IMPORTANT RELEASE INFORMATION.....................................................................................3 Release Highlights.................................................................................................................... 3 Release Number Standardisation.......................................................................................... 3 Component Updates.............................................................................................................. 3 TAFC Agent........................................................................................................................... 3 TAFC Resource Adapter........................................................................................................ 4 TAFC jRemote....................................................................................................................... 4 TAFC Monitor........................................................................................................................ 4 ODBC.................................................................................................................................... 4 JDBC..................................................................................................................................... 4 SQL Engine........................................................................................................................... 5 System Component Requirements........................................................................................... 5 Third party libraries distributed with TAFC................................................................................6 Internationalization library..................................................................................................... 6 XML library............................................................................................................................ 6 Java JRE library.................................................................................................................... 6 Disk Space Requirements......................................................................................................... 6 INSTALLATION OF THE SOFTWARE......................................................................................... 6 Upgrading jBASE (TAFC).......................................................................................................... 6 Amend your .profile............................................................................................................... 6 Upgrade Summary................................................................................................................ 8

Temenos

Page 2 of 8

Release Notes

IMPORTANT RELEASE INFORMATION This section outlines new features in TAFC R09 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.

Release Highlights This section provides an overview of any new TAFC components and advice regarding any components which have been replaced or deprecated.

Release Number Standardisation In the past release numbers for jBASE, T24Browser, and T24 all had different formats, making it harder for the user to insure that compatible components were installed. From R09 all components for T24 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.

Component Updates Prior to R09, a jBASE service pack was required to resolve any issue in any component. This service pack may have included unwanted changes to components the client was not interested in updating. For R09, a new update process has been introduced that gives a client the ability to find and apply ‘upgrades’ on a component basis. This means it is now possible for changes to be isolated and delivered with fewer fixes and for specific components. A service pack installation will still be available, but on the whole should not be required.

TAFC Agent From R09, a server side agent process has been introduced to allow various client drivers to connect to the Temenos Application Framework over a network. The agent supports unsecured TCP/IP connections, secured SSL connections, compression with configurable threshold, and three types of authentication (none, user, and account). The JRemote client, ODBC driver, and JDBC driver all use the agent for connectivity and all benefit from the features mentioned above. Please reference the TAFC Agent User Guide for more details.

Temenos

Page 3 of 8

Release Notes

TAFC Resource Adapter From R09, a JCA 1.5 compliant resource adapter is available for Java Enterprise Edition applications 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. This enables applications like T24 to utilise the connection pooling, security, and transaction features of application servers such as Websphere, Weblogic, and JBoss. Please reference the TAFC JCA User Guide for more details or the “Connectivity” section on the Knowledge Base.

TAFC jRemote From R09, jRemote replaces JavaOBjEX and .NETOBjEX. JRemote is a native Java or .NET API for remote applications (client/server architecture) to access the TAFC runtime. This connectivity is via the TAFC Agent and is the basis for the TAFC Resource Adapter. Please reference the TAFC JRemote User Guide for more details.

TAFC Monitor TAFC R09 has a new monitoring component and allows MW42 type information to be accessed in a Web Browser or via a Java Management Extensions (JMX) console. This component provides access to additional information about the jBC stack that was previously unavailable and is the basis of the TAFC section in the T24 monitor. Please reference the jBASE Monitoring User Guide for more details.

ODBC Open Database Connectivity (ODBC) is a standard API for accessing a database management system using SQL. Prior to R09, ODBC support in jBASE was provided by the jBASE jDP component and the Attunity Connect third party product. ODBC access to the jBASE database is now available using a native jBASE ODBC driver that connects to jBASE via the TAFC Agent. This is a fully featured ODBC driver that can be used from Excel, Crystal Reports, and many other popular Windows client applications. Please reference the jBASE ODBC User Guide for more details. Please see the “SQL Engine” section for details of support SQL syntax.

JDBC Java Database Connectivity (JDBC) is the Java standard API for accessing a database management system using SQL. Prior to R09, JDBC support in jBASE was provided by a jBASE JDBC driver that connected to jBASE via the JavaOBjEX server. This jBASE JDBC driver is a Type 4 JDBC 2.0 compliant driver that connects to jBASE via the TAFC Agent. This is a fully featured JDBC driver that can be used in Java Standard Edition and Java Enterprise Edition applications. Please reference the jBASE JDBC User Guide for more details. Please see the “SQL Engine” section for details of support SQL syntax.

Temenos

Page 4 of 8

Release Notes

SQL Engine The jBASE SQL Engine (jSQL) has been enhanced to support data modification (INSERT, UPDATE), data definition (CREATE TABLE, ALTER TABLE, DROP TABLE), database meta data (DESCRIBE) and has some support for simple JOINs. In R09, jSQL has also introduced the concept of an SQL catalog. The SQL catalog provides the ability to map SQL valid table names to jBASE filenames. This is useful when an application, such as T24, uses non SQL characters in its file names. TAFC R09 supplies an rdbmsCatalog routine to populate the catalog from the VOC. Please reference the jBASE SQL User Guide for more details.

JAuthenticate From R09, JAuthenticate is no longer supported. It is recommended that clients use Java Authentication and Authorisation Service (JAAS) if Pluggable Authentication Module (PAM) or Active Directory (via LDAP) services are required.

JDP From R09, the jBASE Data Provider (jDP) and Attunity Connect are no longer supported. The jDP component has been replaced by the native jBASE ODBC and JDBC drivers.

System Component Requirements The following table shows the minimum Temenos components and release numbers which are designed to run with TAFC. Component

Release

Platform

Temenos Application Framework C Version TAFC

R09 GA

Supported Operating Systems Windows Server 2003 (64 bit Only) RedHat Linux AS5 AIX 5.3 Solaris 10 Sparc HPUX Itanium2 11.31 V3

Oracle Direct Connect

R09 GA

Minimum and recommended 11gR1

DB2 Direct Connect

R09 GA

Minimum version 9.5

MSSQL Direct Connect

R09 GA

Minimum and recommended SQL Server 2008

Temenos

Page 5 of 8

Release Notes Platform

Compiler version

AIX 5.3

IBM XL C/C++ v8.0.0.20

Windows 32 bit (Internal)

Visual Studio.Net 2005

Windows 64 bit

Visual Studio.Net 2005

RH Linux AS5

gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)

HP Itanium2 11.31 V3

HP C/aCC++ B3910B A.06.22

Solaris 10 Sparc

Sun Studio 11

Third party libraries distributed with TAFC Internationalization library ICU 4.0 is required for Locale, Timezone and Multi Byte character set support. This version of ICU allows a client to download updated locale and timezone information from the ICU home page. http://site.icu-project.org/

XML library Xerces 2.7.0 and Xalan 1.10.0 are required for XML transformation within TAFC. Please note, Xalan is not available for Windows 64 bit platforms at this time.

Java JRE library Java Runtime Environment (JRE) 1.5.0 is required for CALLJ functionality within TAFC.

Disk Space Requirements Before upgrading you TAFC installation please ensure you have sufficient disk space available.

INSTALLATION OF THE SOFTWARE Transfer the archive to the target machine and untar the archive to a suitable directory.

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

Temenos

Page 6 of 8

Release Notes

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

Temenos

Page 7 of 8

Release Notes

Upgrade Summary 

Check that the TEMP.RELEASE is pointing to the correct upgrade path.



Run T24.BUILD.LIBRARIES (logout and login with a new session)



Run UpdateMD (Only required when a new version of TAFC is installed)



Logout and login with a new session



Run T24.PRE.RELEASE(logout and login with a new session)

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

Respond to the Model Bank question appropriately.



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 record BNK/T24.UPGRADE.



Authorise any CONVERSION.PGMS records.



Initiate the service RUN.CONVERSION (TSM must also be run)



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.

Temenos

Page 8 of 8