Creating boot.properties for the Administration Server on SOAHOST1 Configuring Oracle Coherence for Deploying Composites

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-111 Figure 5–44 Assign Servers to Machines Screen ■ SOAHOST1: AdminServer, WLS_SOA1 ■ SOAHOST2: WLS_SOA2 Click Next.

20. In the Review WebLogic Domain screen, click Next.

21. In the Configuration Summary screen, click Create.

22. In the Creating Domain screen, click Done.

5.13.5 Creating boot.properties for the Administration Server on SOAHOST1

This is an optional step for enabling the Administration Server to start without prompting you for the administrator username and password. Create a boot.properties file for the Administration Server on SOAHOST1. For the Administration Server: 1. Create the following directories: SOAHOST1 mkdir -p ORACLE_BASEproductfmwuser_ projectsdomainssoadomainserversAdminServersecurity Note: The multicast and unicast addresses are different from the ones used by the WebLogic Server cluster for cluster communication. SOA guarantees that composites are deployed to members of a single WebLogic Server cluster even though the communication protocol for the two entities the WebLogic Server cluster and the groups to which composites are deployed are different. 5-112 Oracle Fusion Middleware High Availability Guide 2. Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file: username=adminuser password=password

5.13.6 Starting and Validating the Administration Server in SOAHOST1

This section describes procedures for starting and validating the Administrator Server in SOAHOST1

5.13.6.1 Starting the Administration Server on SOAHOST1

To start the Administration Server on SOAHOST1, run the following commands: SOAHOST1 cd MW_HOMEuser_projectsdomainssoadomainbin SOAHOST1 .startWebLogic.sh

5.13.6.2 Validating the Administration Server

To verify that the Administration Server is properly configured:

1. In a browser, go to http:vip0:7001console.

2. Log in as the administrator.

3. Verify that the WLS_SOA1 and WLS_SOA2 managed servers are listed.

4. Verify that the SOA_Cluster cluster is listed.

5. Verify that you can access Enterprise Manager at http:vip0:7001em.

5.13.7 Disabling Host Name Verification for the Administration Server and the WLS_ SOAn Managed Servers This step is required if you have not set up the appropriate certificates for hostname verification between the Administration Server and Node Manager. If SSL is not set up, you receive an error message unless you disable host name verification. You can re-enable host name verification when you have set up SSL communication between the Administration Server and the Node Manager. To disable host name verification:

1. In Oracle WebLogic Server Administration Console, select Servers, and then

AdminServer .

2. Select SSL, and then Advanced.

3. In the Change Center, click Lock Edit.

4. Set Hostname Verification to None.

Note: When you start the Administration Server, the username and password entries in the file are encrypted. For security reasons, minimize the time that the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible for the entries to be encrypted. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-113

5. In Oracle WebLogic Server Administration Console, select AdminServer, SSL, and

then Advanced. 6. Set Hostname Verification to None. 7. Save and activate the changes. 8. Repeat these steps for the WLS_SOA1 and WLS_SOA2 servers. 9. Restart the Administration Server.

5.13.8 Configuring Oracle Coherence for Deploying Composites

Although deploying composites uses multicast communication by default, Oracle recommends using unicast communication for SOA high availability. Use unicast if you disable multicast communication for security reasons. Enabling Communication within Clusters 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 a configuration where multiple IPs are available in the same node, you must configure Oracle Coherence to use a specific hostname to create 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 hostname used by Oracle Coherence to create a cluster through the tangosol.coherence.localhost system property. This hostname should be the virtual hostname used by the SOA servers that maps the corresponding listener addresses VIP1 and VIP2. Set this property by adding the -Dtangosol.coherence.localhost parameters to the Arguments field of Oracle WebLogic Server Administration Console’s Server Start tab Figure 5–45 . 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. 5-114 Oracle Fusion Middleware High Availability Guide Figure 5–45 Setting the Hostname Using the Start Server Tab of Oracle WebLogic Server Administration Console Specifying the hostname To add the hostname used by Oracle Coherence: 1. Log into 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 represented as a hyperlink in Name column of the table. The settings page for the selected server appears.

5. Click the Server Start tab illustrated in

Figure 5–45 . 6. Enter the following for WLS_SOA1 and WLS_SOA2 into the Arguments field. For WLS_SOA1, enter the following on a single line, without a carriage return: -Dtangosol.coherence.wka1=soahost1vhn1 -Dtangosol.coherence.wka2=soahost2vhn1 -Dtangosol.coherence.localhost=soahost1vhn1 For WLS_SOA2, enter the following on a single line, without a carriage return: -Dtangosol.coherence.wka1=soahost1vhn1 -Dtangosol.coherence.wka2=soahost2vhn1 -Dtangosol.coherence.localhost=soahost2vhn1 Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-115

7. Click Save and activate the changes.

8. This change requires the SOA servers to be restarted.

5.13.9 Setting Connection Destination Identifiers for B2B Queues