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

Creating a Domain 4-9 Leave all other fields to their default values. Click Next. 19. In the Assign Servers to Machines screen, assign servers to machines as follows: ■ SOAHOST1: – AdminServer – WLS_WSM1 ■ SOAHOST2: – WLS_WSM2 Click Next. 20. In the Target Deployments to Clusters or Servers screen, make sure that the wsm-pm application and the oracle.wsm.seedpolicies library is targeted to the WSM-PM_Cluster only. Make sure that all other deployments are targeted to the AdminServer . Click Next.

21. In the Target Services to Clusters or Servers screen, select the following:

■ On the left, select WSM-PM_Cluster. On the right, select JDBC System Resource this automatically selects all the wsm datasources mds-owsm. ■ On the left, select Admin Server. On the right, select JDBC System Resource this automatically selects all the wsm datasources mds-owsm. All JDBC system resources should be targeted to both the Admin Server and WSM-PM_Cluster. ■ On the left, select WSM-PM_Cluster. On the right, select JOC-Shutdown, and JOC-Startup . ■ On the left, select Admin Server. On the right, deselect JOC-Shutdown and JOC-Startup . Make sure these services are not targeted to the Admin Server. JOC-Shutdown , and JOC-Startup should be targeted only to the WSM-PM_ Cluster . ■ Make sure that all the remaining services are targeted to the Admin Server. ■ Click Next. 22. In the Configuration Summary screen, click Create. 23. In the Create Domain screen, click Done.

4.5 Creating boot.properties for the Administration Server on SOAHOST1

Create a boot.properties file for the Administration Server on SOAHOST1. The boot.properties file enables the Administration Server to start without prompting you for the administrator username and password. Table 4–3 Machines Name Node Manager Listen Address SOAHOST1 SOAHOST1 SOAHOST2 SOAHOST2 4-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter For the Administration Server: 1. Create the following directory structure: mkdir -p ORACLE_BASEadmindomain_nameaserverdomain_ name serversAdminServersecurity 2. In a text editor, create a file called boot.properties in the last directory created in the previous step, and enter the following lines in the file: username=adminuser password=password

4.6 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 Note: When you start the Administration Server, the username and password entries in the file get encrypted. You start the Administration Server in Section 4.7, 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. Note: It is important that you set -DDomainRegistrationEnabled=true whenever a Node Manager is started that must manage the AdminServer. This is due to the fact that the AdminServer domain home does not exist in the NodeManager Domains file and you must use dynamic registration of the domain. Oracle does not recommend using this parameter except in the case specified here. If there is no AdminServer on this machine and this machine is not an AdminServer failover node, you should start the Node Manager as: SOAHOST1 .startNodeManager.sh Creating a Domain 4-11

4.7 Starting the Administration Server on SOAHOST1