AS2 Asynchronous MDN Integration: Step-by-Step in SAP Integration Suite

[NaveenReddy_06]

In this blog, we demonstrate how to implement asynchronous (delayed) MDN handling using the AS2 adapter in SAP Integration Suite. The setup includes creating one iFlow to send AS2 messages and another to receive the MDN response separately. Key steps include configuring the AS2 adapter for async MDNs, managing authentication with certificates (PFX), setting correct AS2 IDs, and monitoring the message and MDN flow. This approach is essential when two systems need to exchange AS2 messages with delayed acknowledgment handling.

We will:

• Create an integration flow (iFlow) to send an AS2 message
• Configure the AS2 adapter to expect a delayed (asynchronous) MDN
• Build another iFlow to receive the MDN response
• Set up authentication and certificates (PFX files) if needed
• Fill in AS2 IDs correctly to match sender and receiver
• Monitor the flow and check the MDN response in trace mode

Step1 :-

• Open the Cloud Integration and create the integration flow with the necessary functions.

• Asynchronous MDN Connection Settings :-

 Configuration of MDN tab in AS2 Adapter: 

1. Private Key Alias for Signature:

• Used to sign the MDN (Message Disposition Notification).
• Ensure the alias exists in Keystore. (This is the name of the keypair that you have used in the decryption process)

1. Signature Encoding:

• Format of the MDN signature.
• Options: binary or base64.[ Better to keep it required as we have Provide private key]

1. Propagate MDN Details to Exchange:

• Sends MDN info (like disposition, timestamp) to integration flow.
• Optional – enable if needed by downstream logic.[Better to keep it required] 

1. Negative MDN on Processing Failures:

• Sends a negative MDN if message processing fails.
• Useful for notifying partners about issues.

Asynchronous MDN Connection Settings:

1. Proxy Type:

• Typically set to Internet.

1. Authentication:

• Method to authenticate async MDN responses.
• Usually None unless required by proxy.

1. Timeout (in ms):

• Wait time for async MDN.
• Example: 300000 ms = 5 minutes.

Step 2 :-

This is the integration flow for which the MDN Attachment need to be sent as we have selected asynchronous Communication.

1. In the Connection tab specify a path for the as2 endpoint. 
2. Select the Authorization to be UserRole/Client_Certificate[In my case I selected User Role] 
3. You need to send the PFX file to the SENDER ADAPTER iflow tenant because you will be receiving the response asynchronously from the sender adapter. 

•  Set Up the Processing Tab for MDN Reception

1.  In the Processing tab of the AS2 sender adapter (the one receiving the asynchronous MDN):

• Source: Select Authorized User
• Partner AS2 ID: Enter the AS2 ID of the original sending system
• Own AS2 ID: Enter the AS2 ID of this iFlow

2. Retry Section is for Retry Handling Configuration

 

3. Monitoring MDNs in Trace Mode

       After deployment:

• Go to Monitor > Message Processing.
• Enable Trace Mode for detailed logs.

4. You’ll see:

• Message content
• MDN details
• Attachments (signed MDNs)

 Always test the full flow end-to-end to ensure the MDN is correctly received and verified.

Description:

This scenario involves creating an iFlow to send AS2 messages using the AS2 adapter configured for asynchronous (delayed) MDNs. A separate iFlow is built to receive and process the MDN responses. To ensure secure communication, necessary certificates must be configured on both sender and receiver sides. Proper AS2 IDs should be maintained for accurate partner identification. Once the setup is complete, the integration flows should be monitored to confirm that messages are delivered successfully and corresponding MDNs are received and processed correctly.