TEMENOS T24

Browser Installation and Configuration

User Guide

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.

Copyright 2007 TEMENOS Holdings NV. All rights reserved.

Browser Installation and Configuration

Table of Contents
Introduction .............................................................................................................................................. 4
Application Overview ........................................................................................................................... 4
ARC Internet Banking .......................................................................................................................... 4
Upgrading Browser / ARC-IB .................................................................................................................. 5
Before Upgrading ................................................................................................................................. 5
After Upgrading .................................................................................................................................... 5
Version Information ................................................................................................................................. 6
Software Installation & Configuration ...................................................................................................... 8
Installing T24 Browser Web Server Software – WAR File................................................................... 9
Java Connection Agent and Java Message Service)............................................................................ 10
Overview ........................................................................................................................................ 10
Pre-Requisites ................................................................................................................................ 10
jBase Agent .................................................................................................................................... 17
For more information please refer to the jBase jAgent User Guide. ..................................................... 17
Configuring ‘browserParameters.xml’ ................................................................................................ 19
Configuring Web Caching .................................................................................................................. 24
What Should be Cached ? ............................................................................................................. 25
Configuring ‘loginPageLinks.xml’ ....................................................................................................... 26
Configuring ‘branchParameters.xml’.................................................................................................. 27
Configuring ‘branchStrings.xml’ ......................................................................................................... 28
Installing T24 HelpText and Online Documentation .......................................................................... 29
Configuring Browser Logging ............................................................................................................ 30
Server Side Logging ....................................................................................................................... 30
Client Side (JavaScript) Logging .................................................................................................... 31
Configuring Web Application Parameters .......................................................................................... 32
Configuring BROWSER.PARAMETERS > SYSTEM ........................................................................ 34
Attributes ........................................................................................................................................ 34
Configuring Microsoft Internet Explorer (IE) ...................................................................................... 48
Configuring Firefox 2.0 to open Tab Windows .................................................................................. 48
Configuring Firefox to use Multiple Sessions..................................................................................... 48
Browser Status Bar Information ......................................................................................................... 48
Functional Configuration ....................................................................................................................... 50
OFX configuration .............................................................................................................................. 50
Keep alive and Auto Hold Configuration ............................................................................................ 51
Header Text Configuration ................................................................................................................. 52
Print header and footer configuration ................................................................................................ 53

TEMENOS T24 User Guide Page 2 of 58

Browser Installation and Configuration

Print header and footer configuration ................................................................................................ 53

Session Persistence .............................................................................................................................. 54
Troubleshooting ..................................................................................................................................... 55
Packet Transmission Errors ............................................................................................................... 55
Cannot find Helptext .......................................................................................................................... 56
Cache-Control: ................................................................................................................................... 57
403 (‘unauthorized’) Errors ................................................................................................................ 58

TEMENOS T24 User Guide Page 3 of 58

Browser Installation and Configuration

Introduction
Application Overview
The T24 Browser product as delivered comprises of a number of sub-components:
• Web Server software – in the form of a Web Archive (WAR) file.
• T24 software – as part of a main T24 release.

Each of these sub-components can be run on a single machine, or on separate machines depending
on the client’s configuration and performance considerations. Please refer to the Version Information
section of this guide for supported web servers. These products should be pre-installed and
configured as per the manufacturer’s instructions. See the Version Information section of this
document for information on all of the products required by T24 Browser.

T24 Browser requires a number of Temenos products installed prior to installation:

• T24
• jBASE
• T24 Connector

In addition a number of third-party products are required:

• A Browser (e.g. Microsoft Internet Explorer, Firefox, etc.).
• Java SDK to be installed on the Web Server.
• Web Server software (e.g. Apache Tomcat, IBM WebSphere, etc.).

ARC Internet Banking

The ARC Internet Banking (ARC-IB) product uses the T24 Browser product as a base.
ARC-IB contains a number of additional parameters, as defined in the browserParameters.xml file.
These are documented in this document.
ARC-IB product contains a number of additional security features to ensure that T24 Browser is
secure for internet access. These are documented in the T24 Browser Security user guide.
For further details on the functionality of ARC-IB please refer to the ARC Internet Banking user guides.

Multiple T24 Browser configurations may access a single T24 server, each hosted on a separate
server machine configured and secured as appropriate. This allows bank employees *using T24
Browser) and internet banking users (using ARC Internet Banking) to use the same instance of T24
(simultaneously). In this scenario, it is unlikely that any versions & enquiries written for internal use
would be exposed on the internet and vice versa.

TEMENOS T24 User Guide Page 4 of 58

Browser Installation and Configuration

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-instantiate any backed-up files.
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 T24 User Guide Page 5 of 58

Browser Installation and Configuration

Version Information
The following table details the minimum versions of software required to run T24 Browser:

Product Versions

Product Minimum Version Description

T24 core product, including T24 Browser server product.
R06
T24 Available from Temenos Distribution.
R08 recommended
Mandatory.
T24 database product.
5.0
JBASE Available from Temenos Distribution.
5.1 recommended
Mandatory.
Connection software allowing connection between the
1.3.2 web server and T24.
T24 Connector
Server 1.5.2 recommended Available from Temenos Distribution.
Mandatory.

A browser Client browser software.

(Microsoft IE - 7.0 Available from http://www.microsoft.com/.
Internet Explorer
or Mozilla Firefox - 2.0 Optional – at least one browser client to be installed.
FireFox)

Netscape These browser products are not supported as a client

