Editing Node Managers Properties File Setting Environment and Superuser Privileges for the wlsifconfig.sh Script

17-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

17.3 Editing Node Managers Properties File

The third step is to edit Node Managers properties file. This must be done for the Node Managers in both nodes OIMHOST1 and OIMHOST2 where server migration is being configured: Interface=eth0 NetMask=255.255.255.0 UseMACBroadcast=true ■ Interface: This property specifies the interface name for the floating IP for example, eth0. ■ NetMask: This property specifies the net mask for the interface for the floating IP. The net mask should the same as the net mask on the interface; 255.255.255.0 is used as an example in this document. ■ UseMACBroadcast: This property specifies whether to use a nodes MAC address when sending ARP packets, that is, whether to use the -b flag in the arping command. Verify in Node Managers output shell where Node Manager is started that these properties are being used, or problems may arise during migration. You should see something like this in Node Managers output: ... StateCheckInterval=500 Interface=eth0 NetMask=255.255.255.0 ... 1. Set the following property in the nodemanager.properties file: ■ StartScriptEnabled: Set this property to true. This is required to enable Node Manager to start the Managed Servers. 2. Start Node Manager on OIMHOST1 and OIMHOST2 by running the startNodeManager.sh script, which is located in the WL_HOMEserverbin directory. Note: Do not specify the sub-interface, such as eth0:1 or eth0:2. This interface is to be used without :0 or :1. Node Managers scripts traverse the different :X-enabled IPs to determine which to add or remove. For example, the valid values in Linux environments are eth0, eth1, eth2, eth3, ethn, depending on the number of interfaces configured. Note: The following steps are not required if the server properties start properties have been properly set and Node Manager can start the servers remotely. 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