Make sure that -Dhttp.proxyHost or -Dhttp.proxyPort is set
When you use the HTTP Analyzer within JDeveloper you will find that all java processes started from then on will send there traffic via the HTTP Analyzer. This includes the embedded oc4j instance. This can be useful if your service is using external services such as a credit card validation system.
Is the relatively straight forward to do this trick for any java process that might have been started outside of JDeveloper. You simply need to supply something like
-Dhttp.proxyHost=localhost -Dhttp.proxyPort=8099 to the java executable. You can of course alter the host name if the process is running on a different machine.
If you are running an instance of oc4j you tend to do this with with oc4j or oc4j.bat. These both read the environment variable
OC4J_JVM_ARGS which can contain the parameters mentioned above.
This may not capture all traffic between SOA services, such as BPEL, as in some cases inter-process communicate will skip the "HTTP Protocol" stack and exchange infosets more directly. This is something we will of course look at in future releases.