IBM Support

Problem with sending MDN after processing the AS2 inbound message.

Troubleshooting


Problem

Problem with sending MDN after processing the AS2 inbound message.

Symptom

GIS is trying to send both SYNC MDN and ASYNC MDN after processing the AS2 message received from the trading partner. After processing the message the HTTPSyncSend BP is trying to send an plain text MDN. After that GIS is trying to send a ASYNC MDN through HTTPAsyncSend BP. But the ASYNC MDN send is failing.

BPs invoked by GIS after processing the received AS2 message.

1. EDIINTParse
2. HTTPAsyncSend
3. HTTPSyncSend

The EDIINTParse BP has the following information:

    Host:<IP address>:<Port>
    User-Agent:GIS/PsHttpClientAdapter
    AS2-Version:1.1
    AS2-To:as2_Receiver
    AS2-From:as2_Sender
    Date:Mon, 16 Feb 2009 10:33:29 GMT
    Subject:Integrator Message
    Message-ID:<>
    Disposition-Notification-To:as2_org_43000
    Receipt-Delivery-Option: http://www.example.com/Path
    Content-Type:application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
    Content-Length:3654
    URI:/as2

HTTPSyncSend BP has the following information:
    status-code: 200
    Content-Type: text/html

    <html>
    Got your data
    </html>

HTTPAsyncSend BP has the following information:
    AS2-To: as2_Receiver
    AS2-From: as2_Sender
    AS2-Version: 1.1
    Subject: Message Disposition Notification
    Date: Mon, 16 Feb 2009 10:33:57 GMT
    Message-ID: <>
    Content-Type: multipart/report;Report-Type=disposition-notification;boundary="_=93036554056187 63Sterling9303655405618763MOKO"


    --_=9303655405618763Sterling9303655405618763MOKO

    Your message was successfully received and processed.

    --_=9303655405618763Sterling9303655405618763MOKO
    Content-Type: message/disposition-notification

    Original-Recipient: rfc822;as2_Sender
    Final-Recipient: rfc822;as2_Sender
    Original-Message-ID: <>
    Disposition: Automatic-action/mdn-sent-automatically;processed

    --_=9303655405618763Sterling9303655405618763MOKO--

Resolving The Problem

If the AS2 message header contains Receipt-Delivery-Option followed by a url in the inbound request as shown below, it shows that the trading partner is requesting for the ASYNC MDN.

Receipt-Delivery-Option: http://www.example.com/Path

If the above header is present, GIS will send an asynchronous MDN in a different HTTP communication session to the URL as mentioned in the option. Trading partner must ensure that their firewall rules allow this communication.

Note: In this case the response sent by the HTTPSyncSend is just simple a HTTP Response for the HTTP communication while receiving AS2 message This is not the MDN. The actual MDN will be send by the HTTPAsyncSend BP in different communication session.

[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

NFX5080

Document Information

Modified date:
08 November 2019

UID

swg21556654

Page Feedback