| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: BICDirService Method Operation |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Overview of SWIFT Message Libraries
What's New in Java CAPS 6 Update 1
Installing the SWIFT Message Library
SWIFT OTD Library System Requirements
Installing the SWIFT OTD Libraries
Installing the eWay on a Java CAPS Supported System
Increasing the heap size from the Enterprise Designer
OTD and Collaboration Locations in Enterprise Designer
SWIFT Message Library JAR Files
Using Message Validation Features
Message Format Validation Rules (MFVR)
In Collaboration Validation Methods
SWIFT Projects and the Enterprise Designer
SWIFT Sample prjSwift_JCD_MFVROnly Project
SWIFT Sample prjSwift_JCD_MFVRAndBICPlusIBAN Project
SWIFT Sample prjSwift_JCD_BICPlusIBANOnly Project
SWIFT Correlation Repository Sample
SWIFT Sample eInsight™ Project
Configuring the Modeling Elements
Configuring the Integration Server
Creating the Deployment Profile
Creating and Starting the Domain
Building and Deploying the Project
BICPlusIBAN Validation Method Definitions
Using SWIFT FIN-Based Funds OTDs
SWIFT OTD Library Funds Features
Using SWIFT OTD Library Java Classes
Designing with Sun JCA Adapters
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.
The BICDir class has the following lookup methods:
Look up BIC by Institution Name: Takes a string and returns a byte array of BICs (one element is possible). The signature is:
BIC[] getBIC(institutionName*);
Look up BIC by Institution Name, City and Country: Takes three strings, an institution name, city, and country, and returns a byte array of BICs (one element is possible). The signature is:
BIC[] getBIC(institutionName*, city*, country*);
Look up Institution Name by BIC: Takes a BIC string, either a BIC 8 or BIC11, and returns a byte array of institution names (one element is possible). The signature is:
institutionName[] getInstitutionName(BIC);
Look up Currency Code by Country Code: Takes a string, a country code, and returns the currency code. The signature is:
currencyCode getCurrencyCode(countryCode);
Look up Country Code by Currency Code: Takes a string, a currency code, and returns the country code. The signature is:
countryCode getCountryCode(currencyCode);
The BICDir class has the following validation methods:
Validate BIC: Takes a string, either a BIC 8 or BIC11, and returns true or false. The signature is:
boolean validateBIC(BIC);
Validate Currency Code: Takes a string, a currency code, and returns true or false. The signature is:
boolean validateCurrencyCode(currencyCode);
Validate Country Code: Takes a string, a country code, and returns true or false. The signature is:
boolean validateCountryCode(countryCode);
The purpose of the exceptions is to give you some indication of what error has occurred and how to rectify it.
These error messages are implemented using the log4j framework. STC.OTD.SWIFT.BICDirService is used as the logging category.
The message of BICDir exception takes the following general form:
“BICDirService Error [”XX“]- “ error-message
Where:
“”: Marks static text.
XX: Stands for a unique number assigned to each error message.
error-message: A descriptive narrative derived from the condition that caused the error, and a possible solution to rectify it.