AS2 Connector 6.0 - Mule 4
Mule runtime engine (Mule) supports the AS2 protocol through Anypoint Connector for AS2 (AS2 Connector).
AS2 Connector enables trading partners to transmit and receive AS2 messages with EDI-X12, EDIFACT, XML, or binary payloads, for example:
-
Send messages, signed or unsigned, over HTTP or HTTPS, using the AS2 protocol
-
Receive messages over HTTP or HTTPS, using the AS2 protocol
-
Receive asynchronous MDN for sent messages
For compatibility information and fixed issues, see the AS2 Connector Release Notes.
Before You Begin
To use this connector, you must be familiar with:
-
The AS2 target resource
-
Anypoint Connectors
-
Mule runtime engine (Mule)
-
Elements and global elements in a Mule flow
-
How to create a Mule app using Anypoint Studio (Studio)
Before creating an app, you must have access to:
-
The AS2 target resource
-
Anypoint Studio version 7.6 or later
Considerations when Migrating from the AS2 connector 5.x
AS2 Connector 6.0 requires Mule 4.3.0 or later. Refer to Upgrading and Migrating for more information.
Common Use Cases For the Connector
-
Send with sync MDN
Sends a message through HTTP or HTTPS using the AS2 protocol requesting the partner for a synchronous MDN (receipt)
-
Send with async MDN
Sends a message through HTTP or HTTPS using the AS2 protocol requesting the partner for an asynchronous MDN (receipt)
-
Listener
Source that receives messages via HTTP or HTTPS using the AS2 protocol
-
MDN Listener
Source that receives asynchronous MDN receipts via HTTP or HTTPS using the AS2 protocol
-
Non repudiation Listener
Source that receives a signed copy of a receipt or a message for persistent non-repudiation storage
Non-Repudiation Storage of AS2 Messages and MDNs
If needed, you can configure non-repudiation storage for your AS2 operations to support regulatory or compliance requirements.
Only signed messages and MDNs are eligible for non-repudiation.
The following AS2 Connector 6.0 sources and operations support the non-repudiation feature:
-
AS2 Send Sync operation
-
AS2 Send Async operation
-
AS2 Listener source
-
AS2 MDN Listener source
Before You Begin for Non-Repudiation Storage
To enable non-repudiation of a message in AS2 Connector, you must implement and configure a separate Mule flow that acts as a non-repudiation flow:
-
The non-repudiation flow must have access to the signed MIME message that is passed to it, along with appropriate non-repudiation specific attributes.
-
This non-repudiation-specific Mule flow is responsible for receiving, storing, and acting upon the messages and attributes it receives.
-
The name of this non-repudiation flow must be configured on an appropriate listener or operation that has non-repudiation storage enabled.
Audience
-
New users, read:
-
Using Anypoint Studio to Configure the Connector to create your Mule app
-
Examples, that provide one or more use cases for the connector
-
Advanced users, read:
-
Examples, that provide one or more use cases for the connector
For a major or minor release, see Upgrading and Migrating.
Next Step
After you complete the prerequisites and experiment with templates and examples, you are ready to create your own app and configure the connector using Anypoint Studio.