Financial Fusion - Trade Force for SWIFT - Version 5

®Financial FusionTradeForce for SWIFT - EAI

version 5.0

Format Library

Installation andAdministration Guide

Financial Fusion and Financial Fusion Server are trademarks ofFinancial Fusion, Inc.

Sybase and Sybase Central are trademarks of Sybase, Inc.

WebLogic is a trademark of BEA Systems, Inc. Oracle is a trademarkof Oracle Corporation. iPlanet is a trademark of the Sun-Netscape

Alliance. SPARC is a trademark of SPARC International, Inc. NT is atrademark of Microsoft Corporation. Solaris, Java, and all Java-basedmarks are trademarks or registered trademarks of Sun Microsystems,

Inc. in the U.S. and other countries.

All other product names are trademarks, registered trademarks,service marks, or trade names of their respective companies.

Copyright © 2002 Financial Fusion, Inc. All rights reserved.

This work may not be reproduced, in whole or in part, in any way orby any means, electronic or mechanical, including photocopying,

recording or through storage and retrieval mechanisms, without priorwritten consent of Financial Fusion, Inc.

Financial Fusion, Inc.561 Virginia Road

Concord, MA 01742 USA

70223-01-0500-01

TABLE OF CONTENTS

About this Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiChapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiConventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixIf You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Product Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Cross-Platform Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Product Support and Education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Creating and Configuring the Database . . . . . . . . . . . . . . . . . . . . . . . . 8Extracting Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Documentation and User Exit Directory Structure. . . . . . . . . . . . 10Pre-Formats Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . 11Library Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Setting the PATH Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Importing Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15TradeForce for SWIFT - EAI Components . . . . . . . . . . . . . . . . . . . . 16SWIFT Format Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Pass Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

iii

Table of Contents

