Database Reference
In-Depth Information
virtual_ipaddress {
10.177.0.60
}
[root@oevm1 ~]#
service keepalived start
Starting keepalived: [ OK ]
This simple configuration ensures the virtual IP address 10.177.0.60 is assigned to one of the servers running this
configuration. State
BACKUP
means there is no preferred server for the virtual IP address.
NOPREEMPT
instructs the
server not to try to grab the virtual IP address at the startup if the IP is already assigned to another server. This will
ensure bringing up the VM after the failure doesn't cause downtime for the front-end services. Listing 11-14 shows
how to check if the virtual IP address was allocated to the server (if
keepalived
is used the outputs of
ifconfig
don't
report the virtual IP address as assigned to any of the interfaces).
Listing 11-14.
Checking the Virtual IP Address Is Assigned to the Application Tier Node
[root@oevm1 ~]#
ip addr list dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:16:3e:29:ea:12 brd ff:ff:ff:ff:ff:ff
inet 10.177.0.61/16 brd 10.177.255.255 scope global eth0
inet 10.177.0.60/32 scope global eth0
inet6 fe80::216:3eff:fe29:ea12/64 scope link
valid_lft forever preferred_lft forever
The are many other configuration options for
keepalived,
and for the production use one should consider adding
settings to monitor the application URLs so that the virtual IP would always be located on the node the application
services are actually running on. One should also set the passwords for the communication between the
keepalived
servers to reduce the risks of someone stealing the virtual IP address, or even adding a
haproxy
package to configure
true software load balancing solution for e-Business Suite.
Installing the e-Business Suite
Having prepared the ODA, it is time to perform the actual installation. This is done in two parts. First install the
database tier, then install the application tier. The hardware configuration and virtualization layer you have configured
on the ODA is transparent to the e-Business Suite installation process, and it does not introduce any complications
specific to deployments on ODA.
The Database Tier Installation
From the e-Business Suite database tier installation point of view, the database server on ODA is just a Linux
machine and the installation process doesn't differ from the one described in the
Oracle E-Business Suite Installation
Guide: Using Rapid Install, Release 12.2 (12.2.0).
12
As the ODA is a preconfigured system, you can skip most of the
preinstallation tasks. However, the following steps still need to be performed:
1.
Download the installation media from Oracle Software Delivery Cloud and stage the
installation on an attached NFS share or local file system
/u02
, which was created in the
previous step, on ODA Base.
12
Available from
otn.oracle.com
documentation section,
http://docs.oracle.com/cd/E18727_01/index.htm
.
