7 Application Server Control Console Management

7.4.1.5.1 Status Metrics

The "Status" section provides information such as heap usage, CPU usage, memory usage, error rate, number of active connections, and time the connections have been open.

Click "Status Metrics" under the "Performance" section to view detailed status details.

7.4.1.5.2 Response and Load Metrics

The "Response and Load" section provides information such as number of active requests, how many requests were submitted, and how long it took for the server to respond to your request. It also provides information about how many bytes of data were processed with the requests.

Click "Response and Load Metrics" under the "Performance" section to view detailed response and load information.

7.4.1.5.3 Module Metrics

The "Module Metrics" section enables you to view the status of the modules being used by clicking on "Module Metrics" under the "Performance" section. It provides information such as the number of active requests, number of requests processed since startup, number of current requests throughput, and the current request processing time.

7.4.1.5.4 Error Log

You can view the last 2000 lines of the httpds error log by clicking "Error Log" under the "Performance" section.

7.4.2.3.1 Configuration

You can verify the type, the IP address, port number, protocol, and path of the document root of the virtual host, in the "Configuration" section of the virtual host page of the virtual host you selected.

7.4.2.3.2 Request Throughput

You can monitor the number of active requests, the current throughput, the throughput since startup, and the total number of requests processed since startup, in the "Request Throughput" section of the virtual host page of the virtual host you selected.

7.4.2.3.3 Load

You can monitor the current data throughput, the data throughput since startup, current response size, average response size since startup, and the total data since startup, in the "Load" section of the virtual host page of the virtual host you selected.

7.4.2.3.4 Request Process Time

You can monitor the current processing time, and the average processing time since startup, in the "Request Processing Time" section of the virtual host page of the virtual host you selected.

7.4.2.4.1 Virtual Hosts Properties

You can view or modify the following settings on General section of the Virtual Hosts Properties page:

• Virtual Host Type: Displays the type of virtual host. The possible types are name-based, IP-based, or default.

• Server Name: Displays the server name for the virtual host.

• Document Root: Displays the path of the directory from which the server serves files. Note that the document root directory is different from the server root directory, which is only used to store the server files. You can specify the directory using the DocumentRoot directive.

• Directory Index: Specifies the resource or resources that Oracle HTTP Server will look for when the client requests the index of a directory by specifying a slash (/) at the end of the directory name.

• Administrator Email: Displays the server's main contact. This address receives notifications if the server experiences error conditions.

• IP Address: Specifies the IP address or addresses on which you want the virtual host to listen. The IP address you specify for the virtual host must already exist for Oracle HTTP Server.

• Listening Ports: Specifies the port or ports on which you want the virtual host to listen. Any ports you specify for the virtual host must already exist for Oracle HTTP Server. Ports for Oracle HTTP Server appear in the Listening Addresses/Ports section of the Server Properties page.

  
  

  See Also: "Specifying a Port for a Listener"

  
  

• Protocol: Displays the protocol settings.

  You can also modify the SSL Wallet path if the virtual host is using the HTTPS protocol, which uses SSL for secure connections. Note that SSL is supported for default virtual hosts and IP-based virtual hosts, but not for name-based virtual hosts.

  The value of the SSL Wallet field corresponds to the SSLWallet entry in httpd.conf file. The path to the SSL Wallet must be in the form of a valid Wallet Resource Locator.

  
  

  See Also: "SSLWallet"

  
  

• Logging: Provides access to the server's error log files and access log files.

  The error log file is an important source of information for maintaining a well-performing server. The error log records all of the information about problem situations so that the system administrator can easily diagnose and fix the problems.

  To provide access to the error log file--without providing access to all of the other configuration files--you may need to move the error log file to a shared directory.

  The access log file contains basic information about every HTTP transaction that the server handles. This information can be used to generate statistical reports about the server's usage patterns.

  In addition to viewing error log files and access log files in the Logging section, you can also perform these tasks for the virtual host:

  Choose a logging level for the error log file.

  
  

  See Also: "Specifying Log Level"

  
  

  Setting the error logging level to Notice, Informational, or Debug tends to flood the error log with unimportant informational messages.

  • Change the error log file name or location

  • Remove an access log file

  • Change an access log file name or location

  • Change the log format of an access log file

    
    

    See Also: "Specifying LogFormat"

    
    

  • Add an access log file (click Add Another Row) and specify a log format and location for it

  When you specify a location for an error log file or access log file, you can enter an absolute path and file name or a relative path and file name for the file. A relative path will be relative to the Server Root directory specified during initial configuration. The Server Root directory is displayed in the General section.

7.4.2.4.2 Virtual Host MIME Languages

The Multipurpose Internet Mail Extension (MIME) Language setting maps the given file extensions to a particular language. This directive is used most commonly for content negotiation, where the Oracle HTTP Server returns the document that most closely matched the preferences set by the client.

To add a new MIME Language:

1. Select "Virtual Hosts MIME Languages" under the Administration section. This opens the Virtual Hosts MIME Languages page.

