NonStop SOAP User's Manual
Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-73
Using the NonStop SOAP Trace Facility
The SOAP server starts a transaction on behalf of the client.
>> 2004/8/21 15:37:46: :<< >>Begin Transaction
The following lines report the first call to the parser. The purpose of this call is to
extract the name of the target service from the XML input
>> 2004/8/21 15:37:46: :<< Locating service name GetData>> 2004/8/21
15:37:46: :
<< SoapDocumentHandler::SoapDocumentHandler()
>> 2004/8/21 15:37:46: :<< SoapDocumentHandler::parse>> In
>> 2004/8/21 15:37:46: :<< Going to call the parser->parse()
>> 2004/8/21 15:37:46: :<< SoapDocumentHandler::parse>> Getting out
>> 2004/8/21 15:37:46: :<< Input Encoding is
The following line reports the name of the target service, as described in the
SDL. The subsequent line reports a service type of 1, which means TS/MP.
>> 2004/8/21 15:37:46: :<< SoapProcessor::process>> service name: GetData
>> 2004/8/21 15:37:46: :<< Service Type is 0
>> 2004/8/21 15:37:46: :<< SoapDocumentHandler::SoapDocumentHandler()
>> 2004/8/21 15:37:46: :<< SoapPWDocumentHandler::SoapPWDocumentHandler()
>> 2004/8/21 15:37:46: :<<
SoapServerPWDocumentHandler::SoapServerPWDocumentHandler()
The following line reports that the SOAP factory class has located the class for
interaction with the target service and created a service object, which is derived
from the SoapDocumentHandler class.
>> 2004/8/21 15:37:46: :<< SoapClassFactory::instantiateByType>> Instantiated
an object of type SoapServerPWDocumentHandler
>> 2004/8/21 15:37:46: :<< Out of ~SoapDocumentHandler()
The following lines report the second call to the parser. The purpose of this call
is to extract the request information.
>> 2004/8/21 15:37:46: :<< SoapDocumentHandler::process:In
>> 2004/8/21 15:37:46: :<< SoapDocumentHandler::parse>> In
>> 2004/8/21 15:37:46: :<< SoapDocumentHandler::process: After the call to
parser->parse()
The next several lines report information needed to send the request. The server
suspends the transaction, because the target service does not support
transactions. The target PATHMON name, the server class name, the size of the
request, and the expected size of the response, are obtained from the SDL file