Siebel System Monitoring and Diagnostics Guide > Configuring Client-Side Logging for Siebel Applications Running in High-Interactivity Mode >

How Client-Side Logging for High-Interactivity Applications Works

When a Siebel Web Client starts, the client-side environment variables, if specified, are read from the client, and then the server-side parameters are read. The log engine then initializes and generates the retrieved log file data to the C:\SiebelLogs directory as shown in Figure 14.

Figure 14. How Client-Side Logging for High interactivity Applications Works
Click for full size image

Figure 14 illustrates the following flow:

  1. When the client starts up, the client-side environment variables are read from the client and the log engine initializes in one of two ways:
    • If no client environment variables are specified, the log engine initializes after reading the server component parameter values.
    • If there are no server component parameter values specified, the log engine initializes directly from the client.

      NOTE:  Client-side settings take precedence over server-side settings.

  2. The log file stores the data retrieved in the C:\SiebelLogs directory. However, if a user does not have permission for the C:\SiebelLogs directory, the log file creation fails, and logging is terminated.

Also, consider the following with regard to client-side logging for high-interactivity applications (not shown in Figure 14):

  • If the disk is full, logging is terminated, and the log file is not created.
  • The minimum log file size is 50 megabytes (MB).

For more information about the following:

Siebel System Monitoring and Diagnostics Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.