Tracing SOAP messages with tcpmon
You can trace SOAP messages that request web services by using the tcpmon tool.
Before you begin
You can use other trace tools to trace SOAP messages, similar to how you can trace web services components. See the tracing web services information to learn more about these other trace tools.
It is not recommended that you use the tcpmon tool in a stressed environment. Tcpmon is only for monitoring SOAP messages in a lightweight environment.
About this task
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 application server 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.
wsdeploy 명령은 JAX-RPC(Java™ API for XML-based RPC) 애플리케이션에서 지원됩니다. 애플리케이션 서버에서 구현되는 JAX-WS(Java API for XML-Based Web Services) 프로그래밍 모델은 wsdeploy 명령을 지원하지 않습니다. 웹 서비스 애플리케이션에 JAX-WS 엔드포인트만 있는 경우 wsdeploy 명령을 실행할 필요가 없습니다. 이 명령은 JAX-RPC 엔드포인트를 처리하는 데에만 사용되기 때문입니다.