|Oracle® Fusion Middleware Installation Guide for Oracle Identity Management
11g Release 1 (11.1.1)
Part Number E12002-05
This section discusses the following topics:
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:
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:
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:
Install Java Access Bridge.
access-1_4.jar from your installation location to the
JAWTAccessBridge.dll files from your installation location to the
accessibility.properties file to the
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:
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:
ps-ef | grep -i nodemanager
This will return the Process Id of the Node Manager Process.
kill -9 <Process Id of the Node Manager Process>
Use the Windows Task Manager to identify running Node Manager processes and kill the same.
Determine if the
nodemanager.properties file is present in the
nodemanager.properties file is not present, then follow the instructions below:
startNodeManager.sh (Located at
<WL_HOME>/server/bin directory) to start Node Manager.
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:
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:
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 Fusion Middleware 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:
Note:Ensure that the following database parameters are set:
'aq_tm_processes' >= 1
'db_cache_size' >= '150994944'
'shared_pool_size' >= '183500800'
If you are installing a new database, be sure to configure your database to use AL32UTF8 character set encoding. If your database does not use the AL32UTF8 character set, you will see the following warning when running RCU: "The database you are connecting is with non-AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the database character set." You can ignore this warning and continue using RCU.
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 Oracle Fusion Middleware 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.
If you are installing Oracle Internet Directory and your database is not configured as per the requirements in the fusion middleware requirements and prerequisites doc, you would see the following warnings: "Recommended value for Database initialization parameter processes is 500. Choose YES to continue or NO to go back to the same screen and specify different database details." To fix this one can click No and apply the requisite configuration mentioned in the fusion middleware requirements and prerequisites doc - section 8 Repository Creation Utility (RCU) Requirements which can be accessed from the following link:
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:
Note:RCU is available only on Linux x86 and Windows x86 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 form
_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 (188.8.131.52.0). This topic includes the following sections:
Note:If the environment variable
LD_ASSUME_KERNELis set, it needs to be unset.
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.
On UNIX systems:
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:
On Windows systems:
Install a loopback adapter on the DHCP host and assign it a non routable IP address.
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.