open standard
An open standard is a standard that is openly accessible and usable by anyone. It is also a prerequisite to use open license, non-discrimination and extensibility. Typically, anybody can participate in the development. There is no single definitio ...
for the secure and payload-agnostic exchange of
Business-to-business
Business-to-business (B2B or, in some countries, BtoB) is a situation where one business makes a commercial transaction with another. This typically occurs when:
* A business is sourcing materials for their production process for output (e.g., a ...
documents using Web services. Secure document exchange is governed by aspects of WS-Security, including XML Encryption and XML Digital Signatures. Payload agnosticism refers to the document type (e.g. purchase order, invoice, etc.) not being tied to any defined
SOAP
Soap is a salt of a fatty acid used in a variety of cleansing and lubricating products. In a domestic setting, soaps are surfactants usually used for washing, bathing, and other types of housekeeping. In industrial settings, soaps are used ...
action or operation.
It is a Conformance Profile of the
OASIS
In ecology, an oasis (; ) is a fertile area of a desert or semi-desert environmentebMS 3.0 specification.OASIS ebXML Messaging Services 3.0: Part 1, Core Features /ref>
AS4 became a standard in 2013. The majority of the AS4 profiling points constraining the ebMS 3.0 specification are based upon the functional requirements of the AS2 specification. By scaling back ebMS 3.0 using AS2 as a blueprint, AS4 provides an entry-level on-ramp for Web services B2B by simplifying the complexities of Web services.
Key technical highlights
* Support for SOAP 1.1 and 1.2 enveloping structure
* Payload agnosticism
* Support for single or multiple payloads contained either within the SOAP body or as SOAP attachment(s)
* Support for payload compression
* Support for message-level security including various combinations of XML Digital Signature and/or XML Encryption
* Support for X.509 security tokens and username/password tokens
* Support for business receipt of non-repudiation similar to the Message Disposition Notification (MDN)AS2 MDN /ref> used by AS2 and specified as an XML schema by the ebXML BPSS group
* Support for the ebMS 3.0 One-Way/Push message exchange pattern with support for either synchronous or asynchronous responses
* Support for the ebMS 3.0 One-Way/Pull message exchange pattern which is beneficial for exchanging documents with non-addressable endpoints