e-Biz Integrator Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26User Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27SWIFT Preformats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30SWIFT Preformats Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Format Library Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Creating Queues (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mapping Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Testing Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Creating Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

From SWIFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36To SWIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Running New Era of Networks Broker. . . . . . . . . . . . . . . . . . . . . . . . 38

Upgrade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39SWIFT Format Libraries Change Details . . . . . . . . . . . . . . . . . . . . . . 39

SW500 Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40SWIFT 2002 Message Change Information . . . . . . . . . . . . . . . . . 40

SWIFT Library Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Full Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Partial Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Appendix A: Support for Previous FFISWIFT Versions . . . . . . . . . . 55Multiple Library Versions for Compatibility . . . . . . . . . . . . . . . . . . . 55

Appendix B: The FFISWIFT Header . . . . . . . . . . . . . . . . . . . . . . . . . . 59Normal FFISWIFT (FROM SWIFT) . . . . . . . . . . . . . . . . . . . . . . . . . 59FFISWIFT with Full Header (FROM SWIFT). . . . . . . . . . . . . . . . . . 61Normal FFISWIFT (TO SWIFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63FFISWIFT with Full Header (TO SWIFT). . . . . . . . . . . . . . . . . . . . . 64

Appendix C: The FFISWIFT Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . 67From SWIFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67To SWIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

iv

Table of Contents

Appendix D: Rule Changes for Upgrading pre-410 Versions ofthe SWIFT Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Modifying Rule Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Modifying Rule Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Mapping of Header Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

From SWIFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74To SWIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

v

ABOUT THIS BOOK

This chapter describes the SWIFT Format Libraries,provides a chapter summary for this guide and informationon where to find additional help.

About This Guide

The SWIFT Format Libraries are a set of prepackagedformats that provide one component of the TradeForce forSWIFT EAI. The TradeForce for SWIFT EAI facilitatesdata conversion and message enrichment between theSWIFT network and legacy or third-party systems. Theentire solution consists of the following seven components:

1. Queues

2. TradeForce for SWIFT - EAI Adapter

3. SWIFT Pre-Formats

4. e-Biz Integrator Rules

5. e-Biz Integrator Formatter

6. User Exits

7. Format Libraries

This document covers the SWIFT Pre-Formats, User Exits,and Format Library Components. The other components aredocumented separately.

vii

About this Book

This document is designed to help you effectively installand use the SWIFT Format Libraries. For information oninstalling and configuring the TradeForce for SWIFT - EAIAdapter, refer to the TradeForce for SWIFT - EAI AdapterInstallation and Administration Guide.

Chapter Summary

This guide is organized into the following chapters:

– Chapter 1: Introduction provides a brief introductionto the format libraries, a list of availabledocumentation, and technical support information.

– Chapter 2: Installation provides instructions oninstalling and configuring the format libraries package.

– Chapter 3: Product Description provides informationon the use of the SWIFT Format components

– Chapter 4: Format Library Use provides informationon setting up formats to be used.

– Chapter 5: Upgrade Information provides upgradeinformation from previous versions of the TradeForcefor SWIFT - EAI Adapter solution.

– Appendix A: Support for Previous FFISWIFTVersions provides information on upgrading.

– Appendix B: FFISWIFT Header provides FFISWIFTheader definitions for to-SWIFT or from-SWIFTmessages.

– Appendix C: FFISWIFT Trailer provides FFISWIFTtrailer definitions for to-SWIFT or from-SWIFTmessages.

– Appendix D: Rule Changes Required to Upgrade pre-410 Versions of the SWIFT Library containsinformation necessary to upgrade your system.

viii

About this Book

Conventions Used in This Guide

This guide uses the following typeface and styleconventions:

Some of the lines of code in the examples must be enteredwithout a return break. The arrow in the example belowindicates you should type the string without pressing Enter.

<this sample code string is longer than the width of the page, → and should be typed without a return break>

If You Need Help

Please refer to the Guide to Financial Fusion SupportServices if you have questions or need technical support.

Note: Each Financial Fusion installation that has purchaseda support contract has one or more designated people whoare authorized to contact technical support. If you cannotresolve a problem using the manuals or online help, pleasehave the designated person contact Financial Fusiontechnical support or the Financial Fusion subsidiary in yourarea.

Convention Used for

Code Elements All Java, XML, and HTML code elements are set in LucidaSans Unicode.

Menu > Submenu The angle bracket indicates movement from one option list tothe next.

Italics File names, path names, and directories are set in italics.

ix

Chapter 1

INTRODUCTION

This chapter includes the following information:

• Supported Platforms

• Product Documentation Set

• Product Support and Education

Supported Platforms

Integration Server Operating System DBMS

e-Biz Integrator 3.6WebSphere MQIntegrator 2.1

Windows NT 4 sp 6aWindows 2000 sp 2

Sybase ASE 12, 12.5SQL Server 2000SQL Server 7Oracle 8i, 8.1.6, 8.1.7DB2 UDB 7.1. 7.2

e-Biz Integrator 3.6WebSphere MQIntegrator 2.1

Solaris 7, 8 Sybase ASE 12, 12.5Oracle 8i, 8.1.6, 8.1.7DB2 UDB 7.1. 7.2

e-Biz Integrator 3.6.1WMQI 2.1

AIX 5.1 Sybase ASE 12, 12.5Oracle 8i, 8.1.6, 8.1.7DB2 UDB 7.1. 7.2

e-Biz Integrator 3.6.1WMQI 2.1

s/390 Version 2.8 DB2 UDB 7.1. 7.2

Installation and Administration Guide 1

Chapter 1: Introduction

NOTE: If you plan to use the SWIFT Format Libraries5.0 with e-Biz Integrator Rules, Formatter, andMessaging 4.1.1 for ISO 15022 messages, you must usea e-Biz Integrator Rules, Formatter, and Messagingversion dated 08/29/00 or later. To verify the versioncompatibility of your current e-Biz Integrator Rules,Formatter, and Messaging installation, check withFinancial Fusion technical support.

Please refer to your documentation for compatibility issuesregarding the use of older platforms with newer versions ofOSs and DBMSs. The TradeForce for SWIFT EAI solutionwill support all previous versions of platforms to MQSI v1.1 e-Biz Intergrator 4.11, 2.1* & 3.x*.

For User Exit modification support for MQSI v2.01 andv2.02 as well as e-Biz Integrator v3.2, v3.2i.x, v3.3x andv3.4x please call Financial Fusion Technical Support.

Note: To compile user exits for the s/390 platform use C++compiler version 2.10. The files have been compiled usingGNUmake. Edit the file ./obj/Makefile adding the paths ofyour components (Rules and Formatter, compiler, etc.). Runmake from the ./obj directory.

2 SWIFT Format Libraries

Product Documentation Set


This section describes the documentation available forSWIFT Format Libraries.

Cross-Platform DocumentationThe SWIFT Solution documentation set includes

• SWIFT Format Libraries Installation Guide

• TradeForce for SWIFT - EAI Adapter Installation andAdministration Guide

Related DocumentationRefer to the following documents for more detail about theuse of e-Biz Integrator, e-Biz Integrator Rules, Formatter,and Messaging, WebSphere MQ Integrator, and IBMWebSphere MQ:

e-Biz IntegratorThe e-Biz Integrator documentation set includes

• Getting Started describes the e-Biz Integratorcomponents and how the components can work togetherin your e-commerce environment.

• Installation and Configuration Guide details theinstallation and initial implementation of e-Biz Integratorand its applications.

• User Guide helps users understand and apply the programthrough its graphical user interfaces (GUIs).

• System Management is intended for systemadministrators and database administrators who workwith e-Biz Integrator on a day-to-day basis.



• Application Development Guide assists programmers inwriting applications that use e-Biz Integrator APIs.

• Programming References are intended for users whobuild and maintain the links between e-Biz Integrator andother applications. The following volumes are included:

– Programming Reference for e-Biz IntegratorFormatter APIs is a reference to e-Biz IntegratorFormatter APIs for those who build and maintain thelinks between e-Biz Integrator and other applications.

– Programming Reference for e-Biz Integrator Rules,Formatter, and Messaging APIs is a reference to e-Biz Integrator Rules, Formatter, and Messaging APIsfor those who build and maintain the links between e-Biz Integrator and other applications.

e-Biz Integrator Rules, Formatter, andMessagingThis set of documentation includes the following:

• User Guide helps users understand and apply the programthrough its graphical user interfaces (GUIs).

• Programming References are intended for those whomust build and maintain the links between e-BizIntegrator Rules, Formatter, and Messaging and otherapplications. This document comes in three volumes.

– Programming Reference for High-Level Messagingand Queuing is a reference to high-level andMessaging and Queuing APIs for those who mustwrite applications to exchange messages.

– Programming Reference for e-Biz IntegratorFormatter is a reference to Formatter APIs for thosewho must write applications to translate messagesfrom one format to another.

– Programming Reference for e-Biz Integrator Rules,Formatter, and Messaging is a reference to Rules APIsfor those who must write applications to performactions based on message contents.



• Installation Guide provides the procedure to install andimplement e-Biz Integrator Rules, Formatter, andMessaging and its corresponding applications.

• System Management Guide is for SAs and DBAs whowork with e-Biz Integrator Rules, Formatter, andMessaging on a day-to-day basis.

WebSphere MQ IntegratorThis set of documentation includes the following:

• Installation and Configuration Guide helps end usersand engineers install and configure WebSphere MQIntegrator.

• User’s Guide helps WebSphere MQ Integrator usersunderstand and apply the program through its graphicaluser interfaces (GUIs).

• Programming References are intended for users whobuild and maintain the links between WebSphere MQIntegrator and other applications. These documentsinclude:

– Programming Reference for e-Biz IntegratorFormatter is a reference to Formatter APIs for thosewho write applications to translate messages from oneformat to another.

– Programming Reference for e-Biz Integrator Rules,Formatter, and Messaging is a reference to RulesAPIs for those who write applications to performactions based on message contents.

– Application Development Guide assists programmersin writing applications that use APIs associated with e-Biz Integrator Rules, Formatter, and Messaging.

• System Management Guide is for system administratorsand database administrators who work with WebSphereMQ Integrator on a day-to-day basis.



IBM WebSphere MQThis set of documentation includes the following:

• WebSphere MQ An Introduction to Messaging andQueuing

• WebSphere MQ Planning Guide

• WebSphere MQ Command Reference

• WebSphere MQ Clients

• WebSphere MQ Application Programming Reference

• WebSphere MQ Application Programming ReferenceSummary

• WebSphere MQ Application Programming Guide

• WebSphere MQ Distributed Queuing Guide

Product Support and Education

For more information on Support Services, education, andconsulting services, refer to the Customer ServicesReference Guide.


Chapter 2

INSTALLATION

To install the SWIFT Format Libraries correctly, you mustcomplete the following procedures, as described in the thesesections:

• Creating and Configuring the Database.

• Extracting Installation Files.

• Setting the PATH Variable.

• Importing Formats.

These procedures are described later in this chapter.

Prior to installing and using the SWIFT Format Libraries,you should attend an integration server (e-Biz Integrator orWebSphere MQ Integrator) training class.


Chapter 2: Installation

Creating and Configuring the Database

If you did not create and configure a database connectionwhile installing your New Era messaging software, use yourDBMS tools to create a database for format data. Create asqlsvses.cfg or nnsyreg.dat file that contains the correctinformation for your database.

Use the sqlsvses.cfg or nnsyreg.dat file to connect to theproper database.

1. Change to the bin directory created during theinstallation of the New Era messaging software.

2. Create a text file named sqlsvses.cfg or nnsyreg.datwithin the bin directory.

3. Insert the following line in sqlsvses.cfg or nnsyreg.dat:

sessionname:server:username:password:databasename

For example:new_format_demo:dodge:user:passwd:TESTDATABASEInput:Dodge:user:passwd:TESTDATABASEOutput:Dodge:user:passwd:TESTDATABASErules:Dodge:user:passwd:TESTDATABASE

orSession.new_format_demoNNOT_SHARED_LIBRARY= dbt26sql65NNOT_FACTORY_FUNCTION= NNSesMS6FactoryNN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuserNN_SES_PASSWORD= NNSYpassNN_SES_DB_NAME= SWIFT1Session.nnfieNNOT_SHARED_LIBRARY= dbt26sql65NNOT_FACTORY_FUNCTION= NNSesMS6FactoryNN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuserNN_SES_PASSWORD= NNSYpassNN_SES_DB_NAME= SWIFT1


Extracting Installation Files

Session.nnrieNNOT_SHARED_LIBRARY= dbt26sql65NNOT_FACTORY_FUNCTION= NNSesMS6FactoryNN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuserNN_SES_PASSWORD= NNSYpassNN_SES_DB_NAME= SWIFT1Session.rulesNNOT_SHARED_LIBRARY= dbt26sql65NNOT_FACTORY_FUNCTION= NNSesMS6FactoryNN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuserNN_SES_PASSWORD= NNSYpassNN_SES_DB_NAME= SWIFT1

NOTE: Oracle does not require a database name.


The SWIFT Format Libraries package includes twoinstallation CDs. One CD contains user exits anddocumentation and the other CDs contain the purchasedformat libraries, including the preformats. The installationCDs contain the files described in the following table.



Documentation and User Exit Directory Structure

Directory Contents

../Documentation pdf files relevant to the product

../User-Exits

/Aix/include/lib/obj/project/src

User-Exit files for use with AIX.

/Hp/include/lib/obj/project/src

User-Exit files for use with HP/UX.

/S390/include/lib/obj/project/src

User-Exit files for use with OS/390.

/SunOS/include/lib/obj/project/src

User-Exit files for use with Solaris.

/WinNT/include/lib/obj/project/src

User-Exit files for use with Windows.

commonref.txt Example commonref.txt configuration file.

ReadMe.txt User-Exits ReadMe Word document.



Pre-Formats Directory Structure

Library Directory StructureAll messages are divided into three subdirectories:

• CA—client application messages

• FROM—messages from SWIFT

• TO—messages to SWIFT

Within each subdirectory is a choice of seven differentconfiguration versions. New users will choose SW500. Theothers are for upgrading purposes.

Within each configuration directory are two subdirectories:

Directory Contents

../Pre-Formats

/Financial-Fusion_Pre-FormatsSW500_NNRules.expSW500_PFFormats.exp

Pre-Format format and rule files for use withe-Biz Integrator.

/MQSA_Pre-FormatsSW500_NNRules_MQSA.expSW500_PFFormats_MQSA.exp

Pre-Format format and rule files for use withMQSA.

ReadMePreFormats5.0.doc Pre-Format Readme Word document.

Directory Contents

.../all/ All format libraries included in one nnfie exportfile for a specific category.

.../individual/ This directory contains the MT### files that inturn contain the nnfie files.



To extract files

1. Create an installation directory (for example SWIFTPP)in the <integration server>/bin directory in which thesqlsvses.cfg file resides.

2. Move to that directory.

3. Copy the appropriate directories (listed in the tableabove) from the CDs to the installation directory.

Setting the PATH Variable

The userexit.cpp is included in the SWIFT Format Librariesinstallation to build the libraries needed for SWIFT userexits. Set your environment variables to ensure that the userexit library built off of userexit.cpp is listed prior to the libdirectory created during the e-Biz Integrator, e-BizIntegrator Rules, Formatter, and Messaging, or MQSIinstallation. If you do not set the path correctly, e-BizIntegrator Formatter will use the default user exits ratherthan the SWIFT-specific user exit.

NTEnsure that nnuserexit.lib is listed prior to <integrationserver>\User-Exits\lib in the PATH environment variable.

SolarisEnsure that libnnuserexit.shlib is listed prior to<integration server>/User-Exits/lib in theLD_LIBRARY_PATH variable.

AIXEnsure that libnnuserexit.shlib is listed prior to<integration server>/User-Exits/lib in the LIBPATHvariable.


Importing Formats

Importing Formats

You can import all components of a given format by usingthe NNFie import/export utility.

Before you begin importing components, you must createthe target database.

It is best to import the formats into an empty database.However, you can import formats into a database containingnonconflicting data. For example, if the database currentlycontains Securities, Settlement, and Reconciliation formats,you can import Corporate Actions formats with no trouble.You can also import formats into a database currentlycontaining the same format, if the existing format name isversioned.

See the System Management guide for your messagingsoftware for more information on importing formats.

NOTE: If importing components into a case-insensitivedatabase, NNFie fails during import if a conflict arisesbetween two components named the same with only casedifferences.

NOTE: Do not modify the SWIFT formats. The formats aredefined for the purpose of communicating with SWIFT. Ifmodified, this functionality is lost.

The shipped formats are fully supported by FinancialFusion, Inc. Custom format modifications are notsupported.


Chapter 3

PRODUCT DESCRIPTION

The SWIFT Format Libraries are a part of TradeForce forSWIFT - EAI, including:

• SWIFT network access

• SWIFT-approved gateway (SWIFTAlliance Access orST400)

• SWIFT Format libraries, preformats, and user exits

• TradeForce for SWIFT - EAI Adapter

• e-Biz Integrator Formatter

• e-Biz Integrator Rules

Each of these components play an integral part in attainingthe goal of an enterprise system that is fully integrated withSWIFT standards.

This chapter describes the following:

• “TradeForce for SWIFT - EAI Components” on page 16.

• “SWIFT Format Libraries” on page 19.


Chapter 3: Product Description

TradeForce for SWIFT - EAI Components

The SWIFT Format Libraries constitute the top-levelcomponent of the TradeForce for SWIFT - EAI. Thissolution facilitates data conversion and message enrichmentbetween the SWIFT network and legacy or third-partysystems.

The entire solution consists of seven components, asfollows:

• QueuesThe components communicate with each other usingqueues. The queues can be WebSphere MQ queues in thecontext of MQSI, EMQ queues in the context of e-BizIntegrator Rules, Formatter, and Messaging, or transportqueues in the context of e-Biz Integrator. The queuesmust be configured as described for each componentbelow.

• TradeForce for SWIFT - EAI AdapterThis optional component mediates between the SWIFTnetwork and queues. On the network side, the adapteruses an API called CAS, which SWIFT developed, tocommunicate with SWIFT Alliance, whichcommunicates with the SWIFT network. On the queueside, any of the queue types mentioned above can beused. This component is sold separately and documentedseparately. Its configuration requirements are extensive,involving a database, queues, configuration files, andsettings in SWIFT Alliance; refer to the separatedocumentation for details.


TradeForce for SWIFT - EAI Components

• PreformatsThe SW410 Pre-format pass is a preliminary passthrough the e-Biz Integrator Rules and e-Biz IntegratorFormatter to enable message routing and more efficientparsing and reformatting. These preformats arecompatible with the SW300 version and earlier of theSWIFT Format Libraries. If you use any other version ofthe Format library, such asSW410_ENDSEQ_OLD_CREDIT_DEBIT_PARSE,you must use the SWIFTMsgProcessor.

• e-Biz Integrator Rules

The Rules component is a message switch that can beused to accept messages, route them through theappropriate formats and then to the appropriatedestination based on business rules. Messages can arrivefrom multiple sources and be routed to multipledestinations, with multiple transformations, based on thevalue of any field or group of fields in a message. Thecustomer must write business-specific rules to drive theSWIFT-interaction process. The Rules engine can readand write to and from multiple queues. Setting up thequeues is one part of the required configuration effort.Rules configuration is also required and can be donethrough the e-Biz Integrator Rules GUI.

• e-Biz Integrator FormatterThe e-Biz Integrator Formatter component is invoked byRules to parse messages and transform them from onerecord format to another. The format libraries are writtenin the language understood by e-Biz Integrator Formatter.In addition to the functionality already provided by thelibraries, the customer must write transformation formatsthat will mediate between our internal format(FFISWIFT) and the customer's required back-officeformats. Those formats can be developed inside the e-BizIntegrator Formatter GUI. Format developmentconstitutes the configuration needed by e-Biz IntegratorFormatter.



• User ExitsUser exits constitute a code module that is invoked by e-Biz Integrator Rules at certain points, under customercontrol, to do complex calculations or enrichments ofmessages. This component is supplied as a shared library(DLL) that consists of compiled code. Source code isprovided for the user exits, which allows customers tocustomize the user exits. The user exits are included withthe format libraries, so they are covered in this manual.User exit configuration consists of creating aconfiguration file (required only for certain exits).

• Format LibrariesThis component is the major topic of this manual. Thesupported SWIFT message types are separated intolibraries. For each SWIFT message type, there is anassociated group of formats and subcomponents. Thesecomponents must be loaded into e-Biz IntegratorFormatter. The e-Biz Integrator Formatter, under thecontrol of e-Biz Integrator Rules, uses these items toparse SWIFT messages, transform the messages into anintermediate code into an intermediate format calledFFISWIFT, and allow customers to convert fromFFISWIFT to the customer's back-office record formats.Going in the to-SWIFT direction, the process is reversed:The libraries allow the customer to convert from back-office formats to FFISWIFT, and then to construct validSWIFT messages from the FFISWIFT. There is noconfiguration required for the format libraries.


SWIFT Format Libraries


The SWIFT Format Libraries comprise several messagetypes, or formats. A complete SWIFT message format is acompound format built in a hierarchical fashion. TheSWIFT format contains subordinate components, which canbe either a compound or flat format, corresponding to theoriginal SWIFT message layout. Refer to the SWIFTdocumentation for description of the SWIFT messagelayouts.

For each message type in the SWIFT libraries, FinancialFusion has created a set of formats to translate data to andfrom the SWIFT network using a simpler structure calledFFISWIFT. FFISWIFT contains all possible subfields in amessage and protects the customer application from dealingwith the complexity of the SWIFT standard.

Review the following sections:

• “Pass Description” on page 20.

• “Formats” on page 22.

• “e-Biz Integrator Rules” on page 26.

• “User Exits” on page 27.

• “SWIFT Preformats” on page 30.

• “SWIFT Preformats Installation” on page 32.



Pass DescriptionEach individual pass is defined as follows:

• PF: the PreFormats insert for e-Biz Integrator Formatterperformance is a “:” at the beginning of the last line of theSWIFT message

• FROM (SWIFT) parses data from the SWIFT networkand reformats it to FFISWIFT.

• CA is the Customer Application pass. It is composed oftwo open ended formats.

– CA_IC### is an input format that parses FFISWIFTand is ready for mapping to an output format that youcreate to match your application.

– CA_SwOC### is an output format that reformats yourapplication input format to FFISWIFT.

• TO (SWIFT) parses and reformats FFISWIFT back into aSWIFT standard format for transmission to the SWIFTnetwork.

For the purpose of reading the following namingconventions chart, terms used for the Format Type in thechart are defined as follows:

• Input: An input format parses the data.

• Output: An output format reformats data from its inputformat to the desired format.

• Compound: The fact that it is a compound type reflectsthat this format is comprised of several subcomponents.These subcomponents are visible in the e-Biz IntegratorFormatter GUI.



Format Library Naming Conventions for Versions 4.x to 5.0

Pass Direction Format Name FormatType

SWIFTMessageType

from FromSWIFT

SW500_SwIC### InputCompound

###

from FromSWIFT

SW500_SwOC100 OutputCompound

###

from FromSWIFT

CA500_IC100This is a message that has beenparsed and reformatted intoFFISWIFT by the SwIC and SwOCformats. This format parsesFFISWIFT. This format is mapped toa format created by the customer tomatch the existing application.

InputCompound

###

to To SWIFT CA500_SwOC100This format reformats the customerapplication format into theFFISWIFT to send back through theIC/OC formats and on to the SWIFTNetwork.

OutputCompound

###

to To SWIFT SW500_IC100This format parses a FFISWIFTmessage that is being sent from thecustomer application TO the SWIFTnetwork.

InputCompound

###

to To SWIFT SW500_OC100This format reformats the messageinto FFISWIFT to send to the SWIFTNetwork.

OutputCompound

###



FormatsYou can view the SWIFT Formats in the e-Biz IntegratorFormatter GUI. Through e-Biz Integrator Formatter, e-BizIntegrator Rules, Formatter, and Messaging translatesmessages from one format to another, simplifying messageexchange between different systems and applications. Thee-Biz Integrator Formatter standardizes how messageformats are described, eliminating the need to custom-codebetween applications to translate each other’s messages.Messages can be converted from any format ascribed toe-Biz Integrator Rules, Formatter, and Messaging to anyother format.

FFISWIFT

The FFISWIFT standard is used as an intermediate state,making it easy to format to any custom application. MostFFISWIFT tags have a fixed length of seven characters.Each field is preceded by a tag, and subfields are delimitedby a double pipe (||).

For example:

Field 32A

SWIFT specification:

6!n3!a15d (Date)(Currency)(Amount)

SWIFT data format:

:32A:001127USD10000,

FFISWIFT:

||32ASA0100||32ASA0211||32ASA0327||32ASA04USD||32ASA0510000,||



FFISWIFT tags comprise three parts. The definition andidentification of its use in the example are as follows:

• SWIFT tag (32A)

Three-character SWIFT tag.

• Sequence indicator (SA)This part of the tag indicates the sequence of themessage. SWIFT divides some messages into portionssuch as Sequence A, Sequence B. This notation is helpfulwhen the same tag is used in different sequences of thesame message. SA is used to indicate sequence A, SB isused to indicate sequence B, and so forth.

• Subfield index (01)These numbers index the subfields of SWIFT tags. In thepreceding example, the date in YYMMDD format isbroken down by FFISWIFT into subfields. Subfield 02corresponds to MM and so forth.

Customer Pass FormatsThe Customer Pass or “CA” formats are a set of formats toparse and reformat FFISWIFT to your existing application.These formats can be used when sending a messageinbound to the SWIFT network or when receiving amessage outbound from the SWIFT network.

NOTE: Do not directly modify the SWIFT Formatcomponents. Components used in the Customer Passformats are also used by the SWIFT Format Librariess. Bychanging a single component you risk breaking SWIFTLibrary Formats that also might be using that formatcomponent. If format modifications are necessary, duplicateand uniquely rename all format components using theFinancial Fusion-provided formats as templates. FinancialFusion does not support modified formats.



CA500_SwOC### to SWIFT

CA500_SwOC### is a set of output formats designed toreformat your data to FFISWIFT. To use this set of formats,you must use SWIFT Library field names in the inputformat definition you create.

To generate the FFISWIFT representation of MT100from your data

1. Create a format that describes your data, using SWIFTLibrary field names. For more information on creatingformats and parsing messages in e-Biz IntegratorFormatter, see the User Guide for WebSphere MQIntegrator, e-Biz Integrator, or e-Biz Integrator Rules,Formatter, and Messaging.

2. Map this format to CA500_SwOC100, provided with theSWIFT Format Libraries.

CA500_SwOC### from SWIFT

CA500_SwOC### is a set of input formats designed toparse FFISWIFT formatted messages.

To use this set of formats

1. Create an output format that describes your datarepresentation. For more information on creating formatsand parsing messages in e-Biz Integrator Formatter, seethe User Guide for WebSphere MQ Integrator, e-BizIntegrator, or e-Biz Integrator Rules, Formatter, andMessaging.

2. Use CA500_IC100 (input format), provided with theSWIFT Format Libraries to map to the output created inthe preceding step.



Blob FormatsThe SWIFT Format Libraries package does not includeTrade Finance messages, because applications that handlethese messages are generally SWIFT-enabled (GEAC SmartStream, for example). SWIFT-enabled applications canprocess SWIFT messages in native format, requiring nomessage formatting or translation.

To route these messages without performing unnecessarydata manipulation, you can use e-Biz Integrator Rules,which requires only header (blocks 1-3) information toevaluate and route the message. For this reason, SWIFTFormat Libraries include two input “blob” formats that treatblock 4, the body of a SWIFT message, as a blob of data,not differentiating between fields. These are provided so e-Biz Integrator Rules can rout the message by the headerfields alone, ignoring the body fields.

• SW500_BLOBIn: use this format for SWIFT inbounddata. For example, use this format to route a messageproduced by a SWIFT-enabled application that containsdata you wish to send to the SWIFT network.

• SW500_BLOBOut: use this format for SWIFT outbounddata. For example, use this format to route a messagereceived from the SWIFT network to a SWIFT-enabledapplication.

NOTE: BLOB formats are available in the System Library.



e-Biz Integrator RulesThe e-Biz Integrator Rules GUI is used to develop rules tomanage message destination IDs, receiver locations,expected message formats, and any processes initiated uponmessage delivery. The dynamic nature of the Rules daemonmeans that rules can be effective immediately, staged overtime, or delayed, depending on how the reload messages aretimed, allowing flexibility in rapidly changingenvironments. Rules can examine the value of any field orgroup of fields in a message to make its determinations. Itcan aggregate conditions with Boolean AND and ORoperators without architectural limits as to the number orcomplexity of the expressions.

The Rules daemon receives the message from SWIFT or thecustomer application and determines message routing basedon the content of the individual fields in the message.Routing destinations can be applications, other rule-basedrouters for distributed architectures, the SWIFT network, orother networks and interfaces.

The SWIFT interface products (such as SWIFTAllianceAccess or ST400) deliver outbound SWIFT messages to anadapter, such as TradeForce for SWIFT - EAI Adapter. Theadapter puts the message to a queue and the Rules daemonretrieves the data from the queue. Subscription logic enteredinto the e-Biz Integrator Rules GUI indicates where themessage is to be routed. This process allows multipleapplications or departments to subscribe to SWIFTmessages and to retrieve those messages via guaranteeddelivery queuing mechanisms by e-Biz Integrator Rules,Formatter, and Messaging.

UERuleng is a modified version of the Rules broker. Itprovides User Exit capabilities. It serves the same functionas the Rules broker, but also assists in the processing ofSWIFT message.



User ExitsUser Exits are used in e-Biz Integrator Formatter and e-BizIntegrator Rules. When you require custom features made toformats, a user exit can be implemented. A User Exit worksby creating custom code and associating it with an outputcontrol. This calls the custom code, which refers to the fieldvalues in an input format. Some examples are table lookups,system date retrieval, determining input field length, etc.

CommonRefThis exit will create a SWIFT common reference field(SWIFT tag 22C) if one is not supplied.

Function name in the source code is:

SndBicRcvBicExchRtToCommonRef

CommonRefAmountFor Message Types 300, 303, 305, 306, 320, 330, 340, 341,350, 600 and 601, the common reference field is generatedfrom two BICs and an amount. e-Biz Integrator Formattershould call this user exit with a single parameter. Forexample:

300CommonRefAmount(id_string)

The id_string is used by the exit to search the“commonref.txt” configuration file for the names of thefields that it should use to calculate the common reference.If the message arrives at the e-Biz Integrator Formatteralready populated with a common reference, the user exitdoes not act.



The following message types call the CommonRefAmountuser type on the direction to SWIFT:

The function name in the source code is

CommonRefAmount

CommonRefDateFor Message Types 360, 361, 362, 364 and 365, thecommon reference field is generated from two BICs and adate. The e-Biz Integrator Formatter should call this userexit with a single parameter. For example:

CommonRefDate(id_string)

The id_string is used by the exit to search the“commonref.txt” configuration file for the names of thefields that it should use to calculate the common reference.If the message arrives at the e-Biz Integrator Formatteralready populated with a common reference, the user exitdoes not act.

The function name in the source code isCommonRefDate

MT300MT303MT305MT306


MT350MT360MT 361MT362




“commonref.txt” Configuration File FormatThe formats of the “commonref.txt” configuration file usedby both the CommonRefAmount and CommonRefDate userexits are as follows:

1. ID_STRING: This field will be used to match against theuser exit call (above).

2. The field name of the first BIC.

3. The field name of the second BIC.

4. The list of field names to be searched for the number.

All fields for one ID_STRING must be on the same line.Field names are separated by one or more blanks.

NOTE: An example commonref.txt file is located in thedistribution User-Exits folder. Place your implementationcommonref.txt file in the directory which contains yourUser Exit shared libraries. For example, nnsy/bin.

UE_ISITC_FFISWIFTThis exit is used to create a series of FFISWIFT tags—onefor ISITC code word that appears in the input message. TheFFISWIFT tags will be the name of the field beingformatted with the first 4 characters dropped and followedby the ISITC code word. For example, if a field 35B insequence B was read into e-Biz Integrator Formatter fieldFLD_SB35B and it contained an /ASCT/ code word, thisexit would add an “SB35B/ASCT/|” tag followed by thevalue for this code word followed by a “|” delimiter.

Function name in the source code is:

UE_ISITC_FFISWIFT



REPLACE_DOTThis sample exit can be used to convert a number string thatuses a US decimal point to a SWIFT comma decimalindicator. If the string does not contain any decimal point(i.e. it is a whole number) then a comma will be appended tothe end. A value of 0 will be converted to “0,00.”

The function name in the source code is

REPLACE_DOT

SWIFT PreformatsThe SW500 preformat pass is a preliminary pass through e-Biz Integrator Rules and e-Biz Integrator Formatter toenable message routing and more efficient parsing andreformatting. These preformats are compatible with theSW300 and above version of the SWIFT Format Library. Ifyou are using any other version of the format library(SW220_ENDSEQ_OLD_CREDIT_DEBIT_PARSE, forexample), you must use the SWIFTMsgProcessor instead ofthe preformats.

The SWIFT500 preformats require default App_Group ofSW500 and a message type of SW500_PF to be set in the.mpf configuration file of EBIZ, MQSI, or at the commandprompt on startup if you are using e-Biz Integrator Rules,Formatter, and Messaging.

The e-Biz Integrator Rules picks up data from a queue andpasses it through the initial format, SW500_PF, whichparses the header and passes block 4 as a Blob message. Thecorresponding output format, SW500_PF_OUT, adds acolon immediately before block 5, the trailer fields. Thisenrichment facilitates formatting a pass through e-BizIntegrator Formatter.



The e-Biz Integrator Rules determines the message typebased on the field SW500_PF_SWhdr_MsgType. The e-BizIntegrator Rules then routes the message through itsappropriate SwIC and SwOC formats, which outputsFFISWIFT.

The SWIFT message is routed through the appropriateformats and placed on a queue before being parsed by theCustomer Application format (CA500_IC###). This is thedefault setup, however, this subscription can be altered sothe message is not output to a queue until after the CustomerApplication formats. The default setup also includes a mocktarget queue of OUTQ. You must modify this to theappropriate queue.



Like the SW500 Format Library, the SW410 preformats areplatform independent with one exception. Mainframe usersare unable to use the CommonRef and CommonRefAmountuser exits that are part of the SWIFT Format Library. Theseuser exits compose a Common Reference field, SWIFT tag22C. If one is not supplied in the customer application data,mainframe users must supply this field in the TO SWIFTdata. The following message types are affected:

SWIFT Preformats InstallationThe installation process includes the following steps:

1. On the command line, enter these session parameters:NNFie –I (lowercase) SW500_PFFormats.exp –s [SessionName]NNFie –I (lowercase) SW500_PFRules.exp –s [SessionName]

2. For e-Biz Integrator and WebSphere MQ Integrator,modify the nnsyreg.dat file to include these defaults:DefaultApplicationGroup = SW500DefaultMessageType = SW500_PF

3. For e-Biz Integrator Rules, Formatter, and Messaging,set these defaults at the command prompt when startingthe Rules engine:App_Group = SW500Message Type = SW500_PF

4. Modify the Rules subscription,OPT_TARGET_QUEUE, to output data to a selectedqueues.



MT350MT360MT 361MT362



Chapter 4

FORMAT LIBRARY USE

The SWIFT Solution requires that you complete thefollowing tasks to ensure the proper routing of messages:

• Creating Queues (optional)

• Mapping Data to the formats

• Testing Formats

• Creating Rules to parse and route the messages

• Running New Era of Networks Broker

Creating Queues (optional)

If your SWIFT Solution requires a transport mechanism,you can use EMQ, WebSphere MQ, or other queuingapplication to create the following five queues (names inparentheses are examples only).

• SWIFT to Financial Fusion (SwToSyQ)

• Financial Fusion to Customer Application (SyToCuQ)

• Customer Application to Financial Fusion (CuToSyQ)

• Financial Fusion to SWIFT (SyToSwQ)


Chapter 4: Format Library Use

For SWIFT inbound messages, you need only the FinancialFusion to SWIFT queue. The Rules daemon places thereformatted message on this queue if specified duringcreation of a routing rule in the e-Biz Integrator Rules GUI.You are not required to create queues to reformat a message,but a transporting mechanism (queueing) might be requiredfor further processing.

Mapping Data

To send messages inbound TO SWIFT, start with dataextracted from your application non-SWIFT-enabledapplication. Compare that data to the format for thecorresponding message type from the SWIFT FormatLibraries SWIFT Format Libraries.

When completing this procedure, think of the following:

• Which fields should be included in the message toSWIFT?

• Does the flat file contain all mandatory fields and datarequired by SWIFT?

• Does the flat file require enrichment to meet SWIFTrequirements?

• What fields will be included and in what order?

Use the e-Biz Integrator Formatter GUI to create an inputformat with appropriate tags and delimiters that define yourmessage. Once you have created this format, view thecorresponding CA500_SwOC### format. use the MapFields tab to map each field to its counterpart in the formatyou just created. For more information on mapping fields,see the User Guide.


Testing Formats

NOTE: Do not modify the formats! You can duplicate aformat and rename with a unique name, if necessary.

Compare the field formats between the two messages.

Testing Formats

Once you have mapped the output from your applicationformats to CA_SwOC, you are ready to test it with msgtest.Type msgtest at a command prompt and follow the systemprompts.

NOTE: Use the msgtest (MQSI and e-Biz Integrator Rules,Formatter, and Messaging) executables found on thestandard MQSI/e-Biz Integrator Rules, Formatter, andMessaging CD.

ApplicationField

ExistingCustomerFormat

SWIFT Field SWIFT Format

Date ddmmyyyy Date yyyymmdd

MonetaryAmount

XXXX.XX Monetary Amount XXXX,XX



Creating Rules

From SWIFT1. Using the NNRie utility, load SW500_PFRules.exp file.

If you use MQSA, load the SW500_PFRules_MQSA.expfile into the e-Biz Integrator Formatter database.

2. Open the Rules Management Console. The following setof generic rules appears in the e-Biz Integrator RulesGUI. A rule appears for every supported message type.


Creating Rules

3. To include a destination queue and customer format,complete the following in the subscription list of themessage type you want to use:

a) Change the default settings for putqueue to yourspecific destination.

a) Add an additional reformat that supports your customformat.

To SWIFT1. In the Rules Management Console, create a subscription

as in the following example.



In the example above, the initial INPUT_FORMAT isthe format you created in your e-Biz IntegratorFormatter and the TARGET_FORMAT(CA500_SwOCXXX) is part of the standard library.

2. To specify your outgoing queue, do the following:

a) Select OUTQ and type your target queue name.

