Watson Supply Chain Ideas

Use this form to submit an idea for a new product feature. The product team will review your input and provide status updates as decisions are made regarding the request.

Before you submit a new idea, please view requests that have already been submitted. If your idea has already been submitted, you can add comments or vote on the existing idea, thereby indicating your agreement with the idea. We may use this information to help prioritize development of new features.

 

Submit ideas for Watson Marketing and Watson Commerce products

Ability to send references in AS2 MDN attachments

Objective:

Return a ticket number (reference) in the MDN.



Initial discovery:

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.
Other References.

How to customize MDN references.


http://www-01.ibm.com/support/docview.wss?uid=swg21995744



Requirement for version 1.2 header to use "EDIINT-Features" header.

https://www.rfc-editor.org/rfc/rfc6017.txt



Support for multiple attachment header EDIINT-Features: multiple-attachments.

https://tools.ietf.org/html/rfc6362



Here is an example MDN. The MDN version/feature is different, and there is an added mime part for the reference number.



---BEGIN RESPONSE---

AS2-From: SENDER

AS2-To: RCV_AS2Identifier

AS2-Version: 1.2

EDIINT-Features: multiple-attachments

Date: Tue, 22 Aug 2017 18:25:02 GMT

Subject: Message Disposition Notification

Content-Description: MIME Message

Message-ID: ????7110-eb1d-4b26-8553-b1ef2f?????b@RCV_AS2Identifier

MIME-Version: 1.0 (produced by the IP*Works! MIME Component)

Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=md5; boundary="boundaryPsAwCw=="





--boundaryPsAwCw==

Content-Type: multipart/report; report-type=disposition-notification; boundary="MDNBoundary"





--MDNBoundary

Content-Type: text/plain; charset="iso-8859-1"



D7RXRIG9

--MDNBoundary

Content-Type: message/disposition-notification; charset="iso-8859-1"



Original-Recipient: rfc822;RECEIVER

Final-Recipient: rfc822;RECEIVER

Original-Message-ID: ????#????426283680#@RCV_AS2Identifier>

Disposition: automatic-action/MDN-sent-automatically; processed

Received-Content-MIC: T6MwCAeZVMzGC5WhPICEPQ==, md5



--MDNBoundary--



--boundaryPsAwCw==

Content-Type: application/pkcs7-signature; name="smime.p7s"

Content-Disposition: attachment; filename="smime.p7s"

Content-Transfer-Encoding: base64



... signature data removed ...



--boundaryPsAwCw==--



---END RESPONSE---




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.



AS2-To: TSTRCV

AS2-From: AS2TEST

AS2-Version: 1.1

Date: Wed, 30 Aug 2017 19:06:38 GMT

Message-ID:

Subject: Signed Message Disposition Notification

Content-Type: multipart/signed;protocol="application/pkcs7-signature";micalg=md5;boundary="_=5685884875464102Sterling5685884875464102MOKO"



--_=5685884875464102Sterling5685884875464102MOKO

Content-Type: multipart/report;Report-Type=disposition- notification;boundary="_=3789724742708672Sterling3789724742708672MOKO"

--_=3789724742708672Sterling3789724742708672MOKO

Your message was successfully received and processed.

--_=3789724742708672Sterling3789724742708672MOKO
Content-Type: message/disposition-notification

Original-Recipient: rfc822;AS2TEST
Final-Recipient: rfc822;AS2TEST
Original-Message-ID:
Received-Content-MIC: sHovIf4/8w8tMBBfe5Gs+g==,MD5
Disposition: Automatic-action/mdn-sent-automatically;processed

--_=3789724742708672Sterling3789724742708672MOKO--

--_=5685884875464102Sterling5685884875464102MOKO
Content-Type: Application/pkcs7-signature;name=EDIINTSIG.p7s

... signature data removed ...

--_=5685884875464102Sterling5685884875464102MOKO--
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 19 2017
What is your industry? Banking
What is the idea priority? Medium
DeveloperWorks ID DW_ID110625
RTC ID RTC_ID551608
Link to original RFE http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=110625
  • Attach files