The inbound process converts a SWIFT FIN formatted message to an XML transaction.
In a basic message flow, inbound processing consists of the following components and steps. For an illustration of the components available in the construction of a message flow, see Using a Channel to Construct a Message Flow. You will define the components in the configuration instructions in Sample Configuration for Inbound Processing: SWIFT to XML.
Inlet
The preparser ensures that the message is converted to a structurally correct SWIFT XML message. The transformation templates that are provided in the Ebix are used to transform the structure of the document.
The iWay Integration Solution for SWIFT supports the preparsers, which are described in Preparsers.
Validation
The inbound SWIFT message is validated for structure and content. The published SWIFT FIN standards and user implementation guides define element types (for example, numeric, alpha, or date) and describe rules to apply for validation.
For example, here is a typical date tag in an inbound SWIFT message:
98a
The value in 98a is validated against an allowed code list.
Route
In our basic message flow, the copy service redirects the output document to the destination.
For details on available services, see the iWay Service Manager User's Guide.
Outlets
Outlets define how messages leave a channel at the end of a process. In our basic sample channel, one outlet is configured. This outlet outputs the XML format of the document. In a real case scenario, it would output the result of your business logic.
iWay Software |