|Oracle® Traffic Director Installation Guide
11g Release 1 (22.214.171.124.0)
Part Number E21034-04
|PDF · Mobi · ePub|
This chapter provides information about global and non-global zones, and discusses the various options for installing Oracle Traffic Director on Oracle SuperCluster.
The setup that is discussed in this chapter is ideal when you are looking for application-level traffic management capabilities to monitor and shape the traffic within Oracle SuperCluster. In Oracle SuperCluster, two zones (global or non-global) are allocated, wherein incoming traffic is screened and routed to one of the back-end application servers. In this scenario, Oracle Traffic Director (web tier) is typically hosted on two zones and the application tier is located on another zone.
This chapter contains the following sections:
Before installing Oracle Traffic Director on Oracle SuperCluster, you must consider the following.
Oracle Traffic Director requires an application domain, such as Oracle VM Server for SPARC (formerly called Logical Domains), running Solaris 11.1 for it to run successfully.
In an Oracle VM Server for SPARC, Oracle Traffic Director can be installed on either a global zone or a non-global zone.
The global zone is the default operating system and has control over all the processes. A global zone always exists even when no other zones are configured. A global zone is also used for system-wide administrative control.
A non-global zone, referred to as a zone, is configured inside the global zone. Each zone is an isolated OS environment that you can use to run applications. The applications and processes that are running in one zone do not affect what is running in other zones.
For more information about global and non-global zones, see "Oracle Solaris Zones" section of Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management: http://docs.oracle.com/cd/E26502_01/html/E29024/zone.html.
One important factor to consider when choosing global or non-global is that Oracle Traffic Director can be configured for high availability only when installed on a global zone. In addition, all administration nodes must be running on the global zone.
Configuring VRRP and hence configuring failover groups is supported only in the global zone, and for a privileged user. This is because of Solaris VRRP limitations. For more information, see the "VRRP Limitations" section of the Managing Oracle Solaris 11.1 Network Performance Guide: http://docs.oracle.com/cd/E26502_01/html/E28993/gkmfl.html.
Oracle Traffic Director can be installed on a global zone or a non-global zone. Note that in order to take advantage of Oracle Traffic Director's high availability capability, it must be installed on a global zone.
Another option to configure Oracle Traffic Director for HA is to install Oracle Solaris Cluster. For more information, see the Oracle Solaris Cluster Data Services Planning and Administration Guide, http://docs.oracle.com/cd/E29086_01/html/E29475/index.html.
For an Oracle Traffic Director installation, it is recommended that the zone (global or non-global) hosting Oracle Traffic Director is unique. Note that for installing Oracle Traffic Director on a non-global zone, it must be configured with appropriate disk and network information.
The steps for installing Oracle Traffic Director on Oracle SuperCluster are as follows:
Configure and create a new zone, either global or non-global. For more information about leveraging zones, see "Oracle Solaris Zones" in Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management:
Download and install Oracle Traffic Director on the zone. For more information, see Chapter 4, "Installing Oracle Traffic Director."