Temenos Connector

TEMENOS Connector

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 t he express written permission of TEMENOS Holdings NV. Copyright 2005 TEMENOS Holdings NV. All rights reserved.

Trusted by over 1 million members

Try Scribd FREE for 30 days to access over 125 million titles without ads or interruptions! Start Free Trial Cancel Anytime.













Temenos Connector

Table of Contents

Application Overview ........................................................................ ........................................................................................................................... ................................................... 3 Temenos Connector Server................................................................................................................. Server................................................................................................................. 3 Prerequisites ..................................................................... ................................................................................................................................ ............................................................... .... 3 OFS Setup................................................................................................................. Setup........................................................................................................................................ .......................4 4 Installing TCServer.jar and dependencies ..................................................................... ....................................................................................... ..................6 Environment Variables .............................................................................. ..................................................................................................................... .......................................7 Configuration of tcserver.xml .................................................................. ........................................................................................................... .........................................9 Custom Listeners .......................................................................... ........................................................................................................................... .................................................15 Message Formatters ............................................................................ ...................................................................................................................... ..........................................18 TCMonitor.......................................................................................................................................24 Telnet Daemon .............................................................................. ............................................................................................................................... .................................................25 Tracing functionality ............................................................................. ....................................................................................................................... ..........................................25 Troubleshooting ................................................................... ............................................................................................................................... .............................................................. ..25

Verification of OFS configuration ..................................................................................................25 Temenos Connector Client ................................................................................... ................................................................................................................ .............................28 Prerequisites and Compability Compability ...................................................................................... ....................................................................................................... .................28 Configuration : channels.xml..........................................................................................................28 Tracing Functionality Functionality ............................................................................ ...................................................................................................................... ..........................................30 Troubleshooting..............................................................................................................................30













Temenos Connector

Introduction Ap p li c ati o n Ov er erv v iew The Temenos Connector allows external programs to link into T24 via the OFS (Open Financial Service) module. The Temenos Connector consists of two elements: The java TCServer opens up T24 to external access via OFS. This can be done using many different channels, including MQSeries, TCP, SSL and RMI. The TCClient is an API which allows other client programs to connect with the TCServer (and therefore onto T24) using the same channels listed above. The TCClient API is available as a java version, as well as C++ offering a COM (Component Object Modelling) layout.

Temenos Te menos Connector Se Server rver Prerequisites T24 / TEMENOS GLOBUS The java TCServer has been developed on top of T24 for jBASE., but is also backwardly compatible with TEMENOS GLOBUS from G12.1 onwards, although TEMENOS GLOBUS releases prior to G13.1, will need the installation of some additional subroutines in order for the TCServer to run correctly. These subroutines are :

•

GLOBUS.INITIALISE

•

GET.ENV.JBASE

•

OFS.INITIALISE.SOURCE

•

OFS.CONNECTION.MANAGER

If unsure whether these subroutine are already deployed or not, type : $ jshow If the result is a full path to a library, this means that jBase can find this subroutine, otherwise, contact your Temenos Representative to get the latest versions.













Temenos Connector

Platform The TCServer has been deployed and tested on the following platforms :

•

Windows 32

•

AIX

•

HP-UX

•

Solaris

•

Linux

•

OS390

•

AS400

•

True64.

OFS Setu Setup p Create an OFS.SOURCE record as presented here :

SOURCE.NAME

TCS

1 DESCRIPTION

OFS ONLINE MODE

2 SOURCE.TYPE

TELNET

3. 1 LOGIN.ID

any

4. 1 EB.PHANT.I EB.PHANT.ID D 5 MAX.CONNE MAX.CONNECTIONS CTIONS

11

6 RESTRICT.LIN RESTRICT.LINK K 7 INITIAL.ROUTINE 8 CLOSE.ROUTINE 9 IN.MSG.RTN 10 OUT.MSG.RTN 11 MSG.PRE.RTN 12 MSG.POST.RTN 13 LOG.FILE.DI LOG.FILE.DIR. R. 14 LOG.DETAIL.L LOG.DETAIL.LEVEL EVEL NONE 15 OFFLINE.QUEUE 16 MAINT.MSG.DE MAINT.MSG.DETS TS













Temenos Connector

21 OUT.QUEUE OUT.QUEUE.NAME .NAME 22 QUEUE.INIT QUEUE.INIT.RTN .RTN 23 QUEUE.CLO QUEUE.CLOSE.RTN SE.RTN 24 SYNTAX.TYPE OFS 25. 1 LOCAL.REF 26 GENERIC.USER

INPUTTER

27 IN.DIR.RTN 28 VERSION 29 IB.USER.CHEC IB.USER.CHECK K 30 EOD.VALIDATE 31 FIELD.VAL 32. 1 ATTRIBUTES 33 RESERVED1 34. 1 OVERRIDE 35 RECORD.STATUS 36 CURR.NO

16

37. 1 INPUTTER.

0_AUBERT1

38. 1 DATE.TIME

07 NOV 02 07:29

39 AUTHORISE AUTHORISER R

