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:
Start the Configuration Wizard to begin configuring a domain.
To start the Configuration Wizard:
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.
Use the Configuration Type screen to select a Domain home directory location, optimally outside the Oracle home directory.
To specify the Domain type and Domain home directory:
Tip:
For more information about this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.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 [ohs]
.
Tip:
For more information about this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.
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.
Use the System Components screen to specify details about the new Oracle HTTP Server instance.
On the System Components screen:
Click Add to create a new Oracle HTTP Server instance.
Specify ohs_1
in the System Component field.
Specify OHS
in the Component Type field.
Restart Interval Seconds: Specify the number of seconds to wait before attempting a restart if an application is not responding.
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.
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 .
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.
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.
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 Administrator's Guide for Oracle HTTP Server.
Go to the DOMAIN_HOME
/bin
directory.
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.
To start the Oracle HTTP Server instance:
On UNIX
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
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
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
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 Administrator's Guide for Oracle HTTP Server.
On the Windows platform, Oracle HTTP Server requires certain Microsoft software to be installed in order to function properly.
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:
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.