10 Creating the Initial Infrastructure Domain for an Enterprise Deployment

The following topics describe how to install and configure an initial domain, which can be used as the starting point for an enterprise deployment. Later chapters in this guide describe how to extend this initial domain with the various products and components that comprise the enterprise topology you are deploying.

• Variables Used When Creating the Infrastructure Domain
  As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section.
• About the Initial Infrastructure Domain
  Before you create the initial Infrastructure domain, be sure to review the following key concepts.
• Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1
  Use the following sections to install the Oracle Fusion Middleware Infrastructure software in preparation for configuring a new domain for an enterprise deployment.
• Creating the Database Schemas
  Before you can configure a Fusion Middleware Infrastructure domain, you must install the schemas listed in this section in a certified database for use with this release of Oracle Fusion Middleware.
• Configuring the Infrastructure Domain
  The following topics provide instructions for creating a WebLogic Server domain using the Fusion Middleware Configuration wizard.
• Configuring the Domain Directories and Starting the Servers on WCCHOST1
  After the domain is created and the node manager is configured, you can then configure the additional domain directories and start the Administration Server and the Managed Servers on WCCHOST1.
• Propagating the Domain and Starting the Servers on WCCHOST2
  After you start and validate the Administration Server and WLS_WSM1 Managed Server on WCCHOST1, you can then perform the following tasks on WCCHOST2.
• Modifying the Upload and Stage Directories to an Absolute Path
  After configuring the domain and unpacking it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters.
• Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group
  When you configure an Oracle Fusion Middleware domain, the domain is configured by default to use the WebLogic Server authentication provider (DefaultAuthenticator). However, for an enterprise deployment, Oracle recommends that you use a dedicated, centralized LDAP-compliant authentication provider.
• Adding the wsm-pm Role to the Administrators Group
  After you configure a new LDAP-based Authorization Provider and restart the Administration Server, add the enterprise deployment administration LDAP group (WCPAdministrators) as a member to the policy.Updater role in the wsm-pm application stripe.
• Configuring the WebLogic Proxy Plug-In
  

10.1 Variables Used When Creating the Infrastructure Domain

As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section.

These directory variables are defined in File System and Directory Variables Used in This Guide.

• ORACLE_HOME

• ASERVER_HOME

• MSERVER_HOME

• APPLICATION_HOME

• JAVA_HOME

• NM_HOME

In addition, you'll be referencing the following virtual IP (VIP) addresses and host names defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:

• ADMINHOST

• WCCHOST1

• WCCHOST2

• WCPHOST1

• WCPHOST2

• DBHOST1

• DBHOST2

• SCAN Address for the Oracle RAC Database (DB-SCAN.examle.com)

10.2 About the Initial Infrastructure Domain

Before you create the initial Infrastructure domain, be sure to review the following key concepts.

• About the Infrastructure Distribution
  
• Characteristics of the Domain
  

10.2.1 About the Infrastructure Distribution

You create the initial Infrastructure domain for an enterprise deployment using the Oracle Fusion Middleware Infrastructure distribution. This distribution contains both the Oracle WebLogic Server software and the Oracle JRF software.

The Oracle JRF software consists of Oracle Web Services Manager, Oracle Application Development Framework (Oracle ADF), Oracle Enterprise Manager Fusion Middleware Control, the Repository Creation Utility (RCU), and other libraries and technologies required to support the Oracle Fusion Middleware products.

Later in this guide, you can then extend the domain to support the Oracle Fusion Middleware products required for your enterprise deployment.

For more information, see "Understanding Oracle Fusion Middleware Infrastructure" in Understanding Oracle Fusion Middleware.

10.2.2 Characteristics of the Domain

The following table lists some of the key characteristics of the domain you are about to create. By reviewing and understanding these characteristics, you can better understand the purpose and context of the procedures used to configure the domain.

Many of these characteristics are described in more detail in Understanding a Typical Enterprise Deployment.

Characteristic of the Domain	More Information
Uses a separate virtual IP (VIP) address for the Administration Server.	Configuration of the Administration Server and Managed Servers Domain Directories
Uses separate domain directories for the Administration Server and the Managed Servers in the domain.	Configuration of the Administration Server and Managed Servers Domain Directories
Includes a dedicated cluster for Oracle Web Services Manager	Using Oracle Web Services Manager in the Application Tier
Uses a per domain Node Manager configuration.	About the Node Manager Configuration in a Typical Enterprise Deployment
Requires a separately installed LDAP-based authentication provider.	Understanding OPSS and Requests to the Authentication and Authorization Stores

10.3 Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

Use the following sections to install the Oracle Fusion Middleware Infrastructure software in preparation for configuring a new domain for an enterprise deployment.

• Installing a Supported JDK
  
• Starting the Infrastructure Installer on WCCHOST1
  
• Navigating the Infrastructure Installation Screens
  
• Installing Oracle Fusion Middleware Infrastructure on the Other Host Computers
  
• Checking the Directory Structure
  After you install the Oracle Fusion Middleware Infrastructure and create the Oracle home, you should see the directory and sub-directories listed in this topic. The contents of your installation vary based on the options you selected during the installation.

10.3.1 Installing a Supported JDK

Oracle Fusion Middleware requires that a certified Java Development Kit (JDK) is installed on your system. See the following sections for more information:

• Locating and Downloading the JDK Software
  
• Installing the JDK Software
  

10.3.1.1 Locating and Downloading the JDK Software

To find a certified JDK, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

After you identify the Oracle JDK for the current Oracle Fusion Middleware release, you can download an Oracle JDK from the following location on Oracle Technology Network:

http://www.oracle.com/technetwork/java/index.html

Be sure to navigate to the download for the Java SE JDK.

10.3.1.2 Installing the JDK Software

Install the JDK in the following locations:

• On the shared storage device, where it will be accessible from each of the application tier host computers. Install the JDK in the /u01/oracle/products/jdk directory.

• On the local storage device for each of the Web tier host computers.

  The Web tier host computers, which reside in the DMZ, do not necessarily have access to the shared storage on the application tier.

For more information about the recommended location for the JDK software, see the Understanding the Recommended Directory Structure for an Enterprise Deployment.

The following example describes how to install a recent version of JDK 1.8.0_101.

1. Change directory to the location where you downloaded the JDK archive file.
   cd download_dir
2. Unpack the archive into the JDK home directory, and then run the following commands:
   tar -xzvf jdk-8u101-linux-x64.tar.gz

   Note that the JDK version listed here was accurate at the time this document was published. For the latest supported JDK, see the Oracle Fusion Middleware System Requirements and Specifications for the current Oracle Fusion Middleware release.

3. Move the JDK directory to the recommended location in the directory structure.

   For example:

   mv ./jdk1.8.0_101 /u01/oracle/products/jdk
   

   For more information, see File System and Directory Variables Used in This Guide.

4. Define the JAVA_HOME and PATH environment variables for running Java on the host computer.

   For example:

   export JAVA_HOME=/u01/oracle/products/jdk
   export PATH=$JAVA_HOME/bin:$PATH
   

5. Run the following command to verify that the appropriate java executable is in the path and your environment variables are set correctly:

   java -version
     java version "1.8.0_101"
     Java(TM) SE Runtime Environment (build 1.8.0_101-b14)
     Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
   

10.3.2 Starting the Infrastructure Installer on WCCHOST1

To start the installation program, perform the following steps.

1. Log in to WCCHOST1.
2. Go to the directory where you downloaded the installation program.
3. Launch the installation program by invoking the java executable from the JDK directory on your system, as shown in the example below.

   $JAVA_HOME/bin/java -d64 -jar distribution_file_name.jar
   

   In this example:

   • Replace JAVA_HOME with the environment variable or actual JDK location on your system.

   • Replace distribution_file_name with the actual name of the distribution JAR file.

     Note that if you download the distribution from the Oracle Technology Network (OTN), then the JAR file is typically packaged inside a downloadable ZIP file.

     To install the software required for the initial Infrastructure domain, the distribution you want to install is fmw_12.2.1.2.0_infrastructure_generic.jar.

     For more information about the actual file names of each distribution, see Identifying and Obtaining Software Downloads for an Enterprise Deployment.

