Why this blog?

I initially created part one, two and three of this blog series just to share the easiness of the Mendelson AS2 software.

In this final part, I just want to add one last example : using Mendelson as a message receiver.

In this blog I will try to highlight the different steps needed for this scenario.

In case you feel parts are missing, please give me a sign and I will add it to this blog.


Introduction

Before you start with your scenario, please have a look at http://as2.mendelson-e-c.com/ and more specifically the Mendelson AS2 test server part.

In here, you can find all relevant information for you receiver AS2 adapter, certificates, signing and monitoring of messages.

NOTE: the Mendelson AS2 software provides the MDN synchronously, but SAP does not support this feature (yet). Please be aware of this.

Configuration for keys and certificates

Download the keys from http://as2.mendelson-e-c.com/ (Mendelson AS2 test server part). Key1 is used for the sender side and key2 for the receiver side.

Within the NetWeaver Administrator, a new view (VIEW1) was made, containing key1. VIEW2 contains key2.

Configuration of the receiver AS2 communication channel

The Mendelson AS test server URL is http://testas2.mendelson-e-c.com:8080/as2/HttpReceiver . IP address is 85.214.40.188.

/wp-content/uploads/2013/10/1_311064.jpg

/wp-content/uploads/2013/10/2_311065.jpg

/wp-content/uploads/2013/10/3_311087.jpg

Verifying the result on the Mendelson side

Monitoring via http://testas2.mendelson-e-c.com:8080/webas2/ . Username and password is guest.

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

  1. Agnieszka Domanska

    Hi Dimitri, thanks for all the B2B blogs.

    Very useful.

    Part 4 of your blog shows us how to send data to test mendelson server which is

    http://85.214.40.188:8080/as2/HttpReceiver

    Based on your blog, I know where I can find key1 and key2 for http://85.214.40.188:8080/as2/HttpReceiver.

    The question I have got is about my own public key certificate ( I have got my public key in my sender system ) and the question is:

    Do I need to upload sender public key certificate ( PI) into test mendelson server ?

    If yes, HOW ? ( I know how to upload it into my own as2 mendelson server ).

    I am looking forward to your reply.

    Kind regards

    Agnieszka Domanska

    (0) 
    1. Dimitri Sannen Post author

      Hi,

      There is no need to upload something into the Mendelson server.

      Have a look at my blog series and the Mendelson requirements for sending messages.

      That should just be fine.

      Kind regards,

      Dimitri

      (0) 
      1. Agnieszka Domanska

        Hi Dimitri, thanks for your reply. I have sorted it out now. The answer is:

        I do not need to upload my sender key into test mendelson server.

        I just need to download key1 from http://as2.mendelson-e-c.com and use that key for sending data to test mendelson server.

        Kind regards

        Agnieszka Domanska

        (0) 
  2. Vijayakumar B

    how can we create expected URL in PI?

    what are the steps we will do for AS2 configuration in sap pi 7.4?

    which URL we need to give to partner for pi side?

    please confirm us…

    (0) 
  3. Thrinath Moorthy

    Hi Dimitri,

    I have followed your steps provided above. But in my log its giving me the following error. I used my own public cert and private key to sign the message in my receiver channel. and used Mendelson cert to encrypt. But its giving me Recipient certificate does not match. the Public cert from SAP PO is a self signed. is it ok to use self-signed certs?

    [Sep 26, 2016 8:43:16 PM] 155edc93-8419-11e6-b602-000023dc249a@P4D: Inbound transmission is a AS2 message [mycompany-mendelsontest], raw message size: 3.81 KB.

    [Sep 26, 2016 8:43:16 PM] 155edc93-8419-11e6-b602-000023dc249a@P4D: Inbound AS2 message is encrypted.

    [Sep 26, 2016 8:43:16 PM] 155edc93-8419-11e6-b602-000023dc249a@P4D: To decrypt the data of the inbound AS2 message a key with the following parameter is required:

    C=DE,ST=Germany,L=Berlin,O=mendelson-e-commerce GmbH,OU=(c) 2016 mendelson-e-commerce GmbH – for authorized use only,CN=mendelson Public Primary Certification Authority – R4,E=ca@mendelson-e-c.com, 10270

    [Sep 26, 2016 8:43:16 PM] 155edc93-8419-11e6-b602-000023dc249a@P4D: A key with the following parameter has been used to decrypt the data of the inbound AS2 message (alias “Key2”):

    E=rosettanet@mendelson.de,C=DE,ST=Berlin,L=Berlin,O=mendelson-e-commerce GmbH,OU=mendelson-e-commerce GmbH,CN=mend, 1133444595

    [Sep 26, 2016 8:43:16 PM] 155edc93-8419-11e6-b602-000023dc249a@P4D: Generating outbound MDN, setting message id to “mendAS2-1474915396473-705@mendelsontestAS2_mycompanyAS2”.

    [Sep 26, 2016 8:43:16 PM] mendAS2-1474915396473-705@mendelsontestAS2_mycompanyAS2: Outbound MDN has been signed with the algorithm “SHA1”.

    [Sep 26, 2016 8:43:16 PM] mendAS2-1474915396473-705@mendelsontestAS2_mycompanyAS2: Outbound MDN created for AS2 message “155edc93-8419-11e6-b602-000023dc249a@P4D”, state set to [processed/error: authentication-failed].

    [Sep 26, 2016 8:43:16 PM] 155edc93-8419-11e6-b602-000023dc249a@P4D: Outbound MDN details: Error decrypting the inbound AS2 message: Recipient certificate does not match.

    Any help or suggestion will be appreciated.

    Thanks

    Thrinath

    (0) 

Leave a Reply