the purpose of the MDN tab is to configure where MDNs are sent to by the server when responding to your transmission, in case you want them sent to a different URL for a particular purpose.
The MDN sent back to you is a response to your communication, however it is not sent on the same connection.
When you send an AS2 message to a partner, the connection is closed once the message is sent. Your partner receives the message, and opens a separate connection to send you an MDN acknowledging that the message was received, or if there is some error condition.
In the case your partner sends you something, they will have some configuration setting identifying what URL to send MDNs to. That is not for you to worry about. The MDN URL (when you are sending an MDN to your partner) is specified in the HTTP request header. If you look at the raw message data, look at the HTTP header that looks like this
Note that this is the default for m-e-c AS2, and will vary depending on if you change the default, or if you use a different AS2 server.
As for the difference between sync vs async MDNs.....the whole concept of closing a connection is done regardless of sync or async MDNs, the ONLY difference is that with sync MDNs, the MDN is sent once the message is received, whereas with async MDNs, the MDN is sent anytime after the message was received (could be immediately after, could be a half hour after the msg was sent)
..the whole concept of closing a connection is done regardless..
On sync MDN the connection after sending a AS2 message is not closed, the receiver will not set up a new connection but answer on the same connection.
On async MDN the connection after sending a AS2 message is closed. The receiver extracts the URL where to send the MDN to from the AS2 message and establishes a new connection to this URL.
The advantage of using async MDN is lower server load and memory consumption on the receiver side.
broomd01 wrote:
What is the purpose of the MDN tab when doing syncronous exchanges? I thought the MDN is sent in the http response of the current communication.
You are right, if all of the trading partners are requesting sync MDN this information is useless.
the purpose of the MDN tab is to configure where MDNs are sent to by the server when responding to your transmission, in case you want them sent to a different URL for a particular purpose.
The MDN sent back to you is a response to your communication, however it is not sent on the same connection.
When you send an AS2 message to a partner, the connection is closed once the message is sent. Your partner receives the message, and opens a separate connection to send you an MDN acknowledging that the message was received, or if there is some error condition.
hope this helps
What about the case where my partner is sending me a document? Is it necessary to include an MDN URL to my partner?
I guess I'm confused about the difference between an async and a sync MDN.
I thought what you are describing (about closing the connection) was an async MDN, while the sync MDN is done within the same communication session.
Thanks for the help.
In the case your partner sends you something, they will have some configuration setting identifying what URL to send MDNs to. That is not for you to worry about. The MDN URL (when you are sending an MDN to your partner) is specified in the HTTP request header. If you look at the raw message data, look at the HTTP header that looks like this
disposition-notification-to = http://***your_url***:8080/mec_as2/HttpReceiver
Note that this is the default for m-e-c AS2, and will vary depending on if you change the default, or if you use a different AS2 server.
As for the difference between sync vs async MDNs.....the whole concept of closing a connection is done regardless of sync or async MDNs, the ONLY difference is that with sync MDNs, the MDN is sent once the message is received, whereas with async MDNs, the MDN is sent anytime after the message was received (could be immediately after, could be a half hour after the msg was sent)
hope this helps
..the whole concept of closing a connection is done regardless..
On sync MDN the connection after sending a AS2 message is not closed, the receiver will not set up a new connection but answer on the same connection.
On async MDN the connection after sending a AS2 message is closed. The receiver extracts the URL where to send the MDN to from the AS2 message and establishes a new connection to this URL.
The advantage of using async MDN is lower server load and memory consumption on the receiver side.
What is the purpose of the MDN tab when doing syncronous exchanges? I thought the MDN is sent in the http response of the current communication.
You are right, if all of the trading partners are requesting sync MDN this information is useless.
Regards
Heller
It seemed like the connection was being closed on a synchronous MDN. Sorry about that....