When the installation program appears, you are ready to begin the installation. See Navigating the Installation Screens for a description of each installation program screen.

10.3.3 Navigating the Infrastructure Installation Screens

The installation program displays a series of screens, in the order listed in the following table.

If you need additional help with any of the installation screens, click the screen name or click the Help button on the screen.

Table 10-1 Navigating the Infrastructure Installation Screens

Screen	Description
Installation Inventory Setup	On UNIX operating systems, this screen will appear if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location. For more information about the central inventory, see Understanding the Oracle Central Inventory in Installing Software with the Oracle Universal Installer.
Welcome	This screen introduces you to the product installer.
Auto Updates	Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization.
Installation Location	Use this screen to specify the location of your Oracle home directory. For the purposes of an enterprise deployment, enter the value of the ORACLE_HOME variable listed in Table 7-2.
Installation Type	Use this screen to select the type of installation and consequently, the products and feature sets you want to install. For this topology, select Fusion Middleware Infrastructure. Note: The topology in this document does not include server examples. Oracle strongly recommends that you do not install the examples into a production environment.
Prerequisite Checks	This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, refer to the Oracle Fusion Middleware System Requirements and Specifications document on the Oracle Technology Network (OTN).
Security Updates	If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates. If you do not have one and are sure you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
Installation Summary	Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file. Response files can be used later in a silent installation situation. For more information about silent or command-line installation, see Using the Oracle Universal Installer in Silent Mode in Installing Software with the Oracle Universal Installer.
Installation Progress	This screen allows you to see the progress of the installation.
Installation Complete	This screen appears when the installation is complete. Review the information on this screen, then click Finish to dismiss the installer.

10.3.4 Installing Oracle Fusion Middleware Infrastructure on the Other Host Computers

If you have configured a separate shared storage volume or partition for WCCHOST2, then you must also install the Infrastructure on WCCHOST2.

For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

To install the software on the other host computers in the topology, log in to each host, and use the instructions in Starting the Infrastructure Installer on WCCHOST1 and Navigating the Infrastructure Installation Screens to create the Oracle home on the appropriate storage device.

Note:

In previous releases, the recommended enterprise topology included a colocated set of Oracle HTTP Server instances. In those releases, there was a requirement to install the Infrastructure on the Web Tier hosts (WEBHOST1 and WEBHOST2). However, for this release, the enterprise deployment topology assumes the Web servers are installed and configured in standalone mode, so they are not considered part of the application tier domain. For more information, see Configuring the Web Tier for an Enterprise Deployment

10.3.5 Checking the Directory Structure

After you install the Oracle Fusion Middleware Infrastructure and create the Oracle home, you should see the directory and sub-directories listed in this topic. The contents of your installation vary based on the options you selected during the installation.

To check the directory structure:

1. Change to the ORACLE_HOME directory where you installed the Infrastructure.
2. Enter the following command:
   ls --format=single-column
   The directory structure on your system must match the structure shown in the following example:

   cfgtoollogs
   coherence 
   em 
   install 
   inventory 
   OPatch 
   oracle_common 
   oraInst.loc 
   oui
   wlserver
   

   For more information about the directory structure after the installation complete, see What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

10.4 Creating the Database Schemas

Before you can configure a Fusion Middleware Infrastructure domain, you must install the schemas listed in this section in 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)

• Common Infrastructure Services (STB)

You use the Repository Creation Utility (RCU) to create the schemas. This utility is installed in the Oracle home for each Oracle Fusion Middleware product. For more information about RCU and how the schemas are created and stored in the database, see Preparing for Schema Creation in Creating Schemas with the Repository Creation Utility.

Follow the instructions in this section to install the required schemas.

• Installing and Configuring a Certified Database
  
• Starting the Repository Creation Utility (RCU)
  
• Navigating the RCU Screens to Create the Schemas
  

10.4.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 the Preparing the Database for an Enterprise Deployment.

10.4.2 Starting the Repository Creation Utility (RCU)

To start the Repository Creation Utility (RCU):

1. Set the JAVA_HOME environment variable so it references the location where you installed a supported JDK.

   For more information, see File System and Directory Variables Used in This Guide.

2. Navigate to the following directory on WCCHOST1:

   ORACLE_HOME/oracle_common/bin
   

3. Start RCU:

   ./rcu
   

10.4.3 Navigating the RCU Screens to Create the Schemas

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

• Task 1, "Introducing RCU"

• Task 2, "Selecting a Method of Schema Creation"

• Task 3, "Providing Database Credentials"

• Task 4, "Specifying a Custom Prefix and Selecting Schemas"

• Task 5, "Specifying Schema Passwords"

• Task 6, "Completing Schema Creation"

Task 1   Introducing RCU

Review the Welcome screen and verify the version number for RCU. Click Next to begin.

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

In the Host Name field, enter the SCAN address of the Oracle RAC Database.

Click Next to proceed, then click OK in 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

1. Specify the custom prefix you want to use to identify the Oracle Fusion Middleware schemas.

   Note:

   Custom prefixes must be 10 characters or less when including WebCenter Portal schemas even though the RCU limit is 12 characters. This is to avoid RCU errors when validating the full WebCenter Portal schemas names. Maximum schema user name length is limited to 30 characters total. WebCenter Portal schema suffixes use up to 20 characters.

   The custom prefix is used to logically group these schemas together for use in this domain. For the purposes of this guide, use the prefix FMW12212.

   Tip:

   Make a note of the custom prefix you choose to enter here; you will need this later, during the domain creation process.

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

2. Select AS Common Schemas.

   When you select AS Common Schemas, all of the schemas in this section are automatically selected.

   If the schemas in this section are not automatically selected, then select the required schemas.

A schema called Common Infrastructure Services is also automatically created; this schema is grayed out and cannot be selected or deselected. This schema (the STB schema) enables you to retrieve information from RCU during domain configuration. For more information, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

Tip:

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.

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.

For the purposes of this guide, you can accept the default settings on the remaining screens, or you can customize how RCU creates and uses the required tablespaces for the Oracle Fusion Middleware schemas.

For more information about RCU and its features and concepts, see About the Repository Creation Utility in Creating Schemas with the Repository Creation Utility.

When you reach the Completion Summary screen, click Close to dismiss RCU.

10.5 Configuring the Infrastructure Domain

The following topics provide instructions for creating a WebLogic Server domain using the Fusion Middleware Configuration wizard.

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.

• Starting the Configuration Wizard
  
• Navigating the Configuration Wizard Screens to Configure the Infrastructure Domain
  

10.5.1 Starting the Configuration Wizard

To begin domain configuration, run the following command in the Oracle Fusion Middleware Oracle home on WCCHOST1.

ORACLE_HOME/oracle_common/common/bin/config.sh

10.5.2 Navigating the Configuration Wizard Screens to Configure the Infrastructure Domain

Follow the instructions in the following sections to create and configure the domain for the topology, with static clusters.

• Creating the Domain with Static Clusters
  

10.5.2.1 Creating the Domain with Static Clusters

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

Domain creation and configuration includes the following tasks.

• Task 1, "Selecting the Domain Type and Domain Home Location"

• Task 2, "Selecting the Configuration Templates"

• Task 3, "Selecting the Application Home Location"

• Task 4, "Configuring the Administrator Account"

• Task 5, "Specifying the Domain Mode and JDK"

• Task 6, "Specifying the Database Configuration Type"

• Task 7, "Specifying JDBC Component Schema Information"

• Task 8, "Providing the GridLink Oracle RAC Database Connection Details"

• Task 9, "Testing the JDBC Connections"

• Task 10, "Selecting Advanced Configuration"

• Task 11, "Configuring the Administration Server Listen Address"

• Task 12, "Configuring Node Manager"

• Task 13, "Configuring Managed Servers"

• Task 14, "Configuring a Cluster"

• Task 15, "Assigning Server Templates"

• Task 16, "Configuring Dynamic Servers"

