2 Preparing to Install Oracle Identity Management

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

It includes 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)

• 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 Oracle Identity Management 11g Release 1 (11.1.1.7.0), 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 jaccess-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 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.4.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.4.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.4.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.4.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 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.4.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.5 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.

  Note:

  For Oracle Internet Directory, you cannot get information about ports using WebLogic Server Administration Console.

• $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 Oracle Process Manager and Notification Server (OPMN).

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

This procedure applies to OID, OVD, ODSM, ODIP, and OIF only.

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 Starting the 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.7 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.8 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