Thanks for your response Param,

The Trace Utility (in soap toolkit 3) can be used to trace SOAP message at
both clientside and serverside.  For clientside, we can use it through the
following steps:

1. Start the Trace Utility, and create a new Formatted Trace, there will
popup a dialog which contains the following fields:

##local port: ________
##destination host:________
##destination port:________

2. Since we we're tracing the message on clientside. We can put a certain
unused port for local port (like 8888). And the
"destination host" and "destination port" should be identical to the Target
server (where the webservice is hosted), for example:

##local port: __8888______
##destination host:____remoteServiceServer____
##destination port:____80____

After that, we also need to modify our webservice client proxy. We need to
make our webservcie client proxy send request to that configured  "local
port" above, so that the Trace Utility can capture the message ( and trace
utilty we help us forward it to the destination host and port after log the
message....)

For example, in your client application code, we call the service like:

WSProxy proxy = new WSProxy();

proxy.Url = "http://localhost:8888/VirtualDir/service.asmx";

proxy.CallMethod();

thus, the message call request will be send to "localhost:8888" first, then
be logged by TraceUtility and finally be forward to

"remoteServiceServer:80"  .....

If there're still anything unclear, please feel free to post here. Thanks,

Steven Cheng
Microsoft Online Support

--------------------

<OmzMG5I4FHA.632@TK2MSFTNGP10.phx.gbl>
<R7hmdEO4FHA.1172@TK2MSFTNGXA01.phx.gbl>

microsoft.public.dotnet.framework.aspnet.webservices:8287

http://www.microsoft.com/downloads/details.aspx?familyid=c943c0dd-ceec-4088-