• Task 17, "Assigning Managed Servers to the Cluster"

• Task 18, "Configuring Coherence Clusters"

• Task 19, "Creating Machines"

• Task 20, "Assigning Servers to Machines"

• Task 21, "Creating Virtual Targets"

• Task 23, "Configuring the JMS File Store"

• Task 24, "Reviewing Your Configuration Specifications and Configuring the Domain"

• Task 25, "Writing Down Your Domain Home and Administration Server URL"

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 the value of the ASERVER_HOME variable, as defined in File System and Directory Variables Used in This Guide.

Tip:

More information about the other options on this screen of the Configuration Wizard, see Configuration Type in Creating WebLogic 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.2.1.2.0 [em]

  Selecting this template automatically selects the following dependencies:

  • Oracle JRF - 12.2.1.2.0 [oracle_common]

  • WebLogic Coherence Cluster Extension - 12.2.1.2.0 [wlserver]

• Oracle WSM Policy Manager - 12.2.1.2.0 [oracle_common]

Tip:

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

Task 3   Selecting the Application Home Location

On the Application Location screen, specify the value of the APPLICATION_HOME variable, as defined in File System and Directory Variables Used in This Guide.

Tip:

More information about the options on this screen can be found in Application Location in Creating WebLogic 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.

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 WebLogic 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 the boot.properties File.

Task 6   Specifying the Database 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 fields as shown in the following table.

Field	Description
DBMS/Service	Enter the service name for the Oracle RAC database where you will install the product schemas. For example: orcl.example.com Be sure this is the common service name that is used to identify all the instances in the Oracle RAC database; do not use the host-specific service name.
Host Name	Enter the Single Client Access Name (SCAN) Address for the Oracle RAC database, which you entered in the Enterprise Deployment Workbook.
Port	Enter the port number on which the database listens. For example, 1521.
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 Creating the Database Schemas). The default user name is prefix_STB, where prefix is the custom prefix that you defined in RCU.

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.

Click Next if the connection to the database is successful.

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

The schema table should be populated, because you selected Get RCU Data on the previous screen. As a result, the Configuration Wizard locates the database connection values for all the schemas required for this domain.

At this point, the values are configured to connect to a single-instance database. However, for an enterprise deployment, you should use a highly available Real Application Clusters (RAC) database, as described in Preparing the Database for an Enterprise Deployment.

In addition, Oracle recommends that you use an Active GridLink datasource for each of the component schemas. For more information about the advantages of using GridLink data sources to connect to a RAC database, see Database Considerations in theHigh Availability Guide.

To convert the data sources to GridLink:

1. Select all the schemas by selecting the checkbox at in the first header row of the schema table.

2. Click Convert to GridLink and click Next.

Task 8   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in following table.

Element	Description and Recommended Value
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521)
ONS Host and Port	In the ONS Host field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, 6200).
Enable Fan	Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.

For more information about specifying the information on this screen, as well as information about how to identify the correct SCAN address, see Configuring Active GridLink Data Sources with Oracle RAC in the High Availability Guide.

You can also click Help to display a brief description of each field on the screen.

Task 9   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source 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 WebLogic Domains Using the Configuration Wizard

Task 10   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options 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.

• Topology

  This is required to add, delete, or modify the Settings for Server Templates, Managed Servers, Clusters, Virtual Targets, and Coherence.

• File Store

  This is required to configure the appropriate shared storage for JMS persistent stores.

Note:

When using the Advanced Configuration screen in the Configuration Wizard:

• If any of the above options are not available on the screen, then return to the Templates screen, and be sure you selected the required templates for this topology.

• Do not select the Domain Frontend Host Capture advanced configuration option. You will later configure the frontend host property for specific clusters, rather than for the domain.

Task 11   Configuring the Administration Server Listen Address

On the Administration Server screen:

1. In the Server Name field, retain the default value - AdminServer.

2. In the Listen Address field, enter the virtual host name that corresponds to the VIP of the ADMINVHN that you procured in Procuring Resources for an Enterprise Deployment and enabled in Preparing the Host Computers for an Enterprise Deployment.

   For more information on the reasons for using the ADMINVHN virtual host, see Reserving the Required IP Addresses for an Enterprise Deployment.

3. Leave the other fields at their default values.

   In particular, be sure that no server groups are assigned to the Administration Server.

Task 12   Configuring Node Manager

Select Per Domain Default Location as the Node Manager type, then specify the Node Manager credentials you will use to connect to the Node Manager.

Tip:

For more information about the options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

For more information about per domain and per host Node Manager implementations, see About the Node Manager Configuration in a Typical Enterprise Deployment.

For additional information, see Configuring Node Manager on Multiple Machines in Administering Node Manager for Oracle WebLogic Server.

Task 13   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 WLS_WSM1 in the Server name column.

3. In the Listen Address column, enter WCCHOST1.

   Be sure to enter the host name that corresponds to WCCHOST1; do not use the IP address.

4. In the Listen Port column, enter 7010.

5. In the Server Groups drop-down list, select JRF-MAN-SVR and WSMPM-MAN-SVR.

   These server groups ensure that the Oracle JRF and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers you are creating.

   Server groups target Fusion Middleware applications and services to one or more servers by mapping defined groups of application services to each defined server group. 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.

   Note:

   Nonce caching for Oracle Web Services is initialized automatically by the WSM-CACHE-SVR server group and is suitable for most custom applications. This initialization is automatically performed in SOA, OSB and other FMW servers that run JRF and create a coherence cluster. Nonce is a unique number that can be used only once in a SOAP request and is used to prevent replay attacks. Nonce caching will naturally scale 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, which provides additional guidance for the use of nonce caching and the WSM-CACHE-SVR server-group in custom WLS servers.

6. Repeat this process to create a second Managed Server named WLS_WSM2.

   For the Listen Address, enter WCCHOST2. For the Listen Port, enter 7010. Apply the same server groups you applied to the first managed server to the WLS_WSM2.

The Managed Server names suggested in this procedure (WLS_WSM1 and WLS_WSM2) will be referenced throughout this document; if you choose different names then be sure to replace them as needed.

Tip:

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

Task 14   Configuring a Cluster

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify WSM-PM_Cluster in the Cluster Name field.

3. From the Dynamic Server Groups drop-down list, select Unspecified.

Tips:

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

Task 15   Assigning Server Templates

Click Next to continue.

Task 16   Configuring Dynamic Servers

Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.

1. Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.

2. Confirm the Server Template selection is Unspecified.

3. Click Next.

Task 17   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign WLS_WSM1 and WLS_WSM2 to the new cluster WSM-PM_Cluster:

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

2. In the Servers pane, assign WLS_WSM1 to WSM-PM_Cluster by doing one of the following:

   • Click once on WLS_WSM1 to select it, then click on the right arrow to move it beneath the selected cluster (WSM-PM_Cluster) in the Clusters pane.

     OR

   • Double-click on WLS_WSM1 to move it beneath the selected cluster (WSM-PM_Cluster) in the clusters pane.

3. Repeat these steps to assign the WLS_WSM2 Managed Server to the WSM-PM_Cluster.

Tip:

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

Task 18   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain.

In the Cluster Listen Port, enter 9991.

Note:

For Coherence licensing information, Oracle Coherence Products in Oracle Fusion Middleware Licensing Information User Manual.

Task 19   Creating Machines

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

1. Select the Unix Machine tab.

2. Click the Add button to create five new UNIX machines.

   Use the values in Table 10-2 to define the Name and Node Manager Listen Address of each machine.

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

Table 10-2 Values to Use When Creating Unix Machines

Name	Node Manager Listen Address	Node Manager Listen Port
ADMINHOST	Enter the value of the ADMINVHN variable.	5556
WCCHOST1	The value of the WCCHOST1 host name variable. For example, WCCHOST1.example.com.	5556
WCCHOST2	The value of the WCCHOST2 host name variable. For example, WCCHOST2.example.com.	5556
WCPHOST1	The value of the WCPHOST1 host name variable. For example, WCPHOST1.example.com.	5556
WCPHOST2	The value of the WCPHOST2 host name variable. For example, WCPHOST2.example.com.	5556

