SwiftAlliance_ UserGuide

Swift Alliance Interface User Guide

Information in this document is subject to c hange without notice. No part of t his document may be reproduced or transmitted in any form or by any means, for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA. COPYRIGHT 2007 - 2008 TEMENOS HEADQUARTERS SA. All rights reser ved.

Swift Alliance ODR-2008-11-0050

Copyright The Programs (which include both the software and documentation) contain proprietary information of Temenos Holdings NV and they are provided under a license agreement containing restrictions on use and disclosure and are also protected by co pyright and other intellectual and industrial property laws. Reverse engineering, disassembly or de -compilation of the Programs, except to t he extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Temenos does not warrant that this document is error -free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs 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 Holding s NV. T24 and jBASE are registered trademarks of Temenos Holdings NV. Other names may be trademarks of their respective owners.

2

Author’s Name: Thomas J


Document Detail Item

Detail

DEVELOPMENT NAME

SWIFT ALLINIACE

GRID REFRENCE

ODR-2008-11-0050

DOCUMENT TYPE

User Guide

SPECIAL COMMENTS(1) (Database / Hardware Specific) Special Comments (2) (Development / Support Specific) Special Comments (3) (Client Specific)

3



Document History Author

4

Version

Date

N.K.SHRINATH

1.0

30 Jan 2006

R.ANAND

1.1

27 Oct 2006

J. Thomas

2.0

10 Oct 2009

Naresh G

2.1

10 Oct 2011



Table of Contents Document Detail................................ .................................................................................... 3 Document History ................................ ................................................................ .................. 4 Overview of this guide ................................................................ ........................................... 6 Assumptions ................................ .......... ...................... .................. .............. .................. .... 6 Document Support ................................................................ ............................................. 6 Introduction ................................................................................................ ........................... 7 Document Purpose ................................................................ ................................. ........... 7 TEMENOS T24 TM Modules Supported ............................................................................. 7 Abbreviations used in this Guide .............................. .. ......... .................. ..... ................ ........ 7 Development Work Flow ................................................................................................ ....... 7 Development Overview ................................................................................................ ...... 7 Changes for R6 and above Compatibility ................................................................ ........... 8 Main Subroutines and their Description ................................................................................. 8 DE.ALLIANCE.OUT ................................................................ ........................................... 8 DE.ALLIANCE.IN ................................................................ ............................................... 8 CONFIGURING TEMENOS CONNECTOR ................................................................ ........ 9 Data Flow................................ ................................. ........................................................... 10 Process Flow ................................................................................................ ...................... 10 Work Flow Diagram ................................ ................................................................ ............. 11 SWIFT-IN ................................................................ ........................................................ 11 SWIFT-OUT ................................................................ .................................................... 12

5



Overview of this guide The purpose of this guide is to help the user to understand the various Templates and the fields in the Templates and the crucial setup of any PARAMETER Files in the SWIFT Interface.

Assumptions It is assumed that the reader of this guide has k nowledge of the following.

§

§

§

Basic knowledge in Windows / UNIX operating systems. Fair knowledge in TEMENOS T24 TM \ <>

If any of the above assumptions are not met, then get back to the Project Manager Onsite for HELP.

Document Support Any queries in any part of this document can be addressed to [email protected]. Refer to the Contact Back To address in the Document Detail pane on Page 3 of this Guide for support.

Scope of this guide User Reference information of this particular development is the only scope of this guide .

. Installation, Customization Procedures, Release Information, Guidelines for testing, Operation and Migration procedures are NOT under the scope of this Document .

6



Introduction Document Purpose This document provides information to the user to understand the different parameter files and their setup. This document provides detailed information about every Field of all the Files used in the SWIFT ALLIANCE.

TEMENOS T24

TM

Modules Supported

All the standard SWIFT messages supported by T24 is handled in this SWIFT Alliance Interface.

Abbreviations used in this Guide S – Single Value Field M – Multi Value Field AMS – Associated Multi Value Starts Here AM – Member of Associated Multi Value AMC – Associated Multi Value Closes Here

Development Work Flow Development Overview The TEMENOS T24 / SWIFT ALLIANCE interface (called thereafter the interface) is based on the Electronic Delivery System. The Electronic Delivery System manages the flow of all messages from T24, such as confirmations, payments and advises whilst giving users full control over formatting and language of presentation. Messages are generated automatically as soon as contract entry is complete or when a scheduled diary event occurs. All messages may be either printed or sent via electronic carrier systems.

In regard to SWIFT messages, the interface is directly connected with the electronic carrier system in order to access the network using the SWIFT ALLIANCE server. The interface, designed to enable online message transfer, allows the host machine (T24 Server) to communicate with the SWIFT ALLIANCE system. Communication between the SWIFT and T24 machines is done through a NFS partition. The Incoming SWIFT messages are processed through the Temenos Connector, here after called TC component. The DE.ALLIANCE.OUT and DE.ALLIANCE.IN subroutines perform a format adjustment and route the messages to the correct directories. As the main processes within Delivery, i.e. mapping, formatting and the carrier control processes are run as a service.

