2 Preparing to Install

This chapter provides information you should review before installing Oracle Identity and Access Management 11g Release 1 (

This chapter discusses the following topics:

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 Installing and Configuring Java Access Bridge (Windows Only)

If you are installing Oracle Identity and Access Management on a Windows operating 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 URL:

  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.3 Identifying Installation Directories

This topic describes directories you must identify in most Oracle Identity and Access 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:

2.3.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 Oracle Middleware Home directory is commonly referred to as MW_HOME.

2.3.2 Oracle Home Directory

Enter a name for the Oracle Home directory of the component. 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 required to host the component, such as binaries and libraries, in the Oracle Home directory. The Oracle Home directory is commonly referred to as ORACLE_HOME.


Avoid using spaces in the directory names, including Oracle Home. Spaces in such directory names are not supported.

2.3.3 Oracle Common Directory

The Installer creates this directory under the location you enter in the Oracle Middleware Home Location field.

The Installer installs the Oracle Java Required Files (JRF) required to host the components, in the Oracle Common directory. There can be only one Oracle Common Home within each Oracle Middleware Home. The Oracle Common directory is commonly referred to as oracle_common.

2.3.4 Oracle WebLogic Domain Directory

A WebLogic 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. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Java components, such as Web applications, EJBs, and Web services, and other resources to the Managed Servers and use the Administration Server for configuration and management purposes only.

Managed Servers in a domain can be grouped together into a cluster.

The directory structure of a domain is separate from the directory structure of the WebLogic Server home. It can reside anywhere; it need not be within the Middleware home directory. A domain is a peer of an Oracle instance.

The Oracle Fusion Middleware Configuration Wizard creates a domain in a directory named user_projects under your Middleware Home (MW_HOME).

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

2.4 Determining Port Numbers

If you want to install an Oracle Identity and Access Management 11g Release 1 (11.1.1) component against an existing Oracle Identity and Access 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 Identity Manager 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 Identity Manager.

2.5 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

2.6 Optional: Updating the WebLogic Administrator Server User Name in Oracle Enterprise Manager Fusion Middleware Control (OIM Only)

Read this section only if the user name for the WebLogic Administrator for the domain is not weblogic. This task is required only if you are using Oracle Identity Manager.

If your WebLogic administrator user name is not weblogic, complete the following steps:

  1. Ensure that the Oracle Identity Manager Managed server is up and running.

  2. Log in to Oracle Enterprise Manager Fusion Middleware Control using your WebLogic Server administrator credentials.

  3. Click Identity and Access > oim > oim( Right-click and select System MBean Browser. The System MBean Browser page is displayed.

  4. Under Application Defined MBeans, select oracle.iam > Server:oim_server1 > Application: oim > XMLConfig > config > >XMLConfig.SOAConfig > SOAConfig.

  5. View the attribute username. By default, the value of the attribute is weblogic. Change this value to your WebLogic administrator user name.

  6. Click Apply. Exit Oracle Enterprise Manager Fusion Middleware Control.

  7. On the command line, use the cd command to move from your present working directory to the IAM_Home/common/bin directory. IAM_Home is the example IDM_Home directory for Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator.

  8. Launch the WebLogic Scripting Tool (WLST) interface as follows:

    On UNIX: Run ./wlst.sh on the command line.

    On Windows: Run wlst.cmd.

    At the WLST command prompt (wls:/offline>), type the following:


    You are prompted to enter the WebLogic Administration Server user name, password, and URL. For more information about using the WLST interface, see the topic "Using the WebLogic Scripting Tool" in the guide Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

    1. Run the deleteCred WLST command:

      deleteCred(map="oim", key="SOAAdminPassword");

    2. Run the createCred WLST command, and replace the ADMIN_PASSWORD with your WebLogic administrator password:

      createCred(map="oim", key="SOAAdminPassword", user="xelsysadm",password="<ADMIN_PASSWORD>");

    3. Run the following WLST command to verify the values:

      listCred(map="oim", key="SOAAdminPassword");

    4. Type exit() to exit the WLST command shell.

  9. Open the Oracle Identity Manager Administration Console, and log in as user xelsysadm.

  10. Create a new user for the user name of your WebLogic administrator.

  11. Search for the Administrators role. Open the role details, and click the Members tab.

  12. Remove all the existing members of the Administrators role.

  13. Add the newly created user (the one with your WebLogic administrator user name) as a member of the Administrators role.

  14. Restart Oracle Identity Manager Managed Server, as described in Starting the Stack.