Oracle Internet Directory Component Names Assigned by Oracle Identity Management Configuring Oracle Internet Directory on OIDHOST2 Ensure that the Oracle Internet

8-30 Oracle Fusion Middleware High Availability Guide 17. On the Installation Progress screen on UNIX systems, a dialog box appears that prompts you to run the oracleRoot.sh script. Open a window and run the script, following the prompts in the window. Click Next. 18. On the Configuration screen, multiple configuration assistants are launched in succession; this process can be lengthy. When it completes, click Next.

19. On the Installation Complete screen, click Finish to confirm your choice to exit.

8.3.3.2.2 Oracle Internet Directory Component Names Assigned by Oracle Identity Management

Installer When you perform an Oracle Internet Directory installation using Oracle Identity Management 11g installer, the default component name that the installer assigns to the Oracle Internet Directory instance is oid1. You cannot change this component name. The instance-specific configuration entry for this Oracle Internet Directory instance is cn=oid1, cn=osdldapd, cn=subconfigsubentry. If you perform a second Oracle Internet Directory installation on another computer and that Oracle Internet Directory instance uses the same database as the first instance, the installer detects the previously installed Oracle Internet Directory instance on the other computer using the same Oracle database, so it gives the second Oracle Internet Directory instance a component name of oid2. The instance-specific configuration entry for the second Oracle Internet Directory instance is cn=oid2, cn=osdldapd, cn=subconfigsubentry. Any change of properties in the entry cn=oid2, cn=osdldapd, cn=subconfigsubentry will not affect the first instance oid1. If a third Oracle Internet Directory installation is performed on another computer and that instance uses the same database as the first two instances, the installer gives the third Oracle Internet Directory instance a component name of oid3, and so on for additional instances on different hosts that use the same database. Note that the shared configuration for all Oracle Internet Directory instances is cn=dsaconfig, cn=configsets,cn=oracle internet directory. Any change in this entry will affect all the instances of Oracle Internet Directory. This naming scheme helps alleviate confusion when you view your domain using Oracle Enterprise Manager by giving different component names to your Oracle Internet Directory instances.

8.3.3.2.3 Configuring Oracle Internet Directory on OIDHOST2 Ensure that the Oracle Internet

Directory repository is running and then follow these steps to configure the Oracle Internet Directory instance on OIDHOST2: 1. Ensure that the system, patch, kernel and other requirements are met. These are listed in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management in the Oracle Fusion Middleware documentation library for the platform and version you are using. Note: The instructions in this section can also be used to scale out Oracle Internet Directory in your 11g Oracle Identity Management high availability configuration. Configuring High Availability for Identity Management Components 8-31 2. Ensure that Oracle Identity Management software has been installed and upgraded on OIDHOST2 as described in Section 8.3.3.1, Installing Oracle Fusion Middleware Components. 3. On OIDHOST1, ports 389 and 636 were used for Oracle Internet Directory. The same ports should be used for the Oracle Internet Directory instance on OIDHOST2. Therefore, ensure that ports 389 and 636 are not in use by any service on OIDHOST2 by issuing these commands for the operating system you are using. If a port is not in use, no output is returned from the command. On UNIX: netstat -an | grep LISTEN | grep :389 netstat -an | grep LISTEN | grep :636 On Windows: netstat -an | findstr LISTEN | findstr :389 netstat -an | findstr LISTEN | findstr :636 4. If the port is in use if the command returns output identifying the port, you must free the port. On UNIX: Remove the entries for ports 389 and 636 in the etcservices file and restart the services, or restart the computer. On Windows: Stop the component that is using the port. 5. Copy the staticports.ini file from the Disk1stageResponse directory to a temporary directory. 6. Edit the staticports.ini file you copied to the temporary directory to assign the following custom ports uncomment the lines where you specify the port numbers for Oracle Internet Directory: The Non-SSL port for OID Oracle Internet Directory Port No = 389 The SSL port for OID Oracle Internet Directory SSL Port No = 636 7. Start the Oracle Identity Management 11g Configuration Assistant under the ORACLE_HOMEbin directory as follows: On UNIX, issue this command: .config.sh On Windows, double-click config.exe

8. On the Welcome screen, click Next.