Is it possible to use TCP/IP Monitor with web services?

Question

Hi!
I have created a web service in workshop 10 and deployed it on a WLS10 inside workshop. I have turned on TCP/IP monitoring and in this case it uses port 13458. I have also generated a test client using the clientgen ANT task.
Now I'm using the generated client classes in the following way:
TestWSXSDService service = new TestWSXSDService_Impl ("http://localhost:13458/TestWSXSD/TestWSXSD?WSDL");
TestWSXSD port = service.getTestWSXSDSoapPort();
Apparently the classes retrieves the WSDL file from the server and this request show up on the TCP/IP Monitor.
However, when I finally executes my request:
port.hello(in);
it's apparently using the endpoint information from the retrieved WSDL file and the request goes to port 7001.
This is the request I want to monitor! Is there a way to make this work with the client classes generated by clientgen or must I make my client in some other way in order to keep a fixed end point against the TCP/IP Monitor?
Thank you.
/John
Edited by johnlindgreen at 08/10/2007 4:51 AM

Answer 1

Hi!
I tried to set the suggested properties both on the client and server side, but as far as I can tell they don't wotk with WLS 10. Maybe I'm doing something wrong?
I tried to serach the documentation and found weblogic.webservice.verbose documented for WLS 8 and weblogic.webservice.client.verbose documented for WLS 9. I couldn't find anything for WLS 10.
But then I re-found something about using a proxy server from a client [url http://edocs.bea.com/wls/docs100/webserv/client.html#proxy_server]. This actually does the trick. So now my code looks like this:
               TestWSXSDService service = new TestWSXSDService_Impl ();
               TestWSXSD port = service.getTestWSXSDSoapPort();
          Proxy p = new Proxy(Proxy.Type.HTTP, new InetSocketAddress("localhost", 13458));
          HttpTransportInfo info = new HttpTransportInfo();
          info.setProxy(p);
          ((Stub)port)._setProperty("weblogic.wsee.connection.transportinfo",info);
This keeps the client use my TCP/IP Monitor as endpoint.
/John