Tip:

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

Task 20   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign any statically defined managed servers to the appropriate machines. Servers that are part of a dynamic cluster will be assigned to the calculated machine names automatically.

The Assign Servers to Machines screen is similar to the Assign Managed Servers to Clusters screen. Select the target machine in the Machines column, select the server name in the left column, and click the right arrow to assign the server to the appropriate machine.

Assign the servers as follows:

• Assign the AdminServer to the ADMINHOST machine.

• Assign the WLS-WSM1 Managed Server to the WCCHOST1 machine.

• Assign the WLS-WSM2 Managed Server to the WCCHOST2 machine.

Tip:

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

Task 21   Creating Virtual Targets

Click Next to continue.

Task 22   Creating Partitions

Click Next to continue.

Task 23   Configuring the JMS File Store

When you configure a domain using the Oracle WSM Policy Manager configuration template, you should select the proper location of the Metadata Services (MDS) JMS File Store, especially when you are configuring an enterprise deployment.

Enter the following location in the Directory column of the JMS File Store screen:

ORACLE_RUNTIME/domain_name/WSM-PM_Cluster/jms

Note:

You can provide a non-shared storage location for this store. It is used only in WSM's development mode. In the production environments, the database will be used to host it instead.

Replace ORACLE_RUNTIME with the actual value of the variable, as defined in File System and Directory Variables Used in This Guide.

Replace domain_name with the name of the domain you are creating.

Task 24   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 WebLogic Domains Using the Configuration Wizard.

Task 25   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

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 Administration Server.

Click Finish to dismiss the Configuration Wizard.

10.6 Configuring the Domain Directories and Starting the Servers on WCCHOST1

After the domain is created and the node manager is configured, you can then configure the additional domain directories and start the Administration Server and the Managed Servers on WCCHOST1.

• Starting the Node Manager in the Administration Server Domain Home on WCCHOST1
  Use these steps to start the per-domain Node Manager for the ASERVER_HOME domain directory.
• Creating the boot.properties File
  You must create a boot.properties if you want to start the Administrator Server without being prompted for the Administrator Server credentials. This step is required in an enterprise deployment. The credentials you enter in this file are encrypted when you start the Administration Server.
• Starting the Administration Server Using the Node Manager
  After you have configured the domain and configured the Node Manager, you can start the Administration Server, using the Node Manager. In an enterprise Deployment, the Node Manager is used to start and stop the Administration Server and all the Managed Servers in the domain.
• Validating the Administration Server
  Before proceeding with the configuration steps, validate that the Administration Server has started successfully by making sure you have access to the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control, which both are installed and configured on the Administration Servers.
• Disabling the Derby Database
  
• Creating a Separate Domain Directory for Managed Servers on WCCHOST1
  When you initially create the domain for enterprise deployment, the domain directory resides on a shared disk. This default domain directory will be used to run the Administration Server. You can now create a copy of the domain on the local storage for both WCCHOST1 and WCCHOST2. The domain directory on the local (or private) storage will be used to run the Managed Servers.
• Starting the Node Manager in the Managed Server Domain Directory on WCCHOST1
  
• Starting and Validating the WLS_WSM1 Managed Server on WCCHOST1
  After you have configured Node Manager and created the Managed Server domain directory, you can use Oracle Enterprise Manager Fusion Middleware Control to start the WLS_WSM1 Managed Server on WCCHOST1.

10.6.1 Starting the Node Manager in the Administration Server Domain Home on WCCHOST1

Use these steps to start the per-domain Node Manager for the ASERVER_HOME domain directory.

1. Verify that the listen address in the nodemanager.properties file is set correctly.
   1. Open the nodemanager.properties file for editing:
      ASERVER_HOME/nodemanager/nodemanager.properties
   2. Make sure the ListenAddress property is set to the value of the ADMINVHN virtual IP address.
   3. Make sure that QuitEnabled is set to ‘true’. If this line is not present in the nodemanager.properties file, add the following line:
      QuitEnabled=true
2. Change to the following directory:
   ASERVER_HOME/bin
3. Start the Node Manager by entering the following command:
   nohup ./startNodeManager.sh > ASERVER_HOME/nodemanager/nodemanager.out 2>&1 &

   For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

10.6.2 Creating the boot.properties File

You must create a boot.properties if you want to start the Administrator Server without being prompted for the Administrator Server credentials. This step is required in an enterprise deployment. The credentials you enter in this file are encrypted when you start the Administration Server.

To create a boot.properties file for the Administration Server:

1. Create the following directory structure:

   mkdir -p ASERVER_HOME/servers/AdminServer/security
   

2. In a text editor, create a file called boot.properties in the security directory created in the previous step, and enter the Administration Server credentials that you defined when you ran the Configuration Wizard to create the domain:

   username=adminuser
   password=password
   

   Note:

   When you start the Administration Server, the username and password entries in the file get encrypted.

   For security reasons, minimize the amount of time the entries in the file are left unencrypted; after you edit the file, you should start the server as soon as possible so that the entries get encrypted.

3. Save the file and close the editor.

10.6.3 Starting the Administration Server Using the Node Manager

After you have configured the domain and configured the Node Manager, you can start the Administration Server, using the Node Manager. In an enterprise Deployment, the Node Manager is used to start and stop the Administration Server and all the Managed Servers in the domain.

To start the Administration Server using the Node Manager:

1. Start the WebLogic Scripting Tool (WLST):

   cd ORACLE_COMMON_HOME/common/bin
   ./wlst.sh
   

2. Connect to Node Manager using the Node Manager credentials:

   wls:/offline>nmConnect('nodemanager_username','nodemanager_password',
               'ADMINVHN','5556','domain_name',
               'ASERVER_HOME')
   

   Note:

   This user name and password are used only to authenticate connections between Node Manager and clients. They are independent of the server administrator ID and password and are stored in the nm_password.properties file located in the following directory:

   ASERVER_HOME/config/nodemanager
   

3. Start the Administration Server:

   nmStart('AdminServer')
   

   Note:

   When you start the Administration Server, it attempts to connect to Oracle Web Services Manager for WebServices policies. It is expected that, since the WSM-PM Managed Servers are not yet started, the following message will appear in the Administration Server log:

   <Warning><oracle.wsm.resources.policymanager>
   <WSM-02141><Unable to connect to the policy access service due to Oracle WSM policy manager host server being down.>
   

4. Exit WLST:

   exit()
   

10.6.4 Validating the Administration Server

Before proceeding with the configuration steps, validate that the Administration Server has started successfully by making sure you have access to the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control, which both are installed and configured on the Administration Servers.

To navigate to Fusion Middleware Control, enter the following URL, and log in with the Oracle WebLogic Server administrator credentials:

ADMINVHN:7001/em

To navigate to the Oracle WebLogic Server Administration Console, enter the following URL, and log in with the same administration credentials:

ADMINVHN:7001/console

10.6.5 Disabling the Derby Database

Before you create the Managed Server directory and start the Managed Servers, disable the embedded Derby database, which is a file-based database, packaged with Oracle WebLogic Server. The Derby database is used primarily for development environments. As a result, you must disable it when you are configuring a production-ready enterprise deployment environment; otherwise, the Derby database process will start automatically when you start the Managed Servers.

To disable the Derby database:

1. Navigate to the following directory in the Oracle home.
   WL_HOME/common/derby/lib
2. Rename the Derber library jar file:
   mv derby.jar disable_derby.jar
3. Complete steps 1 through 2 on each ORACLE_HOME for WCCHOST1 and WCCHOST2 if they use separate shared filesystems.

10.6.6 Creating a Separate Domain Directory for Managed Servers on WCCHOST1

When you initially create the domain for enterprise deployment, the domain directory resides on a shared disk. This default domain directory will be used to run the Administration Server. You can now create a copy of the domain on the local storage for both WCCHOST1 and WCCHOST2. The domain directory on the local (or private) storage will be used to run the Managed Servers.

