Browser Installation
Browser Installation
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.
Browser Installation
Table of Content
Table of Content ................................................................................................................................... 2
Introduction........................................................................................................................................... 3
Technical Architecture .......................................................................................................................... 4
T24 And T24 Browser ....................................................................................................................... 4
Components Of T24 Browser Installation .......................................................................................... 6
Internet Explorer ............................................................................................................................ 6
Network Dispatcher ....................................................................................................................... 6
Web Server.................................................................................................................................... 6
EJB Layer ...................................................................................................................................... 6
MQ Series...................................................................................................................................... 6
T24 Server..................................................................................................................................... 6
bnk.data directory – NFS Mounted ................................................................................................ 7
Database Server............................................................................................................................ 7
Message Flow....................................................................................................................................... 7
Message In ....................................................................................................................................... 7
Message Out..................................................................................................................................... 7
T24 Installation ..................................................................................................................................... 8
Components...................................................................................................................................... 8
Pre requisite ...................................................................................................................................... 8
Installation Procedure........................................................................................................................ 8
Configuration................................................................................................................................... 10
Introduction
The term T24 refers to ‘Temenos 24’ meaning 24 hours NON-STOP processing where by transactions
can be input while the system is running ‘Close Of Business’ (End Of DAY). For the T24 non-stop
processing to be implemented, there are a number of technical and architectural changes that have
been made. This document aims at giving an insight into the technical and architectural changes done
and also talks about the T24 Browser, an important part of T24.
The ‘Non Stop’ processing feature of T24 is available from T24 release G.14.0. As a part of this
release the following applications will support non-stop processing. The ability to use the following
applications when the system is running COB is only allowed if the product ‘NS’ (NON STOP) is
installed.
• SECURITY.MASTER
• CUSTOMER.SECURITY
• STANDING.ORDER
• DATA.CAPTURE
• SC.SETTLEMENT
• ENTITLEMENT
• CURRENCY
• FORWARD.RATES
• PERIODIC.INTEREST
• ACCT.INTERIM.CAP
• TABLE.CAPITALISE.CORR
• PAYMENT.STOP
• GROUP.CREDIT.INT
• GROUP.DEBIT.INT
• ACCT.CAPITALISATION
• ACCOUNT.STATEMENT
• GROUP.CAPITALISATION
• ACCT.STATEMENT.CHARGE
• TURNOVER.DEBIT
• TURNOVER.CREDIT
• GENERAL.CHARGE
• TRANSACTION.CHARGE
• DEBIT.INT.ADDON
• HIGHEST.DEBIT
• INTEREST.STATEMENT
• ACCOUNT.CREDIT.INT
• ACCOUNT.DEBIT.INT
• ACCOUNT.CLOSURE
• ACCOUNT.DEBIT.LIMIT
• BALANCE.REQUIREMENT
• NOTICE.WITHDRAWAL
• AC.LOCKED.EVENTS
• SEC.TRADE
• SECURITY.TRANSFER
• MG.MORTGAGE
• MG.PAYMENT
• LD.LOANS.AND.DEPOSITS
• LD.SCHEDULE.DEFINE
• FD.FID.ORDER
• FD.FIDUCIARY
• PD.PAYMENT.DUE
• PD.CAPTURE
• PRE.SYNDICATION.FILE
• FACILITY
• SL.LOANS
• SL.CHARGE
• SL.BUY.SELL
• SL.ROLLOVER
• SL.REPAYMENT.SCHEDULES
• SL.FACI.RATES
• SL.RATES.PART
• SWAP
• FRA.DEAL
Technical Architecture
T24 And T24 Browser
T24 Browser is an Intranet based browser solution, designed as an accompaniment to the existing
T24 Desktop software. It is not a replacement for Desktop, but rather a complementary product that
offers basic functionality (i.e. contract capture and enquiries), needed for large-scale implementations
- without the need to install software on client PCs. T24 Browser is a ‘light client’, which like Desktop
does not hold any business logic but does not need to be installed at any of the client machines (no
deployment required). With the advent of T24 Browser, there will exist many layers in the T24
technical architecture. These layers are built in for resilience so that there is no single point of failure
henceforth.
Network Dispatcher
HTTP RESPONSE HTTP REQUEST
Internet Explorer
This is the front end that the client will be using to access data in T24. All that the user needs to do is
to supply a ‘url’ that will enable him to connect to T24.
Network Dispatcher
This is a third party software. The job of the network dispatcher is to receive the messages from the IE,
and route it to any one of the available web servers. This is used for load balancing purposes.
Web Server
This server can have either Tomcat or Websphere installed. This server is used to publish the web
pages on to the Internet Explorer. An example would be, when a user wishes to open a version, then
the fields to be displayed and their properties are sent to the web server. The web server then creates
the web page and sends it to the user via the network dispatcher. The web server is a cluster
installation – meaning one installation of web server across multiple severs. The sessions are
persisted on to a database at the web server level. The web server holds the TC (TEMENOS
CONNECTOR) Client and the T24 Browser. The T24 Browser is the one that will parse any HTTP
request to XML request and send it for further processing. The Web Server is capable of storing
tokens that are related to each message (Tokens is discussed in detail later in this section).
EJB Layer
This is the server that contains the web services that can be published for third party systems to
access. Some amount of business logic can be built into these web services.(Please refer the
documentation on Web Services for more information on this). The message received from the Web
Server is routed through a switch/MQ series to any one of the available T24 servers for processing.
There can be multiple EJB servers.
It is vital to understand that this EJB layer is optional and is required only when web services need to
be deployed. If web services is not deployed, then this layer will be used truly for connectivity
purposes.
If the EJB Server is present, the TC (TEMENOS CONNECTOR) Client running on the Web Server will
hold the IP of the EJB Servers and route the messages to EJB Server, else they will hold the IP of the
SWITCH/MQ SERIES though which the message will be routed to the T24 servers.
MQ Series
Software that is capable of handling application specific data load.
T24 Server
This is the T24 server and there can be more than one of them. Each of these servers will contain a
separate T24 installation (minus the bnk.data directory) and jBASE installation. The OFS module
and the TC (TEMENOS CONNECTOR) server have to be compulsorily installed on each of these
servers. TC Server is the entry point into T24. It is in the T24 server, that all the business logic is held
and the actual validation of data happens at this server.
Database Server
T24 is database independent, and supports several different databases, including Oracle and DB2. It is
in this database server that Oracle/DB2/J4 is installed. This is where the T24 data will reside in XML
format. Oracle/DB2 databases support clustering and therefore a single Oracle/DB2 installation can be
done across multiple servers. J4 does not support clustering and therefore only one database server
can be used if J4 is to be used as a database. In order to make use of T24 capabilities, we would
require the database to provided online backup mechanism (taking backup when users are logged in).
Message Flow
Message In
The user initiates a request from the Internet Explorer. This will be a HTTP request. This request is
received by the Network Dispatcher and is routed to any one of the Web Servers. The T24 Browser
which resides on the Web Server parses the HTTP request to XML and passes it on to the TC
(TEMENOS CONNECTOR) Client running on the same server. The TC (TEMENOS CONNECTOR)
Client then routes the request to any one of the T24 servers. The Web Server then sends this HTTP
request to any one of the EJB servers. As mentioned above, the entry point into T24 is the TC
(TEMENOS CONNECTOR) Server. The TC (TEMENOS CONNECTOR) Server running on the T24
server then parses the XML request into OFS format and gives it to T24 (OFS) for processing. Then
the request is processed and the database is updated. At this point the jBASE drivers are used to
convert the data into XML format and then the data is updated in the database.
Message Out
Once the database update is complete, the response is sent to any one of the T24 servers. The TC
(TEMENOS CONNECTOR) Server in the T24 server then parses the OFS response into XML and
passes it on to the any one of the EJB servers. The TC (TEMENOS CONNECTOR) Client running on
the EJB Server receives the response and passes it on to the T24 Browser running on the same
server. The T24 Browser then sends in to any one of the Web Servers. The Web Server then sends
the response as a html page to the Network Dispatcher which then sends it to the appropriate Internet
Explorer screen. The Web Server has the in built intelligence using which it can decide which IE
session initiated the request and hence will instruct the next layer to send the response to the IE
session that actually initiated the request.
T24 Installation
The following section describes the installation of T24 on a WINDOWS machine.
Components
Following are the components that are required for the installation on T24.
1. jBASE
2. T24
3. Web server (Tomcat / Webspheare)
4. Temenos Connector
5. Java developers kit
6. Temenos Browser
Pre requisite
• Minimum of 2 GB of free space
• IE 5 or above
Installation Procedure
Assumption
jBASE 4.1 or above and T24 are installed and users are able to connect and work on T24 running on
jBASE.
Step 1
The first step is to install Java developers kit. This is required by the Temenos Connector and the Web
Server and hence needs to be installed before the installation of the other 2 components. You must
have received a file similar to j2re_1.5.0.4_i586.exe. Execute this file. This will install the required java
component. Install it under the default path prompted by the installation procedure.
Step 2
The next step is to install the Temenos Connector Server component. You must have received a file
by name Setup_TCServer.1.4.0_0.bat. Create a directory named ‘tcs’ under the home directory of T24
(bnk.run). Copy this file to that directory. The Temenos Connector Server is installed on the
Application server and hence we choose this path to install it.
Invoke the command line
Start->Run->Cmd
From the command line, change to the tcs directory
cd c:\bnk\bnk.run\tcs
Execute the bat file.
java –jar TCServer.1.2.1.bat
You will be prompted with the following questions
Step 3
The next step is to install the web server. Depending on the web server being used
(Tomcat/Websphere), perform the installation and not down the path where you have installed the web
server. Tomcat has been used in this document.
Step 4
Assumption : Tomcat is installed under c:\Tomcat5.5
The next step is to install the Temenos Browser component. This will normally be installed on the web
server. In order to install this you need to ensure that Tomcat is not running. Check in the task
manager if Tomcat is running. If it is, then choose
Start->Programs->Apache Tomcat5.5->Stop Tomcat
and stop the TOMCAT service. If not, then copy the file Browserweb.war file which you would find
under the T24InstallationFiles directory on to
C:\Tomcat5.5\Webapps
Now start Tomcat.
Start->programs->Apache Tomcat5.5->Start Tomcat
Wait for a couple of minutes. Now if you look at C:\Tomcat5.5\Webapps directory, you would find a
new sub directory by name BrowserWeb. This is the directory for the Temenos Browser and the
Temenos Connector Client.
Now, stop Tomcat.
Configuration
Step 1
Configure the Temenos Connector Server.
Open the tcserver.xml file with notepad and make the following changes(changed highlighted). You
will find this file under C:\bnk\bnk.run\tcs\conf.
<TCSERVER>
<JMXRmiPort>1099</JMXRmiPort>
<MONITOR_PORT> 9500 </MONITOR_PORT>
<TELNETD_PORT> 9501 </TELNETD_PORT>
<DEBUGGER_PORT> 9502 </DEBUGGER_PORT>
<SPY_PORT> 9503 </SPY_PORT>
<MULTICAST_IP>230.100.100.100</MULTICAST_IP>
<!-- If 0 multicast not enable, default 9509 -->
<MULTICAST_PORT>0</MULTICAST_PORT>
<STACKEXPIRATION>120</STACKEXPIRATION>
<SCALEDOWNSPEED>30</SCALEDOWNSPEED>
<ENCRYPTION_KEY>key</ENCRYPTION_KEY>
<OFSMLValidation>false</OFSMLValidation>
<HEARTBEAT>
<FREQUENCY>30</FREQUENCY>
<MESSAGE>XXX</MESSAGE>
<EXPECTED_ANSWER>EB.RTN.APP.MISS.2</EXPECTED_ANSWER>
</HEARTBEAT>
<MESSAGEFORMATTERS>
</MESSAGEFORMATTERS>
<ADAPTERS>
<ADAPTER id="T24">
<MAX_SESSION> 5 </MAX_SESSION>
<MIN_SESSION> 1 </MIN_SESSION>
<TIMEOUT>30</TIMEOUT>
<LOGIN_CONTEXT></LOGIN_CONTEXT>
<STARTIN>c:\bnk\bnk.run</STARTIN>
<JBASEPATH>c:\jbase4\4.1</JBASEPATH>
<PROGRAM>OFS.CONNECTION.MANAGER</PROGRAM>
<PARAMETER>GCS</PARAMETER>
</ADAPTER>
</ADAPTERS>
<LISTENERS>
<LISTENER Name="Browser.1" type="tcp" active="true">
<ADAPTERID>T24</ADAPTERID>
<PORT> 7001 </PORT>
</LISTENER>
</LISTENERS>
</TCSERVER>
Step 2
Configure the Temenos Connector Client. Edit the file channels.xml with notepad. You will find this file
under C:\Tomcat5.5\webapps\BrowserWeb\WEB-INF\conf
<?xml version="1.0" ?>
<!-- DOCTYPE CHANNEL SYSTEM "../dtd/channel.dtd" -->
<CHANNELS>
<CHANNEL>
<NAME>Browser.1</NAME>
<TIMEOUT>300</TIMEOUT>
<ADAPTER>
<TYPE>tcp</TYPE>
<PORT>7001</PORT>
<SUPPLIER>
<INITIATOR>
<HOSTNAME>127.0.0.1</HOSTNAME>
</INITIATOR>
</SUPPLIER>
<CONSUMER>
<MAX_SESSION>5</MAX_SESSION>
<ACCEPTOR>
<BACKLOG>30</BACKLOG>
</ACCEPTOR>
</CONSUMER>
</ADAPTER>
</CHANNEL>
</CHANNELS>
Step 3
Configure the Temenos Browser. Open the file BrowserParameters.xml with notepad. You will find
this file under C:\Tomcat5.5\webapps\BrowserWeb
<?xml version="1.0"?>
<browserParameters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<messageData>
<parameter>
<parameterName>Server Connection Method</parameterName>
<parameterValue>T24CONNECTOR</parameterValue>
<!-- Options: T24CONNECTOR / INSTANCE -->
</parameter>
<parameter>
<parameterName>Instance</parameterName>
<parameterValue>production</parameterValue>
</parameter>
<parameter>
<parameterName>TC_CHANNEL</parameterName>
<parameterValue>Browser.1</parameterValue>
</parameter>
<parameter>
<parameterName>TC_TIME_OUT</parameterName>
<parameterValue>120</parameterValue>
</parameter>
<parameter>
<parameterName>Use Transformer</parameterName>
<parameterValue>NO</parameterValue>
<!-- Options: YES / NO -->
</parameter>
<parameter>
<parameterName>Log Events</parameterName>
<parameterValue>NO</parameterValue>
<!-- Options: YES / NO -->
</parameter>
<parameter>
<parameterName>Log Level</parameterName>
<parameterValue>NONE</parameterValue>
<!-- Options: NONE / INFO / ERROR / DEBUG -->
</parameter>
<parameter>
<parameterName>Web Server Skins</parameterName>
<parameterValue>arabic:bluesquare:default:xp</parameterValue>
<!-- Skin Names separated by : character -->
</parameter>
<parameter>
<parameterName>CALL_CENTRE_CLASS</parameterName>
<parameterValue>TestAPI</parameterValue>
</parameter>
</messageData>
</browserParameters>
Step 6
Start TC Server.
Go to the installation path of TC Server : C:\bnk\bnk.run\tcs
Change to bin directory and execute TCServer.bat.
Step 7
The next step is to start Tomcat.
Start->Programs->Apache Tomcat5.1->Start Tomcat
Step 8
Now you are ready to log on to Browser. Type the following URL in address bar of IE.
http://localhost:8080/BrowserWeb/servlet/BrowserServlet
Important Setting
Ensure that in IE the following is set to access Browser installed on a local machine
Tools->InternetOptions->Connections->LanSettings->[Check the option]Bypass proxy servers for local
addresses