Configuring Notifications for Messages in XML v2 Format

Edit online

Overview

Edit online

webMethods Module for SWIFT handles all levels of notification that SWIFT Alliance Access (SAA) sends in response to requests from webMethods Module for SWIFT:

  • Information notification: When SAA receives MT messages from webMethods Module for SWIFT, SAA validates the structure and the security signature of the message against SWIFT standards. If the message fails validation, SAA routes the message to a specific routing point and sends an information notification and message status to webMethods Module for SWIFT.
  • Transmission notification: SWIFT Central Services validates messages for FIN, InterAct, and FileAct services, and returns either a Positive (ACK) or Negative (NAK) acknowledgment. If SWIFT accepts the message, it returns ACK. If the message validation fails, SWIFT rejects the message and returns NAK. SAA maps these acknowledgments into transmission notifications and sends them to webMethods Module for SWIFT.
  • Delivery notification: When the message is delivered to the receiver, SWIFT Central Services sends a Delivery Notification (DeIN) acknowledgment. SAA maps DeIN into a delivery report or delivery notification and sends it to webMethods Module for SWIFT.

webMethods Module for SWIFT handles notifications using site-specific processing, configured through Trading Networks processing rules. webMethods Module for SWIFT provides you with the TN documents required to recognize the notification messages. Trading Networks saves incoming notifications and associates them with the original messages using the corresponding processing rule. You can see related messages by viewing the documents in Trading Networks.

Important: webMethods Module for SWIFT handles notifications only for messages exchanged over SAA in XML v2 format.

Configuring webMethods Module for SWIFT to Handle Notifications

Edit online

Step 1: Import Trading Networks Information for Notifications

Edit online

About this task

To enable webMethods Module for SWIFT to handle notifications received from SAA, import the following Trading Networks assets:

Trading Networks Asset Attribute Description
Processing Rules HandleDeliveryNotifications Processes delivery notifications from SAA and relates them to the original document using the 108: tag of the message.
Related SWIFT documents Reconciles all notifications from SAA and relates notifications to the original document using the SenderReference attribute.
Document Attributes Format Identifies the format of the message (MT, MX, or any XML type).
SenderReference Extracted from the outbound document (being sent to) SAA and uniquely identifies any document sent to SAA.
ReconciliationInfo Used to reconcile the MX Delivery Notification message to the corresponding Transmission report. (This attribute is extracted from the inbound Delivery Notification.)
Document Types DeliveryNotification Corresponds to the delivery notification sent by SWIFT to webMethods Module for SWIFT for successful delivery of a message to a counterparty.

To import Trading Networks information for handling notifications

  • Using the xmlv2TNItems.bin file located in the Integration Server_directory \packages\WmFIN \config\xmlv2\ directory, import Trading Networks assets using the instructions described in IBM webMethods Trading Networks Administrator’s Guide .

Step 2: Configure webMethods Module for SWIFT to Handle Notifications

Edit online

About this task

To configure webMethods Module for SWIFT to handle notifications

Procedure

  1. Configure routing rules in SAA using the Routing Application to send different notifications to specific end points (AFT or MQHA). For more information about configuring routing rules in SAA, see SWIFT Alliance Access Administration Guide.
  2. Configure the routing on SAA to send notifications to:
    • AFT - Create a new service to process notifications and submit them to Trading Networks for further processing, or modify the sample service wm.xmlv2:recieveFromAFT from the webMethods Module for SWIFT samples. For more information about the webMethods Module for SWIFT sample services, see webMethods SWIFT Module Samples Guide.
    • MQHA - Create a listener and notification for this connection:
      • Create a listener to wait for a notification document and a trigger that subscribes to the notification document. The notification document is published when a message is put into the MQHA queue by SAA.
      • Create a new service to handle notifications or modify the sample service, wm.xmlv2:receiveFromMQ. This service is called from the above trigger, which subscribes to the Notification document.

      Sample services for the connection, listener, notification, trigger, and receive services are available in the webMethods Module for SWIFT samples. For more information about the webMethods Module for SWIFT sample services, see webMethods SWIFT Module Samples Guide.

  3. Configure the connection details for SAA as described in:

Step 3: View Notifications and Related Messages

Edit online

About this task

You can view the different types of notifications and the messages to which they relate using the Trading Networks pages in My webMethods.

Search for the notification you want to view in Trading Networks by following the instructions described in IBM webMethods Trading Networks Administrator’s Guide .

Notification Details Displayed in the Transaction Details Panel

Edit online

In the Transaction Details panel there are several tabs that display information about the notifications. The following table describes the most important details for the different types of notifications that you can find on the Activity Log and Content tabs. For information about all tabs in the Transaction Details panel, see IBM webMethods Trading Networks Administrator’s Guide .

Tab Notification Details
Activity Log The Brief Message column contains the Document ID of the original message or TN document to which the notification or report is related:
Delivery Notification The TN document related to this notification, for example: 
Related to 53o6d600488qm9n8000004ov (Delivery 
Notification).
Delivery Report ID of the message related to this report, for example: 
Related to 53o6d600488qm65j000004nm (Delivery 
Report).
History Report ID of the message related to this report, for example: 
Related to 50k2ga0049dnll0r000000cs(History 
Report).
Transmission Report ID of the message related to this report, for example: 
Related to 50k2ga0049dnll0r000000cs 
(NetworkAcked).
Content Details displays the contents of the selected item:
Delivery Notification The delivery notification contents of the bizdoc, which is in either XML or MT format:
  • For xmlData—The Data PDU content in XML format. The body tag contains the MT or MX message data:
    • MT message—Base 64 encoded format.
    • MX message—The delivery information.
  • For finMsg—The MT content. The 108: tag in the decoded MT message contains the SenderReference of the original document, for example: 
    {175:1049}{106:090624PTSAUSA0AXXX0077000422}{1 
08:MT910586328}{175:1059}{107:090624PTSAUSA0AX 
XX0078000882}
Delivery Report The delivery report for the selected item:
  • For xmlData—The Data PDU in XML format.
  • For SAA—The SAA content. The 108: tag contains the SenderReference of the original document, for example: 
    {175:1049}{106:090624PTSAUSA0AXXX 
0077000419}{108:MT210244895}{175:1049}{107:090 
624PTSAUSA0AXXX0077000872}
History Report For xmlData, the actual Data PDU content of the history report in XML format.
Transmission Report The content of the transmission report:
  • For xmlData—The Data PDU in XML format.
  • For SAA—The SAA content. The 451: tag provides the processing status of the original document by SWIFT Network, for example: 
    {1:F21PTSAUSA0AXXX0090000441}{4:{177:09070811 
24}{451:0}{108:MT199704775}}

    The value of the tag in the example is 0, indicating that the original message has been successfully acknowledged by SWIFT Network.

For examples of the Data PDU content of the different types of notifications, see Examples of Data PDU Content of Documents.