Setting the trace level for SOAP Gateway

You can turn on internal tracing for SOAP Gateway to help diagnose problems. The trace level can be changed to control the amount of logging.

1. Determine what level of internal logging is required. SOAP Gateway performs best when logging is low or disabled, but troubleshooting may require more logging.

   Table 1. Trace level settings for the SOAP Gateway server log file

   Trace level value	Trace level	Description
   0	Off	The SOAP Gateway server log file and console appenders are disabled. Messages are not written to the SOAP Gateway server log file or job log. Error and fatal messages are still sent to WTO.
   1	Fatal	Only errors that result in an immediate server shutdown are logged.
   2	Error	In addition to logging errors that result in an immediate server shutdown, other errors and exceptions are also logged. NACK responses for synchronous callout applications that use the send-only with acknowledgment protocol are logged. This is the default trace level.
   3	Warn	In addition to what is logged at the error level, warning messages are also logged.
   4	Information	In addition to what is logged at the warning level, the entry and exit of important events and functions are also logged. All ACK and NACK messages for synchronous callout applications that use the send-only with acknowledgment protocol are logged.
   5	Debug	In addition to what is logged at the information level, the contents of buffers sent to and received from IMS Connect and SOAP Gateway are also logged.

2. Issue the command iogmgmt -prop -u -l level where level is the desired trace level.
   For example, issuing the command iogmgmt -prop -u -l 5 captures all available error, tracing, and debugging information.