Financial Fusion

Financial Fusion
TradeForce for SWIFT - EAI v e r s i o n 5.0
Format Library
Installation and Administration Guide
Financial Fusion and Financial Fusion Server are trademarks of Financial Fusion, Inc. Sybase and Sybase Central are trademarks of Sybase, Inc. WebLogic is a trademark of BEA Systems, Inc. Oracle is a trademark of Oracle Corporation. iPlanet is a trademark of the Sun-Netscape Alliance. SPARC is a trademark of SPARC International, Inc. NT is a trademark of Microsoft Corporation. Solaris, Java, and all Java-based marks 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 or by any means, electronic or mechanical, including photocopying, recording or through storage and retrieval mechanisms, without prior written 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix If You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Product Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Cross-Platform Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Product Support and Education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Creating and Configuring the Database . . . . . . . . . . . . . . . . . . . . . . . . 8 Extracting Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Documentation and User Exit Directory Structure. . . . . . . . . . . . 10 Pre-Formats Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . 11 Library Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Setting the PATH Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Importing Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 TradeForce for SWIFT - EAI Components . . . . . . . . . . . . . . . . . . . . 16 SWIFT Format Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Pass Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
iii
Table of Contents
e-Biz Integrator Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 User Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 SWIFT Preformats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 SWIFT Preformats Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Format Library Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Creating Queues (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Mapping Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Testing Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Creating Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 From SWIFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 To SWIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Running New Era of Networks Broker. . . . . . . . . . . . . . . . . . . . . . . . 38 Upgrade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 SWIFT Format Libraries Change Details . . . . . . . . . . . . . . . . . . . . . . 39 SW500 Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 SWIFT 2002 Message Change Information . . . . . . . . . . . . . . . . . 40 SWIFT Library Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Full Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Partial Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Appendix A: Support for Previous FFISWIFT Versions . . . . . . . . . . 55 Multiple Library Versions for Compatibility . . . . . . . . . . . . . . . . . . . 55 Appendix B: The FFISWIFT Header . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Normal FFISWIFT (FROM SWIFT) . . . . . . . . . . . . . . . . . . . . . . . . . 59 FFISWIFT with Full Header (FROM SWIFT). . . . . . . . . . . . . . . . . . 61 Normal FFISWIFT (TO SWIFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 FFISWIFT with Full Header (TO SWIFT). . . . . . . . . . . . . . . . . . . . . 64 Appendix C: The FFISWIFT Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . 67 From SWIFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 To SWIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
iv
Table of Contents
Appendix D: Rule Changes for Upgrading pre-410 Versions of the SWIFT Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Modifying Rule Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Modifying Rule Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Mapping of Header Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 From SWIFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 To SWIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
ABOUT THIS BOOK

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

The SWIFT Format Libraries are a set of prepackaged formats that provide one component of the TradeForce for SWIFT EAI. The TradeForce for SWIFT EAI facilitates data conversion and message enrichment between the SWIFT network and legacy or third-party systems. The entire 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 are documented separately.
vii
About this Book
This document is designed to help you effectively install and use the SWIFT Format Libraries. For information on installing and configuring the TradeForce for SWIFT - EAI Adapter, refer to the TradeForce for SWIFT - EAI Adapter Installation and Administration Guide.
Chapter Summary
This guide is organized into the following chapters: Chapter 1: Introduction provides a brief introduction to the format libraries, a list of available documentation, and technical support information. Chapter 2: Installation provides instructions on installing and configuring the format libraries package. Chapter 3: Product Description provides information on the use of the SWIFT Format components Chapter 4: Format Library Use provides information on setting up formats to be used. Chapter 5: Upgrade Information provides upgrade information from previous versions of the TradeForce for SWIFT - EAI Adapter solution. Appendix A: Support for Previous FFISWIFT Versions provides information on upgrading. Appendix B: FFISWIFT Header provides FFISWIFT header definitions for to-SWIFT or from-SWIFT messages. Appendix C: FFISWIFT Trailer provides FFISWIFT trailer definitions for to-SWIFT or from-SWIFT messages. Appendix D: Rule Changes Required to Upgrade pre410 Versions of the SWIFT Library contains information necessary to upgrade your system.
viii
About this Book
Conventions Used in This Guide

This guide uses the following typeface and style conventions:
Convention
Code Elements
Used for
All Java, XML, and HTML code elements are set in Lucida Sans Unicode. The angle bracket indicates movement from one option list to the next. File names, path names, and directories are set in italics.
Menu > Submenu Italics
Some of the lines of code in the examples must be entered without a return break. The arrow in the example below indicates 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 Support Services if you have questions or need technical support. Note: Each Financial Fusion installation that has purchased a support contract has one or more designated people who are authorized to contact technical support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Financial Fusion technical support or the Financial Fusion subsidiary in your area.
ix
Chapter 1
INTRODUCTION
This chapter includes the following information:
Supported Platforms Product Documentation Set Product Support and Education
Supported Platforms
Integration Server
e-Biz Integrator 3.6 WebSphere MQ Integrator 2.1
Operating System
Windows NT 4 sp 6a Windows 2000 sp 2
DBMS
Sybase ASE 12, 12.5 SQL Server 2000 SQL Server 7 Oracle 8i, 8.1.6, 8.1.7 DB2 UDB 7.1. 7.2 Sybase ASE 12, 12.5 Oracle 8i, 8.1.6, 8.1.7 DB2 UDB 7.1. 7.2 Sybase ASE 12, 12.5 Oracle 8i, 8.1.6, 8.1.7 DB2 UDB 7.1. 7.2 DB2 UDB 7.1. 7.2
e-Biz Integrator 3.6 WebSphere MQ Integrator 2.1 e-Biz Integrator 3.6.1 WMQI 2.1 e-Biz Integrator 3.6.1 WMQI 2.1
Solaris 7, 8
AIX 5.1
s/390 Version 2.8
Installation and Administration Guide 1
Chapter 1: Introduction
NOTE: If you plan to use the SWIFT Format Libraries 5.0 with e-Biz Integrator Rules, Formatter, and Messaging 4.1.1 for ISO 15022 messages, you must use a e-Biz Integrator Rules, Formatter, and Messaging version dated 08/29/00 or later. To verify the version compatibility of your current e-Biz Integrator Rules, Formatter, and Messaging installation, check with Financial Fusion technical support. Please refer to your documentation for compatibility issues regarding the use of older platforms with newer versions of OSs and DBMSs. The TradeForce for SWIFT EAI solution will support all previous versions of platforms to MQSI v 1.1 e-Biz Intergrator 4.11, 2.1* & 3.x*. For User Exit modification support for MQSI v2.01 and v2.02 as well as e-Biz Integrator v3.2, v3.2i.x, v3.3x and v3.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 using GNUmake. Edit the file ./obj/Makefile adding the paths of your components (Rules and Formatter, compiler, etc.). Run make from the ./obj directory.
2 SWIFT Format Libraries
Product Documentation Set

This section describes the documentation available for SWIFT Format Libraries.
Cross-Platform Documentation
The SWIFT Solution documentation set includes
SWIFT Format Libraries Installation Guide TradeForce for SWIFT - EAI Adapter Installation and
Administration Guide
Related Documentation
Refer to the following documents for more detail about the use of e-Biz Integrator, e-Biz Integrator Rules, Formatter, and Messaging, WebSphere MQ Integrator, and IBM WebSphere MQ:
e-Biz Integrator
The e-Biz Integrator documentation set includes
Getting Started describes the e-Biz Integrator

components and how the components can work together in your e-commerce environment.
Installation and Configuration Guide details the

installation and initial implementation of e-Biz Integrator and its applications. User Guide helps users understand and apply the program through its graphical user interfaces (GUIs). System Management is intended for system administrators and database administrators who work with e-Biz Integrator on a day-to-day basis.
Application Development Guide assists programmers in

writing applications that use e-Biz Integrator APIs. Programming References are intended for users who build and maintain the links between e-Biz Integrator and other applications. The following volumes are included: Programming Reference for e-Biz Integrator Formatter APIs is a reference to e-Biz Integrator Formatter APIs for those who build and maintain the links between e-Biz Integrator and other applications. Programming Reference for e-Biz Integrator Rules, Formatter, and Messaging APIs is a reference to eBiz Integrator Rules, Formatter, and Messaging APIs for those who build and maintain the links between eBiz Integrator and other applications.
e-Biz Integrator Rules, Formatter, and Messaging

This set of documentation includes the following:
User Guide helps users understand and apply the program

through its graphical user interfaces (GUIs). Programming References are intended for those who must build and maintain the links between e-Biz Integrator Rules, Formatter, and Messaging and other applications. This document comes in three volumes.
Programming Reference for High-Level Messaging and Queuing is a reference to high-level and Messaging and Queuing APIs for those who must write applications to exchange messages. Programming Reference for e-Biz Integrator Formatter is a reference to Formatter APIs for those who must write applications to translate messages from one format to another. Programming Reference for e-Biz Integrator Rules, Formatter, and Messaging is a reference to Rules APIs for those who must write applications to perform actions based on message contents.
Installation Guide provides the procedure to install and

implement e-Biz Integrator Rules, Formatter, and Messaging and its corresponding applications. System Management Guide is for SAs and DBAs who work with e-Biz Integrator Rules, Formatter, and Messaging on a day-to-day basis.
WebSphere MQ Integrator
Installation and Configuration Guide helps end users

and engineers install and configure WebSphere MQ Integrator.
Users Guide helps WebSphere MQ Integrator users

understand and apply the program through its graphical user interfaces (GUIs). Programming References are intended for users who build and maintain the links between WebSphere MQ Integrator and other applications. These documents include: Programming Reference for e-Biz Integrator Formatter is a reference to Formatter APIs for those who write applications to translate messages from one format to another. Programming Reference for e-Biz Integrator Rules, Formatter, and Messaging is a reference to Rules APIs for those who write applications to perform actions based on message contents. Application Development Guide assists programmers in writing applications that use APIs associated with eBiz Integrator Rules, Formatter, and Messaging. System Management Guide is for system administrators and database administrators who work with WebSphere MQ Integrator on a day-to-day basis.
IBM WebSphere MQ
WebSphere MQ An Introduction to Messaging and

Queuing WebSphere MQ Planning Guide
WebSphere MQ Command Reference WebSphere MQ Clients WebSphere MQ Application Programming Reference
WebSphere MQ Application Programming Reference Summary WebSphere MQ Application Programming Guide WebSphere MQ Distributed Queuing Guide
Product Support and Education

For more information on Support Services, education, and consulting services, refer to the Customer Services Reference Guide.
Chapter 2
INSTALLATION
To install the SWIFT Format Libraries correctly, you must complete the following procedures, as described in the these sections:
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 or WebSphere MQ Integrator) training class.
Chapter 2: Installation
Creating and Configuring the Database

If you did not create and configure a database connection while installing your New Era messaging software, use your DBMS tools to create a database for format data. Create a sqlsvses.cfg or nnsyreg.dat file that contains the correct information for your database. Use the sqlsvses.cfg or nnsyreg.dat file to connect to the proper database. 1. Change to the bin directory created during the installation of the New Era messaging software. 2. Create a text file named sqlsvses.cfg or nnsyreg.dat within 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:TESTDATABASE Input:Dodge:user:passwd:TESTDATABASE Output:Dodge:user:passwd:TESTDATABASE rules:Dodge:user:passwd:TESTDATABASE
or
Session.new_format_demo NNOT_SHARED_LIBRARY= dbt26sql65 NNOT_FACTORY_FUNCTION= NNSesMS6Factory NN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuser NN_SES_PASSWORD= NNSYpass NN_SES_DB_NAME= SWIFT1 Session.nnfie NNOT_SHARED_LIBRARY= dbt26sql65 NNOT_FACTORY_FUNCTION= NNSesMS6Factory NN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuser NN_SES_PASSWORD= NNSYpass NN_SES_DB_NAME= SWIFT1
Extracting Installation Files
Session.nnrie NNOT_SHARED_LIBRARY= dbt26sql65 NNOT_FACTORY_FUNCTION= NNSesMS6Factory NN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuser NN_SES_PASSWORD= NNSYpass NN_SES_DB_NAME= SWIFT1 Session.rules NNOT_SHARED_LIBRARY= dbt26sql65 NNOT_FACTORY_FUNCTION= NNSesMS6Factory NN_SES_SERVER= SWIFT1 NN_SES_USER_ID= NNSYuser NN_SES_PASSWORD= NNSYpass NN_SES_DB_NAME= SWIFT1
NOTE: Oracle does not require a database name.

The SWIFT Format Libraries package includes two installation CDs. One CD contains user exits and documentation and the other CDs contain the purchased format libraries, including the preformats. The installation CDs contain the files described in the following table.
Documentation and User Exit Directory Structure

Directory ../Documentation ../User-Exits /Aix /include /lib /obj /project /src /Hp /include /lib /obj /project /src /S390 /include /lib /obj /project /src /SunOS /include /lib /obj /project /src /WinNT /include /lib /obj /project /src commonref.txt ReadMe.txt User-Exit files for use with AIX. Contents pdf files relevant to the product
User-Exit files for use with HP/UX.
User-Exit files for use with OS/390.
User-Exit files for use with Solaris.
User-Exit files for use with Windows.
Example commonref.txt configuration file. User-Exits ReadMe Word document.
Pre-Formats Directory Structure

Directory ../Pre-Formats /Financial-Fusion_Pre-Formats SW500_NNRules.exp SW500_PFFormats.exp /MQSA_Pre-Formats SW500_NNRules_MQSA.exp SW500_PFFormats_MQSA.exp ReadMePreFormats5.0.doc Pre-Format format and rule files for use with e-Biz Integrator. Pre-Format format and rule files for use with MQSA. Pre-Format Readme Word document. Contents
Library Directory Structure

All messages are divided into three subdirectories:
CAclient application messages FROMmessages from SWIFT TOmessages to SWIFT

Within each subdirectory is a choice of seven different configuration versions. New users will choose SW500. The others are for upgrading purposes. Within each configuration directory are two subdirectories:
Directory .../all/ .../individual/ Contents All format libraries included in one nnfie export file for a specific category. This directory contains the MT### files that in turn contain the nnfie files.
To extract files 1. Create an installation directory (for example SWIFTPP) in the <integration server>/bin directory in which the sqlsvses.cfg file resides. 2. Move to that directory. 3. Copy the appropriate directories (listed in the table above) from the CDs to the installation directory.
Setting the PATH Variable

The userexit.cpp is included in the SWIFT Format Libraries installation to build the libraries needed for SWIFT user exits. Set your environment variables to ensure that the user exit library built off of userexit.cpp is listed prior to the lib directory created during the e-Biz Integrator, e-Biz Integrator Rules, Formatter, and Messaging, or MQSI installation. If you do not set the path correctly, e-Biz Integrator Formatter will use the default user exits rather than the SWIFT-specific user exit. NT Ensure that nnuserexit.lib is listed prior to <integration server>\User-Exits\lib in the PATH environment variable. Solaris Ensure that libnnuserexit.shlib is listed prior to <integration server>/User-Exits/lib in the LD_LIBRARY_PATH variable. AIX Ensure that libnnuserexit.shlib is listed prior to <integration server>/User-Exits/lib in the LIBPATH variable. 12 SWIFT Format Libraries
Importing Formats
Importing Formats
You can import all components of a given format by using the NNFie import/export utility. Before you begin importing components, you must create the target database. It is best to import the formats into an empty database. However, you can import formats into a database containing nonconflicting data. For example, if the database currently contains Securities, Settlement, and Reconciliation formats, you can import Corporate Actions formats with no trouble. You can also import formats into a database currently containing the same format, if the existing format name is versioned. See the System Management guide for your messaging software for more information on importing formats. NOTE: If importing components into a case-insensitive database, NNFie fails during import if a conflict arises between two components named the same with only case differences.
NOTE: Do not modify the SWIFT formats. The formats are defined for the purpose of communicating with SWIFT. If modified, this functionality is lost. The shipped formats are fully supported by Financial Fusion, Inc. Custom format modifications are not supported.
Chapter 3
PRODUCT DESCRIPTION
The SWIFT Format Libraries are a part of TradeForce for SWIFT - EAI, including:
SWIFT network access SWIFT-approved gateway (SWIFTAlliance Access or

ST400) 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 attaining the goal of an enterprise system that is fully integrated with SWIFT 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-level component of the TradeForce for SWIFT - EAI. This solution facilitates data conversion and message enrichment between the SWIFT network and legacy or third-party systems. The entire solution consists of seven components, as follows:
Queues
The components communicate with each other using queues. The queues can be WebSphere MQ queues in the context of MQSI, EMQ queues in the context of e-Biz Integrator Rules, Formatter, and Messaging, or transport queues in the context of e-Biz Integrator. The queues must be configured as described for each component below. TradeForce for SWIFT - EAI Adapter This optional component mediates between the SWIFT network and queues. On the network side, the adapter uses an API called CAS, which SWIFT developed, to communicate with SWIFT Alliance, which communicates with the SWIFT network. On the queue side, any of the queue types mentioned above can be used. This component is sold separately and documented separately. Its configuration requirements are extensive, involving a database, queues, configuration files, and settings in SWIFT Alliance; refer to the separate documentation for details.
TradeForce for SWIFT - EAI Components
Preformats
The SW410 Pre-format pass is a preliminary pass through the e-Biz Integrator Rules and e-Biz Integrator Formatter to enable message routing and more efficient parsing and reformatting. These preformats are compatible with the SW300 version and earlier of the SWIFT Format Libraries. If you use any other version of the Format library, such as SW410_ENDSEQ_OLD_CREDIT_DEBIT_PARSE, you must use the SWIFTMsgProcessor.
e-Biz Integrator Rules

The Rules component is a message switch that can be used to accept messages, route them through the appropriate formats and then to the appropriate destination based on business rules. Messages can arrive from multiple sources and be routed to multiple destinations, with multiple transformations, based on the value of any field or group of fields in a message. The customer must write business-specific rules to drive the SWIFT-interaction process. The Rules engine can read and write to and from multiple queues. Setting up the queues is one part of the required configuration effort. Rules configuration is also required and can be done through the e-Biz Integrator Rules GUI. e-Biz Integrator Formatter The e-Biz Integrator Formatter component is invoked by Rules to parse messages and transform them from one record format to another. The format libraries are written in the language understood by e-Biz Integrator Formatter. In addition to the functionality already provided by the libraries, the customer must write transformation formats that will mediate between our internal format (FFISWIFT) and the customer's required back-office formats. Those formats can be developed inside the e-Biz Integrator Formatter GUI. Format development constitutes the configuration needed by e-Biz Integrator Formatter.
User Exits
User exits constitute a code module that is invoked by eBiz Integrator Rules at certain points, under customer control, to do complex calculations or enrichments of messages. This component is supplied as a shared library (DLL) that consists of compiled code. Source code is provided for the user exits, which allows customers to customize the user exits. The user exits are included with the format libraries, so they are covered in this manual. User exit configuration consists of creating a configuration file (required only for certain exits). Format Libraries This component is the major topic of this manual. The supported SWIFT message types are separated into libraries. For each SWIFT message type, there is an associated group of formats and subcomponents. These components must be loaded into e-Biz Integrator Formatter. The e-Biz Integrator Formatter, under the control of e-Biz Integrator Rules, uses these items to parse SWIFT messages, transform the messages into an intermediate code into an intermediate format called FFISWIFT, and allow customers to convert from FFISWIFT 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 backoffice formats to FFISWIFT, and then to construct valid SWIFT messages from the FFISWIFT. There is no configuration required for the format libraries.
SWIFT Format Libraries

The SWIFT Format Libraries comprise several message types, or formats. A complete SWIFT message format is a compound format built in a hierarchical fashion. The SWIFT format contains subordinate components, which can be either a compound or flat format, corresponding to the original SWIFT message layout. Refer to the SWIFT documentation for description of the SWIFT message layouts. For each message type in the SWIFT libraries, Financial Fusion has created a set of formats to translate data to and from the SWIFT network using a simpler structure called FFISWIFT. FFISWIFT contains all possible subfields in a message and protects the customer application from dealing with 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 Description
Each individual pass is defined as follows:
PF: the PreFormats insert for e-Biz Integrator Formatter

performance is a : at the beginning of the last line of the SWIFT message
FROM (SWIFT) parses data from the SWIFT network

and reformats it to FFISWIFT. CA is the Customer Application pass. It is composed of two open ended formats. CA_IC### is an input format that parses FFISWIFT and is ready for mapping to an output format that you create to match your application. CA_SwOC### is an output format that reformats your application input format to FFISWIFT. TO (SWIFT) parses and reformats FFISWIFT back into a SWIFT standard format for transmission to the SWIFT network. For the purpose of reading the following naming conventions chart, terms used for the Format Type in the chart are defined as follows:
Input: An input format parses the data. Output: An output format reformats data from its input
format to the desired format. Compound: The fact that it is a compound type reflects that this format is comprised of several subcomponents. These subcomponents are visible in the e-Biz Integrator Formatter GUI.
Format Library Naming Conventions for Versions 4.x to 5.0

Pass Direction Format Name Format Type Input Compound Output Compound Input Compound SWIFT Message Type ### ### ###
from from from
From SWIFT From SWIFT From SWIFT
SW500_SwIC### SW500_SwOC100 CA500_IC100 This is a message that has been parsed and reformatted into FFISWIFT by the SwIC and SwOC formats. This format parses FFISWIFT. This format is mapped to a format created by the customer to match the existing application. CA500_SwOC100 This format reformats the customer application format into the FFISWIFT to send back through the IC/OC formats and on to the SWIFT Network. SW500_IC100 This format parses a FFISWIFT message that is being sent from the customer application TO the SWIFT network. SW500_OC100 This format reformats the message into FFISWIFT to send to the SWIFT Network.
to
To SWIFT
Output Compound
###
to
To SWIFT
Input Compound
###
to
To SWIFT
Output Compound
###
Formats
You can view the SWIFT Formats in the e-Biz Integrator Formatter GUI. Through e-Biz Integrator Formatter, e-Biz Integrator Rules, Formatter, and Messaging translates messages from one format to another, simplifying message exchange between different systems and applications. The e-Biz Integrator Formatter standardizes how message formats are described, eliminating the need to custom-code between applications to translate each others messages. Messages can be converted from any format ascribed to e-Biz Integrator Rules, Formatter, and Messaging to any other format.
FFISWIFT
The FFISWIFT standard is used as an intermediate state, making it easy to format to any custom application. Most FFISWIFT tags have a fixed length of seven characters. Each field is preceded by a tag, and subfields are delimited by 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 and identification 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 the message. SWIFT divides some messages into portions such as Sequence A, Sequence B. This notation is helpful when the same tag is used in different sequences of the same message. SA is used to indicate sequence A, SB is used to indicate sequence B, and so forth.
Subfield index (01)

These numbers index the subfields of SWIFT tags. In the preceding example, the date in YYMMDD format is broken down by FFISWIFT into subfields. Subfield 02 corresponds to MM and so forth.
Customer Pass Formats

The Customer Pass or CA formats are a set of formats to parse and reformat FFISWIFT to your existing application. These formats can be used when sending a message inbound to the SWIFT network or when receiving a message outbound from the SWIFT network. NOTE: Do not directly modify the SWIFT Format components. Components used in the Customer Pass formats are also used by the SWIFT Format Librariess. By changing a single component you risk breaking SWIFT Library Formats that also might be using that format component. If format modifications are necessary, duplicate and uniquely rename all format components using the Financial Fusion-provided formats as templates. Financial Fusion does not support modified formats.
CA500_SwOC### to SWIFT CA500_SwOC### is a set of output formats designed to reformat your data to FFISWIFT. To use this set of formats, you must use SWIFT Library field names in the input format definition you create. To generate the FFISWIFT representation of MT100 from your data 1. Create a format that describes your data, using SWIFT Library field names. For more information on creating formats and parsing messages in e-Biz Integrator Formatter, see the User Guide for WebSphere MQ Integrator, e-Biz Integrator, or e-Biz Integrator Rules, Formatter, and Messaging. 2. Map this format to CA500_SwOC100, provided with the SWIFT Format Libraries. CA500_SwOC### from SWIFT CA500_SwOC### is a set of input formats designed to parse FFISWIFT formatted messages. To use this set of formats 1. Create an output format that describes your data representation. For more information on creating formats and parsing messages in e-Biz Integrator Formatter, see the User Guide for WebSphere MQ Integrator, e-Biz Integrator, or e-Biz Integrator Rules, Formatter, and Messaging. 2. Use CA500_IC100 (input format), provided with the SWIFT Format Libraries to map to the output created in the preceding step.
Blob Formats
The SWIFT Format Libraries package does not include Trade Finance messages, because applications that handle these messages are generally SWIFT-enabled (GEAC Smart Stream, for example). SWIFT-enabled applications can process SWIFT messages in native format, requiring no message formatting or translation. To route these messages without performing unnecessary data manipulation, you can use e-Biz Integrator Rules, which requires only header (blocks 1-3) information to evaluate and route the message. For this reason, SWIFT Format Libraries include two input blob formats that treat block 4, the body of a SWIFT message, as a blob of data, not differentiating between fields. These are provided so eBiz Integrator Rules can rout the message by the header fields alone, ignoring the body fields.
SW500_BLOBIn: use this format for SWIFT inbound

data. For example, use this format to route a message produced by a SWIFT-enabled application that contains data you wish to send to the SWIFT network. SW500_BLOBOut: use this format for SWIFT outbound data. For example, use this format to route a message received from the SWIFT network to a SWIFT-enabled application. NOTE: BLOB formats are available in the System Library.
e-Biz Integrator Rules

The e-Biz Integrator Rules GUI is used to develop rules to manage message destination IDs, receiver locations, expected message formats, and any processes initiated upon message delivery. The dynamic nature of the Rules daemon means that rules can be effective immediately, staged over time, or delayed, depending on how the reload messages are timed, allowing flexibility in rapidly changing environments. Rules can examine the value of any field or group of fields in a message to make its determinations. It can aggregate conditions with Boolean AND and OR operators without architectural limits as to the number or complexity of the expressions. The Rules daemon receives the message from SWIFT or the customer application and determines message routing based on the content of the individual fields in the message. Routing destinations can be applications, other rule-based routers for distributed architectures, the SWIFT network, or other networks and interfaces. The SWIFT interface products (such as SWIFTAlliance Access or ST400) deliver outbound SWIFT messages to an adapter, such as TradeForce for SWIFT - EAI Adapter. The adapter puts the message to a queue and the Rules daemon retrieves the data from the queue. Subscription logic entered into the e-Biz Integrator Rules GUI indicates where the message is to be routed. This process allows multiple applications or departments to subscribe to SWIFT messages and to retrieve those messages via guaranteed delivery queuing mechanisms by e-Biz Integrator Rules, Formatter, and Messaging. UERuleng is a modified version of the Rules broker. It provides User Exit capabilities. It serves the same function as the Rules broker, but also assists in the processing of SWIFT message. 26 SWIFT Format Libraries
User Exits
User Exits are used in e-Biz Integrator Formatter and e-Biz Integrator Rules. When you require custom features made to formats, a user exit can be implemented. A User Exit works by creating custom code and associating it with an output control. This calls the custom code, which refers to the field values in an input format. Some examples are table lookups, system date retrieval, determining input field length, etc.
CommonRef
This exit will create a SWIFT common reference field (SWIFT tag 22C) if one is not supplied. Function name in the source code is:
SndBicRcvBicExchRtToCommonRef
CommonRefAmount
For Message Types 300, 303, 305, 306, 320, 330, 340, 341, 350, 600 and 601, the common reference field is generated from two BICs and an amount. e-Biz Integrator Formatter should call this user exit with a single parameter. For example:
300CommonRefAmount(id_string)
The id_string is used by the exit to search the commonref.txt configuration file for the names of the fields that it should use to calculate the common reference. If the message arrives at the e-Biz Integrator Formatter already populated with a common reference, the user exit does not act.
The following message types call the CommonRefAmount user type on the direction to SWIFT: MT300 MT303 MT305 MT306 MT320 MT330 MT340 MT341 MT350 MT360 MT 361 MT362 MT364 MT365 MT600 MT601
The function name in the source code is

CommonRefAmount
CommonRefDate
For Message Types 360, 361, 362, 364 and 365, the common reference field is generated from two BICs and a date. The e-Biz Integrator Formatter should call this user exit 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 the fields that it should use to calculate the common reference. If the message arrives at the e-Biz Integrator Formatter already populated with a common reference, the user exit does not act. The function name in the source code is
CommonRefDate
commonref.txt Configuration File Format

The formats of the commonref.txt configuration file used by both the CommonRefAmount and CommonRefDate user exits are as follows: 1. ID_STRING: This field will be used to match against the user 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 the distribution User-Exits folder. Place your implementation commonref.txt file in the directory which contains your User Exit shared libraries. For example, nnsy/bin.
UE_ISITC_FFISWIFT
This exit is used to create a series of FFISWIFT tagsone for ISITC code word that appears in the input message. The FFISWIFT tags will be the name of the field being formatted with the first 4 characters dropped and followed by the ISITC code word. For example, if a field 35B in sequence B was read into e-Biz Integrator Formatter field FLD_SB35B and it contained an /ASCT/ code word, this exit would add an SB35B/ASCT/| tag followed by the value for this code word followed by a | delimiter. Function name in the source code is:
UE_ISITC_FFISWIFT
REPLACE_DOT
This sample exit can be used to convert a number string that uses a US decimal point to a SWIFT comma decimal indicator. If the string does not contain any decimal point (i.e. it is a whole number) then a comma will be appended to the end. A value of 0 will be converted to 0,00. The function name in the source code is
REPLACE_DOT
SWIFT Preformats
The SW500 preformat pass is a preliminary pass through eBiz Integrator Rules and e-Biz Integrator Formatter to enable message routing and more efficient parsing and reformatting. These preformats are compatible with the SW300 and above version of the SWIFT Format Library. If you are using any other version of the format library (SW220_ENDSEQ_OLD_CREDIT_DEBIT_PARSE, for example), you must use the SWIFTMsgProcessor instead of the preformats. The SWIFT500 preformats require default App_Group of SW500 and a message type of SW500_PF to be set in the .mpf configuration file of EBIZ, MQSI, or at the command prompt on startup if you are using e-Biz Integrator Rules, Formatter, and Messaging. The e-Biz Integrator Rules picks up data from a queue and passes it through the initial format, SW500_PF, which parses the header and passes block 4 as a Blob message. The corresponding output format, SW500_PF_OUT, adds a colon immediately before block 5, the trailer fields. This enrichment facilitates formatting a pass through e-Biz Integrator Formatter.
The e-Biz Integrator Rules determines the message type based on the field SW500_PF_SWhdr_MsgType. The e-Biz Integrator Rules then routes the message through its appropriate SwIC and SwOC formats, which outputs FFISWIFT.
The SWIFT message is routed through the appropriate formats and placed on a queue before being parsed by the Customer Application format (CA500_IC###). This is the default setup, however, this subscription can be altered so the message is not output to a queue until after the Customer Application formats. The default setup also includes a mock target queue of OUTQ. You must modify this to the appropriate queue.
Like the SW500 Format Library, the SW410 preformats are platform independent with one exception. Mainframe users are unable to use the CommonRef and CommonRefAmount user exits that are part of the SWIFT Format Library. These user exits compose a Common Reference field, SWIFT tag 22C. If one is not supplied in the customer application data, mainframe users must supply this field in the TO SWIFT data. The following message types are affected: MT300 MT303 MT305 MT306 MT320 MT330 MT340 MT341 MT350 MT360 MT 361 MT362 MT364 MT365 MT600 MT601
SWIFT Preformats Installation

The 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 = SW500 DefaultMessageType = SW500_PF
3. For e-Biz Integrator Rules, Formatter, and Messaging, set these defaults at the command prompt when starting the Rules engine:
App_Group = SW500 Message Type = SW500_PF
4. Modify the Rules subscription, OPT_TARGET_QUEUE, to output data to a selected queues.
Chapter 4
FORMAT LIBRARY USE

The SWIFT Solution requires that you complete the following 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 queuing application to create the following five queues (names in parentheses 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 Financial Fusion to SWIFT queue. The Rules daemon places the reformatted message on this queue if specified during creation 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 required for further processing.
Mapping Data
To send messages inbound TO SWIFT, start with data extracted from your application non-SWIFT-enabled application. Compare that data to the format for the corresponding message type from the SWIFT Format Libraries SWIFT Format Libraries. When completing this procedure, think of the following:
Which fields should be included in the message to

SWIFT?
Does the flat file contain all mandatory fields and data
required by SWIFT? Does the flat file require enrichment to meet SWIFT requirements? What fields will be included and in what order? Use the e-Biz Integrator Formatter GUI to create an input format with appropriate tags and delimiters that define your message. Once you have created this format, view the corresponding CA500_SwOC### format. use the Map Fields tab to map each field to its counterpart in the format you just created. For more information on mapping fields, see the User Guide.
Testing Formats
NOTE: Do not modify the formats! You can duplicate a format and rename with a unique name, if necessary. Compare the field formats between the two messages.
Application Field Date Monetary Amount Existing Customer Format ddmmyyyy XXXX.XX SWIFT Field SWIFT Format
Date Monetary Amount
yyyymmdd XXXX,XX
Testing Formats
Once you have mapped the output from your application formats to CA_SwOC, you are ready to test it with msgtest. Type msgtest at a command prompt and follow the system prompts. NOTE: Use the msgtest (MQSI and e-Biz Integrator Rules, Formatter, and Messaging) executables found on the standard MQSI/e-Biz Integrator Rules, Formatter, and Messaging CD.
Creating Rules
From SWIFT
1. Using the NNRie utility, load SW500_PFRules.exp file. If you use MQSA, load the SW500_PFRules_MQSA.exp file into the e-Biz Integrator Formatter database. 2. Open the Rules Management Console. The following set of generic rules appears in the e-Biz Integrator Rules GUI. 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 the message type you want to use: a) Change the default settings for putqueue to your specific destination. a) Add an additional reformat that supports your custom format.
To SWIFT
1. In the Rules Management Console, create a subscription as in the following example.
In the example above, the initial INPUT_FORMAT is the format you created in your e-Biz Integrator Formatter 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 each message type that you are using.
Running New Era of Networks Broker

To move messages through e-Biz Integrator Formatter to the SWIFT network and perform the data parsing and manipulation required for SWIFT inbound messages, start the broker. After data manipulation is complete, the broker applies the appropriate rule to the message and routes it accordingly. You have the option to route messages to an output queue for retrieval from TradeForce for SWIFT - EAI Adapter and further message processing. For more information on the TradeForce for SWIFT - EAI Adapter, see the TradeForce for SWIFT - EAI Adapter Installation and Administration Guide.
Chapter 5
UPGRADE INFORMATION
This chapter includes the information necessary to upgrade from TradeForce SWIFT for EAI version 4.10 to version 5.0. The information covered in this chapter includes the following:
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. For

details, see SW500 Prefixes on page 40. An upgrade of SWIFT formats to the new SWIFT 2002 standards. For details, see SWIFT 2002 Message Change Information on page 40.
Chapter 5: Upgrade Information
SW500 Prefixes
All the components in the new library, except field names, are prefixed by SW500.
SWIFT 2002 Message Change Information

The Changed by SWIFT for 2002 column in the table below indicates that SWIFT has made a change in the message for the 2002 standards upgrade. Many of the changes, such as new qualifiers, do not require the formats to 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 will continue to work normally for the SWIFT 2002 upgrade.
Message Number 100 101 102 102P 103 103P MT104 MT107 MT110 MT111 MT112 MT190 MT191 MT192 Supported in Version 5.0 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Changed by SWIFT for 2002 N Y Y Y Y Y Y Y Y N N N N N Format Changes N Y Y Y Y Y Y Y Y N N N N N
Message Number MT195 MT196 MT198 MT199 MT200 MT201 MT202 MT203 MT204 MT205 MT206 MT207 MT210 MT256 MT290 MT291 MT292 MT293 MT295 MT296 MT298 MT299 MT300 MT303 MT304 MT305
Supported in Version 5.0 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Changed by SWIFT for 2002 N N N N N N Y Y Y N N Y N N N N N N N N N N Y Y N N
Format Changes N N N N N N Y N N N N N N N N N N N N N N N Y Y N N
Changed by SWIFT for 2002 N Y-NEW Y-NEW Y N Y N N Y Y Y Y Y Y Y-NEW Y-NEW N N N N N N N N Y N
Format Changes N Y-NEW Y-NEW Y N Y N N Y Y Y Y Y Y Y-NEW Y-NEW N N N N N N N Y Y N
Changed by SWIFT for 2002 N Y N N N Y Y Y N N N N N N N Y-NEW Y-NEW Y Y Y Y Y Y Y Y Y-NEW
Format Changes N N N N N N N N N N N
N N N Y-NEW Y-NEW Y N Y Y N Y N N Y-NEW
Supported in Version 5.0 N-DELETED Y Y Y Y Y Y Y N-DELETED N-DELETED N-DELETED N-DELETED Y Y Y Y Y N-DELETED N-DELETED N-DELETED N-DELETED N-DELETED Y Y Y Y
Changed by SWIFT for 2002 N Y Y Y Y Y Y Y-NEW
Format Changes N Y Y Y N N Y Y-NEW
N N N Y Y
N N N Y Y
Y Y Y N
Y Y Y N
Supported in Version 5.0 N-DELETED Y Y Y Y Y Y Y Y Y Y N-DELETED N-DELETED N-DELETED N-DELETED N-DELETED N-DELETED N-DELETED N-DELETED Y Y N-DELETED N-DELETED N-DELETED N-DELETED Y
Changed by SWIFT for 2002
Format Changes
Y Y Y Y Y Y Y Y Y N
Y Y Y Y Y Y Y Y Y N
N N
N N
Message Number MT565 MT566 MT567 MT568 MT569 MT570 MT571 MT572 MT573 MT574I MT574W MT575 MT576 MT577 MT578 MT579 MT580 MT581 MT582 MT583 MT584 MT586 MT587 MT588 MT589 MT590
Supported in Version 5.0 Y Y Y Y Y N-DELETED N-DELETED N-DELETED N-DELETED Y Y Y Y Y Y Y N-DELETED Y Y N-DELETED Y Y Y Y Y Y
Changed by SWIFT for 2002 Y Y Y N N
Format Changes Y Y Y N N
Y-NEW Y-NEW Y Y N Y N
Y-NEW Y-NEW Y Y N Y N
N N
N N
Y Y N N Y N
Y Y N N Y N
Changed by SWIFT for 2002 N N N N N N N N N N N N N N Y Y Y Y N N N N N N N N
Format Changes N N N N N N N N N N N N N N N N N N N N N N N N N N
Changed by SWIFT for 2002 N N N N N N N N N N N N N N N N N N N N N N N N N N
Format Changes N N N N N N N N N N N N N N N N N N N N N N N N N N
Changed by SWIFT for 2002 N N N N Y N N Y Y N Y Y N Y N N N N N N N N N N N N
Format Changes N N N N Y N N Y Y N Y Y N Y N N N N N N N N N N N N
Message Number MT012 MT015 MT019 MT082 MT083 MT094 ACK/NAK
Supported in Version 5.0 Y Y Y Y Y Y Y
Changed by SWIFT for 2002 N N N N N N N
Format Changes N N N N N N N
SWIFT Library Migration

Software Requirements
This upgrade, whether full or partial, requires a preinstallation of e-Biz Integrator Rules, Formatter version 3.2 or later, and Messaging Integration software. Note: The use of the SWIFT 2002 Format Library with earlier versions of the e-Biz Integrator is not supported and may produce errors.
Full Upgrade
This section describes the typical upgrade to the SWIFT Format Libraries 5.0 to comply with the Message Standard 15022.
New Era of Networks SW IFT SOLUTION V. 5.0.
New Era of Netw orks Rules, Form atter, and M essaging
Preform ats CAS

SW IFT SW IFT Alliance
New Era of Networks Adapter for SW IFT New Era of Networks Access
SW5 00 PP Input SW 5 00 PP_O UT O utput SW 500 Sw IC Input
SW IFT Form at Library

SW 500 Sw O C Output
FFISW IFT
CA500 _IC Input
Customer Application Formats O utput
Custom er App
SW 5 00 OC O utput
SW 5 00 IC Input
FFISW IFT
CA500_ Sw OC O utput
C ustom er Application Formats Input
Database
Database Database Queuing System
Partial Upgrade
If you want to run the e-Biz Integrator Rules, Formatter, and Messaging integration software in conjunction with the SWIFT Format Libraries, to keep an existing 7775 Message Standard implementation for inbound SWIFT messages, and to send 15022 messages out to the SWIFT network, you need to make the following adjustments. To complete a partial upgrade 1. Using NNFie, load the 2002 messages (SW500) into the message database which already contains the 2001 messages. 2. Upgrade your e-Biz Integrator Formatter database to 3.2 or later. These releases include: - e-Biz Integrator 3.x - WebSphere MQ Integrator 2.x. 3. Update all rules in your e-Biz Integrator Rules database with new message types. 4. Duplicate the Standard Library Format CA500_ICXXX. 5. Rename your formats using your own company naming conventions. 6. Replace the existing Customer Application Input format with the CA500_ICXXX Standard Input format. The Customer Application Input format automatically maps to the CA500_SwOCXXX format. 7. Using your back office application, generate the data needed for the 2002 messages to be sent to the SWIFT network. Avoid customization by generating input data using a || delimiter. For example:
3455||gtft667||99i9i9weu||
NOTE: If your back-office application cannot generate the necessary data, use a data enrichment scheme during the CA500_SwOCXXX parse with the use of user exits. The following diagram illustrates such a partial implementation:
N e w E ra o f N etw o rk s S 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 .
N e w E r a o f N e t w o r k s R u le s , F o rm a tt e r, a n d M e s s a g in g S W IF T F o r m a t L ib ra ry
S W 2 20 S w IC In p u t SW 220 SwOC O u tp u t SW 220 S w IC -2 In p u t SW 220 S w O C -2 O u tp u t
CAS
S W IF T
S W IF T A ll i a n c e
N e w E ra o f N etw o rk s A d a p te r fo r S W IF T N e w E ra o f N etw o rk s A ccess
S W IF T P re P ro c e s s o r
I F F S W IF T
CA 220 In p u t
C u s to m e r A p p li c a t io n F o r m a ts O u tp u t C u sto m e r App
SW 500 OC O utp u t
SW 500 IC In p u t
IF F S W IF T
C A 50 0 _ S w O C O u tp ut
C A 5 0 0 _ IC In p u t
D a t a E n r ic h m e n t v i a U s e r E x it D a ta b a s e D a ta b a s e D a ta b a s e D a ta b a s e
OR/ AND
U p d a te C u s to m e r In p u t A p p lic a tio n w it h d a t a fo r N e w M essage S ta n d a rd
Q u e u in g S y s te m
NOTE: For further assistance with a Partial Upgrade please call Financial Fusion Technical Support.
Appendix A
SUPPORT FOR PREVIOUS FFISWIFT VERSIONS

Multiple Library Versions for Compatibility
Where messages have not been changed by SWIFT, Financial Fusion is providing versions of the formats that will use or produce various versions of FFISWIFT that have been released in the past in order to provide as much backward compatibility as possible. The following SWIFT library version is included in each CD:
SW500
The following SWIFT library versions will be provided as needed:
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 from SWIFT versions 2.x. These versions allow you to accept SWIFT Standard 2002 messages while maintaining the current format of FFISWIFT. The only required changes to the CA formats are those which connect your application and follow the SWIFT 2002 standards. If you choose an upgrade version, it allows messages not changed in the SWIFT 2002 standards to require no changes to the FFISWIFT or Customer Application formats. The appropriate version of the library can be determined by examining the format of the existing FFISWIFT and matching it with its appropriate versions. Users should keep in mind that in choosing an upgrade library, they will not be taking advantage of the finer granularity parse that SW500 offers over the SWIFT 2.x version.
SW500
SW500 is the standard library. It has been upgraded to include the SWIFT 2002 standards changes and does not require the pre-processor however it does require the preformats.
SW450_WO_COMPLETE_HEADER
This is the same as the standard SW500 library with the exception of the header. This version of the library uses the less granular parse on the header that was used in previous releases. For specific field information, see Appendix B: FFISWIFT Header.
Multiple Library Versions for Compatibility
SW500_ENDSEQ_OLD_CREDIT_DEBIT
This is the SW500 library built to be backward compatible with versions of FFISWIFT in release SW2xx (excluding the messages that have a tag 61). This library is intended for users who would like to maintain as much compatibility with release SW2xx as possible. This version outputs FFISWIFT that contains the delimiter ENDSEQ to mark the end of repeating sequences. In addition, it parses in the party fields as one field instead of breaking the credit debit field into its own field. This version uses the less granular approach to parsing the header. For more information, see Appendix B: FFISWIFT Header.
SW500_ENDSEQ
This includes the standard library with two changes. The FFISWIFT will include an ENDSEQ after each repeating sequence. This library uses the less granular approach to parsing the header. For more information, see Appendix B: FFISWIFT Header. SW500_OLD_CREDIT_DEBIT This is the SW500 library built to be backward compatible with older versions of the party fields (5xA, 5xD, 8xA, and 8xD) parse. However, this version does not expect any type of ENDSEQ to mark the end of repeating sequences. This version uses the less granular approach to parsing the header. For more information, see Appendix B: FFISWIFT Header.
Appendix B
THE FFISWIFT HEADER

The FFISWIFT header has two definitions depending on the directionto SWIFT or from SWIFT. SWIFT blocks 1 and 2 are positional. The format is data, terminated by ||.
Normal FFISWIFT (FROM SWIFT)

The from SWIFT header:
{1:F01VNDZBET2BXXX0001000002}{2:O5021200910103BANKBEBBAXXX 22221234569101031201N}{3:{113:xxxx}{108:abcdefgh12345678}}
The from SWIFT FFISWIFT header:

F||01||VNDZBET2BXXX||0001||000002||O||502||1200||910103||BANKBE BBAXXX||2222||123456||910103||1201||N||113SA01xxxx||108SA01abc defgh12345678||
Appendix B: The FFISWIFT Header
Table 1: SWIFT Block 1

Position 1 2 3 Man/ Opt Man Man Man FFISWIFT Field Name SWhdr_AppID SWhdr_APDU Receiver_BIC_Code Receiver_LT Receiver_Branch_Code SWhdr_SessNbr Sequence Number SWIFT Field Name Application Identifier Servive Identifier LT Address Data F 01 VNDZBET 2BXXX 0001 000002
4 5
Man Man
Session Number Sequence Number (ISN or OSN)

Position 6 7 8 9 10 Man/ Opt Man Man Man Man Man FFISWIFT Field Name SWhdr_I/Oind SWhdr_MsgType SWhdrInput_Time SWhdrInput_Date Sender_BIC_Code Sender_LT Sender_Branch_Code SWhdrInp_Session_Nu m SWhdrInp_Seq_Num SWhdrOutput_Date SWhdrOutput_Time SWhdrMsg_Priority SWIFT Field Name Input/Output Identifier Message Type Input Time Date from MIR BIC from MID Data O 502 1200 910103 BANKBEB BAXXX 2222 123456 910103 1201 N
11 12 13 14 15
Man Man Man Man Man
Session Number from MIR Sequence Number from MIR Output Date Output Time Message Priority
FFISWIFT with Full Header (FROM SWIFT)

Position NA NA Man/ Opt Opt Opt FFISWIFT Field Name BankingPriority MessageUserReference SWIFT Field Name Banking Priority Data Xxxx
Message User Reference Abcdefgh12 (MUR) 345678
FFISWIFT with Full Header (FROM SWIFT)

The from SWIFT header:
{1:F01VNDZBET2BXXX0001000002}{2:O5021200910103BANKBEBBAXXX 22221234569101031201N}{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||BANKBE BBAXXX||2222||123456||910103||1201||N||103SA01LCN||113SA01xxxx ||108SA01abcdefgh12345678||119SA01REMIT||115SA01PaymentReleas eInfo ||

Position 1 2 3 Man/ Opt Man Man Man FFISWIFT Field Name SWhdr_AppID SWhdr_APDU Receiver_BIC_Code Receiver_LT Receiver_Branch_Code SWhdr_SessNbr Sequence Number SWIFT Field Name Application Identifier Servive Identifier LT Address Data F 01 VNDZBET 2BXXX 0001 000002
4 5
Man Man
Session Number Sequence Number (ISN or OSN)

Position 6 7 8 9 10 Man/ Opt Man Man Man Man Man FFISWIFT Field Name SWhdr_I/Oind SWhdr_MsgType SWhdrInput_Time SWhdrInput_Date Sender_BIC_Code Sender_LT Sender_Branch_Code SWhdrInp_Session_Nu m SWhdrInp_Seq_Num SWhdrOutput_Date SWhdrOutput_Time SWhdrMsg_Priority SWIFT Field Name Input/Output Identifier Message Type Input Time Date from MIR BIC from MID Data O 502 1200 910103 BANKBEB BAXXX 2222 123456 910103 1201 N
11 12 13 14 15
Man Man Man Man Man
Session Number from MIR Sequence Number from MIR Output Date Output Time Message Priority

Position NA NA NA NA NA Man/ Opt Opt Opt Opt Opt Opt FFISWIFT Field Name ServiceID BankingPriority MessageUserReference ValidationFlag AddresseeInfo SWIFT Field Name service-code Banking Priority Message User Reference (MUR) Validation flag Payment-releaseinformation-receiver Data LCN Xxxx Abcdefgh12 345678 REMIT PaymentRel easeInfo
Normal FFISWIFT (TO SWIFT)
Normal FFISWIFT (TO SWIFT)

The to SWIFT header:
{1:F01MLCOUS33GXXX0000000000}{2:O502BANKPB33GXXXN2020}{3:{1 13:xxxx}{108:abcdefgh12345678}}
The to SWIFT FFISWIFT header:

01||MLCOUS33G||XXX||502||BANKPB33G||XXX||N||2||020||xxxx||abcdef gh12345678||

Position 1 2 3 Man/ Opt Man Man Man FFISWIFT Field Name SWhdr_APDU SWhdr_SourceBank SWhdr_SourceBranch SWIFT Field Name Application Identifier Service Identifier LT Address Data 01 MLCOUS3 3G XXX

Position 4 5 6 7 8 9 Man/ Opt Man Man Man Man Man Man FFISWIFT Field Name SWhdr_MsgType SWhdr_DestBank SWhdr_DestBrach SWhdrMsg_Priority SWhdr_Delivery SWhdr_Obsol SWIFT Field Name Message Type Destination Address Destination Address Message Priority Delivery Monitoring Obsolescence Period Data 502 BANKPB33 G XXX N 2 020

Position 10 11 Man/ Opt Opt Opt FFISWIFT Field Name SWhrd_BankingPriority SWhdr_MUR SWIFT Field Name Banking Priority Message User Reference (MUR) Data 113SA01xx xx 108SA01ab cdefgh1234 5678
FFISWIFT with Full Header (TO SWIFT)

The to SWIFT header:
{1:F01MLCOUS33GXXX0000000000}{2:O502BANKPB33GXXXN2020}{3:{1 03:}{113:xxxx}{108:abcdefgh12345678}{119:REMIT} {115:PaymentReleaseInfo}}
The to SWIFT FFISWIFT header:

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

Position 1 2 3 Man/ Opt Man Man Man FFISWIFT Field Name SWhdr_APDU SWhdr_SourceBank SWhdr_SourceBranch SWIFT Field Name Application Identifier Service Identifier LT Address Data 01 MLCOUS33 G XXX
FFISWIFT with Full Header (TO SWIFT)

Position 4 5 6 7 8 9 Man/ Opt Man Man Man Man Man Man FFISWIFT Field Name SWhdr_MsgType SWhdr_DestBank SWhdr_DestBrach SWhdrMsg_Priority SWhdr_Delivery SWhdr_Obsol SWIFT Field Name Message Type Destination Address Destination Address Message Priority Delivery Monitoring Message Obsolescence Data 502 BANKPB33 G XXX N 2 020

Position 10 11 12 13 14 Man/ Opt Opt Opt Opt Opt Opt FFISWIFT Field Name SWhrd_ServiceID SWhrd_BankingPriority SWhdr_MUR SWhrd_ValidationFlag SWhrd_AddresseeInfo SWIFT Field Name Service Identifier Banking Priority Message User Reference (MUR) Validation Flag Addressee Information Data LCN xxxx abcdefgh12 345678 REMIT PaymentRel easeInfo
Appendix C
THE
FFISWIFT TRAILER
The FFISWIFT trailer has definitions depending on the directionto 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 formatted SWIFT trailer without the enclosing block 5 start of block and 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 FOR UPGRADING PRE-410 VERSIONS

Modifying Rule Expressions
The SW500 library represents nearly a complete rewrite of the SWIFT formats, and as part of the rewrite all the field names have changed. This is for several reasons. First, the SW211, SW212 and SW220 libraries had header field names prefixed by the library version number. These version numbers have been removed. Second, the old names were 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 the library, this rule will need to be changed. (See Mapping of Header Field Names below for the field name mappings.) From the mapping, SW211_SWhdr_MsgType should be replaced with SWhdr_MsgType. If any fields from the body of the message are referenced in a rule, then it is necessary to find the equivalent field(s) in the SW500 message. See example 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 two passes to one pass. The first reformat should be changed from SW211_SwIC522 to SW500_SwIC522 and SW211_SwOC522 to SW500_SwOC522 (see below). The second reformat should be completely removed.
Modifying Rule Subscriptions
In the case above, the first putqueue sets the OPT_MSG_TYPE to SW211_SwIC522. The function of the put should be examined to determine if the OPT_MSG_TYPE should be set to SW500_SwIC522.
Mapping of Header Field Names

From SWIFT
Version 2.2
SW220 Field Names SW220_BasicHeaderBlock SW220_SWhdr_AppID SW220_SWhdr_APDU SW220_SWhdr_LT_Addr(REC) SW300 and SW410 Field Names BasicHeaderBlock SWhdr_AppID SWhdr_APDU Receiver_ BIC_Code Receiver_LT Receiver_Branch_Code SWhdr__SessNbr SequenceNumber SWhdr_I/Oind SWhdr_MsgType SWhdr_Input_Time SWhdr_Input_Date Sender_BIC_Code Sender_LT Sender_Branch_Code SWhdrInp_Session_Num SWhdrInp_Seq_Num SWhdrOutput_Date SWhdrOutput_Time SWhdrMsg_Priority BankingPriority MessageUserReference
SW220_SWhdr_SessNbr SW220_Sequence Number SW220_SWhdr_I/Oind SW220_SWhdr_MsgType SW220_SWhdr_Input_Time SW220_SWhdr_Input_Date SW220_SWhdr__LTAddress(SNDR)
SW220_SWhdrInp_Session_Num SW220_SWhdrInp_Seq_Num SW220_SWhdrOutput_Date SW220_SWhdrOutput_Time SW220_SWhdrMsg_Priority SW220_UserHeaderBlock1 SW220_UserHeaderBlock2
Mapping of Header Field Names
Version 2.1
SW211 Field Names SW211_BasicHeaderBlock SW211_SWhdr_AppID SW211_SWhdr_APDU SW211_SWhdr_LT_Addr(REC) SW300 and SW410 Field Names BasicHeaderBlock SWhdr_AppID SWhdr_APDU Receiver_ BIC_Code Receiver_LT Receiver_Branch_Code SWhdr__SessNbr SequenceNumber SWhdr_I/Oind SWhdr_MsgType SWhdr_Input_Time SWhdr_Input_Date Sender_BIC_Code Sender_LT Sender_Branch_Code SWhdrInp_Session_Num SWhdrInp_Seq_Num SWhdrOutput_Date SWhdrOutput_Time SWhdrMsg_Priority BankingPriority MessageUserReference
SW211_SWhdr_SessNbr SW211_Sequence Number SW211_SWhdr_I/Oind SW211_SWhdr_MsgType SW211_SWhdr_Input_Time SW211_SWhdr_Input_Date SW211_SWhdr__LTAddress(SNDR)
SW211_SWhdrInp_Session_Num SW211_SWhdrInp_Seq_Num SW211_SWhdrOutput_Date SW211_SWhdrOutput_Time SW211_SWhdrMsg_Priority SW211_UserHeaderBlock1 SW211_UserHeaderBlock2
To SWIFT
Version 2.2
SW220 Field Names SW220_SWhdr_APDU SW220_SWhdr_SourceBank SW220_SWhdr_SourceBranch SW220_SWhdr_MsgType SW220_SWhdr_DestBank SW220_SWhdr_DestBranch SW220_SWhdrMsg_Priority SW220_SWhdr_Delivery SW220_SWhdr_Obsol SW220_SWhdr_BankingPriority SW220_SWdhr_MUR SW300 and SW410 Field Names SWhdr_APDU SWhdr__SourceBank SWhdr__SourceBranch SWhdr_MsgType SWhdr_DestBank SWhdr_DestBranch SWhdrMsg_Priority SWhdr_Delivery SWhdr_Obsol SWhdr_BankingPriority SWhrd_MUR
Version 2.1
SW211 Field Names SW211_SWhdr_APDU SW211_SWhdr_SourceBank SW2110_SWhdr_SourceBranch SW211_SWhdr_MsgType SW211_SWhdr_DestBank SW211_SWhdr_DestBranch SW211_SWhdrMsg_Priority SW211_SWhdr_Delivery SW211_SWhdr_Obsol SW211_SWhdr_BankingPriority SW211_SWdhr_MUR SW300 and SW410 Field Names SWhdr_APDU SWhdr__SourceBank SWhdr__SourceBranch SWhdr_MsgType SWhdr_DestBank SWhdr_DestBranch SWhdrMsg_Priority SWhdr_Delivery SWhdr_Obsol SWhdr_BankingPriority SWhrd_MUR
INDEX
B
blob formats 25
E
e-Biz Integrator Formatter 17 e-Biz Integrator Rules 17, 26 education services 6 extracting installation files 9
C
CA formats 23 CA500_SwOC### 24 chapter summary viii CommonRef 27 commonref.txt 29 CommonRefAmount 27 CommonRefDate 28 components TradeForce for SWIFT - EAI 16 configuration file format 29 conventions, used in this guide ix Customer Pass formats 23
F
FFISWIFT 22 Format Libraries 18 formats blob 25 import 13 message passes 22 naming convention 21 outbound 24 formats, testing 35 formatsCA500_SwOC### 24
D
data parsing, using broker 38 database connection 8 databse, creating and configuring 8 directory structure documentation and User Exit 10 library 11 pre-formats 11 documentation set, overview 3
G
GUI rules 26
H
help, obtaining ix
I
IFT 36 install, processor file structure 9
Index
installation files, extracting 9 installing the SWIFT Format Libraries 9
R
related documentation 3 REPLACE_DOT 30 rules GUI 26 rules, creating from SWIFT 36 rules, creating to SWIFT 37
M
mapping data map 34 messages moving, using broker 38 migration of SWIFT Libraries full upgrade 51 partial upgrade 51 Msgtest 35
S
S.W.I.F.T. Format Libraries configuring database connection 8 creating database connection 8 Sequence indicator 23 sqlsvses.cfg 8 Subfield index 23 support services, more information 6 supported platforms 1 SW500 56 SW500_ENDSEQ 57 SW500_ENDSEQ_OLD_CREDIT_ DEBIT 57 SW500_OLD_CREDIT_DEBIT 57 SW500_WO_COMPLETE_ HEADER 56 SWIFT 2002 message change information 40 SWIFT Format Libraries change details 39 importing formats 13 SWIFT formats, viewing 22 SWIFT preformats, installing 32
N
naming convention 21 Network Broker, running 38 NNFie 13
O
outbound format 24 overview, of this guide vii
P
pass description, about 20 path 12 PATH variable, setting 12 platforms, supported 1 Preformats 17 processor, directory structure 9
Q
queues 16 creating 33
T
TradeForce for SWIFT - EAI components 16 TradeForce for SWIFT - EAI Adapter 16
Index
U
UE_ISITC_FFISWIFT 29 user exits 18, 27 CommonRef 27 CommonRefAmount 27 CommonRefDate 28 REPLACE_DOT 30 UE_ISITC_FFISWIFT 29
V
version compatibility 55
Format Library Installation and Administration Guide 79

Financial Fusion - Trade Force For SWIFT - Version 5

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Financial Fusion - Trade Force For SWIFT - Version 5

Încărcat de

Drepturi de autor:

Formate disponibile

TradeForce for SWIFT - EAI v e r s i o n 5.0

Installation and Administration Guide

ABOUT THIS BOOK

About This Guide

About this Book

About this Book

Conventions Used in This Guide

Menu > Submenu Italics

If You Need Help

Supported Platforms Product Documentation Set Product Support and Education

s/390 Version 2.8

Installation and Administration Guide 1

2 SWIFT Format Libraries

Product Documentation Set

Product Documentation Set

Getting Started describes the e-Biz Integrator

Installation and Configuration Guide details the

Installation and Administration Guide 3

Application Development Guide assists programmers in

e-Biz Integrator Rules, Formatter, and Messaging

User Guide helps users understand and apply the program

4 SWIFT Format Libraries

Product Documentation Set

Installation Guide provides the procedure to install and

Installation and Configuration Guide helps end users

Users Guide helps WebSphere MQ Integrator users

Installation and Administration Guide 5

WebSphere MQ An Introduction to Messaging and

WebSphere MQ Command Reference WebSphere MQ Clients WebSphere MQ Application Programming Reference

Product Support and Education

6 SWIFT Format Libraries

Installation and Administration Guide 7

Creating and Configuring the Database

8 SWIFT Format Libraries

Extracting Installation Files

NOTE: Oracle does not require a database name.

Extracting Installation Files

Installation and Administration Guide 9

Documentation and User Exit Directory Structure

User-Exit files for use with HP/UX.

User-Exit files for use with OS/390.

User-Exit files for use with Solaris.

User-Exit files for use with Windows.

Example commonref.txt configuration file. User-Exits ReadMe Word document.

10 SWIFT Format Libraries

Extracting Installation Files

Pre-Formats Directory Structure

Library Directory Structure

CAclient application messages FROMmessages from SWIFT TOmessages to SWIFT

Installation and Administration Guide 11

Setting the PATH Variable

Installation and Administration Guide 13

SWIFT network access SWIFT-approved gateway (SWIFTAlliance Access or

e-Biz Integrator Formatter e-Biz Integrator Rules

Installation and Administration Guide 15

Chapter 3: Product Description

TradeForce for SWIFT - EAI Components

16 SWIFT Format Libraries

TradeForce for SWIFT - EAI Components

e-Biz Integrator Rules

Installation and Administration Guide 17