a) Replace it with the queue name you want for eachmessage type that you are using.

Running New Era of Networks Broker

To move messages through e-Biz Integrator Formatter to theSWIFT network and perform the data parsing andmanipulation required for SWIFT inbound messages, startthe broker. After data manipulation is complete, the brokerapplies the appropriate rule to the message and routes itaccordingly.

You have the option to route messages to an output queuefor retrieval from TradeForce for SWIFT - EAI Adapter andfurther message processing. For more information on theTradeForce for SWIFT - EAI Adapter, see the TradeForcefor SWIFT - EAI Adapter Installation and AdministrationGuide.


Chapter 5

UPGRADE INFORMATION

This chapter includes the information necessary to upgradefrom TradeForce SWIFT for EAI version 4.10 to version5.0. The information covered in this chapter includes thefollowing:

• SWIFT Format Libraries 2002 Change Details

• SWIFT Format Library 2002 Upgrade Strategies

SWIFT Format Libraries Change Details

There are two primary changes to the format libraries:

• A change in component prefixes in the new library. Fordetails, see “SW500 Prefixes” on page 40.

• An upgrade of SWIFT formats to the new SWIFT 2002standards. For details, see “SWIFT 2002 MessageChange Information” on page 40.


Chapter 5: Upgrade Information

SW500 PrefixesAll the components in the new library, except field names,are prefixed by SW500.

