Monday, March 2, 2009


EDIINT AS2 is a very popular B2B protocol. Apart from file transfer, I think this is currently the most popular B2B protocol. Although EDIINT was initially meant to replace EDI over VAN connections by EDI over the INTernet (EDIINT), the AS2 protocol can transport any data in an asynchronous manner.

AS2 provides:
  • Firewall friendly as it uses HTTP(S) underneath
  • Straightforward: adds a number of HTTP header fields and MIME based message structure
  • Reliable: send message until you get a 200, duplicates are filtered based on message-id
  • Signing: based on S/MIME message structure and PKCS7 signing (self signed certificates are often used in practice)
  • Encyption: also leveraging the S/MIME message structure
  • Non-repudiation: signed acknowledgement or message receipt, called the Message Disposition Notification
  • Any payload: EDI, XML, binary, text
  • Many implementations: cheap commercial versions available at low price and one or two open source implementations

As is typical in B2B scenario's, AS2 servers are mostly located behind firewalls that only allow inbound connections from well know IP addresses.

AS2 and its family
AS2 has some family: AS1, which goes over SMTP. And a younger brother AS3 which uses FTP as its transport. And now a 4th child joins the family: AS4! AS4 uses uses ebXML messaging v3 as its transport. But what the heck is ebXML?

ebXML was an initiative to define *the* new B2B standard for the 21st century: new transport layer, new message definitions, XML schema building blocks, process layer, protocol profiles and so on. ebXML didn't really take off, mostly because it was considered some sort of threat to the Web Services story. A pitty that the WS-* world and ebXML world weren't able to come together in 2001. ebXML gained a bit of popularity in some European countries like the Netherlands and Denmark, where it is used on a limited scale.

Work continued very quiet and a new version of the transport layer was released in 2007: ebXML Messaging v3. ebXML Messaging v2 and v3 are actually SOAP over HTTP(s) with some extra whistles.

The most important feature of AS4 is pulling or polling. Polling is one of the reasons why file transfer is so popular: it is "asymmetric" and allows one side to stay behind a closed firewall. ebMS 3.0 supports polling and AS4 das well. Well done! WS-Polling was a similar initiative in the WS-* world to introduce polling.

AS4 will not become that popular in my opinion. The spec is rather "heavy" and ebMS 3.0 has very little traction. I'm not aware of any implementation. I would have preferred an extension of AS2 with support for polling, completely independent of the ebMS and WS-* specs. And so we'll simply continue using file transfer (SFTP, FTPS) as our most popular polling mechanism.

- Brik, thanks for pointing me to AS4
- Pictures are from a talk I gave on AS2
- Interesting link for those speaking Dutch: ebXML en ebMS: veilig en betrouwbaar berichten uitwisselen