Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS SWIFT Message Library User's Guide Java CAPS Documentation |
Overview of SWIFT Message Libraries
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 SWIFT Message Library is not installed as part of the standard Java CAPS installation, and needs to be installed after you install Java CAPS. For instructions on installing Repository-based components, see Installing Additional Repository-Based Java CAPS Components in Installing Additional Components for Oracle Java CAPS 6.3.
The annual SWIFT Message Libraries rely on the following components. The Adapters are installed in the standard Java CAPS installation, and you can install the SWIFT Message Library when you install the annual libraries.
File Adapter (the File Adapter is used by most sample Projects)
Batch Adapter (the Batch Adapter is required to run the MX validation sample project)
SWIFT Message Library (this includes all versions of the library)
When you install the SWIFT libraries, install SwiftOTDLibrary.sar and one or both of the following files, depending on which versions of SWIFT messages you are using:
SwiftOTDLibrary2010.sar
SwiftOTDLibrary2009.sar
Because of the size of the SWIFT Message Library, the heap size may need to be increased before using the library. If the heap size is not increased, you might receive OutOfMemoryError messages when you try to build, deploy, or run a SWIFT Message Library Project.
If you receive this message while building or deploying a SWIFT Project, increase the heap size and then retry the process. If you receive the message during runtime, increase the GlassFish server heap size. NetBeans automatically determines the heap size based on available memory, but if you receive the message in NetBeans, increase the heap size for NetBeans as well.
Note - Your Xmx option might have a default value other than 512 depending on your available memory.