1. Installing and Configuring Oracle HTTP Server
  2. Configuring Oracle HTTP Server in a Standalone Domain

5 Configuring Oracle HTTP Server in a Standalone Domain

After you have installed Oracle HTTP Server, you can configure it in a standalone domain.

For more information on other methods available for domain creation, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.

Note:

Perform the configuration steps in this section only if you have selected Standalone HTTP Server (Managed independently of WebLogic server) in the Installation Type screen. If you have selected Collocated HTTP Server (Managed through WebLogic server), see Configuring Oracle HTTP Server in a Collocated Domain.

For information about Oracle HTTP Server domain configuration options, see About Oracle HTTP Server.

The following sections step through the Configuration Wizard:

Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

  1. Change to the following directory:

    (UNIX) ORACLE_HOME/oracle_common/common/bin

    (Windows) ORACLE_HOME\oracle_common\common\bin

    where ORACLE_HOME is your 14c (14.1.2.0.0) Oracle home.

  2. Enter the following command:

    (UNIX) ./config.sh

    (Windows) config.cmd

Navigating the Configuration Wizard Screens to Configure the Domain

Use the Configuration Wizard to configure Oracle HTTP Server in a standalone domain.

Note:

When you are creating an Oracle HTTP Server instance for a new domain, verify that the ports you are assigning to your components are available. The Configuration Wizard does not perform automatic port allocation.

Selecting the Configuration Type and Domain Home Location

Use the Configuration Type screen to select a Domain home directory location, optimally outside the Oracle home directory.

Oracle recommends that you locate your Domain home in accordance with the directory structure in What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or reinstall software.

To specify the Domain type and Domain home directory:

  1. On the Configuration Type screen, select Create a new domain.
  2. In the Domain Location field, specify your Domain home directory.

For more details about this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Selecting the Configuration Template for Oracle HTTP Server

Use the Templates screen to select the template you require.

On the Templates screen, select the following template:

  • Oracle HTTP Server (Standalone) - 14.1.2.0.0 [ohs]
For more information about this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard

Specifying the JDK

Use the JDK Selection screen to select the JDK for the domain.

Select the Oracle HotSpot JDK in the JDK field.

If you select Other JDK Location, select only a JDK that is supported on the platform you are using. Always verify the required JDK version by reviewing the certification information on the Oracle Fusion Middleware Supported System Configurations page for Oracle Fusion Middleware 14c (14.1.2.0.0).

Adding System Components

Use the System Components screen to specify details about the new Oracle HTTP Server instance.

On the System Components screen:

  1. Specify ohs1 in the System Component field.

  2. Specify OHS in the Component Type field.

  3. Restart Interval Seconds: Specify the number of seconds to wait before attempting a restart if an application is not responding.

  4. Restart Delay Seconds: Specify the number of seconds to wait between restart attempts.

Note:

You can rename the Oracle HTTP Server system component name (for example, ohs_1), when you rerun the configuration wizard and select Update an existing domain in the Configuration Type screen. But when you do this, the original Oracle HTTP Server component name and all customized values, like port designation, gets deleted and a new system component with default values get created. So, avoid renaming the Oracle HTTP Server component, unless you want the default settings.

For more information about this screen, see System Components in Creating WebLogic Domains Using the Configuration Wizard.

Specifying the Oracle HTTP Server Details

Use the OHS Server screen to configure the Oracle HTTP Server instance in the domain.

In the Listen Address field, specify the IP address of the host on which the Oracle HTTP Server instance will reside. Do not use localhost. See Specifying the Listen Address in Creating WebLogic Domains Using the Configuration Wizard.

All of the remaining fields are pre-populated, but you can change the values as required. For example, verify that the default port numbers are not used by other services.

Note:

If you change the admin host from default IP address 127.0.0.1 to any other IP address, you must ensure the following:
  • Set ServerName directive in admin.conf to the host name or domain name that maps to the IP address that you have chosen.
  • Create an SSL certificate with a common name matching the host name or domain name set up using the ServerName directive.

For more information, see Configuring SSL for Admin Port in the OHS Admin Guide.

For more information about this screen, see OHS Server in Creating WebLogic Domains Using the Configuration Wizard .

Configuring Node Manager

Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Select Per Domain Default Location as the Node Manager type, then specify Node Manager credentials.

For more information about this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

For more information about Node Manager types, see About Node Manager in Administering Node Manager for Oracle WebLogic Server.

Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen shows detailed configuration information for the domain you are about to create.

Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation does not start until you click Create.

For more details about options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Starting the Instances

After configuration is complete, you can use tools to manage your domain.

Starting Node Manager

To start the per-domain Node Manager:

    • (UNIX) Go to the DOMAIN_HOME/bin directory.

    • (Windows) Go to the DOMAIN_HOME\bin directory.

  2. Enter the following command:

    • (UNIX) Using nohup and nm.out as an example output file: 

      nohup ./startNodeManager.sh > LOG_DIR/nm.out&

      where LOG_DIR is the location of directory in which you want to store the log files.

    • (Windows) startNodeManager.cmd

      Note:

      On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

      See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.

Starting the Oracle HTTP Server Instance

To start the Oracle HTTP Server instance:

  • On UNIX

    1. Go to the DOMAIN_HOME/bin directory.

    2. Modify JAVA_OPTIONS, if the domain is in the secure mode. See Understand How Domain Mode Affects the Default Security Configuration.

      Note:

      You must perform this step only if the domain is in secure production mode.

    3. Run the following command:

      ./startComponent.sh system_component_name

      where system_component_name is the Oracle HTTP Server system component name you provided while configuring the domain.

      For example:

      ./startComponent.sh ohs1

  • On Windows

    1. Go to the DOMAIN_HOME\bin directory.

    2. Run the following command:

      startComponent.cmd system_component_name

      where system_component_name is the Oracle HTTP Server system component name you provided while configuring the domain.

      For example:

      startComponent.cmd ohs1

See Starting Oracle HTTP Server Instances from the Command Line in Administering Oracle HTTP Server.

Missing Libraries Might Cause HTTPD to Exit Without Notice

On the Windows platform, Oracle HTTP Server requires certain Microsoft software to be installed in order to function properly.

If the required software is not installed, Oracle HTTP Server may exit with no output or generate an error message, depending on registry settings.

Make sure that you have installed all packages recommended by Microsoft.You can download packages from http://www.microsoft.com.