In the beginning was EDI, and B2B integration standards were born, and it was good. And the value-added networks that carried the EDI settled over businesses everywhere, and that was good, too (if more than a little expensive). And then came the Internet, cheap data transport, and with it EDIINT – a leaner, meaner integration standard than made for lightweight, Internet-based integration.
Pretty soon almost every business had migrated to the Internet for sending and receiving B2B data, and AS2 (a version of EDIINT) became the ruling standard – until web services came along, a standard unto themselves for agnostic interface between systems.
Confused yet? You’re not alone. The world of B2B integration standards is no longer as simple as it once was, and it has evolved rapidly. But it needs to be simple again, because B2B integration is no longer a luxury – it’s a mission-critical necessity, in the Internet-driven, demand-driven, ad hoc business universe that now contains all commerce.
The size of the door
A lean and mean standard for mapping business communications – one that can be rapidly implemented and easily supported – makes all the sense in the world, because it makes B2B integration practical (and affordable) for businesses of all sizes. Where, then, is the problem?
The problem is that web services – the doorway into and out of organizations doing B2B with other organizations – is robust and platform-agnostic, but also very complicated, because web services handle data transfers of many different kinds. This complexity is a barrier in itself, because a great deal of detail must go into sculpting a particular transaction to work within a web service correctly.
AS2 accommodates that complexity, but that makes AS2 itself very complicated. While it may be lean and mean on the data formatting side (which is its most important feature), the protocol side is klunky and difficult.
Think of it this way: web services are doors, yes, but in practice they resemble bank vault doors – heavy, complicated, hard to open and close correctly. That’s what you want, when you’re trucking in a great deal of valuable content.
But what if the content is bite-sized, immediate, simple? Isn’t it a waste of time and brainpower to figure out how to get small and numerous chunks of data through that ungainly door?
Think now of what most organizations really need: a doggy door. Small, simple, sized to admit only what’s important and nothing else.
AS4 is everything its predecessor is, in terms of B2B business integration. The utility that services business document sharing in AS2 is all there in AS4.
But AS4 is the answer to the doggy-door problem. The bank-vault complexity of web services – which emerges from a broad and complicated technical specification called ebMS – is bypassed by AS4. The AS4 protocol uses, and allows for, only those features of ebMS that are really necessary for conventional B2B integration. All the other forms of data transfer that are accommodated by web services through ebXML are ignored. The machinery for handling them exists, unnecessarily, in AS2, making AS2 somewhat exasperating in practice. In AS4, all of that exasperation goes away, because AS4 only requires the basics, in order to get in and out of the web services doorway.
AS4 is payload-agnostic – meaning that it can be carrying any type of business document, and the transport protocol doesn’t care what it is. A single AS4 message can carry multiple payloads (a must for effective B2B integration). It is friendly to a wide range of security specifications, and supports business receipts (notification of the disposition of the message, once it’s been sent). And it supports ebMS’s One-Way/Push and One-Way/Pull exchange patterns: the first allows transactions to be either synchronous or asynchronous; the second enables endpoint variability.
Put simply, AS4 is following in AS2’s footsteps. The latter simplified the lumbering giant of EDI and made it Internet-friendly, an essential step in the evolution of B2B integration. AS4 has in turn simplified AS2, and made the sharing of messages friendlier still – which removes one of the last excuses for not implementing B2B integration.