7
Application Server Control Management

This chapter provides information for managing Oracle HTTP Server using Oracle Enterprise Manager Application Server Control.

Topics discussed are:

• Overview

• Accessing Application Server Control

• Accessing Oracle HTTP Server Home Page

• Managing Oracle HTTP Server

Documentation from the Apache Software Foundation is referenced when applicable.

Note: Readers using this guide in PDF or hard copy formats will be unable to access third-party documentation, which Oracle provides in HTML format only. To access the third-party documentation referenced in this guide, use the HTML version of this guide and click on the hyperlinks.

Overview

You can manage Oracle HTTP Server in two ways: using Oracle Enterprise Manager, or using command-line utilities such as opmnctl and dcmctl. The sections below provide information on managing Oracle HTTP Server using Oracle Enterprise Manager.

Oracle Enterprise Manager enables you to manage Oracle HTTP Server from a Web browser using Oracle Enterprise Manager Application Server Control. Application Server Control is installed with each instance of Oracle Application Server, enabling you to administer and monitor a single Oracle Application Server instance. You can access and manage the Oracle HTTP Server from the Application Server Control, as described in the sections below.

See Also: "Oracle Application Server Command-line Tools" for more information on management using opmnctl and dcmctl. Oracle Application Server 10g Administrator's Guide for more information on Oracle Enterprise Manager and Application Server Control.

Accessing Application Server Control

After installation, you can access the Application Server Control from the URL specified in setupinfo.txt file. It is located in ORACLE_HOME/Apache/Apache on UNIX or ORACLE_HOME\Apache\Apache on Windows.

setupinfo.txt also contains the URL for Oracle Application Server Welcome page. You can access the Application Server Control by clicking on the "Login to Oracle Enterprise Manager" link on the Oracle Application Server Welcome page. Enter the username, which is ias_admin, and the password, which is specified during the installation process, to access the Application Server Control.

Note: During installation, the Oracle Universal Installer's "End of Installation" screen also contains the location of the Application Server Control and Oracle Application Server Welcome page.

See Also: Oracle Application Server 10g Administrator's Guide for detailed information on accessing Application Server Control.

Accessing Oracle HTTP Server Home Page

Oracle HTTP Server Home page enables you to perform tasks such as monitor the status and performance of your server, start and stop the server, create virtual hosts, modify configuration files, change log properties, manage client requests, and specify a port for a listener.

You can access the Oracle HTTP Server Home page by clicking on the "HTTP Server" link in the Name column of the "System Components" table on the Application Server Control.

Figure 7-1 displays the Oracle HTTP Server Home page.

Figure 7-1 Oracle HTTP Server Home Page

Text description of the illustration httphomepage.gif

Managing Oracle HTTP Server

The Oracle HTTP Server Home page is divided into three sections: Home, Virtual Hosts, and Administration, where you can perform tasks such as:

• Performing Basic Administration

• Managing Virtual Hosts

• Administering Oracle HTTP Server

  Note: Click on Help on the browser page you are on to get additional information about the functionality provided on that page.

Performing Basic Administration

You can perform the following basic administration tasks under the "Home" tab of the Oracle HTTP Server Home page:

• Starting, Restarting, and Stopping Oracle HTTP Server

• Managing Default Server Configuration

• Monitoring Status

• Monitoring Response and Load

• Monitoring Performance

Starting, Restarting, and Stopping Oracle HTTP Server

You can start, restart, or stop the server under the "Home" tab of Oracle HTTP Server Home page. To do so, click on the appropriate button in the "General" section. You can also see the status, and the start time in this section.

Managing Default Server Configuration

You can verify the name of the server, the path of the document root, and the time the server was last modified on the "Default Server Configuration" section under the "Home" tab of the Oracle HTTP Server Home page.

See Also: "Modifying the Document Root, Administrator E-mail, User, and Group Settings" to modify these settings.

Monitoring Status

You can monitor the heap usage, CPU usage, memory usage, error rate, number of active connections, and the time the connections have been open, on the "Status" section under the "Home" tab of the Oracle HTTP Server Home page.

Monitoring Response and Load

You can monitor the number of active requests, the request throughput time, request processing time, data throughput, and data processed on the "Response and Load" section under the "Home" tab of the Oracle HTTP Server Home page.

Monitoring Performance

You can view the general server status, and the response and load information under the "Home" tab on Oracle HTTP Server Home page.

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 on "Status Metrics" under the "Performance" section to view detailed status details.

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 on "Response and Load Metrics" under the "Performance" section to view detailed response and load information.

Module Metrics

The "Module Metrics" section allows 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.

Error Log

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

Managing Virtual Hosts

Figure 7-2 displays the Virtual Hosts page. You can view the Virtual Hosts page by clicking on the "Virtual Hosts" tab on the Oracle HTTP Server Home page. The following topics are discussed in this section:

• Requirements for Managing Virtual Hosts

