Select IPM Schem Leave the other data sources as they are. Click Add and enter the details for the first Oracle RAC instance. Click Next.

8-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite Figure 8–2 Configure RAC Multi Data Source Component Scheme Screen for Oracle IPM In the Configure RAC Multi Data Sources Component Schema screen, do the following: a. Select IPM Schema. Leave the other data sources as they are. b. 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 and later . – Service Name: Enter the service name of the database ecmedg.mycompany.com. – Username: Enter the complete user name including the prefix for the schemas. The user names shown in Figure 8–2 assume that DEV was used as the prefix for schema creation from RCU. – Password: Enter the password to use to access the schemas.

c. Click Add and enter the details for the first Oracle RAC instance.

d. Repeat step c for each Oracle RAC instance.

e. Click Next.

Note: Leave the UCM Schema, SOA Infrastructure, User Messaging Service, OWSM MDS Schema, and SOA MDS Schema information as they are. Extending the Domain with Oracle IPM 8-5 9. 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. 10. In the Optional Configuration screen, select the following: ■ JMS Distributed Destination ■ Managed Servers, Clusters and Machines ■ Deployment and Services Click Next. 11. In the Select JMS Distributed Destination Type screen, select UDD from the drop-down list for the JMS modules of all Oracle Fusion Middleware components. Click Next. If an override warning appears, click OK to acknowledge it. 12. In the Configure Managed Servers screen, add the required managed servers. A server called ipm_server1 is created automatically. Rename this to WLS_IPM1 and add a new server called WLS_IPM2. Give these servers the attributes listed in Table 8–1 . Do not modify the other servers that appear in this screen; leave them as they are. Click Next. 13. In the Configure Clusters screen, click Add to add the clusters as shown in Table 8–2 . Do not modify the other clusters that appear in this screen; leave them as they are. Click Next. 14. In the Assign Servers to Clusters screen, add the following. Do not modify the other assignments that appear in this screen; leave them as they are. ■ IPM_Cluster: – WLS_IPM1 – WLS_IPM2 Click Next. Table 8–1 Managed Servers Name Listen Address Listen Port SSL Listen Port SSL Enabled WLS_IPM1 ECMHOST1VHN1 16000 na No WLS_IPM2 ECMHOST2VHN2 16000 na No Table 8–2 Clusters Name Cluster Messaging Mode Multicast Address Multicast Port Cluster Address IPM_Cluster unicast na na Leave empty 8-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

15. In the Configure Machines screen, click the Unix Machine tab. You should see the

ECMHOST1 and ECMHOST2 machines and have the following entries: Leave all other fields to their default values. Click Next. 16. In the Assign Servers to Machines screen, assign servers to machines as follows: ■ Assign WLS_IPM1 to ECMHOST1. ■ Assign WLS_IPM2 to ECMHOST2. Click Next. 17. In the Target Deployments to Clusters or Servers screen, ensure the following targets: ■ usermessagingserver and usermessagingdriver-email should be targeted only to SOA_Cluster . The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional. ■ WSM-PM should be targeted only to SOA_Cluster. ■ The oracle.rules, oracle.sdp. and oracle.soa. deployments should be targeted to SOA_Cluster only, except for the oracle.soa.workflow.wc library, which should be targeted to both the SOA_Cluster and the IPM_Cluster. ■ The oracle.wsm.seedpolicies library should be targeted to SOA_Cluster and IPM_Cluster and any servers expected to host WSM-PM protected web services. Click Next. 18. In the Target Service to Cluster or Servers screen, target JOC Startup Class and JOC Shutdown Class only to SOA_Cluster. Click Next.

19. In the Configuration Summary screen, click Extend.

20. If a dialog window appears warning about conflicts in ports for the domain, click

OK . This should be due to pre-existing servers in the nodes and the warning can be ignored.

21. In the Creating Domain screen, click Done.

22. Restart the Administration Server to make these changes to take effect. See

Section 8.6, Restarting the Administration Server. Table 8–3 Machines Name Node Manager Listen Address SOAHOST1 SOAHOST1 SOAHOST2 SOAHOST2 ADMINVHN localhost ECMHOST1 ECMHOST1 ECMHOST2 ECMHOST2 Extending the Domain with Oracle IPM 8-7

8.4 Propagating the Domain Configuration to ECMHOST1 and ECMHOST2 Using the unpack Utility