The GWWS server process utilizes the TMTRACE trace functionality that is supported by the Tuxedo. The trace feature in the GWWS is used in conjunction with the TMTRACE.

The trace messages are logged in the ULOG file accessible within the user set-up directory. The user could check the ULOG file to determine the cause of a problem. Also, looking at the ULOG helps the user to determine at what stage of the message processing the problem occurred within the SALT gateway

The trace can be enabled using the environment variables TMTRACE and GWWS_TRACE_LEVEL. The TMTRACE variable enables the trace. And the environment variable GWWS_TRACE_LEVEL controls the amount of trace that will be logged by the SALT gateway.

abort,system, sleep

If any of these trigger specifications are used, GWWS servers may terminate unexpectedly.

For more information, see tmtrace(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference

GWWS_TRACE_LEVEL can be set to 100 or 200. The value '100' provides the least amount of trace information in the ULOG file. The value '200' provides the most amount of trace information.

TMTRACE and GWWS_TRACE_LEVEL environment variables can be set as follows:

export TMTRACE=atmi+ws:ulog

export GWWS_TRACE_LEVEL=100

Trace is enabled for both ATMI and SALT messages (for least amount of tracing).

To enable tracing for only SALT messages, set as follows:

export TMTRACE=ws:ulog

export GWWS_TRACE_LEVEL=200

The following example shows a ULOG file example containing SALT tracing messages.

105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:Begin data transformation of request message, buffer type = FML32, SCO index=4095
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:trace_level<100>:sco_index<4095>:WS<TFML32>:tuxedo_service<TFML32>:direction<inbound>:message_kind<request>:Parsing of the Data message begins before sending to tuxedo
…
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:Entering<TRACE_FSM>
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:SCO[4095] FSM State Transition: --OK-->FindService
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:Exiting<TRACE_FSM>
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:<200>:<4095>:<TFML32>:<TFML32>:<inbound>:<request>:<Message:Style/Encoding><DOC/LITERAL>
…
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:<runSoap2BufConversion> <200>:<4095>:<TFML32>:<TFML32>:<inbound>:<request>:Message config parameters info:input buffer<inbuf>:type<FML32>:schema-name<fml32_TFML32_In>:style<DOC>:encoding<LITERAL>:type<request-response>
…
105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:<100>:<4095>:<TFML32>:<TFML32>:<inbound>:<request>:<XML2Tux> data conversion SOAP to tuxedo completed
…
105106.slc04jtu!GWWS.27653.1388463872.0: TRACE:ws:<buffer2soap> trace_level<200>:sco_index<4095>:WS<TFML32>:tuxedo_service<TFML32>:direction<inbound>:message_kind<response>:Data will be converted to SOAP message:mode<Internal>:style/encoded<DOC>/<LITERAL>:endpoint<http://slc04jtu:12438/TuxAll>:buffertype<outbuf>
105106.slc04jtu!GWWS.27653.1388463872.0: TRACE:ws:<runBuf2SoapConversion> <200>:<4095>:<TFML32>:<TFML32>:<inbound>:<response>:Message config parameters info:output buffer<outbuf>:type<FML32>:schema-name<fml32_TFML32_Out>:style<DOC>:encoding<LITERAL>:type<request-response>
105106.slc04jtu!GWWS.27653.1388463872.0: TRACE:ws:<runBuf2SoapConversion> <200>:<4095>:<TFML32>:<TFML32>:<inbound>:<response>:type<FML32>:name<outbuf>
105106.slc04jtu!GWWS.27653.1388463872.0: TRACE:ws:<nestBuf2Soap> <200>:<4095>:<TFML32>:<TFML32>:<inbound>:<response>:type<BYTE>:schema-type<byte>:minOccur<1>:maxOccur<1>:name<tf32char>:value<0xFFFFFF80>
…
FML32>:<TFML32>:<inbound>:<response>:type<MBSTRING>:schema-type<string>:minOccur<1>:maxOccur<1>:name<tf32mbstr>:value<abcdefg>