This chapter provides information you should review before installing Oracle Identity Management components. It includes the following topics:
Installing and Configuring Java Access Bridge (Windows Only)
Installing Oracle WebLogic Server and Creating the Oracle Middleware Home
Creating Database Schema Using the Repository Creation Utility (RCU)
Before performing any installation, read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the components you are installing. Both of these documents are available on Oracle Technology Network (OTN).
Oracle Fusion Middleware System Requirements, Prerequisites, and Specifications
The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:
http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm
Note:
The system requirements document also covers Oracle Universal Installer Startup Requirements.Oracle Fusion Middleware Supported System Configurations
The certification document covers supported installation types, platforms, operating systems, databases, JDKs, and third-party products:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
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:
Download Java Access Bridge from the following Web site:
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.
Before you can install Oracle Identity Management 11g Release 1 (11.1.1) components, you must install Oracle WebLogic Server and create the Oracle Middleware Home directory.
Note:
If you are installing Oracle Internet Directory 11g Release 1 (11.1.1) without an Oracle WebLogic administration domain, you do not need to install Oracle WebLogic.Perform the following steps to install Oracle WebLogic Server and create the Oracle Middleware Home directory. You can refer to the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for complete information about installing Oracle WebLogic Server.
Insert the Oracle WebLogic Server CD-ROM or download the Oracle WebLogic Server Installer from the following Web site:
http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
Locate the appropriate executable file for your system, such as:
wls1032_linux32.bin for 32-bit Linux systems
wls1032_win32.exe for 32-bit Windows systems
wls1032_generic.jar for all 64-bit platforms
The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Run the Oracle WebLogic Server Installer directly from the CD-ROM, or copy the file to your local system and run it locally. For 64-bit installations:
Before running the installer, set the DISPLAY environment variable on your system.
Replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.
Use the -d64 flag when using 32/64-bit hybrid JDK's (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).
Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOME refers to a 64-bit JDK.
Examples for 32-bit systems:
Linux:
./wls1032_linux32.bin
Windows:
wls1032_win32.exe
Examples for 64-bit systems:
UNIX:
JAVA_HOME/bin/java -jar wls1032_generic.jar
or
JAVA_HOME/bin/java -d64 -jar wls1032_generic.jar
Windows:
JAVA_HOME\bin\java -jar wls1032_generic.jar
Note:
After you start the Oracle WebLogic Server Installer, the Welcome screen appears.Click Next. The Choose Middleware Home Directory screen appears.
Select Create a new Middleware Home and identify the desired location for your new Middleware Home directory, which is the top-level directory for all Oracle Fusion Middleware products. The WebLogic Home directory will be created inside the Middleware Home directory.
Note:
If the Middleware Home directory already exists on your system, it must be an empty directory.Click Next. The Register for Security Updates screen appears.
Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing.
Click Next. The Choose Install Type screen appears.
Select Typical and click Next. The Choose Product Installation Directories screen appears.
Specify the desired location for your WebLogic Server Home directory and click Next.
If you are installing Oracle WebLogic Server on a UNIX system, the Installation Summary screen appears. Go to step 9 now.
If you are installing Oracle WebLogic Server on a Windows system, the Choose Shortcut Location screen appears. Specify a location where you want Windows to create a shortcut to Oracle products and click Next. The Installation Summary screen appears.
Click Next on the Installation Summary screen.
The Installation Progress screen appears.
Click Next. The Installation Complete screen appears.
De-select Run Quickstart and click Done to exit the Installer.
Notes:
The same user that 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.
For Oracle Identity Management Installations that require Oracle WebLogic Server, you must perform the following steps after installing Oracle WebLogic Server and before installing Oracle Identity Management:
Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process.
Determine if the nodemanager.properties file is present in the WL_HOME/common/nodemanager/ directory.
If the nodemanager.properties file is not present, continue installing Oracle Identity Management.
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
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 the latest information about supported databases, visit the following Web site:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
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 Repository Creation Utility (RCU), which is used to create the schemas that Oracle Identity Management components require. For information about RCU requirements, refer to the system requirements document at the following Web site:
http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm
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 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/technology/index.html
Note:
RCU is available only on Linux and Windows platforms. 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 formPREFIX_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.This topic describes optional environment-specific tasks you may want to perform before installing Oracle Identity Management 11g Release 1 (11.1.1). This topic includes the following sections:
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.
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.
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
Install a loopback adapter on the DHCP server, which assigns a local IP address to your system.
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
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.