Creating boot.properties for the Administration Server on SOAHOST1 Starting Node Manager on SOAHOST1 Starting the Administration Server on SOAHOST1

5-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite 8. In the Select Optional Configuration screen, select the following: ■ Administration Server ■ Managed Servers, Clusters and Machines Click Next. 9. In the Configure the Administration Server screen, enter the following values: ■ Name: AdminServer ■ Listen address: enter ADMINVHN. ■ Listen port: 7001 ■ SSL listen port: NA ■ SSL enabled: leave this check box unselected. Click Next. 10. In the Configure Managed Servers screen, click Next. 11. In the Configure Clusters screen, click Next. 12. In the Configure Machines screen, click the Unix Machine tab and then click Add to add the following machine: Leave all other fields to their default values. Please note that the machine name does not need to be a valid host name or listen address; it is just a unique identifier of a Node Manager location. Click Next. 13. In the Assign Servers to Machines screen, assign servers to machines as follows: ■ ADMINVHN: – AdminServer Click Next. 14. In the Configuration Summary screen, click Create. 15. In the Create Domain screen, click Done.

5.3 Creating boot.properties for the Administration Server on SOAHOST1

Create a boot.properties file for the Administration Server on SOAHOST1. This file enables the Administration Server to start without prompting you for the administrator username and password.

1. Create the following directory structure:

mkdir -p ORACLE_BASEadmindomain_nameaserverdomain_nameserversAdminServer security Table 5–1 Machines Name Node Manager Listen Address ADMINVHN localhost Creating a Domain with Administration Server 5-5 2. In a text editor, create a file called boot.properties in the directory created in the previous step, and enter the following lines in the file: username=Admin_Username password=Password 3. Save the file and close the editor.

5.4 Starting Node Manager on SOAHOST1

Perform these steps to start Node Manager on SOAHOST1: 1. Run the setNMProps.sh script, which is located in the ORACLE_COMMON_ HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .setNMProps.sh 2. Start Node Manager: SOAHOST1 cd WL_HOMEserverbin SOAHOST1 export JAVA_OPTIONS=-DDomainRegistrationEnabled=true SOAHOST1 .startNodeManager.sh

5.5 Starting the Administration Server on SOAHOST1

The administration server will be started and stopped using Node Manager. However, the first start of the administration server with Node Manager requires changing the default username and password that the Oracle Fusion Middleware Configuration Wizard set for Node Manager. You must therefore use the start script for the administration server for the first start. Follow these steps to start the Administration Note: When you start the Administration Server, the username and password entries in the file get encrypted. You start the Administration Server in Section 5.5, Starting the Administration Server on SOAHOST1. For security reasons, you want to 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. Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 12.8.3, Incomplete Policy Migration After Failed Restart of SOA Server. Note: It is important that the -DDomainRegistrationEnabled= true parameter is set whenever a Node Manager is started which must manage the Administration Server. If there is no Administration Server on the machine and the machine is not an Administration Server failover node, then Node Manager can be started using SOAHOST1 .startNodeManager.sh without the export command. 5-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite Server using Node Manager steps 1 through 4 are required for the first start; all 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. Open a Web browser and go to http:ADMINVHN:7001console. b. Log in as the administrator.

c. Click on domain_name, then Security, then General, and then expand the