Logging

In order to better support debugging in the Web Server, Synactive has introduced a logging function. This functionality was implemented in the June 2011 release for all releases of Web Server 1.1.89.0 and above. This section will explain all relevant information associated with the log functionality.

The logging feature is designed to accomplish two specific purposes, which are as follows.

The multiple logifles feature means that in order to provide the most detailed debugging, every module in the Web Server will have its own dedicated logfile. This makes it easier to locate a single aspect of the Web Server without necessitating reading through voluminous logfiles in search of a single point of interest. The logfles created are as follows:

Perpetual logging means in that in order to have a constant log and yet avoid over-burdening the system with a large number of logfiles, we use a rotating logfile system. For each log that is maintained, no more than three files are extant at any one time. These files are as follows.

Available Logs

THe following logs are available in the Web Server.

  1. SAPPROXY.log: This log is usually named in the following manner - SYN_SAPPROXY_[port#].log. If multiple instances of Web Server are running, each will be logged under its own individual port number.
  2. SAPPROXY Connection Log: SYN_SAPPROXY_[port#]_[ConnectionID].log. The ConnectionID is the memory address of the CConnectionParam object. This object is unique for each SAPGUI connection.
  3. Fuzion CGWAProxy/WebServer Log: SYN_FUZION_[httpport#]_[httpsport#].log. The httpport# is the HTTP port number. Similarly, the httpsport# is the HTTPS port number. If either is set to '0', then that service is disabled.
  4. Fuzion CGWAProxy/WebServer Connection Log: SYN_FUZION_[ConnectionID].log. The ConntionID is the memory address of the CConnectionParam object. This object is unique for each SAPGUI connection.