Creating boot.properties for the WebLogic Administration Server on IDMHOST1 Starting Node Manager on IDMHOST1 Updating the Node Manager Credentials

Creating the WebLogic Server Domain for Identity Management 6-5 ■ Node manager listen address : localhost Leave all other fields to their default values.

14. Click Next.

15. On the Assign Servers to Machines screen, assign servers to machines as follows: ■ ADMINHOST : AdminServer Click Next. 16. On the Configuration Summary screen, validate that your choices are correct, then click Create.

17. On the Create Domain screen, click Done.

6.3 Creating boot.properties for the WebLogic Administration Server on IDMHOST1

Create a boot.properties file for the Administration Server on IDMHOST1. If the file already exists, edit it. The boot.properties file enables the Administration Server to start without prompting you for the administrator username and password. For the Administration Server: 1. Create the following directory structure. mkdir -p ORACLE_ BASE adminIDMDomainaserverIDMDomainserversAdminServersecurity 2. In a text editor, create a file called boot.properties in the last directory created in the previous step, and enter the username and password in the file. For example: username=weblogic password=password for weblogic user

6.4 Starting Node Manager on IDMHOST1

Perform these steps to start Node Manager on IDMHOST1: 1. Run the startNodeManager.sh script located under the ORACLE_ BASE productfmwwlserver_10.3serverbin directory. 2. Run the setNMProps.sh script on IDMHOST1 to set the StartScriptEnabled property to true: cd MW_HOMEoracle_commoncommonbin .setNMProps.sh Note: The username and password entries in the file are not encrypted until you start the Administration Server, as described in Section 6.5, Updating the Node Manager Credentials. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible so that the entries are encrypted. 6-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 3. Stop the Node Manager by killing the Node Manager process, or stop the service in Windows. 4. Start Node Manager for the Administration Server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

6.5 Updating the Node Manager Credentials

You start the Administration server by using wlst and connecting to Node Manager. The first start of the Administration Server with Node Manager, however, requires that you change the default username and password that the Configuration Wizard sets for Node Manager. Therefore you must use the start script for the Administration Server for the first start. Follow these steps to start the Administration Server using Node Manager. Steps 1-4 are required for the first start operation, but subsequent starts require only Step 4. 1. Start the Administration Server using the start script in the domain directory. IDMHOST1 cd ORACLE_BASEadmindomain_nameaserverdomain_namebin IDMHOST1 .startWebLogic.sh 2. Use the Administration Console to update the Node Manager credentials. a. In a browser, go to http:ADMINVHN.mycompany.com:7001console. b. Log in as the administrator.

c. Click Lock and Edit.