On the Configuration Summary screen, click Create to begin the creation process.

8-136 Oracle Fusion Middleware High Availability Guide Click Next. 13. In the Configure Clusters screen, create a cluster by clicking Add. Enter name: OAM_Cluster Leave all other fields at the default settings. Click Next. 14. On the Assign Servers to Clusters screen, associate the managed servers with the cluster, as follows: ■ Click the cluster name OAM_Cluster in the right window. ■ Click the managed server WLS_OAM1, then click the arrow to assign it to the cluster. ■ Repeat for managed server WLS_OAM2. Click Next. 15. On the Configure Machines screen, create a machine for each host in the topology. Click the UNIX tab if your hosts use a UNIX-based operating system. Otherwise, click the Machines tab. Supply the following information: ■ Name : Name of the host. The best practice is to use the DNS name OAMHOST1 ■ Node Manager Listen Address : The DNS name of the machine OAMHOST1.mycompany.com ■ Node Manager Port : A port for Node Manager to use. Repeat the steps for OAMHOST2: ■ Name : Name of the host. The best practice is to use the DNS name OAMHOST2 ■ Node Manager Listen Address : The DNS name of the machine OAMHOST2.mycompany.com ■ Node Manager Port : A port for Node Manager to use. Click Next. 16. In the Assign Servers to Machines screen, indicate which managed servers will run on the machines just created. ■ Click the machine OAMHOST1 in the right window. ■ Click the managed server WLS_OAM1 in the left window. ■ Click the arrow to assign the managed server to the host OAMHOST1. ■ Click the machine OAMHOST2 in the right window. ■ Click the managed server WLS_OAM2 in the left window. ■ Click the arrow to assign the managed server to the host OAMHOST2. Click Next.

17. On the Configuration Summary screen, click Create to begin the creation process.

When prompted, on Linux and UNIX installations, execute the script oracleRoot.sh as the root user. Configuring High Availability for Identity Management Components 8-137

8.8.4.5 Creating boot.properties for the Administration Server on OAMHOST1

This section describes how to create a boot.properties file for the Administration Server on OAMHOST1. The boot.properties file enables the Administration Server to start without prompting for the administrator username and password. Follow these steps to create the boot.properties file:

1. On OAMHOST1, go the following directory:

MW_HOME user_projectsdomainsdomainNameserversAdminServersecurity For example: cd u01apporacleproductfmwuser_ projectsdomainsIDMDomainserversAdminServersecurity

2. Use a text editor to create a file called boot.properties under the security

directory. Enter the following lines in the file: username=adminUser password=adminUserPassword 3. Stop the Administration Server if it is running. See the Starting and Stopping Oracle Fusion Middleware chapter of the Oracle Fusion Middleware Administrators Guide for information on starting and stopping WebLogic Servers. 4. Start the Administration Server on OAMHOST1 using the startWebLogic.sh script located under the MW_HOMEuser_projectsdomainsdomainNamebin directory. 5. Validate that the changes were successful by opening a web browser and accessing the following pages: ■ WebLogic Server Administration Console at: http:oamhost1.mycompany.com:7001console ■ Oracle Enterprise Manager Fusion Middleware Control at: http:oamhost1.mycompany.com:7001em Log into these consoles using the weblogic user credentials. Note: You cannot run the config.sh script twice to make configuration changes. You must use another tool to make additional configuration changes such as using the MBeans Browser in Fusion Middleware Control Note: When you start the Administration Server, the username and password entries in the file get encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, you should start the server as soon as possible so that the entries get encrypted.