Create a SWIFTNet Routing Rule

Edit online

About this task

To create a SWIFTNet routing rule and select the routing method to process incoming SWIFTNet requests:

Procedure

  1. Create a business process to which the inbound messages will be routed by the SWIFTNet Server Adapter or SWIFTNet7 Adapter.
  2. From the Sterling B2B Integrator Deployment menu, select Adapter Utilities > SWIFTNet Routing Rule.
  3. To the right of Create new SWIFTNet routing rule, click Go!.
  4. Complete the following parameters and click Next:
    Parameter
    Description
    SWIFTNet Routing Rule Name
    Type the name of the SWIFTNet routing rule. Required.
    Note: Special characters such as ! @ # % ^ ( ) + ? , < > { } [ ] | ; " ' / are not permitted.
    Requestor DN
    Type the distinguished name of the requestor or use a wildcard (*) in the string. Required.
    Note: If you use a wildcard in the string for this value, SWIFTNet specifies that a valid DN always ends with o=swift, so the wildcard character is only allowed at the beginning of the string. For example, *,o=abcd,o=swift is allowed, but o=abcd,*,o=swift is not allowed.
    Note: This value should be taken from the Requestor's SWIFTNet Client service configuration (or from the BPML parameters passed to the service), in accordance with the arrangement made between requestor and responder.
    Responder DN
    Type the distinguished name of the responder or use a wildcard (*) in the string. Required.
    Note: If you use a wildcard in the string for this value, SWIFTNet specifies that a valid DN always ends with o=swift, so the wildcard character is only allowed at the beginning of the string. For example, *,o=abcd,o=swift is allowed, but o=abcd,*,o=swift is not allowed.
    Note: This value should be taken from the Requestor's SWIFTNet Client service configuration (or from the BPML parameters passed to the service), in accordance with the arrangement made between requestor and responder.
    Service Name
    Type the name of the SWIFTNet Client service instance configuration that you created in step 1 or use a wildcard (*) in the string. Required.
    Note: This value should be taken from the Requestor's SWIFTNet Client service configuration (or from the BPML parameters passed to the service), in accordance with the arrangement made between requestor and responder.
    Request Type
    Type the request type (message type and name) supported by the file transfer responder or use a wildcard (*) in the string. Optional.
    Note: If you use a wildcard, it must appear at the end of the string. The SWIFT Request Type generally specifies the category first (for example, pain.001.01.01). Therefore, pain.* is allowed but *.001.01 is not allowed.
    Note: This value should be taken from the Requestor's SWIFTNet Client service configuration (or from the BPML parameters passed to the service), in accordance with the arrangement made between requestor and responder.
    Translation Code

    A routing rule parameter sent by SWIFT in the SWIFTNet SnF InterAct MultiPart messages, in the TranslationResult XML comment. It is not used by any other message. Optional.

    For comment, <!-- TranslationResult=TRNR -->, the Translation Code is TRNR.

    Note: Support for multipart (MT/MX) messages:

    The Multipart (MT/MX) message is a new SWIFTNet SnF InterAct Request sent by SWIFT for prior FIN Message in the new ISO 20022 format. The MT is the old FIN format. The MX is the new ISO 20022 format.​

  5. Complete the following parameter and click Next:
    Assign Priority for this Routing Rule (relative to other match rules)
    Enables you to assign priority to the routing rule, if the routing parameters using the wildcard are matched to an existing routing rule. This resolves the issue that occurs when you are using wildcards and an incoming request corresponds to two existing routing rules. In this case, the rule with higher priority will be invoked. Optional.
    Note: If no other rules match the routing parameters used for this rule, the priority will be assigned automatically.
  6. Complete the following parameters and click Next:
    Invoke Business Process
    This is the default selection, indicating that messages will be routed based on a selected business process.
    Business Process
    Select the business process that will be invoked to manage the request and handle the response to a SWIFTNet message (this is the business process that you created in step 2 that will be called when the requestor DN, responder DN, service name, and requestor type match). Required if you select Invoke Business Process.
    Invoke Mode
    Whether the mode of invocation is synchronous (default) or asynchronous. Required if you select Invoke Business Process.
    Store into Mailbox
    Indicates that messages will be routed to a selected mailbox.
    Note:
    If you utilize this option, the routing rule calls the Add Mailbox service and if the mailbox does not exist, it will be automatically created.
    Filter by Name
    Use to filter mailboxes by name to narrow your selection criteria. Only accessible if you select Store into Mailbox.
    Parent Mailbox
    Select the Parent Mailbox into which messages will be routed. Required if you select Store into Mailbox.
    Note: In the Parent Mailbox list, you are not able to pick any mailbox that contains a SWIFT DN (for example, /o=ptscfrnn,o=swift, etc.). Therefore, those DNs are not displayed in the list.
    Store into File System
    Indicates that messages will be routed to the specified directory in your file system
    Note: If you utilize this option, the routing rule calls the File System Adapter and if the directory you specify does not exist, it will be automatically created.
    Root Directory
    The directory into which messages will be routed. Required if you select Store into File System.
    Please specify an XML file that serve as a default response payload whenever appropriate.
    Type the response template that serves as the default response payload.
    Note: This response template is only applicable for Interact Real-time (which requires that a response be sent back immediately) when the action you selected is asynchronous (one-way). The response template is also required, if Action is set as mailbox or file system (in which case the response payload will be taken from response template file).
    Note: The Sterling B2B Integrator attempts to locate any other routing rule defined in the system that matches with your routing rule. You can specify the priority of your rule in relation to those matches rules.
  7. Click Finish to save the routing rule. The rule is now in effect for all incoming SWIFTNet messages (Funds, MX, or generic XML format).