Placing the MSERVER_HOME on local storage is recommended to eliminate the potential contention and overhead cause by servers writing logs to shared storage. It is also faster to load classes and jars need from the domain directory, so any temporary or cache data that Managed Servers use from the domain directory is processed quicker.

As described in Preparing the File System for an Enterprise Deployment, the path to the Administration Server domain home is represented by the ASERVER_HOME variable, and the path to the Managed Server domain home is represented by the MSERVER_HOME variable.

To create the Managed Server domain directory:

1. Sign in to WCCHOST1 and run the pack command to create a template as follows:

   cd ORACLE_COMMON_HOME/common/bin
    
   ./pack.sh -managed=true 
             -domain=ASERVER_HOME 
             -template=/full_path/wcpdomaintemplate.jar 
             -template_name=wcp_domain_template
   

   In this example:

   • Replace ASERVER_HOME with the actual path to the domain directory you created on the shared storage device.

   • Replace full_path with the complete path to the location where you want to create the domain template jar file. You will need to reference this location when you copy or unpack the domain template jar file. It is recommended to choose a shared volume other than ORACLE_HOME, or write to /tmp/ and copy the files manually between servers.

     You must specify a full path for the template jar file as part of the -template argument to the pack command:

     SHARED_CONFIG_DIR/domains/template_filename.jar
     

   • wcpdomaintemplate.jar is a sample name for the jar file you are creating, which will contain the domain configuration files.

   • wcp_domain_template is the label assigned to the template data stored in the template file.

2. Make a note of the location of the wcpdomaintemplate.jar file you just created with the pack command.

   Tip:

   For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Creating Templates and Domains Using the Pack and Unpack Commands.

3. If you haven't already, create the recommended directory structure for the Managed Server domain on the WCCHOST1 local storage device.

   Use the examples in File System and Directory Variables Used in This Guide as a guide.

4. Run the unpack command to unpack the template in the domain directory onto the local storage, as follows:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./unpack.sh -domain=MSERVER_HOME \
               -overwrite_domain=true \
               -template=/full_path/wcpdomaintemplate.jar
               -log_priority=DEBUG \
               -log=/tmp/unpack.log \
               -app_dir=APPLICATION_HOME \
   

   Note:

   The -overwrite_domain option in the unpack command allows unpacking a managed server template into an existing domain and existing applications directories. For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory, they must be restored after this unpack operation.

   Additionally, to customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.sh and configure it to, for example, add custom libraries to the WebLogic Server classpath, specify additional java command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

   In this example:

   • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain will be unpacked.

   • Replace full_path with the complete path to the location where you created or copied the template jar file.

   • wcpdomaintemplate.jar is the name of the template jar file you created when you ran the pack command to pack up the domain on the shared storage device.

   Tip:

   For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Creating Templates and Domains Using the Pack and Unpack Commands.

5. Change directory to the newly created Managed Server directory and verify that the domain configuration files were copied to the correct location on the WCCHOST1 local storage device.

10.6.7 Starting the Node Manager in the Managed Server Domain Directory on WCCHOST1

After you create the Managed Server domain directory, there are two domain home directories and two corresponding Node Manager instances on WCCHOST1. You use one Node Manager to control the Administration Server, running from Administration Server domain home, and you use the other Node Manager to control the Managed Servers, running from the Managed Server domain home.

You must start the two Node Managers independently.

Note:

The Node Manager for the Managed Server's MSERVER_HOME will be reset every time the domain configuration is unpacked. The ListenAddress will be changed to the ADMINVHN instead of the correct hostname. This needs to be changed to the correct value before starting the Node Manager service after an unpack is performed.

Follow these steps to update and start the Node Manager from the Managed Server home:

1. Verify that the listen address in the nodemanager.properties file is set correctly, by completing the following steps:
   1. Change to the following directory:
      MSERVER_HOME/nodemanager/
   2. Open the nodemanager.properties file for editing.
   3. Update the ListenAddress property to the correct hostname as follows:
      WCCHOST1: ListenAddress=WCCHOST1
      WCCHOST2: ListenAddress=WCCHOST2
   4. Update the ListenPort property with the correct Listen Port details.
   5. Make sure that QuitEnabled is set to ‘true’. If this line is not present in the nodemanager.properties file, add the following line:
      QuitEnabled=true
2. Change to the following directory:
   MSERVER_HOME/bin
3. Use the following command to start the Node Manager:
   nohup ./startNodeManager.sh > MSERVER_HOME/nodemanager/nodemanager.out 2>&1 &

For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

10.6.8 Starting and Validating the WLS_WSM1 Managed Server on WCCHOST1

After you have configured Node Manager and created the Managed Server domain directory, you can use Oracle Enterprise Manager Fusion Middleware Control to start the WLS_WSM1 Managed Server on WCCHOST1.

1. Enter the following URL into a browser to display the Fusion Middleware Control login screen:

   http://ADMINVHN:7001/em
   

   In this example:

   • Replace ADMINVHN with the host name assigned to the ADMINVHN Virtual IP address in Identifying and Obtaining Software Downloads for an Enterprise Deployment.

   • Port 7001 is the typical port used for the Administration Server console and Fusion Middleware Control. However, you should use the actual URL that was displayed at the end of the Configuration Wizard session when you created the domain.

     Tip:

     For more information about managing Oracle Fusion Middleware using Oracle Enterprise Manager Fusion Middleware, see Getting Started Using Oracle Enterprise Manager Fusion Middleware Control in Administering Oracle Fusion Middleware.

2. Log in to Fusion Middleware Control using the Administration Server credentials.
3. Select the Servers pane to view the Managed Servers in the domain.
4. Select only the WLS_WSM1 Managed Server, and note the assigned port number
5. Click Control > Start on the tool bar to start the selected WLS_WSM1 Managed Server.
6. To verify that the Managed Server is working correctly, open your browser and enter the following URL, using the appropriate port number:

   WCCHOST1:<port-number>/wsm-pm/
   

   Enter the domain admin user name and password when prompted.

10.7 Propagating the Domain and Starting the Servers on WCCHOST2

After you start and validate the Administration Server and WLS_WSM1 Managed Server on WCCHOST1, you can then perform the following tasks on WCCHOST2.

• Unpacking the Domain Configuration on WCCHOST2
  
• Starting the Node Manager in the Managed Server Domain Directory WCCHOST2
  
• Starting and Validating the WLS_WSM2 Managed Server on WCCHOST2
  

10.7.1 Unpacking the Domain Configuration on WCCHOST2

Now that you have the Administration Server and the first WLS_WSM1 Managed Server running on WCCHOST1, you can configure the domain on WCCHOST2.

1. Log in to WCCHOST2.
2. If you haven't already, create the recommended directory structure for the Managed Server domain on the WCCHOST2 storage device.

   Use the examples in File System and Directory Variables Used in This Guide as a guide.

3. Make sure the wcedgdomaintemplate.jar accessible to WCCHOST2.
   For example, if you are using a separate shared storage volume or partition for WCCHOST2, then copy the template to the volume or partition mounted to WCCHOST2.
4. Run the unpack command to unpack the template in the domain directory onto the local storage, as follows:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./unpack.sh -domain=MSERVER_HOME
               -overwrite_domain=true
               -template=/full_path/wcedgdomaintemplate.jar 
               -log_priority=DEBUG
               -log=/tmp/unpack.log
               -app_dir=APPLICATION_HOME
   

   In this example:

   • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain will be unpacked.

   • Replace full_path with the complete path and file name of the domain template jar file that you created when you ran the pack command to pack up the domain on the shared storage device.

   • Replace APPLICATION_HOME with the complete path to the Application directory for the domain on shared storage. For more information, see File System and Directory Variables Used in This Guide.

   Tip:

   For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Creating Templates and Domains Using the Pack and Unpack Commands.

5. Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on the WCCHOST2 local storage device.

10.7.2 Starting the Node Manager in the Managed Server Domain Directory WCCHOST2

After you unpack the domain configuration into MSERVER_HOME, WCCHOST2 will have a domain home directory structure and Node Manger to control the Managed Servers assigned to the corresponding machine in the domain configuration

