Caché SOAP Log
Caché SOAP Log
To log the SOAP calls made to or from a Caché namespace, set the following nodes of the ^ISCSOAP global in that namespace:
|^ISCSOAP("Log")||Specifies kind of logging. Use one of the following values (case-sensitive):
|^ISCSOAP("LogFile")||Specifies the complete path and filename of the log file to create.|
The log indicates the sender or the recipient as appropriate, so that you can see which web service or client participated in the exchange.
The following shows a partial example of a log file with line breaks added for readability:
01/05/2010 13:27:02 ********************* Output from web client with SOAP action = http://www.mysecureapp.org/GSOAP.AddComplexSecureWS.Add <?xml version="1.0" encoding="UTF-8" ?> <SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' ... <SOAP-ENV:Header> <Security xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> </SOAP-ENV:Header> <SOAP-ENV:Body> ... </SOAP-ENV:Body> </SOAP-ENV:Envelope> 01/05/2010 13:27:33 ********************* Input to web client with SOAP action = http://www.mysecureapp.org/GSOAP.AddComplexSecureWS.Add ERROR #6059: Unable to open TCP/IP socket to server localhost:8080 string
Note the following points:
With Caché XML tools, you can validate signatures of signed XML documents and decrypt encrypted XML documents. If you perform these tasks in this namespace, the log contains details for them as well. See Using Caché XML Tools.
The Caché SOAP log captures SOAP calls even when no message is sent on the wire (that is, when the service and client are both on a single machine).
If a severe error occurs, the system stops writing to the SOAP log. See the console log instead. For information, see “Monitoring Log Files” in the Caché Monitoring Guide.