Configuring Server Migration Targets Click the Migration tab.

Configuring Server Migration for Oracle Identity Manager 17-5

17.4 Setting Environment and Superuser Privileges for the wlsifconfig.sh Script

This section is not required on Windows. On Linux and UNIX-based systems, the fourth step 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 the following steps to set the environment and superuser privileges for the wlsifconfig.sh script: ■ Grant sudo privilege to the WebLogic user oracle with no password restriction, and grant execute privilege on the sbinifconfig and sbinarping binaries. ■ Ensure 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

17.5 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 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 and start Node Manager after the variable has been set in the shell. Table 17–1 Files Required for the PATH Environment Variable File Located in this directory wlsifconfig.sh ORACLE_BASE admindomain_namemserverdomain_ namebinserver_migration wlscontrol.sh WL_HOME commonbin nodemanager.domains WL_HOME common Note: Ask the system administrator for the appropriate sudo and system rights to perform this step. 17-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management preference for each server that is configured with server migration. Follow these steps to configure cluster migration in a migration in a cluster: 1. Log in to the Oracle WebLogic Server 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 OIM_CLUSTER in the Name column of the table.

4. Click the Migration tab.

5. Click Lock and Edit.

6. In the Available field, select the machine to which to allow migration and click the

right arrow. In this case, select OIMHOST1 and OIMHOST2. 7. Select the data source to be used for automatic migration. In this case, select the leasing data source.

8. Click Save.

9. Click Activate Changes.

10. Repeat steps 2 through 9 for the SOA cluster. 11. Set the candidate machines for server migration. You must perform this task for all of the Managed Servers as follows: a. In the Domain Structure window of the Oracle WebLogic Server Administration Console, expand Environment and select Servers. b. Select the server for which you want to configure migration.

c. Click the Migration tab.

d. In the Available field, located in the Migration Configuration section, select