soapClient using proxy

, ,
1

Hi,

We have a problem with new installation - we are trying to connect to WS from corpo net through proxy server.

For client:http it works, but for client:soapClient we have connection timeout. So we suspect that it is not connecting through proxy.

2

Hi Lukasz,

please provide your wM Version.

Can you share your proxy settings from IntegrationServer?

Is the WebService using an EndPoint-Alias or a URL configured directly?

Regards,
Holger

3

Hi,

When using a web service consumer endpoint alias, you have the option of specifying which proxy do you want to use “Settings > Web Services > Create Endpoint Alias” (at least since version 8.2.2).

You choose the proxy from the list of proxies you have defined previously in “Settings > Proxy Servers > Create Alias”.

To actually use the web service consumer endpoint alias, you have to edit the web service descriptor that you want to call in Designer, after you have defined the alias in the IS (you may have to F5-Refresh the Designer).

Best Regards
2016-07-13 09_51_44-localhost_5599 - webMethods Integration Server.png

4

OK, We found the problem source - we were receiving expird cert from target server and this was causing readTimeout :wink: after changing watt.security.ssl.ignoreExpiredChains to true HTTPS works :mrgreen:

5

Hi Lukasz,

can you try to get in contact with your partner system to have them updating their certificates?

Using expired certificates and ignoring this circumstance is a security risk.

Regards,
Holger

6

Hi Holger,

Yes we are aware of that risk.

The problem is on dev/tst environment, not on PROD, so it is not crucial.