Logging server activity

Crystal Enterprise allows you to log specific information about Crystal Enterprise web activity. For details on locating and customizing the web activity logs, see Modifying logging behavior of the Web Component Server.

In addition, each of the Crystal Enterprise servers is designed to log messages to your operating system's standard system log:

• On Windows NT/2000, Crystal Enterprise logs to the Event Log service. You can view the results with the Event Viewer (in the Application Log).
• On UNIX, Crystal Enterprise logs to the syslog daemon as a User application. Each server prepends its name and PID to any messages that it logs.

  This example shows two messages logged to the syslog daemon on UNIX:

  

Each server also logs assert messages to the logging directory of your product installation. The programmatic information logged to these files is typically useful only to Crystal Decisions support staff for advanced debugging purposes. The location of these log files depends upon your operating system:

• On Windows, the default logging directory is C:\Program Files\Crystal Decisions\Logging
• On UNIX, the default logging directory INSTALL_ROOT/crystal/logging directory of your installation.

The important point to note is that these log files are cleaned up automatically, so there will never be more than approximately 1 MB of logged data per server. If you need to reduce the size of these log files for a particular server, or if you want to eliminate the log files entirely, stop the server and add the following command to the server's command line:

-maxlogfilesize <# of bytes>

Replace <# of bytes> with 0 (zero) to eliminate the log files. The procedure for making this modification depends upon your operating system:

• On Windows, use the CCM to stop the server. Then open the server's Properties to modify the command line. Start the server again when you have finished.
• On UNIX, run ccm.sh to stop the server. Then edit ccm.config to modify the server's command line. Start the server again when you have finished. For reference, see ccm.sh.