skip to main content
Troubleshooting the OpenAccess SDK Server : Configuring Logging
 

Configuring Logging

You configure logging by using the OpenAccess SDK Manager to change the ServiceDebugLogLevel service attribute for session and service logs, and the ServiceIPLogOption service attribute for IP session and service logs. Depending on the level of logging you set, the log files can contain any of the following types of messages:
ServiceDebugLogLevel
Fatal Errors
Errors
Warnings
Information
Debug
SSP Packet Log (OpenAccess SDK Server Wire Protocol packets in binary format)
SSP Requests (OpenAccess SDK Server Wire Protocol packets in decoded format)
By default, logging is enabled for Fatal Error messages.
ServiceIPLogOption
Disable All Tracing
Enable Error Tracing
Enable Major Events Tracing
Enable Full Tracing
Enable Verbose Tracing
By default, logging is enabled for Enable Error Tracing.
All Error and Fatal Error messages (for example, an invalid license key encountered message) are logged in a system-wide, platform-specific log facility:
On Windows, use the Event Viewer and look for messages in the Application Log where the Source is either OpenAccess SDK or the name of the service.
On UNIX and Linux, messages are sent to the UNIX or Linux syslog service. The messages are sent by default as USER type messages (the ServiceUnixSyslogFacility service attribute can be used to change the default message type). The OpenAccess SDK Manager can edit the syslog.conf file to configure the actual destination of these messages. Refer to your UNIX or Linux documentation for more information.
The following sections give examples of configuring logging through the ServiceDebugLogLevel service attribute. The procedure is the same for configuring the ServiceIPLogOption service attribute.