Oracle® Fusion Middleware

Installation Guide for Oracle Identity Management

11g Release 1 (11.1.1.7.0)

E12002-12

March 2013

Oracle Fusion Middleware Installation Guide for Oracle Identity Management, 11g Release 1 (11.1.1.7.0)

E12002-12

Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author: Nisha Singh

Contributors:  Don Biasotti, Niranjan Ananthapadmanabha, Heeru Janweja, Deepak Ramakrishnan, Madhu Martin, Sergio Mendiola, Svetlana Kolomeyskaya, Sid Choudhury, Javed Beg, Eswar Vandanapu, Harsh Maheshwari, Sidhartha Das, Mark Karlstrand, Daniel Shih, Don Bosco Durai, Kamal Singh, Rey Ong, Gail Flanegin, Ellen Desmond, Priscilla Lee, Vinaye Misra, Toby Close, Ashish Kolli, Ashok Maram, Peter LaQuerre, Srinivasa Vedam, Vinay Shukla, Sanjeev Topiwala, Shaun Lin, Prakash Hulikere, Debapriya Dutta, Sujatha Ramesh, Ajay Keni, Ken Vincent

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Part I Introduction and Preparation

1 Introduction

- 1.1 Oracle Identity Management 11g Release 1 (11.1.1.7.0) Components

- 1.2 Installation Roadmap

- 1.3 Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure"

- 1.3.1 Understanding the "Install Software - Do Not Configure" Option

- 1.3.2 Understanding the "Install and Configure" Option

- 1.4 Understanding Oracle WebLogic Server Administration Domain Options

- 1.4.1 Create New Domain

- 1.4.2 Extend Existing Domain

- 1.4.3 Expand Cluster

- 1.4.4 Configure Without a Domain

- 1.5 Installing Components on Separate Systems

- 1.6 Understanding the State of Oracle Identity Management Components After Installation

- 1.6.1 Default SSL Configurations

- 1.6.2 Default Passwords

- 1.6.3 Ports Assigned Using Auto Port Configuration

- 1.7 Additional 11g Release 1 (11.1.1) Deployment Information

- 1.7.1 Upgrading to Oracle Identity Management 11g Release 1 (11.1.1.7.0)

- 1.7.2 Installing Oracle Identity Management 11g Release 1 (11.1.1.7.0) for High Availability

- 1.8 Using This Guide

2 Preparing to Install

- 2.1 Reviewing System Requirements and Certification

- 2.2 Understanding Oracle Fusion Middleware Support of 64-bit JDK

- 2.3 Installing and Configuring Java Access Bridge (Windows Only)

- 2.4 Executing the oracleRoot.sh Script on UNIX Platforms

- 2.5 Optional Environment-Specific Preparation

- 2.5.1 Using Symbolic Links

- 2.5.2 Installing Oracle Identity Management on DHCP Hosts

- 2.5.3 Installing Oracle Identity Management on a Multihomed System

- 2.6 Identifying Installation Directories

- 2.6.1 Oracle Middleware Home Location

- 2.6.2 Oracle Home Directory

- 2.6.3 WebLogic Server Directory

- 2.6.4 Oracle Instance Location

- 2.6.5 Oracle Instance Name

- 2.7 Determining Port Numbers

- 2.8 Optional: Configuring the Minimum Amount for Oracle WebLogic Server's Maximum Heap Size

- 2.9 Managing the Oracle WebLogic Server Node Manager Utility for Oracle Identity Management Installations

- 2.10 Locating Installation Log Files

3 Evaluating Single Sign-On Installations

- 3.1 Important Notes for Oracle Portal 11g Installations

- 3.2 Before You Begin

- 3.2.1 Review System Requirements and Specifications

- 3.2.2 Review Certification Information

- 3.2.3 Review Interoperability and Compatibility Information

- 3.3 Single Sign-On Options

- 3.4 Single Sign-On Preparation Considerations

- 3.5 Oracle Single Sign-On Known Limitations

- 3.6 Recommendations

Part II Installing and Configuring Oracle Identity Management (11.1.1.7.0)

4 Installing and Configuring Oracle Identity Management (11.1.1.7.0)

- 4.1 Important Notes Before You Begin

- 4.2 Installing Oracle Identity Management Using "Install and Configure" Option

- 4.2.1 Obtaining the Oracle Fusion Middleware Software

- 4.2.2 Installing Oracle Database

- 4.2.3 Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)

- 4.2.4 Required Installation Privileges for Oracle WebLogic Server and Oracle Identity Management on Windows Operating Systems

- 4.2.5 Installing Oracle WebLogic Server and Creating the Middleware Home

- 4.2.6 Creating the Inventory Directory (UNIX Only)

- 4.2.7 Starting an Installation

- 4.2.8 Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software

- 4.3 Configuring Oracle Identity Management for "Install Software - Do Not Configure" Option

5 Configuring Oracle Internet Directory

- 5.1 OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

- 5.1.1 Appropriate Deployment Environment

- 5.1.2 Components Deployed

- 5.1.3 Dependencies

- 5.1.4 Procedure

- 5.2 OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

- 5.2.1 Appropriate Deployment Environment

- 5.2.2 Components Deployed

- 5.2.3 Dependencies

- 5.2.4 Procedure

- 5.3 OID and OVD with ODSM in a New WebLogic Domain

- 5.3.1 Appropriate Deployment Environment

- 5.3.2 Components Deployed

- 5.3.3 Dependencies

- 5.3.4 Procedure

- 5.4 Only OID in an Existing WebLogic Domain

- 5.4.1 Appropriate Deployment Environment

- 5.4.2 Components Deployed

- 5.4.3 Dependencies

- 5.4.4 Procedure

- 5.5 Only OID Without a WebLogic Domain

- 5.5.1 Appropriate Deployment Environment

- 5.5.2 Components Deployed

- 5.5.3 Dependencies

- 5.5.4 Procedure

- 5.6 Verifying OID Installation

- 5.7 Getting Started with OID After Installation

6 Configuring Oracle Virtual Directory

- 6.1 OVD with ODSM and Fusion Middleware Control in a New WebLogic Domain

- 6.1.1 Appropriate Deployment Environment

- 6.1.2 Components Deployed

- 6.1.3 Dependencies

- 6.1.4 Procedure

- 6.2 Only OVD in an Existing WebLogic Domain

- 6.2.1 Appropriate Deployment Environment

- 6.2.2 Components Deployed

- 6.2.3 Dependencies

- 6.2.4 Procedure

- 6.3 Only OVD Without a WebLogic Domain

- 6.3.1 Appropriate Deployment Environment

- 6.3.2 Components Deployed

- 6.3.3 Dependencies

- 6.3.4 Procedure

- 6.4 Verifying OVD

- 6.5 Getting Started with OVD After Installation

7 Configuring Oracle Directory Integration Platform

- 7.1 Prerequisites

- 7.1.1 Option 1: Oracle Directory Integration Platform with Oracle Internet Directory

- 7.1.2 Option 2: ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

- 7.1.2.1 Installing Oracle Directory Server Enterprise Edition (ODSEE)

- 7.1.2.2 Setting Up Oracle Directory Server Enterprise Edition (ODSEE)

- 7.2 Configuring Oracle Directory Integration Platform with Oracle Internet Directory

- 7.2.1 ODIP with Fusion Middleware Control in a New WebLogic Domain

- 7.2.1.1 Appropriate Deployment Environment

- 7.2.1.2 Components Deployed

- 7.2.1.3 Dependencies

- 7.2.1.4 Procedure

- 7.2.2 Only ODIP in an Existing WebLogic Domain

- 7.2.2.1 Appropriate Deployment Environment

- 7.2.2.2 Components Deployed

- 7.2.2.3 Dependencies

- 7.2.2.4 Procedure

- 7.2.3 Configuring ODIP when OID is Running in SSL Mode 2 - Server Only Authentication

- 7.3 Configuring Oracle Directory Integration Platform with Oracle Unified Directory (OUD)

- 7.4 Configuring ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

- 7.4.1 ODIP with ODSEE in an Existing WebLogic Domain

- 7.4.1.1 Components Deployed

- 7.4.1.2 Dependencies

- 7.4.1.3 Procedure

- 7.4.2 Oracle Directory Integration Platform and ODSEE in a New WebLogic Domain

- 7.4.2.1 Components Deployed

- 7.4.2.2 Dependencies

- 7.4.2.3 Procedure

- 7.4.3 Post-Configuration Steps

- 7.5 Verifying ODIP

- 7.6 Getting Started with ODIP After Installation

8 Configuring Oracle Directory Services Manager

- 8.1 Only ODSM in a New WebLogic Domain

- 8.1.1 Appropriate Deployment Environment

- 8.1.2 Components Deployed

- 8.1.3 Dependencies

- 8.1.4 Procedure

- 8.2 Only ODSM in an Existing WebLogic Domain

- 8.2.1 Appropriate Deployment Environment

- 8.2.2 Components Deployed

- 8.2.3 Dependencies

- 8.2.4 Procedure

- 8.3 Verifying ODSM

- 8.4 Getting Started with ODSM After Installation

9 Configuring Oracle Identity Federation

- 9.1 Using the Information in This Chapter

- 9.2 Understanding OIF Deployments

- 9.3 Understanding OIF Basic and Advanced Deployments

- 9.3.1 Basic Deployment

- 9.3.2 Advanced Deployments

- 9.4 Configuring Oracle HTTP Server for OIF

- 9.5 Performing Basic Oracle Identity Federation Configurations

- 9.5.1 Appropriate Deployment Environment

- 9.5.2 Components Deployed

- 9.5.3 Dependencies

- 9.5.4 Procedure

- 9.6 Performing Advanced Oracle Identity Federation Configurations

- 9.6.1 Appropriate Deployment Environment

- 9.6.2 Components Deployed

- 9.6.3 Dependencies

- 9.6.4 Procedure

- 9.7 Advanced Example: Configuring OIF with OID in a New WebLogic Domain for LDAP Authentication, User Store, and Federation Store

- 9.7.1 Appropriate Deployment Environment

- 9.7.2 Components Deployed

- 9.7.3 Dependencies

- 9.7.4 Procedure

- 9.8 Advanced Example: Configuring OIF in a New or Existing WebLogic Domain with RDBMS Data Stores

- 9.8.1 Appropriate Deployment Environment

- 9.8.2 Components Deployed

- 9.8.3 Dependencies

- 9.8.4 Procedure

- 9.9 Verifying OIF

- 9.10 Getting Started with OIF After Installation

10 Configuring Oracle Unified Directory with Oracle Identity Management 11.1.1.7.0

- 10.1 Before You Begin

- 10.1.1 Review System Requirements and Specifications

- 10.1.2 Review Certification Information

- 10.2 Configuring only Oracle Unified Directory (OUD)

- 10.3 Configuring Oracle Unified Directory (OUD) with ODSM

- 10.4 Configuring OUD/ODSM/ODIP/Fusion Middleware Control and OVD/ODSM

- 10.4.1 Part I: Configuring OVD with ODSM and Fusion Middleware Control in a New WebLogic Administration Domain

- 10.4.1.1 Dependencies

- 10.4.1.2 Procedure

- 10.4.2 Part II: Configuring OUD/ODSM/ODIP and Fusion Middleware Control in a New WebLogic Administration Domain

- 10.4.2.1 Prerequisites

- 10.4.2.2 Dependencies

- 10.4.2.3 Procedure

- 10.4.2.4 Post-Configuration Steps

Part III Appendixes

A Oracle Identity Management 11.1.1.7.0 Software Installation Screens

- A.1 Welcome

- A.2 Install Software Updates

- A.3 Select Installation Type

- A.4 Prerequisite Checks

- A.5 Select Domain

- A.6 Specify Installation Location

- A.7 Specify Security Updates

- A.8 Configure Components

- A.9 Configure Ports

- A.10 Specify Schema Database

- A.11 Specify Oracle Virtual Directory Information

- A.12 Specify OID Administrator Password

- A.13 Select Oracle Identity Federation Configuration Type

- A.14 Specify Oracle Identity Federation Details

- A.15 Installation Summary

- A.16 Installation Progress

- A.17 Configuration Progress

- A.18 Installation Complete

B Starting or Stopping the Oracle Stack

- B.1 Starting the Stack

- B.2 Stopping the Stack

- B.3 Restarting Servers

C Deinstalling and Reinstalling Oracle Identity Management

- C.1 Deinstalling Oracle Identity Management

- C.1.1 Deinstalling the Oracle Identity Management Oracle Home

- C.1.2 Deinstalling the Oracle Common Home

- C.1.3 Deinstalling Applications Registered with Oracle Single Sign-On 10g Release 10.1.4.3.0

- C.2 Reinstalling Oracle Identity Management

D Performing Silent Installations

- D.1 What is a Silent Installation?

- D.2 Before Performing a Silent Installation

- D.2.1 UNIX Systems: Creating the oraInst.loc File

- D.2.2 Windows Systems: Creating the Registry Key

- D.3 Creating Response Files

- D.3.1 OID, OVD, ODSM, ODIP, and OIF

- D.3.2 Securing Your Silent Installation

- D.4 Performing a Silent Installation

- D.5 Installer Command Line Parameters

E Troubleshooting the Installation

- E.1 General Troubleshooting Tips

- E.2 Installation Log Files

- E.3 Configuring OIM Against an Existing OIM 11g Schema

- E.4 Need More Help?

F Software Deinstallation Screens

- F.1 Welcome

- F.2 Select Deinstallation Type

- F.2.1 Option 1: Deinstall Oracle Home

- F.2.1.1 Deinstall Oracle Home

- F.2.2 Option 2: Deinstall ASInstances managed by WebLogic Domain

- F.2.2.1 Specify WebLogic Domain Detail

- F.2.2.2 Select Managed Instance

- F.2.2.3 Deinstallation Summary (Managed Instance)

- F.2.3 Option 3: Deinstall Unmanaged ASInstances

- F.2.3.1 Specify Instance Location

- F.2.3.2 Deinstallation Summary (Unmanaged ASInstance)

- F.3 Deinstallation Progress

- F.4 Deinstallation Complete

Preface

This Preface provides supporting information for the Oracle Fusion Middleware Installation Guide for Oracle Identity Management and includes the following topics:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

The Oracle Fusion Middleware Installation Guide for Oracle Identity Management is intended for administrators that are responsible for installing Oracle Identity Management components.

This document assumes you have experience installing enterprise components. Basic knowledge about the Oracle Identity Management components and Oracle Application Server is recommended.

This document does not cover the information for installing Oracle Identity and Access Management components. For information on installing Oracle Identity and Access Management components, refer to Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

This section identifies additional documents related to Oracle Identity Management. You can access Oracle documentation online from the Oracle Technology Network (OTN) Web site at the following URL:

http://www.oracle.com/technetwork/indexes/documentation/index.html

Note:

Printed documentation is available for sale from the Oracle Store Web site at the following URL:

http://oraclestore.oracle.com/

Refer to the following documents for additional information on each subject:

Oracle Fusion Middleware

- Oracle Fusion Middleware Administrator's Guide

- Oracle Fusion Middleware Security Guide

Oracle Identity Management

- Oracle Fusion Middleware Getting Started with Oracle Identity Management

- Oracle Fusion Middleware User Reference for Oracle Identity Management

Installing and Upgrading

- Oracle Fusion Middleware Installation Planning Guide

- Oracle Fusion Middleware Quick Installation Guide for Oracle Identity Management

- Oracle Fusion Middleware Upgrade Planning Guide

- Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management

- Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server

- Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server

High Availability

- Oracle Fusion Middleware High Availability Guide

- Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

Oracle Internet Directory

- Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory

- Oracle Fusion Middleware Application Developer's Guide for Oracle Identity Management

Oracle Directory Integration Platform

- Oracle Fusion Middleware Integration Guide for Oracle Identity Management

Oracle Virtual Directory

- Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

Oracle Directory Services Manager

- Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory

- Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory

Oracle Identity Federation

- Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

Oracle Single Sign-On

- Oracle Application Server Single Sign-On Administrator's Guide 10g Release 10.1.4.0.1 available at:

http://www.oracle.com/technology/documentation/oim1014.html

Oracle Delegated Administration Services

- Oracle Identity Management Guide to Delegated Administration 10g Release 10.1.4.0.1 available at:

http://www.oracle.com/technology/documentation/oim1014.html

Oracle Fusion Middleware Repository Creation Utility

- Oracle Fusion Middleware Repository Creation Utility User's Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Part I

Introduction and Preparation

Part I introduces Oracle Identity Management 11g Release 1 (11.1.1) installation and describes how to perform preparatory tasks. It contains the following chapters:

- Chapter 1, "Introduction"

- Chapter 2, "Preparing to Install"

- Chapter 3, "Evaluating Single Sign-On Installations"

1 Introduction

This chapter provides an overview of the Oracle Identity Management 11g Release 1 (11.1.1.7.0) installation. This chapter includes the following topics:

- Oracle Identity Management 11g Release 1 (11.1.1.7.0) Components

- Installation Roadmap

- Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure"

- Understanding Oracle WebLogic Server Administration Domain Options

- Installing Components on Separate Systems

- Understanding the State of Oracle Identity Management Components After Installation

- Additional 11g Release 1 (11.1.1) Deployment Information

- Using This Guide

1.1 Oracle Identity Management 11g Release 1 (11.1.1.7.0) Components

Oracle Identity Management 11g Release 1 (11.1.1.7.0) includes the following components:

- Oracle Internet Directory

- Oracle Virtual Directory

- Oracle Directory Services Manager

- Oracle Directory Integration Platform

- Oracle Identity Federation

Note:

This document does not cover the information for installing Oracle Identity and Access Management components. For information on installing Oracle Identity and Access Management components, refer to Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management.

1.2 Installation Roadmap

Table 1-1 describes the high-level tasks for installing and configuring Oracle Identity Management. The table also provides information on where to get more details about each task.

Table 1-1 Tasks in the Oracle Identity Management Installation Procedure

Task

Description

Documentation

Mandatory or Optional?

Task 1 - Prepare your environment for installation.

Ensure that your system environment meets the general installation requirements for Oracle Fusion Middleware as well as Oracle Identity Management and RCU.

For system requirements information, go to:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

For certification information, go to:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Mandatory

Task 2 - Run RCU to create the necessary schemas.

Oracle Identity Management components require schemas that must be installed in an Oracle database. You create and load these schemas in your database by using RCU.

Make sure you have a supported Oracle database up and running. See http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html for more information.

Instructions for creating the schema are provided in "Running Oracle Fusion Middleware Repository Creation Utility (RCU)" in the Oracle Fusion Middleware Repository Creation Utility User's Guide. In addition, refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) in this guide.

Mandatory

Task 3 - Install Oracle WebLogic Server 11g Release 1 (10.3.6) or Oracle WebLogic Server 11g Release 1 (10.3.5), and create a Middleware home.

Oracle Identity Management requires a Middleware home directory. The Middleware home is created during the Oracle WebLogic Server installation.

The WebLogic Server installer also creates the WebLogic home directory within the Oracle Middleware home directory.

Installation instructions are provided in Oracle WebLogic Server Installation Guide.

For more information about the Middleware home and WebLogic home directories, see Oracle Fusion Middleware Concepts Guide.

Mandatory

Task 4 - Install Oracle Identity Management

Use the installer to install Oracle Identity Management 11.1.1.7.0

See Installing Oracle Identity Management Using "Install and Configure" Option.

For more information about the installation types, see Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure".

Mandatory

Task 5 - Configure Oracle Identity Management

After installing, run the Configuration Tool to configure your Oracle Identity Management components.

Note: This step applies if you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0)

See the following topics in this guide:

- Only OID in an Existing WebLogic Domain

- Only OID Without a WebLogic Domain

- OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

- OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

- OVD with ODSM and Fusion Middleware Control in a New WebLogic Domain

- Only OVD in an Existing WebLogic Domain

- Only OVD Without a WebLogic Domain

- Performing Basic Oracle Identity Federation Configurations

- Performing Advanced Oracle Identity Federation Configurations

- ODIP with Fusion Middleware Control in a New WebLogic Domain

- Only ODIP in an Existing WebLogic Domain

- Configuring ODIP when OID is Running in SSL Mode 2 - Server Only Authentication

Optional

1.3 Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure"

The Select Installation Type screen in the Installer presents two options: Install and Configure and Install Software - Do Not Configure. This section describes both options:

- Understanding the "Install Software - Do Not Configure" Option

- Understanding the "Install and Configure" Option

1.3.1 Understanding the "Install Software - Do Not Configure" Option

Choose the Install Software - Do Not Configure option to install Oracle Identity Management components without configuring them during installation. If you choose the Install Software - Do Not Configure option, the Installer installs the component software and then closes. Oracle Identity Management components will not start running after deploying them using the Install Software - Do Not Configure option, as additional configuration is needed.

After you install components using the Install Software - Do Not Configure option, you can configure them at a later time using the Oracle Identity Management 11g Release 1 (11.1.1.7.0) Configuration Wizard. To start the Oracle Identity Management 11g Release 1 (11.1.1.7.0) Configuration Wizard, execute the ORACLE_HOME/bin/config.sh script (config.bat on Windows).

1.3.2 Understanding the "Install and Configure" Option

The Install and Configure option allows you to install Oracle Identity Management components and simultaneously configure some of their fundamental elements, such as passwords, user names, and so on. Oracle Identity Management components start running and are immediately ready for use after deploying them using the Install and Configure option.

1.4 Understanding Oracle WebLogic Server Administration Domain Options

During installation, you have several options for choosing how the Oracle Identity Management components are installed in relation to an Oracle WebLogic Server administration domain. A domain includes a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain.

This section describes each domain option for installing Oracle Identity Management components:

- Create New Domain

- Extend Existing Domain

- Expand Cluster

- Configure Without a Domain

See:

The "Understanding Oracle WebLogic Server Domains" chapter in the Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server guide for more information about Oracle WebLogic Server administration domains.

1.4.1 Create New Domain

Select the Create New Domain option to create a new Oracle WebLogic Server administration domain and install Oracle Identity Management components in it. When you install Oracle Identity Management components in a new domain, the Fusion Middleware Control management component and the Oracle WebLogic Administration Server are automatically deployed with them.

1.4.2 Extend Existing Domain

Select the Extend Existing Domain option to install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain. When you install Oracle Identity Management components using this option, they are essentially "joining" an existing domain.

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

If you want to install and configure Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, by using either the Installer or the Oracle Identity Management 11g Release 1 Configuration Wizard, the existing domain must have been created using the Oracle Identity Management 11g Release 1 Installer. You cannot extend an existing domain for Oracle Identity Management components if the domain was created by another program, such as the Oracle SOA Installer or the Oracle Fusion Middleware Configuration Wizard.

Note:

When you install components using the Extend Existing Domain option, you must provide some credentials for the existing domain, including the user name for the domain. You must enter the user name in ASCII characters only.

1.4.3 Expand Cluster

Select the Expand Cluster option to install Oracle Identity Management components in an Oracle WebLogic Server cluster for High Availability (HA). This document does not explain how to install Oracle Identity Management components in HA configurations. Refer to the following documents for more information:

- Oracle Fusion Middleware High Availability Guide

- Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

1.4.4 Configure Without a Domain

Select the Configure without a Domain option to install Oracle Identity Management components and configure them to be without domain membership.

Note:

Only the Oracle Internet Directory and Oracle Virtual Directory components are certified for installation without a domain.

For Oracle Internet Directory, the Configure without a Domain option is appropriate for environments that have both of the following conditions:

- You do not want to include Oracle Internet Directory in a WebLogic Server administration domain for management purposes.

- You do not want to manage Oracle Internet Directory and Oracle Directory Services Manager using Fusion Middleware Control.

For Oracle Virtual Directory, the Configure without a Domain option is appropriate if you want to register Oracle Virtual Directory with a remote WebLogic Administration Server for management purposes, but you do not want to install Oracle WebLogic Server locally.

1.5 Installing Components on Separate Systems

You can install Oracle Fusion Middleware instances on separate systems. You can also distribute Oracle Fusion Middleware components over multiple systems, which is especially useful for Oracle Identity Management components. You might want to distribute components to improve performance, security, scalability, and availability of Oracle Identity Management services.

The following are two (of many) examples of Oracle Identity Management deployments that benefit from distributing components over multiple systems:

- Oracle Internet Directory on one system, and Oracle Directory Services Manager and Oracle Directory Integration Platform on a separate system.

- Oracle Identity Management components use an Oracle Database to contain the Oracle Metadata Repository. The Oracle Identity Management components and the Oracle Database are installed on separate systems.

Note:

If you install Oracle Identity Management components on a separate system from the database containing the Oracle Metadata Repository, the Oracle Identity Management components will need network access to the repository.

See:

The following documents if you want to configure more than one Oracle Internet Directory against the same Oracle Metadata Repository:

- Oracle Fusion Middleware Installation Planning Guide

- Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory

1.6 Understanding the State of Oracle Identity Management Components After Installation

This topic provides information about the state of Oracle Identity Management components after installation, including:

- Default SSL Configurations

- Default Passwords

- Ports Assigned Using Auto Port Configuration

1.6.1 Default SSL Configurations

By default, Oracle Internet Directory and Oracle Virtual Directory are installed with SSL configured. You must configure SSL for the Oracle WebLogic Administration Server and Oracle WebLogic Managed Server after installation.

See:

The Oracle Fusion Middleware Administrator's Guide for more information.

1.6.2 Default Passwords

By default, the passwords for all Oracle Identity Management components are set to the password for the Oracle Identity Management Instance. For security reasons, after installation, you should change the passwords of the various components so they have different values.

See:

The following documents for information about changing passwords for Oracle Identity Management components:

