Configure the SWIFTNet7 Client Service

About this task

To configure the SWIFTNet7 Adapter:

Procedure

  1. Select Deployment > Services > Configuration.
  2. Search for SWIFTNet7 Client service or select it from the list and click Go!.
  3. Click Edit.
  4. Specify field settings in the Admin Console.
    Note: Each instance of the SWIFTNet7 Client service is configured for a pair of requestor/responder DNs and the SWIFTNet7 Client service name.

    Use the field definitions in the following table to create a new configuration of the SWIFTNet7 Client service.

    Name
    Unique and meaningful name for the service configuration. Required.
    Description
    Meaningful description for the service configuration, for reference purposes. Required.
    Select a Group
    Select one of the options:
    • None – Do not include the configuration in a service group at this time.
    • Create New Group – Enter a unique name for a new group, which will be created with this configuration. (You can then add other services to the group as well.)
    • Select Group – If service groups already exist for this service type, they are displayed in the list. Select a group from the list.
    Store and Forward
    Indicates if the file transfer is done using the store-and-forward method. Valid values are True (use Store-and-Forward) and False (default—do not use Store-and-Forward). Required. BPML element value is SnF.
    SWIFTNet Operation
    The SWIFTNet operation to send an InterAct or FileAct message. Possible values are:
    • Synchronous (default)—InterAct
    • Asynchronous—InterAct
    • Put—FileAct
    • Get—FileAct
    Required. When SWIFTNet Operation is FileAct, you must select either Put or Get. If you do not select an operation, the service uses Synchronous as the default value. BPML element value is sync (default) or async for InterAct, or Put or Get for FileAct.
    Requestor DN
    Distinguished name of the requestor. Required. BPML element value is requestorDN. This DN must be registered with the SAG instance using SWIFTNet Alliance Webstation.
    Responder DN
    Distinguished name of the responder. Required. BPML element value is responderDN. Note: This DN must be registered with the SAG instance using SWIFTNet Alliance Webstation.
    Service Name
    Name of the service to which both SWIFT correspondents have subscribed. Required. BPML element value is serviceName. This must be a SWIFTNet service to which you are subscribed.
    Authoriser DN
    The distinguished name of the authorizing party. Optional.
    This service allows Third Party Copy
    Whether this service uses T-Copy or Y-Copy (check your service agreement with SWIFT). BPML element value is thirdPartyCopy. Valid values are TRUE or FALSE. This parameter is displayed only if you selected File Act and True for Store and Forward on SWIFTNet7 Client service Interface page.
    Note: If the Copy Mode is Y-Copy, Sterling B2B Integration sends an authorization message, which is like sending an Interact store-and-forward request. The SWIFTNet7 Client service is used, but you must set the This service allows Third Party Copy parameter to TRUE, and provide the authorization decision (either Authorised or Refused) for the AuthDecision parameter.
    Request for Third Party Copy
    Whether you are requesting third party copy. When the Copy feature is defined as Optional in the service agreement, you can choose whether you want the Third Party Copy to occur. BPML element value is copyIndicator. Valid values are TRUE or FALSE. Displayed only if you select True for This service allows Third Party Copy. This parameter is displayed only if you selected True for This service allows Third Party Copy.
    Request for Notification from Third Party
    In T-Copy mode, this setting is not applicable, the value should always be set to FALSE.
    In Y-Copy mode, when the Authorisation Notification Indicator feature is available and defined as Optional in the service agreement, you can choose whether you want to receive the Authorisation Notification messages. BPML element value is authNotifIndicator. Valid values are TRUE or FALSE. Displayed only if you selected True for This service allows Third Party Copy. This parameter is displayed only if you selected True for This service allows Third Party Copy.
    Request Type
    Request type supported by the message exchange. Optional for InterAct and required for FileAct in SWIFTNet 6.0. BPML element value is requestType. Note: In SWIFTNet 6.0 FileAct the format convention is as follows:
    <business_area>.<type_of_syntax>.<detailed_syntax_and_format>
    This format starts with a four-characters business area code, followed by a period (dot), followed by a three-character code that designates the type of syntax (which can be <nnn>, FIN, or xxx), followed by another period (dot), and then followed by a more detailed indication of syntax and format.
    Request Reference
    User reference of the request. Optional. BPML element value is requestReference.
    Non Repudiation Required
    Indicates whether non-repudiation is required. Possible values are True (when enabled this means that trading partners cannot deny that they sent a request) or False (default—when enabled this indicates that non-repudiation is not required). Optional. BPML element value is nonRepudiation.
    Switch to SnF mode when real-time transmission failed
    Indicates whether you want to switch to store-and-forward mode if a real-time transmission (InterAct or a FileAct Put) has failed. Possible values are True or False (default). Required. BPML element value is switchToSnF.
    Store and Forward Service Name
    The name of the store-and-forward service. Required when Switch to SnF mode when real-time transmission failed is set to True. BPML element value is SnFServiceName.
    End-to-End Signature Required
    Whether an end-to-end signature is required. Valid values are False (default) and True. Optional. You can use an end-to-end signature regardless of whether you are using non-repudiation (for example, for SWIFT SCORE messages).
    Number of Retries
    Number of retries to connect to SAG. Default value is 3. Optional. BPML element value is numOfRetries.
    Retry Delay (in seconds)
    Time that will elapse before the next retry. Default value is 60 (seconds). Optional. BPML element value is secInRetryDelay.
    Trace
    Trace for logging purposes in the SWIFTNet Server. Valid values are True and False (default). Required. BPML element value is trace.
    Use Signature List
    Whether to use a signature list. This enables you to select your own signatures. If you do not use a signature list then normal Crypto is used. Valid values are False and True. Required. This parameter is displayed only if you selected True for End-to-End Signature Required.
    Return Signature List
    Whether to return a signature list. Valid values are False and True. Required. If you want a signature list returned, the SWIFTNet Server receives the requestor's own signature in the response message. This returned signature will be extracted and saved as a separate message. This message is stored in the database and is made available for Correlation search. This parameter is displayed only if you selected True for End-to-End Signature Required.
    Use RND
    Whether to use RND (digest reference values that terminate on “and RND”). Valid values are False (default) and True. Required. This parameter is displayed only if you selected True for End-to-End Signature Required.
    Delivery Notification (Del. Notifn)
    Indicates that the sender asked the receiver to send a delivery notification. Possible values are True or False (default). Optional. BPML element value is deliveryNotification.
    Note: This parameter is only displayed when you select True for Store and Forward or are performing a FileAct Put. If you are performing a Put operation, you can request the responder to send you a delivery notification and specify a different Delivery Notification DN and Request Type of Delivery Notification, if desired. If you are performing a Get operation, the responder can request Delivery Notification from the requestor after receiving the file. That setting for delivery notification is configured through the SWIFTNet7 Adapter.
    Request Type of Delivery Notification
    Used to request a specific delivery notification message from the remote receiving server application when it returns the delivery notification (when Delivery Notification is set to True). Optional. BPML element value is requestTypeDelNotifn. This parameter is only displayed when you select True for Store and Forward or a FileAct Put.
    Message Priority
    Indicates priority handling in the queue for store-and-forward only. Valid values are Normal (default) and Urgent. Optional. BPML element value is messagePriority. This value is used as a selection criterion when delivering messages from a queue, and in SWIFTNet FileAct to influence the pace of the FileAct flow.
    Use Input Channel
    Whether to use the input channel. Valid values are False (default) and True. Required. This parameter is displayed only if you selected True for Store and Forward and InterAct for SWIFTNet interface.
    Note: Used for InterAct store-and-forward only. Select True if you are using an input channel. If you configure this parameter, the SWIFTNet Server opens the Input Channel automatically during the startup (when the SWIFTNet7 Adapter is enabled). This Input Channel remains open until the SWIFTNet Server is shut down (or the SWIFTNet7 Adapter is disabled). During this time, you still have an option to send message using the input channel or without the input channel. All you need to do is to indicate this by using this parameter in SWIFTNet7 Client service.
    MEFG SWIFTNet IP
    The IP address for the SWIFTNet Server. Required.
    MEFG SWIFTNet Port
    The port for the SWIFTNet Server. Default is NULL. Optional.
    Response Timeout
    The timeout interval (in seconds) in which a response must be received or the message operation fails. Optional. Default is 60 seconds.
    Use SSL
    Whether to enable Secure Socket Layer (SSL) over HTTP communication between Sterling B2B Integration and the SWIFTNet Servers. Valid values are None and Must. Note: Regardless of the value you select for Use SSL, you must also update the business processes associated with the SWIFTNet Client service.
    Cipher Strength
    Indicates the strength of the cipher. Possible values are ALL (default), WEAK, and STRONG. Optional.
    CA Certificate
    The CA certificate of the SWIFTNet Server.
    Note: This is the public key certificate that must be configured to set up the outbound SSL channel. This page is only displayed if you set Use SSL to Must.
    Note: The SWIFTNet7 Client service Configuration page allows you to select the same CA Certificate for SSL processing a second time, and continues to allow additional selections of the same certificate in subsequent edits. If you have already selected a CA Certificate once for a configuration of the SWIFTNet7 Client service, do not select the same CA Certificate again, as this will result in an error when you execute the relevant business process.
    Switch to SnF mode when real-time transmission failed
    Whether to switch to store-and-forward mode when real-time transmission fails. Select True if you want to switch to Store and Forward mode when the real-time transmission (InterAct and FileAct Put) has failed. Valid values are True and False.
    Physical Filename
    Physical name of the file to send. Required if put or get is selected for the SWIFTNet Operation. BPML element value is physicalFilename.
    Logical Filename
    Logical name of the file to send. This name is communicated to the SWIFTNet Server. By default, this name is the Physical Filename without the path. Optional. BPML element value is logicalFilename.
    File Information
    User information about the file transfer. Optional. BPML element value is fileInfo.
    File Description
    User description about the file transfer. Optional. BPML element value is fileDesc.
    SWIFTNet Interface
    SWIFTNet message type. Valid values are InterAct or FileAct. Required.
  5. On the Confirm page, verify that the Enable Service for Business Processes check box is selected to enable the service instance.