5-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
a. Select the SOA Infrastructure, User Messaging Service, and SOA MDS
Schema rows in the table.
b. Select Configure selected component schemas as RAC multi data source
schemas in the next panel.
c. Click Next.
Figure 5–1 Configure JDBC Component Schema Screen
8. In the Configure RAC Multi Data Source Component Schema screen
Figure 5–2 ,
do the following:
a. Select SOA Infrastructure.
b. Enter values for the following fields, specifying the connect information for
the 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 prefix for the schemas. The user names shown in
Figure 5–2 assume that soedg was
used as 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 RAC instance.
d. Repeat for each RAC instance.
Extending the Domain for SOA Components 5-5
e. Deselect SOA Infrastructure.
f. Select User Messaging Service.
g.
Repeat steps b, c, and d for the User Messaging Schema.
h. Deselect User Messaging Service.
i. Select SOA MDS Schema.
j.
Repeat steps b, c, and d for the SOA MDS Schema.
k.
Leave the OWSM MDS Schema information as it is.
l. Click Next
Figure 5–2 Configure RAC Multi Data Source Component Schema Screen
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 Select Optional Configuration screen, select the following:
■
JMS Distributed Destinations
■
Managed Servers, Clusters, and Machines
■
Deployments and Services
Click Next. 11.
In the Select JMS Distributed Destination Type screen:
5-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
■
Select UDD from the drop down list for UMSJMSystemResource.
■
Select UDD from the drop down list for SOAJMSModule. 12.
In the Configure Managed Servers screen, add the required managed servers. A server called soa_server1 is created automatically. Rename this to WLS_
SOA1 and give it the attributes listed in Table 5–1
. Then, add a new server called WLS_SOA2. The WLS_WSM1 and WLS_WSM2 managed servers should already
be present because they are part of the domain that you are extending. In the end, the list of managed servers should match that in
Table 5–1 .
Click Next. 13.
In the Configure Clusters screen, add the following clusters:
Click Next. 14.
In the Assign Servers to Clusters screen, assign servers to clusters as follows:
■
SOA_Cluster: –
WLS_SOA1 –
WLS_SOA2
■
WSM-PM_Cluster: –
WLS_WSM1 –
WLS_WSM2
Click Next. 15.
In the Configure Machines screen, do the following:
■
Delete the LocalMachine that appears by default.
■
Click the Unix Machine tab. The following entries appear listed in Table 5–3
:
Table 5–1 Managed Servers
Name Listen Address
Listen Port SSL Listen Port
SSL Enabled
WLS_SOA1 SOAHOST1VHN1
8001 na
No WLS_SOA2
SOAHOST2VHN1 8001 na
No WLS_WSM1
SOAHOST1 7010
na No
WLS_WSM2 SOAHOST2
7010 na
No
Table 5–2 Clusters
Name Cluster Messaging
Mode Multicast
Address Multicast
Port
Cluster Address
SOA_Cluster unicast
na na
Leave it empty. WSM-PM_Cluster
unicast na
na Leave it empty.
Table 5–3 Machines
Name Node Manager Listen Address
SOAHOST1 SOAHOST1
SOAHOST2 SOAHOST2
Extending the Domain for SOA Components 5-7
Leave all other fields to their default values.
Click Next. 16.
In the Assign Servers to Machines screen, assign servers to machines as follows:
■
ADMINHOST: –
AdminServer
■
SOAHOST1: –
WLS_SOA1 –
WLS_WSM1
■
SOAHOST2: –
WLS_SOA2 –
WLS_WSM2
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.
■
The oracle.sdp., and oracle.soa. libraries should be targeted only to SOA_ Cluster
.
■
The oracle.rules. library should be targeted only to Admin Server and SOA_ Cluster
.
■
The wsm-pm application should be targeted only to WSM-PM_Cluster.
■
The oracle.wsm.seedpolicies library should be targeted only to WSM-PM_ Cluster
.
Target this library to the SOA_Cluster also only if you are planning to deploy WebLogic WebServices to it.
Click Next. 18.
In the Target Services to Clusters or Servers screen, ensure the following targets:
■
Target JOC Startup Class and JOC Shutdown Class only to WSM-PM_ Cluster
.
■
Target mds-owsm, mds-owsm-rac0, and mds-owsm-rac1 to both WSM-PM_ Cluster
and AdminServer. Click Next.
19. In the Configuration Summary screen click Extend.
20. In the Extending Domain screen, click Done.
You must restart the Administration Server for this configuration to take effect.
Note: Click OK to dismiss the warning dialog about the domain
configuration ports conflicting with the host ports. This warning appears because of the existing WSM-PM installation.
5-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
5.4 Restarting the Administration Server