SWIFT 2002 Message Change InformationThe “Changed by SWIFT for 2002” column in the tablebelow indicates that SWIFT has made a change in themessage for the 2002 standards upgrade. Many of thechanges, such as new qualifiers, do not require the formatsto be upgraded. Only messages that have a “Y” (yes) in the“Format Changes” column need to be upgraded. Otherwise,the SW220, SW212, SW211, or SW410 messages willcontinue to work normally for the SWIFT 2002 upgrade.

MessageNumber

Supported inVersion 5.0

Changed bySWIFT for 2002

FormatChanges

100 Y N N

101 Y Y Y

102 Y Y Y

102P Y Y Y

103 Y Y Y

103P Y Y Y

MT104 Y Y Y

MT107 Y Y Y

MT110 Y Y Y

MT111 Y N N

MT112 Y N N

MT190 Y N N

MT191 Y N N

MT192 Y N N



MT195 Y N N

MT196 Y N N

MT198 Y N N

MT199 Y N N

MT200 Y N N

MT201 Y N N

MT202 Y Y Y

MT203 Y Y N

MT204 Y Y N

MT205 Y N N

MT206 Y N N

MT207 Y Y N

MT210 Y N N

MT256 Y N N

MT290 Y N N

MT291 Y N N

MT292 Y N N

