No receiver determination found in spite of correct url

[Former Member]

Hi everybody,

our partner tries to reach our XI on https adapter to start a synchronous process. The url is as follows:

<u>https://[host]:[port]/sap/xi/adapter_plain?party=[PARTY]&service=[SERVICE]&interface=[INTERFACE]&namespace=[NAMESPACE]</u>

I can see the message in the TA: sxmb_moni but there is always the error: No receiver determination found. But everything is correct. There IS a valid receiver determination set up. Are there any other parameters that have to be put into the url to get that connection online?

Regards.

Oliver.

[Former Member · Accepted solution]

Please try this url...and see if it makes a difference...

https://[host]:[port]/sap/xi/adapter_plain?party=[PARTY]&service=[SERVICE]&interface=[INTERFACE]&nam...

Thanks,

Renjith

[Former Member · Accepted solution]

Thank you for the quick answers.

Well, I compared the receiver parameters about a 100 times with the sxmb_moni and everything seems to be ok. I can see no differences.

Renjith, just leave agency and scheme empty?

Regards.

Oliver.

[Former Member · Accepted solution]

Yes please...the reason i am asking you try this is that in the comments of the HTTP inbound handler...you see what is below....so i am asking you to put the parameters that seems to be mandatory from this...

• call-syntax: XI 3

• http://hostname:port/path

• ?namespace=???

• &interface=???

• &service=???

• &party=???

• &agency=???

• &scheme=???

• [&qos= EO|BE|EOIO]

• [&msgguid=???]

• [&queueid=???]

• [&trace=[1|2|3]]

Thanks,

Renjith

[Former Member · Accepted solution]

try to ping the receiver system, it seems that connection is not setting up

Message was edited by:

Shripad Joshi

[former_member189558 · Accepted solution]

Hi,

check out the spellings for Sender Service , Interface and NAmespace from msg in Moni with that of Rec Det object in IR...There must be some diff....

Thanks ,

Himadri

[Former Member · Accepted solution]

There are definetely no differences in spelling. I checked it.

Is the order of party, service, etc. in the url important or can I mix it up as I like? Can I write <b>party=...&service=...</b> as well as <b>service=...&party=...</b>?

Btw: When I test the scenario in Int.Dir. the receiver is found without any problems.

Regards.

Oliver.

[Former Member · Accepted solution]

yes the order is important

[Former Member]

When using HTTP Sending adapter although it is sent directly to the pipeline you still need the sender agreement etc... you can spoof this in the integration directory... have you done this?

Receiver determination is done by sender, interface namespace and I am quite sure that with http you have to define this...

Message was edited by:

Alex Ong

[Former Member]

Check your Id configuration and check the Whether the Receiver agreement has the appropirate communication channel. this might help you.

thankx,

shree

[Former Member]

Which is the correct order? Namespace, interface, service, partner?

There is no communication channel necessary because the message will be directed to a BPM.

[Former Member]

order :party,service,namespace,interface.

if it is directly to BPM then in interface name you need to give abstact interfacename.

Regards

Sreeram Reddy

[Former Member]

When I use http adapter I don't need no interface, right?

What about synchronous processes with http adapter? Do I need one in this case?

[Former Member]

yes . you wont be having interface. in synchorouse while sending it is not required but receving you give it in HTTP adapter

[Former Member]

Sorry, I think it was a bit late yesterday as I wrote this mess.

What I meant was, if I use asynchronous mode I don't need no <u>sender agreement</u> for http adapter. Do I need a <u>sender agreement</u> in a synchronous process with http adapter?

[bhavesh_kantilal]

> When I use http adapter I don't need no interface,

> right?

You dont need a Sender Adapter and a Sender Agreement. But you do need a Sender Message Interafce and the corresponding Receiver Determination.

> What about synchronous processes with http adapter?

> Do I need one in this case?

For asynch calls, you will use a Asynch Interafce with QOS as EO and for synch calls you will use a Synch interafce with QOS as BE.

Look into this simple HTTP - RFC blog and understand things for yourself,

/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit

Regards

Bhavesh

Regards

Bhavesh

[Former Member]

Hi Oliver,

just see in SXMB_MONI msg, the source system details are the same as you config your recever determination - source system details in ID.......just check whether your recver detemination is activated or not.....if not activated, then activate your recver detemintaon....

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

Oliver

check the URL are they using correct busines ssytem namesapce for your outbound .

cross check out bound detials which are in URL with your Receiver Determintion in Directory both should be same. other wise we get this error

[Former Member]

In the msg in SXMB_MONI do you get the details of sender interface, system and name space correctly? It should exactly match the receiver determination object created in ID.

Regards,

Jai Shankar