In this section: |
This topic provides step-by-step instructions for configuring a basic outbound message flow for the iWay Integration Solution for SWIFT. The message flow represents the movement and tasks in the conversion of a message from XML to SWIFT.
If you plan to modify the message flow presented here and would like more information on the supported iWay business components that you can use in channel construction, see the iWay Service Manager User's Guide.
For instructions, see Accessing the iWay Service Manager Administration Console.
Note: Before configuring your XML to SWIFT channel, it is recommended that you first test and configure your SWIFT to XML channel.
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
Tip: If you already added an Ebix to the Registry as described in Adding an Ebix to the Registry, you do not need to add it again for outbound processing. You can go directly to Defining an Inlet.
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.
In this section, you will add a listener to the Registry, and then associate that listener with a new inlet.
Select File from the Type drop-down list and click Next.
The configuration parameters pane opens.
Parameter |
Value |
---|---|
Input Path * |
sreg(SWIFT_OB.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_OB.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_OB.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 |
xml Input files with the extension .xml are allowed. |
Suffix Out |
swift In this example, the extension for output files is .swift. |
Parameter |
Value |
---|---|
Name * |
XMLtoSWIFT_Listener |
Description |
File listener for XML input |
Parameter |
Value |
---|---|
Name * |
XMLtoSWIFT_INLET |
Description |
Inlet for XML to SWIFT |
The next pane prompts you to select a listener.
The listener is added to the inlet.
A route defines the path a message takes through a channel.
The route for the channel for outbound 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.
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 outbound 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 outbound channel, you are ready to add the outbound channel to the Registry and associate the conduits with it.
Parameter |
Value |
---|---|
Name * |
XMLtoSWIFT_QS2_Pflow_Channel |
Description |
XML to SWIFT channel using a process flow. Output will be placed in different folders based on Validation Report results. A channel SREG is used to define the folders. |
You are prompted to associate components with the channel.
The inlet is associated with the channel. Now you need to associate a predefined route with the channel and set it to the default.
The next pane prompts you for the component type.
On the next pane, you are prompted to select a route.
The Construct Channel pane opens.
The following image shows the completed channel (XMLtoSWIFT_QS2_Pflow_Channel) with a defined Inlet, Route, and Outlet.
The Channel Definitions pane opens.
Note: Before you build your channel, verify that your Ebix and preemitter are configured to use the same SWIFT version.
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 make sure that the channel is working as expected, perform the following steps:
The following table contains links to sample XML input files that are attached to this PDF and can be used for testing purposes.
SWIFT MT950 |
SWIFT MT535 |
SWIFT MT541 |
---|---|---|
. MT950.xml |
. MT535.xml |
. MT541.xml |
The following table contains links to the SWIFT output files that are attached to this PDF and can be used to verify your output.
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 output file that is attached to this PDF has been renamed to include a .txt extension. However, please note that the actual SWIFT output file will not carry a .txt extension.
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 |