Follow these steps to update and start the Node Manager from the Managed Server home:

1. Verify that the listen address in the nodemanager.properties file is set correctly, by completing the following steps:
   1. Change to the following directory:
      MSERVER_HOME/nodemanager/
   2. Open the nodemanager.properties file for editing.
   3. Update the ListenAddress property to the correct hostname as follows:
      WCCHOST1: ListenAddress=WCCHOST1
      WCCHOST2: ListenAddress=WCCHOST2
   4. Update the ListenPort property with the correct Listen Port details.
   5. Make sure that QuitEnabled is set to ‘true’. If this line is not present in the nodemanager.properties file, add the following line:
      QuitEnabled=true
2. Navigate to the following directory:

   MSERVER_HOME/bin
   

3. Use the following command to start the Node Manager:

   nohup ./startNodeManager.sh > $MSERVER_HOME/nodemanager/nodemanager.out 2>&1 &
   

For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

10.7.3 Starting and Validating the WLS_WSM2 Managed Server on WCCHOST2

Use the procedure in Starting and Validating the WLS_WSM1 Managed Server on WCCHOST1 to start and validate the WLS_WSM2 Managed Server on WCCHOST2.

10.8 Modifying the Upload and Stage Directories to an Absolute Path

After configuring the domain and unpacking it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters.

This step is necessary to avoid potential issues when performing remote deployments and for deployments that require the stage mode.

To update these directory paths for all the Managed Servers in the Managed Server domain home directory:

1. Log in to the Oracle WebLogic Server Administration Console.

2. In the left navigation tree, expand Domain, and then Environment.

3. Click Lock & Edit.

4. Navigate to and edit the appropriate objects for your cluster type.

   1. For Static Clusters, navigate to Servers and click on the name of the Managed Server to be edited.

5. For each new Managed Server or Server Template to be edited:

   1. Click the Configuration tab, and then click the Deployment tab.

   2. Verify that the Staging Directory Name is set to the following:

      MSERVER_HOME/servers/server_or_template_name/stage
      

      Replace MSERVER_HOME with the directory path for the MSERVER_HOME directory; If using static clusters, update with the correct name of the Managed Server you are editing.

   3. Update the Upload Directory Name to the following value:

      ASERVER_HOME/servers/AdminServer/upload
      

      Replace ASERVER_HOME with the directory path for the ASERVER_HOME directory.

   4. Click Save.

   5. Return to the Summary of Servers or Summary of Server Templates screen as applicable.

6. When you have modified all of the appropriate objects, click Activate Changes.

7. Restart all Managed Servers effected by these change.

10.9 Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

When you configure an Oracle Fusion Middleware domain, the domain is configured by default to use the WebLogic Server authentication provider (DefaultAuthenticator). However, for an enterprise deployment, Oracle recommends that you use a dedicated, centralized LDAP-compliant authentication provider.

The following topics describe how to use the Oracle WebLogic Server Administration Console to create a new authentication provider for the enterprise deployment domain. This procedure assumes you have already installed and configured a supported LDAP directory, such as Oracle Unified Directory or Oracle Internet Directory.

• About the Supported Authentication Providers
  
• About the Enterprise Deployment Users and Groups
  
• Prerequisites for Creating a New Authentication Provider and Provisioning Users and Groups
  
• Provisioning a Domain Connector User in the LDAP Directory
  
• Creating the New Authentication Provider
  
• Provisioning an Enterprise Deployment Administration User and Group
  
• Adding the New Administration User to the Administration Group
  
• Updating the boot.properties File and Restarting the System
  

10.9.1 About the Supported Authentication Providers

Oracle Fusion Middleware supports a variety of LDAP authentication providers. For more information, see Identity Store Types and WebLogic Authenticators in Securing Applications with Oracle Platform Security Services.

The instructions in this guide assume you will be using one of the following providers:

• Oracle Unified Directory

• Oracle Internet Directory

• Oracle Virtual Directory

Note:

By default, the instructions here describe how to configure the identity service instance to support querying against a single LDAP identity store with an unencrypted connection.

If the connection to your identity provider has to be secured through SSL, then additional keystone configuration is required for role management in the Enterprise Manager Fusion Middleware Control to function correctly. For additional configuration information, see Doc ID 1670789.1 at support.oracle.com.

Also, you can configure the service to support a virtualized identity store, which queries multiple LDAP identity stores, by using LibOVD.

For more information about configuring a Multi-LDAP lookup, refer to Configuring the Identity Store Service in Securing Applications with Oracle Platform Security Services.

10.9.2 About the Enterprise Deployment Users and Groups

The following topics provide important information on the purpose and characteristics of the enterprise deployment administration users and groups.

• About Using Unique Administration Users for Each Domain
  
• About the Domain Connector User
  
• About Adding Users to the Central LDAP Directory
  
• About Product-Specific Roles and Groups for Oracle WebCenter Portal
  
• Example Users and Roles Used in This Guide
  

10.9.2.1 About Using Unique Administration Users for Each Domain

When you use a central LDAP user store, you can provision users and groups for use with multiple Oracle WebLogic Server domains. As a result, there is a possibility that one WebLogic administration user can have access to all the domains within an enterprise.

Such an approach is not recommended. Instead, it is a best practice to assign a unique distinguished name (DN) within the directory tree for the users and groups you provision for the administration of your Oracle Fusion Middleware domains.

For example, if you plan to install and configure an Oracle WebCenter Portal enterprise deployment domain, then create a user called weblogic_wcp and an administration group called WCPAdministrators.

10.9.2.2 About the Domain Connector User

Oracle recommends that you create a separate domain connector user (for example, wcpLDAP) in your LDAP directory. This user allows the domain to connect to the LDAP directory for the purposes of user authentication. It is recommended that this user be a non-administrative user.

In a typical Oracle Identity and Access Management deployment, you create this user in the systemids container. This container is used for system users that are not normally visible to users. Placing the user into the systemids container ensures that customers who have Oracle Identity Manager do not reconcile this user.

10.9.2.3 About Adding Users to the Central LDAP Directory

After you configure a central LDAP directory to be the authenticator for the enterprise domain, then you should add all new users to the new authenticator and not to the default WebLogic Server authenticator.

To add new users to the central LDAP directory, you cannot use the WebLogic Administration Console. Instead, you must use the appropriate LDAP modification tools, such as ldapbrowser or JXplorer.

When you are using multiple authenticators (a requirement for an enterprise deployment), login and authentication will work, but role retrieval will not. The role is retrieved from the first authenticator only. If you want to retrieve roles using any other authenticator, then you must enable virtualization for the domain.

To enable virtualization:

1. Locate and open the following configuration file with a text editor:

   ASERVER_HOME/config/fmwconfig/jps-config.xml
   

2. Find the following section:

    <serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
   

3. Add the following line under the serviceInstance section or update the virtualize property as follows:

   <property name="virtualize" value="true"/>
   

   For more information about the virtualize property, see OPSS System and Configuration Properties in Securing Applications with Oracle Platform Security Services.

10.9.2.4 About Product-Specific Roles and Groups for Oracle WebCenter Portal

Each Oracle Fusion Middleware product implements its own predefined roles and groups for administration and monitoring.

As a result, as you extend the domain to add additional products, you can add these product-specific roles to the WCPAdministrators group. After they are added to the WCPAdministrators group, each product administrator user can administer the domain with the same set of privileges for performing administration tasks.

Instructions for adding additional roles to the WCPAdministrators group are provided in Common Configuration and Management Tasks for an Enterprise Deployment.

10.9.2.5 Example Users and Roles Used in This Guide

In this guide, the examples assume that you provision the following administration user and group with the DNs shown below:

• Admin User DN:

  cn=weblogic_wcp,cn=users,dc=example,dc=com
  

• Admin Group DN:

  cn=WCPAdministrators,cn=groups,dc=example,dc=com
  

