"AS4: Secure B2B Document Exchange Using Web Services" is a specification being developed by a subcommittee of the OASIS ebXML Messaging Services Technical Committee.
The intent and purpose of the formation of the AS4 subcommittee is the development of a Web Services Constrained Profile of the ebMS v3.0 specification, referred to as the
"AS4 Profile". This profile will provide guidance for a standardized methodology for the secure and document-agnostic exchange of B2B payloads using Web services.
AS4 is for the secure and payload-agnostic exchange of B2B documents using Web services. The intent is to map the AS2-like functional requirements onto the WS-* stack
using ebMS 3.0 as a leverage point. AS4 constrains the ebMS v3.0 specification (and the underlying WS-I profiles and WS-* stack) for messaging packaging, transport,
security, exchange patterns, and non-repudiation. AS4 is a Web services based protocol that brings simplicity to organizations that are heavily invested in Web services.
It provides B2B vendors an on-ramp to Web services based B2B solutions that have otherwise resisted.
The technical committee which is drafting the initial AS4 Profile is utilizing the lessons learned from AS2. However, that is the only relation between AS4 and AS2.
It is not the plan that AS4 products will take the place of AS2 products. AS4 will offer organizations that are already invested, or want to invest in web services, a
web services based protocol with the simplicity and lessons learned from AS2.
AS4 is being developed in the open standard arena of OASIS to make that subset publicly available and publicly maintained. The extensible nature of Web services via the
WS-* stacks gives great freedom in expanding and adding features in the future by composing other WS-* specifications. That can be done by either evolving the Profile
over time, or by deferring to a full implementation of the ebMS v3 specification.
AS4 will have the AS2 functional requirements plus more functionality because it is a subset of the ebMS v3 specification. In looking over the landscape of using Web
services for B2B messaging, it did not seem like there was anything as simple and elegant as what AS2 affords for that domain space. Whatever was out there was either
very complicated, document/WSDL-centric, or just underspecified.
In the spring of 2007, the Drummond Group invited a large group of B2B software vendors to come together for a series of technical discussions to explore what Web services
B2B might look like. Those series of technical discussions produced a high level list of business functionality. We made some general broad brush consensus on
some Web services functionality around packaging, security, non-repudiation, error handling, etc.
In reviewing these requirements after consensus, the interested parties realized that there was ample common ground with the AS2 functional requirements. And, soon
after, it was noticed that there was some common ground with the ebMS v3 specification development that was ongoing. Eventually, agreement was reached that the best
plan was to profile the ebMS v3 specification as an "entry-level on-ramp" to Web services B2B, similar to ebMS3.
Because of the competition between various WS standards and groups, the group decided against competing with the ebMS v3 effort. Instead, they decided to join forces in
an effort to help drive Web services adoption in the B2B arenas. Obviously, the fractured nature of Web services bodies and the general lack of interoperability are
obstacles to Web services adoption. It was felt that this was a necessary approach to drive adoption. The ideas of our software vendor technical group from last
spring and the ebMS v3 TC, are congruent and both parties felt it is more conducive to work together.
Instead of the subset of ebMS v3 that would be certified based on a document like a Drummond Group Test Plan for instance, the subset would be officially defined as an OASIS
profile. The ebXML Messaging Services Task Committee has embraced this and an official sub-committee of that Task Committee with the express purpose of producing the
AS4 Profile has been created. By aligning ourselves as an ebMS v3 profile, it clarifies a number of opportunities.
Let the EDIGuys experience with AS4 EDI transmissions ease your security concerns!
We'll get you up and running with secure AS4 EDI transmissions!