Return a ticket number (reference) in the MDN.
Per IBM online documentation, using the services related to EDIINT could return a reference number in the AS2 MDN. When we tried the implementation of the MDN we found that while some features are exposed, we cannot return the same version of the MDN and also cannot return in the location we need.
Additional discovery after a deep dive into it:
The MDN building service and the MIME encode BP allow adding an attachment to a message, but we don't know if it would work for an MDN or whether it would work since the AS2 version 1.1 does not support the same feature for multiple attachments in the MDN.
Our legacy platform uses AS2 1.2 version to put add a ticket (reference) number in the MDN in a mime attachment using AS2 header äóìEDIINT-Features: multiple-attachmentsäó.
AS2 version features exposed by B2Bi:
Sterling B2B says it supports AS2 version 1.2, but only supports the feature named "EDIINT-Features : AS2-Reliability".
Additional discovery after trying it out:
IBM support documents show how to return reference numbers in the MDN header but not in an attachment.
Notes from the MDN building service.
This service builds a Message Disposition Notification (MDN) based on information in process data and a specified contract ID. This enables you to perform additional custom operations between message parsing and MDN generation so that you can consider the outcome of those operations before generating the MDN.
When the EDIINT Pipeline service is configured to not build MDNs (the Build MDNs parameter is set to No), the EDIINT Pipeline service propagates MDN building information to business processes launched to extract data.
How to customize MDN references.
Requirement for version 1.2 header to use "EDIINT-Features" header.
Support for multiple attachment header EDIINT-Features: multiple-attachments.
Here is an example MDN. The MDN version/feature is different, and there is an added mime part for the reference number.
Date: Tue, 22 Aug 2017 18:25:02 GMT
Subject: Message Disposition Notification
Content-Description: MIME Message
MIME-Version: 1.0 (produced by the IP*Works! MIME Component)
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=md5; boundary="boundaryPsAwCw=="
Content-Type: multipart/report; report-type=disposition-notification; boundary="MDNBoundary"
Content-Type: text/plain; charset="iso-8859-1"
Content-Type: message/disposition-notification; charset="iso-8859-1"
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: T6MwCAeZVMzGC5WhPICEPQ==, md5
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
... signature data removed ...
Here is a Sterling generated MDN. Note that it has an extra text value in the report that cannot be altered. We cannot just replace it since this is a signed document.
Date: Wed, 30 Aug 2017 19:06:38 GMT
Subject: Signed Message Disposition Notification
Content-Type: multipart/report;Report-Type=disposition- notification;boundary="_=3789724742708672Sterling3789724742708672MOKO"
Your message was successfully received and processed.
... signature data removed ...