Proxy - to - WS - Receiver SOAP call timeout sync

[diego_a]

Hi,

Receiver SOAP call timeout sync

Apdater http SOAP (axis)

URL: the path to the WSDL we got was placed

SOAPAction: you put one of the operators that appear in the image of soapUI.

SOAP Version = 1.2

Now when a test is done from the soapUI program everything works normally

now from the proxy in R3 reports a timeout error.

That may be happening?

thank you.

Diego

[diego_a]

Hi

The timeout issue was solved, the policy is added to the proxy.

Now I have the problem since I sxi_monitor indicates an error:

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

- <!--

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30"

xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIAdapterFramework</SAP:Category>

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: Cannot find dispatch method for {http://xxxxxxx/}file</SAP:AdditionalText>

<SAP:Stack />

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

</SAP:Error>

What could be wrong?

Thank you,

[iaki_vila]

Hi DIego,

I guess this exception is in the WS side. I think you are using the correct URL (may be you path inside the URL is wrong) or you need to set the action in the SOAP channel. If you have a WSDL try to test with an external tool like SOAPui.

Regards.

[diego_a]

Hi,

the problem was solved, I will ask the people of managed web service that does not change the SOAPAction for the full url, before SOAPAction = "ns: invoice" now SOAPAction = "http: \\ xxxxx \ invoice"

Thank you all for the help.

[Former Member]

Hi

Please use complete domain name in the target url. I have faced this issue some time back because ,I was not using the full domain name in the url.

[udo_martens]

HI Diego,

the PI system is not in the same network as your computer. Timeout means not connectivity at all. So PI cant connect the Soap host. A basis expert should execute a ping from the PI system and asure connectivity.

/Udo

[baskar_gopalakrishnan2]

Please check whether firewall port is open.  If not,  talk to the network team.  Basically you might want to check connectivity between PI and ws host server.   Also maks sure target URL entered the right one. Please update more on  this.