- Oracle Fusion Middleware Administrator's Guide

- Component-specific guides listed in the "Related Documents" section in this guide's Preface.

1.6.3 Ports Assigned Using Auto Port Configuration

When you use the Auto Port Configuration option during installation, the Installer follows specific steps to assign ports. The following information describes the default ports and port assignment logic the Installer uses to assign ports for various Oracle Identity Management components when you use the Auto Port Configuration option during installation.

- Oracle Virtual Directory:

- Non-SSL LDAP port: 6051

- SSL LDAP port: 6052

- HTTP Admin port: 8899

- HTTP Web Gateway port: 2223

First, the Installer attempts to assign the default port. If the default port is unavailable, the Installer tries ports within a range of 50 from the default port. For example, when the Installer assigns the non-SSL port for Oracle Virtual Directory, it first attempts to assign 6501. If 6501 is unavailable, it tries ports from 6501 to 6551. The Installer uses this approach to assign all Oracle Virtual Directory ports.

- Oracle Internet Directory:

- Non-SSL port: 3060

- SSL port: 3131

First, the Installer attempts to assign default ports. If the non-SSL port is unavailable, the Installer tries ports from 3061 to 3070, then from 13060 to 13070. Similarly, the Installer first attempts to assign 3131 as the SSL port, then ports from 3132 to 3141, and then from 13131 to 13141.

- Oracle Identity Federation: 7499
First, the Installer attempts to assign the default port. If the default port is unavailable, the Installer tries ports in increments of one, that is: 7500, then 7501, then 7502, and so on. The Installer tries ports up until 9000 to find an available port.

- Oracle Directory Services Manager: 7005
First, the Installer attempts to assign the default port. If the default port is unavailable, the Installer tries ports in increments of one, that is: 7006, then 7007, then 7008, and so on. The Installer tries ports up until 9000 to find an available port.

- Oracle WebLogic Administration Server: 7001

- Oracle Process Manager and Notification Server:

- OPMN Local Port: 6800

- OPMN Remote Port: 6801

- OPMN Request Port: 6802

1.7 Additional 11g Release 1 (11.1.1) Deployment Information

This topic describes additional sources for 11g Release 1 (11.1.1) deployment information, including documentation on the following subjects:

- Upgrading to Oracle Identity Management 11g Release 1 (11.1.1.7.0)

- Installing Oracle Identity Management 11g Release 1 (11.1.1.7.0) for High Availability

1.7.1 Upgrading to Oracle Identity Management 11g Release 1 (11.1.1.7.0)

This guide does not explain how to upgrade previous versions of Oracle Identity Management components, including any previous database schemas, to 11g Release 1 (11.1.1.7.0). To upgrade an Oracle Identity Management component that is earlier than 11g, refer to Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.

If you have an existing Oracle Identity Management 11g Release 1 installation, refer to the "Applying the Latest Oracle Fusion Middleware Patch Set" topic in the Oracle Fusion Middleware Patching Guide.

1.7.2 Installing Oracle Identity Management 11g Release 1 (11.1.1.7.0) for High Availability

This guide does not explain how to install Oracle Identity Management components in High Availability (HA) configurations. To install an Oracle Identity Management component in a High Availability configuration, refer to Oracle Fusion Middleware High Availability Guide.

Specifically, see the "Configuring High Availability for Identity Management Components" topic in the Oracle Fusion Middleware High Availability Guide.

In addition, you may also refer to the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management.

1.8 Using This Guide

Each document in the Oracle Fusion Middleware Documentation Library has a specific purpose. The specific purpose of this guide is to explain how to:

1. Install single instances of Oracle Identity Management 11g Release 1 (11.1.1) components.

2. Verify the installation was successful.

3. Get started with the component after installation.

This guide covers the most common, certified Oracle Identity Management deployments. The following information is provided for each of these deployments:

- Appropriate Installation Environment: Helps you determine which installation is appropriate for your environment.

- Components Installed: Identifies the components that are installed in each scenario.

- Dependencies: Identifies the components each installation depends on.

- Procedure: Explains the steps for the installation.

Part II of this guide explains how to install Oracle Internet Directory, Oracle Virtual Directory, Oracle Directory Services Manager, Oracle Directory Integration Platform, and Oracle Identity Federation Management by using the Oracle Identity Management 11.1.1.7.0 Installer and the Oracle Identity Management Configuration Wizard.

The following is a list of recommendations on how to use the information in this guide to install Oracle Identity Management 11g Release 1 (11.1.1.7.0):

1. Review Chapter 1, "Introduction," for context.

2. Review Chapter 2, "Preparing to Install," for information about what you should consider before you deploy Oracle Identity Management.

3. Review Chapter 4, "Installing and Configuring Oracle Identity Management (11.1.1.7.0)," for general installation and configuration information which applies to all Oracle Identity Management 11g Release 1 (11.1.1.7.0) products.

4. Install, verify, and get started with your Oracle Identity Management component by referring to its specific chapter in this guide.

5. Use the appendixes in this guide as needed.

See Also:

The "Related Documents" section in this guide's Preface for a list of documents that provide additional information about Oracle Identity Management components.

2 Preparing to Install

This chapter provides information you should review before installing Oracle Identity Management 11g Release 1 (11.1.1.7.0) components.

This chapter discusses the following topics:

- Reviewing System Requirements and Certification

- Understanding Oracle Fusion Middleware Support of 64-bit JDK

- Installing and Configuring Java Access Bridge (Windows Only)

- Executing the oracleRoot.sh Script on UNIX Platforms

- Optional Environment-Specific Preparation

- Identifying Installation Directories

- Determining Port Numbers

- Optional: Configuring the Minimum Amount for Oracle WebLogic Server's Maximum Heap Size

- Managing the Oracle WebLogic Server Node Manager Utility for Oracle Identity Management Installations

- Locating Installation Log Files

2.1 Reviewing System Requirements and Certification

Before performing any installation, you should read the system requirements and certification documents to ensure that your environment meets the minimum installation requirements for the products you are installing.

- Oracle Fusion Middleware System Requirements and Specifications
This document contains information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches.

- Oracle Fusion Middleware Supported System Configurations
This document contains information related to supported installation types, platforms, operating systems, databases, JDKs, and third-party products.

- For interoperability and compatibility issues that may arise when installing, refer to Oracle Fusion Middleware Interoperability and Compatibility Guide.
This document contains important information regarding the ability of Oracle Fusion Middleware products to function with previous versions of other Oracle Fusion Middleware, Oracle, or third-party products. This information is applicable to both new Oracle Fusion Middleware users and existing users who are upgrading their existing environment.

2.2 Understanding Oracle Fusion Middleware Support of 64-bit JDK

If you are using a 64-bit JVM in your environment, ensure that all your Oracle Fusion Middleware components are using the 64-bit JVM. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.

For more information, refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document, available at the following page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK. For 32-bit JVM support, refer to the Oracle Fusion Middleware Release Notes for information on how to configure your environment for 32-bit JVM support for your platform.

2.3 Installing and Configuring Java Access Bridge (Windows Only)

If you are installing Oracle Identity Management on a Windows system, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. This is only necessary if you require Section 508 Accessibility features:

1. Download Java Access Bridge from the following Web site:

http://java.sun.com/javase/technologies/accessibility/accessbridge/

2. Install Java Access Bridge.

3. Copy access-bridge.jar and access-1_4.jar from your installation location to the jre\lib\ext directory.

4. Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.

5. Copy the accessibility.properties file to the jre\lib directory.

2.4 Executing the oracleRoot.sh Script on UNIX Platforms

During installation on UNIX platforms, the Installer prompts you to log in as the root user and run the oracleRoot.sh script. You must log in as the root user because the script creates files, edits files, and changes the permissions of certain Oracle executable files in the Oracle_IDM_Home/bin directory.

If the oracleRoot.sh script finds files of the same name, it prompts you to indicate whether or not to override the existing files. Back up the existing files (you can do this from another window), then overwrite them.

2.5 Optional Environment-Specific Preparation

This topic describes optional environment-specific tasks you may want to perform before installing Oracle Identity Management 11g Release 1 (11.1.1.7.0). This topic includes the following sections:

- Using Symbolic Links

- Installing Oracle Identity Management on DHCP Hosts

- Installing Oracle Identity Management on a Multihomed System

Note:

If the environment variable LD_ASSUME_KERNEL is set, it needs to be unset.

2.5.1 Using Symbolic Links

If you want to install Oracle Identity Management using symbolic links, you must create them before installation. For example, you could create symbolic links for the installation by executing the following commands:

prompt> mkdir /home/basedir
prompt> ln -s /home/basedir /home/linkdir

Then, when you run the Installer to install Oracle Identity Management, you can specify /home/linkdir as the Oracle Home.

After installation, you cannot create symbolic links to the Oracle Home. Also, you cannot move the Oracle Home to a different location and create a symbolic link to the original Oracle Home.

2.5.2 Installing Oracle Identity Management on DHCP Hosts

If you plan to install Oracle Identity Management components on a DHCP server, you must ensure the Installer can resolve host names. This may require editing the /etc/hosts file on UNIX systems, and installing a loopback adapter on Windows systems. The following information provides general examples, you should alter these examples to make them specific to your environment.

On UNIX systems:

Configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries. Replace the variables with the appropriate host and domain names:

127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost

Confirm the host name resolves to the loopback IP address by executing the following command:

ping hostname.domainname

On Windows systems:

Install a loopback adapter on the DHCP host and assign it a non routable IP address.

After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file immediately after the localhost line and using the following format, where IP_address represents the local IP address of the loopback adapter:

IP_address   hostname.domainname   hostname

2.5.3 Installing Oracle Identity Management on a Multihomed System

You can install Oracle Identity Management components on a multihomed system. A multihomed system is associated with multiple IP addresses, typically achieved by having multiple network cards on the system. Each IP address is associated with a host name and you can create aliases for each host name.

The Installer retrieves the fully qualified domain name from the first entry in /etc/hosts file on UNIX, or the %SYSTEMROOT%\system32\drivers\etc\hosts file on Windows. For example, if your file looks like the following, the Installer retrieves myhost1.mycompany.com for configuration:

127.0.0.1 localhost.localdomain localhost
10.222.333.444 myhost1.mycompany.com myhost1
20.222.333.444 devhost2.mycompany.com devhost2

For specific network configuration of a system component, refer to the individual component's documentation listed in "Related Documents"for more information.

2.6 Identifying Installation Directories

This topic describes directories you must identify in most Oracle Identity Management installations and configurations—it does not describe one particular Installer screen. During installation, you will have to identify other component-specific directories not described in this topic.

The common directories described in this section include the following:

- Oracle Middleware Home Location

- Oracle Home Directory

- WebLogic Server Directory

- Oracle Instance Location

- Oracle Instance Name

2.6.1 Oracle Middleware Home Location

Identify the location of your Oracle Middleware Home directory. The Installer creates an Oracle Home directory for the component you are installing under the Oracle Middleware Home that you identify in this field. The Installer also creates an Oracle Common Home directory under the Oracle Middleware Home. The Oracle Common Home contains the binary and library files required for Oracle Enterprise Manager Fusion Middleware Control and Oracle Java Required Files (JRF). There can be only one Oracle Common Home within each Oracle Middleware Home.

The Oracle Middleware Home directory is commonly referred to as MW_HOME.

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle Middleware Home directory in the domain must have identical directory paths and names.

2.6.2 Oracle Home Directory

Enter a name for the component's Oracle Home directory. The Installer uses the name you enter in this field to create the Oracle Home directory under the location you enter in the Oracle Middleware Home Location field. The Installer installs the files (such as binaries and libraries) required to host the component in the Oracle Home directory.

The Oracle Home directory is commonly referred to as ORACLE_HOME.

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle Home directory in the domain must have identical directory paths and names.

2.6.3 WebLogic Server Directory

Enter the path to your Oracle WebLogic Server Home directory. This directory contains the files required to host the Oracle WebLogic Server. It is commonly referred to as WL_HOME.

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home directory in the domain must have identical directory paths and names.

2.6.4 Oracle Instance Location

Enter the path to the location where you want to create the Oracle Instance directory. The Installer creates the Oracle Instance directory using the location you enter in this field and using the name you enter in the Oracle Instance Name field. Do not enter a path to an existing directory that contains files—if you enter a path to an existing directory, that directory must be empty.

The Installer installs the component's configuration files and runtime components in the Oracle Instance directory. Runtime components will write only to this directory. You can identify any location on your system for the Oracle Instance directory—it does not have to reside inside the Oracle Middleware Home directory.

2.6.5 Oracle Instance Name

Enter a name for the Oracle Instance directory. The Installer uses the name you enter in this field to create the Oracle Instance directory at the location you specify in the Oracle Instance Location field. This directory is commonly referred to as ORACLE_INSTANCE.

Instance names are important because Oracle Fusion Middleware uses them to uniquely identify instances. If you install multiple Oracle Fusion Middleware instances on the same computer, for example, an Oracle Identity Management instance and an Oracle WebLogic Server instance, you must give them different names.

The name you enter for the Oracle Instance directory must:

- Contain only alphanumeric and underscore (_) characters

- Begin with an alphabetic character (a-z or A-Z)

- Consist of 4-30 characters

- Not contain the hostname or IP address of the computer

Note:

You cannot change the Oracle Instance name after installation.

2.7 Determining Port Numbers

If you want to install an Oracle Identity Management 11g Release 1 (11.1.1) component against an existing Oracle Identity Management 11g Release 1 (11.1.1) component, you may need to identify the ports for the existing component. For example, if you want to install Oracle Directory Integration Platform 11g Release 1 (11.1.1) against an existing Oracle Internet Directory 11g Release 1 (11.1.1) component, you must identify its port when you install Oracle Directory Integration Platform.

You can get information about ports using the following:

- WebLogic Server Administration Console.
Log in to the Administration Console. Click on Servers under Environment to see what ports are in use for the Administration Server and Managed Servers.

- $ORACLE_INSTANCE/config/OPMN/opmn/ports.prop

Note:

If you change a component's port number after installation, the ports.prop file is not updated.

- The $ORACLE_INSTANCE/bin/opmnctl status -l command to see port numbers of components managed by OPMN.

2.8 Optional: Configuring the Minimum Amount for Oracle WebLogic Server's Maximum Heap Size

After installing Oracle Identity Management 11g Release 1 (11.1.1), if you want to configure the minimum (lowest) level of maximum heap size (-Xmx) required for Oracle WebLogic Server to host Oracle Identity Management components, perform the steps in this section.

Note:

This is an optional step, typically performed only for test, development, or demonstration environments.

The minimum (lowest) levels for maximum heap size are:

- Oracle WebLogic Administration Server: 512 MB

- Oracle WebLogic Managed Server: 256 MB

Perform the following steps to configure the heap size for Oracle WebLogic Administration Servers and Oracle WebLogic Managed Servers:

1. Open the setDomainEnv script (.sh or .bat) in the MW_HOME/user_projects/domains/DOMAIN_NAME/bin/ directory.

2. Locate the last occurrence of the EXTRA_JAVA_PROPERTIES entry.

3. In the last occurrence of the EXTRA_JAVA_PROPERTIES entry, locate the last occurrence of heap size parameters: -Xmx, -Xms, and so on.

Note:

These are the heap size parameters for the Oracle WebLogic Administration Server.

4. Set the heap size parameters (-Xms and -Xmx) for the Oracle WebLogic Administration Server as desired, for example: -Xms256m and -Xmx512m

5. To set the heap size parameters for the Oracle WebLogic Managed Server, enter the text in Example 2-1 immediately below the last occurrence of the EXTRA_JAVA_PROPERTIES entry and:

- Set the heap size parameters (-Xms and -Xmx) as desired, for example: -Xms256m -Xmx256m

- Replace wls_ods1 with the name of the Oracle WebLogic Managed Server hosting Oracle Directory Services Manager.

- Replace wls_oif1 with the name the Oracle WebLogic Managed Server hosting Oracle Identity Federation.

Example 2-1 Heap Size Parameters for Oracle WebLogic Managed Server

if [ "${SERVER_NAME}" = "wls_ods1" -o  "${SERVER_NAME}" = "wls_oif1" ] ; then
EXTRA_JAVA_PROPERTIES=" ${EXTRA_JAVA_PROPERTIES} -Xms256m -Xmx256m "
export EXTRA_JAVA_PROPERTIES
fi

6. Save and close the setDomainEnv script.

7. Restart the Oracle WebLogic Administration Server and the Oracle WebLogic Managed Server by referring to Appendix B, "Starting or Stopping the Oracle Stack."

Note:

On UNIX systems, if you execute the ps -ef command and grep for AdminServer or the name of the Oracle WebLogic Managed Server (for example, ps -ef | grep AdminServer or ps -ef | grep wls_oif1), the output contains multiple occurrences of heap size parameters (-Xmx and -Xms).

Be aware that the last occurrence of the heap size parameters in the output are effective and have precedence over the preceding occurrences.

2.9 Managing the Oracle WebLogic Server Node Manager Utility for Oracle Identity Management Installations

Oracle Directory Integration Platform (ODIP) and Oracle Identity Federation (OIF) are configured with a WebLogic domain. Oracle Internet Directory (OID) and Oracle Virtual Directory (OVD) can be configured with or without a WebLogic domain. For Oracle Identity Management products that require a WebLogic domain, you must configure Node Manager.

You must perform the following steps after installing Oracle WebLogic Server and before installing Oracle Identity Management:

1. Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process. Use the following commands to identify running process and kill the same:
For example, on UNIX:

1) ps-ef | grep -i nodemanager

This will return the Process Id of the Node Manager Process.

2) kill -9 <Process Id of the Node Manager Process>

On Windows:

Use the Windows Task Manager to identify running Node Manager processes and kill the same.

2. Determine if the nodemanager.properties file is present in the WL_HOME/common/nodemanager/ directory.

- If the nodemanager.properties file is not present, then follow the instructions below:
On UNIX:

Run startNodeManager.sh (Located at <WL_HOME>/server/bin directory) to start Node Manager.

On Windows:

Run startNodeManager.cmd (Located at <WL_HOME>\server\bin directory) to start Node Manager.

- If the nodemanager.properties file does exist, open it and verify that the ListenPort parameter is included and that it is set. If the ListenPort parameter is not included or set, edit the nodemanager.properties file so that it is similar to the following, where NODE_MANAGER_LISTEN_PORT represents the port the Node Manager listens on, such as 5556:

ListenPort=NODE_MANAGER_LISTEN_PORT

2.10 Locating Installation Log Files

The Installer writes log files to the ORACLE_INVENTORY_LOCATION/logs directory on UNIX systems and to the ORACLE_INVENTORY_LOCATION\logs directory on Windows systems.

On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file.

On Microsoft Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

- installDATE-TIME_STAMP.log

- installDATE-TIME_STAMP.out

- installActionsDATE-TIME_STAMP.log

- installProfileDATE-TIME_STAMP.log

- oraInstallDATE-TIME_STAMP.err

- oraInstallDATE-TIME_STAMP.log

- opatchDATE-TIME_STAMP.log

3 Evaluating Single Sign-On Installations

This chapter includes the following topics:

- Important Notes for Oracle Portal 11g Installations

- Before You Begin

- Single Sign-On Options

- Single Sign-On Preparation Considerations

- Oracle Single Sign-On Known Limitations

- Recommendations

Note:

Existing Oracle Single Sign-On 10g users are encouraged to upgrade to Oracle Access Manager 11g for a more advanced single sign-on solution.

3.1 Important Notes for Oracle Portal 11g Installations

New installations of Oracle Portal 11g require Oracle Single Sign-On 10g during the installation process. Such Oracle Portal 11g users should use their existing Oracle Single Sign-On 10g installation. If you must perform a new installation of Single Sign-On 10g, consider hardware issues, system corruption, and any unforeseen issues. Oracle recommends that you follow the system framework supported by 10g for a new Single Sign-On 10g installation.

After installing Oracle Portal 11g, you may upgrade Oracle Single Sign-On 10g to Oracle Access Manager 11g. For more information, see Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.

3.2 Before You Begin

Before performing any upgrade or installation, you should read the following documents to ensure that your Oracle Fusion Middleware environment meets the minimum installation requirements for the products you are installing.

- Review System Requirements and Specifications

- Review Certification Information

- Review Interoperability and Compatibility Information

3.2.1 Review System Requirements and Specifications

Oracle Fusion Middleware System Requirements and Specifications document is available at:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

This document covers information such as hardware and software requirements, database schema requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches.

3.2.2 Review Certification Information

Oracle Fusion Middleware Supported System Configurations document is available at:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

This document contains certification information related to supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products.

3.2.3 Review Interoperability and Compatibility Information

For interoperability and compatibility issues that may arise when installing, refer to Oracle Fusion Middleware Interoperability and Compatibility Guide.

This document contains important information regarding the ability of Oracle Fusion Middleware products to function with previous versions of other Oracle Fusion Middleware, Oracle, or third-party products. This information is applicable to both new Oracle Fusion Middleware users and existing users who are upgrading their existing environment.

3.3 Single Sign-On Options

Following are the options available for a single sign-on solution:

- Use an existing Oracle Single Sign-On 10g 10.1.2.3.

- Use an existing Oracle Single Sign-On 10g 10.1.4.3.

- Install a new Oracle Single Sign-On 10g 10.1.2.3 as part of Oracle Identity Management 10g 10.1.2.3. For more information, refer to the following link:
http://download.oracle.com/docs/cd/B14099_19/idmanage.htm

- Install a new Oracle Single Sign-On 10g 10.1.4.3 as part of Oracle Identity Management 10g 10.1.4.3. For more information, refer to the following link:
http://download.oracle.com/docs/cd/B28196_01/idmanage.htm

- Use Oracle Access Manager 11g. For more information on installing and configuring Oracle Access Manager 11g Release 1 (11.1.1), see "Installing Oracle Identity and Access Management (11.1.1.7.0)" and "Configuring Oracle Access Manager" in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

3.4 Single Sign-On Preparation Considerations

Consider the following when preparing for a single sign-on solution:

- What Oracle Fusion Middleware products will be installed or configured to use a single sign-on solution?

- Will the single sign-on solution be configured during installation or as a post-installation step?

- If you have an existing Oracle Single Sign-On 10g, when will this installation be upgraded to Oracle Access Manager 11g?

- Oracle Access Manager 11g is an additional installation after installing Oracle Internet Directory 11g.

3.5 Oracle Single Sign-On Known Limitations

Following are the Oracle Single Sign-On known limitations:

- New installations of Oracle Portal 11g require Oracle Single Sign-On 10g (10.1.2.3 or 10.1.4.3) during the configuration phase.

- Premier support ends for Oracle Single Sign-On 10g (10.1.2.3) and Oracle Single Sign-On 10g (10.1.4.3) soon. For complete information, refer to the Oracle Lifetime Support Policy document available at:
http://www.oracle.com/us/support/library/lifetime-support-middleware-069163.pdf

- Premier support has been extended until December 2012 for the use of Oracle Single Sign-On 10g (10.1.4.3) with existing Oracle Portal, Forms, Reports, and Discoverer 11g environments, thereby enabling you to prepare for Oracle Access Manager 11g upgrade.

- New installations of Oracle Single Sign-On 10g (10.1.2.3) are not supported against the 11g environment.

- New installations of Oracle Single Sign-On 10g (10.1.4.3) have been supported with the 11g environment through version 11.1.1.4.

3.6 Recommendations

Oracle recommends that you carefully consider the following requirements and options when choosing a single sign-on solution:

- If an Oracle Single Sign-On 10g with Delegated Administration Services environment is necessary, use an existing Oracle Single Sign-On 10g with Delegated Administration Services environment.

- If a new Oracle Single Sign-On 10g environment must be installed, install under previously supported framework. For example, a full Oracle Identity Management 10g infrastructure, with the intention of upgrading to Oracle Access Manager 11g in near future and decommission rest of 10g.

- If you are not using Oracle Portal, install and configure Oracle Fusion Middleware products with Oracle Access Manager 11g.

- If you are installing Oracle Portal 11g for upgrade purposes, use an existing Oracle Single Sign-On 10g connection during the installation, and upgrade to Oracle Access Manager 11g at a later time. For more information on upgrading to Oracle Access Manager 11g, see Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.
If you are using Delegated Administration Services, ensure that you run it on Oracle Application Server Containers for J2EE. Move from Oracle Single Sign-On 10g to Oracle Access Manager 11g on Oracle WebLogic Server.

- New Oracle Forms and Oracle Reports installations should use Oracle Forms and Oracle Reports Release 2 (11.1.2). This installation has an option to install with Oracle Single Sign-On 10g or Oracle Access Manager 11g. You may upgrade Oracle Single Sign-On 10g to Oracle Access Manager 11g before or after this installation. For more information, see Oracle Fusion Middleware Installation Guide for Oracle Forms and Reports.

- If you are installing only Oracle Discoverer, do not install the Oracle Single Sign-On solution during Oracle Discoverer installation. Configure Oracle Access Manager 11g after the installation.

Part II

Installing and Configuring Oracle Identity Management (11.1.1.7.0)

Part II provides information about installing and configuring the following Oracle Identity Management products:

- Oracle Internet Directory

- Oracle Virtual Directory

- Oracle Directory Services Manager

- Oracle Directory Integration Platform

- Oracle Identity Federation

Part II contains the following chapters:

- Chapter 4, "Installing and Configuring Oracle Identity Management (11.1.1.7.0)"

- Chapter 5, "Configuring Oracle Internet Directory"

- Chapter 6, "Configuring Oracle Virtual Directory"

- Chapter 7, "Configuring Oracle Directory Integration Platform"

