handleSWIFTNetServerSnFRequest and handleSWIFTNet7InterActSnFRequest Business Processes

Edit online

The handleSWIFTNetServerSnFRequest or handleSWIFTNet7InterActSnFRequest business process enable the Sterling B2B Integrator to receive SWIFTNet store-and-forward messages. This is a bootstrap business process used by the inbound SWIFTNet request that includes a store-and-forward option. For Y Copy Services (regardless of InterAct or FileAct), an incoming request is not processed immediately, but instead is stored in the responder mailbox in the Sterling B2B Integrator to be responded to later. The Sterling B2B Integrator then sends an acknowledgement that the request has been successfully stored to the requestor through the SWIFTNet Server.

When a message is received, the message is parsed and then the routing rule will be evaluated.

  • If Action = Store to Mailbox, the Routing Rule calls the Add Mailbox service. If the mailbox does not exist, it will be automatically created.
  • If Action = Store to File System, the Routing Rule calls the File System Adapter. If the directory does not exist, it will be automatically created.
  • If Action = Invoke BP, the specified business process is invoked

Since the responder need to respond immediately, the system will (if necessary) retrieve the Response Template File. This file is the response payload. The Response Template File can be configured inside the Routing Rule as well. For Store and Forward, acknowledgment (positive or negative) will be sent.

Note: These business processes are used with InterAct processing only.

The handleSWIFTNetServerSnFRequest or handleSWIFTNet7InterActSnFRequest business process is initiated as part of the following inbound process flow:

  1. The SWIFTNet Server Adapter or SWIFTNet7 Adapter invokes the handleSWIFTNetServerSnFRequest or handleSWIFTNet7InterActSnFRequest business process and passes it all the necessary parameters to send a request.
  2. The handleSWIFTNetServerSnFRequest or handleSWIFTNet7InterActSnFRequest business process invokes the SOAP Inbound service.
  3. The SOAP Inbound service:
    • Pre-processes the incoming request
    • Searches the SWIFTNet Routing Rule table.
  4. The Mailbox Add service Routes the request payload to the responder mailbox to be responded to later.
  5. Then the SOAP Outbound service invokes the HTTP Response service.
  6. The HTTP Response service sends an acknowledgement to the requestor that the request has been successfully stored.