NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-68
Using the NonStop SOAP Trace Facility
Using the NonStop SOAP Trace Facility
As described in Configuring and Running the Server in a WebServer Environment on
page 6-60, you can use an environment variable called SOAP_TRACE_LEVEL to
specify whether, and at what level, to trace the operation of a server process. The
environment variable called SOAP_TRACE_FILE specifies the trace file name.
If a server process is running as a named process or a server class, the trace output
for each server is written to a different file. Each trace file will have a name of the form:
<name.nnn>
where name is the value of SOAP_TRACE_FILE and nnn is the process name of the
server.
If the trace file already exists when a server process starts up, the server process
appends new trace records to the end of the file.
The server reports these messages to EMS if the trace file cannot be created or
opened:
Error while opening the trace file: name
Error getting the Trace File name suffix: error
where name is the value of SOAP_TRACE_FILE and error is a file-system error
number. The trace file name suffix is the process name appended to the value of
SOAP_TRACE_FILE when the server runs as a named process or a server class.
To interpret a trace, you must understand the logic of a server process, as described in
User-Exit Classes on page 8-4.
A level 2 trace includes fault responses. For a list of faults, see Fault Messages on
page 6-46.
Example 8: Level 1 Trace
This example is output from a Level 1 trace. The SOAP server is running from the
command line and takes its input from a file.
Comments in bold do not appear in the trace file but are included in this manual for
your convenience.
The following line reports that the server process is starting.
The timestamp is in the format yyyy/mm/dd hh:mm:ss.
>> 2004/2/8 7:51:30<< Soap Application.. Starting up..
The following line reports the name of an XML input document, which should
contain a request to a service defined in the SDL file.
>> 2004/2/8 7:51:30<< Start>>> FILE INPUT: SoapPW_Logon.xml