- Chapter 8, "Configuring Oracle Directory Services Manager"

- Chapter 9, "Configuring Oracle Identity Federation"

4 Installing and Configuring Oracle Identity Management (11.1.1.7.0)

This chapter includes the following topics:

- Important Notes Before You Begin

- Installing Oracle Identity Management Using "Install and Configure" Option

- Configuring Oracle Identity Management for "Install Software - Do Not Configure" Option

4.1 Important Notes Before You Begin

Before you start installing and configuring Oracle Identity Management products, keep the following points in mind:

- This chapter provides information for installing and configuring Oracle Identity Management (11.1.1.7.0) for new users. If you are an existing Oracle Identity Management 11g user, refer to "Applying the Latest Oracle Fusion Middleware Patch Set" in the Oracle Fusion Middleware Patching Guide.
For complete information about patching your Oracle Fusion Middleware 11g to the latest release, refer to the Oracle Fusion Middleware Patching Guide.

- The Select Installation Type screen in the Installer presents two options: Install and Configure and Install Software - Do Not Configure. For more information about these options, see Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure".

4.2 Installing Oracle Identity Management Using "Install and Configure" Option

Follow the instructions in this section to install and configure the latest Oracle Identity Management software.

Installing and configuring the latest version of Oracle Identity Management 11g components involves the following steps:

1. Obtaining the Oracle Fusion Middleware Software

2. Installing Oracle Database

3. Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)

4. Required Installation Privileges for Oracle WebLogic Server and Oracle Identity Management on Windows Operating Systems

5. Installing Oracle WebLogic Server and Creating the Middleware Home

6. Creating the Inventory Directory (UNIX Only)

7. Starting an Installation

8. Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software

4.2.1 Obtaining the Oracle Fusion Middleware Software

For installing Oracle Identity Management, you must obtain the following software:

- Oracle WebLogic Server 11g Release 1 (10.3.6) or Oracle WebLogic Server 11g Release 1 (10.3.5)

- Oracle Database

- Oracle Repository Creation Utility

- Oracle Identity Management Suite

For more information on obtaining Oracle Fusion Middleware 11g software, see Oracle Fusion Middleware Download, Installation, and Configuration ReadMe available at:

http://download.oracle.com/docs/cd/E23104_01/download_readme.htm

Note:

Oracle Identity Management 11g Release 1 (11.1.1.7.0) installer is platform specific.

To install Oracle Identity Management 11g Release 1 (11.1.1.7.0) on a 32-bit operating system, you must use the 32-bit installer and to install Oracle Identity Management 11g Release 1 (11.1.1.7.0) on a 64-bit operating system, you must use the 64-bit installer.

4.2.2 Installing Oracle Database

You must install an Oracle Database before you can install some Oracle Identity Management components, such as:

- Oracle Internet Directory

- Oracle Identity Federation, if you want to use an RDBMS data store

For latest information about supported databases, refer to the Oracle Fusion Middleware Supported System Configurations document.

The database must be up and running to install the relevant Oracle Identity Management component. The database does not have to be on the same system where you are installing the Oracle Identity Management component.

The database must also be compatible with Oracle Fusion Middleware Repository Creation Utility (RCU), which is used to create the schemas that Oracle Identity Management components require.

Note:

For information about RCU requirements for Oracle Databases, see "RCU Requirements for Oracle Databases" topic in the Oracle Fusion Middleware System Requirements and Specifications document.

4.2.3 Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)

You must create and load the appropriate Oracle Fusion Middleware schema in your database before installing the following Oracle Identity Management components and configurations:

- Oracle Internet Directory, if you want to use an existing schema rather than create a new one using the Installer during installation.

Note:

When you install Oracle Internet Directory, you have the choice of using an existing schema or creating a new one using the Installer. If you want to use an existing schema, you must create it using the Oracle Fusion Middleware Repository Creation Utility (RCU) before you can install Oracle Internet Directory. If you choose to create a new schema during installation, the Installer creates the appropriate schema for you and you do not need to use the RCU.

- Oracle Identity Federation Advanced configurations that use RDBMS for the Federation Store, Session Store, Message Store, or Configuration Store.

You create and load Oracle Fusion Middleware schema in your database using the RCU, which is available in the Oracle Fusion Middleware 11g Release 1 (11.1.1) release media and on the Oracle Technology Network (OTN) Web site. You can access the OTN Web site at:

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

For information on RCU requirements, refer to the "Repository Creation Utility (RCU) Requirements" topic in the Oracle Fusion Middleware System Requirements and Specifications document.

Note:

Use the Linux RCU to create schemas on supported UNIX databases. Use Windows RCU to create schemas on supported Windows databases.

When you run RCU, create and load only the following schema for the Oracle Identity Management component you are installing—do not select any other schema available in RCU:

- For Oracle Internet Directory, select only the Identity Management - Oracle Internet Directory schema

- For Oracle Identity Federation, select only the Identity Management - Oracle Identity Federation schema

Note:

When you create schema, be sure to remember the schema owner and password that is shown in RCU. For Oracle Identity Federation, it is of the form PREFIX_OIF. You will need to provide this information when configuring Oracle Identity Federation with RDBMS stores.

See:

The Oracle Fusion Middleware Repository Creation Utility User's Guide for complete information.

4.2.4 Required Installation Privileges for Oracle WebLogic Server and Oracle Identity Management on Windows Operating Systems

In order to install Oracle WebLogic Server and Oracle Identity Management on a Microsoft Windows Vista or newer operating system, the operating system user must have Windows "Administrator" privileges.

Even when a user with "Administrator" privileges logs in to the machine, the administrative role is not granted for default tasks. In order to access the Oracle home files and folders, the user must launch the command prompt or Windows Explorer as "Administrator" explicitly, even if the user is logged in as the administrator.

To do so, you can do either one of the following:

- Find the Command Prompt icon (for example, from the Start menu or from the Desktop), right-click on the icon, and select Run as Administrator. Then you can run the executables (for example, the WebLogic Server installer) from the command line.

- Start Windows Explorer, find the executable you want to run (for example, rcu.bat for RCU, config.bat for the Configuration Wizard, or setup.exe for the installer), right-click on the executable, and select Run as Administrator.

4.2.5 Installing Oracle WebLogic Server and Creating the Middleware Home

Oracle Identity Management requires Oracle WebLogic Server and a Middleware home directory. Before you install Oracle Identity Management 11g Release 1 (11.1.1.7.0) components, you must ensure that you have installed Oracle WebLogic Server 11g Release 1 (10.3.6) or Oracle WebLogic Server 11g Release 1 (10.3.5), and created a Middleware Home directory.

For more information, see "Installing Oracle WebLogic Server" in Oracle Fusion Middleware Installation Planning Guide. In addition, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for complete information about installing Oracle WebLogic Server.

For information on installing the Oracle WebLogic Server, see "Preparing for Installation" and "Running the Installation Program in Graphical Mode" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

Notes:

- If you are installing Oracle Internet Directory without an Oracle WebLogic administration domain, you do not need to install Oracle WebLogic.

- The same user who installed Oracle WebLogic Server must install Oracle Identity Management.

- Do not log in to the Oracle WebLogic Server Administration Console during Oracle Identity Management installation.

- If you want to configure the minimum amount for Oracle WebLogic Server's maximum heap size, see Section 2.8, "Optional: Configuring the Minimum Amount for Oracle WebLogic Server's Maximum Heap Size".

4.2.6 Creating the Inventory Directory (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 4-1 to configure the inventory directory information:

Table 4-1 Inventory Directory and Group Screens

Screen

Description

Specify Inventory Directory

Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory.

Click OK to continue.

Inventory Location Confirmation

Run the createCentralInventory.sh script as root.

Click OK to continue.

Note:

If you do not want to use the central inventory, you can create the oraInst.loc file, add the custom location of the inventory, and run the runInstaller by using the following command:

runInstaller -invPtrLoc <full location to oraInst.loc>

4.2.7 Starting an Installation

Perform the following steps to start an Oracle Identity Management installation:

Note:

You must be logged in to the UNIX operating system as a non-root user to start the Installer.

If you are using Sun JDK, start the Installer by executing one of the following commands:

UNIX: <full path to the runInstaller directory>/runInstaller

Windows: <full path to the setup.exe directory>\setup.exe

If you are using Oracle JRockit JDK, start the Installer by executing one of the following commands:

UNIX: <full path to the runInstaller directory>/runInstaller -jreLoc <Middleware Home>/jrockit_1.6.0_24/jre

Windows: <full path to the setup.exe directory>\setup.exe -jreLoc <Middleware Home>\jrockit_1.6.0_24\jre

Notes:

- If you are using Oracle JRockit JDK, the installer prompts you to enter the absolute path of the JDK that is installed on your system. When you install Oracle WebLogic Server, the jrockit_1.6.0_24 directory is created under your Middleware Home. You must enter the absolute path of the JRE folder located in this JDK when launching the installer. For example, on Windows, if the JDK is located in D:\oracle\Middleware\jrockit_1.6.0_24, then launch the installer from the command prompt as follows:
D:\setup.exe -jreLoc D:\oracle\Middleware\jrockit_1.6.0_24\jre

- If you do not specify the -jreLoc option on the command line when using the Oracle JRockit JDK, the following warning message is displayed:
-XX:MaxPermSize=512m is not a valid VM option. Ignoring

This warning message does not affect the installation. You can continue with the installation.

- On 64 bit platforms, when you install Oracle WebLogic Server using the generic jar file, the jrockit_1.6.0_24 directory will not be created under your Middleware Home. You must enter the absolute path of the JRE folder from where your JDK is located.

- On 64 bit platforms, the MaxPermSize should be set to 512M. Before launching the Installer, you can set the MaxPermSize in the environment as follows:
export _JAVA_OPTIONS=-XX:MaxPermSize=512m

If the MaxPermSize is not set to 512M, you will see the following error message:

java.lang.OutOfMemoryError: PermGen space

4.2.8 Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software

Follow the instructions in Table 4-2 to install and configure Oracle Identity Management 11.1.1.7.0.

If you need additional help with any of the installation screens, click Help to access the online help.

Table 4-2 Installation and Configuration Flow for Install and Configure Option

No.

Screen

When Does This Screen Appear?

Description and Action Required

1

Welcome

Always

Click Next to continue.

2

Install Software Updates

Always

Specify any software updates to install before you install Oracle Identity Management.

To get updates from My Oracle Support, you can select Search My Oracle Support for Updates, specify a user name and password, and then click Search for Updates. Before you search, you can click Proxy Settings to change the settings for the proxy server and Test Connection to test the credentials.

To get updates that you have saved to your computer, you can select Search Local Directory for Updates, specify a directory, and then click Search for Updates.

If you do not want to update any software, select Skip Software Updates, and then click Next to continue the installation.

3

Select Installation Type

Always

Select Install and Configure option.

Notes:

- If you choose Install Software - Do Not Configure option, you can configure them at a later time using the Oracle Identity Management 11g Release 1 (11.1.1.7.0) Configuration Wizard. To start the Oracle Identity Management 11g Release 1 (11.1.1.7.0) Configuration Wizard, execute the ORACLE_HOME/bin/config.sh script (config.bat on Windows). For more information, see Configuring Oracle Identity Management for "Install Software - Do Not Configure" Option.

- If you want to configure Oracle Directory Integration Platform with Oracle Unified Directory (OUD), or Oracle Directory Integration Platform with Oracle Directory Server Enterprise Edition (ODSEE), you must select Install Software - Do Not Configure option while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0). After Oracle Identity Management 11g Release 1 (11.1.1.7.0) installation is complete, depending on the component you choose to configure with Oracle Directory Integration Platform, refer to the following sections:

- Configuring Oracle Directory Integration Platform with Oracle Unified Directory (OUD)

- Configuring ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

Click Next to continue.

4

Prerequisite Checks

Always

Ensure that all the prerequisites are met.

Click Next to continue.

5

Select Domain

This screen is displayed if you select Install and Configure option.

Select one of the following options:

- Create New Domain: Enter the User Name, User Password, and Domain Name for the domain you want to create.
Depending on the component you choose, refer to the following sections:

- OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

- OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

- OID and OVD with ODSM in a New WebLogic Domain

- OVD with ODSM and Fusion Middleware Control in a New WebLogic Domain

- Only ODSM in a New WebLogic Domain

- ODIP with Fusion Middleware Control in a New WebLogic Domain

- Advanced Example: Configuring OIF with OID in a New WebLogic Domain for LDAP Authentication, User Store, and Federation Store

- Extend Existing Domain: Enter the Host Name, Port, User Name, and User Password for the existing domain you want to extend into.
Depending on the component you choose, refer to the following sections:

- Only OID in an Existing WebLogic Domain

- Only OVD in an Existing WebLogic Domain

- Only ODSM in an Existing WebLogic Domain

- Only ODIP in an Existing WebLogic Domain

- Expand Cluster: Enter the information for the existing cluster you want to expand your Oracle Identity Management installation into. Enter the Host Name, Port, User Name, and User Password for cluster inclusion.

- Configure Without Domain: You will not be creating or extending the domain of your installation.
Depending on the component you choose, refer to the following sections:

- Only OID Without a WebLogic Domain

- Only OVD Without a WebLogic Domain

6

Specify Installation Location

Always

Specify the Oracle Middleware Home location, Oracle Home Directory, WebLogic Server Directory, Oracle Instance Location, and Oracle Instance Name.

For more information about these directories, see "Understanding Oracle Fusion Middleware Concepts and Directory Structure" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

7

Specify Security Updates

Always

This screen allows you to decide how you want to be notified about security issues:

- If you want to be notified about security issues through E-mail, enter your E-mail address in the E-mail field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty. You will see the following message:
You have not provided an E-mail address. Do you wish to remain uninformed of critical security issues in your configuration?

Click Yes to continue.

Click Next to continue.

8

Configure Components

This screen is displayed if you select Install and Configure option.

- Select the Oracle Identity Management components that you wish to install and configure.

- For Create Domain installations, the Enterprise Manager checkbox under Management Components is automatically selected. Oracle Enterprise Manager Fusion Middleware Control Console (Fusion Middleware Control Console) will be installed and configured; you cannot deselect it. It is implicitly selected for configuration.

- If you select No Domain Flow, only Oracle Internet Directory and Oracle Virtual Directory will be available for configuration.

- In installations in which you select to extend the Domain, Enterprise Manager (Fusion Middleware Control Console) is not available as a selectable component. In the extend the domain installation only Oracle Directory Services Manager is available as a selection under the Management Components area.

- Oracle Directory Services Manager can be installed and configured as a stand-alone component.

- If you select to install Oracle Internet Directory or Oracle Virtual Directory in the create domain installation flow, Oracle Directory Services Manager is automatically selected and cannot be deselected. For extend domain or expand cluster, the Oracle Directory Services Manager can be deselected by you if you select to install Oracle Internet Directory or Oracle Virtual Directory.

- The Clustered selection field appears and is available if at least one Java component is selected for installation and configuration. Only managed servers and the applications that are deployed to them can be clustered. Enterprise Manager (Fusion Middleware Control Console) is not clustered during the installation because it is deployed to the administrative server.

- If you select to expand a cluster installation, at least one cluster should be present when you select this option.

- If you select to expand a cluster the Java EE components which are configured as part of the cluster will be listed.

Click Next to continue.

9

Configure Ports

This screen is displayed if you select Install and Configure option.

Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next to continue.

10

Specify Schema Database

This screen is displayed if you select Install and Configure option and choose to configure Oracle Internet Directory.

Choose whether to use an existing schema or to create a new one using the Installer.

Note: If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility.

To use an existing schema:

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next to continue.
Note: If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

To create a new schema:

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.
Note: If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next to continue.

11

Specify Oracle Virtual Directory Information

This screen is displayed if you select Install and Configure option and choose to configure Oracle Virtual Directory.

Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next to continue.

12

Specify OID Administrator Password

This screen is displayed if you select Install and Configure option and choose to configure Oracle Internet Directory.

Enter the password for the Oracle Internet Directory administrator.

Click Next to continue.

13

Select Oracle Identity Federation Configuration Type

This screen is displayed if you select Install and Configure option and choose to configure Oracle Identity Federation.

Select one of the following configuration types:

- Basic: You do not need to choose the datastore and authentication engine types or specify the connection details for Oracle Identity Federation.
For more information, see Performing Basic Oracle Identity Federation Configurations

- Advanced: This option will enable you to choose the configuration types for the datastores, the authentication engine, and specify the connection details datastores and authentication engine.
For more information, see Performing Advanced Oracle Identity Federation Configurations

Note: The procedure in this table shows the screens that appears when the Basic option is selected. If you want to select Advanced option, refer to the following for complete details:

- Performing Advanced Oracle Identity Federation Configurations

- Advanced Example: Configuring OIF with OID in a New WebLogic Domain for LDAP Authentication, User Store, and Federation Store

- Advanced Example: Configuring OIF in a New or Existing WebLogic Domain with RDBMS Data Stores

Click Next to continue.

14

Specify Oracle Identity Federation Details

This screen is displayed if you select Install and Configure option and choose to configure Oracle Identity Federation.

Enter the following information:

- PKCS12 Password: Enter the password Oracle Identity Federation will use for encryption and for signing wallets. The Installer automatically generates these wallets with self-signed certificates. Oracle recommends using the wallets only for testing.

- Confirm Password: Enter the PKCS12 password again.

- Server ID: Enter a string that will be used to identify this Oracle Identity Federation instance. A prefix oif will be added to the beginning of the string you enter. Each logical Oracle Identity Federation instance within an Oracle WebLogic Server administration domain must have a unique Server ID. Clustered Oracle Identity Federation instances acting as a single logical instance will have the same Server ID.

Click Next to continue.

15

Installation Summary

Always

Verify the information on this screen. If you want to change any options, you can return to a previous screen by clicking a link in the navigation tree on the left or by clicking Back until you get to the screen. After you edit the required options, you can continue the installation from the previous screen.

Click Save if you want to save a response file. You will be prompted for a name and location for the response file, which will contain information specific to your installation. After the installer creates the response file, you can use it exactly as is to replicate the installation on other systems, or you can modify the response file in a text editor.

Click Install to begin the installation.

16

Installation Progress

Always

If you are installing on a UNIX system, you may be asked to run the ORACLE_HOME/oracleRoot.sh script to set up the proper file and directory permissions. For more information, see Section 2.4, "Executing the oracleRoot.sh Script on UNIX Platforms".

Click Next to continue.

17

Configuration Progress

This screen is displayed if you select Install and Configure option.

Click Next to continue.

18

Installation Complete

Always

Click Save to save the installation configuration, and then click Finish to exit the installer.

Oracle Identity Management 11g Release 1 (11.1.1.7.0) is installed and configured if you selected Install and Configure option in the Select Installation Type screen. By default Oracle_IDM1 is created as the Oracle Identity Management Oracle home directory. This home directory is also referred to as IDM_Home in this guide.

To locate the installation log files, see Section 2.10, "Locating Installation Log Files".

4.3 Configuring Oracle Identity Management for "Install Software - Do Not Configure" Option

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard to configure the following components:

- Oracle Internet Directory (OID)

- Oracle Virtual Directory (OVD)

- Oracle Directory Services Manager (ODSM)

- Oracle Directory Integration Platform (ODIP)

- Oracle Identity Federation (OIF)

Run the Oracle Identity Management 11g Configuration Wizard as follows:

On UNIX systems:

ORACLE_IDM1/bin/config.sh

On Windows systems:

ORACLE_IDM1\bin\config.bat

The Oracle Identity Management 11g Configuration Wizard is displayed. You can use this wizard to configure your component in a new domain, in an existing domain, or without a domain. Note that you can install and configure only Oracle Internet Directory and Oracle Virtual Directory without a domain. For more information, see the following topics:

- Only OID in an Existing WebLogic Domain

- Only OID Without a WebLogic Domain

- OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

- OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

- OVD with ODSM and Fusion Middleware Control in a New WebLogic Domain

- Only OVD in an Existing WebLogic Domain

- Only OVD Without a WebLogic Domain

- Performing Basic Oracle Identity Federation Configurations

- Performing Advanced Oracle Identity Federation Configurations

- ODIP with Fusion Middleware Control in a New WebLogic Domain

- Only ODIP in an Existing WebLogic Domain

- Configuring ODIP when OID is Running in SSL Mode 2 - Server Only Authentication

5 Configuring Oracle Internet Directory

This chapter explains how to configure Oracle Internet Directory.

This chapter discusses the following topics:

- OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

- OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

- OID and OVD with ODSM in a New WebLogic Domain

- Only OID in an Existing WebLogic Domain

- Only OID Without a WebLogic Domain

- Verifying OID Installation

- Getting Started with OID After Installation

Table 5-1 Oracle Internet Directory Configuration Scenarios

Scenario

Description

OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

The configuration described in this topic is appropriate for environments that have all of the following conditions:

- You want to manage Oracle Internet Directory using Fusion Middleware Control.

- You want Oracle Internet Directory to be in a WebLogic administration domain.

- There is no WebLogic Administration Server managing other 11g Release 1 (11.1.1) Oracle Directory Services components.

- You want to install Oracle Internet Directory and a WebLogic Administration Server colocated on the same host.

OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- You want to install Oracle Internet Directory and Oracle Directory Integration Platform colocated on the same host.

- There is no WebLogic Administration Server managing other 11g Release 1 (11.1.1) Oracle Directory Services components.

OID and OVD with ODSM in a New WebLogic Domain

The configuration described in this topic is appropriate for environments that have the following conditions:

- A new WebLogic Administration Server is necessary to manage Oracle Internet Directory and Oracle Virtual Directory components.

- You want to install Oracle Internet Directory and Oracle Virtual Directory together in the same WebLogic domain, which can be extended at a later time to add new Oracle Identity Management components.

Only OID in an Existing WebLogic Domain

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- A WebLogic Administration Server is available to manage 11g Release 1 (11.1.1) Oracle Directory Services components and you want Oracle Internet Directory to join that domain.

- You want to install Oracle Internet Directory separately from the WebLogic Administration Server.

Only OID Without a WebLogic Domain

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- You do not want to include Oracle Internet Directory in a WebLogic administration domain for management purposes.

- You do not want to manage Oracle Internet Directory using Fusion Middleware Control.

5.1 OID with ODSM and Fusion Middleware Control in a New WebLogic Domain

This topic describes how to configure Oracle Internet Directory (OID) with Oracle Directory Services Manager (ODSM) and Fusion Middleware Control in a new WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

5.1.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have all of the following conditions:

- You want to manage Oracle Internet Directory using Fusion Middleware Control.

- You want Oracle Internet Directory to be in a WebLogic administration domain.

- There is no WebLogic Administration Server managing other 11g Release 1 (11.1.1) Oracle Directory Services components.

- You want to install Oracle Internet Directory and a WebLogic Administration Server colocated on the same host.

5.1.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Administration Server

- Oracle Internet Directory

- Oracle Directory Services Manager

- Fusion Middleware Control

5.1.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Database

- If you want to use an existing schema, Identity Management - Oracle Internet Directory schema existing in the Oracle Database.

5.1.4 Procedure

Perform the following steps to configure Oracle Internet Directory with Oracle Directory Services Manager and Fusion Middleware Control in a new domain:

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

1. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

2. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

3. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

4. Select Oracle Internet Directory. The Oracle Directory Services Manager and Fusion Middleware Control management components are automatically selected for this installation.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

5. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Schema Database screen appears.

6. Choose whether to use an existing schema or to create a new one using the Installer.

Note:

If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility or follow the To create a new schema section mentioned below.

Refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) for more information.

To use an existing schema

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

The Create Oracle Internet Directory screen appears.

5. Continue the installation by going to step 7 now.

To create a new schema

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.

Note:

If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next. The Create Oracle Internet Directory screen appears.

7. Enter the following information for Oracle Internet Directory:

- Realm: Enter the location for your realm. For example, dc=mycompany,dc=com

- Administrator Password: Enter the password for the Oracle Internet Directory administrator.

- Confirm Password: Enter the administrator password again.

Click Next.

8. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

9. The Configuration Progress screen appears. Click Next to continue.

10. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

Note:

You may see the following error message in $Instance_home/diagnostics/logs/OID/oid1/** log files after configuring Oracle Internet Directory:

"2010-02-01T07:27:42+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:stadp47] [pid: 26444] [tid: 0] Main:: FATAL * gslsmaiaInitAudCtx * Audit struct initialization failed. Audit error code: 62005"

You can ignore this error message.

5.2 OID with ODIP, ODSM, and Fusion Middleware Control in a New WebLogic Domain

This topic describes how to configure Oracle Internet Directory (OID) with Oracle Directory Integration Platform (ODIP), Oracle Directory Services Manager (ODSM), and Fusion Middleware Control in a new WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

5.2.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- You want to install Oracle Internet Directory and Oracle Directory Integration Platform colocated on the same host.

- There is no WebLogic Administration Server managing other 11g Release 1 (11.1.1) Oracle Directory Services components.

5.2.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Administration Server

- Oracle Internet Directory

- WebLogic Managed Server

- Oracle Directory Integration Platform

- Oracle Directory Services Manager

- Fusion Middleware Control

5.2.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Database

- If you want to use an existing schema, Identity Management - Oracle Internet Directory schema existing in the Oracle Database.

5.2.4 Procedure

Perform the following steps to configure Oracle Internet Directory with Oracle Directory Integration Platform, Oracle Directory Services Manager, and Fusion Middleware Control in a new domain:

1. Ensure that Oracle Internet Directory, Oracle Directory Integration Platform, and Oracle Directory Services Manager are installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select Oracle Internet Directory and Oracle Directory Integration Platform. The Oracle Directory Services Manager and Fusion Middleware Control management components are automatically selected for this installation.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Schema Database screen appears.

7. Choose whether to use an existing schema or to create a new one using the Installer.

Note:

If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility or follow the To create a new schema section mentioned below.

Refer to "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)" for more information.

To use an existing schema

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

The Create Oracle Internet Directory screen appears.

5. Continue the installation by going to step 8 now.

To create a new schema

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.

Note:

If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next. The Create Oracle Internet Directory screen appears.

8. Enter the following information for Oracle Internet Directory:

- Realm: Enter the location for your realm. For example: dc=mycompany,dc=com

- Administrator Password: Enter the password for the Oracle Internet Directory administrator.

- Confirm Password: Enter the administrator password again.

Click Next.

9. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

10. The Configuration Progress screen appears. Click Next to continue.

11. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

Note:

You may see the following error message in $Instance_home/diagnostics/logs/OID/oid1/** log files after configuring Oracle Internet Directory:

"2010-02-01T07:27:42+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:stadp47] [pid: 26444] [tid: 0] Main:: FATAL * gslsmaiaInitAudCtx * Audit struct initialization failed. Audit error code: 62005"

You can ignore this error message.

5.3 OID and OVD with ODSM in a New WebLogic Domain

This topic describes how to configure Oracle Internet Directory and Oracle Virtual Directory (OVD) with Oracle Directory Services Manager in a new WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

5.3.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have the following conditions:

- A new WebLogic Administration Server is necessary to manage Oracle Internet Directory and Oracle Virtual Directory components.

- You want to install Oracle Internet Directory and Oracle Virtual Directory together in the same WebLogic domain, which can be extended at a later time to add new Oracle Identity Management components.

5.3.2 Components Deployed

Performing the configuration in this section deploys the following:

- WebLogic Administration Server

- Oracle Internet Directory

- Oracle Virtual Directory

- WebLogic Managed Server

- Oracle Directory Services Manager

- Fusion Middleware Control

5.3.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Database

- If you want to use an existing schema, Identity Management - Oracle Internet Directory schema existing in the Oracle Database.

5.3.4 Procedure

Perform the following steps to configure Oracle Internet Directory and Oracle Virtual Directory in a new domain:

1. Ensure that Oracle Internet Directory and Oracle Virtual Directory are installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".
After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select Oracle Internet Directory and Oracle Virtual Directory. The Oracle Directory Services Manager and Oracle Fusion Middleware Control will be automatically selected.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Oracle Virtual Directory Information screen appears.

7. Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next. The Specify Schema Database screen is displayed.

8. Choose whether to use an existing schema or to create a new one using the Installer.

Note:

If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility or follow the To create a new schema section mentioned below.

Refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) for more information.

To use an existing schema

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

The Create Oracle Internet Directory screen appears.

5. Continue the installation by going to step 8 now.

To create a new schema

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.

Note:

If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next. The Create Oracle Internet Directory screen appears.

9. Enter the following information for Oracle Internet Directory:

- Realm: Enter the location for your realm. For example: dc=mycompany,dc=com

- Administrator Password: Enter the password for the Oracle Internet Directory administrator.

- Confirm Password: Enter the administrator password again.

Click Next.

10. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

11. The Configuration Progress screen appears. Click Next to continue.

12. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

5.4 Only OID in an Existing WebLogic Domain

This topic describes how to configure only Oracle Internet Directory (OID) in an existing WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

5.4.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- A WebLogic Administration Server is available to manage 11g Release 1 (11.1.1) Oracle Directory Services components and you want Oracle Internet Directory to join that domain.

- You want to install Oracle Internet Directory separately from the WebLogic Administration Server.

5.4.2 Components Deployed

Performing the configuration in this section deploys only Oracle Internet Directory.

5.4.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Database

- If you want to use an existing schema, Identity Management - Oracle Internet Directory schema existing in the Oracle Database.

5.4.4 Procedure

Perform the following steps to configure only Oracle Internet Directory in an existing domain:

1. Ensure that Oracle Internet Directory is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Extend Existing Domain and enter the following information:

- Enter the name of the host that contains the domain in the Host Name field.

- Enter the Oracle WebLogic Server listen port in the Port field.

- Enter the user name for the domain in the User Name field.

- Enter the password for the domain user in the User Password field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Internet Directory. Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Schema Database screen appears.

7. Choose whether to use an existing schema or to create a new one using the Installer.

Note:

If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility or follow the To create a new schema section mentioned below.

Refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) for more information.

To use an existing schema

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

The Create Oracle Internet Directory screen appears.

5. Continue the installation by going to step 8 now.

To create a new schema

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.

Note:

If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next. The Create Oracle Internet Directory screen appears.

8. Enter the following information for Oracle Internet Directory:

- Realm: Enter the location for your realm. For example: dc=mycompany,dc=com

- Administrator Password: Enter the password for the Oracle Internet Directory administrator.

- Confirm Password: Enter the administrator password again.

Click Next.

9. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

10. The Configuration Progress screen appears. Click Next to continue.

11. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

Note:

You may see the following error message in $Instance_home/diagnostics/logs/OID/oid1/** log files after configuring Oracle Internet Directory:

"2010-02-01T07:27:42+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:stadp47] [pid: 26444] [tid: 0] Main:: FATAL * gslsmaiaInitAudCtx * Audit struct initialization failed. Audit error code: 62005"

You can ignore this error message.

5.5 Only OID Without a WebLogic Domain

This topic describes how to configure only Oracle Internet Directory (OID) without a WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

5.5.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- You do not want to include Oracle Internet Directory in a WebLogic administration domain for management purposes.

- You do not want to manage Oracle Internet Directory and Oracle Directory Services Manager using Fusion Middleware Control.

5.5.2 Components Deployed

Performing the configuration in this section deploys only Oracle Internet Directory.

5.5.3 Dependencies

The configuration in this section depends on the following:

- Oracle Database

- If you want to use an existing schema, Identity Management - Oracle Internet Directory schema existing in the Oracle Database.

5.5.4 Procedure

Perform the following steps to configure only Oracle Internet Directory without a domain:

1. Ensure that Oracle Internet Directory is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Notes:

- Installing Oracle WebLogic Server is optional in this particular scenario. Instead, you can create the Middleware Home by following the procedure as described later in Step 3.

- If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

- If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Configure without a Domain and click Next. The Specify Installation Location screen appears.

3. Enter the following information in each field:

- Oracle Middleware Home Location: If an Oracle Middleware Home directory already exists, enter the path to it in this field. If an Oracle Middleware Home directory does not exist, enter a path to the location where you want the Installer to create the directory that will contain the Oracle Common Home and Oracle Home directories. The Installer creates an Oracle Common Home directory and an Oracle Home directory inside the directory you identify in this field.
The Oracle Middleware Home directory is commonly referred to as MW_HOME.

Note:

The Oracle Middleware Home directory is not required to contain an Oracle WebLogic Server installation.

- Oracle Home Directory: Enter a name for the Oracle Home directory. The Installer uses the name you enter in this field to create the Oracle Home directory under the location you enter in the Oracle Middleware Home Location field. The Oracle Home directory is commonly referred to as ORACLE_HOME.

- Oracle Instance Location: Enter the directory path to the location where you want to create the Oracle Instance directory. The Installer creates the Oracle Instance directory using the location you enter in this field and using the name you enter in the Oracle Instance Name field. You can identify any location on your system for the Oracle Instance directory—it does not have to reside inside the Oracle Middleware Home directory.

- Oracle Instance Name: Enter a name for the Oracle Instance directory. The Installer uses the name you enter in this field to create the Oracle Instance directory at the location you specify in the Oracle Instance Location field. This directory is commonly referred to as ORACLE_INSTANCE.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. On the Configure Components screen, select only Oracle Internet Directory. Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Schema Database screen appears.

7. Choose whether to use an existing schema or to create a new one using the Installer.

Note:

If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility or follow the To create a new schema section mentioned below.

Refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) for more information.

To use an existing schema

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

The Create Oracle Internet Directory screen appears.

5. Continue the installation by going to step 8 now.

To create a new schema

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.

Note:

If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next. The Create Oracle Internet Directory screen appears.

8. Enter the following information for Oracle Internet Directory:

- Realm: Enter the location for your realm. For example: dc=mycompany,dc=com

- Administrator Password: Enter the password for the Oracle Internet Directory administrator.

- Confirm Password: Enter the administrator password again.

Click Next.

9. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

10. The Configuration Progress screen appears. Click Next to continue.

11. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

Note:

- If you perform this installation and configuration, but later decide you want to manage Oracle Internet Directory using Fusion Middleware Control, you must register Oracle Internet Directory with a WebLogic Administration Server.
Refer to the "Registering an Oracle Instance or Component with the WebLogic Server" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for more information.

- You may see the following error message in $Instance_home/diagnostics/logs/OID/oid1/** log files after configuring Oracle Internet Directory:
"2010-02-01T07:27:42+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:stadp47] [pid: 26444] [tid: 0] Main:: FATAL * gslsmaiaInitAudCtx * Audit struct initialization failed. Audit error code: 62005"

You can ignore this error message.

5.6 Verifying OID Installation

Verify the Oracle Internet Directory (OID) installation by:

- Executing the $ORACLE_INSTANCE/bin/opmnctl status -l command. For example, if Oracle Internet Directory is configured then the following result can be seen:

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component                    | process-type       |     pid | status   |        uid |  memused |    uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
oid1                             | oidldapd           |   24032 | Alive    |  582907955 |   113004 |   0:00:41 | N/A
oid1                             | oidldapd           |   24024 | Alive    |  582907954 |    56288 |   0:00:42 | N/A
oid1                             | oidmon             |   24001 | Alive    |  582907953 |    50232 |   0:00:43 | LDAPS:3131,LDAP:3060
EMAGENT                          | EMAGENT            |   24000 | Alive    |  582907952 |     5852 |   0:00:43 | N/A

- Executing the $ORACLE_HOME/bin/ldapbind command on the Oracle Internet Directory non-SSL and SSL ports. For example:
On Non-SSL ports:

$ORACLE_HOME/bin/ldapbind -h <hostname> -p <port> -D cn=orcladmin -w <password>

On SSL ports:

$ORACLE_HOME/bin/ldapbind -h <hostname> -p <port> -D cn=orcladmin -w <password> -U 1

5.7 Getting Started with OID After Installation

After installing Oracle Internet Directory (OID), refer to the "Getting Started with Oracle Internet Directory" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

6 Configuring Oracle Virtual Directory

This chapter explains how to configure Oracle Virtual Directory (OVD).

This chapter discusses the following topics:

- OVD with ODSM and Fusion Middleware Control in a New WebLogic Domain

- Only OVD in an Existing WebLogic Domain

- Only OVD Without a WebLogic Domain

- Verifying OVD

- Getting Started with OVD After Installation

6.1 OVD with ODSM and Fusion Middleware Control in a New WebLogic Domain

This topic describes how to configure Oracle Virtual Directory (OVD) with Oracle Directory Services Manager (ODSM) and Fusion Middleware Control in a new WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

6.1.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have all of the following conditions:

- You want to manage Oracle Virtual Directory using Fusion Middleware Control.

- You want Oracle Virtual Directory to be in a WebLogic administration domain.

- There is no WebLogic Administration Server managing other 11g Release 1 (11.1.1) Oracle Directory Services components.

- You want to install Oracle Virtual Directory and a WebLogic Administration Server colocated on the same host.

6.1.2 Components Deployed

Performing the configuration in this section deploys the following components.

- WebLogic Administration Server

- Oracle Virtual Directory

- Oracle Directory Services Manager

- Fusion Middleware Control

6.1.3 Dependencies

The configuration in this section depends on Oracle WebLogic Server.

6.1.4 Procedure

Perform the following steps to configure Oracle Virtual Directory with Oracle Directory Services Manager and Fusion Middleware Control in a new domain:

1. Ensure that Oracle Virtual Directory is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Virtual Directory. The Oracle Directory Services Manager and Fusion Middleware Control management components are automatically selected for this installation.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Oracle Virtual Directory Information screen appears.

7. Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next.

8. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

9. The Configuration Progress screen appears. Click Next to continue.

10. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

6.2 Only OVD in an Existing WebLogic Domain

This topic describes how to configure only Oracle Virtual Directory (OVD) in an existing WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

6.2.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for environments that have both of the following conditions:

- A WebLogic Administration Server is available to manage 11g Release 1 (11.1.1) Oracle Directory Services components and you want Oracle Virtual Directory to join that domain.

- You want to install Oracle Virtual Directory separately from the WebLogic Administration Server.

6.2.2 Components Deployed

Performing the configuration in this section deploys only Oracle Virtual Directory.

6.2.3 Dependencies

The configuration in this section depends on Oracle WebLogic Server.

6.2.4 Procedure

Perform the following steps to configure only Oracle Virtual Directory in an existing domain:

1. Ensure that Oracle Virtual Directory is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Extend Existing Domain and enter the following information:

1. Enter the name of the host that contains the domain in the Host Name field.

2. Enter the Oracle WebLogic Server listen port in the Port field.

3. Enter the user name for the domain in the User Name field.

4. Enter the password for the domain user in the User Password field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To configure Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Virtual Directory. Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Oracle Virtual Directory Information screen appears.

7. Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next.

8. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

9. The Configuration Progress screen appears. Click Next to continue.

10. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

6.3 Only OVD Without a WebLogic Domain

This topic describes how to configure only Oracle Virtual Directory (OVD) without a WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

6.3.1 Appropriate Deployment Environment

Perform the configuration in this topic if you want to register Oracle Virtual Directory with a remote WebLogic Administration Server for management purposes, but you do not want to install Oracle WebLogic Server locally.

Note:

To manage Oracle Virtual Directory using Fusion Middleware Control in this environment, you must register Oracle Virtual Directory with the remote WebLogic Administration Server after installation.

6.3.2 Components Deployed

Performing the configuration in this section deploys only Oracle Virtual Directory.

6.3.3 Dependencies

The configuration in this section depends on Oracle WebLogic Server.

6.3.4 Procedure

Perform the following steps to configure only Oracle Virtual Directory without a domain:

1. Ensure that Oracle Virtual Directory is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Notes:

- Installing Oracle WebLogic Server is optional in this particular scenario. Instead, you can create the Middleware Home by following the procedure as described later in Step 3.

- If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

- If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. Select Configure without a Domain on the Select Domain screen and click Next. The Specify Installation Location screen appears.

3. Enter the following information in each field:

- Oracle Middleware Home Location: If an Oracle Middleware Home directory already exists, enter the path to it in this field. If an Oracle Middleware Home directory does not exist, enter a path to the location where you want the Installer to create the directory that will contain the Oracle Common Home and Oracle Home directories. The Installer creates an Oracle Common Home directory and an Oracle Home directory inside the directory you identify in this field.
The Oracle Middleware Home directory is commonly referred to as MW_HOME.

Note:

The Oracle Middleware Home directory is not required to contain an Oracle WebLogic Server installation.

- Oracle Home Directory: Enter a name for the Oracle Home directory. The Installer uses the name you enter in this field to create the Oracle Home directory under the location you enter in the Oracle Middleware Home Location field. The Oracle Home directory is commonly referred to as ORACLE_HOME.

- Oracle Instance Location: Enter the directory path to the location where you want to create the Oracle Instance directory. The Installer creates the Oracle Instance directory using the location you enter in this field and using the name you enter in the Oracle Instance Name field. You can identify any location on your system for the Oracle Instance directory—it does not have to reside inside the Oracle Middleware Home directory.

- Oracle Instance Name: Enter a name for the Oracle Instance directory. The Installer uses the name you enter in this field to create the Oracle Instance directory at the location you specify in the Oracle Instance Location field. This directory is commonly referred to as ORACLE_INSTANCE.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Virtual Directory. Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Oracle Virtual Directory Information screen appears.

7. Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next.

8. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

9. The Configuration Progress screen appears. Click Next to continue.

10. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

11. Execute the following command to register Oracle Virtual Directory with the WebLogic Administration Server. Registering with the WebLogic Administration Server allows you to manage Oracle Virtual Directory using Fusion Middleware Control.

$ORACLE_INSTANCE/bin/opmnctl registerinstance
-adminHost HOSTNAME
-adminPort WEBLOGIC_PORT
-adminUsername WEBLOGIC_ADMIN_USERNAME

Note:

You will be prompted for the WebLogic administrator's user name and password.

For example:

$ORACLE_INSTANCE/bin/opmnctl registerinstance \
-adminHost myhost \
-adminPort 7001 \
-adminUsername weblogic \

Note:

The default administrative port on the WebLogic Administration Server is 7001.

6.4 Verifying OVD

Verify the Oracle Virtual Directory (OVD) installation by:

- Starting the Oracle Virtual Directory instance, by executing the following command:
$ORACLE_INSTANCE/bin/opmnctl startall

- Verifying that Oracle Virtual Directory has started by executing the following command:
$ORACLE_INSTANCE/bin/opmnctl status -l

- Executing the $ORACLE_HOME/bin/ldapbind command on the Oracle Virtual Directory non-SSL and SSL ports.
For example:

ldapbind -p <port number>
ldapbind -p <SSL port> -U 1

Note:

For more information on OPMN commands, see Oracle Fusion Middleware Oracle Process Manager and Notification Server Administrator's Guide.

6.5 Getting Started with OVD After Installation

After installing Oracle Virtual Directory (OVD), refer to the "Getting Started with Administering Oracle Virtual Directory" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

7 Configuring Oracle Directory Integration Platform

This chapter explains how to configure Oracle Directory Integration Platform.

This chapter discusses the following topics:

- Prerequisites

- Configuring Oracle Directory Integration Platform with Oracle Internet Directory

- Configuring Oracle Directory Integration Platform with Oracle Unified Directory (OUD)

- Configuring ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

- Verifying ODIP

- Getting Started with ODIP After Installation

7.1 Prerequisites

Ensure the prerequisites are met depending on the component you wish to configure. This section discusses the following topics:

- Option 1: Oracle Directory Integration Platform with Oracle Internet Directory

- Option 2: ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

7.1.1 Option 1: Oracle Directory Integration Platform with Oracle Internet Directory

If you want to configure Oracle Directory Integration Platform with Oracle Internet Directory, ensure that Oracle Internet Directory is installed and configured as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

7.1.2 Option 2: ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

If you want to configure Oracle Directory Integration Platform with Oracle Directory Server Enterprise Edition (ODSEE) ensure that the following prerequisites are met.

- Installing Oracle Directory Server Enterprise Edition (ODSEE)

- Setting Up Oracle Directory Server Enterprise Edition (ODSEE)

7.1.2.1 Installing Oracle Directory Server Enterprise Edition (ODSEE)

Ensure that Oracle Directory Server Enterprise Edition (ODSEE) is installed, as described in the Oracle Directory Server Enterprise Edition Installation Guide 11g Release 1 (11.1.1.5.0), available at the following link:

http://download.oracle.com/docs/cd/E20295_01/html/821-1218/index.html

7.1.2.2 Setting Up Oracle Directory Server Enterprise Edition (ODSEE)

Follow the steps below for setting Up Oracle Directory Server Enterprise Edition (ODSEE):

Go to <DSEE_HOME>/bin directory and execute the following commands:

- Create a new ODSEE server instance.
./dsadm create <ODSEE instance>

For Example:

./dsadm create /scratch/<userid>/dsee/dseeinstance1/

- Start the ODSEE server instance.
./dsadm start <ODSEE instance>

For Example:

./dsadm start /scratch/<userid>/dsee/dseeinstance1/

- Create the root suffix.
./dsconf create-suffix -h <ODSEE Server> -p <ODSEE port> <SUFFIX_DN>

where the SUFFIX_DN is the full DN of the new suffix. For a root suffix, the convention is to use the domain-component (dc) naming attribute.

For Example, to create a suffix for the DN dc=example,dc=com , use this command:

./dsconf create-suffix -h localhost -p 1389 dc=example,dc=com

- Enable changelog.
./dsconf set-server-prop -h <ODSEE Server> -p <ODSEE port> retro-cl-enabled:on

For Example:

./dsconf set-server-prop -h localhost -p 1389 retro-cl-enabled:on

- Restart the ODSEE server instance.
./dsadm restart <ODSEE instance>

For Example:

./dsadm restart /scratch/<userid>/dsee/dseeinstance1/

7.2 Configuring Oracle Directory Integration Platform with Oracle Internet Directory

This section describes how to configure Oracle Directory Integration Platform with Oracle Internet Directory. It includes the following topics:

- ODIP with Fusion Middleware Control in a New WebLogic Domain

- Only ODIP in an Existing WebLogic Domain

- Configuring ODIP when OID is Running in SSL Mode 2 - Server Only Authentication

7.2.1 ODIP with Fusion Middleware Control in a New WebLogic Domain

This topic describes how to configure Oracle Directory Integration Platform (ODIP) with Fusion Middleware Control in a new WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

7.2.1.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate if there is no WebLogic Administration Server managing other 11g Release 1 (11.1.1) Oracle Directory Services components and Oracle Internet Directory is installed without a domain.

7.2.1.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Managed Server

- Oracle Directory Integration Platform

- WebLogic Administration Server

- Fusion Middleware Control

7.2.1.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Internet Directory

- Oracle Database for Oracle Internet Directory

- Identity Management - Oracle Internet Directory schema existing in the Oracle Internet Directory database.

7.2.1.4 Procedure

Perform the following steps to configure Oracle Directory Integration Platform with Fusion Middleware Control in a new domain:

1. Ensure that Oracle Directory Integration Platform is installed, as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Directory Integration Platform. The Fusion Middleware Control management component is automatically selected for this installation.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify OID Details screen appears.

7. Identify the Oracle Internet Directory for Oracle Directory Integration Platform by entering the following information:

- Hostname: Enter the hostname or IP address of the Oracle Internet Directory host.

- Port: Enter the Oracle Internet Directory LDAP SSL port.

- User Name: Enter the user name of the Oracle Internet Directory Administrator.

- Password: Enter the password for the user name Oracle Directory Integration Platform will use to connect to Oracle Internet Directory.

Click Next. The Specify Schema Database screen appears.

8. Enter the following information about the Oracle Internet Directory schema:

- Connect String: Enter the database connection information. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Password: Enter the password for the ODSSM schema in the Password field.

Click Next.

9. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

10. The Configuration Progress screen appears. Click Next to continue.

11. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

7.2.2 Only ODIP in an Existing WebLogic Domain

This topic describes how to configure only Oracle Directory Integration Platform (ODIP) in an existing WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

7.2.2.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate for the following environments:

An environment that has the following condition:

- A WebLogic Administration Server is managing an 11g Release 1 (11.1.1) Oracle Internet Directory component and you want Oracle Directory Integration Platform to join that domain.

An environment that has the following condition:

- A WebLogic Administration Server is managing other 11g Release 1 (11.1.1) Oracle Directory Services—but not Oracle Internet Directory, which is installed without a domain.

7.2.2.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Managed Server

- Oracle Directory Integration Platform

7.2.2.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Internet Directory

- Oracle Database for Oracle Internet Directory

- Identity Management - Oracle Internet Directory schema existing in the Oracle Internet Directory database.

7.2.2.4 Procedure

Perform the following steps to configure only Oracle Directory Integration Platform in an existing domain:

1. Ensure that Oracle Directory Integration Platform is installed, as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Extend Existing Domain and enter the following information:

- Enter the name of the host that contains the domain in the Host Name field.

- Enter the Oracle WebLogic Server listen port in the Port field.

- Enter the user name for the domain in the User Name field.

- Enter the password for the domain user in the User Password field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To configure Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Directory Integration Platform. Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify OID Details screen appears.

7. Identify the Oracle Internet Directory for Oracle Directory Integration Platform by entering the following information:

- Hostname: Enter the hostname or IP address of the Oracle Internet Directory host.

- Port: Enter the Oracle Internet Directory LDAP SSL port.

- User Name: Enter the user name of the Oracle Internet Directory Administrator.

- Password: Enter the password for the user name Oracle Directory Integration Platform will use to connect to Oracle Internet Directory.

Click Next. The Specify Schema Database screen appears.

8. Enter the following information about the Oracle Internet Directory schema:

- Connect String: Enter the database connection information. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Password: Enter the password for the ODSSM schema in the Password field.

Click Next.

9. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

10. The Configuration Progress screen appears. Click Next to continue.

11. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

7.2.3 Configuring ODIP when OID is Running in SSL Mode 2 - Server Only Authentication

You cannot install and configure Oracle Directory Integration Platform 11g Release 1 (11.1.1) when Oracle Internet Directory (OID) is already installed and running in SSL Mode 2 - Server Only Authentication.

If Oracle Internet Directory is already installed and running in SSL Mode 2 - Server Only Authentication, you must perform the following steps to configure Oracle Directory Integration Platform 11g Release 1 (11.1.1):

1. Configure Oracle Internet Directory to temporarily run in SSL Mode 1 - No Authentication.
Refer to the "Configuring Secure Sockets Layer (SSL)" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for complete information.

2. Install Oracle Directory Integration Platform, as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

3. Configure Oracle Internet Directory to run in SSL Mode 2 - Server Only Authentication again. Refer to the "Configuring Secure Sockets Layer (SSL)" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

4. Configure Oracle Directory Integration Platform to run in SSL Mode 2 by referring to the following sections in the Oracle Fusion Middleware Integration Guide for Oracle Identity Management:

- Configuring Oracle Directory Integration Platform for SSL Mode 2 - Server Only Authentication

- Managing the SSL Certificates of Oracle Internet Directory and Connected Directories

7.3 Configuring Oracle Directory Integration Platform with Oracle Unified Directory (OUD)

To configure Oracle Directory Integration Platform with Oracle Unified Directory (OUD), see Part II: Configuring OUD/ODSM/ODIP and Fusion Middleware Control in a New WebLogic Administration Domain.

7.4 Configuring ODIP with Oracle Directory Server Enterprise Edition (ODSEE)

This section describes how to configure Oracle Directory Integration Platform (ODIP) with Oracle Directory Server Enterprise Edition (ODSEE). It includes the following topics:

- ODIP with ODSEE in an Existing WebLogic Domain

- Oracle Directory Integration Platform and ODSEE in a New WebLogic Domain

- Post-Configuration Steps

7.4.1 ODIP with ODSEE in an Existing WebLogic Domain

This topic describes how to configure Oracle Directory Integration Platform (ODIP) with Oracle Directory Server Enterprise Edition (ODSEE) in an existing WebLogic administration domain. It includes the following sections:

- Components Deployed

- Dependencies

- Procedure

7.4.1.1 Components Deployed

Performing the configuration in this section deploys only Oracle Directory Integration Platform.

7.4.1.2 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Directory Server Enterprise Edition (ODSEE)

7.4.1.3 Procedure

Perform the following steps to configure Oracle Directory Integration Platform with Oracle Directory Server Enterprise Edition (ODSEE) in an existing WebLogic administration domain.

1. Ensure that all the prerequisites are met as described in Option 2: ODIP with Oracle Directory Server Enterprise Edition (ODSEE).

2. Ensure that Oracle Directory Integration Platform is installed using Install Software - Do Not Configure option, as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

3. Run the <MW_HOME>/oracle_common/bin/config.sh script (on UNIX) or <MW_HOME>\oracle_common\bin\config.cmd (on Windows). The Oracle Fusion Middleware Configuration Wizard appears.

4. On the Welcome screen, select the Extend an existing WebLogic domain option. Click Next.

5. On the Select a WebLogic Domain Directory screen, browse to the directory that contains the WebLogic domain in which you want to configure Oracle Directory Integration Platform (ODIP) with Oracle Directory Server Enterprise Edition (ODSEE). Click Next. The Select Extension Source screen appears.

6. On the Select Extension Source screen, select the Oracle Enterprise Manager - 11.1.1.0 [oracle_common] and Oracle Directory Integration Platform - 11.1.1.2.0 [Oracle_IDM1] domain configuration option.

Note:

When you select Oracle Directory Integration Platform - 11.1.1.2.0 [Oracle_IDM1] option, Oracle Identity Management - 11.1.1.2.0 [Oracle_IDM1] is also selected by default.

Click Next. The Specify Domain Name and Location screen appears.

7. The Specify Domain Name and Location screen automatically selects the application location. Click Next. The Select Optional Configuration screen appears.

8. On the Select Optional Configuration screen, select Managed Servers, Clusters, and Machines option. Click Next. The Configure Managed Servers screen appears.

9. On the Configure Managed Servers screen, specify the Managed Server name. Click Next.

10. On the Configure Clusters screen, configure Clusters as required. Click Next.

11. On the Configure Machines screen, select the Machine or Unix Machine tab. Click on Add and specify the machine name. Click Next.

12. If you added a machine on the Configure Machines screen, then the Assign Servers to Machines screen appears. On the Assign Servers to Machines screen, assign the Administration Server and the Managed server to the specified machine. Click Next.

13. On the Configuration Summary screen, review the domain configuration, and click Extend to start extending the domain.

14. Click Done, once the domain is extended.
Your existing domain is extended to support Oracle Directory Integration Platform.

7.4.2 Oracle Directory Integration Platform and ODSEE in a New WebLogic Domain

This topic describes how to configure Oracle Directory Integration Platform and Oracle Directory Server Enterprise Edition (ODSEE) in a new WebLogic administration domain. It includes the following sections:

- Components Deployed

- Dependencies

- Procedure

7.4.2.1 Components Deployed

Performing the configuration in this section deploys only Oracle Directory Integration Platform.

7.4.2.2 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Directory Server Enterprise Edition (ODSEE)

7.4.2.3 Procedure

Perform the following steps to configure Oracle Directory Integration Platform and Oracle Directory Server Enterprise Edition (ODSEE) in a new WebLogic administration domain.

1. Ensure that all the prerequisites are met as described in Option 2: ODIP with Oracle Directory Server Enterprise Edition (ODSEE).

2. Ensure that Oracle Directory Integration Platform is installed, as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

3. Run the <MW_HOME>/oracle_common/bin/config.sh script (on UNIX) or <MW_HOME>\oracle_common\bin\config.cmd (on Windows). The Oracle Fusion Middleware Configuration Wizard appears.

4. On the Welcome screen, select the Create a new WebLogic domain option. Click Next.

5. On the Select Domain Source screen, select Generate a domain configured automatically to support the following products: option. Select the following domain configuration options:

- Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

- Oracle Directory Integration Platform - 11.1.1.2.0 [Oracle_IDM1]

Note:

When you select Oracle Enterprise Manager - 11.1.1.0 [oracle_common] and Oracle Directory Integration Platform - 11.1.1.2.0 [Oracle_IDM1], Oracle Identity Management - 11.1.1.2.0 [Oracle_IDM1] and Oracle JRF 11.1.1.0 [oracle_common] is also selected by default.

Click Next. The Specify Domain Name and Location screen appears.

6. On the Specify Domain Name and Location screen, enter a name and location for the domain to be created. In addition, enter a location to store applications for the domain. Click Next. The Configure Administrator User Name and Password screen is displayed.

7. Configure a user name and a password for the administrator. The default user name is weblogic. Click Next. The Configure Server Start Mode and JDK screen is displayed.

8. Choose JRockit SDK 1.6.0_24 and Production Mode in the Configure Server Start Mode and JDK screen. Click Next. The Select Optional Configuration Screen is displayed.

9. On the Select Optional Configuration screen, select Managed Servers, Clusters, and Machines option. Click Next. The Configure Managed Servers screen appears.

10. On the Configure Managed Servers screen, specify the Managed Server name. Click Next.

11. On the Configure Clusters screen, configure Clusters as required. Click Next.

12. On the Configure Machines screen, select the Machine or Unix Machine tab. Click on Add and specify the machine name. Click Next.

13. If you added a machine on the Configure Machines screen, then the Assign Servers to Machines screen appears. On the Assign Servers to Machines screen, assign the Administration Server and the Managed server to the specified machine. Click Next.

14. On the Configuration Summary screen, review the domain configuration, and click Create to start creating the domain.

15. Click Done, once the domain is created successfully.
A new WebLogic domain to support Oracle Directory Integration Platform is created in the <MW_HOME>\user_projects\domains directory (on Windows). On UNIX, the domain is created in the <MW_HOME>/user_projects/domains directory.

7.4.3 Post-Configuration Steps

After configuring Oracle Directory Integration Platform, perform the following tasks:

1. Run the <MW_HOME>/oracle_common/common/bin/setNMProps.sh script (on UNIX) or <MW_HOME>\oracle_common\common\bin\setNMProps.cmd (on Windows).

2. Start the Administration Server, Node Manager and Managed Server as described in Starting the Stack.

3. Set the WL_HOME and ORACLE_HOME environment variables and execute <ORACLE_HOME>/bin/dipConfigurator. Provide the following information when prompted for input.

- WebLogic host, port, username and password details.

- Oracle Directory Server Enterprise Edition (ODSEE) host, port, username and password details.

- Specify the suffix under which DIP metadata is to be stored.

4. Verify the Oracle Directory Integration Platform installation and configuration. For more information, see Verifying ODIP.

5. The dipConfigurator will set the below ACIs for the specified metadata suffix. But for the other suffixes, set the below ACIs for the containers in OUD, in order to write the changes imported from the other sources:

dn: <Container DN>
changetype:modify
add: aci
aci: (target="ldap:///<Container DN>")(version 3.0; acl "Anonymous read-search
access"; allow (read,add,delete,search,write,compare,proxy)
groupdn="ldap:///cn=dipadmingrp,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>"; allow
(read,add,delete,search,write,compare,proxy)
groupdn="ldap:///cn=odipigroup,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>"; )
-
add: aci
aci: (targetattr="*")(version 3.0; acl "Anonymous read-search access"; allow
(search,read,write,compare,add)
groupdn="ldap:///cn=dipadmingrp,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>"; allow (search,read,write,compare,add)
groupdn="ldap:///cn=odipigroup,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>";)

Note:

ODIP configuration can be recreated any number of times if ODIP configuration is deleted or corrupted. However, if there are any sync profiles that already exists, the connected directory password of the existing profiles needs to be reset after executing dipConfigurator.

For recreating the ODIP configuration, re-run step 3 and step 4.

7.5 Verifying ODIP

Verify the Oracle Directory Integration Platform (ODIP) installation using the dipStatus command, which is located in the $ORACLE_HOME/bin/ directory.

Note:

You must set the WL_HOME and ORACLE_HOME environment variables before executing the dipStatus command.

The following is the syntax for the dipStatus command:

$ORACLE_HOME/bin/dipStatus -h HOST -p PORT -D wlsuser [-help]

- -h | -host identifies the Oracle WebLogic Server where Oracle Directory Integration Platform is deployed.

- -p | -port identifies the listening port of the Oracle WebLogic Managed Server where Oracle Directory Integration Platform is deployed.

- -D | -wlsuser identifies the Oracle WebLogic Server login ID.

Note:

You will be prompted for the Oracle WebLogic Server login password. You cannot provide the password as a command-line argument.

Best security practice is to provide a password only in response to a prompt from the command. If you must execute dipStatus from a script, you can redirect input from a file containing the Oracle WebLogic Server password. Use file permissions to protect the file and delete it when it is no longer necessary.

7.6 Getting Started with ODIP After Installation

After you install Oracle Directory Integration Platform (ODIP), no additional configuration is needed. The next step is to create synchronization profiles.

The Oracle Fusion Middleware Integration Guide for Oracle Identity Management explains how to manage Oracle Directory Integration Platform. For information about creating synchronization profiles using Oracle Enterprise Manager Fusion Middleware Control Console, refer to the "Managing Synchronization Profiles Using Fusion Middleware Control" section in that guide.

8 Configuring Oracle Directory Services Manager

This chapter explains how to configure Oracle Directory Services Manager (ODSM).

This chapter discusses the following topics:

- Only ODSM in a New WebLogic Domain

- Only ODSM in an Existing WebLogic Domain

- Verifying ODSM

- Getting Started with ODSM After Installation

8.1 Only ODSM in a New WebLogic Domain

This topic describes how to configure only Oracle Directory Services Manager (ODSM) in a new WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

8.1.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate if Oracle Internet Directory was installed without a domain and you want to manage it using Oracle Directory Services Manager.

8.1.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Managed Server

- Oracle Directory Services Manager

- WebLogic Administration Server

- Fusion Middleware Control

8.1.3 Dependencies

The configuration in this section depends on Oracle WebLogic Server.

8.1.4 Procedure

Perform the following steps to configure only Oracle Directory Services Manager in a new domain:

1. Ensure that Oracle Directory Services Manager is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Directory Services Manager. The Fusion Middleware Control management component is automatically selected for this installation.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next.

7. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

8. The Configuration Progress screen appears. Click Next to continue.

9. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

8.2 Only ODSM in an Existing WebLogic Domain

This topic describes how to configure only Oracle Directory Services Manager (ODSM) in an existing WebLogic administration domain. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

8.2.1 Appropriate Deployment Environment

The configuration described in this topic is appropriate if you want to deploy an additional Oracle Directory Services Manager component in an existing domain.

8.2.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Managed Server

- Oracle Directory Services Manager

8.2.3 Dependencies

The configuration in this section depends on Oracle WebLogic Server.

8.2.4 Procedure

Perform the following steps to configure only Oracle Directory Services Manager in an existing domain:

1. Ensure that Oracle Directory Services Manager is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

2. On the Select Domain screen, select Extend Existing Domain and enter the following information:

1. Enter the name of the host that contains the domain in the Host Name field.

2. Enter the Oracle WebLogic Server listen port in the Port field.

3. Enter the user name for the domain in the User Name field.

4. Enter the password for the domain user in the User Password field.

Click Next. The Specify Installation Location screen appears.

3. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To configure Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

4. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

5. Select only Oracle Directory Services Manager. Ensure no other components are selected and click Next. The Configure Ports screen appears.

6. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next.

7. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

8. The Configuration Progress screen appears. Click Next to continue.

9. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

8.3 Verifying ODSM

To verify the Oracle Directory Services Manager (ODSM) installation, enter the following URL into your browser's address field:

http://host:port/odsm

- host represents the name of the WebLogic Managed Server hosting Oracle Directory Services Manager.

- port represents the WebLogic Managed Server listen port. You can determine the exact port number of the Managed Server through the Oracle WebLogic Administration Console. After logging in to the console, expand Environment on the left navigation pane. Click Servers. The Summary of Servers page is displayed. The port for the Oracle Directory Services Manager (ODSM) Managed Server is displayed on this page.

Oracle Directory Services Manager is installed and running if the Welcome to Oracle Directory Services Manage screen appears.

Note:

While the appearance of the Welcome screen verifies Oracle Directory Services Manager is installed and running, you cannot connect to Oracle Internet Directory or Oracle Virtual Directory from Oracle Directory Services Manager without the appropriate credentials.

8.4 Getting Started with ODSM After Installation

After you install Oracle Directory Services Manager (ODSM), no additional configuration is needed. The next step is to log in to Oracle Internet Directory or Oracle Virtual Directory. The process for logging in to both directory servers is the same. Information about logging in to both Oracle Internet Directory and Oracle Virtual Directory provided below so you can learn more about Oracle Directory Services Manager in the context of each directory server.

- For information about logging in to Oracle Internet Directory from Oracle Directory Services Manager, refer to the "Logging in to the Directory Server from Oracle Directory Services Manager" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

- For information about logging in to Oracle Virtual Directory from Oracle Directory Services Manager, refer to the "Logging in to the Directory Server from Oracle Directory Services Manager" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

9 Configuring Oracle Identity Federation

This chapter explains how to configure Oracle Identity Federation (OIF).

This chapter discusses the following topics:

- Using the Information in This Chapter

- Understanding OIF Deployments

- Understanding OIF Basic and Advanced Deployments

- Configuring Oracle HTTP Server for OIF

- Performing Basic Oracle Identity Federation Configurations

- Performing Advanced Oracle Identity Federation Configurations

- Advanced Example: Configuring OIF with OID in a New WebLogic Domain for LDAP Authentication, User Store, and Federation Store

- Advanced Example: Configuring OIF in a New or Existing WebLogic Domain with RDBMS Data Stores

- Verifying OIF

- Getting Started with OIF After Installation

9.1 Using the Information in This Chapter

Oracle Identity Federation deployments vary greatly. As described in the following topics, there are several components, and several options for those components, that comprise an Oracle Identity Federation deployment.

Use this chapter as a starting point for your Oracle Identity Federation deployment, as it does not describe every possible installation and configuration. You should also use the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation, which provides additional and detailed deployment information, to supplement the information in this chapter.

9.2 Understanding OIF Deployments

When you configure Oracle Identity Federation 11g Release 1 (11.1.1), a WebLogic Managed Server is created and the Oracle Identity Federation J2EE application is installed on it. If you configure Oracle Identity Federation in a new Oracle WebLogic Server administration domain by selecting the Create Domain option, the Fusion Middleware Control management component is also deployed.

Oracle Identity Federation functionality depends on several components and modules. You can integrate and configure these components and modules during or after the Oracle Identity Federation installation.

The following is a list and brief description of some of the components and modules that determine Oracle Identity Federation functionality. Refer to the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation for complete information.

- Authentication Engine: The module that challenges users when they log in.

- User Data Store: The repository containing the identity information of the users the Oracle Identity Federation system authenticates.

- Federation Data Store: The repository containing federated user account linking data.

- Service Provider (SP) Integration Engine: The module that creates a local authenticated session for the user based on a received federated Single Sign-On (SSO) token.

- User Session Store and Message Store: The repository containing transient runtime session state data and protocol messages.

- Configuration Data Store: The repository containing Oracle Identity Federation configuration data.

9.3 Understanding OIF Basic and Advanced Deployments

There are two types of Oracle Identity Federation 11g Release 1 (11.1.1) deployments: Basic and Advanced. This topic describes both types of deployments and includes the following sections:

- Basic Deployment

- Advanced Deployments

9.3.1 Basic Deployment

The Basic deployment includes Oracle Identity Federation with minimum functionality enabled and the following configuration:

- No User Data Store

- No Federation Store

- JAAS Authentication Engine

- Test Service Provider (SP) Engine

- Memory Session Data Store

- Memory Message Data Store

- XML file system Configuration Store

9.3.2 Advanced Deployments

The Advanced deployments allows you to choose between different types of data stores and authentication engines. The following is a list and description of the types of data stores and authentication engines you can choose during an Advanced installation:

Authentication Engine

- JAAS: Delegates authentication to the application server.

- LDAP: Uses form login and LDAP bind with credentials supplied by user to authenticate against LDAP repository.

User Data Store

- None: No User Data Store. Typically used with Custom or JAAS Authentication Engines, environments without user attributes, or Windows CardSpace.

- LDAP: Typical configuration that stores user data in an LDAP repository.

- RDBMS: Uses database tables with user names (and optionally user attributes) in columns.

Federation Data Store

- None: No Federation Data Store. Typically used when there are no persistent account linking records. No Federation Data Store is also an alternative to using name identifiers, such as e-mail address, X.509 DN, Kerberos, or Windows Name Identifier.

- LDAP: Stores federation in an LDAP repository. Commonly deployed when the User Data Store is also LDAP.

- RDBMS: Stores federation in a relational database repository. Commonly deployed when the User Data Store is also RDBMS.

- XML: Stores federation data in an XML file system. Commonly used for testing purposes.

User Session Store and Message Store

- Memory: Stores transient runtime session state data and protocol messages in in-memory tables. Commonly used for single instance deployments. Memory provides better performance than the RDBMS User Session Store, but increases runtime memory requirements.

- RDBMS: Stores transient runtime session state data and protocol messages in a relational database. Recommended for High Availability cluster environments.

Note:

User Session Store and Message Store appear in the Installer as separate configuration items, however, most deployments use the same type of repository for both stores.

Configuration Data Store

- File System: Stores Oracle Identity Federation configuration data on the local file system. Commonly used in single-instance and testing environments.

- RDBMS: Stores Oracle Identity Federation configuration data in a relational database. Commonly used in High Availability environments or single-instances with failover redundancy.

9.4 Configuring Oracle HTTP Server for OIF

When you install Oracle Identity Federation (OIF), Oracle HTTP Server also gets installed. Oracle HTTP Server is required when using Oracle Identity Federation for enterprise level single sign-on with Oracle Single Sign-On and Oracle Access Manager. Although Oracle Identity Federation can function without Oracle HTTP Server, there are advantages to configuring it as a proxy for Oracle Identity Federation.

To configure the Oracle HTTP Server so that the Oracle Identity Federation application can be accessed through Oracle HTTP Server ports, you can:

- Ensure that Oracle Identity Federation is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

- Run <ORACLE_HOME>/bin/config.sh (On UNIX) or <ORACLE_HOME>\bin\config.bat to start the Oracle Identity Management Configuration Wizard. Click Next to continue.

- On the Configure Components screen, select Oracle HTTP Server and Oracle Identity Federation.

See:

The "Deploying Oracle Identity Federation with Oracle HTTP Server" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation for more information about integrating Oracle Identity Federation and Oracle HTTP Server.

9.5 Performing Basic Oracle Identity Federation Configurations

This topic describes how to perform a Basic Oracle Identity Federation (OIF) configuration. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

9.5.1 Appropriate Deployment Environment

The Basic Oracle Identity Federation configuration is appropriate for:

- Creating a base to gradually build complex implementations upon after installation

- Deploying test environments

- Deploying small, self-contained configurations

9.5.2 Components Deployed

Performing the Basic Oracle Identity Federation configuration deploys the following components:

If you install Oracle Identity Federation in a new domain:

- WebLogic Managed Server

- Oracle Identity Federation

- WebLogic Administration Server

- Fusion Middleware Control

- Optionally, Oracle HTTP Server

If you install Oracle Identity Federation in an existing domain:

- WebLogic Managed Server

- Oracle Identity Federation

- Optionally, Oracle HTTP Server

9.5.3 Dependencies

The Basic Oracle Identity Federation configuration depends on Oracle WebLogic Server.

9.5.4 Procedure

Perform the following steps to deploy a Basic Oracle Identity Federation configuration:

1. Ensure that Oracle Identity Federation is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

2. Run <ORACLE_HOME>/bin/config.sh (On UNIX) or <ORACLE_HOME>\bin\config.bat to start the Oracle Identity Management Configuration Wizard. Click Next to continue.

3. On the Select Domain screen, choose whether to configure Oracle Identity Federation in a new or existing domain:
To configure Oracle Identity Federation in a new domain:

1. Select Create New Domain.

2. Enter the user name for the new domain in the User Name field.

3. Enter the user password for the new domain in the User Password field.
Enter the user password again in the Confirm Password field.

4. Enter a name for the new domain in the Domain Name field.

5. Click Next. The Specify Installation Location screen appears.

Continue the installation by going to step 4 now.

To configure Oracle Identity Federation in an existing domain:

1. Select Extend Existing Domain.

2. Enter the name of the host that contains the domain in the Host Name field.

3. Enter the listen port for the WebLogic Administration Server in the Port field.

4. Enter the user name for the domain in the User Name field.

5. Enter the password for the domain user in the User Password field.

Click Next. The Specify Installation Location screen appears.

4. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To configure Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

5. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

6. Select Oracle Identity Federation—and optionally, Oracle HTTP Server. Refer to "Configuring Oracle HTTP Server for OIF" for information about configuring these two components simultaneously.
If you are installing Oracle Identity Federation in a new domain, the Fusion Middleware Control management component is automatically selected for installation.

Ensure no other components are selected and click Next. The Configure Ports screen appears.

7. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Select Oracle Identity Federation Configuration Type screen appears.

8. Select Basic and click Next. The Specify OIF Details screen appears.

9. Enter the following information:

- PKCS12 Password: Enter the password Oracle Identity Federation will use for encryption and for signing wallets. The Installer automatically generates these wallets with self-signed certificates. Oracle recommends using the wallets only for testing.

- Confirm Password: Enter the PKCS12 password again.

- Server ID: Enter a string that will be used to identify this Oracle Identity Federation instance. A prefix of oif will be added to the beginning of the string you enter. Each logical Oracle Identity Federation instance within an Oracle WebLogic Server administration domain must have a unique Server ID. Clustered Oracle Identity Federation instances acting as a single logical instance will have the same Server ID.

Click Next.

10. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

11. The Configuration Progress screen appears. Click Next to continue.

12. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

9.6 Performing Advanced Oracle Identity Federation Configurations

This topic generally describes how to perform an Advanced Oracle Identity Federation (OIF) configuration. Refer to the next two topics in this chapter for information on performing specific Advanced Oracle Identity Federation configurations.

This topic includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

9.6.1 Appropriate Deployment Environment

The Advanced Oracle Identity Federation configuration provides a fast and simplified method for deploying Oracle Identity Federation with its vital components integrated and configured.

9.6.2 Components Deployed

Performing the Advanced Oracle Identity Federation configuration deploys the following components:

If you configure Oracle Identity Federation in a new domain:

- WebLogic Managed Server

- Oracle Identity Federation

- WebLogic Administration Server

- Fusion Middleware Control

- Optionally, Oracle HTTP Server

If you configure Oracle Identity Federation in an existing domain:

- WebLogic Managed Server

- Oracle Identity Federation

- Optionally, Oracle HTTP Server

9.6.3 Dependencies

The Advanced Oracle Identity Federation configuration depends on the following components:

- Oracle WebLogic Server

- Oracle Database, if using RDBMS for User Store, Federation Store, Session Store, Message Store, or Configuration Store.

- New Identity Management - Oracle Identity Federation schema existing in the database, if using RDBMS for Federation Store, Session Store, Message Store, or Configuration Store.

- Database table for storing user dative using RDBMS for User Store

- LDAP repository, if using LDAP for Authentication, User Store, or Federation Store.

9.6.4 Procedure

Perform the following steps to deploy an Advanced Oracle Identity Federation configuration:

1. Decide if you want to use RDBMS for User Store, Federation Store, Session Store, Message Store, or Configuration Store. If you do, perform the following steps a and b.

1. Install the database for Oracle Identity Federation. Refer to Installing Oracle Database for more information.

2. Create the Identity Management - Oracle Identity Federation schema in the database. Refer to "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)" for more information.

Note:

The schema is not required for RDBMS User Stores.

2. Decide if you want to use an LDAP repository for Authentication, User Store, or Federation Store. If you do, you must install the LDAP repository before you can install Oracle Identity Federation.

3. Ensure that Oracle Identity Federation is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

4. Run <ORACLE_HOME>/bin/config.sh (On UNIX) or <ORACLE_HOME>\bin\config.bat to start the Oracle Identity Management Configuration Wizard. Click Next to continue.

5. On the Select Domain screen, choose whether to install Oracle Identity Federation in a new or existing domain:
To configure Oracle Identity Federation in a new domain:

1. Select Create New Domain.

2. Enter the user name for the new domain in the User Name field.

3. Enter the user password for the new domain in the User Password field.

4. Enter the user password again in the Confirm Password field.

5. Enter a name for the new domain in the Domain Name field.

6. Click Next. The Specify Installation Location screen appears.

Continue the installation by going to step 6 now.

To configure Oracle Identity Federation in an existing domain:

1. Select Extend Existing Domain.

2. Enter the name of the host that contains the domain in the Host Name field.

3. Enter the listen port for the WebLogic Administration Server in the Port field.

4. Enter the user name for the domain in the User Name field.

5. Enter the password for the domain user in the User Password field.

6. Click Next. The Specify Installation Location screen appears.

6. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

7. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

8. Select Oracle Identity Federation—and optionally, Oracle HTTP Server. Refer to "Configuring Oracle HTTP Server for OIF" for information about configuring these two components simultaneously.
If you are installing Oracle Identity Federation in a new domain, the Fusion Middleware Control management component is automatically selected for installation.

Ensure no other components are selected and click Next. The Configure Ports screen appears.

9. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Select Oracle Identity Federation Configuration Type screen appears.

10. Select Advanced and click Next. The Specify OIF Details screen appears.

11. Enter the following information:

- PKCS12 Password: Enter the password Oracle Identity Federation will use for encryption and for signing wallets. The Installer automatically generates these wallets with self-signed certificates. Oracle recommends using the wallets only for testing.

- Confirm Password: Enter the PKCS12 password again.

- Server ID: Enter a string that will be used to identify this Oracle Identity Federation instance. A prefix of oif will be added to the beginning of the string you enter. Each logical Oracle Identity Federation instance within an Oracle WebLogic Server administration domain must have a unique Server ID. Clustered Oracle Identity Federation instances acting as a single logical instance will have the same Server ID.

Click Next. The Select OIF Advanced Flow Attributes screen appears.

12. Select the appropriate option for each configuration item and click Next.

Note:

User Session Store and Message Store appear in the Installer as separate configuration items, however, most deployments use the same type of repository for both stores.

The screens that appear next depend on the options you selected for the configuration items on the Select OIF Advanced Flow Attributes screen. The following information describes all possible screens that may appear. This information about all possible screens that may appear is not presented in a linear sequence and your installation may not encounter all of the screens. Enter information for the appropriate screens and proceed to step 13.

If you selected LDAP for Authentication Type, the Specify Authentication LDAP Details screen will appear. Enter the following information:

- LDAP Type: Select the appropriate LDAP repository.

- LDAP URL: Enter the URL connection string for the LDAP repository in the form: protocol://hostname:port

Note:

If you selected Microsoft Active Directory for the LDAP Type, you must specify an SSL LDAP URL, that is, ldaps://hostname:port.

- LDAP Bind DN: Enter the bind DN for the LDAP repository.

- LDAP Password: Enter the password for the bind DN.

- User Credential ID Attribute: Enter the LDAP attribute Oracle Identity Federation will use to authenticate users. For example, if you enter mail and the value of the mail attribute for a user is jane.doe@domain.com, then Jane Doe must enter jane.doe.@domain.com when challenged. Values for the LDAP attribute you identify for User Credential ID Attribute must be unique for all users.

- User Unique ID Attribute: Enter the LDAP attribute that will uniquely identify users to Oracle Identity Federation. The value you enter must be identical to the value you enter for the User Data Store's User ID Attribute parameter. For example, if you enter mail for User Unique ID Attribute and you configure the User Data Store's User ID Attribute parameter with a value of EmailAddress, then the value of mail in the authentication engine repository must equal the value of EmailAddress in the User Data Store. Values for the LDAP attribute you identify for User Unique ID Attribute must be unique for all users.

- Person Object Class: Enter the LDAP object class that represents a user in the LDAP repository. For example: inetOrgPerson for Oracle Internet Directory and Sun Java System Directory Server, and user for Microsoft Active Directory.

- Base DN: Enter the root DN that searches will start from.

If you selected LDAP for User Store, the Specify LDAP Attributes for User Data Store screen will appear. Enter the following information:

- LDAP Type: Select the appropriate LDAP repository.

- LDAP URL: Enter the URL connection string for the LDAP repository in the form: protocol://hostname:port

Note:

If you selected Microsoft Active Directory for the LDAP Type, you must specify an SSL LDAP URL, that is, ldaps://hostname:port.

- LDAP Bind DN: Enter the bind DN for the LDAP repository.

- LDAP Password: Enter the password for the bind DN.

- User Description Attribute: Enter the readable LDAP attribute that will identify the owner of a federation record. For example: uid for Oracle Internet Directory and Sun Java System Directory Server, and sAMAccountName for Microsoft Active Directory.

- User ID Attribute: Enter the LDAP attribute that will uniquely identify the user during authentication. For example: uid for Oracle Internet Directory and Sun Java System Directory Server, and sAMAccountName for Microsoft Active Directory.

- Person Object Class: Enter the LDAP object class that represents a user in the LDAP repository. For example: inetOrgPerson for Oracle Internet Directory and Sun Java System Directory Server, and user for Microsoft Active Directory.

- Base DN: Enter the root DN that searches will start from.

If you selected RDBMS for User Store, the Specify User Store Database Details screen will appear. Enter the following information:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the database username.

- Password: Enter the password for the database user.

- Login Table: Enter the name of the table that will store user data. The value you enter must be a valid table name, and the values you enter for User ID Attribute and User Description Attribute must be valid column names in the table you identify.

- User ID Attribute: Enter the name of the table column to use for the Oracle Identity Federation user ID. The value you enter must be a valid column name in the table you identified for the Login Table parameter.

- User Description Attribute: Enter the name of the table column to use for the user description. The value you enter must be a valid column name in the table you identified for the Login Table parameter.

If you selected LDAP for Federation Store, the Specify LDAP Attributes for Federation Data Store screen will appear. Enter the following information:

- LDAP Type: Select the appropriate LDAP repository.

- LDAP URL: Enter the URL connection string for the LDAP repository in the form: protocol://hostname:port

Note:

If you selected Microsoft Active Directory for the LDAP Type, you must specify an SSL LDAP URL, that is, ldaps://hostname:port.

- LDAP Bind DN: Enter the bind DN for the LDAP repository.

- LDAP Password: Enter the password for the bind DN.

- User Federation Record Context: Enter the location of the container where you want Oracle Identity Federation to store federation records. If the container you identify does not exist, it will be created at runtime. However, if you identify cn=example,dc=test,dc=com as the User Federation Record Context, dc=test,dc=com must exist in the LDAP repository.

- LDAP Container Object Class: Optional. Enter the object class for the container that stores federation records. If this field is empty, the default value of applicationProcess is used.

- Active Directory Domain: Appears only if you select Microsoft Active Directory for the LDAP Type. Enter the name of the Microsoft Active Directory domain.

If you selected RDBMS for Federation Store, the Specify Federation Store Database Details screen will appear. Enter the following information:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the name of the schema owner created by RCU, which is of the form PREFIX_OIF.

- Password: Enter the password for the database user.

If you selected RDBMS for User Session Store, Message Store, or Configuration Store, the Specify Transient Store Database Details screen will appear. Enter the following information:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the name of the schema owner created by RCU, which is of the form PREFIX_OIF.

- Password: Enter the password for the database user.
Click Next.

13. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

14. The Configuration Progress screen appears. Click Next to continue.

15. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

9.7 Advanced Example: Configuring OIF with OID in a New WebLogic Domain for LDAP Authentication, User Store, and Federation Store

This section describes how to configure Oracle Identity Federation (OIF) with Oracle Internet Directory in a new WebLogic administration domain for LDAP Authentication, User Store, and Federation Store.

Note:

When you configure Oracle Identity Federation with Oracle Internet Directory, the Installer automatically configures connection, credential, attribute, and container settings using the Oracle Internet Directory configuration.

This section includes the following information about this configuration:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

9.7.1 Appropriate Deployment Environment

Perform the configuration in this topic to quickly deploy Oracle Identity Federation with Oracle Internet Directory as the LDAP repository for Authentication, User Store, and Federation Store.

9.7.2 Components Deployed

Performing the configuration in this section deploys the following components:

- WebLogic Managed Server

- Oracle Identity Federation

- Oracle Internet Directory

- Oracle Directory Services Manager

- WebLogic Administration Server

- Fusion Middleware Control

- Optionally, Oracle HTTP Server

9.7.3 Dependencies

The configuration in this section depends on the following components:

- Oracle WebLogic Server

- Oracle Database for Oracle Internet Directory

- Identity Management - Oracle Internet Directory schema existing in the database for Oracle Internet Directory

- Oracle Database for Oracle Identity Federation, if using RDBMS for Session Store, Message Store, or Configuration Store.

- New Identity Management - Oracle Identity Federation schema existing in the database for Oracle Identity Federation, if using RDBMS for Session Store, Message Store, or Configuration Store.

9.7.4 Procedure

Perform the following steps to configure Oracle Identity Federation with Oracle Internet Directory in a new domain for LDAP Authentication, User Store, and Federation Store:

1. Decide if you want to use RDBMS for Session Store, Message Store, or Configuration Store. If you do, perform the following steps a and b.

1. Install the database for Oracle Identity Federation. Refer to Installing Oracle Database for more information.

2. Create the Identity Management - Oracle Identity Federation schema in the database. Refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) for more information.

2. Install the Oracle Database for Oracle Internet Directory. Refer to Installing Oracle Database for more information.

3. Create the Identity Management - Oracle Internet Directory schema in the database for Oracle Internet Directory. Refer to "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)" for more information.

4. Ensure that Oracle Identity Federation is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

5. Run <ORACLE_HOME>/bin/config.sh (On UNIX) or <ORACLE_HOME>\bin\config.bat to start the Oracle Identity Management Configuration Wizard. Click Next to continue.

6. On the Select Domain screen, select Create New Domain and enter the following information:

- User Name: Enter the user name for the new domain.

- User Password: Enter the user password for the new domain.
Enter the user password again in the Confirm Password field.

- Domain Name: Enter a name for the new domain.

Click Next. The Specify Installation Location screen appears.

7. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

8. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

9. Select Oracle Internet Directory, Oracle Identity Federation, and optionally, Oracle HTTP Server. Refer to "Configuring Oracle HTTP Server for OIF" for information about configuring Oracle HTTP Server with Oracle Identity Federation.
The Oracle Directory Services Manager and Fusion Middleware Control management components are automatically selected for this installation.

Ensure no other components are selected and click Next. The Configure Ports screen appears.

10. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Schema Database screen appears.

11. Identify the ODS schema for Oracle Internet Directory that you created in step 3 by selecting Use Existing Schema and entering the following information:

- Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Enter the password for the ODS schema in the Password field and click Next.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

The Create Oracle Internet Directory screen appears.

12. Enter the following information for Oracle Internet Directory:

- Realm: Enter the location for your realm.

- Administrator Password: Enter the password for the Oracle Internet Directory Administrator.

- Confirm Password: Enter the administrator password again.

Click Next. The Specify OIF Details screen appears.

13. Enter the following information:

- PKCS12 Password: Enter the password Oracle Identity Federation will use for encryption and for signing wallets. The Installer automatically generates these wallets with self-signed certificates. Oracle recommends using the wallets only for testing.

- Confirm Password: Enter the PKCS12 password again.

- Server ID: Enter a string that will be used to identify this Oracle Identity Federation instance. A prefix of oif will be added to the beginning of the string you enter. Each logical Oracle Identity Federation instance within an Oracle WebLogic Server administration domain must have a unique Server ID. Clustered Oracle Identity Federation instances acting as a single logical instance will have the same Server ID.

Click Next. The Select OIF Advanced Flow Attributes screen appears.

Notes:

- Notice that the options for Authentication Type, User Store and Federation Store are automatically set to LDAP because you are installing Oracle Internet Directory with Oracle Identity Federation.

- The Installer sets the User Federation Record Context to cn=fed,BASE_REALM, where BASE_REALM is typically dc=myhost,dc=mycompany,dc=com.

14. Select the appropriate option for each configuration item and click Next:

Note:

User Session Store and Message Store appear in the Installer as separate configuration items, however, most deployments use the same type of repository for both stores.

- User Session Store: Memory or RDBMS

- Select Memory to store transient runtime session state data in in-memory tables.

- Select RDBMS to store transient runtime session state data in a relational database.

- Message Store: Memory or RDBMS

- Select Memory to store transient protocol messages in in-memory tables

- Select RDBMS to store transient protocol messages in a relational database.

- Configuration Store: File or RDBMS

- Select File to store Oracle Identity Federation configuration data on the local file system.

- Select RDBMS to store Oracle Identity Federation configuration data in a relational database.

Note:

The screens that appear next depend on the options you selected for the configuration items.

- If you selected RDBMS for User Session Store, Message Store, or Configuration Store, go to step 15 now.

- If you did not select RDBMS for User Session Store, Message Store, or Configuration Store, go to step 16 now.

15. Enter the following information on the Specify Transient Store Database Details screen:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the name of the schema owner created by RCU, which is of the form PREFIX_OIF.

- Password: Enter the password for the database user.
Click Next.

16. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

17. The Configuration Progress screen appears. Click Next to continue.

18. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

9.8 Advanced Example: Configuring OIF in a New or Existing WebLogic Domain with RDBMS Data Stores

This topic describes how to configure Oracle Identity Federation (OIF) in a new or existing WebLogic administration domain with RDBMS data stores. It includes the following sections:

- Appropriate Deployment Environment

- Components Deployed

- Dependencies

- Procedure

9.8.1 Appropriate Deployment Environment

Perform the configuration in this topic to quickly deploy Oracle Identity Federation with RDBMS User Store, Federation Store, Session Store, Message Store, and Configuration Store.

9.8.2 Components Deployed

Performing the configuration in this section deploys the following components:

If you configure Oracle Identity Federation in a new domain:

- WebLogic Administration Server

- Fusion Middleware Control

- WebLogic Managed Server

- Oracle Identity Federation

- Optionally, Oracle HTTP Server

If you configure Oracle Identity Federation in an existing domain:

- WebLogic Managed Server

- Oracle Identity Federation

- Optionally, Oracle HTTP Server

9.8.3 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Database for User Store, Federation Store, Session Store, Message Store, and Configuration Store.

- New Identity Management - Oracle Identity Federation schema existing in the database for Federation Store, Session Store, Message Store, and Configuration Store.

- Table for storing user data in the User Store database.

- LDAP repository, if using LDAP for Authentication.

9.8.4 Procedure

Perform the following steps to configure Oracle Identity Federation in a new or existing domain with RDBMS User Store, Federation Store, User Session Store, Message Store, and Configuration Store:

1. Install the database(s) for the RDBMS User Store, Federation Store, User Session Store, Message Store, and Configuration Store. Refer to Installing Oracle Database for more information.

2. Create the Identity Management - Oracle Identity Federation schema in the database(s). Refer to Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU) for more information.

3. Decide if you want to use an LDAP repository for Authentication. If you do, you must install the LDAP repository before you can install Oracle Identity Federation.

4. Ensure that Oracle Identity Federation is installed, as described in Installation Roadmap and Installing Oracle Identity Management Using "Install and Configure" Option.

5. Run <ORACLE_HOME>/bin/config.sh (On UNIX) or <ORACLE_HOME>\bin\config.bat to start the Oracle Identity Management Configuration Wizard. Click Next to continue.

6. On the Select Domain screen, choose whether to install Oracle Identity Federation in a new or existing domain:
To configure Oracle Identity Federation in a new domain:

1. Select Create New Domain.

2. Enter the user name for the new domain in the User Name field.

3. Enter the user password for the new domain in the User Password field.

4. Enter the user password again in the Confirm Password field.

5. Enter a name for the new domain in the Domain Name field.

6. Click Next. The Specify Installation Location screen appears.

7. Continue the installation by going to step 7 now.

To install Oracle Identity Federation in an existing domain:

1. Select Extend Existing Domain.

2. Enter the name of the host that contains the domain in the Host Name field.

3. Enter the listen port for the WebLogic Administration Server in the Port field.

4. Enter the user name for the domain in the User Name field.

5. Enter the password for the domain user in the User Password field.

6. Click Next. The Specify Installation Location screen appears.

7. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories".

Note:

To install Oracle Identity Management components in an existing Oracle WebLogic Server administration domain, each Oracle WebLogic Server Home, Oracle Middleware Home, and Oracle Home directory in the domain must have identical directory paths and names.

After you enter information for each field, click Next. The Specify Security Updates screen appears.

8. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

9. Select Oracle Identity Federation—and optionally, Oracle HTTP Server. Refer to "Configuring Oracle HTTP Server for OIF" for information about configuring these two components simultaneously.
If you are installing Oracle Identity Federation in a new domain, the Fusion Middleware Control management component is automatically selected for installation.

Ensure no other components are selected and click Next. The Configure Ports screen appears.

10. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Select Oracle Identity Federation Configuration Type screen appears.

11. Select Advanced and click Next. The Specify OIF Details screen appears.

12. Enter the following information:

- PKCS12 Password: Enter the password Oracle Identity Federation will use for encryption and for signing wallets. The Installer automatically generates these wallets with self-signed certificates. Oracle recommends using the wallets only for testing.

- Confirm Password: Enter the PKCS12 password again.

- Server ID: Enter a string that will be used to identify this Oracle Identity Federation instance. A prefix of oif will be added to the beginning of the string you enter. Each logical Oracle Identity Federation instance within an Oracle WebLogic Server administration domain must have a unique Server ID. Clustered Oracle Identity Federation instances acting as a single logical instance will have the same Server ID.

Click Next. The Select OIF Advanced Flow Attributes screen appears.

13. Select the following and click Next:

- Authentication Type: JAAS or LDAP

- Select JAAS to delegate authentication to the application server.

- Select LDAP to authenticate against an LDAP repository.

- User Store: RDBMS

- Federation Store: RDBMS

- User Session Store: RDBMS

- Message Store: RDBMS

- Configuration Store: RDBMS

Note:

The screen that appears next depends on what you selected for Authentication:

- If you selected LDAP for Authentication Type, the Specify Authentication LDAP Details screen appears. Continue you installation by going to step 14 now.

- If you selected JAAS for Authentication Type, the Specify User Store Database Details screen appears. Continue you installation by going to step 15 now.

14. Enter the following information on the Specify Authentication LDAP Details screen to identify the LDAP repository that will perform authentication:

- LDAP Type: Select the appropriate LDAP repository.

- LDAP URL: Enter the URL connection string for the LDAP repository in the form: protocol://hostname:port

Note:

If you selected Microsoft Active Directory for the LDAP Type, you must specify an SSL LDAP URL, that is, ldaps://hostname:port.

- LDAP Bind DN: Enter the bind DN for the LDAP repository.

- LDAP Password: Enter the password for the bind DN.

- User Credential ID Attribute: Enter the LDAP attribute Oracle Identity Federation will use to authenticate users. For example, if you enter mail and the value of the mail attribute for a user is jane.doe@domain.com, then Jane Doe must enter jane.doe.@domain.com when challenged. Values for the LDAP attribute you identify for User Credential ID Attribute must be unique for all users.

- User Unique ID Attribute: Enter the LDAP attribute that will uniquely identify users to Oracle Identity Federation. The value you enter must be identical to the value you enter for the User Data Store's User ID Attribute parameter. For example, if you enter mail for User Unique ID Attribute and you configure the User Data Store's User ID Attribute parameter with a value of EmailAddress, then the value of mail in the authentication engine repository must equal the value of EmailAddress in the User Data Store. Values for the LDAP attribute you identify for User Unique ID Attribute must be unique for all users.

- Person Object Class: Enter the LDAP object class that represents a user in the LDAP repository. For example: inetOrgPerson for Oracle Internet Directory and Sun Java System Directory Server, and user for Microsoft Active Directory.

- Base DN: Enter the root DN that searches will start from.

Click Next. The Specify User Store Database Details screen appears.

15. Enter the following information to identify the database that will store user data:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the database username.

- Password: Enter the password for the database user.

- Login Table: Enter the name of the table that will store user data. The value you enter must be a valid table name, and the values you enter for User ID Attribute and User Description Attribute must be valid column names in the table you identify.

- User ID Attribute: Enter the name of the table column to use for the Oracle Identity Federation user ID. The value you enter must be a valid column name in the table you identified for the Login Table parameter.

- User Description Attribute: Enter the name of the table column to use for the user description. The value you enter must be a valid column name in the table you identified for the Login Table parameter.

Click Next. The Specify Federation Store Database Details screen appears.

16. Enter the following information to identify the database that will store federated user account linking data:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the name of the schema owner created by RCU, which is of the form PREFIX_OIF.

- Password: Enter the password for the database user.

Click Next. The Specify Transient Store Database screen appears.

17. Enter the following information to identify the database that will store transient runtime session state data, protocol messages, and Oracle Identity Federation configuration data:

- HostName: Enter the connection string to the database host in the form: hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form: hostname1:port1:instance1^hostname2:port2:instance2@servicename.

- Username: Enter the name of the schema owner created by RCU, which is of the form PREFIX_OIF.

- Password: Enter the password for the database user.

Click Next.

18. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

19. The Configuration Progress screen appears. Click Next to continue.

20. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.

9.9 Verifying OIF

Verify the Oracle Identity Federation (OIF) installation by:

- Accessing the Oracle Identity Federation metadata at the following URL. Oracle Identity Federation was installed and the Oracle Identity Federation server is running if you can access the metadata.
http://host:port/fed/sp/metadata

Note:

host represents the name of the WebLogic Managed Server where Oracle Identity Federation was installed. port represents the listen port on that WebLogic Managed Server.

- Accessing Fusion Middleware Control to verify that Oracle Identity Federation is available and running. For more information, see "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" in the Oracle Fusion Middleware Administrator's Guide.

9.10 Getting Started with OIF After Installation

After installing Oracle Identity Federation (OIF), refer to the "Common Tasks" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

10 Configuring Oracle Unified Directory with Oracle Identity Management 11.1.1.7.0

This chapter discusses the following topics:

- Before You Begin

- Configuring only Oracle Unified Directory (OUD)

- Configuring Oracle Unified Directory (OUD) with ODSM

- Configuring OUD/ODSM/ODIP/Fusion Middleware Control and OVD/ODSM

10.1 Before You Begin

Before performing any installation, you should read the following documents to ensure that your Oracle Fusion Middleware environment meets the minimum installation requirements for the products you are installing.

- Review System Requirements and Specifications

- Review Certification Information

10.1.1 Review System Requirements and Specifications

Oracle Fusion Middleware System Requirements and Specifications document is available at:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

This document covers information such as hardware and software requirements, database schema requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches.

10.1.2 Review Certification Information

Oracle Fusion Middleware Supported System Configurations document is available at:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

This document contains certification information related to supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products.

10.2 Configuring only Oracle Unified Directory (OUD)

To configure only Oracle Unified Directory (OUD), refer to the following topics of the Oracle Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 1 (11.1.1):

- "Installing the Software", available at:
http://download.oracle.com/docs/cd/E22289_01/html/821-1274/installing-the-software.html#scrolltoc

- "Setting Up the Directory Server", available at:
http://download.oracle.com/docs/cd/E22289_01/html/821-1274/setting-up-ds.html#scrolltoc

10.3 Configuring Oracle Unified Directory (OUD) with ODSM

To configure Oracle Unified Directory (OUD) with Oracle Directory Services Manager (ODSM), refer to the following topics:

- Installing Oracle WebLogic Server 11g Release 1 (10.3.5 or 10.3.6). For more information, see "Install Oracle WebLogic Server" in the Oracle Fusion Middleware Installation Planning Guide. In addition, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for complete information about installing Oracle WebLogic Server.

- "Installing the Software" in the Oracle Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 1 (11.1.1), available at:
http://download.oracle.com/docs/cd/E22289_01/html/821-1274/installing-the-software.html#scrolltoc

Note:

In the Specify Installation Location screen enter the location of the Oracle Middleware Home for the OUD Base Location Home.

- "Setting Up the Directory Server" in the Oracle Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 1 (11.1.1), available at:
http://download.oracle.com/docs/cd/E22289_01/html/821-1274/setting-up-ds.html#scrolltoc

- "Managing Oracle Unified Directory With Oracle Directory Services Manager" in the Oracle Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 1 (11.1.1), available at:
http://download.oracle.com/docs/cd/E22289_01/html/821-1273/managing-ojd-with-odsm.html

10.4 Configuring OUD/ODSM/ODIP/Fusion Middleware Control and OVD/ODSM

This topic describes how to configure Oracle Unified Directory (OUD), Oracle Directory Services Manager (ODSM), Oracle Directory Integration Platform (ODIP) and Fusion Middleware Control in a new WebLogic administration domain (for example: domain1); and Oracle Virtual Directory(OVD) and Oracle Directory Services Manager (ODSM) in a separate WebLogic administration domain (for example: domain2). It includes the following sections:

- Part I: Configuring OVD with ODSM and Fusion Middleware Control in a New WebLogic Administration Domain

- Part II: Configuring OUD/ODSM/ODIP and Fusion Middleware Control in a New WebLogic Administration Domain

10.4.1 Part I: Configuring OVD with ODSM and Fusion Middleware Control in a New WebLogic Administration Domain

This topic describes how to configure Oracle Virtual Directory (OVD) with Oracle Directory Services Manager (ODSM) and Fusion Middleware Control in a new WebLogic administration domain. It includes the following sections:

- Dependencies

- Procedure

Note:

Part I is optional if you do not wish to use Oracle Virtual Directory (OVD).

10.4.1.1 Dependencies

The configuration in this section depends on Oracle WebLogic Server.

10.4.1.2 Procedure

Perform the following steps to configure Oracle Virtual Directory with Oracle Directory Services Manager and Fusion Middleware Control in a new domain:

1. Ensure that Oracle WebLogic Server 11g Release 1 (10.3.5 or 10.3.6) is installed. For more information, see "Install Oracle WebLogic Server" in the Oracle Fusion Middleware Installation Planning Guide. In addition, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for complete information about installing Oracle WebLogic Server.

Note:

After installing Oracle WebLogic Server, ensure that you complete the following steps:

1. Open the setNMProps file (located at <MW_HOME>/oracle_common/common/bin directory), and ensure that the StartScriptEnabled property is set to true.

2. Run the <MW_HOME>/oracle_common/common/bin/setNMProps.sh script (on UNIX) or <MW_HOME>\oracle_common\common\bin\setNMProps.cmd (on Windows).

3. Start the Node Manager by executing the following command:
On UNIX:

Run startNodeManager.sh (Located at <WL_HOME>/server/bin directory).

On Windows:

Run startNodeManager.cmd (Located at <WL_HOME>\server\bin directory).

2. Ensure that Oracle Virtual Directory is installed, as described in Installing Oracle Identity Management Using "Install and Configure" Option.

Note:

If you selected Install and Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, the Select Domain screen is displayed.

If you selected Install Software - Do Not Configure option in the Select Installation Type screen while installing Oracle Identity Management 11g Release 1 (11.1.1.7.0), as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software, you must now start the Oracle Identity Management Configuration Wizard. Run <ORACLE_HOME>/bin/config.sh (on UNIX) or <ORACLE_HOME>\bin\config.bat (on Windows) to start the Oracle Identity Management Configuration Wizard. The Select Domain screen is displayed.

3. On the Select Domain screen, select Create New Domain and enter the following information:

- Enter the user name for the new domain in the User Name field.

- Enter the user password for the new domain in the User Password field.

- Enter the user password again in the Confirm Password field.

- Enter a name for the new domain in the Domain Name field.

Click Next. The Specify Installation Location screen appears.

4. Identify the Homes, Instances, and the WebLogic Server directory by referring to Section 2.6, "Identifying Installation Directories". After you enter information for each field, click Next. The Specify Security Updates screen appears.

5. Choose how you want to be notified about security issues:

- If you want to be notified about security issues through email, enter your email address in the Email field.

- If you want to be notified about security issues through My Oracle Support (formerly MetaLink), select the My Oracle Support option and enter your My Oracle Support Password.

- If you do not want to be notified about security issues, leave all fields empty.

Click Next. The Configure Components screen appears.

6. Select only Oracle Virtual Directory. The Oracle Directory Services Manager and Fusion Middleware Control management components are automatically selected for this installation.
Ensure no other components are selected and click Next. The Configure Ports screen appears.

7. Choose how you want the Installer to configure ports:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next. The Specify Oracle Virtual Directory Information screen appears.

8. Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next.

9. The Installation Summary screen appears. Verify the information on this screen. Click Configure to begin the configuration.

10. The Configuration Progress screen appears. Click Next to continue.

11. The Installation Complete screen appears. Click Save to save the configuration information to a file, and then click Finish to exit the installer.
A new WebLogic domain (for example: domain2) is created to support Oracle Virtual Directory (OVD) with Oracle Directory Services Manager (ODSM) and Fusion Middleware Control in the <MW_HOME>\user_projects\domains directory (on Windows). On UNIX, the domain is created in the <MW_HOME>/user_projects/domains directory.

For managing Oracle Virtual Directory (OVD) with Oracle Directory Services Manager (ODSM), refer to the "Getting Started with Administering Oracle Virtual Directory" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.

10.4.2 Part II: Configuring OUD/ODSM/ODIP and Fusion Middleware Control in a New WebLogic Administration Domain

This topic describes how to configure Oracle Unified Directory (OUD), Oracle Directory Services Manager (ODSM), Oracle Directory Integration Platform (ODIP) and Fusion Middleware Control in a New WebLogic administration domain. It includes the following sections:

- Prerequisites

- Dependencies

- Procedure

- Post-Configuration Steps

10.4.2.1 Prerequisites

Ensure that the following prerequisites are met.

- Installing Oracle WebLogic Server 11g Release 1

- Installing Oracle Unified Directory

- Setting Up Oracle Unified Directory with Replication Topology Option

10.4.2.1.1 Installing Oracle WebLogic Server 11g Release 1

Ensure that Oracle WebLogic Server 11g Release 1 (10.3.5 or 10.3.6) is installed. For more information, see "Install Oracle WebLogic Server" in the Oracle Fusion Middleware Installation Planning Guide. In addition, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for complete information about installing Oracle WebLogic Server.

10.4.2.1.2 Installing Oracle Unified Directory

Ensure that Oracle Unified Directory is installed, as described in "Installing the Software" in the Oracle Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 1 (11.1.1), available at the following link:

http://download.oracle.com/docs/cd/E22289_01/html/821-1274/installing-the-software.html#scrolltoc

Note:

In the Specify Installation Location screen enter the location of the Oracle Middleware Home for the OUD Base Location Home.

10.4.2.1.3 Setting Up Oracle Unified Directory with Replication Topology Option

For the first directory server in your replication topology, follow the instructions in "To Set Up the Directory Server Using the GUI" in the Oracle Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 1 (11.1.1), available at the following link:

http://download.oracle.com/docs/cd/E22289_01/html/821-1274/ds-gui-setup.html#to-set-up-the-directory-server-using-the-gui

Note:

To enable the changelog adapter, ensure that Oracle Unified Directory instance is setup with the replication topology option. Enabling the changelog adapter is a prerequisite for Oracle Directory Integration Platform (ODIP).

10.4.2.2 Dependencies

The configuration in this section depends on the following:

- Oracle WebLogic Server

- Oracle Unified Directory

10.4.2.3 Procedure

Perform the following steps to configure Oracle Unified Directory (OUD), Oracle Directory Services Manager (ODSM), Oracle Directory Integration Platform (ODIP) and Fusion Middleware Control in one domain.

1. Ensure that all the prerequisites are met as described in Prerequisites.

2. Ensure that Oracle Directory Integration Platform is installed using Install Software - Do Not Configure option, as described in Installing and Configuring Oracle Identity Management 11g Release 1 (11.1.1.7.0) Software.

3. Run the <MW_HOME>/oracle_common/common/bin/config.sh script (on UNIX) or <MW_HOME>\oracle_common\common\bin\config.cmd (on Windows). The Oracle Fusion Middleware Configuration Wizard appears.

4. On the Welcome screen, select the Create a new WebLogic domain option. Click Next.

5. On the Select Domain Source screen, select Generate a domain configured automatically to support the following products: option. Select the following domain configuration options:

- Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

- Oracle Directory Services Manager - 11.1.1.5.0 [Oracle_OUD1]

- Oracle Directory Integration Platform - 11.1.1.2.0 [Oracle_IDM1]

Note:

When you select Oracle Enterprise Manager - 11.1.1.0 [oracle_common] and Oracle Directory Integration Platform - 11.1.1.2.0 [Oracle_IDM1], Oracle Identity Management - 11.1.1.2.0 [Oracle_IDM1] and Oracle JRF 11.1.1.0 [oracle_common] is also selected by default.

Click Next. The Specify Domain Name and Location screen appears.

6. On the Specify Domain Name and Location screen, enter a name and location for the domain to be created. In addition, enter a location to store applications for the domain. Click Next. The Configure Administrator User Name and Password screen is displayed.

7. Configure a user name and a password for the administrator. The default user name is weblogic. Click Next. The Configure Server Start Mode and JDK screen is displayed.

8. Choose JRockit SDK 1.6.0_24 and Production Mode in the Configure Server Start Mode and JDK screen. Click Next. The Select Optional Configuration Screen is displayed.

9. On the Select Optional Configuration screen, select Administration Server and Managed Servers, Clusters, and Machines option. Click Next. The Configure the Administration Server screen appears.

10. On the Configure the Administration Server screen, specify the Administration Server name and the Listen port (the default port is 7001). Click Next. The Configure Managed Servers screen appears.

Note:

If you used the default values for the Administration Server name and the Listen port for the Oracle Directory Services Manager (ODSM) that is managing Oracle Virtual Directory (OVD), then you must use a different Administration Server name and Listen port for the Oracle Directory Services Manager (ODSM) that is managing Oracle Directory Integration Platform (ODIP).

For example, you can use 8001 as the Listen port for the Administration Server for Oracle Directory Services Manager (ODSM) that is managing Oracle Directory Integration Platform (ODIP).

11. On the Configure Managed Servers screen, specify the Managed Server name and the Listen port (the default port is 7005). Click Next.

Note:

If you used the default values for the Managed Server name and the Listen port for the Oracle Directory Services Manager (ODSM) that is managing Oracle Virtual Directory (OVD), then you must use a different Managed Server name and Listen port for the Oracle Directory Services Manager (ODSM) that is managing Oracle Directory Integration Platform (ODIP).

For example, you can use wls_ods2 as the Managed Server name and 8005 as the Listen port for the Managed Server for Oracle Directory Services Manager (ODSM) that is managing Oracle Directory Integration Platform (ODIP).

12. On the Configure Clusters screen, configure Clusters as required. Click Next.

13. On the Configure Machines screen, select the Machine or Unix Machine tab. Click on Add and specify the machine name. Click Next.

14. If you added a machine on the Configure Machines screen, then the Assign Servers to Machines screen appears. On the Assign Servers to Machines screen, assign the Administration Server and the Managed server to the specified machine. Click Next.

15. On the Configuration Summary screen, review the domain configuration, and click Create to start creating the domain.

16. Click Done, once the domain is created successfully.
A new WebLogic domain (for example: domain1) is created to support Oracle Unified Directory (OUD), Oracle Directory Services Manager (ODSM), Oracle Directory Integration Platform (ODIP) and Fusion Middleware Control in the <MW_HOME>\user_projects\domains directory (on Windows). On UNIX, the domain is created in the <MW_HOME>/user_projects/domains directory.

10.4.2.4 Post-Configuration Steps

After configuring Oracle Directory Integration Platform, perform the following tasks:

1. If the Administration Server and the Managed Server is not up and running then start the Administration Server and the Managed Server (wls_ods2) as described in Starting the Stack.

2. Verify the Oracle Unified Directory (OUD) server is up and running using the status command, which is located in the <OUD_INSTANCE>/bin/ directory.

3. Set the JAVA_HOME, WL_HOME and ORACLE_HOME environment variables and execute <ORACLE_HOME>/bin/dipConfigurator. Provide the following information when prompted for input.

- WebLogic host, port, username and password details.

- Oracle Unified Directory (OUD) host, port, username and password details. Also provide Oracle Unified Directory (OUD) admin port which is required to add global acis to access Changelog for DIP account.

- Specify the suffix under which DIP metadata is to be stored.

Following is a sample output for the dipConfigurator command:

Enter WLS Admin Server Host Name : myhost1.mycompany.com
Enter WLS Admin Server Port : 8001
Enter username to contact WebLogic Server : weblogic
[Enter password to contact WebLogic Server : ]
Enter backend LDAP Server HostName : myhost1.mycompany.com
Enter backend LDAP Server Port : 4389
Enter username to contact LDAP server : cn=directory manager
[Enter password to contact LDAP Server : ]
Enter backend LDAP Server Admin Port : 4444
Enter SUFFIX to store DIP metadata : dc=us,dc=mycompany,dc=com

Note:

dipConfigurator script creates a new ASInstance, and a new EMAgent component in that ASInstance. These agents are required for DIP metrics to display in Fusion Middleware Control. The instance, such as dip_inst1, is created under the MW_HOME directory.

4. Verify the Oracle Directory Integration Platform (ODIP) installation and configuration. For more information, see Verifying ODIP.

5. The dipConfigurator will set the below ACIs for the specified metadata suffix. But for the other suffixes, set the below ACIs for the containers in OUD, in order to write the changes imported from the other sources:

dn: <Container DN>
changetype:modify
add: aci
aci: (target="ldap:///<Container DN>")(version 3.0; acl "Anonymous read-search
access"; allow (read,add,delete,search,write,compare,proxy)
groupdn="ldap:///cn=dipadmingrp,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>"; allow
(read,add,delete,search,write,compare,proxy)
groupdn="ldap:///cn=odipigroup,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>"; )
-
add: aci
aci: (targetattr="*")(version 3.0; acl "Anonymous read-search access"; allow
(search,read,write,compare,add)
groupdn="ldap:///cn=dipadmingrp,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>"; allow (search,read,write,compare,add)
groupdn="ldap:///cn=odipigroup,cn=DIPadmins,cn=Directory Integration
Platform,<metadata suffix>";)

Note:

ODIP configuration can be recreated any number of times if ODIP configuration is deleted or corrupted, for example, while setting up OUD Replication Gateway or OUD Proxy Server. However, if there are any sync profiles that already exists, the connected directory password of the existing profiles needs to be reset after executing dipConfigurator.

For recreating the ODIP configuration, re-run step 3.

Part III

Appendixes

Part IV contains the following appendixes:

- Appendix A, "Oracle Identity Management 11.1.1.7.0 Software Installation Screens"

- Appendix B, "Starting or Stopping the Oracle Stack"

- Appendix C, "Deinstalling and Reinstalling Oracle Identity Management"

- Appendix D, "Performing Silent Installations"

- Appendix E, "Troubleshooting the Installation"

- Appendix F, "Software Deinstallation Screens"

A Oracle Identity Management 11.1.1.7.0 Software Installation Screens

This appendix describes the screens of the Oracle Identity Management 11g software Installation and Wizard that enables you to install and configure Oracle Internet Directory, Oracle Virtual Directory, Oracle Directory Service Manager, Oracle Directory Integration Platform, and Oracle Identity Federation.

It contains the following topics:

- Welcome

- Install Software Updates

- Select Installation Type

- Prerequisite Checks

- Select Domain

- Specify Installation Location

- Specify Security Updates

- Configure Components

- Configure Ports

- Specify Schema Database

- Specify Oracle Virtual Directory Information

- Specify OID Administrator Password

- Select Oracle Identity Federation Configuration Type

- Specify Oracle Identity Federation Details

- Installation Summary

- Installation Progress

- Configuration Progress

- Installation Complete

A.1 Welcome

The Welcome screen is displayed each time you start the Oracle Identity Management 11g Installer wizard.

Figure A-1 Welcome Screen

Click Next to continue.

A.2 Install Software Updates

This screen enables you to search for and install software updates before you install Oracle Identity Management.

Figure A-2 Install Software Updates Screen

To get updates from My Oracle Support, you can select Search My Oracle Support for Updates, specify a user name and password, and then click Search for Updates. Before you search, you can click Proxy Settings to change the settings for the proxy server and Test Connection to test the credentials.

To get updates that you have saved to your computer, you can select Search Local Directory for Updates, specify a directory, and then click Search for Updates.

If you do not want to update any software, you can select Skip Software Updates. The link on the left changes from My Oracle Support Updates to Skip Software Updates.

Click Next to start the software updates or continue the installation.

A.3 Select Installation Type

This screen enables you to select the installation type.

Figure A-3 Select Installation Type Screen

The Select Installation Type screen presents two options: Install and Configure and Install Software - Do Not Configure.

- Choose the Install and Configure option to install Oracle Identity Management components and simultaneously configure some of their fundamental elements, such as passwords, user names, and so on. Oracle Identity Management components start running and are immediately ready for use after deploying them using the Install and Configure option.

- Choose the Install Software - Do Not Configure option to install Oracle Identity Management components without configuring them during installation. If you choose the Install Software - Do Not Configure option, the Installer installs the component software and then closes. Oracle Identity Management components will not start running after deploying them using the Install Software - Do Not Configure option, as additional configuration is needed.
After you install components using the Install Software - Do Not Configure option, you can configure them at a later time using the Oracle Identity Management 11g Release 1 (11.1.1.7.0) Configuration Wizard. To start the Oracle Identity Management 11g Release 1 (11.1.1.7.0) Configuration Wizard, execute the ORACLE_HOME/bin/config.sh script (config.bat on Windows).

Click Next to continue.

A.4 Prerequisite Checks

The installation program ensures that you have a certified version, the correct software packages, sufficient space and memory to perform the operations that you have selected. If any issues are detected, errors appear on this page.

The following example screen applies to Windows operating systems only.

Figure A-4 Prerequisite Checks Screen

On this screen, you can select to Abort, Retry, or Continue with the installation.

If all the prerequisite checks pass inspection, click Next to continue.

A.5 Select Domain

This screen allows you to select the Domain. Select one of the following options:

- Option 1: Create New Domain

- Option 2: Extend Existing Domain

- Option 3: Expand Cluster

- Option 4: Configure Without a Domain

Option 1: Create New Domain

Figure A-5 Create New Domain option

Enter the User Name, User Password, and Domain Name for the domain you want to create.

Click Next to continue.

Option 2: Extend Existing Domain

Figure A-6 Extend Existing Domain option

Enter the Host Name, Port, User Name, and User Password for the existing domain you want to extend into.

Click Next to continue.

Option 3: Expand Cluster

Figure A-7 Expand Cluster option

Enter the information for the existing cluster you want to expand your Oracle Identity Management installation into. Enter the Host Name, Port, User Name, and User Password for cluster inclusion.

Click Next to continue.

Option 4: Configure Without a Domain

If you select this option, you will not be creating or extending the domain of your installation.

Click Next to continue.

A.6 Specify Installation Location

This screen allows you to enter a location for the new Oracle Identity Management 11g software being installed.

Figure A-8 Specify Installation Location Screen

Ensure that Oracle WebLogic Server is already installed on your machine. Navigate to the Oracle Fusion Middleware Home directory by clicking Browse. Enter a name for the new Oracle Home directory for Oracle Identity Management 11g components.

If the Middleware location does not exist, you must install WebLogic Server and create a Middleware Home directory, as described in Section 4.2.5, "Installing Oracle WebLogic Server and Creating the Middleware Home", before running the Oracle Identity Management Installer.

Note:

If you do not specify a valid Middleware Home directory on the Specify Installation Location screen, the Installer displays a message and prompts you to confirm whether you want to proceed with the installation of only Oracle Identity Manager Design Console and Oracle Identity Manager Remote Manager. These two components of Oracle Identity Manager do not require a Middleware Home directory.

If you want to install only Oracle Identity Manager Design Console or Remote Manager, you do not need to install Oracle WebLogic Server or create a Middleware Home directory on the machine where Design Console or Remote Manager is being configured.

Click Next to continue.

A.7 Specify Security Updates

This screen allows you to provide your E-mail address to be informed of the latest product issues.

Figure A-9 Specify Security Updates Screen

Click Next to continue.

A.8 Configure Components

This screen allows you to select the Oracle Identity Management components that you wish to install and configure.

Figure A-10 Configure Components Screen

Click Next to continue.

A.9 Configure Ports

This screen allows you to choose how you want the Installer to configure ports.

Figure A-11 Configure Ports Screen

TheConfigure Ports screen presents two options:

- Select Auto Port Configuration if you want the Installer to configure ports from a predetermined range.

- Select Specify Ports using Configuration File if you want the Installer to configure ports using the staticports.ini file. You can click View/Edit File to update the settings in the staticports.ini file.

Click Next to continue.

A.10 Specify Schema Database

This screen is displayed if you selected Oracle Internet Directory. This screen allows you to choose whether to use an existing schema or to create a new one using the Installer.

Figure A-12 Specify Schema Database Screen

The Specify Schema Database screen presents two options:

Note:

If you want to use an existing schema, it must currently reside in the database to continue with the installation. If it does not currently reside in the database, you must create it now using the Oracle Fusion Middleware Repository Creation Utility.

- Use Existing Schema
To use an existing schema:

1. Select Use Existing Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the password for the existing ODS schema in the Password field.

4. Click Next to continue.

Note:

If your existing ODS and ODSSM schemas have different passwords, the Specify ODSSM Password screen will appear after you click Next. Enter the password for your existing ODSSM schema and click Next.

- Create Schema
To create a new schema:

1. Select Create Schema.

2. Enter the database connection information in the Connect String field. The connection string must be in the form of hostname:port:servicename. For Oracle Real Application Clusters (RAC), the connection string must be in the form of hostname1:port1:instance1^hostname2:port2:instance2@servicename.

3. Enter the name of the database user in the User Name field. The user you identify must have DBA privileges.

Note:

If you are using Oracle Database 11g Release 2 (11.2) or higher version, the database user should be only 'SYS'.

4. Enter the password for the database user in the Password field.

5. Click Next. The Enter OID Passwords screen appears.

6. Create a password for the new ODS schema by entering it in the ODS Schema Password field.
Enter it again in the Confirm ODS Schema Password field.

7. Create a password for the new ODSSM schema by entering it in the ODSSM Schema Password field.
Enter it again in the Confirm ODSSM Schema Password field.

8. Click Next to continue.

A.11 Specify Oracle Virtual Directory Information

This screen is displayed if you selected Oracle Virtual Directory. This screen allows you to specify Oracle Virtual Directory information.

Figure A-13 Specify Oracle Virtual Directory Information Screen

Enter the following information:

- LDAP v3 Name Space: Enter the name space for Oracle Virtual Directory. The default value is dc=myhost,dc=mycompany,dc=com.

- HTTP Web Gateway: Select this option to enable the Oracle Virtual Directory HTTP Web Gateway.

- Secure: Select this option if you enabled the HTTP Web Gateway and you want to secure it using SSL.

- Administrator User Name: Enter the user name for the Oracle Virtual Directory administrator. The default value is cn=orcladmin.

- Password: Enter the password for the Oracle Virtual Directory administrator.

- Confirm Password: Enter the password for the Oracle Virtual Directory administrator again.

- Configure Administrative Server in secure mode: Select this option to secure the Oracle Virtual Directory Administrative Listener using SSL. This option is selected by default. Oracle recommends selecting this option.

Click Next to continue.

A.12 Specify OID Administrator Password

This screen is displayed if you selected Oracle Internet Directory.

Figure A-14 Specify OID Administrator Password Screen

Enter the password for the Oracle Internet Directory administrator.

Click Next to continue.

A.13 Select Oracle Identity Federation Configuration Type

This screen is displayed if you selected Oracle Identity Federation.

Figure A-15 Select Oracle Identity Federation Configuration Type Screen

Select one of the following configuration types:

- Basic: You do not need to choose the datastore and authentication engine types or specify the connection details for Oracle Identity Federation.

- Advanced: This option will enable you to choose the configuration types for the datastores, the authentication engine, and specify the connection details datastores and authentication engine.

Click Next to continue.

A.14 Specify Oracle Identity Federation Details

This screen is displayed if you selected Oracle Identity Federation.

Figure A-16 Specify Oracle Identity Federation Details Screen

Enter the following information:

- PKCS12 Password: Enter the password Oracle Identity Federation will use for encryption and for signing wallets. The Installer automatically generates these wallets with self-signed certificates. Oracle recommends using the wallets only for testing.

- Confirm Password: Enter the PKCS12 password again.

- Server ID: Enter a string that will be used to identify this Oracle Identity Federation instance. A prefix oif will be added to the beginning of the string you enter. Each logical Oracle Identity Federation instance within an Oracle WebLogic Server administration domain must have a unique Server ID. Clustered Oracle Identity Federation instances acting as a single logical instance will have the same Server ID.

Click Next to continue.

A.15 Installation Summary

This screen displays a summary of your Oracle Identity Management 11g installation.

Figure A-17 Installation Summary Screen

Review the contents of this screen, and click Install to start installing the Oracle Identity Management 11g software.

A.16 Installation Progress

This screen displays the progress of the Oracle Identity Management installation.

Figure A-18 Installation Progress Screen

If you want to quit before the installation is completed, click Cancel. The installation progress indicator gives a running inventory of the files that are being installed. If you are only installing the software binaries, installation is complete after all of the binaries have been installed.

Click Next to continue.

A.17 Configuration Progress

This screen displays the progress of the Oracle Identity Management configuration.

Figure A-19 Configuration Progress Screen

If you want to abort the configuration before the configuration is completed, click Abort. If you want to retry the configuration, click Retry.

Click Next to continue.

A.18 Installation Complete

This screen displays a summary of the installation parameters, such as Location, Disk Space, and Applications. To save the installation configuration in a response file, which is used to perform silent installations, click Save.

Figure A-20 Installation Complete Screen

Click Finish to complete the installation process.

B Starting or Stopping the Oracle Stack

You must start or stop the components of the Oracle stack in a specific order. This appendix describes that order and contains the following topics:

- Starting the Stack

- Stopping the Stack

- Restarting Servers

Note:

When executing the startManagedWebLogic and stopManagedWebLogic scripts described in the following topics:

- SERVER_NAME represents the name of the Oracle WebLogic Managed Server, such as wls_oif1, wls_ods1, or oam_server1.

- You will be prompted for values for USER_NAME and PASSWORD if you do not provide them as options when you execute the script.

- The value for ADMIN_URL will be inherited if you do not provide it as an option when you execute the script.

B.1 Starting the Stack

After completing the installation and domain configuration, you must start the Administration Server and various Managed Servers to get your deployments up and running:

1. To start the Administration Server, run the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.
On UNIX systems:

MW_HOME/user_projects/domains/domain_name/startWebLogic.sh

On Windows systems:

MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd

You entered the domain name and location on the Specify Domain Name and Location Screen in the Configuration Wizard.

2. Ensure that the Node Manager is running. Oracle WebLogic Administration Server does not do this automatically. If the Node Manager is not running, start the Node Manager by executing the following command:

$WLS_HOME/server/bin/startNodeManager.sh

3. Start system components, such as Oracle Internet Directory and Oracle Virtual Directory, by executing the following command:

ORACLE_INSTANCE/bin/opmnctl startall

You can verify that the system components have started by executing the following command:

ORACLE_INSTANCE/bin/opmnctl status -l

4. To start the Managed Servers, run the startManagedWebLogic.sh (on UNIX operating systems) or startManagedWebLogic.cmd (on Windows operating systems) script in the bin directory inside the directory where you created your domain. You must start these Managed Servers from the command line.
This command also requires that you specify a server name. You must start the servers you created when configuring the domain, as shown in the following example:

- oam_server1 (Oracle Access Manager Server)

- oim_server1 (Oracle Identity Manager Server)

For example, to start Oracle Access Manager Server on a UNIX system:

MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh oam_server1

On Windows systems:

MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd oam_server1

Before the Managed Server is started, you are prompted for the WebLogic Server user name and password. These were provided on the Configure Administrator Username and Password Screen in the Configuration Wizard.

If your Administration Server is using a non-default port, or resides on a different host than your Managed Servers (in a distributed environment), you must also specify the URL to access your Administration Server.

On UNIX systems:

MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh oam_server1 http://host:admin_server_port

On Windows systems:

MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd oam_server1 http://host:admin_server_port

Instead of being prompted for the Administration Server user name and password, you can also specify them directly from the command lime.

On UNIX systems:

MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh oam_server1 http://host:admin_server_port -Dweblogic.management.username=user_name -Dweblogic.management.password=password

On Windows systems:

MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd oam_server1 http://host:admin_server_port -Dweblogic.management.username=user_name -Dweblogic.management.password=password

Note:

You can use the Oracle WebLogic Administration Console to start managed components in the background. See Oracle Fusion Middleware Introduction to Oracle WebLogic Server for more information.

If you do not know the names of the Managed Servers that should be started, you can view the contents of the following file on UNIX systems:

MW_HOME/user_projects/domains/domain_name/startManagedWebLogic_readme.txt

On Windows systems:

MW_HOME\user_projects\domains\domain_name\startManagedWebLogic_readme.txt

Or, you can access the Administration Server console at the following URL:

http://host:admin_server_port/console

Supply the user name and password that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard. Then, navigate to Environment > Servers to see the names of your Managed Servers.

B.2 Stopping the Stack

You can stop the Oracle WebLogic Administration Server and all the managed servers by using Oracle WebLogic Administration Console. See Oracle Fusion Middleware Introduction to Oracle WebLogic Server for more information.

To stop the stack components from the command line, perform the following steps:

1. Stop WebLogic managed components, such as Oracle Directory Integration Platform, Oracle Identity Federation, Oracle Directory Services Manager, Oracle Access Manager, Oracle Identity Manager, and Oracle Adaptive Access Manager, by executing the following command:

MW_HOME/user_projects/domains/DOMAIN_NAME/bin/stopManagedWebLogic.sh \
{SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD}

2. Stop system components, such as Oracle Internet Directory and Oracle Virtual Directory, by executing the following command:

ORACLE_INSTANCE/bin/opmnctl stopall

3. Stop the Oracle WebLogic Administration Server by executing the following command:

MW_HOME/user_projects/domains/DOMAIN_NAME/bin/stopWebLogic.sh

4. If you want to stop the Node Manager, you can use the kill command:

kill -9 PID

B.3 Restarting Servers

To restart the Administration Server or Managed Servers, you must stop the running Administration Server or Managed Servers first before starting them again. For more information, see Stopping the Stack and Starting the Stack.

C Deinstalling and Reinstalling Oracle Identity Management

This appendix provides information about deinstalling and reinstalling Oracle Identity Management 11g Release 1 (11.1.1). It contains the following topics:

- Deinstalling Oracle Identity Management

- Reinstalling Oracle Identity Management

Note:

Always use the instructions provided in this appendix for removing the software. If you try to remove the software manually, you may experience problems when you try to reinstall the software. Following the procedures in this appendix ensures that the software is properly removed.

C.1 Deinstalling Oracle Identity Management

This topic contains procedures for deinstalling Oracle Identity Management. It contains the following sections:

- Deinstalling the Oracle Identity Management Oracle Home

- Deinstalling the Oracle Common Home

- Deinstalling Applications Registered with Oracle Single Sign-On 10g Release 10.1.4.3.0

C.1.1 Deinstalling the Oracle Identity Management Oracle Home

The deinstaller attempts to remove the Oracle Home directory from which it was started. Before you choose to remove your Oracle Identity Management Oracle Home directory, make sure that it is not in use by an existing domain and that you stop all running processes that use this Oracle Home.

Deinstalling Oracle Identity Management will not remove any WebLogic domains that you have created—it only removes the software in the Oracle Identity Management Oracle Home directory.

Note:

The oraInventory is required for removing instances and Oracle Home. For example, on UNIX it can be found in the following location:

/etc/oraInst.loc

This section describes how to deinstall your Oracle Identity Management Oracle Home using the graphical, screen-based deinstaller. However, you can also perform a silent deinstallation using a response file. A deinstall response file template that you can customize for your deinstallation is included in the Disk1/stage/Response directory on UNIX, or in the Disk1\stage\Response directory on Windows.

Perform the following steps to deinstall your Oracle Identity Management Oracle Home using the graphical, screen-based deinstaller:

1. Verify your Oracle Identity Management Oracle Home is not in use by an existing domain.

2. Stop all processes that use the Oracle Identity Management Oracle Home.

3. Open a command prompt and move (cd) into the IDM_ORACLE_HOME/oui/bin directory (UNIX) or the IDM_ORACLE_HOME\oui\bin directory (Windows).

4. Invoke the Deinstaller from command line using the -deinstall option. For example:
On UNIX:

./runInstaller -deinstall

On Windows:

setup.exe -deinstall

The Welcome screen appears.

5. Click Next.

- If you are deinstalling Oracle Internet Directory, Oracle Virtual Directory, Oracle Directory Services Manager, Oracle Directory Integration Platform, or Oracle Identity Federation, the Select Deinstallation Type screen appears.
Select the deinstallation type you want to perform. Table C-1 lists and describes each of the deinstallation types:

Table C-1 Deinstallation Types

Type

Description

Deinstall Oracle Home

Select this option to deinstall the binaries contained in the listed Oracle Identity Management Oracle Home.

If you select this option, the Deinstall Oracle Home screen appears next, where you can save a response file that contains the deinstallation settings before deinstalling.

Deinstall ASInstances managed by WebLogic Domain - Applicable to Oracle Internet Directory and Oracle Virtual Directory only.

Select this option to deinstall the Oracle Identity Management system component instances, such as Oracle Internet Directory and Oracle Virtual Directory, that are registered in a WebLogic domain.

If you select this option, the Specify WebLogic Domain Detail screen appears next where you identify the administration domain containing the system components you want to deinstall. The Select Managed Instance screen appears next, where you identify the instances you want to deinstall.

Note: When de-installing managed instances, ensure that the Administration server is up and running.

DeInstall Unmanaged ASInstances - Applicable to Oracle Internet Directory and Oracle Virtual Directory only.

Select this option to deinstall the Oracle Identity Management system component instances, such as Oracle Internet Directory and Oracle Virtual Directory, that are not registered in a WebLogic domain.

If you select this option, the Specify Instance Location screen appears next where you identify the instances you want to deinstall.

Regardless of the option you choose and the subsequent screens that appear, you will arrive at the Deinstall Progress screen, which shows the progress and status of the deinstallation. If you want to quit before the deinstallation is completed, click Cancel.

Click Finish after the deinstallation progresses to 100%. The Deinstallation Complete screen appears.

6. Click Finish on the Deinstallation Complete screen to exit the deinstaller.

C.1.2 Deinstalling the Oracle Common Home

The ORACLE_COMMON_HOME directory located in the MW_HOME directory contains the binary and library files required for Oracle Enterprise Manager Fusion Middleware Control and Oracle Java Required Files (JRF). Before you deinstall the ORACLE_COMMON_HOME directory, ensure that no other Oracle Fusion Middleware software, such as Oracle SOA Suite, depends on ORACLE_COMMON_HOME. You cannot deinstall the ORACLE_COMMON_HOME directory until all software that depends on it has been deinstalled.

Perform the following steps to deinstall the ORACLE_COMMON_HOME directory:

1. Stop all processes that use the ORACLE_COMMON_HOME directory. To know all the processes that are using ORACLE_COMMON_HOME directory use the following commands:
On UNIX:

ps-ef grep <oracle_common>

On Windows:

Use the Windows Task Manager to identify the processes that use the ORACLE_COMMON_HOME directory.

2. Deinstall your Oracle Identity Management Oracle Home by performing the steps in Deinstalling the Oracle Identity Management Oracle Home.

3. Open a command prompt and move (cd) into the ORACLE_COMMON_HOME/oui/bin/ directory (on UNIX) or the ORACLE_COMMON_HOME\oui\bin\ directory (on Windows).

4. Invoke the Deinstaller from command line using the -deinstall option and the -jreLoc option, which identifies the location where Java Runtime Environment (JRE) is installed. For example:
On UNIX:

./runInstaller -deinstall -jreLoc FULL_PATH_TO_JRE_DIRECTORY

On Windows:

setup.exe -deinstall -jreLoc FULL_PATH_TO_JRE_DIRECTORY

The Welcome screen appears.

5. Click Next. The Select Deinstallation Type screen appears.

6. Select the Deinstall Oracle Home option at the top of the Select Deinstallation Type screen.

Note:

The path to the ORACLE_COMMON_HOME directory appears in the text describing the Deinstall Oracle Home option.

Click Next. The Deinstall Oracle Home screen appears.

7. Confirm the correct ORACLE_COMMON_HOME directory is listed and click Deinstall.
The Deinstallation Progress screen appears, along with a Warning dialog box prompting you to confirm that you want to deinstall the ORACLE_COMMON_HOME directory.

8. Click Yes on the Warning dialog box to confirm you want to remove the ORACLE_COMMON_HOME directory. The deinstallation begins.

9. Click Finish after the deinstallation progresses to 100%. The Deinstallation Complete screen appears.

10. Click Finish on the Deinstallation Complete screen to exit the deinstaller.

C.1.3 Deinstalling Applications Registered with Oracle Single Sign-On 10g Release 10.1.4.3.0

To deinstall a partner application registered with Oracle Single Sign-On 10g Release 10.1.4.3.0, you must manually deregister the partner application from Oracle Single Sign-On. Refer to the "Reregister mod_osso on the single sign-on middle tiers" section in Chapter 9 of the Oracle Application Server Single Sign-On Administrator's Guide 10g Release 10.1.4.0.1 available at:

http://www.oracle.com/technology/documentation/oim1014.html

C.2 Reinstalling Oracle Identity Management

Perform the following steps to reinstall Oracle Identity Management:

1. Verify the directory you want to reinstall Oracle Identity Management into does not contain an existing Oracle Identity Management instance. If it does, you must deinstall it before reinstalling. You cannot reinstall Oracle Identity Management 11g Release1(11.1.1) in a directory that contains an existing Oracle Identity Management instance.

2. Reinstall Oracle Identity Management as if it was the first installation by performing the steps in the appropriate procedure in this guide.

D Performing Silent Installations

This appendix describes how to install Oracle Identity Management in silent mode. This appendix contains the following topics:

- What is a Silent Installation?

- Before Performing a Silent Installation

- Creating Response Files

- Performing a Silent Installation

- Installer Command Line Parameters

D.1 What is a Silent Installation?

A silent installation eliminates the need to monitor the Oracle Identity Management installation because no graphical output is displayed and no input by the user is required.

To perform a silent Oracle Identity Management installation, you invoke the Installer with the -silent flag and provide a response file from the command line. The response file is a text file containing variables and parameter values which provide answers to the Installer prompts.

D.2 Before Performing a Silent Installation

This topic describes tasks that may be required before you perform a silent installation. This topic includes the following sections:

- UNIX Systems: Creating the oraInst.loc File

- Windows Systems: Creating the Registry Key

D.2.1 UNIX Systems: Creating the oraInst.loc File

The Installer uses the Oracle inventory directory to keep track of all Oracle products installed on the systems. The inventory directory is stored in a file named oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation.

Perform the following steps to create the oraInst.loc file if it does not exist:

1. Log in as the root user.

2. Using a text editor such as vi or emacs, create the oraInst.loc file in any directory. The contents of the file consist of the following two lines:

inventory_loc=oui_inventory_directory
inst_group=oui_install_group

Replace oui_inventory_directory with the full path to the directory where you want the Installer to create the inventory directory. Replace oui_install_group with the name of the group whose members have write permissions to this directory.

3. Exit from the root user.

Note:

After you performing the silent installation on UNIX platforms, you must run the ORACLE_HOME/root.sh script as the root user. The root.sh script detects settings of environment variables and enables you to enter the full path of the local bin directory.

D.2.2 Windows Systems: Creating the Registry Key

If you have not installed Oracle Identity Management on your system, you must create the following Registry key and value:

HKEY_LOCAL_MACHINE / SOFTWARE / Oracle / inst_loc = [inventory_directory]

Replace inventory_directory with the full path to your Installer files. For example: C:\Program Files\Oracle\Inventory

D.3 Creating Response Files

Before performing a silent installation, you must provide information specific to your installation in a response file. Response files are text files that you can create or edit in a text editor. The Installer will fail if you attempt a silent installation using a response file that is not configured correctly.

Several default response files, which you can use as templates and customize for your environment, are included in the installation media. These default response files are located in the Disk1/stage/Response directory on UNIX, or in the Disk1\stage\Response directory on Windows.

Creating Response Files for Oracle Identity Management Software Installation

When you use the Oracle Identity Management Installation Wizard to install the software for the first time, you can save a summary of your installation in a response file.

To create a response file for Oracle Identity Management software Installer for Oracle Internet Directory, Oracle Virtual Directory, Oracle Directory Service Manager, Oracle Directory Integration Platform, and Oracle Identity Federation, complete the following steps:

1. On the Installation Summary screen in the installation wizard, click Save in the Save Response File field.

2. When prompted, save the file to a local directory.

D.3.1 OID, OVD, ODSM, ODIP, and OIF

The following is a list of the default response files included in the installation media for the Oracle Identity Management Suite containing Oracle Internet Directory (OID), Oracle Virtual Directory (OVD), Oracle Directory Services Manager (ODSM), Oracle Directory Integration Platform (ODIP), and Oracle Identity Federation (OIF):

- im_install_only.rsp: Use this response file to install Oracle Identity Management components without configuring them.

- im_install_config.rsp: Use this response file to install and configure Oracle Identity Management components.

- im_config_only.rsp: Use this response file with the Oracle Identity Management 11g Release 1 (11.1.1) Configuration Wizard (config.sh script or config.bat) in ORACLE_HOME/bin/ to configure installed components.

D.3.2 Securing Your Silent Installation

Your response files contain certain passwords required by the Installer. To minimize security issues regarding these passwords in the response file, follow these guidelines:

- Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.

- If possible, remove the response files from the system after the silent installation is completed.

D.4 Performing a Silent Installation

To perform a silent Oracle Identity Management installation, you invoke the Installer with the -silent flag and provide a response file from the command line.

On UNIX

The following is the syntax for running the Installer from the command line on UNIX systems:

runInstaller [-mode] [-options] [(COMMAND_LINE_VARIABLE=VARIABLE_VALUE)*]

For example:

./runInstaller -silent -response FILE

On Windows

The following is the syntax for running the Installer from the command line on Windows systems:

setup.exe [-mode] [-options] [(COMMAND_LINE_VARIABLE=VARIABLE_VALUE)*]

For example:

setup.exe -silent -response FILE

D.5 Installer Command Line Parameters

Table (UNKNOWN STEP NUMBER) lists and describes supported Installer command line parameters:

Table D-1 Installer Command Line Parameters

Parameter

Description

Installation Modes - Only One Mode Can be Specified

-i | -install

Launches the Installer in GUI mode. This is the default mode and is used if no mode is specified on the command line.

-silent

Install in silent mode. The Installer must be passed either a response file or command line variable value pairs.

-d | -deinstall

Launches the Installer in GUI mode for deinstallation.

-p | -prerequisite

Launches the Installer in GUI mode but only checks the prerequisites. No software is installed.

-v | -validate

Launches the Installer in GUI mode and performs all prerequisite and validation checking, but does not install any software.

-sv | -silentvalidate

Performs all prerequisite and validation checking in silent mode. You must pass the Installer either a response file or a series of command line variable value pairs.

Installation Options

-help | --help | --usage

Displays the usage parameters for the runInstaller command.

-invPtrLoc file

Pointer to the inventory location file. Replace file with the full path and name of the oraInst.loc file.

-response file | -responseFile file

Pointer to the response file. Replace file with the full path and name of the response file.

-jreLoc location

Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where your JRE is installed.

-logLevel level

Specify the level of logging performed by the Installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:

- severe

- warning

- info

- config

- fine

- finer

- finest

-debug

Obtain debug information from the Installer.

-force

Allow the silent installation to proceed in a non-empty directory.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage. This command causes the timeTakentimestamp.log file to be created.

-waitforcompletion

Windows only - the Installer will wait for completion instead of spawning the Java engine and exiting.

-noconsole

Messages will not be displayed to the console window.

-ignoreSysPrereqs

Ignore the results of the system prerequisite checks and continue with the installation.

-executeSysPrereqs

Execute the system prerequisite checks only, then exit.

-paramFile file

Specify the full path to the oraparam.ini file. This file is the initialization file for the Installer. The default location of this file is Disk1/install/platform.

-novalidation

Disables all validation checking performed by the Installer.

-nodefaultinput

For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated.

Command Line Variables

Installer Variables

Installer variables are specified using varName=value. For example:

ORACLE_HOME=/scratch/install/IDM_Home

Session Variables

Session variables are specified using session:varName=value

E Troubleshooting the Installation

This appendix describes solutions to common problems that you might encounter when installing Oracle Identity Management. It contains the following topics:

- General Troubleshooting Tips

- Installation Log Files

- Configuring OIM Against an Existing OIM 11g Schema

- Need More Help?

E.1 General Troubleshooting Tips

If you encounter an error during installation:

- Consult the Oracle Fusion Middleware 11g Release 1 (11.1.1). You can access the Release Notes on the Oracle Technology Network (OTN) Documentation Web site. To access this Web site, go to the following URL:

http://www.oracle.com/technetwork/indexes/documentation/index.html

- Verify your system and configuration is certified. See Reviewing System Requirements and Certification for more information.

- Verify your system meets the minimum system requirements. See Reviewing System Requirements and Certification for more information.

- Verify you have satisfied the dependencies for the deployment you are attempting. Each deployment documented in this guide contains a "Dependencies" section.

- If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

- If an error occurred while the Installer is copying or linking files:

1. Note the error and review the installation log files.

2. Remove the failed installation. See "Deinstalling Oracle Identity Management" for more information.

3. Correct the issue that caused the error.

4. Restart the installation.

- If an error occurred while configuring Oracle Identity Manager using the Oracle Identity Manager Configuration Wizard:

1. Note the error and review the configuration log files.

2. Verify whether the dependencies are met. For example, Administration Server and Database should be up and running.

3. Correct the issue that caused the error.

4. Restart the Oracle Identity Manager Configuration Wizard.

E.2 Installation Log Files

The Installer writes log files to the ORACLE_INVENTORY_LOCATION/logs directory on UNIX systems and to the ORACLE_INVENTORY_LOCATION\logs directory on Windows systems.

On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file.

On Microsoft Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The server log files are created in the <DOMAIN_HOME>/server/<servername/logs directory.

The following install log files are written to the log directory:

- installDATE-TIME_STAMP.log

- installDATE-TIME_STAMP.out

- installActionsDATE-TIME_STAMP.log

- installProfileDATE-TIME_STAMP.log

- oraInstallDATE-TIME_STAMP.err

- oraInstallDATE-TIME_STAMP.log

E.3 Configuring OIM Against an Existing OIM 11g Schema

In this scenario, you have created and loaded the appropriate Oracle Identity Manager (OIM) schema, installed and configured Oracle Identity Manager in a new or existing WebLogic domain. During domain configuration, you have configured JDBC Component Schemas by using the Oracle Fusion Middleware Configuration Wizard.

If you want to configure Oracle Identity Manager in a second WebLogic domain against the existing Oracle Identity Manager 11g schemas, you must complete the following steps when you try to configure Oracle Identity Manager using the Oracle Identity Manager Configuration Wizard:

1. When prompted, you must copy the .xldatabasekey file from the first WebLogic domain directory (/<MW_HOME>/user_projects/domains/<name_of_your_first_oim_domain>/config/fmwconfig/) to the second WebLogic domain directory (/<MW_HOME>/user_projects/domains/<name_of_your_second_oim_domain>/config/fmwconfig/). Proceed with the Oracle Identity Manager configuration.

2. After configuring Oracle Identity Manager using the Oracle Identity Manager Configuration Wizard, copy the cwallet.so, default_keystore.jks, and xlserver.crt files from the first WebLogic domain directory (/<MW_HOME>/user_projects/domains/<name_of_your_first_oim_domain>/config/fmwconfig/) to the second domain Home directory (/<MW_HOME>/user_projects/domains/<name_of_your_second_oim_domain>/config/fmwconfig/).

3. After copying the files, start the Oracle Identity Manager Managed Server, as described in Starting the Stack.

E.4 Need More Help?

If you cannot solve a problem using the information in this appendix, look for additional information in My Oracle Support at

http://support.oracle.com.

If you cannot find a solution to your problem, open a service request.

F Software Deinstallation Screens

This appendix describes the screens of the Oracle Fusion Middleware 11g Deinstallation Wizard that enables you to remove the Oracle Identity Management software from your machine. This appendix contains the following topics:

- Welcome

- Select Deinstallation Type

- Deinstallation Progress

- Deinstallation Complete

F.1 Welcome

The Welcome screen is the first screen that appears when you start the Oracle Fusion Middleware 11g Deinstallation Wizard.

Figure F-1 Welcome Screen

Click Next to continue.

F.2 Select Deinstallation Type

Select the type of deinstallation you want to perform.

Figure F-2 Select Deinstallation Type Screen

Table F-1 Deinstallation Types

Type

Description

Deinstall Oracle Home

Select this option to deinstall the binaries contained in the listed Oracle Identity Management Oracle Home.

If you select this option, the Deinstall Oracle Home screen appears next, where you can save a response file that contains the deinstallation settings before deinstalling.

Deinstall ASInstances managed by WebLogic Domain - Applicable to Oracle Internet Directory and Oracle Virtual Directory only.

Select this option to deinstall the Oracle Identity Management system component instances, such as Oracle Internet Directory and Oracle Virtual Directory, that are registered in a WebLogic domain.

If you select this option, the Specify WebLogic Domain Detail screen appears next where you identify the administration domain containing the system components you want to deinstall. The Select Managed Instance screen appears next, where you identify the instances you want to deinstall.

Deinstall Unmanaged ASInstances - Applicable to Oracle Internet Directory and Oracle Virtual Directory only.

Select this option to deinstall the Oracle Identity Management system component instances, such as Oracle Internet Directory and Oracle Virtual Directory, that are not registered in a WebLogic domain.

If you select this option, the Specify Instance Location screen appears next where you identify the instances you want to deinstall.

Click Next to continue.

F.2.1 Option 1: Deinstall Oracle Home

If you selected Deinstall Oracle Home on the Select Deinstallation Type screen, the following screen appears:

F.2.1.1 Deinstall Oracle Home

This screen shows the Oracle Home directory that is about to be deinstalled. It is the Oracle Home directory in which the deinstaller was started.

Figure F-3 Deinstall Oracle Home Screen

Verify that this is the correct directory, and also verify that there are no processes associated with this Oracle Home.

Click Deinstall to start the deinstallation process.

F.2.2 Option 2: Deinstall ASInstances managed by WebLogic Domain

If you selected Deinstall ASInstances managed by WebLogic Domain on the Select Deinstallation Type screen, the following screens appears:

- Specify WebLogic Domain Detail

- Select Managed Instance

- Deinstallation Summary (Managed Instance)

F.2.2.1 Specify WebLogic Domain Detail

Specify the WebLogic Domain credentials:

- Domain Host Name
The name of the system on which the WebLogic Domain is running.

- Domain Port No
Listen port number of the domain. The default port number is 7001.

- User Name
The WebLogic Domain user name.

- Password
The password of the WebLogic Domain user.

Figure F-4 Specify WebLogic Domain Detail Screen

Click Next to continue.

F.2.2.2 Select Managed Instance

Select the managed instance you want to deinstall.

Figure F-5 Select Managed Instance Screen

Click Next to continue.

F.2.2.3 Deinstallation Summary (Managed Instance)

Verify that the specified instance is the one you want to deinstall.

Figure F-6 Deinstallation Summary Screen

Click Deinstall to start the deinstallation process.

F.2.3 Option 3: Deinstall Unmanaged ASInstances

If you selected Deinstall Unmanaged ASInstances on the Select Deinstallation Type screen, the following screen appears:

- Specify Instance Location

- Deinstallation Summary (Unmanaged ASInstance)

F.2.3.1 Specify Instance Location

Specify the full path to your Oracle Instance directory. If you are unsure, click Browse to find this directory on your system.

Figure F-7 Specify Instance Location Screen

Click Next to continue.

F.2.3.2 Deinstallation Summary (Unmanaged ASInstance)

Verify that the specified instance is the one you want to deinstall.

Figure F-8 Deinstallation Summary Screen

Click Deinstall to start the deinstallation process.

F.3 Deinstallation Progress

This screen shows you the progress of the deinstallation.

Figure F-9 Deinstallation Progress Screen

If you want to quit before the deinstallation is completed, click Cancel.

F.4 Deinstallation Complete

This screen summarizes the deinstallation that was just completed.

Figure F-10 Deinstallation Complete Screen

Click Finish to dismiss the deinstaller.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.