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 WebLogic Server 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.
• Navigating the Configuration Wizard Screens to Configure the Domain
  Use the Configuration Wizard to configure Oracle HTTP Server in a standalone domain.
• Starting the Instances
  After configuration is complete, you can use tools to manage your domain.

5.1 Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

1. Go to the /oracle_common/common/bin directory:

   (UNIX) ORACLE_HOME/oracle_common/common/bin

   (Windows) ORACLE_HOME\oracle_common\common\bin

   where ORACLE_HOME is your 12c (12.2.1.1) Oracle home.

2. Enter the following command:

   (UNIX) ./config.sh

   (Windows) config.cmd

5.2 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 Domain Type and Domain Home Location
  Use the Configuration Type screen to select a Domain home directory location, optimally outside the Oracle home directory.
• Selecting the Configuration Template for Oracle HTTP Server
  Use the Templates screen to select the template you require.
• Specifying the Domain Mode and JDK
  Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).
• Adding System Components
  Use the System Components screen to specify details about the new Oracle HTTP Server instance.
• Specifying the Oracle HTTP Server Details
  Use the OHS Server screen to configure the Oracle HTTP Server instance in the domain.
• 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.
• Reviewing Your Configuration Specifications and Configuring the Domain
  The Configuration Summary screen shows detailed configuration information for the domain you are about to create.

5.2.1 Selecting the Domain 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.

Tip:

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

5.2.2 Selecting the Configuration Template for Oracle HTTP Server

Use the Templates screen to select the template you require.

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following template:

• Oracle HTTP Server (Standalone) - 12.2.1.3.0 [ohs]

  .

Tip:

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

5.2.3 Specifying the Domain Mode and JDK

Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

• Select the Oracle HotSpot JDK in the JDK field.

Tip:

For more information about this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

5.2.4 Adding System Components

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

On the System Components screen:

1. Click Add to create a new Oracle HTTP Server instance.

2. Specify ohs_1 in the System Component field.

3. Specify OHS in the Component Type field.

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

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

5.2.5 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. For more information, 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.

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

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

Tip:

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

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

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

Tip:

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

5.3 Starting the Instances

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

Note:

• For more information on additional tools you can use to manage your domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.

• If you are attempting to create an Oracle HTTP Server instance that uses a TCP port in the reserved range (typically less than 1024), then you must perform some extra configuration to allow the server to bind to privileged ports. For more information, see Starting Oracle HTTP Server Instances on a Privileged Port (Unix Only) in Administering Oracle HTTP Server.

• Starting Node Manager
  
• Starting the Oracle HTTP Server Instance
  

5.3.1 Starting Node Manager

To start the per-domain Node Manager:

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

5.3.2 Starting the Oracle HTTP Server Instance

To start the Oracle HTTP Server instance:

• On UNIX

  1. Go to the Domain_Home/bin directory. Domain_Home is the complete path to the location where you have configured Oracle HTTP Server.

     For example:

     cd /user_projects/domains/base_domain/bin

  2. 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 ohs_1

• On Windows

  1. Go to the Domain_Home\bin directory. Domain_Home is the complete path to the location where you have configured Oracle HTTP Server.

     For example:

     cd \user_projects\domains\base_domain\bin

  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 ohs_1

For more information, 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 Microsoft Visual C++ run-time libraries to be installed on the system in order to function. If they are not installed, Oracle HTTP Server might exit with no output or generate an error dialog box, depending on registry settings.

5.3.2.1 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 following software is not installed, Oracle HTTP Server may exit with no output or generate an error message, depending on registry settings.

• Microsoft Visual C++ 2008 Feature Pack Redistributable Package (x64)

• Microsoft Visual C++ 2012 Feature Pack Redistributable Package (x64)

• Any other packages recommended by Microsoft

If Oracle HTTP Server fails to start and no error messages are logged by Oracle HTTP Server in the server error log or in Node Manager logs, follow this procedure to diagnose the problem:

1. Verify that the following runtime libraries are installed: Microsoft Visual C++ 2008 and 2012 Feature Pack Redistributable Package (x64)
   1. If either runtime library is missing, download it from http://www.microsoft.com
   2. After installing the package, install any service packs or other fixes to this package that are recommended by Microsoft.
   3. Try to start Oracle HTTP Server again after installing the runtime library and associated service packs or fixes..
2. Attempt to start Oracle HTTP Server from a command prompt.

   Note:

   Oracle HTTP Server does not function properly when started from a command prompt in this manner. This mechanism for starting Oracle HTTP Server is for diagnostic purposes only.
   1. Create the DOMAIN_HOME/servers/ohs-instancename/logs directory if it has not yet been created by Oracle HTTP Server.
   2. Try to start Oracle HTTP Server using Fusion Middleware Control or WLST.
   3. Copy the file DOMAIN_HOME/servers/ohs-instancename/logs/lastinvocation.log to a new file startohs.cmd.
   4. Open a new command prompt and run startohs.cmd in that new command prompt.
   5. If it generates error messages after the script runs, use those messages to diagnose the startup failure.
   6. If it does not generate error messages after the script runs, proceed to the next step.