0_AUBERT1

40 CO.CODE

GB-001-0001

41 DEPT.CODE

1

42 AUDITOR.CODE 43 AUDIT.DATE AUDIT.DATE.TIME .TIME

Please note that although the SOURCE.TYPE field is set to “TELNET”, the TCServer does not actually use telnet, this is merely to specify that we will have online (and not batch) data coming. To test that T24 is now ready to be accessed by the TCServer, at the jShell type: $ OFS.CONNECTION.MANAGER TCS An alternative way is to ensure that the environment variable called OFS_SOURCE is set up to the value of the Record ID of the table OFS.SOURCE (in our example : “TCS”) $ export OFS_SOURCE=TCS (or “set OFS_SOURCE=TCS” for windows …)













Temenos Connector

$ OFS.CONNECTION.MANA OFS.CONNECTION.MANAGER GER A response like this should be expected: OFS VERSION 2.0 ? Type anything at the prompt: e.g. “hello world”. The answer should be: NO SIGN ON NAME SUPPLIED DURING SIGN ON PROCESS Alternatively a real enquiry can be entered at the prompt : ENQUIRY.SELECT,,/, If the test is successful then the TCServer is ready to be deployed. To quit the test type: “exit”.

Installi ng TCServer.jar TCServer.jar and d epe ependencies ndencies The jar File and a Setup.sh (or Setup.bat), should be copied to any desired location and the script executed. Prompts will appear for the following information:

•

The path for the TCServer installation

•

The path to T24 (the xxx.run directory)

•

The path to the jBase version

•

The OFS.SOURCE record ID.

Note that this setup will only deploying files in the install directory, so special privileges to install it (apart from write access to this directory) will not be required. For Windows, there is no update to the registry, so to uninstall, simply delete the whole directory. However, if installing the NT Service (in the ./bin path), write access to the Registry will be required. The removeService.bat will remove any entry.















Temenos Connector

Figure 1 - TCSe TCServer rver Inst allation p rogr am

Once installed, the two 2 files (TCServer.bat and TCServer.sh) will be present in the /bin directory and can be executed (.bat for windows, .sh for Unix/Linux) to start the server. On unix, the rights of this file, may need review.













Temenos Connector

By default, this file contains “tags” like “, etc. These tags are substituted on the fly by the values specified in the tcserver.xml file. Even if the environment has been “piped”, this file can be edited and these special tags added, instead of having a “hardcoded” path.













Temenos Connector

Configuration of t cserver. cserver.xml xml This file contains all the configuration parameters of the TCServer and is located in the ./conf directory. The

structure of this file looks like this :

Message formatters are used to format (change) the requests and/or the responses Adapters define how to connect with T24. The link to the message formatters can be specified here. The listeners define the channel by which external programs connect to the TCServer (MQSeries, TCP, SSL etc.)

Initial settings













Temenos Connector

STACKEXPIRATION is the number of seconds a RESPONSE will stay in the internal queue before the server removes it; this can happen if the client application does not retrieve it. The encryption key will be described later in this document.

Messageformatters

com.temenos.formatter.CRLFtoVM

MESSAGEFORMATTERS are java classes used to format a request or a response. The classes can be listed here by giving them a specific ID. The TCServer will load the class, but will not activate them. There is no restriction on listing classes; they will not affect resource usage.

Adapters

CRLFtoVM VMtoCRLF R> 5 1













Temenos Connector

ADAPTERS define the way the TCServer connects with T24Server. Multiple adapters can be specified, defined by the attribute “id” with different settings, they will only be activated if referenced by a listener

Tags OFSENTRY specifies which process will be used to communicate with T24Server. This should always be OFS.CONNECTION.MANAGE OFS.CONNECTION.MANAGER. R. OFSTIMEOUT specifies after how many seconds the TCServer will assume that something went wrong, and will stop waiting. A value of 0 means “wait forever”. MIN_SESSION is the number of initial processes. The TCServer will create new session if necessary up to MAX_SESSION. GLOBUSPATH, JBASEPATH, OFSENTRY and OFSSOURCE are the values entered during installation. These values will be used to “fork” a new OFS.CONNECTION.MANAGER process. These are these values which will replace the tags in environment.vars. ENVIRONMENT specifies which file contains the name-value pairs for the environment variables. The default value is “environment.vars”. REQUEST_FORMATTER and RESPONSE_FORMATTER are a link MESSAGEFORMATTERS MESSAGEFORMAT TERS section. At this point the required formatter is specified.

BACK

to

the

Listeners LISTENERS define the communication with the TCServer. The following types of listeners are supported :

•

raw-tcp A raw socket accepting anything, processing it as-is. TCClient

Socket.















Temenos Connector

Example Exa mple list ene eners rs in the above tcserver.xls

Lis.1













Temenos Connector

G13101 4001

G13101 7002

G13101 myhost qm.test test.in ch.test 5 NO













Temenos Connector

