Define Web Service - Inbound Channel URL

[Former Member]

Hi,

Previously when defining a web service we would input the following for Step 2 (Inbound Channel):

http://HOST:PORT/XISOAPAdapter/MessageServlet?channel=:service:communicationchannel

We then employed a different PI contractor and she just told us to click 'Propose URL' instead of entering a URL as above. This currently generates:

http://HOST:PORT/sap/xi/engine?type=entry

Both work. The advantage of the second option is you don't need to set up a sender agreement/sender adapter as the WSDL generated makes no reference to a communication channel. The disadvantage of the second option is if you want to enforce Async you need to manually amend the WSDL whereas if a channel existed you could do this via the Quality of Service.

Question to the PI experts out there is what option is best and thus recommended ?

Cheers,

PaulC.

[MichalKrawczyk · Accepted solution]

hi,

first one is using SOAP adapter on java stack (so the most preferred way)

second one is using SOAP adapter on ABAP stack (does not exist on single stack PI)

so better to use the first one as ABAP stack will be gone,

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Michal,

Ok. Your answer convinces me we should use option 1.

As an aside when does this "Single stack PI" come into existance ? We are on NW7.02 SP 10.

Thanks for your help.

PaulC.

[MichalKrawczyk · Accepted solution]

Hi,

single stack is already an option from PI 7.30 (latest one is 7.31)

so we're using single stack PI already

Regards,

Michal Krawczyk

[smavachee]

Hello Paul,

First option is always preferable as it points towards specific sender business service along with its respected sender CC. Whereas if you are using second option, sometimes you may deal with an error for Sender agreement.

Similar thread at..

Also look at..

SOAP Sender End Point

Regards,

Sunil