Basic Validation Features

The SWIFT OTD Library accomplishes validation operations via Java-based Collaboration Definitions packaged with the library. These Collaboration Definitions have the following validation features provided to enhance their use:

• Message Format Validation Rules (MFVRs): Set of functions that accurately test the semantic validity of a given subset of the SWIFT messages.

• BICDirService (Bank Identifier Code Directory Service) Lookup: A set of methods that provide search and validation functionality for SWIFT”s BIC codes and ISO currency and country codes. The information used to look up and validate is provided by SWIFT.

• BICPlusIBAN Validation: A set of methods that provide search and validation functionality for SWIFT”s BIC and IBAN codes. The SWIFT OTD Library implements the suggested validation rules provided by SWIFT. Please see BICPlusIBAN Directory Technical Specifications from SWIFT for more information.

These validation features share the following use characteristics:

• Each available method and function is fully incorporated into and used by the appropriate SWIFT message OTD.

• You can modify the validation rules for your system if desired. Customize the Collaboration’s validation rules by checking the Collaboration out (from Version Control) and modify the Validation Collaboration code. The sample implementation and instructions are provided in the Validation Collaboration as Java comments.

• Validation methods and functions have no dependencies outside SWIFT data files and the individual OTD.

Installing the OTD library allows eGate and any eWay you use with the library to provide full support for these features. The rest of this section provides a summary of how these features operate with the SWIFT OTD Library.

Validation Components

In addition to components described under Basic Validation Features, the SWIFT OTD Library also contains the following basic components:

• SWIFT OTDs (2001, 2002, 2003, 2005, 2006, 2007, and 2008): OTDs in the SWIFT OTD Library that represent standard SWIFT message types. See Increasing the heap size from the heapSize.bat file for details. The validation features are only available with the 2003, 2005, 2006, 2007, and 2008 OTD libraries.

• MT Funds OTDs: Specialized OTDs that allow you to automate the specialized funds operations. This category contains FIN-based OTDs.

• Validation Collaboration Definitions: Validation eGate components provided for each SWIFT message type. See Validation Collaboration Definitions for details.

• Sample Projects: Sample Projects have been provided as examples of validation implementation. See SWIFT Projects for details.

Validation Methods

The SWIFT OTD Library now provides two additional OTD API methods, validate() and validateMFVR(), that can be invoked by a Collaboration to validate SWIFT 2003, 2005, 2006, 2007 and 2008 OTDs directly in the Collaboration. (see In Collaboration Validation Methods). This is an alternative to using the Validation Collaboration Definitions.

Validation Collaboration Definitions

Validation Collaboration Definitions are provided for many key SWIFT message types. These Collaboration Definitions, when combined with eGate Services, become Java-based Collaborations that verify the syntax of the SWIFT messages.

This verification is done by parsing the data into a structure that conforms to the SWIFT standard specifications. The validation functions use these Collaborations to access specific data that is then verified according the algorithms of the MFVR specifications.

For lists of these Collaboration Definitions, see Message Validation Rules.

Validation Operation

You can combine the library’s validation features in any way desired, to meet your specific needs. The SWIFT OTD Library packages a prebuilt implementation that takes SWIFT messages from a JMS Queue or Topic and validates them individually, then writes the results to a specified JMS Queue or Topic. One set contains valid messages, and the other contains the invalid ones, along with messages indicating the errors generated.

Validation Project examples

The validation Collaboration Definitions are part of the OTD Library and packaged with validation Project examples you can import into eGate.

Basic validation steps

Each validation Collaboration Definition has only the applicable tests for a specific OTD/message type, but they all operate according to the same general format, as follows:

• The Service first tests a message to make sure it is syntactically correct, by parsing it into the OTD.

• If the message fails, the message and its parser error are sent to an error Queue. If the message is valid, all applicable MFVR functions are applied to the message.

• Any and all errors produced from these tests are accumulated, and the combined errors, as well as the message, are written to an error Queue for later processing. As long as no error is fatal, all applicable tests are applied.

• Again any and all errors produced from these tests are accumulated, and the combined errors and message are written to the error Queue for later processing.

• If no errors are found in a message, it is sent to a Queue for valid messages.

For an explanation of using these Collaboration Definitions and the validation Project examples, see SWIFT Projects.