MT293 Y N N

MT295 Y N N

MT296 Y N N

MT298 Y N N

MT299 Y N N

MT300 Y Y Y

MT303 Y Y Y

MT304 Y N N

MT305 Y N N

MessageNumber



FormatChanges



MT306 Y N N

MT307 Y Y-NEW Y-NEW

MT308 Y Y-NEW Y-NEW

MT320 Y Y Y

MT321 Y N N

MT330 Y Y Y

MT340 Y N N

MT341 Y N N

MT350 Y Y Y

MT360 Y Y Y

MT361 Y Y Y

MT362 Y Y Y

MT364 Y Y Y

MT365 Y Y Y

MT380 Y Y-NEW Y-NEW

MT381 Y Y-NEW Y-NEW

MT390 Y N N

MT391 Y N N

MT392 Y N N

MT395 Y N N

MT396 Y N N

MT398 Y N N

MT399 Y N N

MT400 Y N Y

MT405 Y Y Y

MT410 Y N N

MessageNumber



FormatChanges



MT412 Y N N

MT416 Y Y N

MT420 Y N N

MT422 Y N N

MT430 Y N N

MT450 Y Y N

MT455 Y Y N

MT456 Y Y N

MT490 Y N N

MT491 Y N N

MT492 Y N N

MT495 Y N

MT496 Y N N

MT498 Y N N

MT499 Y N N

MT500 Y Y-NEW Y-NEW

MT501 Y Y-NEW Y-NEW

MT502 Y Y Y

MT503 Y Y N

MT504 Y Y Y

MT505 Y Y Y

MT506 Y Y N

MT507 Y Y Y

MT508 Y Y N

MT509 Y Y N

MT510 Y Y-NEW Y-NEW

MessageNumber



FormatChanges



MT512 N-DELETED N N

MT513 Y Y Y

MT514 Y Y Y

