Sunday, February 5, 2017

Connection Methods in SWIFT Alliance

A connection method is part of a message partner profile. It specifies the type of communication.
back-office application or external product. The location of the message or parameter files for
transmission are specified as a connection point, which is associated with a connection method.
The Application Interface application supports several connection methods. This section
provides basic descriptions of these connection methods after the summary table.

To exchange FileAct messages between Alliance Access and a message partner, the following
connection methods are available:
• Direct FileAct
• File Transfer
• WebSphere MQ

Direct FileAct
The Direct FileAct connection method enables the transfer of a payload file between Alliance
Access and a back-office application. A payload file contains the data that is to be transferred.
The FileAct transmission parameters are always deducted from the message partner profile. No
XML version 2 message or parameter file with FileAct settings is required with the payload file.
Dedicated Direct FileAct input and output file directories are accessible to both Alliance Access
Alliance Access 7.0
244 System Management Guide
and the back-office application or operator. The back-office application or operator use these
directories to simply drop the payload files to send over SWIFTNet or get the payload files
received from SWIFTNet.

Direct FileAct also enables back-office applications to benefit from simplified reporting of
network acknowledgements and of reconciled delivery notifications.
A message partner profile with the Direct FileAct connection method must exist for each
correspondent that will use Direct FileAct to transmit files between each other.

The Direct FileAct connection method requires the licence package 22: DIRECT FILEACT.
The file-transfer session can be started automatically or manually. For example, if a back-office
application stores a payload file in a pre-configured input directory, then the presence of the file
in the directory can automatically start a file-transfer session.
You can define a message partner profile for Direct FileAct only through the Alliance
Configuration package on Alliance Web Platform. You can also view a message partner profile
for Direct FileAct through the Alliance Monitoring package on Alliance Web Platform.

File Transfer
The File Transfer method enables the transfer of batch files containing multiple FIN, FileAct, or
InterAct messages between Alliance Access and a back-office application. For FileAct
messages, in addition to transferring a payload file, Alliance Access or a back-office application
also transfers an XML version 2 message containing the FileAct settings which control the file
transfer, and an optional parameter file. The file-transfer session can be started automatically or
manually.

Note For FileAct messages, the body of the XML version 2 message does not contain
the payload of the message to be transmitted. Instead, the body of the message
points to the location of the payload file.
To exchange FileAct messages, XML version 2 with revision 2 or 3 is required.
For each message format, the communication media are file system directories. Alliance Access
can read or write a batch message file from or to a directory in a local or remote file system.
The File Transfer connection method supports the following message file data formats:



1 comment:

  1. Dear Guru,
    I want to implement FileAct using File Transfer as the connection method. Can you please share a white paper on how to do it in step by procedure? I mean, defining a Message Partner and any SWIFTNet Emission/Reception profile etc..
    Thanks.

    ReplyDelete