BOX for SWIFTNet
Functions
Complementary Services
SDI/SDO
BOX offers features enabling a customer to continue using MERVA-specific batch input and output functions. This feature eases a migration from MERVA to BOX and provides an emulation of the MERVA sequential dataset (SDS) programs DSLSDI and DSLSDO.
The functions provided in MERVA to import SWIFT FIN messages from a sequential MVS dataset and to export FIN messages into a sequential MVS dataset are supported.
MERVA API Emulation
To further ease migration from MERVA, BOX includes an emulation of the most important services provided by the IBM program DSLAPI including Queue Management Services, TOF (Tokenized Form) Services, and Message Format Services.
Web Services
BOX currently offers two specific functions implemented as Web Services:
- The Validation Service allows an application to send a message to the service and to receive a reply indicating whether the message passed validation, or if not, which syntactical or semantic errors occurred
- The Authorization Service checks if an RMA authorization exists for a specific correspondent and specific message type and returns the result to the calling application.
With these Web Services BOX provides the same functions as the former MERVA BKE lookup and the MERVA validation API call, but through a modern, future-oriented interface fitting into the strategy of a Service Oriented Architecture (SOA).
Duplicate Checking
Duplication Checking is a specific configurable part of the workflow and is not related to any PDE / PDM handling. If this feature is active, BOX stores all relevant parameters of every message such as amount, TRN, sender, and recipient. Every new message is checked against this database. If the message is found to be a duplicate it is passed to the corresponding error queue. Options can be defined as to which message types are to be checked, which parameters are to be extracted, and the time period for which messages are to be checked.
Message Enrichment
User Data is a feature of MERVA allowing external applications or processing steps in MERVA itself to include user or application specific data in a message. This data is not only stored in the MERVA message, but can also be used for routing purposes in MERVA.
This requirement has been considered in the BOX design and BOX provides similar functionality. The information can be provided through application interfaces such as MQ or via the MERVA API emulation. User data can be displayed in BOX Journals and Application Queues. The data can be filtered and searched for by standard BOX search and filter functions and can be analyzed for routing decisions.
In addition to the configuration options of the graphical user interface it is also possible to customize screens using X-HTML syntax. This is particularly helpful for visualizing customer specific user data and offers a high degree of flexibility for implementing customer specific requirements such as those previously available with MERVA MCBs.
Interfaces to Third Party Software
It may be essential that messages are passed to external applications at a specific stage of message processing. A typical example is the requirement to apply an OFAC (Office of Foreign Assets Control) filter on specific message types. Depending on the results of this check some special handling of the messages may be required. Based on a modular plugin architecture such functionality provided by third party software can be integrated transparently into the BOX message processing workflow.