MT515 Y Y Y

MT516 Y Y N

MT517 Y Y N

MT518 Y Y Y

MT519 Y Y-NEW Y-NEW

MT520 N-DELETED

MT521 N-DELETED

MT522 N-DELETED

MT523 N-DELETED

MT524 Y N N

MT526 Y N N

MT527 Y N N

MT528 Y Y Y

MT529 Y Y Y

MT530 N-DELETED

MT531 N-DELETED

MT532 N-DELETED

MT533 N-DELETED

MT534 N-DELETED

MT535 Y Y Y

MT536 Y Y Y

MT537 Y Y Y

MT538 Y N N

MessageNumber



FormatChanges



MT539 N-DELETED

MT540 Y Y Y

MT541 Y Y Y

MT542 Y Y Y

MT543 Y Y Y

MT544 Y Y Y

MT545 Y Y Y

MT546 Y Y Y

MT547 Y Y Y

MT548 Y Y Y

MT549 Y N N

MT550 N-DELETED

MT551 N-DELETED

MT552 N-DELETED

MT553 N-DELETED

MT554 N-DELETED

MT555 N-DELETED

MT556 N-DELETED

MT557 N-DELETED

MT558 Y N N

MT559 Y N N

MT560 N-DELETED

MT561 N-DELETED

MT562 N-DELETED

MT563 N-DELETED

MT564 Y Y Y

MessageNumber



FormatChanges



MT565 Y Y Y

MT566 Y Y Y

MT567 Y Y Y

MT568 Y N N

MT569 Y N N

MT570 N-DELETED

MT571 N-DELETED

MT572 N-DELETED

MT573 N-DELETED

MT574I Y Y-NEW Y-NEW

MT574W Y Y-NEW Y-NEW

MT575 Y Y Y

MT576 Y Y Y

MT577 Y N N

MT578 Y Y Y

MT579 Y N N

MT580 N-DELETED

MT581 Y N N

MT582 Y N N

MT583 N-DELETED

MT584 Y Y Y

MT586 Y Y Y

MT587 Y N N

MT588 Y N N

MT589 Y Y Y

MT590 Y N N

MessageNumber



FormatChanges



MT591 Y N N

MT592 Y N N

MT595 Y N N

MT596 Y N N

MT598 Y N N

MT599 Y N N

MT600 Y N N

MT601 Y N N

MT604 Y N N

MT605 Y N N

MT606 Y N N

MT607 Y N N

MT608 Y N N

MT609 Y N N

MT643 Y Y N

MT644 Y Y N

MT645 Y Y N

MT646 Y Y N

MT649 Y N N

MT690 Y N N

MT691 Y N N

MT692 Y N N

MT695 Y N N

MT696 Y N N

MT698 Y N N

MT699 Y N N

MessageNumber



FormatChanges



MT700 Y N N

MT701 Y N N

MT705 Y N N

MT707 Y N N

MT710 Y N N

MT711 Y N N

MT720 Y N N

MT721 Y N N

MT730 Y N N

MT732 Y N N

MT734 Y N N

MT740 Y N N

MT742 Y N N

MT747 Y N N

MT750 Y N N

MT752 Y N N

MT754 Y N N

MT756 Y N N

MT760 Y N N

MT767 Y N N

MT768 Y N N

MT769 Y N N

MT790 Y N N

MT791 Y N N

MT792 Y N N

MT795 Y N N

MessageNumber



FormatChanges



MT796 Y N N

MT798 Y N N

MT799 Y N N

MT900 Y N N

MT910 Y Y Y

MT920 Y N N

MT935 Y N N

MT940 Y Y Y

MT941 Y Y Y

MT942 Y N N

MT950 Y Y Y

MT970 Y Y Y

MT971 Y N N

MT972 Y Y Y

MT973 Y N N

MT985 Y N N

MT986 Y N N

MT990 Y N N

MT991 Y N N

MT992 Y N N

MT995 Y N N

MT996 Y N N

MT998 Y N N

MT999 Y N N

MT010 Y N N

MT011 Y N N

MessageNumber



FormatChanges



MT012 Y N N

MT015 Y N N

MT019 Y N N

MT082 Y N N

MT083 Y N N

MT094 Y N N

ACK/NAK Y N N

MessageNumber



FormatChanges


SWIFT Library Migration


Software RequirementsThis upgrade, whether full or partial, requires a pre-installation of e-Biz Integrator Rules, Formatter version 3.2or later, and Messaging Integration software.

Note: The use of the SWIFT 2002 Format Library withearlier versions of the e-Biz Integrator is not supported andmay produce errors.

Full UpgradeThis section describes the typical upgrade to the SWIFTFormat Libraries 5.0 to comply with the Message Standard15022.

SWIFT Format Library

New Era of Networks Rules,Formatter, and Messaging

SWIFTAlliance

New Era ofNetworks

Adapter forSWIFT

New Era ofNetworks

Access

SWIFT

CAS

Queuing System

Database

Database

CustomerApp

New Era of NetworksSWIFT SOLUTION

V. 5.0.

SW500SwOCOutput

SW500OC

Output

SW500IC

Input

CA500_ICInput

CA500_SwOC

Output

SW500SwICInput

FFISWIFT

FFISWIFT

CustomerApplication

FormatsOutput

CustomerApplication

FormatsInput

SW500

PPInput

SW500PP_OUT

Output

Preformats

Database



Partial UpgradeIf you want to run the e-Biz Integrator Rules, Formatter, andMessaging integration software in conjunction with theSWIFT Format Libraries, to keep an existing 7775 MessageStandard implementation for inbound SWIFT messages,and to send 15022 messages out to the SWIFT network, youneed to make the following adjustments.

To complete a partial upgrade

1. Using NNFie, load the 2002 messages (SW500) into themessage database which already contains the 2001messages.

2. Upgrade your e-Biz Integrator Formatter database to 3.2or later. These releases include:

- e-Biz Integrator 3.x

- WebSphere MQ Integrator 2.x.

3. Update all rules in your e-Biz Integrator Rules databasewith new message types.

4. Duplicate the Standard Library Format CA500_ICXXX.

5. Rename your formats using your own company namingconventions.

6. Replace the existing Customer Application Input formatwith the CA500_ICXXX Standard Input format. TheCustomer Application Input format automatically mapsto the CA500_SwOCXXX format.

7. Using your back office application, generate the dataneeded for the 2002 messages to be sent to the SWIFTnetwork. Avoid customization by generating input datausing a || delimiter. For example:

3455||gtft667||99i9i9weu||…



NOTE: If your back-office application cannot generate thenecessary data, use a data enrichment scheme during theCA500_SwOCXXX parse with the use of user exits.

The following diagram illustrates such a partialimplementation:

NOTE: For further assistance with a Partial Upgrade pleasecall Financial Fusion Technical Support.

S W IF T F o r m a t L ib r a r y

N e w E r a o f N e t w o r k s R u le s ,F o r m a tt e r , a n d M e s s a g in g

S W IF TA ll i a n c e

N e w E r a o fN e t w o r k s

A d a p te r fo rS W IF T

N e w E r a o fN e t w o r k s

A c c e s s

S W IF T

C A S

Q u e u in g S y s t e m

D a ta b a s e D a ta b a s eD a ta b a s e

C u s t o m e rA p p

N e w E r a o f N e t w o r k sS W IF T M IG R A T IO N S O L U T IO N

F R O M V 2 .X T O V . 5 .0 .

S W 2 2 0S w O C

O u t p u t

S W 5 0 0O C

O u t p u t

S W 5 0 0IC

In p u tC A 5 0 0 _ S wO C O u t p u t

S W 2 2 0S w ICIn p u t

I F F S W IF T

IF F S W IF T C A 5 0 0 _ ICIn p u t

S W IF TP r e P r o c e s s o r

S W 2 2 0S w IC -2

In p u t

S W 2 2 0S w O C - 2O u t p u t

D a ta E n r ic h m e n tv ia U s e r E x it

D a ta b a s e O R /A N D

U p d a teC u s to m e r

In p u tA p p l ic a t io n

w ith d a tafo r N e w

M e s s a g eS ta n d a r d

C A 2 2 0In p u t

C u s to m e rA p p li c a t io n

F o r m a tsO u t p u t


Appendix A

SUPPORT FOR PREVIOUSFFISWIFT VERSIONS

Multiple Library Versions for Compatibility

Where messages have not been changed by SWIFT,Financial Fusion is providing versions of the formats thatwill use or produce various versions of FFISWIFT that havebeen released in the past in order to provide as muchbackward compatibility as possible.

The following SWIFT library version is included in eachCD:

• SW500

The following SWIFT library versions will be provided asneeded:

• SW500_WO_COMPLETE_HEADER

• SW500_ENDSEQ_OLD_CREDIT_DEBIT

• SW500_ENDSEQ

• SW500_OLD_CREDIT_DEBIT


Appendix A: Support for Previous FFISWIFT Versions

The last three library versions allow you to upgrade fromSWIFT versions 2.x. These versions allow you to acceptSWIFT Standard 2002 messages while maintaining thecurrent format of FFISWIFT. The only required changes tothe CA formats are those which connect your applicationand follow the SWIFT 2002 standards. If you choose anupgrade version, it allows messages not changed in theSWIFT 2002 standards to require no changes to theFFISWIFT or Customer Application formats.

