Calling external Web Service: PI is looking for a logical port and proxy.

[Former Member]

Hi,

My scenario is ECC Proxy -> PI -> External Webservice (WS adapter).

the Web service adapter fails with the error message:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">WS_ADAPTER_SYS_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>System error while calling Web service adapter: Error when initializing SOAP client application: &#39;error_text&#39;</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

When I debug the message processing, it is looking for a port in table SSRVRTCONFIG, finds it(entry created automatically when WS adapter and the corresponding receiver agreement is activated in ID.

Then the program looks for an entry in "SRT_CFG_CLI_ASGN" for a proxy and logical port combination and errors out.

to be able to call an external web service, do we need a proxy to be created? I tried to create but the proxy creation fails because the external WSDL has some unsupported tags.

Also do we need to do any other configuration in SOAMANAGER? I am assuming not because the Web service is external.

Any help would be appreciated.

Thanks

Vijay

[Former Member]

Vijay,

Check Note 1142454, it might help.

Regards,

Neetesh

[Former Member]

I already checked that note and made sure that the points mentioned are met. I have a trace set up on the target system and would know if the call reaches them and then fails in authorization. Right now the call doesnt even reach the target system and also from debugging I know that the program is looking for a proxy and then fails.

[Former Member]

Have you tried using a TCP/IP Gateway? That will help in tracing and will give you an idea where exactly the issue is.