Performance Tuning for Content Manager

Chapter 9. Tuning WebSphere for Content Manager 261

Windows under <installed drive>:\IBM\IBMHttpServer\conf directory. The

definition of each parameter is described in the httpd.conf file itself.

In this section, we discuss the performance tuning settings that are associated

with the Web servers.

9.4.1 Access logs

Access logs collect all incoming HTTP requests. Logging degrades performance

because the I/O operation overhead causes logs to grow significantly in a short

time.

Default value

Logging of every incoming HTTP request is enabled.

How to view or set

1. Open the IBM HTTP Server httpd.conf file, located in the directory

IBM_HTTP_Server_root_directory/conf.

2. Search for a line with the text CustomLog.

3. Comment out this line by placing # in front of the line.

4. Save and close the httpd.conf file.

5. Stop and restart the IBM HTTP Server.

Our recommendation

Disable the access logs.

9.4.2 Web server configuration refresh interval (RefreshInterval)

WebSphere Application Server administration tracks a variety of configuration

information about WebSphere Application Server resources. Some of this

information, such as URIs pointing to WebSphere Application Server resources,

must be understood by the Web server. This configuration data is pushed to the

Web server through the WebSphere Application Server plug-in at intervals

specified by this parameter. Periodic updates enable new servlet definitions to be

added without having to restart any of the WebSphere Application Server

servers. However, the dynamic regeneration of this configuration information is

costly in terms of performance.

Default values

60 seconds.