1. Enterprise Deployment Guide for Oracle WebCenter Content
  2. Configuring the Enterprise Deployment
  3. Creating the Initial Infrastructure Domain for an Enterprise Deployment

10 Creating the Initial Infrastructure Domain for an Enterprise Deployment

It is important to understand how to install and configure an initial domain, which can be used as the starting point for an enterprise deployment. You can extend this initial domain with the various products and components that constitute the enterprise topology you are deploying.

This chapter provides information on variables used when creating the infrastructure domain, creating the database schemas and configuring the infrastructure domain.

Parent topic: Configuring the Enterprise Deployment

Variables Used When Creating the Infrastructure Domain

While creating the infrastructure domain, you will be referencing the directory variables listed in this section.

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

  • ORACLE_HOME

  • APPLICATION_HOME

  • JAVA_HOME

In addition, you'll be referencing the following virtual IP (VIP) addresses and host names defined in Reserving the Required IP Addresses for an Enterprise Deployment:

  • ADMINVHN

  • WCCHOST1

  • WCCHOST2

  • DBHOST1

  • DBHOST2

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

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

Understanding the Initial Infrastructure Domain

Before creating the initial Oracle Fusion Middleware Infrastructure domain, ensure that you review the following key concepts.

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

About the Infrastructure Distribution

You create the initial Infrastructure domain for an enterprise deployment by 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 that are 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 that are required for your enterprise deployment.

See Understanding Oracle Fusion Middleware Infrastructure in Understanding Oracle Fusion Middleware.

Parent topic: Understanding the Initial Infrastructure Domain

Characteristics of the Initial Infrastructure Domain

The following table lists some of the key characteristics of the initial Infrastructure domain. 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

Contains only an Administration Server. Managed Servers are added to the domain later, when you extend the initial domain to include Oracle Fusion Middleware products.

About a Typical Enterprise Deployment

Uses a separate virtual IP (VIP) address for the Administration Server.

Configuration of the Administration Server and Managed Servers Domain Directories

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

Parent topic: Understanding the Initial Infrastructure Domain

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.

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

Installing a Supported JDK

Oracle Fusion Middleware requires that a certified Java Development Kit (JDK) is installed on your system.

Parent topic: Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

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.

Installing the JDK Software

Install the JDK onto the VOL1 and VOL2 shared storage volumes mounted to /u01/oracle/products on the application tier hosts. Name the folder for the JDK without version numbers to avoid re-configuration challenges during JDK upgrades. Example: /u01/oracle/products/jdk.

Note:

Multiple installations may be needed as recommended mount points use multiple product shared volumes.

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

  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-8u131-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_131 /u01/oracle/products/jdk
  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
    The Java version in the output should be displayed as 1.8.0_131.
  6. Repeat steps 1 through 5 for each unique products shared volume on an appropriate host. For example: WCCHOST1 and WCCHOST2.

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 following example:
    $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.

      If you download the distribution from the Oracle Technology Network (OTN), then the JAR file is typically packaged inside a downloadable compressed file.

      To install the software required for the initial Infrastructure domain, the distribution you want to install is fmw_12.2.1.3.0_infrastructure.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.

Parent topic: Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

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 appears if you are installing any Oracle product on this host for the first time. Specify the location where you want to create your central inventory. Ensure that the operating system group name selected on this screen has write permissions to the central inventory location.

See Understanding the Oracle Central Inventory in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer.

Note:

Oracle recommends that you configure the central inventory directory on the products shared volume. Example: /u01/oracle/products/oraInventory

You may also need to execute the createCentralinventory.sh script as root from the oraInventory folder after the installer completes.

Welcome

This screen introduces you to the product installer.

Auto Updates

Use this screen to search My Oracle Support automatically for available patches or automatically search a local directory for patches that you have 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 as a consequence, the products and feature sets that 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 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 that 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 that you have 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 Oracle Fusion Middleware 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.

Parent topic: Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

Installing Oracle Fusion Middleware Infrastructure on the Other Host Computers

