How to intercept all the calls from a local Weblogic server to a remote one?

[Giuseppe]

Hi,
I'm using fiddler to intercept the calls from my web browser to a local server from about two months and it is simply AMAZING so thank you for this great tool.

Now I would like to use it in a manner a bit more complex. I would like to intercept the calls (XML/SOAP) form my local webserver (WebLogic) to a remote one of which obviously I know the specific IP and port.

I have some problem to configure the proxy used by Weblogic, in fact it seems that the standard manner doesn't work. Maybe it is a my fault (I'm not an expert in this field) or maybe the weblogic domain, configured by my company, has some particular restriction that prevent me to use a proxy.

I guess if there is a manner to redirect to fiddler all the outgoing request to a specific address on a specific port ad using an OS configuration instead of a local server configuration. I mean, when windows detects an outgoing connection to a specific remote address and port it automatically redirect (transparently) it to another, in this case to fiddler.

Is there an easy way to obtain this behaviour?
Thanks in advance.

Best regards,

[Eric Lawrence]

Hi, Giuseppe--

This:

I guess if there is a manner to redirect to fiddler all the outgoing request to a specific address on a specific port ad using an OS configuration instead of a local server configuration. I mean, when windows detects an outgoing connection to a specific remote address and port it automatically redirect (transparently) it to another, in this case to fiddler.

 

... is typically what's called a "transparent proxy" and it's a capability Fiddler does not really have. 

Can you explain how you attempted to configure your WebLogic server to proxy its traffic through Fiddler?

(Alternatively, if you are in control of the URLs that WebLogic is requesting, you can simply edit them to point directly at your PC running Fiddler, then you can use script in Fiddler to rewrite the URLs to their proper destinations).

Regards,
Eric Lawrence
Telerik

[Giuseppe]

Hi Eric,
thanks for the quick answer.
To configure weblogic I went to its console and then in:

"Settings for myserver" -> "configuration" -> "server start"

In the textbox "Arguments:" (that was initially empty) I put

-jvmargs -Dhttp.proxySet=true -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8888

[Eric Lawrence]

Hello, Giuseppe--

Unfortunately, I don't have a WebLogic instance to try with.

Have you tried setting the proxy directly within the affected code (e.g. using setProperty)? http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureJavaApp

You might also ask this question on either a WebLogic forum or a more general web forum (e.g. serverfault.com)

Regards,
Eric Lawrence
Telerik

[Giuseppe]

Hi Eric,
I perfectly understand, I will ask in a weblogic forum so, thanks in any case for your replies.
Unfortunately I can not do it via code because the code that manages the connections and the environment are under management of other teams. This is why I like so much your software, it allows to "hack" the exchanged messages without the need of changing much into the system (for now just between the UI and the module which I'm working on but soon I'm sure also the soap message exchanged between my module and the backend!).
When I will find the solution I will put it here as reference for other users that maybe have the same issue.

Thanks a lot!

And best regards

[Akif]

This works for me in Weblogic

Set this in the setDomainEnv.cmd

set PROXY_SETTINGS= -DproxySet=true -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8888

The startWeblogic.cmd will pick it up and Fiddler will show the outbound calls