3. Collect Windows error information when attempting to start Oracle HTTP Server.

   Error reporting for Oracle HTTP Server library errors may be inhibited on your system. Refer to the following Microsoft article for information on verifying or correcting error reporting:

   "HOWTO: How To Change Hard Error Popup Handling in Windows NT" at http://support.microsoft.com/kb/128642

   1. Change ErrorMode to the desired value.

      • The default mode is 1, which means library errors are not reported for Oracle HTTP Server.

      • Change the mode to 2 to enable reporting to the Windows event log. This is the recommended setting for this task.

      • Change the mode to 0 to enable hard error pop-ups. If this is changed to 0, set it back to the previous value immediately after collecting diagnostic information as it can result in operational problems if errors occur when the server is unattended.

   2. Try to start Oracle HTTP Server using Fusion Middleware Control or WLST or the startohs.cmd script which was created in the previous step.
   3. Check for diagnostic information in a hard error popup or in the Windows event log, depending on the setting of ErrorMode.

      To check the Windows event log, open Windows Event Viewer and view the logs for Event Viewer (Local) / Windows Logs / Application

      Find the event log entries written at the time of the attempt to start Oracle HTTP Server.

      Errors locating runtime libraries might be reported as SideBySide errors with event ids 33 or 35, which text describing the Oracle library attempting to load the library and the specific library being loaded. Example:

      level=Error
      Source=SideBySide
      Event Id = 33
      Activation context generation failed for "C:\work\Oracle\MD1212\ORACLE~1\bin\oraiau.dll".
      Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="amd64",
      publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found.
      Please use sxstrace.exe for detailed diagnosis.
      

      The indicated library must be installed. This example shows VC90, which is the Microsoft Visual C++ 2008 library described in Step 1 above.

   4. Restore ErrorMode to the previous setting.

5.3.2.2 Missing Libraries Might Cause HTTPD to Exit Without Notice

On the Windows platform, Oracle HTTP Server requires Microsoft Visual C++ run-time libraries to be installed on the system in order to function. If they are not installed, Oracle HTTP Server might exit with no output or generate an error dialog box, depending on registry settings.

If Oracle HTTP Server fails to start and no error messages are logged by Oracle HTTP Server in the server error log or in Node Manager logs, follow this procedure to diagnose the problem:

1. Verify that the following run-time library is installed: Microsoft Visual C++ 2008 Feature Pack Redistributable Package (x64)
   1. If this run-time library is missing, download it from http://www.microsoft.com
   2. After installing this package, install any service packs or other fixes to this package which are recommended by Microsoft.
   3. Try to start Oracle HTTP Server again after installing the run-time library and associated service packs or fixes..
2. Attempt to start Oracle HTTP Server from a command prompt.

   Note:

   Oracle HTTP Server does not function properly when started from a command prompt in this manner. This mechanism for starting Oracle HTTP Server is for diagnostic purposes only.
   1. Create the DOMAIN_HOME/servers/ohs-instancename/logs directory if it has not yet been created by Oracle HTTP Server.
   2. Try to start Oracle HTTP Server using Fusion Middleware Control or WLST.
   3. Copy the file DOMAIN_HOME/servers/ohs-instancename/logs/lastinvocation.log to a new file startohs.cmd.
   4. Open a new command prompt and run startohs.cmd in that new command prompt.
   5. If it generates error messages after the script runs, use those messages to diagnose the startup failure.
   6. If it does not generate error messages after the script runs, proceed to the next step.
3. Collect Windows error information when attempting to start Oracle HTTP Server.

   Error reporting for Oracle HTTP Server library errors may be inhibited on your system. Refer to the following Microsoft article for information on verifying or correcting error reporting:

   "HOWTO: How To Change Hard Error Popup Handling in Windows NT" at http://support.microsoft.com/kb/128642

   1. Change ErrorMode to the desired value.

      • The default mode is 1, which means library errors are not reported for Oracle HTTP Server.

      • Change the mode to 2 to enable reporting to the Windows event log. This is the recommended setting for this task.

      • Change the mode to 0 to enable hard error pop-ups. If this is changed to 0, set it back to the previous value immediately after collecting diagnostic information as it can result in operational problems if errors occur when the server is unattended.

   2. Try to start Oracle HTTP Server using Fusion Middleware Control or WLST or the startohs.cmd script which was created in the previous step.
   3. Check for diagnostic information in a hard error popup or in the Windows event log, depending on the setting of ErrorMode.

      To check the Windows event log, open Windows Event Viewer and view the logs for Event Viewer (Local) / Windows Logs / Application

      Find the event log entries written at the time of the attempt to start Oracle HTTP Server.

      Errors locating run-time libraries might be reported as SideBySide errors with event ids 33 or 35, which text describing the Oracle library attempting to load the library and the specific library being loaded. Example:

      level=Error
      Source=SideBySide
      Event Id = 33
      Activation context generation failed for "C:\work\Oracle\MD1212\ORACLE~1\bin\oraiau.dll".
      Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="amd64",
      publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found.
      Please use sxstrace.exe for detailed diagnosis.
      

      The indicated library must be installed. This example shows VC90, which is the Microsoft Visual C++ 2008 library described in Step 1 above.

   4. Restore ErrorMode to the previous setting.