If you have configured a separate shared storage volume or partition for secondary hosts, then you must install the Infrastructure on one of those hosts.

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 that the web servers are installed and configured in standalone mode, so they are not considered part of the application tier domain. See Configuring the Web Tier for an Enterprise Deployment

Parent topic: Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

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 that 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 
inventory 
OPatch 
oracle_common 
oraInst.loc 
oui
wlserver
    See What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

Parent topic: Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

Disabling the Derby Database

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 starts automatically when you start the Managed Servers.
To disable the Derby database:
  1. Navigate to the following directory in the Oracle home:
    cd WL_HOME/common/derby/lib
  2. Rename the Derby library jar file:
    mv derby.jar disable_derby.jar
  3. If each host uses a separate file system, repeat steps 1 and 2 on each host.

Parent topic: Installing the Oracle Fusion Middleware Infrastructure on WCCHOST1

Creating the Database Schemas

Oracle Fusion Middleware components require the existence of schemas in a database before you configure a Fusion Middleware Infrastructure domain. Install the schemas listed in this topic 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)

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 Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Complete the following steps to install the required schemas:

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

Installing and Configuring a Certified Database

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

See the Preparing the Database for an Enterprise Deployment.

Parent topic: Creating the Database Schemas

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.
  2. Navigate to the following directory on WCCHOST1:
    ORACLE_HOME/oracle_common/bin
  3. Start RCU:
    ./rcu

    Note:

    If your database has Transparent Data Encryption (TDE) enabled, and you want to encrypt your tablespaces created by the RCU, provide the -encryptTablespace true option when you start the RCU.

    This will default the appropriate RCU GUI Encrypt Tablespace checkbox selection on the Map Tablespaces screen without further effort during the RCU execution. See Encrypting Tablespaces in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Parent topic: Creating the Database Schemas

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

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 generates a SQL script, which can be provided to your database administrator. See Understanding System Load and Product Load in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Click Next.

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 Connection Details

Provide the database connection details for RCU to connect to your database.

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

  2. Enter the Port number of the RAC database scan listener, for example 1521.

  3. Enter the RAC Service Name of the database.

  4. Enter the User Name of a user that has permissions to create schemas and schema objects, for example SYS.

  5. Enter the Password of the user name that you provided in step 4.

  6. If you have selected the SYS user, ensure that you set the role to SYSDBA.

  7. Click Next to proceed, and 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 Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Task 4   Specifying a Custom Prefix and Selecting Schemas

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

    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 FMW1221_

    Tip:

    Make a note of the custom prefix that you choose to enter here; you l 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 the schemas in this section are automatically selected.

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

There are two mandatory schemas that are selected by default. You cannot deselect them: Common Infrastructure Services (the STB schema) and WebLogic Services (the WLS schema). The Common Infrastructure Services schema enables you to retrieve information from RCU during domain configuration. See Understanding the Service Table Schema in Oracle Fusion Middleware 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 Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Click Next to proceed, and 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. Ensure that the complexity of the passwords meet the database security requirements before you continue. RCU proceeds at this point even if you do not meet the password polices. Hence, perform this check outside RCU itself.

Click Next.

Tip:

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

Task 6   Verifying the Tablespaces for the Required Schemas

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.

Note:

You can configure a Fusion Middleware component to use JDBC stores for JMS servers and Transaction Logs, by using the Configuration Wizard. These JDBC stores are placed in the Weblogic Services component tablespace. If your environment expects to have a high level of transactions and JMS activity, you can increase the default size of the <PREFIX>_WLS tablespace to better suit the environment load.

Click Next to continue, and then click OK on the dialog window to confirm the tablespace creation.

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

Task 7   Creating Schemas

Review the summary of the schemas to be loaded and click Create to complete schema creation.

Note:

If failures occurred, review the listed log files to identify the root cause, resolve the defects, and then use RCU to drop and recreate the schemas before you continue.

Task 8   Reviewing Completion Summary and Completing RCU Execution

When you reach the Completion Summary screen, verify that all schema creations have been completed successfully, and then click Close to dismiss RCU.

Parent topic: Creating the Database Schemas

Verifying Schema Access

