Home arrow Oracle arrow Page 2 - Monitoring the Oracle HTTP Server

How to Monitor the Oracle HTTP Server - Oracle

In this third part of a five-part article, you'll learn how to manage the Oracle HTTP Server (OHS) from the command line, how to monitor the OHS, and more. It is excerpted from chapter five of the book Oracle 10g Application Server Exam Guide, written by Sam Alapati (McGraw-Hill, 2006; ISBN: 0072262710).

  1. Monitoring the Oracle HTTP Server
  2. How to Monitor the Oracle HTTP Server
  3. Using Oracle HTTP Server Log Files
  4. CERTIFICATION OBJECTIVE 5.03: OHS Configuration Directives
By: McGraw-Hill/Osborne
Rating: starstarstarstarstar / 3
January 25, 2007

print this article



You can view the following types of Oracle HTTP Server metrics using the Application Server Control.

Status Metrics    The OHS Status metrics show you a summary of the memory usage, CPU usage, connection rates, and error rates for the server.

exam watch:   Oracle recommends that you use the Application Server Control page to modify the Oracle HTTP Server configuration, rather than directly edit the httpd.conf file.  

Response and Load Metrics   Response and Load Metrics provide an overall picture of server performance. The Response metrics show the average number of requests submitted and the length of time the server took to respond to the user's requests. The Load metrics show the average number of bytes of data processed with the requests. Of course, large loads will result in a slower response time.

Module Metrics    The module metrics for the HTTP Server show the current response times for the various HTTP modules.

Server Properties Page

You can view and modify basic OHS settings from the Server Properties page, which can be reached in the following way:

  1. Navigate to the relevant Application Server Control HTTP Server home page. 
  2. Click the Administration tab, which will take you to the Administration page. 
  3. On the Administration page, click Server Properties.


Here's a brief summary of the Oracle HTTP Server settings you can view and modify from the Server Properties page:

General Settings

In the General section of the Server Properties page, you can view general OHSsettings. You can also modify the following settings from here:

  • Document root location    You can specify a relative path or an absolute path for the document root location, with the relative path being relative to the ServerRoot directory specified in the configuration file. 
  • Administrator E-Mail   All error messages to users contain the Administrator E-mail address to be used by the HTTP Server. 
  • User and group settings   You can modify the initially chosen values for the user and group directives in the httpd.conf configuration file.
  • Listener addresses and ports   Using this section, you can do the following:

    • Change the default port setting for the HTTP Server. 
    • Add, remove, or change a current listening address or port.

Note that the Listening Addresses/Ports table contents are the same as the contents of the Listen directive in the OHS Server configuration file ( httpd.conf ).

Error Log and Access Log Settings

You can view the error logs and the access logs and change their settings from the Logging section of the Server Properties page. You can perform the following tasks from here:

  • Change an error log or access log filename or location. 
  • Set the logging level for the error logs.
  • Set the IP Address Translation type. 
  • Add and remove an access log file. 
  • Change the log format of an access log file.

Client Request Handling Settings

The Client Request Handling Settings section shows information about various client request settings, such as the following:

  1. Maximum Requests Processed Simultaneously   You use this to limit the number of simultaneous user requests, and the value seen here is the same as the settings specified for the MaxClients directive (UNIX) and the ThreadsPerChild directive (Windows).
  2. Request Timeout    This value is the same as the Timeout directive setting.
  3. Limit Requests Handled by Each Child Server Process    This value is the same as the setting of the configuration directive MaxRequestsPerChild on UNIX hosts and is unavailable on Windows hosts.

Client Connection Settings

The Client Connection Settings section shows you various client connection settings such as the following:

  • Allow Multiple Requests per Connection   This value is equivalent to the setting for the KeepAlive directive.
  • Connection Timeout    This specifies the number of seconds an idle connection will remain open, and its value is equivalent to the KeepAliveTimeout directive setting.
  • Limit Requests per Connection    This specifies the maximum simultaneous requests per connection, and its value is equivalent to the setting of the MaxKeepAliveRequests directive.

>>> More Oracle Articles          >>> More By McGraw-Hill/Osborne

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort


- Oracle Java Security Woes Continue
- Oracle's New IaaS Cloud Option: There's a Ca...
- Oracle Acquires Eloqua to Boost Cloud Presen...
- Choosing Innovation: Oracle Survey Insights
- Oracle Fixes Privilege Escalation Bug
- Oracle`s Communications Service Availability...
- Oracle Releases Exalytics, Taleo Plans
- Oracle Releases Communications Network Integ...
- Oracle Releases Communications Data Model 11...
- Oracle Releases PeopleSoft PeopleTools 8.52
- Oracle Integrates Cloudera Apache Distro, My...
- Oracle Releases MySQL 5.5.18
- Oracle Announces NoSQL Database Availability
- Sorting Database Columns With the SELECT Sta...
- Retrieving Table Data with the LIKE Operator

Developer Shed Affiliates


Dev Shed Tutorial Topics: