Fusion Middleware Documentation
Advanced Search


Installing and Configuring the Oracle Fusion Middleware Infrastructure
Close Window

Table of Contents

Show All | Collapse

3 Configuring your Oracle Fusion Middleware Infrastructure Domain

This chapter describes how to create and configure your Oracle Fusion Middleware Infrastructure domain.

The following topics are covered:

3.1 Creating the Database Schemas

Before you can configure a Fusion Middleware Infrastructure domain, you must install the following schemas on a certified database for use with this release of Oracle Fusion Middleware:

  • 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)

  • Call Control (UCSCC)

  • Service Table (STB)

Follow the instructions in this section to install these schemas:

3.1.1 Installing and Configuring a Certified Database

Make sure you have installed and configured a certified database, and that the database is up and running.

For more information, see "Installing a Database and Database Schemas" in Planning an Installation of Oracle Fusion Middleware.

3.1.2 Starting the Repository Creation Utility (RCU)

To start the Repository Creation Utility (RCU):

  1. Navigate to the ORACLE_HOME/oracle_common/bin directory on your system.

  2. Start RCU:

    On UNIX operating systems:

    ./rcu
    

    On Microsoft Windows operating systems:

    rcu.bat
    

3.1.3 Navigating the RCU Screens to Create the Schemas

Follow the instructions in this section to create the schemas for the Oracle Fusion Middleware Infrastructure domain:

Task 1   Introducing RCU

Click Next.

Task 2   Selecting a Method of Schema Creation

If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load Concurrently 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 activities in the database, you must select Prepare Scripts for System Load on this screen. This option will generate a SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.

Tip:

For more information about the options on this screen, see "Create repository" in Creating Schemas with the Repository Creation Utility.

Task 3   Providing Database Credentials

On the Database Connection Details screen, provide the database connection details for RCU to connect to your database.

Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.

Tip:

For more information about the options on this screen, see "Database Connection Details" in Creating Schemas with the Repository Creation Utility.

Task 4   Specifying a Custom Prefix and Selecting Schemas

Specify the custom prefix you want to use for your schemas, then select AS Common Schemas. All of the schemas in this section are automatically selected.

The custom prefix is used to logically group these schemas together for use in this domain.

Tip:

For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.

For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.

Description of rcu_select_components.gif follows
Description of the illustration rcu_select_components.gif

Tip:

You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.

Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

Task 5   Specifying Schema Passwords

Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.

Tip:

You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.

Task 6   Completing Schema Creation

Navigate through the remainder of the 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 Creating Schemas with the Repository Creation Utility

3.2 Configuring Your WebLogic Domain

This section provides instructions for creating a WebLogic domain using the configuration wizard. For more information on other methods available for domain creation, see "Additional Tools for Creating, Extending, and Managing WebLogic Domains" in Creating Domains Using the Configuration Wizard.

The following topics are covered in this section:

3.2.1 Starting the Configuration Wizard

To begin domain configuration, navigate to the ORACLE_HOME/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

config.cmd

On Windows operating systems, you can also start the Configuration Wizard from the Start menu by selecting All Programs, then selecting Oracle, then selecting OracleHome, then selecting WebLogic Server 12c (12.1.2), then selecting Tools, then selecting Configuration Wizard.

3.2.2 Navigating the Configuration Wizard Screens to Configure the Domain

Follow the instructions in this section to create and configure the domain for the topology.

Note:

You can use the same procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.

If you need to configure multiple products in a single domain, refer to "Installing Multiple Products in the Same Domain" in Planning an Installation of Oracle Fusion Middleware for important information.

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Create a New Domain.

In the Domain Location field, specify your Domain home directory.

It is recommended that you locate your Domain home in accordance with the directory structure summarized in Appendix B, where the Domain home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or reinstall your software.

Tip:

More information about the Domain home directory can be found in "Choosing a Domain Home" in Planning an Installation of Oracle Fusion Middleware.

More information about reinstalling the software can be found in Section 5.7.

More information about the other options on this screen can be found in Configuration Type in Creating Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Templates

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

  • Oracle Enterprise Manager - 12.1.2.0 [em]]

    Selecting this template automatically selects the following dependencies:

    • Oracle JRF - 12.1.2.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 12.1.2.0 [wlserver]

  • Oracle WSM Policy Manager - 12.1.2.0 [oracle_common]

Description of config_templates.gif follows
Description of the illustration config_templates.gif

Tip:

More information about the options on this screen can be found in Templates in Creating Domains Using the Configuration Wizard.

Task 3   Selecting the Application Home Location

On the Application Location screen, select the location where you want to store your applications associated with your domain. This location is also referred to as the Application home directory.

It is recommended that you locate your Application home in accordance with the directory structure summarized in Appendix B, where the Application home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or reinstall your software.

Tip:

More information about the Application home directory can be found in "Choosing an Application Home" in Planning an Installation of Oracle Fusion Middleware.

More information about reinstalling the software can be found in Section 5.7.

More information about the options on this screen can be found in Application Location in Creating Domains Using the Configuration Wizard.

Task 4   Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.

It is recommended that you make a note of the user name and password specified on this screen; you will need these credentials later to boot and connect to the domain's Administration Server.

Task 5   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

  • Select Production in the Domain Mode field.

  • Select the Oracle Hotspot JDK in the JDK field.

Selecting Production Mode on this screen gives your environment a higher degree of security, requiring a user name and password to deploy applications and to start the Administration Server.

Tip:

More information about the options on this screen, including the differences between development mode and production mode, can be found in Domain Mode and JDK in Creating Domains Using the Configuration Wizard.

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.

Task 6   Specifying the Datasource Configuration Type

Select RCU Data to activate the fields on this screen. The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.

Note:

If you choose to select Manual Configuration on this screen, you will have to manually fill in the parameters for your schema on the JDBC Component Schema screen.

After selecting RCU Data, fill in the following fields:

Field Description

DBMS/Service

Enter the database DBMS name, or service name if you selected a service type driver.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number on which the database listens.

Schema Owner

Schema Password

Enter the user name and password for connecting to the database's Service Table schema. This is the schema user name and password that was specified for the Service Table component on the "Schema Passwords" screen in RCU (see Section 3.1, "Creating the Database Schemas").

The default user name is prefix_STB, where prefix is the custom prefix that you defined in RCU.


Description of config_datasource.gif follows
Description of the illustration config_datasource.gif

Click Get RCU Configuration when you are finished specifying the database connection information. The following output in the Connection Result Log indicates that the operating 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:

More information about the RCU Data option can be found in "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.

More information about the other options on this screen can be found in Datasource Defaults in Creating Domains Using the Configuration Wizard

Task 7   Specifying JDBC Component Schema Information

Verify that the 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.

Tip:

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

More information about the other options on this screen can be found in JDBC Component Schema in Creating Domains Using the Configuration Wizard.

Task 8   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the datasource connections you have just configured.

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.

Tip:

More information about the other options on this screen can be found in Test Component Schema in Creating Domains Using the Configuration Wizard

Task 9   Selecting Advanced Configuration

To complete domain configuration for the topology, the following must be selected on the Advanced Configuration screen:

  • Administration Server

    This is required to properly configure the listen address of the Administration Server.

  • Node Manager

    This is required to configure Node Manager.

  • Managed Servers, Clusters and Coherence

    This is required to configure the Managed Servers and cluster, and also for configuring the machine and targeting the Managed Servers to the machine.

    Tip:

    If you want to configure dynamic clusters, see the following:

Task 10   Configuring the Administration Server Listen Address

On the Administration Server screen, 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."

Task 11   Configuring Node Manager

The Node Manager screen can be used to select the type of node manager you want to configure, along with the Node Manager credentials.

Select Per Domain as the Node Manager type, then specify the Node Manager credentials.

Tip:

More information about the options on this screen can be found in Node Manager in Creating Domains Using the Configuration Wizard.

More information about the types of Node Manager can be found in "Node Manager Overview" in Administering Node Manager for Oracle WebLogic Server.

Task 12   Configuring Managed Servers

Use the Managed Servers screen to create two new Managed Servers:

  1. Click the Add button to create a new Managed Server.

  2. Specify infra_server_1 in the Server name column.

  3. In the Listen Address drop-down list, select the IP address of the host on which the Managed Server will reside. Do not use "All Local Addresses."

  4. In the Server Groups drop-down list, select both JRF-MAN-SVR and WSMPM-MAN-SVR. These two server groups ensure that the Oracle JRF and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers you are creating.

    Nonce (a unique number that can be used only once in a SOAP request and is used to prevent replay attacks) caching for Oracle Web Services is configured automatically in these steps and is suitable for most applications; nonce caching will naturally scale with the number of added Managed Servers running web service applications. For advanced caching instructions when using very large numbers of messages, see "Caching the Nonce with Oracle Coherence" in Securing Web Services and Managing Policies with Oracle Web Services Manager. These instructions will guide the use of the WSM-CACHE-SVR server-group; otherwise, WSM-CACHE-SVR is not required to be set.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

  5. Repeat this process to create a second Managed Server named infra_server_2.

    Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

    For more information about the high availability standard topology, see "Understanding the Fusion Middleware Standard HA Topology" in High Availability Guide.

    For more information about the next steps to prepare for high availability after your domain is configured, see Section 4.3.

These server names will be referenced throughout this document; if you choose different names then be sure to replace them as needed.

Description of config_managed_servers.gif follows
Description of the illustration config_managed_servers.gif

Tip:

More information about the options on this screen can be found in Managed Servers in Creating Domains Using the Configuration Wizard.

Task 13   Configuring a Cluster

Use the Clusters screen to create a new cluster:

  1. Click the Add button.

  2. Specify infra_cluster_1 in the Cluster Name field.

  3. Leave the cluster Address field blank.