Verify schema access by connecting to the database as the new schema users are created by the RCU. Use SQL*Plus or another utility to connect, and provide the appropriate schema names and passwords entered in the RCU.

For example:

./sqlplus

SQL*Plus: Release 12.1.0.2.0 Production on Wed Mar 15 03:17:54 2017

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Enter user-name: FMW1221_WLS
Enter password: WLS_schema_password
Last Successful login time: Tue Feb 28 2017 09:37:25 -07:00

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Real Application Clusters, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options

SQL>

Parent topic: Creating the Database Schemas

Configuring the Infrastructure Domain

You can create and configure a WebLogic domain for the enterprise deployment topology 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 WebLogic Domains Using the Configuration Wizard.

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

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

Parent topic: Configuring the Infrastructure Domain

Navigating the Configuration Wizard Screens to Configure the Infrastructure Domain

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

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:

For 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]

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. Refer to creating-initial-infrastructure-domain-enterprise-deployment.html#GUID-CF612A2F-B312-458C-9D48-517D2357C2C4__BABHHCBF for a partial screen shot of a sample Database Configuration Type screen.

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 operation succeeded: 

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

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 the High Availability Guide.

To convert the data sources to GridLink:

  1. Select all the schemas by selecting the check box 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 Table 10-2 and in creating-initial-infrastructure-domain-enterprise-deployment.html#GUID-CF612A2F-B312-458C-9D48-517D2357C2C4__BABJBCFF.

Table 10-2 Recommended Values for Selected Fields on the GridLink Oracle RAC Component Schema Screen

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 Port field, enter the SCAN address for the Oracle RAC database.

In the Port field, enter the ONS Remote port (typically, 6200).

Enable Fan

Select the Enable Fan check box to 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 configure the Managed Servers and cluster, and also for configuring the machine and targeting the Managed Servers to the machine.

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

There are no Managed Servers in the initial Infrastructure domain. Click Next to proceed to the next screen.

Task 14   Configuring a Cluster

There are no clusters in the initial Infrastructure domain. Click Next to proceed to the next screen.

Task 15   Configure Server Templates

There are no server templates in the initial Infrastructure domain. Click Next to proceed to the next screen.

Task 16   Configure Coherence Clusters

There are no clusters in the initial Infrastructure domain. Click Next to proceed to the next screen.

Task 17   Creating Machines

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.

  1. Select the Unix Machine tab.

  2. Click the Add button to create a new Unix machine.

    Use the values in Table 10-3 to define the Name and Node Manager Listen Address of the new 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-3 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

Tip:

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

Task 18   Assigning Server To Machine

Complete the following steps:

  1. Select admin server from the Server pane.

  2. Select ADMINHOST from the Machines pane.

  3. Click Next to proceed to the next screen.

Task 19   Reviewing Virtual Targets

Click Next to proceed to the next screen.

Task 20   Reviewing Partitions

Click Next to proceed to the next screen.

Task 21   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 22   Monitoring Configuration Progress

After all the processes are complete, click Next to proceed to the next screen.

Task 23   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 Node Manager and Administration Server, and the URL is needed to access the Administration Server.

Click Finish to dismiss the configuration wizard.

Parent topic: Configuring the Infrastructure Domain

Starting the Administration Server

After the domain is created, you can then perform the following tasks 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. When you start the Administration Server, the credentials that you enter in this file are encrypted.
  • 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 by 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 you proceed with the configuration steps, validate that the Administration Server has started successfully by making sure that you have access to the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control; both of these are installed and configured on the Administration Servers.

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

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.

Parent topic: Starting the Administration Server

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. When you start the Administration Server, the credentials that you enter in this file are encrypted.

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 that you 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 are 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 are encrypted.

  3. Save the file and close the editor.

Parent topic: Starting 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 by 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 by using the Node Manager:

  1. Start the WebLogic Scripting Tool (WLST):
    cd ORACLE_COMMON_HOME/common/bin
./wlst.sh
  2. Connect to Node Manager by 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 the WSM-PM Managed Servers are not yet started, and so, the following message appears 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()

