Extended financial messaging services with support for SWIFT


IBM® Message Entry and Routing with Interfaces to Various Applications (MERVA) is an extension to IBM WebSphere® Business Integration for Financial Networks. It provides access to the Society for Worldwide Interbank Financial Telecommunication (SWIFT) Internet Protocol Network (known as SIPN) for additional services using a scalable financial messaging infrastructure. IBM MERVA is a financial message processor that handles message formatting, queuing and routing for more detailed, expansive financial operations that support mission-critical applications.

MERVA offers:

SWIFT message handling

Efficient message queuing and routing

Robust messaging infrastructure

Flexible message formatting and flows

MERVA ESA components

The IBM licensed program IBM Message Entry and Routing with Interfaces to Various Applications for ESA (hereafter abbreviated to MERVA ESA) provides routing and message handling for S.W.I.F.T. messages (defined by the Society for Worldwide Interbank Financial Telecommunication s.c.) or for user-defined messages. It interfaces to the IBM Websphere® Business Integration for Financial Networks for connection to the SWIFT network, via the Application Programming Interface (API) to the Telex network, and to other MERVA systems. Message processing and checking are provided for SWIFT messages, and data formats for other network connections can be added. User applications can access the services of the MERVA products via the API and sequential batch interfaces.

Message queuing and routing is the basic functionality of MERVA. Messages are stored in logical queues in a VSAM relative record data set (RRDS) and key-sequenced data set (KSDS) or in tables of a DB2® relational database. These messages are then routed from one queue to another queue based on predefined routing conditions. Queue definition is very flexible. There is no restriction in the number of queues on a specific implementation. Furthermore, queues can be on the same system or on distant MERVA systems, allowing users to establish a cross-system or even a cross-country messaging infrastructure. Routing definition is also extremely flexible. Messages can be routed from any queue to any other queue without restriction. Routing can be conditional or unconditional.

Message formatting allows users to adapt MERVA to the different message types used by the external networks and therefore keep the existing applications independent of external message types (which constantly change). Message processing functions provide users all the necessary tools to better manage and control the flow of messages:

MERVA ESA Components provide features which run in different environments:

Operating System Software Hardware
VSE, Windows, z/OS MERVA ESA, 5648-B29, is compatible with z/OS or VSE (Virtual Storage Extended).

The various features of the MERVA ESA Components, 5648-B30, require different software:

The MERVA Message Processing Client and Import/Export components of MERVA ESA are compatible with the following Windows® products: Windows 2000 Professional, Windows 2000 Server, Windows Server 2003, or Windows XP Professional.

The Traffic Reconciliation component of MERVA ESA is compatible with z/OS.
MERVA ESA, 5648-B29, runs native on processors supported by IBM z/OS or VSE. The required size of the processor depends on the operating system type and on which of the following data communication systems is used: Information Management System (IMS) or Customer Information Control System (CICS®) in either a z/OS or VSE environment.

The various features of the MERVA ESA Components, 5648-B30, require different hardware:

The MERVA Message Processing Client and Import/Export components of MERVA ESA run on Intel®-compatible processors.

The Traffic Reconciliation component of MERVA ESA runs native on processors supported by z/OS. The required size of the processor depends on whether the IMS or CICS data communication system is used.

Not in United States?

Contact IBM

Considering a purchase?