Description of config_clusters.gif follows
Description of the illustration config_clusters.gif

By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.

New clusters can also be created using Fusion Middleware Control. In such cases, cluster communication (unicast or multicast) can be configured when the new cluster is created. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help

Tip:

More information about the options on this screen can be found in Clusters in Creating Domains Using the Configuration Wizard.

Task 14   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign infra_server_1 and infra_server_2 to the new cluster infra_cluster_1:

  1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, infra_cluster_1.

  2. In the Servers pane, assign infra_server_1 to infra_cluster_1 by doing one of the following:

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

    • Double-click on infra_server_1 to move it beneath the selected cluster (infra_cluster_1) in the clusters pane.

  3. Repeat to assign infra_server_2 to infra_cluster_1.

Description of config_servers_to_clusters.gif follows
Description of the illustration config_servers_to_clusters.gif

Tip:

More information about the options on this screen can be found in Assign Servers to Clusters in Creating Domains Using the Configuration Wizard.

Task 15   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the default port number 0 as the Coherence cluster listen port.

See Table 4-2 for more information and next steps for configuring Coherence.

Note:

For Coherence licensing information, refer to "Oracle Coherence" in Licensing Information.

Task 16   Creating a New Machine

Use the Machines screen to create a new machine in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.

Tip:

If you plan to create a high availability environment and know the list of machines required for your target topology, you can follow the directions in this section to create all of the machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.

  1. Click the Add button to create a new machine.

  2. Specify infra_machine_1 in the Name field.

  3. In the Node Manager Listen Address field, select the IP address of the machine where the Managed Servers are being configured.

    You must select a specific interface and not "localhost." This allows Coherence cluster addresses to be dynamically calculated.

  4. Verify the port in the Node Manager Listen Port field.

    The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

Note:

If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.

Description of config_machines.gif follows
Description of the illustration config_machines.gif

Tip:

More information about the options on this screen can be found in Machines in Creating Domains Using the Configuration Wizard.

Task 17   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created:

  1. In the Machines pane, select the machine to which you want to assign the servers; in this case, infra_machine_1.

  2. In the Servers pane, assign AdminServer to infra_machine_1 by doing one of the following:

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

    • Double-click on AdminServer to move it beneath the selected machine (infra_machine_1) in the Machines pane.

  3. Repeat to assign both infra_server_1 and infra_server_2 to infra_machine_1.

Description of config_servers_to_machines.gif follows
Description of the illustration config_servers_to_machines.gif

Tip:

More information about the options on this screen can be found in Assign Servers to Machines in Creating Domains Using the Configuration Wizard.

Task 18   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Domain creation will not begin until you click Create.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating Domains Using the Configuration Wizard.

Task 19   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the following items about the domain you just configured:

  • Domain Location

  • Administration Server URL

Description of config_success.png follows
Description of the illustration config_success.png

You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.

Click Finish to dismiss the configuration wizard.

3.3 Starting the Servers

After configuration is complete, do the following to access the tools with which you can 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.

3.3.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

On Windows operating systems, it is recommended 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.

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.

3.3.2 Starting the Administration Server

To start the Administration Server, go 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 in Task 5, you will be prompted for the login credentials of the Administrator user as provided on the Administrator Account screen in Task 4.

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 access the Administration Server Console. The URL is provided on the Configuration Success screen in Task 19.

Note:

Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.

http://administration_server_host:administration_server_port/console

The default Administration Server port number is 7001.

Description of admin_console.gif follows
Description of the illustration admin_console.gif

For more information about how to use the Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.

3.3.3 Starting the Managed Servers

To start the Managed Servers:

  1. Login 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 (Task 19). The default Administration Server port number is 7001.

    The login credentials were provided on the Administrator Account screen (Task 4).

  2. From the "Target Navigation" pane, click the arrows to expand the domain until the Managed Servers (adf_server_1 and adf_server_2) are visible.

    Description of fmw_control_servers_down.gif follows
    Description of the illustration fmw_control_servers_down.gif

  3. Select the first Managed Server (infra_server_1).

  4. Next to the WebLogic Server menu, select Start Up.

    Description of fmw_control_server_startup.gif follows
    Description of the illustration fmw_control_server_startup.gif

  5. Repeat Steps 3 and 4 to start infra_server_2.

  6. In the Target Navigation page, select your domain name to see that all the servers are up and running.

    Description of fmw_control_servers_up.gif follows
    Description of the illustration fmw_control_servers_up.gif

Tip:

More information about managing Oracle Fusion Middleware using Oracle Enterprise Manager Fusion Middleware Control can be found in Administering Oracle Fusion Middleware with Fusion Middleware Control.

3.4 Verifying Your Configuration

To verify that your domain is configured properly, see Section 4.1. You should familiarize yourself with the tasks described in this section and perform them to verify that your domain is properly configured.