The scenario involves the B2B Sender sending a EDI document which is compressed, signed and encrypted. The B2B Receiver returns MDN (The Internet messaging format used to convey a receipt.) to the sender during the same HTTP session as the sender’s original message.

2.1 ABCCompany configuration:

a) Select the Compress outbound messages in Send settings

b) Select Request sync MDN option from MDN settings

2.2 AS2 Sender Adapter Configuration:

a) Modify the security settings as shown below and keep other properties as it was done

in part 1

b) Save and Deploy the integration flow

2.3 Post AS2 message from AS2 Mendelson:

The scenario involves the B2B Sender sending a EDI document which is compressed, signed and encrypted. The B2B Receiver returns MDN (The Internet messaging format used to convey a receipt.) to the sender on a different communication session than the sender’s original message session.

Prerequisite: This scenario involves sending an Asynchronous MDN. You need to configure cloud connector to establish the communication between SAP Cloud integration tenant and on- premise system where mendelson has been installed.

You can refer the setup guide or blog for setting up the cloud connector for more details.

a) Create a Virtual To Internal system mapping on Cloud connector as shown below.

b) Give access to all Path and sub-paths to the mapped system

3.1 ABCCompany configuration:

In the AS2 Mendelson tool, the MDN settings of ABCCompany should have the below configuration.

Request Async MDN selected.

Request signed MDN option is checked.

3.2 AS2 Sender Adapter Configuration:

a) Change the MDN settings of AS2 Sender adapter to have the configuration

Provide the alias name of the private key from SAP Cloud Integration tenant.

Select Proxy type as “On-Premise”.

Keep the other properties of AS2 Sender as configured in scenario 1.

b) Save and Deploy the integration flow.

3.3 Post AS2 message from mendelson tool:

Message should be processing successfully.

Take away:

We have learnt on how to configure and send AS2 messages securely using signing and encryption.

In the next part of this blog series, I would extend this simple AS2 inbound scenario to use the EDI Flow steps to transform the ANSI X12 bulk payload to split, validate and convert to IDOC document.