• Product-specific LDAP Connector User:

  cn=wcpLDAP,cn=systemids,dc=example,dc=com
  

  This is the user you will use to connect WebLogic Managed Servers to the LDAP authentication provider. This user must have permissions to read and write to the Directory Trees:

  cn=users,dc=example,dc=com
  cn=groups,dc=example,dc=com
  

Note:

When using Oracle Unified Directory, this user will need to be granted membership in the following groups to provide read and write access:

cn=orclFAUserReadPrivilegeGroup,cn=groups,dc=example,dc=com
cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com
cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=example,dc=com
cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com

10.9.3 Prerequisites for Creating a New Authentication Provider and Provisioning Users and Groups

Before you create a new LDAP authentication provider, back up the relevant configuration files:

ASERVER_HOME/config/config.xml
ASERVER_HOME/config/fmwconfig/jps-config.xml
ASERVER_HOME/config/fmwconfig/system-jazn-data.xml

In addition, back up the boot.properties file for the Administration Server in the following directory:

ASERVER_HOME/servers/AdminServer/security

10.9.4 Provisioning a Domain Connector User in the LDAP Directory

This example shows how to create a user called wcpLDAP in the central LDAP directory.

To provision the user in the LDAP provider:

1. Create an ldif file named domain_user.ldif with the contents shown below and then save the file:

   dn: cn=wcpLDAP,cn=systemids,dc=example,dc=com
   changetype: add
   orclsamaccountname: wcpLDAP
   userpassword: password
   objectclass: top
   objectclass: person
   objectclass: organizationalPerson
   objectclass: inetorgperson
   objectclass: orcluser
   objectclass: orcluserV2
   mail: [e-mail]
   givenname: wcpLDAP
   sn: wcpLDAP
   cn: wcpLDAP
   uid: wcpLDAP
   

   Note:

   If you are using Oracle Unified Directory, then add the following four group memberships to the end of the LDIF file to grant the appropriate read/write privileges:

   dn:
   cn=orclFAUserReadPrivilegeGroup,cn=groups,dc=example,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=wcpLDAP,cn=systemids,dc=example,dc=com
   
   dn: cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=example,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=wcpLDAP,cn=systemids,dc=example,dc=com
   
   dn: cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=wcpLDAP,cn=systemids,dc=example,dc=com
   
   dn: cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=wcpLDAP,cn=systemids,dc=example,dc=com
   

2. Provision the user in the LDAP directory.

   For example, for an Oracle Unified Directory LDAP provider:

   OUD_INSTANCE_HOME/bin/ldapmodify -a \
                                    -h oudhost.example.com
                                    -D "cn=oudadmin" \
                                    -w password \
                                    -p 1389 \
                                    -f domain_user.ldif
   

   For Oracle Internet Directory:

   OID_ORACLE_HOME/bin/ldapadd -h oidhost.example.com \
                                -p 3060 \
                                -D cn="orcladmin" \
                                -w password \
                                -c \
                                -v \
                                -f domain_user.ldif
   

10.9.5 Creating the New Authentication Provider

To configure a new LDAP-based authentication provider:

1. Log in to the WebLogic Server Administration Console.

2. Click Security Realms in the left navigational bar.

3. Click the myrealm default realm entry.

4. Click the Providers tab.

   Note that there is a DefaultAuthenticator provider configured for the realm. This is the default WebLogic Server authentication provider.

   
   Description of the illustration GUID-1E1C5049-4817-4FF7-9195-7C22C48BCEC5-default.gif

5. Click Lock & Edit in the Change Center.

6. Click the New button below the Authentication Providers table.

7. Enter a name for the provider.

   Use one of the following names, based on the LDAP directory service you are planning to use as your credential store:

   • OUDAuthenticator for Oracle Unified Directory

   • OIDAuthenticator for Oracle Internet Directory

   • OVDAuthenticator for Oracle Virtual Directory

8. Select the authenticator type from the Type drop-down list.

   Select one of the following types, based on the LDAP directory service you are planning to use as your credential store:

   • OracleUnifiedDirectoryAuthenticator for Oracle Unified Directory

   • OracleInternetDirectoryAuthenticator for Oracle Internet Directory

   • OracleVirtualDirectoryAuthenticator for Oracle Virtual Directory

9. Click OK to return to the Providers screen.

10. On the Providers screen, click the newly created authenticator in the table.

11. Select SUFFICIENT from the Control Flag drop-down menu.

    
    Description of the illustration GUID-4D2D6A99-F897-4D0D-B74A-050A6ABF4C8F-default.gif

    Setting the control flag to SUFFICIENT indicates that if the authenticator can successfully authenticate a user, then the authenticator should accept that authentication and should not continue to invoke any additional authenticators.

    If the authentication fails, it will fall through to the next authenticator in the chain. Make sure all subsequent authenticators also have their control flags set to SUFFICIENT; in particular, check the DefaultAuthenticator and make sure that its control flag is set to SUFFICIENT.

12. Click Save to save the control flag settings.

13. Click the Provider Specific tab and enter the details specific to your LDAP server, as shown in the following table.

    Note that only the required fields are discussed in this procedure. For information about all the fields on this page, consider the following resources:

    • To display a description of each field, click Help on the Provider Specific tab.

    • For more information on setting the User Base DN, User From Name Filter, and User Attribute fields, see Configuring Users and Groups in the Oracle Internet Directory and Oracle Virtual Directory Authentication Providers in Administering Security for Oracle WebLogic Server 12c (12.2.1).

    Parameter	Sample Value	Value Description
    Host	For example: oud.example.com	The LDAP server's server ID.
    Port	For example: 1689	The LDAP server's port number.
    Principal	For example: cn=wcpLDAP, cn=systemids,dc=example,dc=com	The LDAP user DN used to connect to the LDAP server.
    Credential	Enter LDAP password.	The password used to connect to the LDAP server.
    SSL Enabled	Unchecked (clear)	Specifies whether SSL protocol is used when connecting to the LDAP server.
    User Base DN	For example: cn=users,dc=example,dc=com	Specify the DN under which your users start.
    All Users Filter	(&(uid=*)(objectclass=person))	Instead of a default search criteria for All Users Filter, search all users based on the uid value. If the User Name Attribute for the user object class in the LDAP directory structure is a type other than uid, then change that type in the User From Name Filter field. For example, if the User Name Attribute type is cn, then this field should be set to: (&(cn=*)(objectclass=person)))
    User From Name Filter	For example: (&(uid=%u)(objectclass=person))	If the User Name Attribute for the user object class in the LDAP directory structure is a type other than uid, then change that type in the settings for the User From Name Filter. For example, if the User Name Attribute type is cn, then this field should be set to: (&(cn=%u)(objectclass=person))).
    User Name Attribute	For example: uid	The attribute of an LDAP user object that specifies the name of the user.
    Group Base DN	For example: cn=groups,dc=example,dc=com	Specify the DN that points to your Groups node.
    Use Retrieved User Name as Principal	Checked	Must be turned on.
    GUID Attribute	entryuuid	This value is prepopulated with entryuuid when OracleUnifiedDirectoryAuthenticator is used for OUD. Check this value if you are using Oracle Unified Directory as your authentication provider.

14. Click Save to save the changes.

15. Return to the Providers page by clicking Security Realms in the right navigation pane, clicking the default realm name (myrealm), and then Providers.

16. Click Reorder, and then use the resulting page to make the Provider you just created first in the list of authentication providers.

    
    Description of the illustration GUID-C97DBDDA-B14C-472C-BB10-31BCA17B75DC-default.gif

17. Click OK.

18. In the Change Center, click Activate Changes .

19. Restart the Administration Server and all managed servers.

    To stop the Managed Servers, log in to Fusion Middleware Control, select the Managed Servers in the Target Navigator and click Shut Down in the toolbar.

    To stop and start the Administration Server using the Node Manager:

    1. Start WLST:

       cd ORACLE_COMMON_HOME/common/bin
       ./wlst.sh
       

    2. Connect to Node Manager using the Node Manager credentials you defined in when you created the domain in the Configuration Wizard:

       wls:/offline>nmConnect('nodemanager_username','nodemanager_password',
                   'ADMINVHN','5556','domain_name',
                   'ASERVER_HOME')
       

    3. Stop the Administration Server:

       nmKill('AdminServer')
       

    4. Start the Administration Server:

       nmStart('AdminServer')
       

    5. Exit WLST:

       exit()
       

    To start the Managed Servers, log in to Fusion Middleware Control, select the Managed Servers, and click Start Up in the toolbar.

