My organization recently implemented a new proxy/firewall appliance and now I find that my development broker instance (WMB version 8.0.0.1) is unable to call external web services.
Does anyone have any experience in configuring the broker to use a proxy?
If the web service I was trying to call were being served via HTTP, I suspect that routing traffic through a TCP/IP Monitor in Toolkit would solve the problem (as Toolkit is proxy-aware), but the one I need to call at the moment is being served via HTTPS.
It depends what sort of proxy you are using.
There are essentially 2 possible setups, in the first instance you will make an ssl connection to the proxy and the proxy will make an ssl connection on the client (brokers) behalf to the remote server.
In the second scenario you will make an unsecured tcp/ip connection to the proxy and use this as a tunnel to make an ssl connection from the client (Broker) to the remote server. To use this option you need to fill in the "HTTP(S) proxy location" in the request node properties.