Parent topic: Starting the Administration Server

Validating the Administration Server

Before you proceed with the configuration steps, validate that the Administration Server has started successfully by making sure that you have access to the Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control; both of these 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

Parent topic: Starting the Administration Server

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 that you have already installed and configured a supported LDAP directory, such as Oracle Unified Directory or Oracle Internet Directory.

Parent topic: Creating the Initial Infrastructure Domain for an Enterprise Deployment

About the Supported Authentication Providers

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

The instructions in this guide assume that you are using one of the following providers:

  • Oracle Unified Directory

  • Oracle Internet Directory

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

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

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.

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

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.

It is a best practice to create and assign a unique distinguished name (DN) within the directory tree for the users and groups that you provision for the administration of your Oracle Fusion Middleware domains.

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

About the Domain Connector User

Oracle recommends that you create a separate domain connector user (for example, wccLDAP) 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 Governance do not reconcile this user.

A few products, such as IPM require the domain connector user to have the permission to modify data of the LDAP directory. If such products are included, then the domain connector user should be the administrative user.

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. Browse to the Fusion Middleware Control, and log in with the administrative credentials.

    http://adminvhn:7001/em

  2. Navigate to WebLogic Domain > Security > Security Provider Configuration.

  3. Expand Security Store Provider.

  4. Expand Identity Store Provider.

  5. Click Configure.

  6. Add a custom property.

  7. Select property virtualize with value true and click OK.

  8. Select property user.create.bases, example value used in this guide is cn=users,dc=example,dc=com.

  9. Select property group.create.bases, example value used in this guide is cn=groups,dc=example,dc=com.

  10. Click OK again to persist the change.

  11. Restart the Administration Server and all managed servers.

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

About Product-Specific Roles and Groups for Oracle WebCenter Content

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 WCCAdministrators group. After they are added to the WCCAdministrators group, each product administrator user can administer the domain with the same set of privileges for performing administration tasks.

For instructions on adding additional roles to the WCCAdministrators group, see Common Configuration and Management Tasks for an Enterprise Deployment.

Example Users and Groups Used in This Guide

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

  • Admin User DN:

    cn=weblogic_wcc,cn=users,dc=example,dc=com

  • Admin Group DN:

    cn=WCCAdministrators,cn=groups,dc=example,dc=com
  • Product-specific LDAP Connector User:
    cn=wccLDAP,cn=systemids,dc=example,dc=com
    This is the user that you 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:

This user needs 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

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

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

Backing up the Configuration

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
Enabling Authentication Provider Virtualization

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. Sign-in to the Fusion Middleware Control by using the administrator's account. For example: weblogic. 

    http://adminvhn:7001/em

  2. Click WebLogic Domain > Security > Security Provider Configuration.

  3. Expand Security Store Provider.

  4. Expand Identity Store Provider.

  5. Click Configure.

  6. Add a custom property.

  7. Select property virtualize with value true and click OK.

  8. Click OK again to persist the change.

  9. Restart the Administration Server and all managed servers.

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

Provisioning a Domain Connector User in the LDAP Directory

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

To provision the user in the LDAP provider:

  1. Create an LDIF file named domain_user.ldif with the following contents and then save the file: 

    dn: cn=wccLDAP,cn=systemids,dc=example,dc=com
changetype: add
orclsamaccountname: wccLDAP
userpassword: password
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetorgperson
objectclass: orcluser
objectclass: orcluserV2
mail: wccLDAP@example.com
givenname: wccLDAP
sn: wccLDAP
cn: wccLDAP
uid: wccLDAP

    Note:

    If you use 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=wccLDAP,cn=systemids,dc=example,dc=com

dn: cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=example,dc=com
changetype: modify
add: uniquemember
uniquemember: cn=wccLDAP,cn=systemids,dc=example,dc=com

dn: cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com
changetype: modify
add: uniquemember
uniquemember: cn=wccLDAP,cn=systemids,dc=example,dc=com