7



The interface is run as a TSA Service for the Outgoing messages. The messages are sent in real time. The demons send outgoing messages and then the TC processes the incoming messages from the NFS partition directory.

Changes for R6 and above Compatibility From R6 and above release, all the Incoming messages from the external system like SWIFT will be processed through TC. There are set of configurations that need to be done at the TC Server level to read the incoming SWIFT messages and hand it over to the core delivery system.

Main Subroutines and their Description DE.ALLIANCE.OUT The messages are produce by T24 modules and placed into the unformatted SWIFT queue. The SWIFT.OUT service wil l format all the messages which are in the unformatted queue and then invokes the Swift Interface routine DE.ALLIANCE.OUT begins its execution. The formatted outgoing swift messages are placed into F.ALLIANCE.INPUT directory, which is defined at the jbase level.

When messages are placed into F.ALLIANCE.INPUT the SWIFT ALLIANCE application transfers them to the SWIFT ALLIANCE server and subsequently to the SWIFT network. The file type used for the outgoing messages is ‘DOS -PCC’ this should be configured i n the message partner of the outgoing interface in SWIFT Alliance Server.

DE.ALLIANCE.IN The Naming conventions to be followed for the incoming messages are as follows: 1.

For all the Incoming swift messages the id should be prefixed with ‘MSG.xxxxxx’

2.

For all ACK/NAK messages the id should be prefixed with either ‘ACK.xxxxxx’ or ‘NAK.xxxxxx’

The File type used for processing the incoming message is either ‘RJE’ or ‘DOS -PCC’ preferably RJE type. If the file type is RJE then the local reference field in the DE.INTERFACE file ALLIANCE record should be set to RJE. This DE.ALLIANCE routine is invoked when the service SWIFT.INWARD is started. It reads the incoming messages as well as the ACK/NAK messages from the F.ALLIANCE.MSG directory and formats the message by prefixing DE.CARRIER=SWIFT, and converting the carriage return to tag to the messages. The formatted messages are written back to F.ALLIANCE.IN directory along with extension .txt.

8



The TC server has the Listeners for swift this will process th e message which are in the F.ALLIANCE.IN and will update the unformatted queue in T24. On invoking the core SWIFT.IN service the unformatted messages will be formatted and will invoke the DE application to process the necessary transaction to be created in T24.

CONFIGURING TEMENOS CONNECTOR The ‘tcserver.xml’ should be configured to pick the messages from F.ALLIANCE.IN directory and post the messages to T24 through tSS. To configure the tcserver follow the below steps.

§

Add the below adapter tag within the tag.

5 1 300 F:\Temenos\ModelBank-R10\Temenos\bnk\bnk.run F:\Temenos\ModelBank-R10\Temenos\TAFC F:\Temenos\ModelBankR11\Temenos\bnk\bnk.run\t24bin\eb_interface\tSS SWIFT The path of T24 and path of Jbase given in and tag should be replaced with the exact path on site. The value spe cified in the tag is the name of the OFS.SOURCE record created in T24.

§

Add the below listener tag within the tag.

SWIFT F:\Temenos\ModelBank-R11\Temenos\bnk\bnk.run\\F.ALLIANCE.IN F:\Temenos\ModelBankR11\Temenos\bnk\bnk.run\\F.ALLIANCE.RESPONSE F:\Temenos\ModelBankR11\Temenos\bnk\bnk.run\\F.ALLIANCE.ERROR 500 txt $

9



Where the , and tags should hold the exact path of the files on site. This batch file listener listens to the in directory specified in
Data Flow The SWIFT carrier control programs SWIFT.OUT / SWIFT.IN (T24 core program) takes messages from the SWIFT queue, then it sends and receives messages to and from the SWIFT ALLIANCE interface. When the TSA service for outgoing is invoked it checks for outward messages to be sent, similarly when the TSA service for incoming is invoked it checks for inward messages given by Temenos Conne ctor. The SWIFT ALLIANCE interface invoked by OUT routines adjusts the messages in order to pass the information to the SWIFT ALLIANCE server. The same process is used for different kind of messages.

Process Flow The outgoing messages are processed by the TSA service SWIFT.OUT, which invokes the core routine DE.OUTWARD. The incoming messages from Temenos Connector are processed using the TSA service SWIFT.IN, w hich inv okes the core routine DE.INWARD. TEMENOS Technical Consulting SWIFT ALLAINCE .

10



Work Flow Diagram SWIFT-IN

11



SWIFT-OUT

12


SwiftAlliance_ UserGuide

Recommend Documents