B2b Adapter AS2 Sender Url

[Former Member]

Hi gurus,

normally the incoming message is expected at http(s)://server:port/AS2/<PATH>.

the <PATH> is given by the communication channel under Expected Url-path  = /POC/PARTNER

when i try to send the data to http(s)://server:port/AS2/POC/PARTNER also tested  http(s)://server:port/POC/PARTNER

503   Service Unavailable

I would appreciate if anyone can assist me, thank you

PM

[silentbull]

Thanks Ryan,

I know covansys is just an example

Regards

Sam

[Ryan-Crosby]

You're welcome, I mentioned to swap because I couldn't tell from your previous response when you had said "COVANSYS".

Regards,

Ryan Crosby

[silentbull]

Hello Ryan

When we tried to send message, we are getting the 403 error.

Remote server returned response code 403 and error message Forbidden

I believe when we tried to access in IE, it is asking for username and pwd. Do I need to provide one for the third party or is there a way to disable these user credentials one.

Regards

Krish

[Ryan-Crosby]

Hi Sam,

You have a few of potential options regarding authentication:

1. Disable authentication and make access available for anonymous users.

2. Setup authentication using ClientCertLoginModule.

3. Setup authentication using HeaderVariableLoginModule

We used option #3 because we were directing requests via web dispatcher and had the outside access control at the firewall - we simply altered the incoming request to insert the one http header variable we chose with the necessary information and that way we didn't have to get into the business of trading certificates with clients.

Regards,

Ryan Crosby

[silentbull]

Thanks, since we alrady have firewall, we used the first option and now the messages are trying to hit the server.

I received error as channel binding not found in the sender channel, but could not able to get the incoming payload.

Is there any save attachment module or common configuration to accept anything and save it local directory.

[Ryan-Crosby]

Hi Sam,

Yes, right in the AS2 sender you have several archive options depending on what you want to save to the file system.  The options are listed as:

Archive Messages and MDN

Incoming Wired Message

Payload after Charset conversion

Payload after Decryption

Archive Error Messages

Archive Positive MDN

Archive Negative MDN

Here is a sample for what we are using:

Regards,

Ryan Crosby

[silentbull]

Hello Peter

How do we differentiate messages from the same sender to our systems.

For eg., My third party van provider sends me Orders and Invoices to a reverse proxy which in turn sends it to my AS2 adapter using the url http(s)://server:port/AS2/

Does the sender needs to use different path for different message types, if this is the case, my firewall team needs to create many versions of reverse proxy for many messages.

Regards

Sam

[Ryan-Crosby]

Hi Sam,

You can use the same URL for multiple message types - simply pass the messages over to an EDI Separator receiver channel and then setup the necessary Separator sender channels to fit your requirement.  We are using URLs of the following setup in our system even with partners that send multiple message types:

http://server:port/AS2/PARTNER/

Regards,

Ryan Crosby

[silentbull]

Hello Ryan

I am not using edi here and just as2 adapter to send and receive idoc-xml.

I did not understand this part

http://server:port/AS2/PARTNER/

Regards

Sam

[Ryan-Crosby]

Hi Sam,

PARTNER is just used to represent some third party so they have their own URL.  If they are different message types then the need for multiple URLs would depend on how your ESR content is setup or if it's being used.  If it's strictly pass through then one URL is fine, if you are using ESR content then you would need one URL per sender interface.

Regards,

Ryan Crosby

[silentbull]

Hello Ryan

My third party is sending data to our reverse proxy which in turn forwards to the PI system.

As of now, I have given the forwarding url as http(s)://server:port/AS2/ to my infrastructure team who sets up the reverse proxy and the reverse proxy url is given to my third party.

How can i set a partner url like the one you have given. This is a good idea which can differentiates different partners. Should i create my own server url and put this in sender AS2 channel under expected url path. 

If so, this resolves the problem of different partners, what should i do next to differentiate different messages coming from same partner.Can I still use edi separator as my messages are only idoc-xml for AS2 adapter

http://server:port/AS2/PARTNER/

[Ryan-Crosby]

HI Sam,

Here is how you generate a URL for a specific partner - setup an AS2 sender channel like so:

The system will then answer for that channel on the appropriate URL as you can see in the channel monitoring:

As far as the remainder of the setup it would depend on if the XML is already in IDoc format or if you need to map it.  Also, if you use PARTNER/.* then you can instruct the partner to use a different path for each message type which you can then use to dynamically determine receivers and receiver interfaces in the case of multiple IDoc types.

Regards,

Ryan Crosby

[silentbull]

Hello Ryan

Thanks, that gave me bit of clarity.

So, the complete url that I should give to the partner for him to send messages to us would be the

http://server:port/AS2/Covansys as per your screenshot.

Please confirm this.

I am going to receive idoc xml for DELVRY05 and invoices  from the same partner.  So can i use a receiver determination and based on the message type of the orders, route the message to the appropriate sender agreement.

As previously mentioned, the partner is sending the message to our reverse proxy which will be common path, so we can't setup reverse proxy for each message type.

Regards

Sam

[Ryan-Crosby]

Hi Sam,

Yes, although I would swap Covansys with some name to represent which ever partner you are receiving messages from - that is simply an example of one of our partners.  If you are able to handle that step in the receiver determination then you are all set to just give them the one uniform URL for all messages and it should work.

Regards,

Ryan Crosby

[Former Member]

This message was moderated.

[Dimitri]

Dear Peter,

Please have a look at my blog:http://scn.sap.com/community/b2b-integration/blog/2013/08/07/easy-to-use-as2-software--part-ii

I guess you can filter out the URL I used.

Kind regards,

Dimitri

[Former Member]

Hi Dimitri

thank you for quick response. I could not find the sender Partner URL. Is there a template URL for sender CC like HTTP adapter?

http://<SAP PI HOST>/sap/xi/adapter_plain?party=AAA&service=ABB&namespace=urn:TEST.common.com/EDI&interface=IDoc_ORDERS_OB&qos=EO

[Dimitri]

Hi Peter,

Like I stated in my document, I left it on .*, but you can enter the URL from which you receive the message.

Please revert back if this is not clear.

Kind regards,

Dimitri