Navigator Browser.
Not supported
Opera
Safari
Java Software Development Kit to be installed on the Web
Server platform.
5.0 (1.5.0) Available
Sun Java SDK
from http://java.sun.com/javase/downloads/index_jdk5.jsp.
Mandatory – may be delivered as part of the web server
product.
Web Server product.
Available from http://jakarta.apache.org.
4.0.4
Apache Tomcat Required when using the ActivIdentity 4Tress server for
5.0 recommended
authentication.
Optional – at least one web server to be installed.
5.1 Web Server / Application Server product.
IBM WebSphere
6.0 recommended Available from http://www.ibm.com/.

TEMENOS T24 User Guide Page 6 of 58

Browser Installation and Configuration

Optional – at least one web server to be installed.

Web Server / Application Server product.
BEA WebLogic 7.0 Available from http://www.bea.com/.
Optional – at least one web server to be installed.
Web Server / Application Server product.
Oracle
Application 10g Available from http://www.bea.com/.
Server
Optional – at least one web server to be installed.

TEMENOS T24 User Guide Page 7 of 58

Browser Installation and Configuration

Software Installation & Configuration

Having installed and configured the chosen web server product, the supplied T24 Browser software
requires installation.

The Browser Software is delivered as a WAR file - Web Archive for the Web Server
(“BrowserWeb.war”).

Also delivered is the following documentation:

1. Browser User Guides (as part of the T24 User Guides)
2. Details of changes made in each build of the Browser (“Browser Build Info.txt”).

TEMENOS T24 User Guide Page 8 of 58

Browser Installation and Configuration

Installing T24 Browser Web Server Software – WAR File

These instructions are to be used when installing on a standalone web server.

To install the WAR file:

1. Copy the supplied T24 Browser Web Archive file, BrowserWeb.war, to the Web Server directory
as detailed in the Web Server manufacturer’s instructions (e.g. the ‘webapps’ directory of Apache
Tomcat).
2. Start the Web Server.

When the Web Server starts, the WAR file should automatically be expanded creating a BrowserWeb
directory. If for any reason this directory is not created please consult the web server manufacturer’s
instructions on how to install a web archive file.

TEMENOS T24 User Guide Page 9 of 58

Browser Installation and Configuration

Java Connection Agent and Java Message Service)

Overview

JCA jRemote (Java Connection Agent) connectivity offers industry standard, JEE compliant,
connection that is capable of leveraging all the proprietary features of high end applications servers
such as Websphere, via a jBoss application server.

The JMS (Java Message Service) functionality uses the same JCA jRemote connection but it includes
a resilient re-try mechanism and configurable on screen time out message service especially for JMS
via a different set up configuration.

An unchanged TC Instance (TCServer) connectivity remains a connection option.

Pre-Requisites

Before the JMS connection method can be used in Browser or ARC-IB the following components must
be installed:

Component Minimum Release

Temenos Application Framework (TAFC) R09

Browser/ARC-IB R09

Application Server e.g. JBoss Must Implement J2EE Connector Architecture

Java JDK 1.5

NOTE: This guide will document the installation & configuration of T24 Browser using the JBoss
Application Server software 4.2.3.GA. If you wish to deploy T24 Browser or ARC-IB on any other
compliant Application Server then you must refer to its deployment and connectivity documentation.

JBoss Application Server

The JMS connection method can ONLY be utilized when T24 Browser/ARC-IB is installed on an
Application Server such as JBoss. JMS will NOT function under a simple web server such as TomCat.
The JBoss Application server (4.2.3.GA) must be downloaded and installed on your machine. The
JBoss Application Server can be downloaded from http://jboss.org/

TEMENOS T24 User Guide Page 10 of 58

Browser Installation and Configuration

The following is to be used as a guide for Windows installation only. For further details instructions on
how install JBoss on other platforms please consult the JBoss documentation set.

Installation on windows

Download the preconfigured JBoss from the Knowledge Base.

e.g.
jboss-4.2.3.GA-TOCFpreconfigured.zip

Simply unzip this file to your local directory ensuring that the following files are present:
• ofsmessage-ejb.jar
• t24destinations-service.xml
• jremote-ra.rar
• t24-ds.xml

Before you start JBoss ensure that your JAVA_HOME environment variable has been set:

Windows Environment Variables

Ensure that it is set to a Java jdk of 1.5 or higher. To test that the install is correct start JBoss by
running the following:
[JBoss Install Directory]\bin\run.bat
e.g.
Install Directory:\jboss-4.2.3.GA\bin\run.bat

TEMENOS T24 User Guide Page 11 of 58

Browser Installation and Configuration

A console will appear and if no errors are reported then all is OK. To close JBoss simply close
console window.

First launch of a jBoss session.

TEMENOS T24 User Guide Page 12 of 58

Browser Installation and Configuration

Deploying T24 Browser or ARC-IB war files.

JBoss supports applications deployed in two formats:

1. A packaged war file.
2. An exploded directory containing the web application, use WinZip or similar application to
unpack the Browser or ARC-IB war files.

The following instructions will install an exploded directory.

To deploy a T24 Browser or ARC-IB in jBoss copy the exploded Browser or ARC-IB war files to the
following location:

[JBoss Install Directory] \server\default\deploy

e.g.
C:\jboss-4.2.3.GA\server\default\deploy

Then rename each of these directories to have ‘.war’ at the end:

BrowserWeb.war
ARC-IB.war

Deploy directory with war files exploded and renamed.

TEMENOS T24 User Guide Page 13 of 58

Browser Installation and Configuration

browserParameters.xml

To ensure that T24 Browser or ARC-IB applications use the JMS or JCA connection method the
following must be configured in browserParmaters.xml:

To use JCA the Server Connection Method must have a value of AGENT, the value of INSTANCE will
use the TCServer connection method.

browserParameter set up to use JCA

