on 04-25-2014 7:29 PM
Hello Experts,
I am using the AS2 adapter from the B2B Addon.
I am stuck in the scenario Sender AS2 -> SAP PO; with the 403 forbidden error.
Few queries;
1. Is virtual receiver mandatory ?
2. Is is mandatory to have party for sender and receiver. Currently I am having only Sender ( Party + Comm. Component ) and Receiver ( Comm. Component ( Partner Type = LS )).
Can you help please.
Thanks
Saurabh
Hi All,
This issue was resolved by installing the certificates properly. I created 3 entries in SAP PO keystore view.
1. Private key of self
2. Public key of sender
3. Public key of self
initially it was only KeyPair of self..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saurabh
From your AS2 environment , are you able to reach the http / https port of your SAP PI system and vice versa.
Basically , you need to ensure that the network ports are open in both directions. As I can see from the above the port is 8080 . A simple telnet test should be able to establish that.
Basis team should be able to take care of this.
Secondly the certificates need to be exchanged between the 2 sides. Can you please confirm if these are done.
Thanks
Rishi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the same error and the problem was that I had wrong value in Expected URL-Path in my AS2 sender communication channel.
What has worked for me was creating very generic AS2 sender communication channel ( with .* ) e.g.
.
As soon as, I was able to send a message out of AS2 software into PI, I restricted values of Expected URL-Path, Expected sender's AS2Name, Expected own AS2Name etc. one by one.
403 forbidden error means that PI does not know which communication channel assign the message to! I hope it helps.
Hi,
We are working on the similar scenario, we have created the URL as sent to partner - http://public ip:port/AS2/auth
1. we have tested the URL in the browser , and we gave the password and we receive the error
"Use POST-Requests to submit AS2-Messages"
2. This is message in communication channel monitoring for sender channel - " Channel is listening for incoming connections on /AS2/auth " we are not clear in this statement".
3. once the partner post the message in the URL, where will we receive the message in PO 7.4 , how to see it.
4. Please tell us any setting to be made from PO 7.4 side.
Thanks & Regards
vijay
Hi Saurabh
1. Is virtual receiver mandatory ?
--> Virtual receiver is not mandatory.
2. Is is mandatory to have party for sender and receiver. Currently I am having only Sender ( Party + Comm. Component ) and Receiver ( Comm. Component ( Partner Type = LS )).
--> It is not mand to have the party. Please refer the below blog for step by step configuration
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harish,
Thanks for your quick response.
I have configured with the following details :
Sender Party : ABC ( 009 | GLN | 333333333 )
Sender Component : DEF
Receiver Party : PQR ( 009 | GLN | 111111111 )
Receiver Component : XYZ
Sender AS2 adapter :
Expected URL : http://10.194.35.20:8080/as2/HttpReceiver
Message ID Left : .*
Message ID Right : .*
Sender AS2 name : 333333333
Receivers AS2 name : 111111111
Expected subject : AS2 message
Partners in Mendelson :
Partner 1 :
( Local station )
1. Name : Mendelson_AS2
2. AS2 ID : 333333333
3. Email : receiver@as2server.com
MDN tab : http://<Mendelson desktop PC IP>:8080/as2/HttpReceiver
Parnter 2 :
1. Name : PQR
2. AS2 ID : 111111111
3. Email : sender@as2server.com
Receipt URL : http://<PI-Host>:<PI-PORT>/AS2/.*
Payload subject : AS2 message
Error details :
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Transmission failed, remote AS2 server reports "Forbidden".
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: HTTP 403
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Message payload stored to
Hi Saurabh,
I faced this problem last week during testing and it turned out to be a mismatch/typo in my AS2 IDs. I checked yours and they look ok but check your settings. I'm not in front of my computer at the moment but I also noticed the mention of expected URL in your AS2 sender. I may be mistaken but I'm pretty sure this would be labeled URL Pattern. If you enter a value of .* then all requests sent to /AS2/ will be handled by the one channel.
Regards,
Ryan Crosby
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.