Enabling Host Name Verification Certificates Editing the Node Manager Properties File

8-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence

8.3 Enabling Host Name Verification Certificates

The third step is to create the appropriate certificates for host name verification between Node Manager and the Administration Server. This procedure is described in Section 7.3, Enabling Host Name Verification Certificates for Node Manager. If you have not yet created these certificates, perform the steps in this section to create certificates for host name verification between Node Manager and the Administration Server.

8.4 Editing the Node Manager Properties File

The fourth step in configuring server migration is to edit the Node Manager properties file. This task must be performed for the Node Managers in both nodes 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. Do not specify the sub-interface, such as eth0:1 or eth0:2. This interface is to be used without :0 or :1. Node Manager 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. ■ NetMask: This property specifies the net mask for the interface for the floating IP. The net mask should be 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, or in other words, whether to use the -b flag in the arping command. Verify in the Node Manager output the 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 the Node Manager 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 for Node Manager to start the Managed Servers using start scripts. 2. Start Node Manager on APPHOST1 and APPHOST2 by running the startNodeManager.sh script, which is located in the WL_HOMEserverbin directory. 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 8-5

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