AS2 Async MDN Egress Connector
Version: 17.01
Supported Since: 17.01
What is AS2 Async MDN Egress Connector?
According to the AS2 protocol upon the receipt of an AS2 Message it is required to send a Message Disposition Notifications (MDN) to the AS2 message sending party declaring the processing status of the AS2 message. With the AS2 message, the sending party should declare their preferred method of receiving the MDN. There are two methods,
-
Synchronous MDN (Request MDN with the HTTP response for the AS2 message)
-
Asynchronous MDN (Request MDN as a different HTTP request)
AS2 Async MDN Egress Connector can be used to send asynchronous MDNs when remote AS2 trading parties send AS2 messages requesting an asynchronous MDN. AS2 Async MDN Egress connector is compliant with the RFC 4130 written by Drummond & Moberg.
Sample Use Case
Prerequisite
In order to use the AS2 Async MDN Egress Connector you must first select the "AS2 Connector" dependency from the connector list when you are creating an empty Ultra project. If you have already created a project, you can add the "AS2 Connector" dependency via Component Registry. From Tools menu, select Ultra Studio → Component Registry and from the Connectors list, select the "AS2 Connector" dependency.
1. Confirming the receipt of an invoice over AS2
To utilize the AS2 Async MDN Egress Connector there should be a established AS2 connectivity between you and your remote AS2 trading partner.
This is a simple scenario simulating the use case of sending an async MDN upon the receipt of an AS2 message containing a invoice document from a remote AS2 partner. Here it is assumed that the remote AS2 trading partner will always request for an async MDN responses. Here the received invoice file will be store into a local directory and send an Message Disposition Notification (MDN) to the trading partner. The MDN is the response to the trading partner which contains the processing status of the received AS2 message.
For the above scenario it is required to have three 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 third element is a Attachment Saver element which is responsible for saving the invoice file into a user defined local directory. Third element is the AS2 Async MDN Egress Connector element that will prepare and send the MDN in a new HTTP request.
In-order to understand the functionality of AS2 Ingress Connector element and Attachment Saver element please refer to their reference resources.
In Ports
Input |
The message comes through this port will contain the required information to prepare the async MDN message. |
Side Ports
Connector Operation |
This port is used to connect operational elements to the Egress Connector. By-default, user does not have to connect any operational element and the default connector operation will be used. However if there are any specific operations to be done user can utilize the connector operation. |
Out Ports
On Exception |
The message will be sent to this outport if the processing element failed to prepare the async MDN message using the provided information due to some reason |
Response Processor |
The response message received for the async MDN HTTP message will be directed to this port. You can use this port to connect any precessing element or connector that is supposed to consume the response. |
Parameters
* marked fields are mandatory
The AS2 Async MDN Egress Connector uses the HTTP as the underlying transport protocol which makes it inherit the properties of HTTP Egress Connector. Therefore it is possible to view and customize those HTTP transport specific properties defined under the Transport Configuration category and Sender Configuration category. To understand them please refer to NIO HTTP Egress Connector reference.
Egress Timeout |
Advanced |
Timeout value in milliseconds for the egress message |
Weight |
Advanced |
Weight for the Egress Connector if Egress Load Balancer element is used with Weighted/Weighted with Failover algorithm is used |
In this topic
In this topic