Forum Discussion

MartinE's avatar
MartinE
New Contributor
16 years ago

[RESOLVED]SOAP Monitor and HTTP-Proxy

Hi all,

could need a helping hand with my proxy problem. I'm using lates SOUPUI 3.0.1 community on Windows XP.

I have the following sitiuation:
1) WebService consumer (client)
2) SOAP UI with SOAP Monitor configured as proxy on port 8081
3) local proxy (running on the computer where soap UI is running)
4) company proxy
5) webservice provider (server)

The webservice consumer is configured to use the soapui host as proxy, the service endpoint addresses are not changed, the webservice calls arrive there as i can see according messages in the log - so connection 1-2 is ok.

The "local proxy" is required as soapui does not play very well with our companies NTLM proxy for any reason (will be clarified with company IT). The global proxy configuration is ok - at least the WSDL query when creating a new soapUI project from "outside" works.

When calling the webservice from the client, i can see a timeout message in the command prompt of soapUI so the request gets stuck somewhere between 2 - 5. Could it be that soap monitor does not use the soapUI global proxy preferences?

Also tried to use tunneling without success :-(

Any hint would be greatly appreciated.

Regards,
Martin

3 Replies

  • Hello,

    Let see, it looks like this;

          1.                                  2.                                3.                      4.                      5.
    WS Client --> soapUI Monitor(tunnel/proxy) --> local proxy --> company proxy --> WS server

    Well, you can not use soapUI monitor in proxy mode for this. But you should be able to use tunnel for this. Try this:
    1. set a local proxy host/port in soapUI's global settings
    2. start soapUI monitor in tunnel mode , set port ( ex. 9999 ) and for end point set web service end point. Other fields does not need to be set if you are using plain http protocol.
    3. i'll assume that client(1) and soapUI(2) are on same computer so you should send request from client to localhost: in this case http://localhost:9999. If client and soapUI are not on same computer that replace localhost with ip machine running soapUI.

    Also, just to be sure use nightly build. There were some changes regarding this problem.

    Let me know does this helps you,
    robert
  • MartinE's avatar
    MartinE
    New Contributor
    OK, works as expected with nightly build from 2009-10-14 using tunneling. Thanks for your help robert, Martin
  • IamDiana's avatar
    IamDiana
    New Contributor
    In above case, can I know how you accessed your webservices from the client ? What url you used ?
    This will be more useful to me, as I am trying to do the same setup now as you described.