Swift Binding Component

About SWIFTAlliance Gateway

SWIFTAlliance Gateway is a modular software package that is installed on top of the SWIFTNet Link (SNL) software, and is designed to enable application-to-application communication. Using the SWIFTNet interactive services, InterAct and FileAct, messages and files are typically exchanged between a customer application (client) and a central application (server) over the Secure IP Network (SIPN). SWIFTAlliance Gateway can handle large volumes of information and is therefore suitable for use with both client and server applications.

Introduction to SWIFTNet

SWIFTNet is a global business messaging network for secure connectivity between institutions that !!participate in the financial services industry. As such, SWIFTNet is designed to satisfy institutional community requirements for inter-operability of mission-critical financial software solutions. SWIFTNet provides an assurance of infrastructure reliability, availability, access control, correspondent and message authentication, message integrity, and confidentiality, to business applications that are interconnected among a community of institutions. Optionally, SWIFTNet also provides non-repudiation support, message validation, store-and-forward, and role-based access control.

SWIFTNet messaging services

SWIFTNet offers four messaging services, SWIFTNet InterAct, FileAct, Browse, and FIN. Of these four, the SWIFTAlliance Gateway specifically addresses FileAct and InterAct in client mode, with both Real Time and Store-and-Forward transfers.

SWIFTNet InterAct

SWIFTNet InterAct provides secure and reliable exchange of individual structured financial messages. SWIFT customers’ messaging requirements vary from customer to customer but also from message to message. SWIFTNet InterAct offers you a broad range of telecommunication modes.

Store-and-Forward Messaging

SWIFTNet InterAct’s store-and-forward capability is designed for messages that are destined for a large number of correspondents, many of whom may not be online at the time of transmission. It removes the uncertainty and inconvenience of worrying about whether or not your correspondents are on-line at the time you send the message. The message is delivered as soon as the recipient is ready to receive it. As a result, it provides an ideal way to send individual instructions, confirmations, and reports to large numbers of correspondents, some of whom may be in different time zones.

Real-Time Messaging

Real-time messaging offers a low-cost alternative to store-and-forward for messages which are destined for correspondents that are online at the time of transmission. As a result, it is ideal for sending individual instructions, confirmations, and reports to a few large correspondents, or for messages to market infrastructures.

SWIFTNet FileAct

SWIFTNet FileAct provides secure and reliable transfer of files, such as batches of structured financial messages or large reports. Typical applications include repetitive credit transfers such as pension or salary payments, securities value-added information and reporting, and regulatory reporting. SWIFTNet FileAct offers a variety of messaging modes.

Store-and-Forward File Transfers

SWIFTNet FileAct’s store-and-forward capability ensures that your correspondents receive your message whether or they are online at the time of transmission. Messages are delivered when the recipient is ready to receive it. Store-and-Forward is an ideal way to send individual instructions, confirmations and reports to large numbers of correspondents, some of which may be in different time zones.

Real-time File Transfers

Real-time messaging provides a lower-cost alternative to store-and-forward for files that are destined for correspondents that are online at the time of transmission. This makes it ideal for sending files to a few large correspondents or market infrastructures. Note: For more information regarding SWIFTNet, SWIFTAlliance Gateway, and InterAct and FileAct services, see the SWIFTNet Service Design Guide and SWIFTAlliance Gateway Operations Guide.

General Description of Swift Binding Component

As specified in JBI Specification 1.0 (JSR 208): BCs are used to send and receive messages via particular protocols and transports. They serve to isolate the JBI environment from the particular protocol by providing normalization and denormalization from and to the protocol-specific format, allowing the JBI environment to deal only with normalized messages. (Note that protocol-specific metadata can be attached to a normalized message, or the message exchange, in their metadata, allowing protocol-specific information to be conveyed to a SE or BC in a fashion that is opaque to other JBI environment components.) The Swift Binding Component (refer to as Swift BC herein) is such an implementation in compliance with JSR 208, it provides a comprehensive solution for configuring and connecting to backend systems supporting Swift protocol. The Swift BC implements all the required BC interfaces in JBI specification so that it can be deployed and run in any JBI compliant target environment. To facilitate the process of service definition and binding, the implementation also comes with a design time component – a Netbeans module which makes WSDL authoring and Swift binding a convenient process in Netbeans IDE.

Development Information

• Features & Limitations TBD • Requirements & Use Cases TBD

User Information

• Description of SwiftBC WSDL Extensibility Elements o Component Configuration - Swift Binding Component follows the following convention not covered in JBI spec to support component configuration at installation and runtime:  Component configuration defaults are present in the JBI descriptor of the component  Defaults may be overridden via JBI installation configuration parameters at installation time.  At run-time, a custom JMX MBean exposes the configuration and allows relevant settings to be changed on-the-fly.

Future Enhancements

• TBD

Downloads

• Swift version 1.x XSD's

Download Swift version 1.0 xsd's and import the required xsd's based on the message type into the created project.

Swift Binding Component Demos

Design Time - Creation & Validation of WSDL with Swift BC Binding • Swift BC WSDL Creation and Validation 1 TBD

Swift Information Resources

For more insight into Swift please go through

• Swift Specification

• Swift Tools & Resources

People

• Contributor: Oscar Montoya, Harry Liu, Alex Fung

• Manager: Fred Aabedi

This page (revision-5) was last changed on 07-May-07 14:06 PM, -0700 by Fred Aabedi.
This page was created on 07-May-07 10:08 AM, -0700 by Fred Aabedi.

More info...