Click Lock and Edit. Click Domain_name-Security-General and expand Advanced at the Validating the WebLogic Administration Server Disabling Host Name Verification for the Oracle WebLogic Administration Server

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.

d. Click Domain_name-Security-General and expand Advanced at the

bottom. e. Enter a new username for Node Manager or make a note of the existing one and update the Node Manager password. f. Save and activate the changes. 3. Stop the WebLogic Administration Server by issuing the command stopWebLogic.sh located under the ORACLE_BASEadmindomain_ nameaserverdomain_namebin directory. 4. Start WLST and connect to the Node Manager with nmconnect and the credentials you just updated. Then start the WebLogic Administration Server using nmstart. IDMHOST1 cd ORACLE_COMMON_HOMEcommonbin IDMHOST1 .wlst.sh On Windows, the command is: wlst.cmd Once in the wlst shell, execute the following commands: wls:offline nmConnectAdmin_User,Admin_Pasword, IDMHOST1,5556, IDMDomain,u01apporacleadminIDMDomainaserverIDMDomain wls:nmdomain_name nmStartAdminServer Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. Creating the WebLogic Server Domain for Identity Management 6-7 where Admin_user and Admin_Password are the Node Manager username and password you entered in Step 2.

6.6 Validating the WebLogic Administration Server

Perform these steps to ensure that the Administration Server is properly configured: 1. In a browser, go to http:ADMINVHN.mycompany.com:7001console. 2. Log in as the WebLogic administrator, for example: weblogic. 3. Check that you can access Oracle Enterprise Manager Fusion Middleware Control at http:ADMINVHN.mycompany.com:7001em. 4. Log in to Oracle Enterprise Manager Fusion Middleware Control as the WebLogic administrator, for example: weblogic.

6.7 Disabling Host Name Verification for the Oracle WebLogic Administration Server

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server. See Chapter 16, Setting Up Node Manager. If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the EDG topology configuration is complete as described in Chapter 16, Setting Up Node Manager. Perform these steps to disable host name verification: 1. Go to the Oracle WebLogic Server Administration Console at: http:adminvhn.mycompany.com:7001console 2. Log in as the user weblogic, using the password you specified during the installation.

3. Click Lock and Edit.

4. Expand the Environment node in the Domain Structure window.

5. Click Servers. The Summary of Servers page appears.

6. Select AdminServeradmin in the Name column of the table. The Settings page

for AdminServeradmin appears.

7. Click the SSL tab.

8. Click Advanced.

9. Set Hostname Verification to None.

10. Click Save.

Note: Admin_user and Admin_Password are only used to authenticate connections between Node Manager and clients. They are independent from the server administration ID and password and are stored in the ORACLE_BASEadmindomain_ nameaserverdomain_nameconfignodemanagernm_ password.properties file. 6-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

11. Click Activate Changes.

6.8 Stopping and Starting the WebLogic Administration Server