20. After the restart, review the contents of the following log file:

    ASERVER_HOME/servers/AdminServer/logs/AdminServer.log
    

    Verify that no LDAP connection errors occurred. For example, look for errors such as the following:

    The LDAP authentication provider named "OUDAuthenticator" failed to make connection to ldap server at ...
    

    If you see such errors in the log file, then check the authorization provider connection details to verify they are correct and try saving and restarting the Administration Server again.

21. After you restart and verify that no LDAP connection errors are in the log file, try browsing the users and groups that exist in the LDAP provider:

    In the Administration Console, navigate to the Security Realms > myrealm > Users and Groups page. You should be able to see all users and groups that exist in the LDAP provider structure.

10.9.6 Provisioning an Enterprise Deployment Administration User and Group

This example shows how to create a user called weblogic_wcp and a group called WCPAdministrators.

To provision the administration user and group in LDAP provider:

1. Create an ldif file named admin_user.ldif with the contents shown below and then save the file:

   dn: cn=weblogic_wcp,cn=users,dc=example,dc=com
   changetype: add
   orclsamaccountname: weblogic_wcp
   userpassword: password
   objectclass: top
   objectclass: person
   objectclass: organizationalPerson
   objectclass: inetorgperson
   objectclass: orcluser
   objectclass: orcluserV2
   mail: [e-mail]
   givenname: weblogic_wcp
   sn: weblogic_wcp
   cn: weblogic_wcp
   uid: weblogic_wcp
   

2. Provision the user in the LDAP directory.

   For example, for an Oracle Unified Directory LDAP provider:

   OUD_INSTANCE_HOME/bin/ldapmodify -a \
                                    -h oudhost.example.com
                                    -D "cn=oudadmin" \
                                    -w password \
                                    -p 1389 \
                                    -f admin_user.ldif
   

   For Oracle Internet Directory:

   OID_ORACLE_HOME/bin/ldapadd -h oidhost.example.com \
                                -p 3060 \
                                -D cn="orcladmin" \
                                -w password \
                                -c \
                                -v \
                                -f admin_user.ldif
   

3. Create an ldif file named admin_group.ldif with the contents shown below and then save the file:

   dn: cn=WCPAdministrators,cn=Groups,dc=example,dc=com
   changetype: add
   objectclass: top
   objectclass: groupOfUniqueNames
   objectclass: orclGroup
   uniquemember: cn=weblogic_wcp,cn=users,dc=example,dc=com
   cn: WCPAdministrators
   displayname: WCPAdministrators
   description: Administrators Group for the Oracle WebCenter Portal Domain
   

4. Provision the group in the LDAP Directory.

   For Oracle Unified Directory:

   OUD_INSTANCE_HOME/bin/ldapmodify -a \
                                    -D "cn=oudadmin" \
                                    -h oudhost.example.com \
                                    -w password \
                                    -p 1380 \
                                    -f admin_group.ldif
   

   For Oracle Internet Directory:

   OID_ORACLE_HOME/bin/ldapadd -h oid.example.com \
                               -p 3060 \
                               -D cn="orcladmin" \
                               -w password \
                               -c \
                               -v \
                               -f admin_group.ldif
   

5. Verify that the changes were made successfully:

   1. Log in to the Oracle WebLogic Server Administration Console.

   2. In the left pane of the console, click Security Realms.

   3. Click the default security realm (myrealm).

   4. Click the Users and Groups tab.

   5. Verify that the administrator user and group you provisioned are listed on the page.

10.9.7 Adding the New Administration User to the Administration Group

After adding the users and groups to Oracle Internet Directory, the group must be assigned the Administration role within the WebLogic domain security realm. This enables all users that belong to the group to be administrators for the domain.

To assign the Administration role to the new enterprise deployment administration group:

1. Log in to the WebLogic Administration Server Console using the administration credentials that you provided in the Configuration Wizard.

   Do not use the credentials for the administration user you created and provided for the new authentication provider.

2. In the left pane of the Administration Console, click Security Realms.
3. Click the default security realm (myrealm).
4. Click the Roles and Policies tab.
5. Expand the Global Roles entry in the table and click Roles.
   
   Description of the illustration GUID-ACD10298-8167-4E09-8C24-91A5DACC091B-default.gif
6. Click the Admin role.
   
   Description of the illustration GUID-DA55366E-ABE6-442D-B137-081295E9EAEE-default.gif
7. Click Add conditions.
8. Select Group from the Predicate List drop-down menu, and then click Next.
9. Enter WCPAdministrators in the Group Argument Name field, and then click Add.

   WCPAdministrators is added to the list box of arguments.

10. Click Finish to return to the Edit Global Role page.

    The WCPAdministrators group is now listed.

11. Click Save to finish adding the Admin Role to the WCPAdministrators group.
12. Validate that the changes were made by logging in to the WebLogic Administration Server Console using the new weblogic_wcp user credentials.

    If you can log in to the Oracle WebLogic Server Administration Console and Fusion Middleware Control with the credentials of the new administration user you just provisioned in the new authentication provider, then you have configured the provider successfully.

10.9.8 Updating the boot.properties File and Restarting the System

After you create the new administration user and group, you must update the Administration Server boot.properties file with the administration user credentials that you created in the LDAP directory:

1. On WCPHOST1, go the following directory:

   ASERVER_HOME/servers/AdminServer/security
   

2. Rename the existing boot.properties file:

   mv boot.properties boot.properties.backup
   

3. Use a text editor to create a file called boot.properties under the security directory.
4. Enter the following lines in the file:

   username=weblogic_wcp
   password=password
   

5. Save the file.
6. Restart the Administration Server.

10.10 Adding the wsm-pm Role to the Administrators Group

After you configure a new LDAP-based Authorization Provider and restart the Administration Server, add the enterprise deployment administration LDAP group (WCPAdministrators) as a member to the policy.Updater role in the wsm-pm application stripe.

1. Use the Oracle WebLogic Server Administration Server credentials to log in to Oracle Enterprise Manager Fusion Middleware Control.

   These are the credentials you created when you initially configured the domain and created the Oracle WebLogic Server Administration user name (typically, weblogic_wcp) and password.

2. From the WebLogic Domain menu, select Security, and then Application Roles.
3. Select the wsm-pm application stripe from the Application Stripe drop-down menu.
4. Click the triangular play icon next to the role name text box to search for all role names in the wsm-pm application stripe.
5. Select the row for the policy.Updater role to be edited.
6. Click the Edit icon to edit the role.
7. Click the Add icon on the Edit Application Role page.
8. In the Add Principal dialog box, select Group from the Type drop-down menu.
9. Search for the enterprise deployment administrators group, by entering the group name WCPAdministrators in the Principal Name Starts With field and clicking the right arrow to start the search.
10. Select the appropriate administrators group in the search results and click OK.
11. Click OK on the Edit Application Role page.

10.11 Configuring the WebLogic Proxy Plug-In

Before you can validate that requests are routed correctly through the Oracle HTTP Server instances, you must set the WebLogic Plug-In Enabled parameter for the clusters you just configured.

1. Log in to the Oracle WebLogic Server Administration Console.
2. In the Domain Structure pane, expand the Environment node.
3. Click Lock & Edit in the Change Center.
4. Click Clusters.
5. Select the cluster to which you want to proxy requests from Oracle HTTP Server.

   The Configuration: General tab is displayed.

6. Scroll down to the Advanced section and expand it.
7. Set WebLogic Plug-In Enabled to yes.
8. Click Save.
9. If more than one cluster was deployed for the latest domain extension, repeat steps 4 through 8 until all the clusters are consistently updated.
10. Click Activate Changes in the Change Center.
11. Restart all Managed Servers in all of the clusters that you modified in this chapter.