SOAP messages are reaching to PO server not able see them in the message monitors.

[former_member630137]

Hi All,

i developed a web service and provided it to a 3rd part vendor who will call it from outside of my network.

To accept the calls from outside a web dispatcher is in place. now the problem is SOAP call are coming to PO server but i am unable to see the messages in the message monitor.

we checked the logs on web dispatcher we are able to see the traffic from third party and routed to PO server. on the PO sever log i see web dispatcher IP and method POST with status '405'(405 Method Not Allowed). didn't understand what is the problem and why getting the 405 status.

can someone please help me to fixing the issue, its urgent. Thank you.

[sugata_bagchi2]

What is the URL format you have provided to the sender SOAP application ?

ask them to send the request in the below format of URL -

https://<yourWeb Dispatcher Host name>:<port>/XISOAPAdapter/MessageServlet?channel=:<sender system>:<sender channel name used for this interface>

Thanks

Sugata

[former_member630137]

Hi Sugata,

after lot of trouble shooting we got the issue, web dispatcher is configured to message server after changing it to application server we tested the web service from SOAP UI its working(i can see the message in Monitor).
what we done is In SOAP UI it is getting my PO system URL there if i changed the HOST and port with web dispatcher info its working where as same endpoint URL if vendor is using in the application he is getting 500 error.

do i need to overwrite endpoint URL in my web service with web dispatcher URL ?
if yes then how to do , please advice.

Thanks.

[JaySchwendemann]

Am I getting the following right?

• You had an initial WSDL with a wrong endpoint and changed that and now it is working through(!) the web dispatcher for you
• The same changed WSDL with the changed endpoint going through the web dispatcher however is NOT working for the customer and he is presented a http 500?

If so, you might want to look at web dispatcher (foremost) and at PI (second). 500 means that the server hat troubles processing the request. That server might be the web dispatcher, might also be PI.

My guts feeling is that the 500 stems from a wrong endpoint address your customer is trying to call hence PI returns HTTP 500. However, you will have a easier life if you monitor this on web dispatcher as you then can see which endpoint URL the caller actually used.

Cheers

Jens