SWIFTNet Routing Rule

The SWIFTNet Routing Rule is used by the SWIFTNet Server adapter or SWIFTNet7 Adapter to manage interactive messages from the SWIFTNet MEFG Server, and enables you to configure how you want to process when you receive either an InterAct request payload or FileAct file that was transferred. The rule routes an incoming request message to a user-defined business process based on the following parameters:

  • requestorDN
  • responderDN
  • requestType
  • serviceName

You configure these four parameters and create the SWIFTNet routing rule through the SWIFTNet Routing Rule interface. The SWIFTNet Routing Rule page enables you to assign a routing method (any business process, mailbox, or file system directory) to a set of Requestor, Responder, Service, and Request Type. After a message is parsed, the routing rule or rules you have created are applied to the routing of SWIFTNet messages (Funds, MX, or generic XML format), and the server response messages are constructed and sent back to SWIFTNet through the SWIFTNet MEFG Server. The routing rule is evaluated after:

  • In case of InterAct, it is evaluated when a request is received.
  • In case of InterAct, it is evaluated when a request is received.
  • In case of FileAct Get, it is evaluated when the transfer is done on requestor side.

You can also use a wildcard (*) for these parameters. Using a wildcard, you can configure a generic routing rule that handles multiple messages from different requestors. Depending on which parameter you are configuring, the wildcard can be used at the beginning, middle, or end of the pattern. For the requestor DN or responder DN, it can be used at the beginning. For the request type it can be used at the end. Additionally you can set the priority of the routing rule to determine which rule supersedes another if there are two or more routing rules with different business processes that match an incoming request or file because you are using the wildcard feature.

Also, the priority function for the SWIFTNet routing rules necessitates that the Sterling B2B Integrator only allow one user to perform update on the priority at any particular time. So, when a user is creating, editing, deleting or importing a SWIFTNet routing rule, a lock will be created so that no other user is allowed to perform those operations.

Note: The wildcard must appear only once in routing criteria. For example: *,o=swift is allowed, but *,o=swift,* is not allowed because in the latter example the wildcard appears twice in the string.

You would want to use the wildcard function if, for example, the responder has 1,000 requestors that he or she might receive InterAct messages from, and would therefore need to configure 1,000 routing rules even though he or she intends to invoke the same business process for all the requestors. In this scenario, the user can create one SWIFTNet routing rule and use the wildcard feature to solve his or her business problem.

Note: If you are using CHIPS adapter with SWIFTNet as transport interface, the SWIFTNet Routing Rule will be automatically created for you.

You can also export and import SWIFTNet routing rules.

Note: Each time a user adds, modifies, or deletes a SWIFTNet routing rule, the action is logged to create an audit trail based on the user who performed the event.