This chapter provides information you should review before installing Oracle Identity and Access Management 11g Release 1 (11.1.1.7.0) components.
This chapter discusses the following topics:
Section 2.1, "Reviewing System Requirements and Certification"
Section 2.2, "Installing and Configuring Java Access Bridge (Windows Only)"
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 the 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 and Access Management 11g Release 1 (11.1.1.7.0), refer to Oracle Fusion Middleware Interoperability and Compatibility Guide for Oracle Identity and Access Management.
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.
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:
Download Java Access Bridge from the following URL:
http://java.sun.com/javase/technologies/accessibility/accessbridge/
Install Java Access Bridge.
Copy access-bridge.jar and jaccess-1_4.jar from your installation location to the jre\lib\ext directory.
Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.
Copy the accessibility.properties file to the jre\lib directory.
This topic describes directories that you must identify in most of the Oracle Identity and Access Management installations and configurations.
The following are the common directories described in this section:
For more information about the common directories and basic concepts of Oracle Fusion Middleware and Oracle WebLogic Server, refer to "Understanding Oracle Fusion Middleware Concepts" in the Oracle Fusion Middleware Administrator's Guide.
Identify the location of your Oracle Middleware Home directory. The installer creates an Oracle Home directory for the component that 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.
Enter a name for the Oracle Home directory of the component. The installer uses the name that 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 variable.
Note:
Avoid using spaces in the directory names, including Oracle Home. Spaces in such directory names are not supported.
The installer creates this directory under the location that 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.
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).
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.
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.
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