From the Rollover by Time list, select Never, Hourly, Daily, or Weekly to

Logging 9-27 With buffered logging, Oracle Web Cache stores log messages in memory. Oracle Web Cache writes them out in bulk to the access log when the buffer size or the flush interval is reached. The buffer size is set to 2048 bytes. Buffered logging increases performance by reducing the number of disk IO operations. If the Oracle Web Cache server shuts down unexpectedly, buffered log messages may be lost. Oracle recommends disabling buffering to view access log results immediately.

d. If buffering is enabled, in the Flush Interval field, enter the interval, in

seconds, when Oracle Web Cache writes contents of the buffer to the access log file. The default is 10 seconds. When the interval is reached, Oracle Web Cache writes buffered information to the access log file. Even if the buffer is not full, Oracle Web Cache updates the access log. Oracle recommends not changing the default, unless you want to lower the interval to see results more frequently. A value of 0 specifies that Oracle Web Cache will only flush the buffered access log when the specified buffer size has been exceeded.

4. Specify the following settings for each site in the Site-Specific Settings table:

a. If you want to apply the settings from the Default Settings row to this site,

click Use Default for all Sites Settings. Deselect this checkbox to provide site-specific overrides in the other fields.

b. In the File Name field, enter a name for the access log file.

The default file name is access_log.

c. Click Enable Logging to enable logging for the site; deselect to disable logging

for the site. Site-specific logging only takes effect if logging is enabled for the cache. If you enable this option, ensure that it is also selected for the cache in Step 3b. d. Select Log ESI Fragment Requests? to log the ESI fragment log messages from the log element of esi:environment or esi:include in the access_log_file .fragment file. If the x-esi-info field is selected, select to log the events to the access_ log_file .fragment file. The x-esi-info field is automatically selected if the Format Style is End-User Performance Monitoring Format. If the x-esi-info field is not selected, select Dont Log.

e. From the Format Style list, select an access log format.

See Section 9.2.1 for a description of the default formats and Section 9.5 to create a customized style for your environment.

f. From the Rollover Policy list, select a rollover policy to specify how often you

want to change the frequency at which Oracle Web Cache saves current log information to access_log_file.yyyymmddhhmm and writes future log information to a new log file with the configured log file name. For high-volume sites, select a policy with a high frequency. See Section 9.6 to modify an existing policy or create a new rollover policy.

5. Click Apply and restart Oracle Web Cache. See

Section 2.13 . 9-28 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache

9.5 Creating a Customized Access Log Format

If the default formats described in Section 9.2.1 are not suitable for your environment, create a new log format: 1. Navigate to the Web Cache Home page in Fusion Middleware Control. See Section 2.6.2 .

2. From the Web Cache menu, select Administration and then Access Logs.

The Access Log Configuration page displays.

3. Click the Log Formats tab, and click Create.

The Create Log Format dialog box displays.

4. In the Format Name field, enter a unique name for the format, keeping the

following restrictions in mind: ■ The format name cannot contain any spaces or special characters other than underscore _. ■ The name must be unique among other format names, rollover policy names, and session names.

5. From the Separator list, select the separator to use for separating access log fields.

6. In Print XLF Directive field, select Yes to include XLF directive information at the

top of the access log or No to not include directive information in the access log. Directive information typically consists of version, date, and field information. For example: Version: 1.0 Date: 12-Jul-2008 00:00:00 Fields: c-ip x-auth-id x-clf-date csHost x-req-line sc-status bytes See http:www.w3.orgTRWD-logfile.html for further information about XLF directives.

7. In the XLF Fields section, select an access log field name from the Field Name list.

See Table 9–5 for a listing of the supported access logs fields 8. If you select csheader_name or sc csheader_name, scheader_name, or x-cookiecookie_name, then enter the header or cookie name in the Header Cookie name field. See Table 9–6 , Table 9–7 , and Table 9–8 for a description of the headers allowed for csheader_name and scheader_name

9. Click Add.

10. Perform Steps 7 and 9 for each format you want in the access log, and then use the Move Up and Move Down buttons to order the fields. The order in which fields are entered determines the order in which the fields are logged.

11. Click OK to apply changes and return to the Access Log Configuration page.

12. Click Apply in the Access Log Configuration page to apply this change.

9.6 Creating a Customized Access Log Rollover Policy

To modify an existing rollover policy or create a new rollover policy: