Datasheet: WebSphere Transformation Extender Pack for SWIFTNet FIN

IBM WebSphere Transformation Extender Pack for SWIFTNet FIN

Datasheet

October 2008

Datasheet: WebSphere Transformation Extender Pack for SWIFTNet FIN

Description
The IBM WebSphere Transformation Extender (WTX) Pack for SWIFTNet FIN delivers a powerful and flexible set of components that support the SWIFT FIN message standard, and allows for easy integration of SWIFT messages into your existing systems. Major benefits of the Pack are: Easily maintain compliance with SWIFT FIN Standards Regular and timely Pack updates in line with Standards changes SWIFT Type Trees for easy integration Comprehensive validation and error reporting

The Pack components can be deployed in many different ways, including the WTX Command Server and Launcher editions, or used with WTX for Integration Servers to utilize WebSphere Message Broker (WMB), WebSphere Enterprise Service Bus (WESB), or WebSphere Process Server (WPS). The Pack components can also be embedded in your application via the APIs provided by the WTX for Application Programming edition. The current edition supports the SWIFT SR 2009 standard message set. Released in May 2009, the current version number of this Pack is 4.2.4 and is supported on WTX versions 8.0, 8.1 and 8.2 The Pack is submitted each year for certification against the SWIFTReady Message Data Services label. The currently certified version is for 2008.

Pack Contents:
SWIFT Type Trees, providing full syntactic definition of all MT messages in the SWIFT Standard, including full code-word validation Logical Message Format (LMF) Transformation Maps for simplified integration Java validation component for enhanced error reporting , including validation for Conditional Network Rules, Field Level Network Validated Rules and ISO 15022 Market Practice rules Connectivity maps for SWIFT Alliance Access, utilizing MQSA Sample Integration Flow Designer (IFD) system to assist with deployment and testing with the WTX with Launcher edition. These files enable all maps in the Pack to be compiled, and use file watches to move messages between the back-office application and the SWIFT Network. Maps for creating BIC, Country and Currency Code lookup files from standard SWIFT directory files

Pre-requisites:
IBM WebSphere Transformation Extender Design Studio A base edition of IBM WebSphere Transformation Extender for multiplatforms or z/OS o WebSphere Transformation Extender for Application Programming o WebSphere Transformation Extender with Command Server o WebSphere Transformation Extender with Launcher o WebSphere Transformation Extender for Integration Servers

Complementary industry Packs:

IBM WebSphere Transformation Pack for SWIFTNet Funds IBM WebSphere Transformation Pack for SEPA

October 2008

Datasheet: WebSphere Transformation Extender Pack for SWIFTNet FIN Logical message Format (LMF)
The Pack utilizes an IBM Logical Message Format (LMF), an XML representation of the SWIFT message set that eases integration with internal systems, and helps to shield users from SWIFT standards changes. The LMF provides an independent representation of SWIFT messages, based upon actual business elements and classes. In doing so, it provides a full set of business messages independent of any network message format or structure. The chief advantage of this is that different message formats can be mapped to each other through the LMF; then, when changes in the elements in those messages occur (for example, SWIFT standards releases etc), changing the LMF will reflect those changes and minimize the impact on the integration maps with your host application. The LMF itself is implemented as a WTX type tree. LMF Transformation Maps are available for: Payments Transfers Datasheet: WebSphere Transformation Extender Pack for SWIFTNet FIN Treasury markets Trading Statements Settlement Cash management Corporate actions

Integrating Business Applications

In order to transform data for business applications, maps will need to be developed based on either the LMF type trees or the standard SWIFT Type Trees in the Pack, along with custom-built or imported type trees for the Application. Type trees are also available as templates in one of the optional Enterprise Packs for SAP, SAP XI, Siebel and PeopleSoft.

Validation and Error Reporting

The Java Validation Component (JVC) provides a framework for validating SWIFT messages and can be used to check messages before they are transmitted to SWIFT. It provides superior error reporting functionality compared to using a type tree for validation. There is no need to build a debug version of the map, or visually analyze map trace files as the JVC points to the source of the error. The JVC supports the complete Category 1 through Category 9 SWIFT MT message set. The JVC will validate the following as per the 2009 SWIFT Standards: Message Syntax (structure of message) Field Syntax (size and data type) Field Cardinality (Optional, Mandatory, Repeating) Codeword validation Network Rules, both Conditional and Field level SWIFT Header Bank Identifier Codes (BICs) Currency Codes and associated number of decimal places in amount fields Country Codes ISO 15022 Market Practice rules (SWIFT rules V1.1 August 26, 2002) The JVC features an XML -based error reporting mechanism. This provides enhanced error reporting capabilities, by pointing you directly to the source of the error.

October 2008

Datasheet: WebSphere Transformation Extender Pack for SWIFTNet FIN SWIFT Alliance Access and WMQ Connectivity
The IBM WTX Pack for SWIFTNet FIN connects to the SWIFT Alliance Access server for connectivity to the SWIFT network. IBM WebSphere MQ enables this connection. The SWIFTAlliance Access server has a component called MQSA that mediates and routes between the native Alliance queues and a set of queues hosted by a WebSphere MQ Server. The WTX system will typically be on a separate machine on the network and will interact with the Alliance using WebSphere MQ Client software. To be fully operational, a number of MQ queues need to be created and configured, as well as configuring the MQSA component to route from these queues to the native Alliance queues.

Sample Map System for the Launcher Edition

The Pack contains a set of Integration Flow Designer (IFD) files to assist with deployment and testing. These files enable all maps in the Pack to be compiled, and uses file triggers to initiate maps to process messages between the back-office application and the SWIFT Network. The system pulls all the components of the Pack together, and demonstrates message flows in both directions, both from internal systems out to SWIFT and vice versa. The LMF, JVC and SWIFT Alliance Access components are all utilized via a series of file triggers to initiate the various components. There is also an archive option to preserve all messages processed by the system

October 2008