This topic discusses tracing SOAP messages that request Web services by using the tcpmon tool.
Note: The tcpmon command can be run only from a Windows or Linux workstation.
You can use other trace tools to trace SOAP messages, similar to how you can trace Web services components. See Tracing Web services for more information about these other
trace tools.
You can trace SOAP messages exchanged between a client and the server by installing a monitor or sniffer application to capture the HTTP traffic between the two points. The WebSphere product provides a utility class, com.ibm.ws.webservices.engine.utils.tcpmon, to trace the SOAP messages. The com.ibm.ws.webservices.engine.utils.tcpmon class redirects messages from a port, records the messages, and forwards the messages to another port.
WebSphere Application Server typically listens on port 9080, or port 80 if you are using IBM HTTP Server. The tcpmon process can be configured to listen on a particular port, such as 9088, while redirecting messages to another port, such as 9080 or port 80. The client is redirected to use port 9088 to access Web services.
Redirecting an application client to a different port is done by changing the SOAP address in the client Web Services Description Language (WSDL) file to use port 9088 and then running the wsdeploy command-line tool on the client enterprise archive (EAR) file to regenerate the service implementation.
Trace SOAP messages in
Web services by following the actions listed in the steps for this task section.
ResultThe messages exchanged between the client and server appear in the TCPMonitor Request and Response pane.
Related tasks
Tracing Web services
Troubleshooting Web services