This section contains the following topics:
Before you configure a Fusion Middleware Infrastructure domain, you must install the following schemas on a certified database to use them with this Oracle Fusion Middleware release.
Metadata Services (MDS)
Audit Services (IAU)
Audit Services Append (IAU_APPEND)
Audit Services Viewer (IAU_VIEWER)
Oracle Platform Security Services (OPSS)
User Messaging Service (UMS)
WebLogic Services (WLS)
Service Table (STB)
Follow the instructions in this topic to create database schemas:
Verify that you installed and configured a certified database and that it is up and running.
For more information, see Installing a Database and Database Schemas in Planning an Installation of Oracle Fusion Middleware.
You start RCU from the
To start the Repository Creation Utility:
On UNIX operating systems:
On Microsoft Windows operating systems:
Follow this series of steps to create schemas for the Oracle Fusion Middleware Infrastructure domain.
If you have the permission and privileges to perform DBA actions on your database, select System Load and Product Load on the Create Repository screen.
(The procedure in this document assumes that you have the necessary privileges.)
If you do not have the necessary permission or privileges to perform DBA actions, you must select Prepare Scripts for System Load. This option generates a SQL script that you can give to your database administrator. See Understanding System Load and Product Load in Creating Schemas with the Repository Creation Utility.
For more about options on this screen, see Create repository in Creating Schemas with the Repository Creation Utility.
On the Database Connection Details screen, enter database connection details for RCU to connect to your database.
Click Next then click OK on the dialog window to confirm a successful database connection.
For more information about options on this screen, see Database Connection Details in Creating Schemas with the Repository Creation Utility.
On the Select Components screen, enter a custom prefix you want to use for your schemas, then select AS Common Schemas.
All schemas in this section are automatically selected. The custom prefix logically groups these schemas together for this domain.
For more on custom prefixes, see Understanding Custom Prefixes in Creating Schemas with the Repository Creation Utility.
For more on how to organize schemas in a multi-domain environment, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.
Make a note of the custom prefix that you enter; you need the prefix when you create a domain.
Click Next then click OK on the dialog window to confirm that prerequisite checking for schema creation is successful.
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
You must make a note of passwords you set on this screen; you need them when you create a domain.
Navigate through the remaining RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.
For more information about RCU and its features and concepts, see About Repository Creation Utility.
This topic describes how to create a WebLogic domain using the Configuration Wizard.
There are other ways to create a domain; see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.
To configure a WebLogic domain, follow these steps:
To start domain configuration, navigate to the
/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.
On UNIX operating systems:
On Microsoft Windows operating systems:
On Windows operating systems, you can also start the Configuration Wizard from the Start menu: Select All Programs, then Oracle, then OracleHome. Select WebLogic Server 12c (12.2.
version), then Tools, then Configuration Wizard.
In addition to creating and configuring a domain, you can use this procedure to extend an existing domain. If your settings don't match those in the procedure, change your selections as you need to or see supporting documentation for more details.
To configure multiple products in one domain, see Installing Multiple Products in the Same Domain in Planning an Installation of Oracle Fusion Middleware.
You must select a Domain home directory location, optimally outside the Oracle home directory.
To specify the Domain type and Domain 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. The Domain home resides outside Oracle home directory. This directory structure helps avoid issues when you upgrade or reinstall software.
For more on the Domain home directory, see Choosing a Domain Home in Planning an Installation of Oracle Fusion Middleware.
For more about reinstalling the software, see About Reinstalling the Software.
For more about other options on this screen, see "Configuration Type" in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:
Oracle Enterprise Manager - 18.104.22.168 [em]]
Selecting this template automatically selects the following dependencies:
Oracle JRF - 22.214.171.124 [oracle_common]
WebLogic Coherence Cluster Extension - 126.96.36.199 [wlserver]
Oracle WSM Policy Manager - 188.8.131.52 [oracle_common]
For more information about options on this screen, see "Templates" in Creating WebLogic Domains Using the Configuration Wizard.
On the Application Location screen, select a location to store applications associated with your domain. This location is the Application home directory.
Oracle recommends that you locate your Application home in accordance with the directory structure that "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware describes. Oracle recommends that you locate the Application home outside the Oracle home directory. This directory structure helps avoid issues when you upgrade or reinstall your software.
For more information about the Application home directory, see "Choosing an Application Home" in Planning an Installation of Oracle Fusion Middleware.
For more information about reinstalling the software, see About Reinstalling the Software.
For more information about the options on this screen, see "Application Location" in Creating WebLogic Domains Using the Configuration Wizard.
Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.
Oracle recommends that you make a note of the user name and password that you specify; you need these credentials later to boot and connect to the domain's Administration Server.
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).
Select Production in the Domain Mode field.
Select the Oracle Hotspot JDK in the JDK field.
Select Production Mode to give your environment a higher degree of security. Doing this means that you must enter a user name and password to deploy applications and to start the Administration Server.
For details about options on this screen, including differences between development mode and production mode, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.
In production mode, you can create a boot identity file to bypass the need to enter credentials when you start the Administration Server. See "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
Use the Database Configuration type screen to specify details about the database and database schema.
Select RCU Data to activate fields on this screen. RCU Data tells the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas required to configure a domain.
If you select Manual Configuration on this screen, you must enter schema parameters manually on the JDBC Component Schema screen.
Enter the database DBMS name, or service name if you selected a service type driver.
Enter the name of the server hosting the database.
Enter the port number on which the database listens.
Enter a user name and password to connect to the database's Service Table schema. This is the schema user name and password that you entered for the Service Table component on the "Schema Passwords" screen in RCU (see Creating Database Schemas).
The default user name is prefix
Click Get RCU Configuration when you finish specifying database connection information. The following output in the Connection Result Log shows that the configuration succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Use the JDBC Component Schema screen to verify or specify details about the database schemas.
Verify that values 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.
To configure data sources for Oracle RAC databases in high availability environments, see these topics in High Availability Guide:
More information about other options on this screen is in "JDBC Component Schema" in Creating WebLogic Domains Using the Configuration Wizard.
Use the JDBC Component Schema Test screen to test datasource connections that you just configured.
A green check mark in the Status column indicates a successful test. If you encounter issues, see the error message in the Connection Result Log section of the screen, fix the problem, then test the connection again.
See Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard for more information about the other options on this screen.
To complete domain configuration for the topology, select these options on the Advanced Configuration screen:
Managed Servers, Clusters and Coherence
Required to configure the Managed Servers and cluster, and for configuring the machine and targeting Managed Servers to the machine.
You do not need to select:
Domain Frontend Host Capture
Deployments and Services
JMS File Store
Use the Administration Server screen to select the host’s IP address.
Select the drop-down list next to Listen Address and select the IP address on the host where the Administration Server will reside. Do not use All Local Addresses.
Use the Node Manager screen to select the Node Manager type 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.
In this screen, you create Managed Servers.
To create two new Managed Servers:
infra_server_1in the Server name column.
Installation and configuration procedures use
infra_server_# for Managed Servers names. If you use different names, substitute
infra_server_# with them.
See About Server Groups for more on server groups.
You must configure a second Managed Server to configure the standard topology for high availability. If you are not creating a highly available environment, this step is optional.
For more about the high availability standard topology, see "Understanding the Fusion Middleware Standard HA Topology" in High Availability Guide.
For more about the next steps to prepare for high availability after your domain is configured, see High Availability Configuration Tasks.
For details about options on this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
To create a new cluster:
infra_cluster_1in the Cluster Name field.
By default, server instances in a cluster use unicast to communicate with each other. To change your cluster communications to use multicast, see Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.
You can create new clusters using Fusion Middleware Control and configure cluster communication (unicast or multicast) as you go through cluster creation steps. See Create and Configure Clusters in Administration Console Online Help.
For more information on options on this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.
infra_server_2 to the new cluster
infra_cluster_1, use the Assign Servers to Clusters screen:
Click once on
infra_server_1 to select it, then click on the right arrow to move it beneath the selected cluster (
infra_cluster_1) in the Clusters pane.
infra_server_1 to move it beneath the selected cluster (
infra_cluster_1) in the clusters pane.
For more about options on this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
In the Coherence Clusters screen, configure the Coherence cluster that gets added automatically to the domain. Leave the default port number 0 as the Coherence cluster listen port.
Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that can be assigned to a Managed Server port number is 60535, instead of 65535.
See Table 4-2 for more information and next steps for configuring Coherence. For Coherence licensing information, see "Oracle Coherence" in .
You create a new machine in the domain using the Machines screen. You assign servers to this machine in the next screen.
If you plan to create a high availability environment and know the list of machines that your target topology requires, you can follow the steps in this topic to create all machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.
To create a new machine in the domain:
infra_machine_1in the Name field.
Examples in the procedures may use port number
5556. You must replace this port number with your own port number as needed.
If you extend an existing domain, you can assign servers to any existing machine. You don't need to create a new machine unless your situation requires it.
See "Machines" in Creating WebLogic Domains Using the Configuration Wizard for more information about these options.
In this screen, assign the domain servers to the machine you just created.
To assign the Administration Server and Managed Servers to the new machine:
Click once on
AdminServer to select it, then click on the right arrow to move it beneath the selected machine (
infra_machine_1) in the Machines pane.
AdminServer to move it beneath the selected machine (
infra_machine_1) in the Machines pane.
infra_machine_1. Click Next.
For more information about options on this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Summary screen has detailed configuration information for the domain you are about to create. Review each item to verify it is correct.
You can go back to any previous screen if you need to make changes; use the Back button or select the screen in the navigation pane.
Domain creation does not begin until you click Create.
For more information about options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen shows information about the domain you just configured.
Administration Server URL
You must make a note of both items because you need them later; you need the Domain Location to access scripts that start Node Manager and Administration Server. You need Admin Server URL to access the Administration Server.
Click Finish to dismiss the Configuration Wizard.
Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group.
Any application services that map to a server group automatically target all servers assigned to that group. For more information, see Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.
The WSM-CACHE-SVR server group configures Nonce caching for Oracle Web Services automatically, and is suitable for most applications. Nonce is a unique number that can be used only once in a SOAP request and prevents replay attacks. Nonce caching scales with the number of added Managed Servers running Web service applications.
For advanced caching configurations, see Caching the Nonce with Oracle Coherence in Securing Web Services and Managing Policies with Oracle Web Services Manager.
When you finish configuration, take the following steps to access tools to manage your domain.
For more on tools you can use to manage a domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.
When you finish configuration, take the following steps to start Node Manager.
To start your per-domain Node Manager, go to the
On UNIX operating systems, use
nm.out as an example output file:
nohup ./startNodeManager.sh > nm.out&
On Windows operating systems, run:
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 restarts. For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.
For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
After you finish configuration, you need to start the Administration Server to manage your domain.
To start the Administration Server:
On UNIX operating systems, go the
/bin directory and run:
On Windows operating systems, run:
If you chose Production Mode on the Domain Mode and JDK screen in Specifying the Domain Mode and JDK, you see a prompt for Administrator user login credentials. You provided these in the Administrator Account screen in Configuring the Administrator Account.
For more information about starting the Administration Server, see Starting and Stopping Administration Servers in Administering Oracle Fusion Middleware.
In production mode, you can create a boot identity file to bypass the need to enter credentials when starting the Administration Server. See Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.
To verify that the Administration Server is up and running, open the Administration Server Console. The URL is on the Configuration Success screen in Writing Down Your Domain Name and Administration Server URL.
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
The default Administration Server port number is
For more information about using the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.
You start the Managed Servers from Oracle Fusion Middleware Control.
To start Managed Servers:
The Administration Server host and port number were in the URL on the Configuration Success screen (Writing Down Your Domain Name and Administration Server URL). The default Administration Server port number is
You specified login credentials on the Administrator Account screen (Specifying a Custom Prefix and Selecting Schemas).
For more information about managing Oracle Fusion Middleware using Oracle Enterprise Manager Fusion Middleware Control, see Manage Infrastructure in Administering Oracle Fusion Middleware with Fusion Middleware Control .
Oracle recommends that you verify that your domain is configured properly.
See Basic Administrative Tasks for a New Domain to verify your configuration. Familiarize yourself with tasks that this topic describes and run them.