INTRODUCTION TO AS2
A common transport used for EDI is Value-Added Networks (VANs)
The most common way of implementing EDI over the Internet (EDIINT) is by AS2 (Applicability Statement 2). The AS2 specification defines MIME-based secure peer-to-peer business data interchange. Messages containing an envelope with MIME data are transmitted using HTTP over TCP/IP.
After transmitting an EDI message to a trading partner, we usually want to confirm whether the message - in all its entirety - actually went through. More so if our EDI (Electronic Data Interchange) is carried out over the Internet, where message packets may have to go through a number of hops. This concern can be easily addressed if you do your EDI over AS2. That's because AS2 provides an electronic return receipt known as an MDN (Message Disposition Notification).
AS2 requires that the HTTP adapter is used on both the receive-side and the send-side.
The BizTalk EDI Application that contains artifacts (including pipelines and schemas) that are needed to process AS2 documents.
Whenever you create an application that will process AS2 messages, you must add a reference to the BizTalk EDI Application from your application
--
Pipeline components related to AS2 process.
AS2EdiReceive
AS2Receive
AS2EdiSend
AS2Send
The AS2EdiReceive pipeline that performs AS2 processing, and then EDI processing, of an EDI message received over AS2. For more information, see AS2 Receive Components.
The AS2Receive pipeline that performs AS2 processing of a non-EDI message received over AS2. For more information, see AS2 Receive Components.
The AS2EdiSend pipeline that performs EDI processing, and then AS2 processing, of an EDI message being sent over AS2. For more information, see AS2 Send Components.
The AS2Send pipeline that performs AS2 processing of a non-EDI message being sent over AS2. For more information, see AS2 Send Components.
References:
https://msdn.microsoft.com/en-us/library/bb259978.aspx
Architecture
https://msdn.microsoft.com/en-us/library/bb246059.aspx
AS2 MESSAGE
https://msdn.microsoft.com/en-us/library/bb245990.aspx
MDN
http://www.jscape.com/blog/bid/100671/What-is-an-AS2-MDN
MIME
http://www.rfc-editor.org/rfc/rfc4130.txt
A common transport used for EDI is Value-Added Networks (VANs)
The most common way of implementing EDI over the Internet (EDIINT) is by AS2 (Applicability Statement 2). The AS2 specification defines MIME-based secure peer-to-peer business data interchange. Messages containing an envelope with MIME data are transmitted using HTTP over TCP/IP.
After transmitting an EDI message to a trading partner, we usually want to confirm whether the message - in all its entirety - actually went through. More so if our EDI (Electronic Data Interchange) is carried out over the Internet, where message packets may have to go through a number of hops. This concern can be easily addressed if you do your EDI over AS2. That's because AS2 provides an electronic return receipt known as an MDN (Message Disposition Notification).
AS2 requires that the HTTP adapter is used on both the receive-side and the send-side.
The BizTalk EDI Application that contains artifacts (including pipelines and schemas) that are needed to process AS2 documents.
Whenever you create an application that will process AS2 messages, you must add a reference to the BizTalk EDI Application from your application
--
Pipeline components related to AS2 process.
AS2EdiReceive
AS2Receive
AS2EdiSend
AS2Send
The AS2EdiReceive pipeline that performs AS2 processing, and then EDI processing, of an EDI message received over AS2. For more information, see AS2 Receive Components.
The AS2Receive pipeline that performs AS2 processing of a non-EDI message received over AS2. For more information, see AS2 Receive Components.
The AS2EdiSend pipeline that performs EDI processing, and then AS2 processing, of an EDI message being sent over AS2. For more information, see AS2 Send Components.
The AS2Send pipeline that performs AS2 processing of a non-EDI message being sent over AS2. For more information, see AS2 Send Components.
References:
https://msdn.microsoft.com/en-us/library/bb259978.aspx
Architecture
https://msdn.microsoft.com/en-us/library/bb246059.aspx
AS2 MESSAGE
https://msdn.microsoft.com/en-us/library/bb245990.aspx
MDN
http://www.jscape.com/blog/bid/100671/What-is-an-AS2-MDN
MIME
http://www.rfc-editor.org/rfc/rfc4130.txt
No comments:
Post a Comment