To use JMS the parameter value JMS must be present in the Server Connection Method.

browserParameter set up to use JMS

JMSConnectionTimeout

This parameter determines the amount of seconds the server has to be disconnected or the amount of
processing time has to elapse before a timeout error message is displayed on screen in Browser and
ARC-IB.
This parameter only functions when JMS is the selected Server Connection Method.

TEMENOS T24 User Guide Page 14 of 58

Browser Installation and Configuration

t24-destinations-service.xml (For JMS only)

Check that MS queues have been created in the jboss-4.2.3.GA\server\default\deploy directory you
will find a file called “t24‐destinations‐service.xml”. The example below defines two queues called
“t24OFSQueue” and “t24OFSReplyQueue”:

<server>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=t24OFSQueue">
<depends optional‐attribute‐name="DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=t24OFSReplyQueue">
<depends optional‐attribute‐name="DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>

Both queues deployed in t24-destinations-service.xml

TEMENOS T24 User Guide Page 15 of 58

Browser Installation and Configuration

T24-ds.xml

The t24-ds.xml file (T24 Data Source) will configure the port numbers, server name (IP) and
OFS.SCOURCE settings to be used by T24 Browser or ARC-IB.

Set your Server name (IP Address), Port Number and OFS.SOURCE ID, denoted by the red boxes.

Other Parameters

More information about other parameters can be found here:

http://www.jboss.org/community/docs/DOC-9328

TEMENOS T24 User Guide Page 16 of 58

Browser Installation and Configuration

jBase Agent

For further information of the jBase Agent refer to its documentation.

Launching the jBase Agent

(jbase_agent can be replaced with the command tafc_agent the functionality will be the same)
To start the jBase Agent you will need to go to the jshell and type:

jsh> jbase_agent –p [PORT_NUMBER]

e.g.
jsh> jbase_agent –p 7001

jbase_agent launched

Once the jbase_agent (tafc_agent) has been launched and JBoss is started you will be able to login to
T24 or ARC-IB in the normal manner.

For more information please refer to the jBase jAgent User Guide.

TEMENOS T24 User Guide Page 17 of 58

Browser Installation and Configuration

Finally launch your BROWSER or ARC-IB URL and login.

BROWSER sign on page launched.

Toolbox

No changes need be carried out to allow toolbox to connect to the T24 server, simply follow existing
connection directions.

TEMENOS T24 User Guide Page 18 of 58

 Browser Installation and Configuration

Configuring ‘browserParameters.xml’
Once the WAR file has been expanded, the ‘browserParameters.xml’ file found in the created T24
Browser directory requires configuring. This XML file contains a number of parameters used to
configure the connection to the T24 server and the web server servlet. The settings are as follows:

Parameter Name Description Values

Product Specifies the configuration of the BROWSER
Browser product installed.
ARC-IB
This has been set at build time and
should not be changed.
If the parameter is not present then the
system will default to standard
BROWSER mode.
Server Connection Method Specifies how the web server INSTANCE
communicates to the T24 host machine.
TAG
This is by using the T24 Connector
product in one of two ways : an instance
environment or TAG server
Instance Specifies the ‘instance’ of a Connector As defined in
environment to use for connections. An ‘browserConnection.xml’.
‘instance’ defines a set of channels to be
used by the Connector.
This is only used if the ‘Server
Connection Method’ parameter is set to
‘INSTANCE’.
TAG_MASTER_URL This is the URL to the TAG Master
Node.
*Refer to TAG Reference Guide and
TAG Quick Start Guide for TAG server
installation and settings
TAG_COMPONENT_NAME The TAG component name to DefaultTBrowserReceiver
communicate with.
*Refer to TAG Reference Guide and
TAG Quick Start Guide for TAG server
installation and settings
TAG_AGENT_NAME This is the TAG agent name to
communicate with.
*Refer to TAG Reference Guide and
TAG Quick Start Guide for TAG server
installation and settings
Branch Whether this Web Server is a Branch or YES
not.
NO (default)
Set to YES when using the Branch
Resilience Module and the web server
being configured is a Branch.

TEMENOS T24 User Guide Page 19 of 58

 Browser Installation and Configuration

TC_TIME_OUT The T24 Connector timeout value.

Use Transformer This option is no longer available as YES
from Browser version 2.0 onwards.
NO (recommendation)
Default is server transformation.
AllowResize Determines whether T24 Browser YES (recommendation)
windows should be resized and
NO
repositioned when launched.

TEMENOS T24 User Guide Page 20 of 58

 Browser Installation and Configuration

Web Server Skins List of the ‘skins’ resident on the web As defined in
server platform. These control the
BROWSER.PARAMETERS.
browser look and feel. Skin names are
separated by a ‘:’ character. Valid skin
names are defined in the T24
application BROWSER.PARAMETERS -
SYSTEM record.
Skins currently delivered are :- arabic,
arc-ib, and default.
CALL_CENTRE_CLASS The Call Centre class to use for the
Browser API.
noFrames Specifies the default usage of frames / YES (ARC-IB)
no-frames functionality.
NO (recommendation)
Individual composite screens can
specify whether they should use frames
(or not).
This property is used to determine
whether to use frames for those
composite screens which have not
expressed a preference in the
EB.COMPOSITE.SCREEN definition.
clientLogging Determines whether client side YES
(JavaScript) logging should be enabled.
NO (recommendation)
See the ‘Logging Configuration’ section
(below) for more details.
useTabbedMenu Specifies the default rendering for YES (ARC-IB)
menus.
NO (recommendation)
Individual menus can specify whether
they should rendered as tabs or using
the traditional tree structure.
This property is used to determine which
rendering to use for menus which have
not expressed a preference.
useInternalObfuscation Specifies whether 'internal obfuscation' YES (ARC-IB)
should be used.
NO (recommendation)
'Internal obfuscation' ensures that
version and enquiry names are 'mixed
up' before they make it to the client (for
security).
It is only valid in the ARC-IB
configuration.

