Restarting the Administration Server Configuring Oracle Coherence for Deploying Composites

5-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

5.4 Restarting the Administration Server

Restart the Administration Server using the procedure in Section 4.5, Creating boot.properties for the Administration Server on SOAHOST1.

5.5 Configuring Oracle Coherence for Deploying Composites

Although deploying composites uses multicast communication by default, Oracle recommends using unicast communication instead in SOA enterprise deployments. Use unicast if you disable multicast communication for security reasons. Enabling Communication for Deployment Using Unicast Communication Multicast communication enables Oracle Fusion Middleware SOA to discover all of the members of a cluster to which to it deploys composites dynamically. However, unicast communication does not enable nodes to discover other cluster members in this way. Consequently, you must specify the nodes that belong to the cluster. You do not need to specify all of the nodes of a cluster, however. You need only specify enough nodes so that a new node added to the cluster can discover one of the existing nodes. As a result, when a new node has joined the cluster, it is able to discover all of the other nodes in the cluster. Additionally, in configurations such as SOA enterprise deployments where multiple IPs are available in the same box, you must configure Oracle Coherence to use a specific host name to create the Oracle Coherence cluster. Specify the nodes using the tangosol.coherence.wkan system property, where n is a number between 1 and 9. You can specify up to 9 nodes. Start the numbering at 1. This numbering must be sequential and must not contain gaps. In addition, specify the host name used by Oracle Coherence to create a cluster through the tangosol.coherence.localhost system property. This local host name should be the virtual host name used by the SOA server as the listener addresses SOAHOST2VHN1and SOAHOST2VHN1. Set this property by adding the -Dtangosol.coherence.localhost parameters to the Arguments field of the Oracle WebLogic Server Administration Console’s Server Start tab Figure 5–3 . Note: An incorrect configuration of the Oracle Coherence framework that is used for deployment may prevent the SOA system from starting. The deployment framework must be properly customized for the network environment on which the SOA system runs. Oracle recommends the following configuration described in this section. Tip: To guarantee high availability during deployments of SOA composites, specify enough nodes so that at least one of them is running at any given time. Note: SOAHOST1VHN1 is the virtual host name that maps to the virtual IP where WLS_SOA1 listening in SOAHOST1. SOAHOST2VHN1 is the virtual host name that maps to the virtual IP where WLS_SOA2 is listening in SOAHOST2. Extending the Domain for SOA Components 5-9 Figure 5–3 Setting the Host Name Using the Start Server Tab of Oracle WebLogic Server Administration Console Specifying the host name To add the host name used by Oracle Coherence, complete these steps:

1. Log into the Oracle WebLogic Server Administration Console.

2. In the Domain Structure window, expand the Environment node.

3. Click Servers. The Summary of Servers page appears.

4. Click the name of the server WLS_SOA1 or WLS_SOA2, which are represented

as hyperlinks in Name column of the table. The settings page for the selected server appears.

5. Click Lock and Edit.

6. Click the Server Start tab illustrated in

Figure 5–3 .

7. Enter the following for WLS_SOA1 and WLS_SOA2 into the Arguments field.

For WLS_SOA1, enter the following: -Dtangosol.coherence.wka1=SOAHOST1VHN1 -Dtangosol.coherence.wka2=SOAHOST2VHN1 -Dtangosol.coherence.localhost=SOAHOST1VHN1 For WLS_SOA2, enter the following: -Dtangosol.coherence.wka1=SOAHOST2VHN1 -Dtangosol.coherence.wka2=SOAHOST1VHN1 -Dtangosol.coherence.localhost=SOAHOST2VHN1 5-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

8. Click Save and Activate Changes.

5.6 Setting Connection Destination Identifiers for B2B Queues