Select Configure selected component schemas as RAC multi data source Click Next. Click Add. Click Next.

4-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 6. In the Specify Domain Name and Location screen, enter the domain name wcedg_domain. Make sure that the domain directory matches the directory and shared storage mount point recommended in Chapter 2, Database and Environment Preconfiguration : enter ORACLE_BASEadmindomain_nameaserver for the domain directory and ORACLE_BASEadmindomain_ nameaserverapplications for the application directory. This directory should be in shared storage.

7. Click Next.

8. In the Configure Administrator Username and Password screen, enter the username and password to be used for the domain’s administrator. Click Next. 9. In the Configure Server Start Mode and JDK screen, do the following: ■ For WebLogic Domain Startup Mode, select Production Mode. ■ For JDK Selection, select JROCKIT SDK1.6.0_version. Click Next. 10. In the Configure JDBC Components Schema screen, do the following: a. Select the OWSM MDS schema.

b. Select Configure selected component schemas as RAC multi data source

schemas in the next panel .

c. Click Next.

11. The Configure RAC Multi Data Sources Component Schema screen is displayed Figure 4–2 . Note: If multiple Oracle Homes are installed for example a WebCenter Home and a SOA Home, available products will show up for both homes. In this step, select only products from the WebCenter home wc. This is indicated by brackets at the end of the product name; for example, Oracle JRF - 11.1.1.0 [wc]. Creating a Domain 4-7 Figure 4–2 Configure RAC Multi Data Source Component Schema Screen In this screen, do the following: a. Enter values for the following fields, specifying the connect information for the Oracle RAC database that was seeded with RCU. – Driver: Select Oracle driver Thin for RAC Service-Instance connections, Versions:10, 11 . – Service Name: Enter the service name of the database, for example, wcedg.mycompany.com. – Username: Enter the complete user name including the prefix for the schemas. – Password: Enter the password to use to access the schemas. b. Enter the host name, instance name, and port.

c. Click Add.

d. Repeat this for each Oracle RAC instance.

e. Click Next.

12. In the Test JDBC Data Sources screen, the connections should be tested automatically. The Status column displays the results. Ensure that all connections were successful. If not, click Previous to return to the previous screen and correct your entries. Click Next when all the connections are successful. 13. In the Select Advanced Configuration screen, select the following: ■ Administration Server 4-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter ■ Managed Servers, Clusters and Machines ■ Deployment and Services Click Next. 14. 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: unchecked Click Next.

15. In the Configure Managed Servers screen, click Add to add the following

managed servers: Click Next. 16. In the Configure Clusters screen, Click Add to add the following clusters: Click Next. 17. In the Assign Servers to Clusters screen, assign servers to clusters as follows: ■ WSM-PM_Cluster: – WLS_WSM1 – WLS_WSM2 Click Next. 18. In the Configure Machines screen, do the following: ■ Click the Unix Machine tab and then click Add to add the following machines: Table 4–1 Managed Servers Name Listen Address Listen Port SSL Listen Port SSL Enabled WLS_WSM1 SOAHOST1 7010 na No WLS_WSM2 SOAHOST2 7010 na No Table 4–2 Clusters Name Cluster Messaging Mode Multicast Address Multicast Port Cluster Address WSM-PM_Cluster unicast na na Leave it empty. Note: Name can be any unique string. Node Manager Listen Address must be a resolvable host name. 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