• Performing Basic Tasks on Virtual Hosts Page

• Modifying Virtual Hosts

• Administering Virtual Hosts

  Note: Click on Help on the browser page you are on to get additional information about the functionality provided on that page.

  Figure 7-2 Virtual Hosts Page

  

  Text description of the illustration virtualpage.gif

Requirements for Managing Virtual Hosts

Virtual hosts that meet the following requirements can be managed by the Application Server Control:

• A ServerName directive is specified for each virtual host.

  See Also: "ServerName"

• Only a single <IP listen address>:<port> pair that meets the following requirements can be specified for the virtual host:
  • The IP listen address is either a numeric IP address, * for all addresses, or the keyword _default_.

  • The port is either a port number or * for all the ports that Oracle HTTP Server is using. Alternatively, if :<port> is omitted, the main server's default port will be used.

• The virtual host must be specified in a particular section of the configuration file, as follows:
  • Non-SSL virtual hosts must be specified at the top nesting level of the configuration file.

  • SSL virtual hosts must be specified just inside an <IfDefine SSL> directive, and that directive must be at the top nesting level of the configuration file.

    See Also: "Block Directives"

Performing Basic Tasks on Virtual Hosts Page

You can do the following on the Virtual Hosts page:

• View settings for a virtual host.

• Create a new virtual host using the Virtual Host Creating wizard. To do so, click Create.

• Create a new virtual host by modifying a copy of the settings of an existing virtual host. To do so, click Create Link. The existing virtual host is left unchanged.

• Delete a virtual host.

• Modify the settings for an existing virtual host. To do so, click on the link for the host and access modification features.

Modifying Virtual Hosts

The sections below provide information on modifying or monitoring an existing virtual host. You can monitor the following for specific virtual hosts by clicking on their link on the "Virtual Hosts" page:

• Configuration

• Request Throughput

• Load

• Request Process Time

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.

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.

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.

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.

Administering Virtual Hosts

This sections contains information about administering virtual hosts. You can perform the following administrative tasks for specific virtual hosts by clicking on their link on the "Virtual Hosts" page:

• Virtual Hosts Properties

• Virtual Host MIME Languages

• Virtual Host MIME Encoding

• Virtual Host MIME Types

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 Log Formats"

  • 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.

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 Application Server Control 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.

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 allows 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 Application Server Control 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.

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 Application Server Control 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.

Administering Oracle HTTP Server

Figure 7-3 displays the "Administration" page. You can view the "Administration" page by clicking on the "Administration" tab on the Oracle HTTP Server Application Server Control Home page. The following topics are discussed in this section:

• Server Properties

• MIME Languages

• MIME Types

• MIME Encoding

• PL/SQL Properties

• Advanced Server Properties

  Note: Click on Help on the browser page you are on to get additional information about the functionality provided on that page.

  Figure 7-3 Administration Page

  

  Text description of the illustration adminpage.gif

Server Properties

You can view and modify the following basic settings for your Oracle HTTP Server on the "Server Properties" page.

• Modifying the Document Root, Administrator E-mail, User, and Group Settings

• Specifying a Port for a Listener

• Changing the Error Log Properties

• Adding an Access Log File

• Changing the Access Log Properties

• Managing the Client Request and Connection Handling

Modifying the Document Root, Administrator E-mail, User, 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 Application Server Control 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.

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.

See Also: "Specifying Listener Ports and Addresses"

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 Application Server Control 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.

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.

See Also: "Error Log"

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" for more information on error log levels.

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 Application Server Control 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.

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.

See Also: "Access Log"

Note: At installation time, an access log with the common LogFormat is created.

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 Application Server Control 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.

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 Application Server Control 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.

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.

See Also: "Oracle HTTP Server Processing Model" for more information on child processes and child threads.

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 Application Server Control 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.

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 "MIME Language" in the "Administration" page. This opens the 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 Application Server Control 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.

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 "MIME Types" in the "Administration" page. This opens the 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 Application Server Control 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.

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 allows 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 "MIME Encoding" in the "Administration" page. This opens the 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 Application Server Control 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.

PL/SQL Properties

Oracle HTTP Server contains the mod_plsql module, which provides support for building PL/SQL-based applications on the Web. PL/SQL stored procedures retrieve data from a database, and generate HTTP responses containing data and code to display in a Web browser.

In order to use mod_plsql, you must install the PL/SQL Web Toolkit into a database, and create a Database Access Descriptor (DAD) which provides mod_plsql with connection information for the database.

See Also: "mod_plsql" for more information on installing the PL/SQL Web Toolkit into a database.

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" for more information on mod_plsql configuration parameters.

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.

Advanced Server Properties

You can access the Oracle HTTP Server configuration files directly on the Advanced Server Properties page. Use these files to customize the features of your server.

Editing the Server Configuration Files

Perform the steps below 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 Application Server Control 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.