Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS SWIFT Message Library User's Guide Java CAPS Documentation |
Installing the SWIFT Message Library
To Increase the Heap Size for GlassFish
To Increase the Heap Size for NetBeans
Using the SWIFT Message Library
Message Library and Collaboration Locations in NetBeans
SWIFT Message Library JAR Files
Using Message Validation Features
Validation Collaboration Definitions
Message Format Validation Rules (MFVR)
In Collaboration Validation Methods
Calling the Validation Methods in your Collaboration
About the SWIFT MX Validation Sample
SWIFT Correlation Repository Sample
Linking the Domain Name and Direction to a Color
Using the SCR for Monitoring Flows
Using the Viewer for Monitoring Transactions
Using the Viewer to Repair Messages
BICDirService Method Operation
To Update BICPlusBAN Information
BICPlusIBAN Validation Method Definitions
Parse Debug Level Message Example
Using SWIFT FIN-Based Funds OTDs
SWIFT Message Library Funds Features
The Society for Worldwide Interbank Financial Telecommunication (SWIFT) Message Library contains template messages for use with the Oracle Java Composite Application Platform Suite (Java CAPS). These messages correspond to the SWIFT user-to-user message types employed by its SWIFT network. The library provides an individual object type definition for each SWIFT message type, as defined in the SWIFT standards documentation.
Each SWIFT message library represents a corresponding SWIFT message type. You can use these libraries to transfer SWIFT message data with the Oracle Java CAPS.
SWIFT periodically revises their message types, adding to or subtracting from the total set of message types, and modifying the definitions of individual message types. New sets are identified with the year they are issued, such as 2009 and 2010. New SWIFT Message Libraries are released corresponding to each revised set of SWIFT message types. Java CAPS supports the message types for the current and previous year, so Java CAPS 6.3 supports the 2009 and 2010 libraries.
You must install each year’s version via a separate SAR file.