InterAct and FileAct Protocol

When you use the InterAct or FileAct protocol to transport messages to and from SWIFTNet, the SWIFTNet Server serves requests and receives messages to and from SWIFTNet, through a client application and a server application that communicate with the SWIFTNet network through the InterAct protocol. The SWIFTNet Server operates independently from the Sterling B2B Integrator.

The SWIFTNet Server Adapter or SWIFTNet7 Adapter is responsible for receiving request messages from SWIFTNet through the SWIFTNet Server and sending responses back. The SWIFTNet Server Adapter or SWIFTNet7 Adapter is comprised of two parts: the service part and the adapter part. The service part is used in a business process that does not require configuration except for enabling it for document tracking. The adapter part is configured through the Admin Console or the GPM, and this adapter is responsible for starting and stopping the SWIFTNet Server from Sterling B2B Integration using the Command Line Adapter 2 (CLA2), which is built into the SWIFTNet Server Adapter or SWIFTNet7 Adapter. A Command Line 2 client operates in remote installations (with the SWIFTNet Server) to enable Sterling B2B Integration to run a program from a command line in a business process.

The SWIFTNet Client service is responsible for sending SWIFTNet InterAct and FileAct messages (both requests and responses) to SWIFTNet, which are initiated by the Sterling B2B Integrator. The SWIFTNet Client service enables you to use InterAct and FileAct messaging with a store-and-forward option. The benefits of using store-and-forward include:

  • The sender and receiver do not need to be online at the same time, as is necessary for real-time messaging.
  • The sender is notified if a message cannot be delivered (and can optionally be notified when messages are delivered).

The SWIFTNet Client service enables you to use either synchronous or asynchronous messaging using InterAct and Put or Get mode in FileAct.

The SWIFTNet Routing Rule is used by the SWIFTNet Client or SWIFTNet7 Client service to route incoming request to a business process for processing. It uses four parameters:

  • RequesterDN
  • ResponderDN
  • Service name
  • Request type

These parameters are used to map an incoming request to a business process. The SWIFTNet Routing Rule page enables you to assign any business process to a set of routing parameters. You need to create a SWIFTNet routing rule and associate it with an appropriate business process to process incoming SWIFTNet requests.