Database Reference
In-Depth Information
This configuration allows you to mount the
/cloudfs
to the application tier servers from any of the ODA Base
VMs. You can also use virtual IP addresses on the ODA Base VMs for the NFS mounts to make sure you can mount
NFS volumes, even if one of the ODA Base VMs is down and the virtual IP is relocated to the remaining node. Listing
11-12 shows the
/etc/fstab
entries for both application tier nodes that are used to mount the volumes from ACFS.
10
Listing 11-12.
/etc/fstab Entries for the Shared NFS Mount on Both Application Tier VMs
[oracle@oevm1 ~]$
grep cloudfs /etc/fstab
s1-vip:/cloudfs /cloudfs nfs rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tc
p,nolock,acregmin=0,acregmax=0 0 0
[oracle@oevm2 ~]$
grep cloudfs /etc/fstab
s2-vip:/cloudfs /cloudfs nfs rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tc
p,nolock,acregmin=0,acregmax=0 0 0
One has to be aware that this is not really a highly available solution for the NFS-mounted ACFS volumes on the
application tier VMs. Our testing shows the mounted file systems can and will still hang after a virtual IP relocation
happens on the DB nodes. You thus have to be ready to take action to recover the services on application tiers too.
Configure the Virtual IP for the Application Tier
The virtualized ODA platform does not support VM migrations from one physical server to the other, which means
you need to have two application tier VMs—one on each physical server—to ensure the availability of e-Business Suite
if one of the servers becomes unavailable. As there's no load balancing solution provided for VMs either, the best you
can do is use an external load balancer to route the traffic to the application tier VMs you'll configure on the ODA. The
e-Business Suite-specific configuration for using load balancers is explained in “Using Load-Balancers with Oracle
E-Business Suite Release 12.2 (Doc ID 1375686.1).”
In this chapter, you'll find out how to use Linux
keepalived
11
software to improve the availability of e-Business
Suite if an external load balancer is not available.
Keepalived
is available on the Oracle Linux 6 public yum repository.
In this scenario, a very simple configuration that only manages a virtual IP address will be used. The virtual IP
address will be mounted on one of the servers and will be configured as the web entry point for the e-Business Suite
front-end services, this way providing an Active/Passive configuration from an end-user perspective.
You'll have two application tier nodes in the configuration—
oevm1
and
oevm2
—and the virtual IP 10.177.0.60
will be assigned hostname
oevip
. Listing 11-13 provides the commands for the installation of
keepalived
and shows
the content of its configuration file. No configuration changes to
keepalived
will be needed after cloning the second
application tier node.
Listing 11-13.
Linux keepalived Installation and Configuration
[root@oevm1 ~]#
yum install keepalived
[root@oevm1 ~]#
vi /etc/keepalived/keepalived.conf
[root@oevm1 ~]#
cat /etc/keepalived/keepalived.conf
vrrp_instance VI_1 {
interface eth0
state BACKUP
NOPREEMPT
virtual_router_id 1
10
The recommended mount options are listed in My Oracle Support note “Sharing the Application Tier File System in Oracle
E-Business Suite Release 12.2 (Doc ID 1375769.1).”