dn: cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com
changetype: modify
add: uniquemember
uniquemember: cn=wccLDAP,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 idstore.example.com
                                 -D "cn=oudadmin" \
                                 -w password \
                                 -p 1389 \
                                 -f domain_user.ldif

    For Oracle Internet Directory:

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

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

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 edg_default_authenticator.gif follows
    Description of the illustration edg_default_authenticator.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 that you plan 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 that you plan 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 edg_provider_control_flag.gif follows
    Description of the illustration edg_provider_control_flag.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 falls 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 option 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:

    Parameter Sample Value Value Description

    Host

    For example: idstore.example.com

    The LDAP server's server ID.

    Port

    For example: 1389

    The LDAP server's port number.

    Principal

    For example: cn=wccLDAP, 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 use Oracle Unified Directory as your authentication provider.

  14. Click Save to save the changes.

  15. Click Security Realms in the right navigation pane, and then click the default realm name (myrealm), and then Providers to return to the Providers page.

  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 edg_provider_order.gif follows
    Description of the illustration edg_provider_order.gif

  17. Click OK.

  18. On the Providers Page, click DefaultAuthenticator.

  19. From the Control Flag drop-down, select SUFFICIENT.

  20. Click Save to update the DefaultAuthenticator settings.

  21. In the Change Center, click Activate Changes.

  22. Restart the Administration Server.

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

  23. 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 that they are correct and try saving and restarting the Administration Server again.

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

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

Provisioning an Enterprise Deployment Administration User and Group

This example shows how to create a user called weblogic_wcc and a group called WCCAdministrators.

To provision the administration user and group in LDAP provider:

  1. Create an LDIF file named admin_user.ldif with the following contents and then save the file: 

    dn: cn=weblogic_wcc,cn=users,dc=example,dc=com
changetype: add
orclsamaccountname: weblogic_wcc
userpassword: password
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetorgperson
objectclass: orcluser
objectclass: orcluserV2
mail: weblogic_wcc@example.com
givenname: weblogic_wcc
sn: weblogic_wcc
cn: weblogic_wcc
uid: weblogic_wcc

  2. Provision the user in the LDAP directory.

    For example, for an Oracle Unified Directory LDAP provider:

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

    For Oracle Internet Directory:

    OID_ORACLE_HOME/bin/ldapadd -h idstore.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 following contents and then save the file: 

    dn: cn=WCCAdministrators,cn=Groups,dc=example,dc=com
displayname: WCCAdministrators
objectclass: top
objectclass: groupOfUniqueNames
objectclass: orclGroup
uniquemember: cn=weblogic_wcc,cn=users,dc=example,dc=com
cn: WCCAdministrators
uniquemember: cn=wccLDAP, cn=systemids, dc=example, dc=com
cn: WCCAdministrators
description: Administrators Group for the Oracle WebCenter Content 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 oidhost.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 that you provisioned are listed on the page.

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

Adding the Administration Role to the New Administration Group

After you add 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 by using the administration credentials that you provided in the Configuration Wizard.

    Do not use the credentials for the administration user that 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.

    Figure 10-1 Global Roles Under Security Realms

    Description of Figure 10-1 follows
    Description of "Figure 10-1 Global Roles Under Security Realms"
  6. Click the Admin role.

    Figure 10-2 Adding Conditions for the Admin Role

    Description of Figure 10-2 follows
    Description of "Figure 10-2 Adding Conditions for the Admin Role"
  7. Click Add conditions.
  8. Select Group from the Predicate List drop-down menu, and then click Next.
  9. Enter WCCAdministrators in the Group Argument Name field, and then click Add.

    WCCAdministrators is added to the list box of arguments.

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

    The WCCAdministrators group is now listed.

  11. Click Save to finish adding the Admin Role to the WCCAdministrators group.
  12. Validate that the changes were made by logging in to the WebLogic Administration Server Console by using the new weblogic_wcc 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 that you just provisioned in the new authentication provider, then you have configured the provider successfully.

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group

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 WCCHOST1, 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_wcc
password=password
  5. Save the file.
  6. Restart the Administration Server.

Parent topic: Creating a New LDAP Authenticator and Provisioning Enterprise Deployment Users and Group