http-PI-Idoc scenario

[former_member745782]

hello everybody,

I designed my interface scenario http-PI-Idoc

Mapping is a very easy point to point

I would like know where ( to witch URL) the third part system need post xml data

this one?:

http://<mysever>:<myport>/sap/xi/engine?type=entry ???

or this?

http://<mysever>:<myport>/

and in wich mode i can set configuration?

it's necessary send also some parameters like Sender Interface, namespace, QOS?

In witch mode?

i'm searching a example about this but i don't find nothing

thanks

Alex

[baskar_gopalakrishnan2 · Accepted solution]

Refer this link

http://help.sap.com/saphelp_nwpi71/helpdata/en/44/8f54b8b01e3673e10000000a114a6b/content.htm

Example:

http://sap-ag.com:8088/sap/xi/adapter_plain?service=sender&namespace=yahoo.com&interface=someinterfa...

which mode?

If you are using synchronous then specify QOS=BE otherwise (EOIO or EO) for asynchronous

[former_member745782 · Accepted solution]

thanks so much to everybody.

And what about authentication?

it's necessary send authentication to XI? or can i bypass it?

[former_member854360 · Accepted solution]

Hi,

Define the Security Check for Incoming Messages

2. Under Security Check for Incoming Messages, you can select which HTTP Security Level is to be required for incoming messages:

○ HTTP

○ HTTPS without client authentication

○ HTTPS with client authentication

http://help.sap.com/saphelp_nwpi71/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm

[former_member200962 · Accepted solution]

it's necessary send authentication to XI? or can i bypass it?

you need to provide the sending application a PI user-id and password......PIAPPLUSER

[Former Member · Accepted solution]

You can put directly User&Password credentials in Endpoint URL to WS 3rdParty Consumer, like follow:

&sap-user=<user>&sap-password=<password>

[former_member200962 · Accepted solution]

You can put directly User&Password credentials in Endpoint URL to WS 3rdParty Consumer

this approach should only be followed for testing purpose....it is not recommended to send user-id and password in a URL in real case.

[Shabarish_Nair · Accepted solution]

You can put directly User&Password credentials in Endpoint URL to WS 3rdParty Consumer, like follow:
> 
> &sap-user=<user>&sap-password=<password>

yes. the autnetication cannot be bypassed unless you go for a HTTPS connection.

Either the source application can embed the user id password into their code or extend the calling URL with the above syntax as mentioned by sapntaleoni. But this is generally not recommended due to obvious security reasons

[former_member745782 · Accepted solution]

really thanks to everybody!

last question:

If i decide to use mode "HTTPS without client authentication", then address will be:

https://<my server>:<myport>sap/xi/adapter_plain/?namespace=<namespace>.....etc etc

with HTTPS correct?

and the <port> will be always the same?

again thanks

[baskar_gopalakrishnan2 · Accepted solution]

>with HTTPS correct?

Yes url will be https://blah.com

>and the <port> will be always the same?

Port will be different for https. Most likely 50001. Please confirm with Basis team.

[markangelo_dihiansan · Accepted solution]

Hello,

with HTTPS correct?
and the <port> will be always the same? 

The HTTPs port can be found by typing SMICM and then pressing shift+f1. There you will see the ports used for http,https, smtp, telnet etc...

Hope this helps,

Mark

[Former Member · Accepted solution]

The HTTPS port may be different from HTTP port, depend on system configurations.

Usually http port is 5<SN>00 and https port is 5<SN>01

Check it, as suggested above, in SMICM transaction -> GoTo -> Services

[former_member745782 · Accepted solution]

super

now work!

thanks to everybody

[Shabarish_Nair]

the URL will be as provided by Santhosh.

For QoS, if it is async it can be EO or EOIO (if queuing is required). For sync communication it will be BE

[santhosh_kumarv]

Check this help.sap link

http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm

it will be something like below.

http://<hostname:abap http port>//sap/xi/adapter_plain/?namespace=<namespace>&interface=<interface>&service=<service>

~SaNv...