The appropriate version of the library can be determined byexamining the format of the existing FFISWIFT andmatching it with its appropriate versions. Users should keepin mind that in choosing an upgrade library, they will not betaking advantage of the finer granularity parse that SW500offers over the SWIFT 2.x version.

SW500SW500 is the standard library. It has been upgraded toinclude the SWIFT 2002 standards changes and does notrequire the pre-processor however it does require thepreformats.

SW450_WO_COMPLETE_HEADER

This is the same as the standard SW500 library with theexception of the header. This version of the library uses theless granular parse on the header that was used in previousreleases.

For specific field information, see Appendix B: “FFISWIFTHeader”.


Multiple Library Versions for Compatibility

SW500_ENDSEQ_OLD_CREDIT_DEBITThis is the SW500 library built to be backward compatiblewith versions of FFISWIFT in release SW2xx (excludingthe messages that have a tag 61). This library is intended forusers who would like to maintain as much compatibilitywith release SW2xx as possible.

This version outputs FFISWIFT that contains the delimiter“ENDSEQ” to mark the end of repeating sequences. Inaddition, it parses in the party fields as one field instead ofbreaking the credit debit field into its own field.

This version uses the less granular approach to parsing theheader. For more information, see Appendix B: “FFISWIFTHeader”.

SW500_ENDSEQ

This includes the standard library with two changes. TheFFISWIFT will include an ENDSEQ after each repeatingsequence. This library uses the less granular approach toparsing the header. For more information, see Appendix B:“FFISWIFT Header”.

SW500_OLD_CREDIT_DEBIT

This is the SW500 library built to be backward compatiblewith older versions of the party fields (5xA, 5xD, 8xA, and8xD) parse. However, this version does not expect any typeof “ENDSEQ” to mark the end of repeating sequences. Thisversion uses the less granular approach to parsing theheader. For more information, see Appendix B: “FFISWIFTHeader”.


Appendix B

THE FFISWIFT HEADER

The FFISWIFT header has two definitions depending on thedirection—to SWIFT or from SWIFT. SWIFT blocks 1 and2 are positional. The format is data, terminated by ||.

Normal FFISWIFT (FROM SWIFT)

The from SWIFT header:

{1:F01VNDZBET2BXXX0001000002}{2:O5021200910103BANKBEBBAXXX22221234569101031201N}{3:{113:xxxx}{108:abcdefgh12345678}}

The from SWIFT FFISWIFT header:

F||01||VNDZBET2BXXX||0001||000002||O||502||1200||910103||BANKBEBBAXXX||2222||123456||910103||1201||N||113SA01xxxx||108SA01abcdefgh12345678||


Appendix B: The FFISWIFT Header

Table 1: SWIFT Block 1


Position Man/Opt

FFISWIFT FieldName

SWIFT Field Name Data

1 Man SWhdr_AppID Application Identifier F

2 Man SWhdr_APDU Servive Identifier 01

3 Man Receiver_BIC_CodeReceiver_LTReceiver_Branch_Code

LT Address VNDZBET2BXXX

4 Man SWhdr_SessNbr Session Number 0001

5 Man Sequence Number Sequence Number (ISNor OSN)

000002

Position Man/Opt

FFISWIFT FieldName


6 Man SWhdr_I/Oind Input/Output Identifier O

7 Man SWhdr_MsgType Message Type 502

8 Man SWhdrInput_Time Input Time 1200

9 Man SWhdrInput_Date Date from MIR 910103

10 Man Sender_BIC_CodeSender_LTSender_Branch_Code

BIC from MID BANKBEBBAXXX

11 Man SWhdrInp_Session_Num

Session Number fromMIR

2222

12 Man SWhdrInp_Seq_Num Sequence Number fromMIR

123456

13 Man SWhdrOutput_Date Output Date 910103

14 Man SWhdrOutput_Time Output Time 1201

15 Man SWhdrMsg_Priority Message Priority N


FFISWIFT with Full Header (FROM SWIFT)


FFISWIFT with Full Header (FROM SWIFT)

The from SWIFT header:

{1:F01VNDZBET2BXXX0001000002}{2:O5021200910103BANKBEBBAXXX22221234569101031201N}{3: {103:LCN}{113:xxxx}{108:abcdefgh12345678}{119:REMIT}{115: PaymentReleaseInfo}}

The from SWIFT FFISWIFT header:

F||01||VNDZBET2BXXX||0001||000002||O||502||1200||910103||BANKBEBBAXXX||2222||123456||910103||1201||N||103SA01LCN||113SA01xxxx||108SA01abcdefgh12345678||119SA01REMIT||115SA01PaymentReleaseInfo ||


Position Man/Opt

FFISWIFT FieldName


NA Opt BankingPriority Banking Priority Xxxx

NA Opt MessageUserReference Message User Reference(MUR)

Abcdefgh12345678

Position Man/Opt

FFISWIFT FieldName


1 Man SWhdr_AppID Application Identifier F

2 Man SWhdr_APDU Servive Identifier 01

3 Man Receiver_BIC_CodeReceiver_LTReceiver_Branch_Code

LT Address VNDZBET2BXXX

4 Man SWhdr_SessNbr Session Number 0001

5 Man Sequence Number Sequence Number (ISNor OSN)

000002





Position Man/Opt

FFISWIFT FieldName


6 Man SWhdr_I/Oind Input/Output Identifier O


8 Man SWhdrInput_Time Input Time 1200

9 Man SWhdrInput_Date Date from MIR 910103

10 Man Sender_BIC_CodeSender_LTSender_Branch_Code

BIC from MID BANKBEBBAXXX

11 Man SWhdrInp_Session_Num

Session Number fromMIR

2222

12 Man SWhdrInp_Seq_Num Sequence Number fromMIR

123456

13 Man SWhdrOutput_Date Output Date 910103

14 Man SWhdrOutput_Time Output Time 1201


Position Man/Opt

FFISWIFT FieldName


NA Opt ServiceID service-code LCN

NA Opt BankingPriority Banking Priority Xxxx

NA Opt MessageUserReference Message User Reference(MUR)

Abcdefgh12345678

NA Opt ValidationFlag Validation flag REMIT

NA Opt AddresseeInfo Payment-release-information-receiver

PaymentReleaseInfo


Normal FFISWIFT (TO SWIFT)

Normal FFISWIFT (TO SWIFT)

The to SWIFT header:

{1:F01MLCOUS33GXXX0000000000}{2:O502BANKPB33GXXXN2020}{3:{113:xxxx}{108:abcdefgh12345678}}

The to SWIFT FFISWIFT header:

01||MLCOUS33G||XXX||502||BANKPB33G||XXX||N||2||020||xxxx||abcdefgh12345678||



Position Man/Opt

FFISWIFT FieldName


1 Man SWhdr_APDU Application Identifier 01

2 Man SWhdr_SourceBank Service Identifier MLCOUS33G

3 Man SWhdr_SourceBranch LT Address XXX

Position Man/Opt

FFISWIFT FieldName



5 Man SWhdr_DestBank Destination Address BANKPB33G

6 Man SWhdr_DestBrach Destination Address XXX


8 Man SWhdr_Delivery Delivery Monitoring 2

9 Man SWhdr_Obsol Obsolescence Period 020




FFISWIFT with Full Header (TO SWIFT)

The to SWIFT header:

{1:F01MLCOUS33GXXX0000000000}{2:O502BANKPB33GXXXN2020}{3:{103:}{113:xxxx}{108:abcdefgh12345678}{119:REMIT} {115:PaymentReleaseInfo}}

The to SWIFT FFISWIFT header:

01||MLCOUS33G||XXX||502||BANKPB33G||XXX||N||2||020||LCN||xxxx||abcdefgh12345678||REMIT||PaymentReleaseInfo ||


Position Man/Opt

FFISWIFT FieldName


10 Opt SWhrd_BankingPriority Banking Priority 113SA01xxxx

11 Opt SWhdr_MUR Message User Reference(MUR)

108SA01abcdefgh12345678

Position Man/Opt

FFISWIFT FieldName


1 Man SWhdr_APDU Application Identifier 01

2 Man SWhdr_SourceBank Service Identifier MLCOUS33G

3 Man SWhdr_SourceBranch LT Address XXX


FFISWIFT with Full Header (TO SWIFT)



Position Man/Opt

FFISWIFT FieldName



5 Man SWhdr_DestBank Destination Address BANKPB33G

6 Man SWhdr_DestBrach Destination Address XXX


8 Man SWhdr_Delivery Delivery Monitoring 2

9 Man SWhdr_Obsol Message Obsolescence 020

Position Man/Opt

FFISWIFT FieldName


10 Opt SWhrd_ServiceID Service Identifier LCN

11 Opt SWhrd_BankingPriority Banking Priority xxxx

12 Opt SWhdr_MUR Message User Reference(MUR)

abcdefgh12345678

13 Opt SWhrd_ValidationFlag Validation Flag REMIT

