Configuring Server Migration 8-5
8.5 Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
The fifth step for server migration is to set environment and superuser privileges for the wlsifconfig.sh script:
1.
Ensure that your PATH environment variable includes these files:
2.
Grant sudo configuration for the wlsifconfig.sh script.
■
Configure sudo to work without a password prompt.
■
For security reasons, sudo should be restricted to the subset of commands required to run the wlsifconfig.sh script. For example, perform these steps to
set the environment and superuser privileges for the wlsifconfig.sh script:
a.
Grant sudo privilege to the WebLogic user oracle with no password restriction, and grant execute privilege on the sbinifconfig and
sbinarping binaries.
b.
Make sure the script is executable by the WebLogic user oracle. The following is an example of an entry inside etcsudoers granting sudo
execution privilege for oracle and also over ifconfig and arping:
oracle ALL=NOPASSWD: sbinifconfig,sbinarping
8.6 Configuring Server Migration Targets
The sixth step is to configure server migration targets. You first assign all the available nodes for the clusters members and then specify candidate machines in order of
preference for each server that is configured with server migration. Follow these steps to configure cluster migration in a migration in a cluster:
Note: When running Node Manager from a shared storage
installation, multiple nodes are started using the same nodemanager.properties file. However, each node may require
different NetMask or Interface properties. In this case, specify individual parameters on a per-node basis using environment
variables. For example, to use a different interface eth3 in HOSTn, use the Interface environment variable as follows:
HOSTn export JAVA_OPTIONS=-DInterface=eth3 Then, start Node Manager after the variable has been set in the shell.
Table 8–1 Files Required for the PATH Environment Variable
File Located in this directory
wlsifconfig.sh ORACLE_BASEadmindomain_namemserverdomain_
namebinserver_migration wlscontrol.sh
WL_HOMEcommonbin nodemanager.domains
WL_HOMEcommonnodemanager
Note: Ask the system administrator for the sudo and system rights
as appropriate to this step.
8-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
1.
Log in to the Administration Console http:Host:Admin_Portconsole. Typically, Admin_Port is 7001 by default.
2. In the Domain Structure window, expand Environment and select Clusters. The
Summary of Clusters page is displayed.
3.
Click the cluster for which you want to configure migration bi_cluster in the Name column of the table.
4. Click the Migration tab.