12-16 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
Perform these steps to configure server migration:
a.
Log in to the Oracle WebLogic Server Administration Console.
b. In the Domain Structure window, expand the Environment node and then
click Servers. The Summary of Servers page opens. c.
Click the name of the server represented as a hyperlink in Name column of the table for which you want to configure migration. The settings page for the
selected server opens.
d.
Open the Migration subtab.
e. In the Available field of the Migration Configuration section, select the
machines to which to allow migration and click the right arrow.
f. Choose the Automatic Server Migration Enabled option. This enables Node
Manager to start a failed server on the target node automatically.
g. Click Save.
h.
Restart the Administration Server, managed servers, and Node Manager.
16.
Test server migration for the new server. To test migration, perform the following steps from the node where you added the new server:
■
Abruptly stop the WLS_IPMn managed server. To do this, run kill -9 pid on the PID of the managed server. You can identify the PID of the node using the
following command:
ps -ef | grep WLS_IPMn
■
Watch the Node Manager Console for a message indicating that WLS_IPM1s floating IP has been disabled.
■
Wait for Node Manager to attempt a second restart of WLS_IPMn. Node Manager waits for a fence period of 30 seconds before trying this restart.
■
Once Node Manager restarts the server, stop it again. Node Manager should log a message indicating that the server will not be restarted again locally.
Note: Since this new node uses an existing shared storage
installation, the node already is using a Node Manager and an environment configured for server migration that includes netmask,
interface, wlsifconfig script superuser privileges, and so on. Verify the privileges defined in the new node to make sure server migration will
work. Refer to
Chapter 10, Configuring Server Migration for more
details on privilege requirements.
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 12-17
12.6.2.2 Scale-out Procedure for Oracle UCM
Perform these steps to scale out the Oracle UCM servers in the topology:
1.
On the new node, mount the existing Middleware home, which should include the ECM installation and domain directory, and ensure that the new node has access
to this directory, just like the rest of the nodes in the domain.
2.
To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute the following command:
ECMHOSTn cd ORACLE_COMMON_HOMEouibin ECMHOSTn .attachHome.sh -jreLoc ORACLE_BASEproductfmwjrockit_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 in to 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 Manager address to map the IP of the node that is being used for scale-out.
6.
Use the Oracle WebLogic Server Administration Console to clone WLS_UCM1 into a new managed server. Name it WLS_UCMn, where n is a number.
7.
Assign the host name or IP of ECMHOSTn to use for the new managed server as the listen address of the managed server.
8.
Run the pack command on SOAHOST1 to create a template pack:
SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmindomain_name
aserverdomain_name -template=edgdomaintemplateScale.jar -template_ name=edgdomain_templateScale
Note: After a server is migrated, to fail it back to its original node or
machine, stop the managed server from the Oracle WebLogic Administration Console and then start it again. The appropriate Node
Manager will start the managed server on the machine to which it was originally assigned.
Note:
These steps assume that you are adding a new UCM server to node n, where no managed server was running previously.
Note: These steps assume that you are adding a new server to node
n, where no managed server was running previously.
Note: If the domain directory for other managed servers resides on a
shared directory, this step is not required. Instead, the new nodes mount the already existing domain directory and use it for the new
added managed server.
12-18 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
9.
Run the following command on SOAHOST1 to copy the created template file to ECMHOSTn:
SOAHOST1 scp edgdomaintemplateScale.jar oracleECMHOSTn:ORACLE_COMMON_HOME commonbin
10.
Run the unpack command on ECMHOSTn to unpack the template in the managed server domain directory:
ECMHOSTn cd ORACLE_COMMON_HOMEcommonbin ECMHOSTn .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_
name -template= edgdomaintemplateScale.jar -app_dir=ORACLE_BASEadmindomain_
name mserverapplications
11.
Start Node Manager on the new node. To start Node Manager, use the installation in shared storage from the already existing nodes and then start Node Manager by
passing the host name of the new node as a parameter as follows:
ECMHOSTn WL_HOMEserverbinstartNodeManager.sh New_Node_IP
12.
Disable host name verification for the new managed server. Before you can start and verify the WLS_UCMn managed server, you must disable host name
verification. You can re-enable it after you have configured server certificates for the communication between the Oracle WebLogic Administration Server and
Node Manager in ECMHOSTn. If the source server from which the new one has been cloned had already disabled host name verification, these steps are not
required the host name verification setting is propagated to the cloned server.
Perform these steps to disable host name verification:
a.
In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Administration Console.
b. Expand the Environment node in the Domain Structure window.
