NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-69
Using the NonStop SOAP Trace Facility
The following line reports the name of the target service, in this case Logon. The
process method in the SoapProcessor class discovers the name of the service
by parsing the XML input file.
>> 2004/2/8 7:51:30<< SoapProcessor::process>> service name: Logon
The following line reports that the SOAP factory class has located the class for
interaction with the target service.
>> 2004/2/8 7:51:30<< SoapClassFactory::instantiate, ServiceName: "Logon"
ClassName: "SoapPW_Logon"
The following lines report the creation of the service object, which is derived
from the SoapDocumentHandler class.
>> 2004/2/8 7:51:30<< SoapDocumentHandler::SoapDocumentHandler()
>> 2004/2/8 7:51:30<< SoapPWDocumentHandler::SoapPWDocumentHandler(int, int)
>> 2004/2/8 7:51:30<< Out of ~SoapDocumentHandler()
The following line indicates that the server has serviced the request. If the server
is running from the command line, it stops itself after each request. If the server
runs as a TS/MP server class, it persists, waiting for another request.
>> 2004/2/8 7:51:30<< EndRequest>>> Input File Name: SoapPW_Logon.xml
Example 9: Level 2 Trace
This example is output from a Level 2 trace. The SOAP server is running as a
Pathway_CGI server class and taking its input from a client over HTTP.
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/8/21 15:37:46<< Soap Application.. Starting up..