handleSWIFTNetServerRequest and handleSWIFTNet7InterActRequest Business Processes

Edit online

The handleSWIFTNetServerRequest business process (handleSWIFTNet7InterActRequest business process for SWIFTNet7) enable the Sterling B2B Integrator to receive SWIFTNet messages. This is the bootstrap business process used by the inbound SWIFTNet request through the SWIFTNet Server. It is a system business process used by the SWIFTNet Server Adapter or SWIFTNet7 Adapter, which pre-processes the incoming request, search the SWIFTNet Routing Rule table, executes the matching routing rule, and route the request payload to the business process for processing.

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

The handleSWIFTNetServerRequest or handleSWIFTNet7InterActRequest business process is initiated as part of the following inbound process flow:

  1. The SWIFTNet Server Adapter or SWIFTNet7 Adapter invokes the handleSWIFTNetServerRequest or handleSWIFTNet7InterActRequest business process and passes it all the necessary parameters to send a request.
  2. The handleSWIFTNetServerRequest or handleSWIFTNet7InterActRequest business process invokes the SOAP Inbound service.
  3. The SOAP Inbound service:
    • Pre-processes the incoming request.
    • Searches the SWIFTNet Routing Rule table.
    • Routes the request payload to the business process for processing.
  4. 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.
  5. The business process also evaluates the routing rule and since the responder need to respond immediately, the system will (if necessary) retrieve the Response Template File. This file becomes the response payload. The Response Template File can be configured inside the Routing Rule as well.
  6. Then the SOAP Outbound service invokes the HTTP Response service.
  7. The HTTP Response service sends a response to the request.