4-8 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server
ServerAdmin WebMasterexample.com
4.
In the DirectoryIndex section of the file, enter the directory index. This is the main index page that will be displayed when a client first accesses the Web site.
The following is an example of the syntax:
DirectoryIndex index.html index.html.var
5.
In the User and Group section of the file, enter the user name and group. The following is an example of the syntax:
User nobody Group nobody
The user name is for the server, when sending and responding to requests. The user should not have privileges that allow it to access files or run programs that
are for internal-use only. For example, when a request comes from Oracle Portal, Oracle HTTP Server will respond as the user defined in this field, and should have
privileges to access the content in Oracle Portal. However, the user should not have privileges to access company-confidential content.
Oracle recommends that you set up a group specifically for running the server. The user defined for Oracle HTTP Server must be a member of this group. Oracle
also recommends that you do not set the group as root.
6.
Create aliases, if needed. An alias maps to a specified directory. For example, to use a specific set of icons, you can create an alias to the directory that has the icons
for the Web pages. The following is an example of the syntax:
Alias icons {ORACLE_HOME}config{COMPONENT_TYPE}{COMPONENT_ NAME
}icons Directory {ORACLE_HOME}content{COMPONENT_TYPE}{COMPONENT_NAME}icons
Options MultiViews Order allow, deny
Allow from all Directory
7.
Save the file.
8.
Restart Oracle HTTP Server. See Section 4.1.4
.
4.4 Configuring Oracle HTTP Server
This section includes the following sections:
■
Section 4.4.1, Configuring Secure Sockets Layer
■
Section 4.4.2, Configuring MIME Settings
■
Section 4.4.3, Configuring the mod_perl Module
■
Section 4.4.4, Configuring the mod_wl_ohs Module
■
Section 4.4.5, Enabling the mod_osso Module
■
Section 4.4.6, Modifying an Oracle HTTP Server Configuration File
Note: User and Group are relevant only when running Oracle
HTTP Server as root on UNIX.
Getting Started with Oracle HTTP Server 4-9
■
Section 4.4.7, Disabling the Options Method
4.4.1 Configuring Secure Sockets Layer
Secure Sockets Layer SSL is an encrypted communication protocol that is designed to securely send messages across the Internet. It resides between Oracle HTTP Server on
the application layer and the TCPIP layer, transparently handling encryption and decryption when a secure connection is made by a client.
One common use of SSL is to secure Web HTTP communication between a browser and a Web server. This case does not preclude the use of non-secured HTTP. The
secure version is simply HTTP over SSL HTTPS. The differences are that HTTPS uses the URL scheme https: rather than http:.
By default, an SSL listen port is configured and enabled using a default wallet
during Oracle HTTP Server installation. Wallets store your credentials, such as certificate
requests, certificates, and private keys. The default wallet that is automatically installed with Oracle HTTP Server is for
testing purposes only. A real wallet must be created for your production server. The default wallet is located in the ORACLE_INSTANCEconfigOHSohs_
namekeystoresdefault directory. You can either place the new wallet in this location, or change the SSLWallet directive in ORACLE_
INSTANCE
configOHSohs_namessl.conf to point to the location of your real wallet.
4.4.1.1 Using Fusion Middleware Control to Configure a Wallet and SSL
For instructions on configuring wallets and SSL using Fusion Middleware Control, see Enabling SSL for Oracle HTTP Server Virtual Hosts in the Oracle Fusion Middleware
Administrators Guide.
4.4.2 Configuring MIME Settings
Multipurpose Internet Mail Extension MIME settings are used by Oracle HTTP Server to interpret file types, encodings, and languages. MIME settings for Oracle
HTTP Server can only be set using Fusion Middleware Control. You cannot specify the MIME settings using opmnctl commands.
The following tasks can be completed on the MIME Configuration page:
■
Configuring MIME Types
■
Configuring MIME Encoding
■
Configuring MIME Languages
4.4.2.1 Configuring MIME Types
MIME type maps a given file extension to a specified content type. The MIME type is used for filenames containing an extension.
4.4.2.1.1 Using Fusion Middleware Control to Configure MIME Types To configure a MIME
type using Fusion Middleware Control, do the following:
1. Select Administration from the Oracle HTTP Server menu.
2. Select MIME Configuration from the Administration menu. The MIME
configuration page appears.