TEMENOS T24 User Guide Page 21 of 58

 Browser Installation and Configuration

useExternalObfuscation Specifies weather 'external obfuscation' YES (ARC-IB)

should be used.
NO (recommendation)
'External obfuscation' ensures that Java
script is 'mixed up' before making it to
the client (for security).
It is only valid in the ARC-IB
configuration.
suppressMissingHelp Determines whether an error message YES (ARC-IB)
should be displayed if a help file is
NO (recommendation)
missing.
This may be acceptable for internal
BrowserWeb configurations, but not for
ARC-IB deployments.
cleanPrint Determines whether printing will print YES (ARC-IB)
the entire HTML page, or just any
NO (recommendation)
versions or enquiries that are on that
page.
Note that this is only supported when
noFrames is set to NO.
useKeepaliveHandling Determines weather the keep alive YES (ARC-IB)
functionality is enabled.
NO (recommendation)
Keep alive ensures that a user does not
get logged out of Browser for as long as
they continue to use the application.
For more information, see the ‘Keep
Alive and Auto Hold Configuration’
section, below.
useAutoHoldDeals Determines weather the auto hold YES (recommendation)
functionality is enabled.
NO (recommendation)
The auto hold functionality ensures that
changes made to a version are sent to
the server on a regular bases, and the
version is placed into the hold state for
later retrieval.
For more information, see the ‘Keep
Alive and Auto Hold Configuration’
section, below.
stripFrameToolbars Determines whether toolbar buttons and YES (ARC-IB)
dropdown are stripped out of contract
NO (recommendation)
applications.
Note that this is a placeholder function,
required until this functionality is
implemented in T24.

TEMENOS T24 User Guide Page 22 of 58

 Browser Installation and Configuration

enableHotfields Determines whether hotfields are YES (recommendation)

allowed.
NO (ARC-IB)
Note that this is a placeholder function,
required until this functionality is
implemented in T24.
T24XmlFilterRegEx Defines a filter through which any XML A regular expression
that comes back from T24 is passed.
Any text that matches the regular
expression is removed. This is a security
measure, to protect against cross site
scripting attacks (e.g. spurious '<script>'
tags).
This property should usually be left at it's
default value.
stripUserName Determines whether the T24 user name YES (ARC-IB)
is included in the HTML or XML sent to
NO (recommendation)
the client.
This is as a security measure.
See the security selection, below, for
more information.
showStatusInfo Determines whether information is NO (ARC-IB,
displayed on the browser Status Bar
recommendation)
(e.g. JavaScript function names, release
information, etc.). YES
graphDisplayType Determines whether charts will be svgObject
displayed as an SVG graphic or as a
pngImage
PNG image.
The SVG graphic supports drilldowns
but requires the user to have an SVG
viewer installed.
The PNG image supports less
functionality but can be displayed in
browsers that don't have an SVG
viewer.

TEMENOS T24 User Guide Page 23 of 58

Browser Installation and Configuration

Configuring Web Caching

T24 Browser can now indicate to Web browsers how long to cache certain 'static' web resources like
images, css files and JavaScript files. This can improve page load times.

This is configured inside the “WEB-INF/web.xml” file as described below.

How Long to Cache For ?

The MaxAgeInSeconds variable defines how long the content should be held locally in the user’s web
cache after which the cache will be cleared.
The default value is 1 day (86400 seconds).
To change this, change the number of seconds in the <param-value> tag.

The filter MaxAgeInSeconds parameter from web.xml

TEMENOS T24 User Guide Page 24 of 58

Browser Installation and Configuration

What Should be Cached ?

Only infrequently changing (static) content like images, css files, JavaScript files etc should be cached.
web.xml provides a mechanism for indicating which directories and file extensions should be cached
using the '<filter-mapping>' element.
The <url-pattern> element defines which resources will be stamped with an 'expiry time' indicating how
long the web browser should cache them for.

Some examples of url-pattern values could include :

/plaf/* All files in the plaf directory (contains images and css files)
*.gif All files with a .gif extension located under the web root (BrowserWeb) directory

Multiple <filter-mapping> elements can be defined.

Sensitive information should not be cached in web browsers as this would create a security risk to
users. So although “*/*” would try to cache all information it should not be used. Moreover it may not
work quite as expected.

The filter mapping parameter from WEB.XML

Please note that changes to web.xml require the web server to be restarted to take effect.

TEMENOS T24 User Guide Page 25 of 58

Browser Installation and Configuration

Configuring ‘loginPageLinks.xml’
Once the WAR file has been expanded, the ‘loginPageLinks.xml” file found in the created T24 Browser
directory can be configured if required. This XML file contains a list of links that will dynamically be
added to the Login page of T24 Browser (not ARC-IB). These will be displayed on the right hand side
of the login page.
The file contains “parameterName” and “parameterValue” tags which correspond to the hyperlink text
and hyperlink URL respectively.
The default file delivered contains the following 2 links :-
<parameter>
<parameterName>Temenos Web Site</parameterName>
<parameterValue>http://www.temenos.com</parameterValue>
</parameter>
<parameter>
<parameterName>T24 Portal</parameterName>
<parameterValue>../portal/portal.htm</parameterValue>
</parameter>

These are displayed as 2 hyperlinks :- “Temenos Web Site” and “T24 Portal”.

TEMENOS T24 User Guide Page 26 of 58

 Browser Installation and Configuration

