How do you trace the entire SOAP message which is being sent to Information Services Director (ISD) when a service operation is invoked by a web service (HTTP) client?
WebSphere Application Server (WAS) tracing can capture the entire SOAP message. The following instructions were made using WAS 7.0. The procedure should be the same for other WAS releases, though the exact names of the links, admin pages, buttons etc may vary slightly between those releases.
These instructions explain how to enable the trace at runtime, without restarting the server.
- Log into WAS Administration Console.
- From then left navigation menu, expand Troubleshooting
- Click on "Logs and trace" link
- In the main panel, click on the server name in the table for your server
- Under General Properties in the main panel, choose Diagnostic Trace
- Click the "Runtime" tab.
- Under Trace Output section, select File option
- Provide the path to where you want the trace file to go
- Set the max file size and number of files based on your requirements*
- Click apply.
- Under Additional Properties, click "Change log detail levels"
- In the text area, add the following options (separated by colon ' : ' characters)
- Click OK to save the changes, and then click OK on the parent page to save changes.
* Depending on how many messages you need to trace, and how much data in these messages, you need to set the file size and number of files so that the log will contain all of the data you want to inspect before the logs roll over. Some experimentation may be necessary.
For further detail on this (and other) web services tracing, visit the Information Center for your exact WAS release, and search for the topic "Tracing Web Services".