Version: 17.07
Supported Since: 17.01
AS2 MDN Creator is a processing element that is being used in AS2 message flows. When a AS2 trading partner sends a message they requests a Message Disposition Notification (MDN) response for it. The MDN is the response to the trading partner which contains the processing status of the received AS2 message. The MDN can be sent as the response to the received AS2 message (synchronous MDN) or else it will be sent as a new AS2 message (asynchronous MDN) to the trading partner. It will be decided on the preference of the trading partner they will be denote in the receiving AS2 message. AS2 MDN Creator is there to recognize the requested method of MDN and forward the message to the relevant outport to send the MDN.
This is a simple scenario which is simulating the use case of receiving an invoice document from a remote partner over AS2 protocol and sending the response MDN. Here the received invoice file will be store into a local directory and send a Message Disposition Notification (MDN) to the trading partner.
For the above scenario it is required to have four elements for the AS2 message flow configuration of the UltraESB. The first element is a AS2 Ingress Connector which is responsible for receiving the AS2 message, parsing it to extract the invoice file, set the extracted invoice as a attachment of the message and finally preparing the response for the message and add it as the response message payload. The second element is a Attachment Saver element which is responsible for saving the invoice file into a user defined local directory. The third element is a AS2 MDN Creator which will evaluate requested format of MDN. If the remote trading party has requested a synchronous MDN then it will invoke the response message which will contain the MDN message through its Sync MDN Requested out port. If the remote trading party has requested for a asynchronous MDN then the AS2 MDN Creator will forward the response message to the final element of the flow, which is an AS2 Async MDN Sender. It will prepare and send the MDN in a new HTTP request.
In-order to understand the functionality of AS2 Ingress Connector element, Attachment Saver element and the AS2 Async MDN Egress Connector element please refer to their reference resources.
For this sample use case, configuration of the AS2 Ingress Connector is as follows.
For this sample use case, configuration of the Attachment Saver element is as follows.
For the AS2 Async MDN Egress Connector there are HTTP transport specific properties to be configuration. If required you can customize their default values.
Async MDN Requested |
The message will be sent to this outport the trading partner has requested a asynchronous MDN for the AS2 message |
Sync MDN Requested |
The message will be sent to this outport the trading partner has requested a synchronous MDN for the AS2 message |
On Exception |
The message will be sent to this outport if the processing element failed while processing the received AS2 message |