Configuring ‘branchParameters.xml’
This configuration file only requires configuring if the Branch Resilience (BR) T24 module is being
used, and the Browser web application is being installed at a branch.
For full details on configuring the Branch Resilience module for T24 please refer to the user guide for
that module.
Once the WAR file has been expanded, the ‘branchParameters.xml’ file found in the created T24
Browser directory under “WEB-INF/conf/branch” requires configuring. This XML file contains a
number of parameters used to configure the connection to the T24 Central server and the T24 Branch
server. The settings are as follows:

Parameter Name Description Values

Branch Id The Id of this branch. For example : “LONDON”.
This must match a branch Id defined in
the T24 table BR.BRANCH.
Online Instance The name of the T24 Connector An instance defined in the
Instance to use when the main T24 T24 Connector file
server is online (i.e. the connection to ‘conf/browserConnection.xml’.
use to communicate with the T24
Central server).
When this instance is in use T24
Browser requests will be directed to the
main T24 server.
Offline Instance The name of the T24 Connector An instance defined in the
Instance to use when the main T24 T24 Connector file
server is offline (i.e. the connection to ‘conf/browserConnection.xml’.
use to communicate with the T24
Branch server)
When this instance is in use T24
Browser requests will be directed to the
branch T24 server.

TEMENOS T24 User Guide Page 27 of 58

Browser Installation and Configuration

Configuring ‘branchStrings.xml’
This configuration file only requires configuring if the Branch Resilience T24 module is being used,
and the Browser web application is being installed at a branch.
Once the WAR file has been expanded, the ‘branchStrings.xml’ file can be found in the created T24
Browser directory under “WEB-INF/conf/branch” requires. This XML file contains a number of strings
used by the T24 Browser product. For example, error messages and page titles. These only require
changing if translations are required for a specific branch. The settings are as follows:

Parameter Name Description

BRANCH_ADMIN_LOGIN_TITLE The title to be displayed on the Branch
Administrator Login screen.
ERROR_STATE_CHANGED The message to be displayed when a
user runs a request following a state
change. The user is requested to re-
authenticate them self.
ERROR_NOT_BRANCH_SERVER The error message to be displayed
when attempting to perform branch
operations when the web server is not
running in Branch mode.
ERROR_NOT_BRANCH_ADMIN The error message to be displayed
when a command is run that requires
the user to have signed in as a Branch
Administrator.

TEMENOS T24 User Guide Page 28 of 58

Browser Installation and Configuration

Installing T24 HelpText and Online Documentation

In order to use the integrated HelpText and Online Documentation in T24 Browser, the relevant
released documentation must be installed on the web server.

For full information on how to setup, configure and use the T24 HelpText and Online
Documentation System please refer the to the ‘HelpText and Online Documentation’ user guide
under the System Administration section.

TEMENOS T24 User Guide Page 29 of 58

Browser Installation and Configuration

Configuring Browser Logging

Server Side Logging
In case of any problems occurring in T24 Browser, a logging mechanism exists that can be used to
obtain information regarding the status of the system. The logging system used by T24 Browser, by
default, wraps the Apache “log4j” mechanism.
Apache “log4j” allows logging of messages to be turned on and off for different “packages”.
The level and severity of messages being logged can be configured as: OFF, FATAL, ERROR, WARN,
INFO and DEBUG. Setting a packages category level to OFF will ensure no messages are logged,
whereas a setting of DEBUG will log detailed messages for use in debugging.

Log settings are defined in the file:

BrowserWeb\WEB-INF\classes\log4j.properties
In this file, logging for the root package is defined as follows:
log4j.logger.com.temenos=ERROR, console
This sets the log level to ERROR, and directs output to the console.
To set the log level to info, and direct output to a log file instead of the console, use:
log4j.logger.com.temenos=INFO, logFile

More specific log levels can be set for lower level packages.
For example:
log4j.logger.com.temenos.t24browser=WARN
log4j.logger.com.temenos.t24browser.servlets=DEBUG
The first of these entries sets the log level of the ‘com.temenos.t24browser’ package (and it’s
subpackages) to WARN.
The second entry would override the log level for the ‘com.temenos.t24browser.servlets’ package (and
any subpackages) to DEBUG.
The packages match the Java packages in the code; usually just the root level described above
should be changed (unless directed otherwise by the development team).

As can be seen, log messages can be directed to the console or a log file. Those directed to the
console end up in the web server logs (whose location varies depending on the web server); the
location of the log file used when specified is also set in log4j.properties.
Although there is unlikely to be a need to do so, it is possible to use the standard Java Logging APIs
(part of the Java distribution) in place of log4j. In order to do so, locate the file:
<install-dir>\WEB-INF\classes\META-
INF\services\com.temenos.t24.commons.logging.LoggerFactory
And, replace the line that reads:
com.temenos.t24.commons.logging.impl.Log4jLoggerFactory
With:
com.temenos.t24.commons.logging.impl.JavaLoggerFactory

TEMENOS T24 User Guide Page 30 of 58

Browser Installation and Configuration

Client Side (JavaScript) Logging

