Topics: |
This topic highlights the configuration of the sample inbound message flow for the iWay Integration Solution for SWIFT. The message flow represents the movement and tasks in the conversion of a message from SWIFT FIN format to XML format.
Topics: |
How to: |
The iWay e-Business Information Exchange (Ebix) framework supplies several Ebix files for the iWay Integration Solution for SWIFT.
An Ebix file for SWIFT is named SWIFT_ccyy.ebx, where ccyy is the release year. For example, an Ebix file for the 2019 SWIFT FIN messages is named SWIFT_2019.ebx.
For more information on the supported SWIFT FIN messages, see Ebix-Supported Transaction Sets.
Note: You can download the latest Ebix archives from the Information Builders Technical Support Center:
https://techsupport.informationbuilders.com/
Note: The SWIFT 2019 Ebix is attached to the sample channels.
For more information on how to add (import) an Ebix to an application project, see How to Import an Ebix.
The New (Select a wizard) dialog opens, as shown in the following image.
The New Register Set Wizard opens, as shown in the following image.
The named register set opens as a new tab in the workspace, where you can define your registers, as shown in the following image.
The following image shows a sample register set (SWIFT_IB), which is used for inbound processing.
The selected channel opens in the Channel Builder, which displays as a tab in your workspace, as shown in the following image.
The following image shows a sample listener configuration for the inbound channel.
The following table lists and describes the available configuration parameters for the listener.
Parameter |
Value |
---|---|
Active |
Enables (set to true by default) or disables the listener. |
Input Path |
sreg(SWIFT_IB.InputDir) This value is a special register that uses a defined directory in which input messages are received. Ensure that you have created this directory; otherwise, errors will occur during deployment. |
Destination |
sreg(SWIFT_IB.DefaultDir) This value is a special register that uses a defined directory in which output files are stored after transformation. Ensure that you have created this directory; otherwise, errors will occur during deployment. |
Removal Destination |
sreg(SWIFT_IB.ArchiveDir) This value is a special register that uses a defined directory to which input messages are moved if they fail during transformation. Ensure that you have created this directory; otherwise, errors will occur during deployment. It is recommended to configure a removal destination when you are constructing a basic channel. |
Suffix In Filter |
* Input files with any file extension are allowed. |
Suffix Out |
xml The extension for output files is .xml. |
Accept Zero Length Files? |
true If true, listener expects flat (non-XML). Automatic parsing is not performed. |
The following image shows a sample preparser configuration for the inbound channel.
The following table lists and describes the available configuration parameters for the preparser:
Parameter |
Description |
---|---|
version |
Represents the SWIFT release year you are using. |
template |
Represents the template to use for the SWIFT to XML transform. Enter the following: MT%toXML.xch |
timestamp |
Writes a time stamp to the log file. Select true or false. |
systemMessages |
Determines whether to process system messages. If true is selected, the system messages are automatically parsed and directly written to a good validation report. If false is selected, the system messages are bypassed and not processed. There is also a separate preparser available if you want to set up a standalone channel to parse just system messages. |
A route defines the path a message takes through a channel.
Channel Builder defines the route for you automatically. Just add your process flow(s) to the route in Channel Builder.
Process flows (pflows) are defined and created in the process flow editor. To create a new process flow, right-click on Flows, select New, and then click Flows, and follow the dialog.
The following image is a sample process flow for the inbound channel.
How to: |
Outlets define how a message leaves the channel. In the sample inbound configuration, a Passthrough outlet is used. For details on supported protocols, which can be used as outlets, see the iWay Service Manager Protocol Guide.
To build the channel:
The Channel Object dialog opens.
The following image shows a sample inbound channel displayed in the Channel Builder.
You can manually build your channel by right-clicking the bundle name, selecting Integration Tools, and then clicking Build from the context menu, as shown in the following image.
How to: |
For more information, see:
To ensure that the channel is working as expected, perform the following steps:
For more information on obtaining SWIFT sample files (MT535.swift, MT541.swift, and MT950.swift) for testing purposes, see Extracting SWIFT User Samples.
For example, a SWIFT input file named MT950.txt is named MT950_2019-11-27T17_17_38_932Z.xml on output.