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.
• Understanding 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 in Preparation for an Enterprise Deployment
  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 a Per Host Node Manager for an Enterprise Deployment
  For specific enterprise deployments, Oracle recommends that you configure a per-host Node Manager, as opposed to the default per-domain Node Manager.
• Configuring the Domain Directories and Starting the Servers on SOAHOST1
  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 SOAHOST1.
• Propagating the Domain and Starting the Servers on SOAHOST2
  After you start and validate the Administration Server and WLS_WSM1 Managed Server on SOAHOST1, you can then perform the following tasks on SOAHOST2.
• Modifying the Upload and Stage Directories to an Absolute Path
  After creating the domain and unpacking it to the Managed Server domain directory, verify and update the upload and stage directories for the Managed Servers.
• 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 (SOA Administrators) as a member to the wsm-pm application stripe role: policy.Updater.

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:

• ADMINVHN

• SOAHOST1

• SOAHOST2

• DBHOST1

• DBHOST2

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

10.2 Understanding 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 Initial Infrastructure 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 (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 Initial Infrastructure Domain

Table 10-1 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.

Table 10-1 Characteristics of the Initial Infrastructure domain

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 host 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 in Preparation for an Enterprise Deployment

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 SOAHOST1
  
• Navigating the Infrastructure Installation Screens
  
• Installing Oracle Fusion Middleware Infrastructure on the Other Host Computers
  
• Checking the Directory Structure
  

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.

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

1. Change directory to the location where you downloaded the JDK archive file.
2. Unpack the archive into the JDK home directory, and then run these commands:

   cd download_dir
   tar -xzvf jdk-8u51-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_51 /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_51" 
     Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
     Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
   

10.3.2 Starting the Infrastructure Installer on SOAHOST1

To start the installation program, perform the following steps.

1. Log in to SOAHOST1.
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.0.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.

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.

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.
Auto Updates - Patch Selection	This screen appears if both of the following statements are true: You searched for available patches earlier in the installation session, using the Auto Updates screen. The Auto Updates feature located one or more application patches that must be applied to the Oracle home you are creating in this installation session. This screen lists the patches that were found by the Auto Updates feature. Select one or more patches and click Next to apply the selected patches to the Oracle home.
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 SOAHOST2, then you must also install the Infrastructure on SOAHOST2.

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 SOAHOST1 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 following directory and sub-directories. The contents of your installation vary based on the options you selected during the installation.

To check the directory structure:

1. Change directory to the ORACLE_HOMEdirectory.
2. Enter the following command:
   ls -l
   The directory structure on your system should match the structure shown in the following example:

   /u01/oracle/products/fmw/
   
   cfgtoollogs
   coherence
   em
   install
   inventory
   OPatch
   oracle_common
   oraInst.loc
   oui
   root.sh
   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. Navigate to the ORACLE_HOME/oracle_common/bin directory on your system.
2. Make sure the JAVA_HOME environment variable is set to the location of a certified JDK on your system. The location should be up to but not including the bin directory. For example, if your JDK is located in /u01/oracle/products/jdk:

   On UNIX operating systems:

   export JAVA_HOME=/u01/oracle/products/jdk
   

3. Start RCU:

   On UNIX operating systems:

   ./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 Concurrently on the Create Repository screen. The procedure in this document assumes that you have the necessary privileges.

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

Tip:

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

Task 3    Providing Database Credentials

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

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.

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

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.

Description of the illustration GUID-DCC1E24A-F5EC-43F0-8F13-AC2CFDEA8AAA-default.png

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

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

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.0 [em]

  Selecting this template automatically selects the following dependencies:

  • Oracle JRF - 12.2.1.0 [oracle_common]

  • WebLogic Coherence Cluster Extension - 12.2.1.0 [wlserver]

• Oracle WSM Policy Manager - 12.2.1.0 [oracle_common]

Description of the illustration GUID-A1464A2D-0AB5-43D0-ACD7-58E662A72A9D-default.png

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 Figure 10-1 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.

Figure 10-1 Setting the Database Configuration Type for an Enterprise Deployment

Description of "Figure 10-1 Setting the Database Configuration Type for an Enterprise Deployment"

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

Figure 10-2 Sample Values for the GridLink Oracle RAC Component Schema Scree

Description of "Figure 10-2 Sample Values for the GridLink Oracle RAC Component Schema Scree"

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.

• Managed Servers, Clusters and Coherence

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

• JMS 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 Manual Node Manager Setup as the Node Manager type.

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

   Be sure to enter the host name that corresponds to SOAHOST1; 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, WSM-CACHE-SVR, and WSMPM-MAN-SVR. (See Figure 10-3 .)

   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 configured automatically by the WSM-CACHE-SVR server group and is suitable for most applications. 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.

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

   For the Listen Address, enter SOAHOST2. 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.

Figure 10-3 Using the Configuration Wizard to Define Managed Servers for an Enterprise Deployment

Description of "Figure 10-3 Using the Configuration Wizard to Define Managed Servers for an Enterprise Deployment"

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. Leave the other fields empty.

Description of the illustration GUID-2D68E3CF-47FC-46D9-8296-EB108EC95884-default.gif

Tips

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

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

Description of the illustration GUID-9C11A36A-1797-4740-84B8-7BC120D538A5-default.gif

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 16    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, refer to "Oracle Coherence" in Oracle Fusion Middleware Licensing Information.

Task 17    Creating Machines

Use the Machines screen to create three 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 three new Unix machines.

   Use the values in Table 10-2 to define the Name and Node Manager Listen Address of each machine. Figure 10-4 shows a portion of the Machines screen, with example values for 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
SOAHOST1	The value of the SOAHOST1 host name variable. For example, SOAHOST1.example.com.	5556
SOAHOST2	The value of the SOAHOST2 host name variable. For example, SOAHOST2.example.com.	5556
ADMINHOST	Enter the value of the ADMINVHN variable.	5556

Figure 10-4 Example Values for the Configuration Wizard Unix Machines Screen

Description of "Figure 10-4 Example Values for the Configuration Wizard Unix Machines Screen"

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 Servers to Machines

Use the Assign Servers to Machines screen to assign the Administration Server and the two Managed Servers to the appropriate machine.

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 Managed Server 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 SOAHOST1 machine.

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

Description of the illustration GUID-5F925E0C-46BF-402C-9C61-4AFD7F120402-default.gif

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

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 20    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 21    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 a Per Host Node Manager for an Enterprise Deployment

For specific enterprise deployments, Oracle recommends that you configure a per-host Node Manager, as opposed to the default per-domain Node Manager.

For more information about the advantages of a per host Node Manager, see About the Node Manager Configuration in a Typical Enterprise Deployment

• Creating a Per Host Node Manager Configuration
  The step in configuring a per-host Node Manager is to create a configuration directory and two new node manager configuration files. You must also edit the default startNodeManager.sh file.
• Creating the boot.properties File
  You must create a boot.properties if you want start the Node Manager without being prompted for the Node Manager 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 Node Manager on SOAHOST1
  After you manually set up the Node Manager to use a per-host Node Manager configuration, you can start the Node Manager on SOAHOST1, using the startNodeManager.sh script.
• Configuring the Node Manager Credentials and Type
  By default, a per-host Node Manager configuration does not use Secure Socket Layer (SSL) for for Node Manager-to-server communications. As a result, you must configure each machine in the domain to use a communication type of “plain,” rather than SSL. In addition, you should set the Node Manager credentials so you can connect to the Administration Server and Managed Servers in the domain.

10.6.1 Creating a Per Host Node Manager Configuration

The step in configuring a per-host Node Manager is to create a configuration directory and two new node manager configuration files. You must also edit the default startNodeManager.sh file.

To create a per-host Node Manager configuration, perform the following tasks, first on SOAHOST1, and then on SOAHOST2:

1. Log in to SOAHOST1 and create a directory for the Node Manager configuration files :

   For example:

   mkdir —p /u02/oracle/config/nodemanager
   

   Note that this directory should be on a local disk, because it is specific to the host. This directory location is known as the Node Manager home, and it is identified by the NM_HOME directory variable in examples in this guide.

2. Change directory to the Node Manager home directory:

   cd NM_HOME
   

3. Create a new text file called nodemanager.properties and add the values shown in Example 10-1 to this new file.

   For more information about the properties you can add to the nodemanager.properties file, see Node Manager Properties in Administering Node Manager for Oracle WebLogic Server.

   As part of this configuration in the nodemanager.properties file, you will enable Crash Recovery for the Node Manager. For more information, see “Node Manager and System Crash Recovery” in Administering Node Manager for Oracle WebLogic Server.

4. Locate the startNodeManager.sh file in the following directory:

   WL_HOME/server/bin
   

5. Copy the startNodeManager.sh file to the Node Manager home directory.
6. Edit the new startNodeManager.sh file and add the NODEMGR_HOME property as follows:

   NODEMGR_HOME="NM_HOME"
   

   In this example, replace NM_HOME with the actual path to the Node Manager home.

7. Create another new file in the Node Manager home directory, called nodemanager.domains.

   The nodemanager.domains file provides additional security by restricting Node Manager client access to the domains listed in this file.

8. Perform steps 1 though 7 on SOAHOST2.
9. Add the following entries to the new nodemanager.domains files:

   On SOAHOST1, add values for both the Administration Server domain home and the Managed Servers domain home:

   soaedg_domain=MSERVER_HOME;ASERVER_HOME
   

   On SOAHOST2, add the value for the Managed Servers domain home only:

   soaedg_domain=MSERVER_HOME
   

   In these examples, replace ASERVER_HOME and MSERVER_HOME with the values of the respective variables, as described in File System and Directory Variables Used in This Guide.

Example 10-1 Contents of the nodemanager.properties File

DomainsFile=/u02/oracle/config/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=12.2.1
AuthenticationEnabled=true
NodeManagerHome=/u02/oracle/config/nodemanager
#Include the specific JDK home
JavaHome=/u01/oracle/products/jdk
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
#Leave blank for listening on ANY
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/u02/oracle/config/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50

10.6.2 Creating the boot.properties File

You must create a boot.properties if you want start the Node Manager without being prompted for the Node Manager 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 Node Manager on SOAHOST1

After you manually set up the Node Manager to use a per-host Node Manager configuration, you can start the Node Manager on SOAHOST1, using the startNodeManager.sh script.

To start the Node Manager on SOAHOST1:

1. Change directory to the Node Manager home directory:

   cd NM_HOME
   

2. Run the following command to start the Node Manager and send the output of the command to an output file, rather than to the current terminal shell:

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

3. Monitor the the nodemanager.out file; make sure the NodeManager starts successfully. The output should eventually contain a string similar to the following:
   <INFO><Plain socket listener started on port 5556>

10.6.4 Configuring the Node Manager Credentials and Type

By default, a per-host Node Manager configuration does not use Secure Socket Layer (SSL) for for Node Manager-to-server communications. As a result, you must configure each machine in the domain to use a communication type of “plain,” rather than SSL. In addition, you should set the Node Manager credentials so you can connect to the Administration Server and Managed Servers in the domain.

The following procedure temporarily starts the Administration Server with the default start script, so you can perform these tasks. After you perform these tasks, you can stop this temporary session and use the Node Manager to start the Administration Server.

1. Start the Administration Server, using the default start script:
   1. Change directory to the following directory:

      cd ASERVER_HOME/bin
      

   2. Run the start script:

      ./startWebLogic.sh
      

      Watch the output to the terminal, until you see the following:

      <Server state changed to RUNNING>
      

2. Log in to the WebLogic Server Administration Console, using the WebLogic administrator user and password.
3. Configure the Node Manager type:
   1. Click Lock & Edit.
   2. In the Domain Structure navigation tree, expand Domain, and then Environment.
   3. Click Machines.
   4. Click the link for the ADMINHOST machine.
   5. Click the Node Manager tab.
   6. Change the Type property from SSL to Plain.
   7. Click Save.
   8. Repeat this task for each machine in the domain.
   9. Click Activate Changes.
4. Set the Node Manager credentials:
   1. Click Lock & Edit.
   2. In the Domain Structure navigation pane, click the name of the domain.
   3. Select the Security tab.
      The Security > General tab should be selected.
   4. Scroll down and expand the Advanced security options.
   5. Make a note of the user name in the NodeManager Username field.
      Optionally, you can edit the value to create a new Node Manager user name.
   6. Enter a new password in the NodeManager Password and Confirm NodeManager Password fields
   7. Click Save and then Activate Changes.
5. In a new terminal window, use the following steps to refresh the SystemSerialized.dat file. Without this step, you won’t be able to connect to the Node Manager and use it to start the servers in domain:
   1. Change directory to the
      cd ORACLE_COMMON_HOME/common/bin
   2. Start the WebLogic Server Scripting Tool (WLST):
      ./wlst.sh
   3. Connect to the Administration Server, using the following WLST command:
      connect('admin_user','admin_password','admin_url')

      For example:

      connect('weblogic','mypassword','t3://ADMINVHN:7001')

   4. Use the nmEnroll command to enables the Node Manager to manage servers in a specified WebLogic domain.
      nmEnroll('ASERVER_HOME')

      For example:

      nmEnroll('/u01/oracle/config/domains/soaedg_domain')

6. Optionally, if you want to customize any startup properties for the Administration Server, you can use the following WLST command to create a startup.properties file for the Administration Server:
   nmGenBootStartupProps('AdminServer')

   The startup.properties file is created in the following directory:

   ASERVER_HOME/servers/AdminServer/data/nodemanager/
   

7. Return to the terminal window where you started the Administration Server with the start script.
8. Press Ctrl/C to stop the Administration Server process.

   Wait for the Administration Server process to end and for the terminal command prompt to appear.

10.7 Configuring the Domain Directories and Starting the Servers on SOAHOST1

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

• 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 Adminstration 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 Serverls.
• Disabling the Derby Database
  
• Creating a Separate Domain Directory for Managed Servers on SOAHOST1
  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 SOAHOST1 and SOAHOST2. The domain directory on the local (or private) storage will be used to run the Managed Servers.
• Starting and Validating the WLS_WSM1 Managed Server on SOAHOST1
  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 SOAHOST1.

10.7.1 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 Adminstration 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 you defined in the WebLogic Server Administration Console:

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

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

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

10.7.4 Creating a Separate Domain Directory for Managed Servers on SOAHOST1

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 SOAHOST1 and SOAHOST2. 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 tmp 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. Log in to SOAHOST1 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=complete_path/soadomaintemplate.jar 
             -template_name=soa_domain_template
   

   In this example:

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

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

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

   • soa_domain_template is the name assigned to the domain template file.

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

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

   ORACLE_COMMON_HOME/common/bin/
   

   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 SOAHOST1 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=complete_path/soadomaintemplate.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 complete_path with the complete path to the location where you created or copied the template jar file.

   • soadomaintemplate.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 SOAHOST1 local storage device.

10.7.5 Starting and Validating the WLS_WSM1 Managed Server on SOAHOST1

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

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 then click Control > Start on the tool bar.
5. To verify that the Managed Server is working correctly, open your browser and enter the following URL:

   SOAHOST1:7010/wsm-pm/
   

   Enter the domain admin user name and password when prompted.

10.8 Propagating the Domain and Starting the Servers on SOAHOST2

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

• Unpacking the Domain Configuration on SOAHOST2
  
• Unpacking the Domain on SOAHOST2
  
• Starting the Node Manager on SOAHOST2
  
• Starting and Validating the WLS_WSM2 Managed Server on SOAHOST2
  

10.8.1 Unpacking the Domain Configuration on SOAHOST2

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

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

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

3. Make sure the soadomaintemplate.jar accessible to SOAHOST2.
   For example, if you are using a separate shared storage volume or partition for SOAHOST2, then copy the template to the volume or partition mounted to SOAHOST2.
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=complete_path/soadomaintemplate.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 complete_path/soadomaintemplate.jar 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 SOAHOST2 local storage device.

10.8.2 Unpacking the Domain on SOAHOST2

This procedure assumes you have copied the file that you created earlier in a location that is accessible from both SOAHOST1 and SOAHOST2; such as the ASERVER_HOME directory, which is located on the shared storage filer:

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

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

3. Make sure the soadomaintemplate.jar accessible to SOAHOST2.
   For example, if you are using a separate shared storage volume or partition for SOAHOST2, then copy the template to the volume or partition mounted to SOAHOST2.
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=complete_path/soadomaintemplate.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 complete_path/soadomaintemplate.jar 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 SOAHOST2 local storage device.

10.8.3 Starting the Node Manager on SOAHOST2

After you manually set up the Node Manager to use a per host Node Manager configuration, you can start the Node Manager using the following commands on SOAHOST2:

1. Change directory to the Node Manager home directory:

   cd NM_HOME
   

2. Run the following command to start the Node Manager and send the output of the command to an output file, rather than to the current terminal shell:

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

10.8.4 Starting and Validating the WLS_WSM2 Managed Server on SOAHOST2

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

10.9 Modifying the Upload and Stage Directories to an Absolute Path

After creating the domain and unpacking it to the Managed Server domain directory, verify and update the upload and stage directories for the Managed Servers.

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

5. For each Managed Server in the Managed Server domain home directory:

   1. Click the name of the Managed Server.

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

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

      MSERVER_HOME/servers/server_name/stage
      

      Replace MSERVER_HOME with the directory path for the MSERVER_HOME directory; replace server_name with the name of the Server you are editing.

      Note that if you plan to configure the staging directory for the Administration Server, then you must set the property is set to:

      ASERVER_HOME/servers/AdminServer/stage
      

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

   5. Click Save.

   6. Return to the Summary of Servers screen.

6. When you have modified these values for each Managed Server, click Activate Changes.

7. Restart all Managed Servers.

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

However, you can configure the service to support a virtualized identity store, which queries multiple LDAP identity stores, 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.10.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 SOA Suite
  
• Example Users and Roles Used in This Guide
  

10.10.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 SOA Suite enterprise deployment domain, then create a user called weblogic_soa and an administration group called SOA Administrators.

10.10.2.2 About the Domain Connector User

Oracle recommends that you create a separate domain connector user (for example, soaLDAP) 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.10.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.

Enabling virtualization involves the following steps:

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

   DOMAIN_HOME/config/fmwconfig/jps-config.xml
   

2. Add or update the following 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.10.2.4 About Product-Specific Roles and Groups for Oracle SOA Suite

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 SOA Administrators group. After they are added to the SOA Administrators 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 SOA Administrators group are provided in Common Configuration and Management Tasks for an Enterprise Deployment.

10.10.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_soa,cn=users,dc=example,dc=com
  

• Admin Group DN:

  cn=SOA Administrators,cn=groups,dc=example,dc=com
  

• Product-specific LDAP Connector User:

  cn=soaLDAP,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.10.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:

DOMAIN_HOME/servers/AdminServer/security

10.10.4 Provisioning a Domain Connector User in the LDAP Directory

This example shows how to create a user called soaLDAP 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=soaLDAP,cn=systemids,dc=example,dc=com
   changetype: add
   orclsamaccountname: soaLDAP
   userpassword: password
   objectclass: top
   objectclass: person
   objectclass: organizationalPerson
   objectclass: inetorgperson
   objectclass: orcluser
   objectclass: orcluserV2
   mail: [e-mail]
   givenname: soaLDAP
   sn: soaLDAP
   cn: soaLDAP
   uid: soaLDAP
   

   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=us,dc=oracle,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=soaLDAP,cn=systemids,dc=us,dc=oracle,dc=com
   
   dn: cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=us,dc=oracle,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=soaLDAP,cn=systemids,dc=us,dc=oracle,dc=com
   
   dn: cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=soaLDAP,cn=systemids,dc=example,dc=com
   
   dn: cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com
   changetype: modify
   add: uniquemember
   uniquemember: cn=soaLDAP,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.10.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.

    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=soaLDAP, 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','PLAIN')
       

    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.10.6 Provisioning an Enterprise Deployment Administration User and Group

This example shows how to create a user called weblogic_soa and a group called SOA Administrators.

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_soa,cn=users,dc=example,dc=com
   changetype: add
   orclsamaccountname: weblogic_soa
   userpassword: password
   objectclass: top
   objectclass: person
   objectclass: organizationalPerson
   objectclass: inetorgperson
   objectclass: orcluser
   objectclass: orcluserV2
   mail: [e-mail]
   givenname: weblogic_soa
   sn: weblogic_soa
   cn: weblogic_soa
   uid: weblogic_soa
   

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=SOA Administrators,cn=Groups,dc=example,dc=com
   displayname: SOA Administrators
   objectclass: top
   objectclass: SOA Administrators
   objectclass: orclGroup
   uniquemember: cn=weblogic_soa,cn=users,dc=example,dc=com
   cn:SOA Administrators
   description: Administrators Group for the Oracle SOA Suite 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 3060 \
                                    -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.10.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 button.
8. Select Group from the Predicate List drop-down menu, and then click Next.
9. Enter SOA Administrators in the Group Argument Name field, and then click Add.

   SOA Administrators is added to the list box of arguments.

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

    The SOA Administrators group is now listed.

11. Click Save to finish adding the Admin Role to the SOA Administrators group.
12. Validate that the changes were made by logging in to the WebLogic Administration Server Console using the new weblogic_soa 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.10.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 SOAHOST1, 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_soa
   password=password
   

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

10.11 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 (SOA Administrators) as a member to the wsm-pm application stripe role: policy.Updater.

To perform this task, refer to Configuring Roles for Administration of Oracle SOA Suite Products.