JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Java CAPS SWIFT Message Library User's Guide     Java CAPS Documentation
search filter icon
search icon

Document Information

SWIFT Message Library

Overview of SWIFT Message Libraries

Library Versions and Access

Installing the SWIFT Message Library

Increasing the Heap Size

To Increase the Heap Size for GlassFish

To Increase the Heap Size for NetBeans

Using the SWIFT Message Library

SWIFT Message Type OTDs

SWIFT Message Structure

Message Library and Collaboration Locations in NetBeans

SWIFT Message Type Reference

Category 1 Messages

Category 2 Messages

Category 3 Messages

Category 4 Messages

Category 5 Messages

Category 6 Messages

Category 7 Messages

Category 8 Messages

Category 9 Messages

Validation Collaborations

SWIFT Generic Library

SWIFT Message Library JAR Files

Using Message Validation Features

Basic Validation Features

Validation Components

Validation Methods

Validation Collaboration Definitions

Validation Operation

Basic validation steps

Library Methods

Message Validation Rules

Message Format Validation Rules (MFVR)

MFVR Validation Methods

MFVR Errors

In Collaboration Validation Methods

validate()

Description

Syntax

Parameters

Return Values

Throws

validateMFVR()

Description

Syntax

Parameters

Return Values

Throws

validateMPR()

Description

Syntax

Parameters

Return Values

Throws

Calling the Validation Methods in your Collaboration

SWIFT Projects

Importing a Sample Project

To Import a Sample Project

SWIFT Projects and NetBeans

About the SWIFT MX Validation Sample

Sample Project

Descriptions of components

Running the MX Sample Project

SWIFT Correlation Repository Sample

Prerequisites

Installation steps

Preparing an SCR flow

Designing an SCR flow

Linking the Domain Name and Direction to a Color

Using the SCR for Monitoring Flows

Using the Viewer for Monitoring Transactions

Using the SCR as Gatekeeper

Using the Viewer to Repair Messages

Updating BICDirService

Source of Information

Update Operation

BICDirService Method Operation

Lookup Method Definitions

Validation Method Definitions

BICDir Exceptions

Error message framework

Error Message General Form

Updating BICPlusIBAN

To Update BICPlusBAN Information

BICPlusIBAN Validation Method Definitions

Error Message Information

Error Messages

Setting the Debug Level

Message Examples

Parse Debug Level Message Example

Using SWIFT FIN-Based Funds OTDs

SWIFT Message Library Funds Features

Using SWIFT Message Library Java Classes

Relation to OTD Message Types

SWIFT Message Library Javadoc

OTD Library Java Classes

Updating BICDirService

The BICDirService feature is a database service. The data files used to populate BICDirService must be updated periodically from SWIFT’s source CD-ROM issued once every four months.

Source of Information

The Java constructor for the BICDir class loads the required data from the following SWIFT-supplied files:

The constructor takes an argument from the directory that contains these two files. It then opens each file and loads the appropriate fields into a searchable structure. For more details on these files, see the current SWIFT BIC Database Plus Technical Specifications document for actual file layout and positioning information.

The data used to look up and validate comes from SWIFT’s own BIC bank files containing its BIC codes and its currency and country codes. When necessary, SWIFT updates these files with a new version of its lookup tables, to keep them current. You can upload these files to Java CAPS and control when updates to the system occur and access these files via SWIFT updates.

Update Operation

The BICDirService feature allows multiple simultaneous objects to access its methods with near-local object response times. The SWIFT standards are not always sufficiently complete to enable STP. Currently a message can pass network validation but fail at the receiving end because of incompatible definitions or codes, or because of missing data. The result is having to manually repair or follow up on these messages and possible retransmission of the message.

The SWIFT Message Library’s BICDirService ensures that valid, up-to-date BIC, country, and currency codes are present in the messages processed through Java CAPS. This feature increases the likelihood that a given message can flow “straight through”.

You must update the BICDirService information before running components that utilize this feature. This procedure updates the BICDirService information.

To Update BIC Information

  1. In the NetBeans Projects window, expand CAPS Components Library > Message Library > Swift.
  2. Right-click the bic.jar file, point to Version Control, and select Check Out. Click Check Out on the dialog box that appears.
  3. Right-click the bic.jar file again, and select Update BIC Files.

    A browser window appears so you can browse to and select the files to update.

  4. Navigate to the location of the CU.dat file on the SWIFT update CD-ROM. select the file, and click Open.
  5. Repeat the above two steps to update the FI.dat and CT.dat files.

BICDirService Method Operation

The BICDirService methods are static methods of a single Java class, the BICDir class. There is one method per each required lookup and validation. The BICDir methods are not dependent on any module other than SWIFT data files.

Lookup Method Definitions

The BICDir class has the following lookup methods:

Validation Method Definitions

The BICDir class has the following validation methods:

BICDir Exceptions

The purpose of the exceptions is to give you some indication of what error has occurred and how to rectify it.

Error message framework

These error messages are implemented using the log4j framework. STC.OTD.SWIFT.BICDirService is used as the logging category.

Error Message General Form

The message of BICDir exception takes the following general form:

“BICDirService Error [”XX“]– “ error-message

Where: