SWIFT Module 7.1 SP10.July 2020 | Package Services | XML Parsing Templates for SWIFT FIN Messages | Overview
SWIFT Module provides XML parsing template files to define the structure of SWIFT FIN messages. Each parsing template describes the message using an XML syntax, and each parsing template defines a unique SWIFT message. SWIFT Module uses the parsing template when it receives a message of that type.
XML parsing templates are used only when receiving messages in Integration Server.
To fully define the entire set of SWIFT FIN messages, a parsing template is required for each type of SWIFT message. The parsing templates are installed in the appropriate category and version folder. SWIFT Module reads the parsing template as needed at run time.
The name of each parsing template is based on the definition of the message type it contains. Each message type has a unique ID, which is usually a three-digit number. Typically, the name of a parsing template follows a convention that indicates the MT defined in the parsing template. The following table shows the format used for the names of parsing templates:
Format of Parsing Template Name
Used for…
Incoming ACK/NAK messages returned by the SWIFT system. Any service message will follow this file name format.
where nnn is the unique id for the message type.
All other incoming messages types and all outgoing message. SWIFT Module looks for a specific parsing template file for the specific type of message, for example, swiftmt101.xml.
The parsing templates that are provided with SWIFT Module are a mixture of messages that conform to the older SWIFT message standard (ISO 1775) and the new standard (ISO 15022). SWIFT Module can support both standards because of the flexible parsing template syntax. As a result, when SWIFT issues an update of their message standards, you can define new parsing templates for new SWIFT message formats or update existing parsing templates for updated SWIFT message formats.
The wm.fin.trp:receiveMessage converts messages that are received from SWIFT into Integration Server document structures. Likewise, the wm.fin.trp:sendMessage service converts Integration Server documents into SWIFT FIN messages, so that the messages can be sent to SWIFT.