14 Opt SWhrd_AddresseeInfo Addressee Information PaymentReleaseInfo


Appendix C

THE FFISWIFT TRAILER

The FFISWIFT trailer has definitions depending on thedirection—to SWIFT or from SWIFT.

From SWIFT

SWIFT trailer

The SWIFT trailer, block 5, consists of a list of trailer fields.Each field consists of:

{5:{< SWIFT trailer tag>: [<data>]}{< SWIFT trailer tag>: [<data>]}…}

For example:

{5:{MAC:41720873}{CHK:123456789ABC}}

FFISWIFT trailer definition<SWIFT trailer tag with colon>[<data>]||<SWIFT trailer tag with colon>[<data>]||…

The FFISWIFT equivalent of the example above.

MAC:41720873||CHK:123456789ABC||


Appendix C: the FFISWIFT Trailer

To SWIFT

The outbound FFISWIFT trailer is a properly formattedSWIFT trailer without the enclosing block 5 start of blockand close of block.

SWIFT outbound trailer {5:{< SWIFT trailer tag>: [<data>]}{< SWIFT trailer tag>: [<data>]}…}

For example:

{5:{MAC:41720873}{CHK:123456789ABC}}

FFISWIFT trailer definition{< SWIFT trailer tag>: [<data>]}{< SWIFT trailer tag>: [<data>]}…||

The to SWIFT FFISWIFT equivalent of the example above.

{MAC:41720873}{CHK:123456789ABC}||


Appendix D

RULE CHANGES FORUPGRADING PRE-410 VERSIONS

Modifying Rule Expressions

The SW500 library represents nearly a complete rewrite ofthe SWIFT formats, and as part of the rewrite all the fieldnames have changed. This is for several reasons. First, theSW211, SW212 and SW220 libraries had header fieldnames prefixed by the library version number. Theseversion numbers have been removed. Second, the old nameswere inconsistent in their spelling, use of capitalization, etc.They are now much more consistent.

A typical rule expression is as follows:


Appendix D: Rule Changes for Upgrading pre-410 Versions

The rule references a field from the header. To upgrade thelibrary, this rule will need to be changed. (See “Mapping ofHeader Field Names” below for the field name mappings.)

From the mapping, “SW211_SWhdr_MsgType” should bereplaced with SWhdr_MsgType. If any fields from the bodyof the message are referenced in a rule, then it is necessaryto find the equivalent field(s) in the SW500 message. Seeexample below from the Rules GUI.


Modifying Rule Expressions



Modifying Rule Subscriptions

Subscriptions also need to be modified.

In the rules above, the most significant change is from twopasses to one pass. The first reformat should be changedfrom SW211_SwIC522 to SW500_SwIC522 andSW211_SwOC522 to SW500_SwOC522 (see below). Thesecond reformat should be completely removed.


Modifying Rule Subscriptions

In the case above, the first putqueue sets theOPT_MSG_TYPE to SW211_SwIC522. The function ofthe put should be examined to determine if theOPT_MSG_TYPE should be set to SW500_SwIC522.



Mapping of Header Field Names

From SWIFTVersion 2.2

SW220 Field Names SW300 and SW410 Field Names

SW220_BasicHeaderBlock BasicHeaderBlock

SW220_SWhdr_AppID SWhdr_AppID

SW220_SWhdr_APDU SWhdr_APDU

SW220_SWhdr_LT_Addr(REC) Receiver_ BIC_CodeReceiver_LTReceiver_Branch_Code

SW220_SWhdr_SessNbr SWhdr__SessNbr

SW220_Sequence Number SequenceNumber

SW220_SWhdr_I/Oind SWhdr_I/Oind

SW220_SWhdr_MsgType SWhdr_MsgType

SW220_SWhdr_Input_Time SWhdr_Input_Time

SW220_SWhdr_Input_Date SWhdr_Input_Date

SW220_SWhdr__LTAddress(SNDR) Sender_BIC_CodeSender_LTSender_Branch_Code

SW220_SWhdrInp_Session_Num SWhdrInp_Session_Num

SW220_SWhdrInp_Seq_Num SWhdrInp_Seq_Num

SW220_SWhdrOutput_Date SWhdrOutput_Date

SW220_SWhdrOutput_Time SWhdrOutput_Time

SW220_SWhdrMsg_Priority SWhdrMsg_Priority

SW220_UserHeaderBlock1 BankingPriority

SW220_UserHeaderBlock2 MessageUserReference


Mapping of Header Field Names

Version 2.1


SW211_BasicHeaderBlock BasicHeaderBlock

SW211_SWhdr_AppID SWhdr_AppID


SW211_SWhdr_LT_Addr(REC) Receiver_ BIC_CodeReceiver_LTReceiver_Branch_Code

SW211_SWhdr_SessNbr SWhdr__SessNbr

SW211_Sequence Number SequenceNumber

SW211_SWhdr_I/Oind SWhdr_I/Oind


SW211_SWhdr_Input_Time SWhdr_Input_Time

SW211_SWhdr_Input_Date SWhdr_Input_Date

SW211_SWhdr__LTAddress(SNDR) Sender_BIC_CodeSender_LTSender_Branch_Code

SW211_SWhdrInp_Session_Num SWhdrInp_Session_Num

SW211_SWhdrInp_Seq_Num SWhdrInp_Seq_Num

SW211_SWhdrOutput_Date SWhdrOutput_Date

SW211_SWhdrOutput_Time SWhdrOutput_Time


SW211_UserHeaderBlock1 BankingPriority

SW211_UserHeaderBlock2 MessageUserReference



To SWIFTVersion 2.2

Version 2.1



SW220_SWhdr_SourceBank SWhdr__SourceBank

SW220_SWhdr_SourceBranch SWhdr__SourceBranch


SW220_SWhdr_DestBank SWhdr_DestBank

SW220_SWhdr_DestBranch SWhdr_DestBranch


SW220_SWhdr_Delivery SWhdr_Delivery

SW220_SWhdr_Obsol SWhdr_Obsol

SW220_SWhdr_BankingPriority SWhdr_BankingPriority

SW220_SWdhr_MUR SWhrd_MUR



SW211_SWhdr_SourceBank SWhdr__SourceBank

SW2110_SWhdr_SourceBranch SWhdr__SourceBranch


SW211_SWhdr_DestBank SWhdr_DestBank

SW211_SWhdr_DestBranch SWhdr_DestBranch


SW211_SWhdr_Delivery SWhdr_Delivery

SW211_SWhdr_Obsol SWhdr_Obsol

SW211_SWhdr_BankingPriority SWhdr_BankingPriority

SW211_SWdhr_MUR SWhrd_MUR


INDEX

Bblob formats 25

CCA formats 23CA500_SwOC### 24chapter summary viiiCommonRef 27commonref.txt 29CommonRefAmount 27CommonRefDate 28components

TradeForce for SWIFT - EAI 16configuration

file format 29conventions, used in this guide ixCustomer Pass formats 23

Ddata parsing, using broker 38database connection 8databse, creating and configuring 8directory structure

documentation and User Exit 10library 11pre-formats 11

documentation set, overview 3

Ee-Biz Integrator Formatter 17e-Biz Integrator Rules 17, 26education services 6extracting installation files 9

FFFISWIFT 22Format Libraries 18formats

blob 25import 13message passes 22naming convention 21outbound 24

formats, testing 35formatsCA500_SwOC### 24

GGUI rules 26

Hhelp, obtaining ix

IIFT 36install, processor file structure 9


Index

installation files, extracting 9installing the SWIFT Format

Libraries 9

Mmapping data map 34messages moving, using broker 38migration of SWIFT Libraries

full upgrade 51partial upgrade 51

Msgtest 35

Nnaming convention 21Network Broker, running 38NNFie 13

Ooutbound format 24overview, of this guide vii

Ppass description, about 20path 12PATH variable, setting 12platforms, supported 1Preformats 17processor, directory structure 9

Qqueues 16

creating 33

Rrelated documentation 3REPLACE_DOT 30rules GUI 26rules, creating from SWIFT 36rules, creating to SWIFT 37

SS.W.I.F.T. Format Libraries

configuring database connection 8creating database connection 8

Sequence indicator 23sqlsvses.cfg 8Subfield index 23support services, more information 6supported platforms 1SW500 56SW500_ENDSEQ 57SW500_ENDSEQ_OLD_CREDIT_

DEBIT 57SW500_OLD_CREDIT_DEBIT 57SW500_WO_COMPLETE_

HEADER 56SWIFT 2002 message change

information 40SWIFT Format Libraries

change details 39importing formats 13

SWIFT formats, viewing 22SWIFT preformats, installing 32

TTradeForce for SWIFT - EAI

components 16TradeForce for SWIFT - EAI

Adapter 16


Index

UUE_ISITC_FFISWIFT 29user exits 18, 27

CommonRef 27CommonRefAmount 27CommonRefDate 28REPLACE_DOT 30UE_ISITC_FFISWIFT 29

Vversion compatibility 55

Format Library Installation and Administration Guide 79

Financial Fusion - Trade Force for SWIFT - Version 5

Documents

Transcript of Financial Fusion - Trade Force for SWIFT - Version 5