5-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
For example: wls:offlinenmConnectweblogic, my_password, APPHOST1 , 9556,
bifoundation_domain ,u01apporacleadminbifoundation_domainaserver bifoundation_domain
wls:nmbifoundation_domain nmStartAdminServer
5.5 Enabling Administration Server High Availability
The Oracle WebLogic Server Administration Server is a singleton application, so it cannot be deployed in an active-active configuration. By default, the Administration
Server is only available on the first installed node, and for this enterprise topology, it is available only on APPHOST1. If this node becomes unavailable, then the
Administration Console and Fusion Middleware Control also become unavailable. To avoid this scenario, the Administration Server and the applications deployed to it
must be enabled for high availability. The enterprise deployment architecture in this guide calls for the deploying the Administration Server on a disk shared between
APPHOST1 and APPHOST2.
The process described in this guide initially deploys the Administration Server and the bi_server1 Managed Server on the shared disk mounted on APPHOST1, and then
manually migrates the bi_server1 Managed Server domain information to the local file system. This process is necessary to overcome certain design constraints in the Oracle
Universal Installer.
This section contains the following topics:
■
Section 5.5.1, Enabling ADMINVHN on APPHOST1
■
Section 5.5.2, Create a Machine for the Administration Server
■
Section 5.5.3, Enabling the Administration Server to Listen on the Virtual IP Address
■
Section 5.5.4, Creating a Separate Domain Directory for the bi_server1 Managed Server
■
Section 5.5.5, Enabling Fusion Middleware Control Failover
5.5.1 Enabling ADMINVHN on APPHOST1
The Administration Server must be configured to listen on a virtual IP Address to enable it to seamlessly failover from one host to another. In case of a failure, the
Administration Server, along with the virtual IP Address, can be migrated from one host to another.
However, before the Administration Server can be configured to listen on a virtual IP Address, one of the network interface cards on the host running the Administration
Note: APPHOST1 is the address of the node where the domain was
created, not the listen address of the Administration Server. Also, the username and password are only used to authenticate
connections between Node Manager and clients. They are independent from the server admin ID and password, and are stored
in the ORACLE_BASEadmindomain_nameaserverdomain_ nameconfignodemanagernm_password.properties file.
Creating a Domain with the Administration Server and First Managed Server 5-7
Server must be configured to listen on this virtual IP Address. The steps to enable a virtual IP Address are completely dependent on the operating system.
Follow the steps in this section to enable a virtual IP Address on APPHOST1. In a UNIX environment, the command must be run as the root user:
1.
On APPHOST1, run the ifconfig command to get the value of the netmask. In a UNIX environment, run this command as the root user. For example:
[rootAPPHOST1 ~] sbinifconfig eth0
Link encap:Ethernet HWaddr 00:11:43:D7:5B:06
inet addr:139.185.140.51 Bcast:139.185.140.255
Mask:255.255.255.0 inet6 addr: fe80::211:43ff:fed7:5b0664 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1 RX packets:10626133 errors:0 dropped:0 overruns:0 frame:0
TX packets:10951629 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:4036851474 3.7 GiB TX bytes:2770209798 2.5 GiB
Base address:0xecc0 Memory:dfae0000-dfb00000
2.
On APPHOST1, bind the virtual IP Address to the network interface card using ifconfig. In a UNIX environment, run this command as the root user. Use a
netmask value that was obtained in Step 1.
The syntax and usage for the ifconfig command is as follows: sbinifconfig networkCardInterface Virtual_IP_Address netmask netMask
For example: sbinifconfig eth0:1 100.200.140.206 netmask 255.255.255.0
3.
Update the routing table using arping. In a UNIX environment, run this command as the root user.
sbinarping -q -U -c 3 -I networkCardInterface Virtual_IP_Address For example:
sbinarping -q -U -c 3 -I eth0 100.200.140.206 See also
Section 2.2.3.1, Enabling Virtual IPs for the Managed Servers for information
about enabling VIP2 and VIP3 for the Managed Servers on APPHOST1 and APPHOST2.
5.5.2 Create a Machine for the Administration Server
