11-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
Log into the Oracle WebLogic Server Administration Console and configure server migration following these steps:
a. Expand the Environment node in the Domain Structure windows and then
choose Servers. The Summary of Servers page appears.
b.
Select the server represented as hyperlink for which you want to configure migration from the Names column of the table. The Setting page for that
server appears.
c. Click the Migration tab.
d.
In the Available field of the Migration Configuration section, click the right arrow to select the machines to which to allow migration.
e. Select Automatic Server Migration Enabled. This enables the Node Manager
to start a failed server on the target node automatically.
f. Click Save.
g.
Restart the Administration Server, managed servers, and the Node Manager. To restart the Administration Server, use the procedure in
Section 4.7, Starting the Administration Server on SOAHOST1.
17.
Update the cluster address to include the new server:
a. In the Administration Console, select Environment, and then Cluster.
b. Click the SOA_Cluster server.
The Settings screen for the SOA_Cluster appears.
c. Click Lock and Edit.
d. Add the new server’s address and port to the Cluster address field. For
example: ADMINVHN:8011,SOAHOST2VHN1:8011,SOAHOSTNVHN1:8001
e.
Save and activate the changes.
18.
Test server migration for this new server. Follow these steps from the node where you added the new server:
a.
Abruptly stop the WLS_SOAn managed server by running kill -9 pid on the PID of the managed server. You can identify the PID of the node using
ps -ef | grep WLS_SOAn.
b.
In the Node Manager Console you should see a message indicating that WLS_ SOA1s floating IP has been disabled.
c.
Wait for the Node Manager to try a second restart of WLS_SOAn. Node Manager waits for a fence period of 30 seconds before trying this restart.
d.
Once Node Manager restarts the server, stop it again. Now Node Manager should log a message indicating that the server will not be restarted again
locally.
Note: Specify the least-loaded machine as the migration target for
the new server. The required capacity planning must be completed so that this node has enough available resources to sustain an additional
managed server.
Managing the Topology 11-15
11.4.2.2 Scaling Out WebCenter
In scaling out your topology, you add new managed servers, configured with Oracle WebCenter applications, to new nodes.
Before performing the steps in this section, check that you meet these requirements:
■
In your topology, there are existing nodes running managed servers configured with WebCenter applications.
■
The new node can access the existing home directories for WebLogic Server and Oracle WebCenter. You use the existing installations in shared storage for creating
a new managed server. There is no need to install WebLogic Server or WebCenter binaries in a new location, although you need to run pack and unpack to create a
managed server domain.
■
WC_Spaces and WC_Utilities servers must be either both scaled out on the new node, or both not scaled out. This is because of the local affinity between
WebCenter Spaces and the Analytics application.
To scale out the topology:
1. On the new node, mount the existing Middleware home, which should include the
WebCenter installation and the domain directory, and ensure that the new node has access to this directory, just as the rest of the nodes in the domain do.
2. To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute
the following commands: WCHOSTn cd ORACLE_BASEproductfmwwc
WCHOSTn .attachHome.sh -jreLoc ORACLE_BASEfmwjrockit_160_version To update the Middleware home list, create or edit, if another WebLogic
installation exists in the node the MW_HOMEbeabeahomelist file and add ORACLE_BASEproductfmw to it.
3. Log into the Oracle WebLogic Administration Console.
4. Create a new machine for the new node that will be used, and add the machine to
the domain.
5. Update the machines Node Managers address to map the IP address of the node
that is being used for scale out.
6.
Use the Oracle WebLogic Server Administration Console to clone either WC_ Spaces1 or WC_Portlet1 or WC_Collaboration1 or WC_Utilities1 into a new
managed server. Name it WLS_XXXn, where n is a number and assign it to the new machine.
7.
For the listen address, assign the host name or IP to use for the new managed server. Perform these steps to set the managed server listen address:
a.
Log into the Oracle WebLogic Server Administration Console.
b. In the Change Center, click Lock Edit.