2. Enter the new language code in the Standard Language code field. Examples include en for English, fr for French, and es for Spanish.

3. Enter the types of files that should be opened with the language code in the File Extension(s) field. The extension argument is case-insensitive, and can be specified with or without a leading period. Examples include .en, .fr, and .es.

4. In the Default Language Code field, enter the default language type that should be used if no language is specified.

5. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

6. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

To remove a MIME language, select it and click Remove.

7.4.2.4.3 Virtual Host MIME Encoding

The Multimedia Internet Mail Extension (MIME) mapping allows the Oracle HTTP Server to determine the type of file from the given extension. As part of its MIME support, Oracle HTTP Server enables you to add or remove MIME encodings. The Encoding directive maps the given filename extensions to the specified encoding type.

To add a new MIME encoding:

1. Select "Virtual Hosts MIME Encoding" under the Administration section. This opens the Virtual Hosts MIME Encoding page.

2. Click Add Another Row.

3. Enter the new encoding type in the Encoding field. Examples include x-gzip, and x-compress.

4. Enter the types of files that should be opened with the encoding type in the File Extension(s) field.The extension argument is case-insensitive, and can be specified with or without a leading period.

5. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

6. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

To remove a MIME encoding, select it and click Remove.

7.4.2.4.4 Virtual Host MIME Types

The Multipurpose Internet Mail Extension (MIME) type maps the given filename extensions onto the specified content type. The MIME type is used for filenames containing an extension. This mapping is added to any extension already in use, overriding any mappings that already exist for the same extension.

To add a new MIME type:

1. Select "Virtual Hosts MIME Types" under the Administration section. This opens the Virtual Hosts MIME Types page.

2. Click Add Another Row.

3. Enter the new MIME type in the MIME type field. Examples include: text/plain, text/.html, and image/.gif.

4. Enter the types of files in the File Extension(s) field that should be opened with the MIME type. The extension argument is case-insensitive, and can be specified with or without a leading period. Examples include .txt, .html, and .gif.

5. In the Default MIME Type field, enter the default MIME type that should be used for unknown file types.

6. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

7. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

To remove a MIME type, select it and click Remove.

7.4.3.1.1 Modifying the DocumentRoot, Administrator E-mail, and Group Settings

After you start Oracle HTTP Server, the system is ready to listen for and respond to requests. You may need to make modifications to the document root, administrator email, User, and Group settings in order to process requests efficiently.

• Document Root: The directory from which the server serves files. Note that the document root directory is different from the server root directory, which is only used to store the server files. You can specify the directory using the DocumentRoot directive.

• Administrator Email Address: The server's main contact. This address receives notifications if the server experiences error conditions.

• User: Specifies the user ID to which the server answers requests. This directive is only used on UNIX systems. You should have privileges to access files that are available for everyone, and should be able to execute code which is not meant for HTTP requests. It is recommended that you set up a new user for running the server.

• Group: Specifies the group under which the server answers requests. This directive is only used on UNIX systems. It is recommended that you create a new group for running the server.

To modify these settings:

1. Select "Server Properties" under the "Administration" page. This opens the Oracle HTTP Server Properties page.

2. Type a new path in the "Document Root" field to change the document root directory. The path should be relative to the Server Root directory specified during initial configuration.

3. Type the appropriate email address in the "Administrator Email" field. Oracle HTTP Server uses this email address to issue notices and warnings. The administrator should have full privileges.

4. Add or change the User identifier by typing a new user name in the fields provided.

5. Add or change the Group identifier by typing a new group name in the fields provided.

6. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

7. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

7.4.3.1.2 Specifying a Port for a Listener

When you start Oracle HTTP Server, it connects to a port and awaits client requests. Oracle HTTP Server automatically attempts to listen on port 7777.

To specify a listener port:

1. Select "Server Properties" in the "Administration" page. This opens the Server Properties page.

2. Scroll down to the Listening Addresses/Ports table.

   The first row in the Listening Addresses/Ports table identifies the default listener port. To edit the default listener port, edit the number in the Listening Port column.

   To add port settings, click Add Another Row to add a new row to the table. Enter the IP address and/or port number to the new row.

3. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

4. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

7.4.3.1.3 Changing the Error Log Properties

You can change Error Log properties from the Oracle HTTP Server Home page. The Error Log file is an important source of information for maintaining a well-performing server. The Error Log records all of the information about problem situations so that you can easily diagnose and fix the problems.

To customize the error log properties:

1. Select "Server Properties" in the "Administration" page. This opens the Server Properties page.

2. Scroll to the "Logging" section of the Server Properties page.

3. Type the full path name of the directory where you want to keep the error log file in the Error Log Filename field. You can also type the relative path name. A relative path is assumed to be relative to the Server Root directory.

4. Select the logging level from the Error Logging Level drop-down menu. The logging level indicates the severity of the error being reported.

   
   

   Note: Setting the log level to notice, info, or debug tends to flood the error log with informational messages. Use these options only if you need to perform a very detailed analysis or to debug a specific performance problem.

   
   
   
   

   See Also: "Using Oracle Diagnostic Logging"

   
   

5. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

6. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

7.4.3.1.4 Adding an Access Log File

You can change Access Log properties from the Oracle HTTP Server Home page. The Access Log contains basic information about every HTTP transaction that the server handles. Specifically, the access log file contains hostname, remote logname, remote user, time, request, response code, and bytes transferred. This information can be used to generate statistical reports about the server's usage patterns.

To create an access log file:

1. Select "Server Properties" in the "Administration" page. This opens the Server Properties page.

2. Scroll to the Logging section of the Server Properties page.

3. Click Add Another Row in the Select Access Log table to add a new row. When the page reloads, scroll back to the Logging section.

4. Type the full path and filename of the access log file you want to create in the empty field. For example, you can type the following location:

   • UNIX: ORACLE_HOME/Apache/Apache/logs/access_log

   • Windows: ORACLE_HOME\Apache\Apache\logs\access_log

   You can enter an absolute path or a relative path. A relative path will be relative to the Server Root directory specified during initial configuration.

5. Set the log format by typing a new format name. The default is common. For information on creating custom log formats, go to "Adding an Access Log File" from the online help for the Server Properties page.

   
   

   Note: For a full description of the available log formats, click Help at the top of the Server Properties page.

   
   

6. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

7. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

7.4.3.1.5 Changing the Access Log Properties

To change access log properties:

1. Select "Server Properties" in the "Administration" page. This opens the Server Properties page.

2. Scroll to the Logging section of the Server Properties page.

3. Select the Client Access Log file you want to relocate in the Select Access Log section.

4. Type the new destination in the Client Access Log Filename field. The destination can be the full path and filename, or a relative path and filename. A relative path is assumed to be relative to the Server Root directory.

5. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

6. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

7.4.3.1.6 Managing the Client Request and Connection Handling

You can specify how the child processes on UNIX, child threads on Windows, and connections should initialize resources during the server's processing phase through the Oracle HTTP Server Home page. The Child Process and Connection settings impact the ability of the server to process requests. You may need to modify these settings as the number of requests increases or decreases to maintain a well-performing server.

To modify child process and connection settings:

1. Select "Server Properties" in the "Administration" page. This opens the Server Properties page.

2. Scroll to the Client Request Handling or Client Connection Handling sections of the Server Properties page.

3. Modify the Client Request Handling and Client Connections Handling directives by changing the default values in the appropriate fields.

   For help on individual settings, click Help at the top of the Server Properties page.

4. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

5. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.

7.4.3.5.1 Creating a Database Access Descriptor (DAD) for mod_plsql

You can create a DAD using Oracle HTTP Server Home page:

1. Select "PL/SQL Properties" in the "Administration" page. This opens the mod_plsql Services page.

2. On the mod_plsql Services page, scroll to the DAD Status section. Click Create. This opens the DAD Type page.

3. If you intend to use mod_plsql with Oracle Application Server Portal or Oracle Login Server, select the Portal radio button. Otherwise, select the General radio button. The subsequent screens are populated with default values based on your selection. Click Next. This opens the Database Connection page.

4. Type a unique name in the DAD Name field. Enter the database account, password, and connection information in the Database Connectivity Information section. In the Default page field, type the name of the PL/SQL procedure that should be invoked when one is not specified. In the NLS Language field, type the Oracle Language and Character Set for the back-end database. Choose an Authentication Mode in the Authentication Mode section. Click Next. This opens the Document, Alias, and Session page.

5. On the Document, Alias, and Session page, fill in the fields that are required for your DAD configuration. Click Next. This opens the Advanced page.

6. On the Advanced page, fill in the fields that are required for your DAD configuration. These fields are typically not configured. Refer to the online help for more information. Click Finish. This opens the Confirmation page. Click OK.

7. Restart Oracle HTTP Server.

   
   

   See Also: "mod_plsql"

   
   

7.4.3.5.2 Deleting a Database Access Descriptor (DAD) for mod_plsql

You can delete a DAD using the Oracle HTTP Server Home page:

1. Select "PL/SQL Properties" in the "Administration" page. This opens the mod_plsql Services page.

2. On the mod_plsql Services page, scroll to the DAD Status section. Select the radio button in the Select column for the DAD you would like to delete. Click Delete.

3. Restart Oracle HTTP Server.

7.4.3.6.1 Editing the Server Configuration Files

Perform the following steps to modify the Oracle HTTP Server configuration files:

1. Select "Advanced Server Properties" in the "Administration" section. This opens the Advanced Server Properties page.

2. Select the configuration file you want to edit. A text editor appears where you can make the appropriate changes.

3. Click Apply at the bottom of the page to accept the changes. If you do not click Apply, you will lose your changes. If you make a mistake or want to undo any changes, click Revert.

   Oracle Enterprise Manager 10g Application Server Control Console displays a confirmation page, which confirms that the appropriate configuration files have been updated.

4. Click Yes to restart the Oracle HTTP Server so the changes will take effect. Click No to restart the server later.