Getting Started with Oracle HTTP Server 4-7
3.
Enter the documentation root directory in the Document Root field that forms the main document tree visible from the Web site.
4.
Enter the e-mail address in the Administrators E-mail Address field that the server will includes in error messages sent to the client.
5.
Enter the directory index in the Directory Index field. The is the main index page that will be displayed when a client first accesses the Web site.
6.
Enter the user name in the Operating System User field. This is the user name 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 user specifically for running the server. Oracle also recommends that you do not set the user to root.
7.
Enter the group name in the Operating System Group field. This is the group for the server, when sending and responding to requests. The user defined for Oracle
HTTP Server must be a member of this group.
Oracle recommends that you set up a group specifically for running the server. Oracle also recommends that you do not set the group as root.
8.
The Modules region is used to enable or disable modules. There are three modules that you can enable or disable: mod_perl, mod_fcgi, and mod_osso.
For instructions on configuring the mod_perl module, see Configuring the mod_
perl Module on page 4-11.
9.
Create an alias, if necessary in the Aliases table. An alias maps to a specified directory. For example, to use a specific set of content pages for a group you can
create an alias to the directory that has the content pages.
10. Review the settings. If the settings are correct, then click Apply to apply the
changes. If the settings are incorrect, or you decide to not apply the changes, then click Revert to return to the original settings.
11.
Restart Oracle HTTP Server. See Section 4.1.4
. The server properties are saved, and shown on the Server Configuration page.
4.3.2 Editing the httpd.conf File to Specify Server Properties
To specify the server properties using the httpd.conf file:
1.
Open the httpd.conf file using either a text editor or the Advanced Server Configuration page in Fusion Middleware Control. See
Section 4.4.6, Modifying an Oracle HTTP Server Configuration File.
2.
In the DocumentRoot section of the file, enter the directory that stores the main content for the Web site. The following is an example of the syntax:
DocumentRoot {ORACLE_INSTANCE}config{COMPONENT_TYPE}{COMPOENT_ NAME
}htdocs
3.
In the ServerAdmin section of the file, enter the administrators e-mail address. This is the e-mail address that will appear on client pages. The following is an
example of the syntax:
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.
