| Oracle® Fusion Middleware Installation Guide for Oracle Identity Management 11g Release 1 (11.1.1) Part Number E12002-05 |
|
|
View PDF |
| Oracle® Fusion Middleware Installation Guide for Oracle Identity Management 11g Release 1 (11.1.1) Part Number E12002-05 |
|
|
View PDF |
This section discusses the following topics:
Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure"
Understanding Oracle WebLogic Server Administration Domain Options
Understanding the State of Oracle Identity Management Components After Installation
Table 2-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 2-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: |
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 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 and create a Middleware home. |
Oracle Identity Management requires a Middleware home directory. The Middleware home is created during the Oracle WebLogic Server 10.3.4 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 but do not configure Oracle Identity Management |
Use the installer to install Oracle Identity Management 11.1.1.2.0 Choose the Install Software - Do Not Configure option on the Select Installation Type Screen. |
See Installing OID, OVD, ODSM, ODIP, and OIF (11.1.1.4.0). For more information about the installation types, see Installation Types: "Install Software - Do Not Configure" vs. "Install and Configure". |
Mandatory |
|
Task 5 - Update your software. |
Run the Patch Set Installer to update your software to Oracle Identity Management 11.1.1.4.0. |
See "Applying the Latest Oracle Fusion Middleware Patch Set with the Patch Set Installers" in Oracle Fusion Middleware Patching Guide. |
Mandatory |
|
Task 6 - Configure Oracle Identity Management |
After patching, run the Configuration Tool to configure your Oracle Identity Management components. |
See the following topics in this guide:
|
Mandatory |
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:
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.4.0) Configuration Wizard. To start the Oracle Identity Management 11g Release 1 (11.1.1.4.0) Configuration Wizard, execute the ORACLE_HOME/bin/config.sh script (config.bat on Windows).
Important:
To install the latest Oracle Identity Management software, you must choose the Install Software - Do Not Configure installation type option, for Oracle Identity Management 11.1.1.2.0.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.
Note:
Do not choose the Install and Configure option for Oracle Identity Management 11.1.1.2.0, if you want to install the latest Oracle Identity Management software.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:
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.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.
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 (11.1.1.4.0) Configuration Wizard, the existing domain must have been created using the Oracle Identity Management 11g Release 1 (11.1.1.4.0) 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.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:
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.
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 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: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.
This topic provides information about the state of Oracle Identity Management components after installation, including:
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.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:Component-specific guides listed in the "Related Documents" section in this guide's Preface.
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 port: 6501
SSL port: 7501
Admin port: 8899
HTTP port: 8080
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
|
 Copyright © 2001, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
