Create an AS2 Agreement in Azure BizTalk Services
Updated: January 6, 2015
This topic lists the steps to create an agreement to exchange messages between trading partners using the AS2 protocol.
AS2 non-EDI messaging
AS2 messages can be sent to a non-EDI destination or received from a non-EDI destination. This functionality is built into AS2 so you don’t have to worry about the transport protocol. You can use X12, EDIFACT, or other protocols that are not included with BizTalk Services. For example, you receive a non-EDI message from a supplier over AS2. You process the XML data and then transform the message to UBL documents.
Non-EDI messaging is enabled in the BizTalk Service project or in the BizTalk Services Portal. To use non-EDI messaging in the BizTalk Service project, use any of the following tools in the Toolbox:
XML One-Way Bridge
XML Request-Reply Bridge
Two-Way External Service Endpoint
Two-Way Relay Endpoint
AS2 Non-Repudiation of Receipt (NRR)
AS2 includes Non-Repudiation of Receipt (NRR) support. Non-Repudiation provides proof that a message is valid and authentic. If the message validity is ever questioned, its validity can be proven and possibly legally binding.
For example, you and Contoso agree to non-repudiation. You send an AS2 message to Contoso to purchase widgets. Then, you deny sending the message to purchase the widgets from Contoso. With non-repudiation enabled, Contoso can retrieve the message to confirm that you agreed to purchase the widgets.
Non-Repudiation of Receipt (NRR) is enabled in the BizTalk Services Portal and is used for EDI and non-EDI messages.
The topics in this section list the steps to create an AS2 agreement, including Non-Repudiation and non-EDI destinations.
In This Section
Other ResourcesCreate Agreements in Azure BizTalk Services