To specify the Domain type and Domain home directory:

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

On the Templates screen, select one of the following templates:

• For a Full-JRF configuration, select Oracle HTTP Server (Collocated) - 14.1.2.0.0 [ohs].

• For a Restricted-JRF configuration, select Oracle HTTP Server (Restricted JRF) - 14.1.2.0.0 [ohs].

  Selecting this template automatically selects the following as dependencies:

  • Oracle Enterprise Manager-Restricted JRF

  • Oracle Restricted JRF

  • WebLogic Coherence Cluster Extension

If you are unsure what operational mode you want, see About Full-JRF and Restricted-JRF Modes for an overview of both modes.

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

  Note:

  As of WebLogic Server 14.1.2.0.0, when you select Production mode, WebLogic Server automatically sets some of the security configurations of Secured Production to more secure values. However, there are certain security configurations (such as SSL/TLS) that require manual configuration. See Using Secured Production Mode in Administering Security for Oracle WebLogic Server.

  The port configuration in Oracle HTTP Server should be consistent with the port configuration in WebLogic Server. For example, if the SSL ports are enabled and Listen ports (non-SSL) are disabled in Oracle HTTP Server, then the SSL ports should also be enabled in WebLogic Server.

  If you want to disable the more secure default settings, then you may select Disable Secure Mode. This will enable the non-SSL listen ports.

  If you want to retain the more secure default settings of Secured Production mode in general, but want to change which ports (listen ports, SSL listen ports, or administration ports) will be enabled by default in your domain, then you may:

  • Leave Disable Secure Mode unselected, and
  • Change the default port selections under Enable or Disable Default Ports for Your Domain

  For more information, see Understand How Domain Mode Affects the Default Security Configuration in Securing a Production Environment for Oracle WebLogic Server.

• Select the Oracle HotSpot JDK in the JDK field.

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.

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.

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.

For an Autonomous Transaction Processing database (both Autonomous Transaction Processing-Dedicated (ATP-D) and Autonomous Transaction Processing Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format:

@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass TNS_alias as the database service name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

Example connect string for Autonomous Transaction Processing-Dedicated (ATP-D) database:

@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

Example connect string for Autonomous Transaction Processing Shared (ATP-S) database:

@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

• Configuring Active GridLink Data Sources with Oracle RAC

• Configuring Multi Data Sources

See JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard for more details about this screen.

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.

For more information about this screen, see JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard.

On the Advanced Configuration screen, select:

• System Components

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.

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

On the Assign System Components to Machines screen:

1. In the Machine list box, select the machine (for example, infra_machine_1) to which you want to assign the Oracle HTTP Server instance.

2. Assign the Oracle HTTP Server instance to the selected machine in one of the following ways:

   • Double-click ohs1 in the System Components list box.

   • Select the ohs1 in the System Components list box and click the right arrow.

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.

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.

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

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.

The procedures in this section describe how to start the Administration Server using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.