Posts Tagged ‘AS2’

The AS2 Standard for EDI Over the Internet (EDIINT)

Monday, October 19th, 2009

Though I have concerns about AS2, it IS the B2B standard for exchanging electronic business documents over the internet using the popular http/https communications protocol. AS2 is more sophisticated than just plain HTTP or HTTPS because it defines extra standards such as HTTP protocol responses, and message format wrappers for EDI documents. AS2 can be used with non-EDI documents where non-EDI acknowledgments called Message Delivery Notifications (MDN) are used to acknowledge receipt of AS2 files.



AS2 Acronyms. EDI-INT AS2 is a mouthful of acronyms. EDI stands for Electronic Data Interchange (EDI). EDI-INT stands for EDI over the Internet which is a working group of the Internet Engineering Task Force (IETF). This group is charge with documenting the requirements and best practices for secure, interoperable EDI over the internet. AS2 stands for Application Statement 2 which is based on the Hypertext Transfer Protocol (HTTP) and HTTP Secure / Secure Socket Layer (HTTPS).

Why Use EDI-INT AS2? If two businesses desire to exchange electronic business documents directly, by by-passing traditional Value Added Networks (VAN), then they should use a secure, viable communications protocol. The biggest reason to implement EDI-INT AS2 is that the Internet Engineering Task Force (IETF) recommends it as the standard for HTTP/HTTPS data transfer. The IETF is the key International standards group for internet architecture and the smooth operations of the internet. The AS2 standard is recommended for its security and interoperability. At the same time, AS2 is a cumbersome protocol to implement.

Characteristics of EDI-INT AS2. The AS2 is the http-based standard for exchanging B2B documents over the internet. My concern with AS2 is whether a business or its trading partners have the technical know-how and resources to implement it and maintain it. Below are some characteristics of the AS2 standard.

  • Security and Verification. Increased verification and security achieved through the use of receipts and digital signatures.
  • Real-time Data Exchange. Transactions and acknowledgments occur in real-time. This can be a plus for transactional-based data exchange such as with financial authorizations and other real-time operations.
  • Exchange of Public and Private Keys. Public keys are used for encrypting each other’s EDI files, while the private key is used for decrypting.
  • Always Open Link. AS2 is a push-only protocol. It is not ad/hoc or push/pull as with a FTP-type communications protocols. With AS2, companies receive AS2 data by having a computer waiting for incoming http requests.
  • Cumbersome to Implement and Maintain. Because of the security, certifications and verifications, AS2 adds on layers of complexities that can overwhelm a technical staff in terms of know-how as well as labor to maintain the B2B interfaces.

More EDI-INT AS2 Links. Wikipedia AS2 | EDIdEv – Electronic Data Interchange Development | Secure File Transfer Protocols | EDI University – AS2.


Back to B2B Commerce Resources.

B2B – Confusion Over Data Formats and Protocols

Monday, September 14th, 2009

Business-to-Business (B2B) eCommerce terms such as EDI, XML, AS2, SFTP, and so on can get very confusing.

What is really needed for two businesses to exchange electronic documents between each other? Most business see the value of establishing a B2B eCommerce interface in order to transfer electronic documents. What is confusing is that there are several technical methodologies needed to establish a B2B eCommerce interface to transfer the electronic documents. First, there is the data standard to be used when formatting the data within the electronic document. Second, there is the communications method or protocol to transport the electronic document over data communications lines or the internet.



Data Standards. B2B eCommerce electronic documents can be electronically transferred using a variety of different data formats such as Electronic Data Interchange (EDI) X12, EDIFACT, or Extended Markup Language (XML). These formats define the data and layout so that the data within the electronic document can be easily integrated into dissimilar business systems.

Data Format Example. Take for example an electronic purchase order document. Depending on specificity, the data standard may define the purchase order field in such terms as field name, data type, field length, and allowable content.

The EDI Versus XML Debate There is a lot of debate in B2B eCommerce circles over the use of EDI Versus XML. Both will work, but in my opinion EDI / EDIFACT data standards are superior in supporting B2B eCommerce. This is because EDI has mature data specifications (XML is designed for minimum data specifications) and the file sizes of EDI documents are much smaller to transport over communications lines or the internet (i.e. XML is a bandwidth hog).

The Challenge of Universal B2B eCommerce Data Standards. B2B eCommerce data standards have come and gone. There are now many different and proprietary data standards. See posting, Will There Ever be an Universal Standard for Supply Chain Information Exchange? for more on the challenges and promises of universal B2B eCommerce data standards.

Communications Protocol. Electronic documents can be transferred over communications lines using a variety of different communications protocols. Now-a-days, more and more businesses are using the internet versus private communications lines to conduct B2B eCommerce. Additionally due to hackers and SOX-compliance, it is now becoming a necessity to encrypt most, if not all, electronic documents to protect them from unauthorized use. Common communications protocols for B2B eCommece include File Transfer Protocol (FTP), Secure FTP using SSH, FTPS (FTP over SSL), AS2 (HTTPS), Simple Mail Transfer Protocol (SMTP) / AS1, and so on.

Note: Many businesses are challenged by B2B eCommerce because there are so many EDI-type standards and so many proprietary integration applications that can support B2B eCommerce. They may all work, but which one and which one works with what? See posting, Is B2B eCommerce at a Crossroads?.

Back to B2B Commerce Resources.