SOAP Gateway logs
SOAP Gateway provides a server log with diagnostic information and a transaction log that records message traffic.
The following table shows a comparison of the SOAP Gateway logs:
| Feature | Purpose |
|---|---|
| Server log | The server log provides diagnostic and usage
information for SOAP Gateway server
administrators. This log includes messages from the SOAP Gateway management utility. The server log file is stored on the local file system. |
| Transaction log | The transaction log provides a complete record of every request made to a SOAP Gateway web service provider (provider scenario) or an external web service (callout scenario). The information for each transaction includes the request and response processing details for IMS Connect and the target (provider) or source (callout) IMS application. This information can be used for diagnostic purposes by the SOAP Gateway server administrator, by IMS and IMS Connect administrators, and by client application developers. Because the transaction log contains a record of every message processing event associated with the requests, it is also useful for auditing the activity of SOAP Gateway applications and gathering performance data. When transaction logging is enabled by using the iogmgmt -tranLog command, the transaction log file is stored on the local file system. The server administrator must manage the log files to ensure that server has adequate storage space. SOAP Gateway can also send the information to a remote transaction collector with theIBM® Tivoli® Composite Application Manager for Transactions (ITCAM) Transaction Tracking API (TTAPI) by using the iogmgmt -tranAgent command. |