Starting the Administration Server on SOAHOST1 Click Lock and Edit. Click domain_name, Security, General, and then expand the Advanced Validating the Administration Server

Creating a Domain 4-11

4.7 Starting the Administration Server on SOAHOST1

The Administration Server is started and stopped using Node Manager. However, the first start of the Administration Server with Node Manager, requires changing the defaulted username and password that are set for Node Manager by the Configuration Wizard. Therefore, 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, subsequent starts require only step 4: 1. Start the Administration Server using the start script in the domain directory SOAHOST1 cd ORACLE_BASEadmindomain_nameaserverdomain_namebin SOAHOST1 .startWebLogic.sh 2. Use the Administration Console to update the Node Manager credentials. a. In a browser, go to the following URL; http:ADMINVHN:7001console b. Log in as the administrator.

c. Click Lock and Edit.

d. Click domain_name, Security, General, and then expand the Advanced

options 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 Administration Server process by using CTRL-C in the shell where it was

started, or by process identification and kill in the OS.

4. Start WLST and connect to Node Manager with nmconnect and the credentials set

in the previous steps and start the Administration Server using nmstart. SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .wlst.sh Once you are in the WLST shell: wls:offlinenmConnectAdmin_User,Admin_Password, SOAHOST1,5556,domain_name,u01apporacleadmindomain_ name aserverdomain_name wls:nmdomain_name nmStartAdminServer

4.8 Validating the Administration Server

Perform these steps to ensure that the Administration Server is properly configured: 1. In a browser, go to http:ADMINVHN:7001console. Note: This username and password are used only to authenticate connections between Node Manager and clients. They are independent of the server admin ID and password and are stored in the ORACLE_BASEadmindomain_nameaserverdomain_ nameconfignodemanagernm_password.properties file. 4-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 2. Log in as the administrator. 3. Verify that the WLS_WSM1 and WLS_WSM2 managed servers are listed. 4. Verify that the WSM-PM_Cluster cluster is listed. 5. Check that you can access Oracle Enterprise Manager at http:ADMINVHN:7001em. 6. Log in to EM Console with the username and password you specified in Section 4.5, Creating boot.properties for the Administration Server on SOAHOST1. 4.9 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server Use the pack and unpack commands to separate the domain directory used by the Administration Server from the domain directory used by the managed server in SOAHOST1as recommended in Chapter 2, Database and Environment Preconfiguration. 1. Run the pack command on SOAHOST1 to create a template pack as follows: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmindomain_ name aserverdomain_name -template=soadomaintemplate.jar -template_name=soa_ domain_template 2. Run the unpack command on SOAHOST1 to unpack the template in the managed server domain directory as follows: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_name -template=soadomaintemplate.jar -app_dir=ORACLE_BASEadmindomain_ name mserverapplications

4.10 Applying the Java Required Files JRF Template to the WSM-PM_ Cluster