JavaScript logging is disabled by default.
It may be enabled by setting the ‘clientLogging’ property in browserParameters.xml to ‘YES’.
The logging is based on Firebug (see: http://www.getfirebug.com/logging.html).

If the (Firefox only) Firebug plug-in is installed, logging will appear in its console (at the base of the
Firefox screen).
In IE, or Firefox without the plug-in installed, it can be viewed via firebug lite by pressing F12 or
Ctrl+Shift+L (see: http://www.getfirebug.com/lite.html).

TEMENOS T24 User Guide Page 31 of 58

Browser Installation and Configuration

Configuring Web Application Parameters

Every J2EE web application has a web.xml file located in the WEB-INF directory.
The structure of the file is standard, and does not differ between web servers.

The web.xml file is used to:

• Specify the URLs to associate with servlets
• Identify the location of the file to use for reading browserParameters
o by default, this is browserParameters.xml; although this may be changed to allow
easy configuration switching.
• Configure ARC-IB filters:
o AuthenticationFilter
ƒ Implements integration with a third party authentication server; see below.
If the AuthenticationFilter is enabled, then the AuthenticationListener (below)
must also be enabled.
o ObfuscationServletFilter
ƒ Provides some level of security; see below.
o VersionEnquiriesFilter
ƒ Provides some level of security; see below.
o BrowserServletFormFieldInputFilter
ƒ Provides some level of security; see below.
o HelpServletFormFieldInputFilter
ƒ Provides some level of security; see below.
• Configure ARC-IB listeners
o AuthenticationListener
o Implements integration with a third party authentication server; see below.
If the AuthenticationFilter (above) is enabled, then the AuthenticationListener must
also be enabled.
• Configure authentication
o Determine which files are protected

TEMENOS T24 User Guide Page 32 of 58

Browser Installation and Configuration

• Configure Graph display format

o GraphSessionListener.
ƒ This is an optional HttpSessionListener that will clear 'used' files from
the .../work/GraphImages folder at the end of a user’s session. It is only
recommended to use this if displaying graphs as .png images rather than SVG
graphics. To enable the GraphSessionListener, uncomment the associated
<listener> element.
o GraphServlet
ƒ In ARC-IB the GraphServlet is disabled by default but must be enabled to
display graphs and charts as pngImages instead of svgObjects. To enable the
GraphServlet, uncomment the associated <servlet> and <servlet-mapping>
elements.

Each configurations web.xml file is set up as appropriate, and it is unlikely that it will need to be
changed.
If it does need to be changed for any reason, or to get a better understanding of its content, please
refer to the comments in the file itself.

TEMENOS T24 User Guide Page 33 of 58

Browser Installation and Configuration

Configuring BROWSER.PARAMETERS > SYSTEM

T24 is shipped with a SYSTEM record in the BROWSER.PARAMETERS application in T24. The fields
for this application are described in the helptext for BROWSER.PARAMETERS.
One field in particular should be verified during the installation. In particular, TELLER should be listed
as one of the non standard applications in the NON.STD.APPS field of this record. If TELLER is not
listed, then Browser will not be forced to check that a users till is open every time a new TELLER
record is opened – the check will only be run before the record is committed.

Attributes
Attributes set in the BROWSER.PARAMETERS will be applied across the system please note that the
TCServer will need to be stopped and restarted after this field has been edited and authorised.
The attributes are described below and described in the following sections :-

BROWSER.PARAMETERS with ATTRIBUTES and all options.

TEMENOS T24 User Guide Page 34 of 58

Browser Installation and Configuration

CHECKFILE.ENRICHMENT

Check File Enrichments will give the User enrichment text for a field after the focus has been moved
away from it, this enhancement will work for all field listed in the STANDARD.SELECTION System
fields.

To enable the system to allow Check file enrichments the SYSTEM record in
BROWSER.PARAMETERS will need to be edited so that the Attributes field has
CHECKFILE.ENRICHMENT flagged up.

Check File Enrichment

This will by default allow all users to use Check File Enrichments functionality, this functionality is
automatically applied and will provide enrichments to fields associated with tables and that are
listed on the STANADARD.SELECTION record.

When populating a valid field the enrichment will be displayed when the focus is shifted off that field by
either the Tab key or left clicking on another field.

TEMENOS T24 User Guide Page 35 of 58

Browser Installation and Configuration

Enrichment focus

If it is decided to withhold this functionality from a User, that User can be exempted by selecting the
NO.CHECKFILE.ENRICHMENT option in the Attributes filed in the BROWSER.PREFERENCES
record for that User. Other Users will still be able to utilise this functionality.

CHECKFILE.ENRICHMENT Setting

TEMENOS T24 User Guide Page 36 of 58

Browser Installation and Configuration

MAXIMIZE.WINDOWS

With this setting all Browser windows will be opened are in the maximized state automatically.
This is a system wide setting and even if a specific window is resized to a desired state when it’s
reopened again the screen will be maximised.

MULTILINE.VERSION.HEADERS

Selecting the ‘MULTILINE.VERSION.HEADERS’ attribute will cause all header lines defined in a
VERSION record to be displayed when the version is opened, as in the image below :-

MULTILINE.VERSION.HEADERS Setting

Using Multi-line Version Headers

TEMENOS T24 User Guide Page 37 of 58

Browser Installation and Configuration

Otherwise, only the first line will be displayed, as in the image below:

Disabling Multi-line Version Headers

If no header lines are defined, the application will display the version description or name and
application.

TEMENOS T24 User Guide Page 38 of 58

Browser Installation and Configuration

NO.AUTOCOMPLETE

Autocomplete feature in Internet explorer can be disabled for T24 Browser by setting the ATTRIBUTE
NO.AUTOCOMPLETE on BROWSER PARAMETERS table. SYSTEM record should be amended as
showed below :-

NO.AUTOCOMPLETE Setting

Refer to Internet Explorer’s user guide for more information about AUTOCOMPLETE feature.

TEMENOS T24 User Guide Page 39 of 58

Browser Installation and Configuration

NO.LANG.IN.VERSION

The NO.LANG.IN.VERSION attribute allows language fields on Versions to be displayed without the
language MNEMONIC code being displayed as a prefix to the field prompt text. This is particularly
useful when there is only one language defined in T24. However, when multiple languages are
defined this may cause some confusion so should only be used sparingly.
SYSTEM record should be amended as showed below :-

NO.LANG.IN.VERSION Setting

TEMENOS T24 User Guide Page 40 of 58

Browser Installation and Configuration

If a version is run with the NO.LANG.IN.VERSION attribute set then the result will be as follows :-

Language Mnemonics Selection Shown

Otherwise the version will be displayed as follows with language mnemonics on display :-

Language Mnemonics Shown

TEMENOS T24 User Guide Page 41 of 58

Browser Installation and Configuration

NO.AUTO.REFRESH

The NO.AUTO.REFRESH attribute can be used to remove the Auto Refresh field on the enquiry
selection screen. This means that the user cannot have an enquiry automatically refresh after a pre-
defined time.

NO.AUTO.REFRESH Setting

TEMENOS T24 User Guide Page 42 of 58

Browser Installation and Configuration

NO.SELECTION

The NO.SELECTION attribute can be used to display enquiry results screens without the enquiry
selection section being displayed at the bottom of the screen. This can be particularly useful when
screen space is limited (i.e. in a composite screen frame).

NO.SELECTION Setting

If an enquiry is run with a specific criteria and with the NO.SELECTION attribute set then the result will
be as follows :-

No Enquiry Selection Shown

TEMENOS T24 User Guide Page 43 of 58

Browser Installation and Configuration

Otherwise the enquiry will be displayed as follows with the section on display :-

Enquiry Selection Shown

TEMENOS T24 User Guide Page 44 of 58

Browser Installation and Configuration

NO.SORT.OPTIONS

T24 Browser always sorts options displayed in combo boxes on its screens. However, in particular
with Local Reference fields that use a Vetting Table to provide values, it may be desirable to display
the options in the order in which they are defined.

The "NO.SORT.OPTIONS" attribute in BROWSER.PARAMETERS allows Vetting Table options to

be displayed in the order in which they were defined in LOCAL.TABLE.

NO.SORT.OPTIONS Setting

TEMENOS T24 User Guide Page 45 of 58

Browser Installation and Configuration

If a Local Reference field Vetting is defined as follows :-

Vetting Table Definition

and the attribute NO.SORT.OPTIONS is set, then the field will be displayed as follows :-

Options Unsorted

TEMENOS T24 User Guide Page 46 of 58

Browser Installation and Configuration

Otherwise the field ill be displayed sorted as follows :-

Options Sorted

TEMENOS T24 User Guide Page 47 of 58

Browser Installation and Configuration

Configuring Microsoft Internet Explorer (IE)

T24 Browser uses popups to submit requests to the T24 server. In particular, these are used to
unlock records when windows are closed. Therefore, when using T24 Browser please ensure that the
Web Server is added in the allowed popups list in Microsoft Internet Explorer. Failure to do this will
cause the Browser to have problems.

Configuring Firefox 2.0 to open Tab Windows

Firefox users who want to set up their windows to open in tabs must do the following:
1. In the browser url field for Firefox, type about:config
2. Make sure these are your settings for the following values
browser.link.open_external 3
browser.link.open_newwindow 3
browser.link.open_newwindow.restriction 0
All new windows will now open in a new tab.

Configuring Firefox to use Multiple Sessions

By default, each new instance of Firefox will use the same web session. This will lead to security
violations if a user attempts to sign onto multiple instances of the browser using different users.
The solution is to create a new Profile for each additional web session that is required and execute
this profile when Firefox is run.
To create a new profile, see knowledgebase here:
http://kb.mozillazine.org/Creating_a_new_Firefox_profile_on_Windows

Once the new profile is created, a shortcut should be made with new parameters passed in to execute
the profile e.g -P "profilename" -no-remote
Further information can be found here:
http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile

Browser Status Bar Information

The Browser status bar displays information concerning the currently logged in user and the last
request status as follows :-

The information shown contains :-

1. Build Information
• The T24 Release

TEMENOS T24 User Guide Page 48 of 58

Browser Installation and Configuration

• The Browser Release

2. User name
3. Company Id
4. Bank date
5. Timing Information (in milliseconds)
• Total time to process the request
• Time in the Browser Servlet (web server)
• Time in the Temenos Connector
• Time in OFS (T24 Server)
• XML Parse time (parsing a HTTP Request in to XML)

In Firefox the status bar is not enabled by default due to its security features. To see this feature, go to
the top of the Firefox Browser and click on Tools -> Options -> Content.
Then, check the Enable JavaScript box -> Advanced and check the “Change status bar text”.

TEMENOS T24 User Guide Page 49 of 58

Browser Installation and Configuration

Functional Configuration
OFX configuration
OFX (Open Financial Exchange) is an XML based file format used by Microsoft Money, as well as
other personal finance packages.
T24 Browser makes particular use of OFX to allow ARC Internet Banking clients to download their
statements, etc.

For more information on OFX, see:

ƒ The OFX home page: http://www.ofx.net/ofx
ƒ 1-Way OFX: http://www.microsoft.com/money/fi/OFXDoc.mspx

Browser can be configured to allow a user to download enquiries in OFX.

This is achieved on an enquiry by enquiry basis, by creating a special version which is only used to
generate the OFX data.

The OFX enquiry should be a copy of the originating enquiry, but with six columns.
The order of the columns is important, and their content is mapped to the OFX fields as follows:
1. Transaction type (<TRNTYPE>)
2. Transaction date (<DTPOSTED>)
3. Transaction amount( <TRNAMT>)
4. Transaction Id (<FITID>)
5. Check (or other reference) number (<CHECKNUM>)
6. Name of payee or description of transaction (<NAME>)
Note that the column names are not important.

The new, OFX, enquiry must then be referenced from the originating enquiry:
ƒ Add a header field to the enquiry, with a name of “OFX” and a value of “OFX=<ofx-enq-
name>”.
Replace <ofx-enq-name> with the name of the new OFX Enquiry.

TEMENOS T24 User Guide Page 50 of 58

Browser Installation and Configuration

Keep alive and Auto Hold Configuration

The Keep Alive functionality ensures that a user does not get logged out of Browser for as long as
they continue to use the application.

It may be enabled (for all users) by setting the ‘useKeepaliveHandling’ property in

browserParameters.xml to ‘YES’.
By default this is disabled for T24 Browser, but is enabled by default in the ARC Internet Banking
product.
This feature is implemented by sending ‘keep alive’ or ‘heartbeat’ messages to T24 when the user
types characters into form fields, so long as the delay between their key presses is less than the T24
or session timeout specified on the server.
When the user does not type anything into a T24 field for longer than the timeout period, a message is
displayed in a dialog. This gives the user the option to remain logged in.

The Auto Hold functionality is controlled by the ‘useAutoHoldDeals’ property in

browserParameters.xml. By default this is disabled for T24 Browser, but is enabled by default in the
ARC Internet Banking product.

The auto hold functionality ensures that, along with the heartbeat message, a users key presses are
sent to the server on a regular bases. The form (version) in question will be placed into the SHLD
state for later retrieval.
Thus, if a user starts to complete a form, then closes the browser, their changes will be available for
retrieval from the hold state in future when they log on.

TEMENOS T24 User Guide Page 51 of 58

Browser Installation and Configuration

Header Text Configuration

It is possible to respond to a user making a selection in a tabbed menu.
An example of this is the ‘header text’ functionality; text on the screen at all times that describes the
version or enquiry that is currently on display.
This is implemented outside of T24, in JavaScript, in an HTML page which is loaded into a Composite
Screen for ARC Internet Banking users.
In order to customize the text that is displayed, a file with the same name as the menu item in question
should be added to the following directory:
<install-dir>/modelbank/help/ARC/headertext
This text is read via the T24 help mechanism (which allows the use of subdirectories for localization)
when a link on the menu is selected.
For implementation details, see the sample file header-bottomleft.html.

TEMENOS T24 User Guide Page 52 of 58

Browser Installation and Configuration

Print header and footer configuration

When the ‘cleanPrint’ functionality is enabled in browserParameters.xml, it is possible to print a
custom header and footer along with the data.
The header is the contents of an html element with the id ‘printHeader’. If such an element is present
on the page, it is invisible on screen and only used in the printed output.
Likewise, the footer is an HTML element with an id of ‘printFooter’.
To customize the header and footer, ensure the relevant HTML element is present (add it if not), and
change its content as necessary.
For more details, see the sample file gen-footer.htm.

TEMENOS T24 User Guide Page 53 of 58

Browser Installation and Configuration

Session Persistence
Session persistence allows HTTP session data that is normally stored in the memory of a web server
to be written to an external store such as a database. This is required when running multiple web
servers for high availability and resilience of T24 Browser. In this scenario, sequential requests could
be directed to different web servers, therefore, session data pertinent to the user must be shared
between the web server instances.
In terms of WebSphere, the session data is written to a DB2 database (although this could also be to
an Oracle database instead).

For detailed instructions on configuring session persistence for your web server please refer to the
documentation supplied by the web server manufacturer.

TEMENOS T24 User Guide Page 54 of 58

Browser Installation and Configuration

Troubleshooting
Packet Transmission Errors
Analysis: While using glance, click the Network button to view two specific Network graphs: Packets
and Errors. The percentage of packet errors is high.

Action: While the application is running, investigate the problem using:

netstat -p tcp

Look particularly at the value of "connect requests dropped due to full queue" over time. If it's
increasing, check the value of the maximum number of TCP connections by using:

ndd -get /dev/tcp tcp_conn_request_max

to get the current value and

ndd -set /dev/tcp tcp_conn_request_max 1024

to set it to a higher value, 1024 in this example.

TEMENOS T24 User Guide Page 55 of 58

Browser Installation and Configuration

Cannot find Helptext

Analysis: Cannot find helptext when running Tomcat or any other web server as a service (on
Windows NT based systems) and the helptext is located on a remote machine.

Action: In helpParameters.xml use a full UNC (universal naming convention) path

e.g. \\machinename\sharename\folder.
In addition the machine will require the correct read/write permission on the remote machine, this can
be done as with a normal user however the username is the name of the machine where the web
server is running as a service. Notice in the screenshot below the user UKLAP-
KDEVLIN$ (EUROPE\UKLAP-KDEVLIN$), this is actually a machine.

TEMENOS T24 User Guide Page 56 of 58

Browser Installation and Configuration

Cache-Control:
Cache-Control can be applied to the web server to prevent the response being cached the browser
e.g. IE. Due to this the expired pages cannot be refreshed. This will also force the browser to prompt
the user re-send the last request to T24. This can be prevented by configuring the web server to send
the following HTTP headers.
a) Cache-Control :no-cache
b) Expires :0
For more information on this topic kindly refer to the web server documentation.

TEMENOS T24 User Guide Page 57 of 58

Browser Installation and Configuration

403 (‘unauthorized’) Errors

Analysis:
T24 returns 403 errors to the clients Browser when they are using ARC-IB.

Action:
If the versions and enquiries filter is incorrectly specified, then the versions and enquires being
accessed by the user may be blocked.
See the T24 Browser Security user guide for details of how to resolve this issue.

TEMENOS T24 User Guide Page 58 of 58