SOAP messages: Debugging HTTP traffic problems

If, after reviewing the client logs, you discover that there is an error in the HTTP transfer of SOAP messages, you must manually enable the HTTP debugging option on the Service Manager server. This option allows you to trace all HTTP and SOAP messages between the Service Manager server and client. You can trace HTTP traffic in one of two ways.

  • Trace all HTTP connections to the server
  • Trace a dedicated connection to the server

To review all the HTTP traffic, you can enable the debughttp parameter from the Service Manager initialization file (sm.ini) file. This causes the server to record all messages sent from and to the server to the following log files.

  • logs\sm.log
  • RUN\TEST.log

This method of debugging SOAP messages traces all Service Manager processes, but significantly reduces system performance because the log files the server produces contain all HTTP traffic, including HTTP headers and attachments. For this reason it is recommended that you not enable this parameter on production systems, but rather in test environments only.

To review HTTP traffic use the -httpPort paremeter as in the sample below. In addition, you can create a dedicated log file for this connection. By starting a new Service Manager process and specifying a separate log parameter, you reduce the amount of system resources needed to produce debugging output. For example, you can enter the following command from the server OS command line to create a dedicated servlet and log file.

sm -httpPort:portnumber -debughttp:1 -log:../logs/debug.log

For portnumber, type a communications port number on which you want the server to use for SOAP requests. You can use the -log parameter to define a path to any log file you want.