In this section: |
This topic provides step-by-step instructions on how to configure a basic 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.
To access the iWay Service Manager Administration Console, you must first ensure that the iWay Service Manager service is running.
For instructions on starting iWay Service Manager, see the iWay Service Manager User's Guide.
or,
from a browser such as Microsoft Internet Explorer, enter the following URL,
http://host:port
where:
The following image shows the URL with the default values.
Note: The default user name and password is iway.
The iWay Service Manager Administration Console opens, as shown in the following image.
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 2013 SWIFT FIN messages is named SWIFT_2013.ebx.
For details on the supported SWIFT FIN messages, see Ebix-Supported Transaction Sets.
This topic describes how to add an Ebix to the Registry on Windows and UNIX.
Note: Ebix archives are not packaged with the iWay Service Manager installation. You can download all Ebix archives from the following website, which is hosted and maintained by iWay Software:
http://techsupport.informationbuilders.com
Note: A 2013 Ebix is attached with the sample channels that are provided in this document. If you are going to download and attach an Ebix, then you must delete the Ebix from the sample channels or remove it from the channel being deployed.
The Ebix pane opens, as shown in the following image.
You are prompted for the name of the Ebix and an optional description.
Note: This step must be repeated for each SWIFT Ebix that is added to the Registry.
On the Ebix pane, you will see that the Ebix was successfully added. Later you will associate it with the channel for inbound processing.
Depending on your system configuration, there are two methods that you can use to add an Ebix to the Registry on UNIX and z/OS.
An inlet defines how a message enters a channel. For SWIFT, it typically contains the following:
For the purpose of this example, we will show the configuration with a File listener. For details on supported protocols, see the iWay Service Manager Protocol Guide.
The configuration parameters pane opens, as shown in the following image.
Parameter |
Value |
---|---|
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 |
* Input files with any file extension are allowed. |
Suffix Out |
xml The extension for output files is .xml. |
Accepts non-XML (flat) only |
true If true, listener expects flat (non-XML). Automatic parsing is not performed. |
You are prompted for the name of the listener and an optional description.
In a later step, you will associate this listener with the inlet.
The SWIFT preparser parses a SWIFT input message into an XML output.
For details on the supported SWIFT FIN messages, see Ebix-Supported Transaction Sets.
The Preparsers configuration parameters pane opens.
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 |
validateoff |
Select false to validate the structure. |
timestamp |
Writes a time stamp to the log file. Select true or false. |
You are prompted for a name and optional description for the new preparser.
In the next procedure, you will associate this preparser with an inlet.
Now that you have added a File listener and a preparser to the Registry, you are ready to add and define an inlet. You will associate the previously created listener and preparser with the inlet.
Parameter |
Value |
---|---|
Name * |
SwiftToXml_Inlet |
Description |
Inlet for SWIFT to XML (Listener and SWIFTPreParser) |
The next pane prompts you for the component type.
The next pane prompts you to select a listener.
The listener is associated with the inlet. Now you need to associate the preparser created earlier with the inlet.
The next pane prompts you for the component type.
On the next pane, you are prompted to select a preparser.
You have now successfully completed definition of the inlet.
A route defines the path a message takes through a channel.
The route for the channel for inbound processing consists of a process. A process is a stateless, lightweight, short-lived microflow executed by iWay Service Manager on a message as it passes through the system. A service is an executed procedure that handles the business logic of a message.
This section describes how to create a process flow with iWay Integration Tools (iIT) Designer and bind it to a sample channel as a route.
For details on the full features of iIT Designer, and additional information on using its capabilities, see the iWay Integration Tools Designer User's Guide.
You will complete the following high-level steps to define the route.
Parameter |
Value |
---|---|
Name * |
SWIFT_to_XML_QS_Pflow |
Description |
SWIFT to XML transformation where output transform data will be written to a good or bad folder depending on the validation report service. The definition of folders can be found in the channel SREG. |
You are prompted for the type of component to associate with the route.
The route, with its associated process flow, has been successfully defined.
An outlet defines how a message leaves a channel. In the sample inbound configuration, a default outlet is used. For details on supported protocols, which can be used as outlets, see the iWay Service Manager Protocol Guide.
Now that you have defined the inlet, route, and outlet for the inbound channel, you are ready to add the inbound channel to the Registry and associate the conduits with it.
Parameter |
Value |
---|---|
Name * |
Swift2013ToXml_QS2_Pflow_Channel |
Description |
SWIFT to XML channel using a process flow. Output XML will be placed in different folders based on results of the Validation Report. A channel SREG is used to define the folders. |
You are prompted to associate components with the channel.
The next pane prompts you to select an inlet.
The inlet is added to the channel.
Now you need to associate the route defined earlier with the channel.
The next pane prompts you for the component type.
On the next pane, you are prompted to select a route.
The following image shows the completed channel (Swift2013ToXml_QS2_Pflow_Channel) with a defined Inlet, Route, and Outlet.
The Channel Definitions pane opens.
The Add Ebix components pane opens.
The following image shows that the SWIFT 2013 Ebix is now bound to the Swift2013ToXml_QS2_Pflow_Channel.
Now that you have associated all the components with the channel, you are ready to build it.
The build results of the selected channel are displayed, as shown in the following image.
If an error or errors are displayed in the Message column, take the appropriate action as instructed.
Deployment is the mechanism by which a channel moves from being stored in the Registry to becoming active in iWay Service Manager. For more information on deployment, see the iWay Service Manager User's Guide.
A green check mark now appears under the status column, as shown in the following image.
The channel is ready to accept inbound data.
To ensure that the channel is working as expected, perform the following steps:
The following table contains links to SWIFT files that are attached to this PDF and can be used to verify your channel.
SWIFT MT950 (Statement of Cash) |
SWIFT MT535 (Statement of Holding) |
SWIFT MT541 (Receive Against Payment) |
---|---|---|
. MT950.txt |
. MT535.txt |
. MT541.txt |
Note: For file association compatibility only, each SWIFT file that is attached to this PDF has been renamed to include a .txt extension. However, please note that the actual SWIFT file that is placed in the input directory will not carry a .txt extension.
For example, a SWIFT input file named MT950.txt is named MT950__2013-11-27T17_17_38_932Z.xml on output.
The following table contains links to sample XML validation reports that are attached to this PDF and can be used to verify your output.
SWIFT MT950 |
SWIFT MT535 |
SWIFT MT541 |
---|---|---|
. MT950_rpt.xml |
. MT535_rpt.xml |
. MT541_rpt.xml |
The following table contains links to SWIFT FIN message report files that are attached to this PDF and can be used to verify your output.
SWIFT MT950 |
SWIFT MT535 |
SWIFT MT541 |
---|---|---|
. 950.xml |
. 535.xml |
. 541.xml |
Using the Archive Manager feature of iWay Service Manager, you can archive your channel configuration with its associated components and import them into another Registry. They will then be available from that Registry for modification or reuse.
For details on this feature, see the iWay Service Manager User's Guide.
iWay Software |