This is the most simple LISTENER possible. By defining such a listener, the TCServer will just listen to a Socket on the port and will forward to T24Server whatever it receives. A message ends with a CRLF. If such a Listener is used, one can just “telnet” the server by specifying the port. Eg : telnet localhost 4001. Note that this listener doesn’t implement a Telnet emulation, so maybe an echo will not be present. This listener type is useful for test purposes. This is NOT recommended to use it in a live environment. The ADAPTERID tag specifies what adapter should be used when a message comes to this listener. All listeners have the same ADAPTERID tag, except mqseries-fwd.

Lis.2 The definition of the type « tcp » looks exactly the same as a “raw-tcp” channel type. However, it is not possible to communicate through a raw socket, as this kind of listener is expecting a specific binary format only the TCClient can generate and understand. This type of listener is the most common and can be used from any type of TCClient (java, COM, C++, . . .)

Mq.1 An MQ Queue is defined by four parameters :

• •

MQHOST The MQHOST has the format [()]. Eg : LOCALHOST(1415). If no port is specified, the default 1414 will be used. MQMANAGER













Temenos Connector

ATM This listener has a of type “custom” allowing it to define a java class which will act as a custom listener. This functionality is very useful for development of interfaces. Refer to the following section on creating custom listeners.

Custom List ene eners rs The key in creating custom listeners is to create a java class which extends the class com.Temenos.tocf.tcs.API.AbstractListener. This is in the tcserver.jar. There are the following methods:

•

public abstract void stopIt();

•

public abstract boolean boolean isStopped();

•

public byte[] process(byte[] bRequest) {

•

public byte[] processAsync(byte[] bRequest, String sTag) {

•

public void messageReady(byte[] requestId, byte[] bResponse, String sTag){};

•

public void run();

stopIt() is called when the TCServer wants to stop the listener. isStopped() must return whether or not the listener is stopped.













Temenos Connector

run(). The class AbstractListener implements Runnable, and will create a new thread with the class

whenever it needs to be started. Here is the code of a simple Listener. In this instance, the listener does not, in fact, listen to anything, but simply sends in an asynchronous way, a message to T24Server every 5 sec. The responses are received via the messageReady() method: The same kind of sample, but using a synchronous communication :

import com.temenos.tocf.tcs.API.*; public

class

ListenerTest

private boolean private boolean _bIsStopped = false;

extends

_bStopIt

public void messageReady(byte[] requestId, byte[] bResponse, String sTag) {

System.out.println("Received System.out.println("Rec eived : " + new String(bResponse)); } public void run() {

String sRequest = “ENQUIRY.SELECT,,INPUTT/123456,%CURRENCY”; while (!_bStopIt) {

AbstractListener =

false















Temenos Connector

import com.temenos.tocf.tcs.API.*; public class ListenerTest extends AbstractListener { private boolean _bStopIt = false ;













Temenos Connector

/ext/.

If the class had a package name (eg com.mycompany) it should be located in : /ext/ com/mycompany.

Alternatively, if a jar file was made, it can be added in the classpath.

Message Me ssage Form atters

Message Formatters are classes which can be locally written that will format any Request/Response Request/Response before/after having send it to T24. A message formatter can be very useful in charset conversion conversion or interfaces. For













Temenos Connector

package com.temenos.formatter;

import com.temenos.messageformatter.*; import java.io.*;

public class CRLFtoVM extends Formatter {

private static final byte CR = 13; private static final private static final byte VM = (byte) 253;

byte

public byte[] format (byte[] request, byte[] response) {

LF

=

10;













Temenos Connector

com.temenos.form com.temenos.formatter.TestFormatter atter.TestFormatter Hello World

For the above definition, the value of the tag can be retrieved as follows : String sParam = super.getParam(“MYPARAM”); The call can also be cancelled, so that the request will not be sent to T24Server. In this case, if a RESPONSE formatter is defined, it will be invoked with a null response. However this response can be overridden by returning any chosen value from the













Temenos Connector

com.temenos.formatter.CP838TOUTF8 com.temenos.formatter.UTF8TOCP838

CP838_TO_UTF8, OFSML, UTF8_TO_CP838 ORMATTER>















Temenos Connector

com.temenos.formatter;

package

com.temenos.messageformatter.*;

import public

class

CP838TOUTF8

extends

Formatter{













Temenos Connector

package

com.temenos.formatter;

import public

com.temenos.messageformatter.*; class

CharsetConverter

extends

Formatter{













Temenos Connector

com.temenos.formatt com .temenos.formatter.CharsetConverter er.CharsetConverter KSC5601 UTF-8













Temenos Connector

Telnet Daemon

The server can be managed via a telnet session using the correct port number. The port the TCServer is listening on can be changed using the tag in the jTCServer.xml file. If the is left unspecified, the TCServer will not start the telnet deamon.













Temenos Connector

Type “OFS.CONNECTION.MANAGER TCS”, where “TCS” is the OFS.SOURCE record ID. A message like “OFS “OFS VERSION 2.0” should be received, received, this confirms that OFS is active. Then type an enquiry in OFS format, e.g.:































































Temenos Connector

Recommend Documents