Note:
Perform the configuration steps in this section only if you selected Collocated HTTP Server (Managed through WebLogic server) in the Installation Type screen. If you selected Standalone HTTP Server (Managed independently of WebLogic server), see Configuring Oracle HTTP Server in a Standalone Domain.
For information about Oracle HTTP Server domain configuration options, see About Oracle HTTP Server.
If you have not created the Oracle Fusion Middleware Infrastructure domain, you can create it at the same time as Oracle HTTP Server. For instructions, see Configuring the Oracle Fusion Middleware Infrastructure Domain in Installing and Configuring the Oracle Fusion Middleware Infrastructure. However, in Selecting Advanced Configurations, ensure that you select System Components too.
Before starting the configuration wizard, it is important to shut down the Administration Server. This prevents any configuration locks, saves, or activations from occurring during the configuration of the domain.
To stop the Administration Server, go to the DOMAIN_HOME/bin directory.
On UNIX operating systems:
./stopWebLogic.sh
On Windows operating systems:
stopWebLogic.cmd
You may be prompted for the login credentials of the Administrator user you provided when you configured the Oracle Fusion Middleware Infrastructure domain.
Start the Configuration Wizard to begin configuring a domain.
To start the Configuration Wizard:
Use the Configuration Wizard to extend an existing Infrastructure domain with an Oracle HTTP Server instance.
Note:
When you are adding an Oracle HTTP Server instance to an existing domain, verify that the ports you are assigning to any new components are available. The Configuration Wizard does not perform automatic port allocation.
The following sections step through the Configuration Wizard:
You must specify the domain to be updated with Oracle HTTP Server.
To specify the Domain type and Domain home directory:
Tip:
For more information, see About the Domain Home Directory.
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 Update Domain Using Product Templates is selected, then select one of the following templates:
For a Full-JRF configuration, select Oracle HTTP Server (Collocated) - 12.2.1.3.0 [ohs].
For a Restricted-JRF configuration, select Oracle HTTP Server (Restricted JRF) - 12.2.1.3.0 [ohs].
If you are unsure what operational mode you want, see Understanding Full-JRF and Restricted-JRF Modes for an overview of both modes.
Tip:
For more information about this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.
Use the Database Configuration type screen to specify details about the database and database schema.
On the Database Configuration type screen, all fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain. Verify and ensure that credentials in all the fields are the same that you have provided while configuring Oracle Fusion Middleware Infrastructure.
Verify the database connection information, then select Get RCU Configuration. The following output in the Connection Result Log indicates that the operation succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the schema installed when RCU is run, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.
For more information about this screen, see Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Use the JDBC Component Schema screen to verify or specify details about the database schemas.
Verify that the values populated on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.
Tip:
For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:
For more information about this screen, see JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
Use the JDBC Component Schema Test screen to test the data source connections.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.
Tip:
For more information about this screen, see JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard .
Use the Advanced Configuration screen to complete the domain configuration.
On the Advanced Configuration screen, select:
System Components
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 Assign System Components to Machines screen to assign Oracle HTTP Server system components to the machine that you defined when you configured the initial Fusion Middleware Infrastructure domain..
On the Assign System Components to Machines screen:
In the Machine list box, select the machine (for example, infra_machine_1) to which you want to assign the Oracle HTTP Server instance.
Assign the Oracle HTTP Server instance to the selected machine in one of the following ways:
Double-click ohs_1 in the System Components list box.
Select the ohs_1 in the System Components list box and click the right arrow.
Tip:
You can associate an Oracle HTTP Server machine to an existing machine or create a new machine. You typically create additional machines when you are planning to scale out the topology to multiple host computers. For more information, see Scaling Out a Topology (Machine Scale Out) in High Availability Guide.
The Configuration Summary screen has detailed configuration information for the domain you are about to extend.
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 update does not start until you click Update.
Tip:
For more information about this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The End of Configuration screen shows information about the domain you just configured.
Make a note of the following items because you need them later:
Domain Location
Administration Server URL
You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.
Click Finish to dismiss the Configuration Wizard.
After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.
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.
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 Administration Server, go to the DOMAIN_HOME/bin directory.
On UNIX operating systems, run:
./startWebLogic.sh
On Windows operating systems, run:
startWebLogic.cmd
If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.
Tip:
For more information about starting the Administration Server, see Starting and Stopping Administration Servers in Administering Oracle Fusion Middleware.
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.
You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the Configuration Success screen, as described in “Writing Down Your Domain Home and Administration Server URL” in Navigating the Configuration Wizard Screens to Configure the Domain (http://administration_server_host:administration_server_port/console). The default Administration Server port number is 7001.
Note:
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.
To start the Oracle HTTP Server instance:
Log in to Oracle Fusion Middleware Control:
http://administration_server_host:administration_server_port/em
The Administration Server host and port number were in the URL on the Configuration Success screen. The default Administration Server port number is 7001.
The login credentials were provided on the Administrator Account screen while installing.
Click WebTier in the navigation panel on the left side.
Select the Oracle HTTP Server instance you want to start (for example, ohs_1) and click Start Up from the top panel.
Tip:
For more information about managing Oracle HTTP Server using Oracle Enterprise Manager Fusion Middleware Control, see Manage Oracle HTTP Server in Administering Oracle Fusion Middleware with Fusion Middleware Control.
For other tools and instructions, see Starting Oracle HTTP Server Instances in Administering Oracle HTTP Server.