MERVA Bridge

The MERVA Bridge connects MERVA ESA with FTM SWIFT, and lets MERVA applications transfer FIN messages via the SIPN, or internally using the FMT FIN service.

The MERVA Bridge connects MERVA ESA with FTM SWIFT by transporting messages between MERVA ESA queues and IBM MQ queues. These messages are converted between MERVA ESA and FTM SWIFT formats. The FTM SWIFT message flows use these IBM MQ queues for input, reply, and output.

The messages exchanged between MERVA ESA and FTM SWIFT are written into the MERVA ESA journal if requested in the MERVA Bridge customization module DSLKPROC. The format of these journal records is different from the records created by the SWIFT Link. There is no one-to-one relationship between the types of journal records.

MERVA Bridge messages are grouped by IBM MQ message types. SWIFT Link messages are grouped by whether they are sent or received. Table 1 shows how the journal IDs from MERVA Bridge correspond to those of SWIFT Link. For example, MERVA Bridge journal ID 90 corresponds to SWIFT Link journal ID 50. The layout of these journal records is described in more detail in MERVA for ESA Version 4: Concepts and Components.

For more information about how to customize the DSLKPROC, see the section in MERVA for ESA Version 4: Customization Guide that describes the MERVA Bridge to FTM SWIFT.