XI Server Proxy - WAS4.0 http configuration

[Former Member]

I have the following scenario:

File to XI to R/3. I'm using the file adapter as the sender and an XI adapter as the receiver, which should call a server abap server proxy.

I created a virtual host on the was4.0 r/3 system called /XIS with the an alias of default_host/sap/xi/engine

When I test the alias I get the following error:

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code>

<SAP:P1>/xis?sap-client=110</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Pipeline ID , which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /xis?sap-client=110)</SAP:Stack>

I created an RFC destination and used the path prefix of /sap/xi/engine?type=entry. Testing this I get a return code of 500, which I think is good. I added the role of sap_xi_appl_serv_user to the xi service id that I'm using.

When I run my scenario, I get a 401 return code when I try to call the server proxy.

Any help would be great.

Thanks,

Mark

[MichalKrawczyk]

hi,

401 is an authorization issue

are you sure all your passwords are ok?

(in RFC dest)

Regards,

michal

[Former Member]

Yes, I have the correct password. Also, from the sm59, I can do a connection test and get a 500 return code, which means I have the correct id and password.

[MichalKrawczyk]

hi,

and do you see pipeline URL filled in SXMB_ADM on your XI ?

integration server config?

Regards,

michal

[agasthuri_doss]

Hi Mark,

check the user for proper authorization

This might help you

http://help.sap.com/saphelp_bw31/helpdata/en/ce/1629a698b3ed48ab2360aaa096a4a5/content.htm

Thanks & Regards

Agasthur iDoss

[Former Member]

Michal,

How can I check "URL filled in SXMB_ADM on your XI

integration server config?

If I go to SXMB_ADM --> Integration Server Config, I do not see a whole lot, just Global Config Data (Role of Business system = IS) and specific Config Data.

[Former Member]

Michal,

Thanks for all of your help. I finally figured it out. In my receiver XI adapter I had it pointing the port,path,etc..to our main integration server and not the application server (r/3) where the proxies reside. I can now call and execute my server proxy.

For some reason my soap xml messages on the r/3 app server are being queued in a waiting status. If I go to SXMB_ADM and run the queues, then my proxies get processed. Why are they getting put in a que?

Thanks.