1 Overview of Installing Oracle Traffic Director

Oracle Traffic Director is a software load balancer for load balancing HTTP/S and TCP traffic to servers in the back-end. These back-end servers, which are referred to as origin servers within Oracle Traffic Director, can be application servers, web servers, LDAP servers and so on. For information about the features of the product, see "Getting Started with Oracle Traffic Director" section of the Oracle Traffic Director Administrator's Guide.

This guide provides information about installing Oracle Traffic Director on Exalogic running either Oracle Linux or Oracle Solaris, and Oracle SuperCluster.

Note:

Before you start installing Oracle Traffic Director, it is recommended that you get a basic understanding of the product and its features, the related terminology, and the installation topology. For more information, see the "Getting Started with Oracle Traffic Director" section of the Oracle Traffic Director Administrator's Guide.

This chapter contains the following section:

• Section 1.1, "Installation, Deinstallation and Reinstallation Task Flow"

• Section 1.2, "Prerequisites for Installing Oracle Traffic Director"

1.1 Installation, Deinstallation and Reinstallation Task Flow

Table 1-1 provides information about the tasks that need to be performed for installing Oracle Traffic Director on Exalogic physical and virtual configurations and on Oracle SuperCluster. In addition, it includes information about deinstalling and reinstalling Oracle Traffic Director.

Table 1-1 Installation, Deinstallation and Reinstallation Task Flow

Task	For more information, see...
Creating projects and shares on Exalogic	Section 2.2
Mounting shares on Exalogic	Section 2.3
Global and non-global zones on Oracle SuperCluster	Section 3.1
Installing Oracle Traffic Director	Section 4.1
Creating the administration server	Section 5.1
Creating an administration node	Section 5.2
Verifying the installation	Section 6.1
Deinstalling Oracle Traffic Director	Section 6.2
Reinstalling Oracle Traffic Director	Section 6.3

For information about upgrading Oracle Traffic Director from 11.1.1.6.0 to 11.1.1.7.0, see Chapter 7, "Upgrading Oracle Traffic Director."

1.2 Prerequisites for Installing Oracle Traffic Director

This section provides the following information:

• "Prerequisites for Installing Oracle Traffic Director on Exalogic"

• "Prerequisites for Installing Oracle Traffic Director on Oracle SuperCluster"

1.2.1 Prerequisites for Installing Oracle Traffic Director on Exalogic

The following are the prerequisites for installing Oracle Traffic Director on Exalogic.

• In an environment where the underlying InfiniBand fabric is leveraging the InfiniBand partition technology, Oracle Traffic Director will need to be part of the partition with full membership. A full member of an IB partition can communicate with any other member of the partition. Full membership ensures that the Oracle Traffic Director administration server and all the administration nodes are able to communicate with each other without any issues. In addition, the Oracle Traffic Director instances should have two-way communication with app-tier nodes. So the compute nodes running Oracle Traffic Director and the compute nodes in the app-tier should all be full members of an IB partition. For more information about leveraging InfiniBand partitions, see "Using InfiniBand Partitions in Exalogic Physical Environments" in the Oracle Exalogic Elastic Cloud Machine Owner's Guide:

  http://docs.oracle.com/cd/E18476_01/doc.220/e18478/toc.htm

• Supported Platforms: Exalogic physical and virtual configurations.

• Minimum memory: 2 GB RAM for a vServer hosting the administration server.

  Note:

  • A vServer hosting Oracle Traffic Director server instances can also be configured with 2GB RAM. However, memory and vCPU requirements for administration server instances can vary depending on the configuration and load requirements.

  • If Oracle Traffic Director is configured with content caching, then the virtual memory size must be increased based on how much memory is allocated for caching static content. For more information about content caching, see the Oracle Traffic Director Administrator's Guide.

• CPUs per administration server/node: 2 CPUs in an Exalogic physical configuration; 2 to 4 vCPUs in an Exalogic virtual configuration.

• Java runtime environment (JRE): JRE 6, included in the installer.

• The following packages are mandatory for installing Oracle Traffic Director on Oracle Linux 5.

  • compat-glibc-2.3.4-x86_64 or higher

  • compat-libstdc++-33-3.2.3-x86_64 or higher

  • compat-libstdc++-33-3.2.3-i386

  • glibc-2.5-12-x86_64 or higher

  • glibc-devel-2.5-x86_64 or higher

  • glibc-devel-2.5-12-i386

  • libgcc-4.1.1-x86_64 or higher

  • libgcc-4.1.1-i386

  • libstdc++-4.1.1-x86_64 or higher

  • libstdc++-4.1.1-i386

  • sysstat-8.0.4-5.fc10.x86_64.rpm or higher

  • libaio-devel-0.3.106-5.x86_64.rpm or higher

  • libaio-0.3.106-i386

• Two hosts (either physical compute node or virtual machine) within Exalogic.

  Note:

  Oracle Traffic Director needs to be installed on two hosts only if you wish to provide high availability. You can install Oracle Traffic Director on a single host if you do not wish to configure it for high availability.

• If you intend to configure Oracle Traffic Director for high availability, a floating/virtual IP address within the network interface is required. The virtual IP address can be an address that is not being used within the same subnet.

1.2.2 Prerequisites for Installing Oracle Traffic Director on Oracle SuperCluster

The following are the prerequisites for installing Oracle Traffic Director on Oracle SuperCluster.

• Supported Platforms: Solaris 11.1 global zones residing in Oracle SuperCluster domains.

  Note:

  While Oracle Traffic Director can be deployed on non-global zones, it will not have high availability capability.

• Minimum memory: 2 GB RAM for an Oracle VM Server for SPARC hosting the administration server.

  Note:

  • An Oracle VM Server for SPARC hosting Oracle Traffic Director server instances can also be configured with 2GB RAM. However, memory and CPU requirements for administration server instances can vary depending on the configuration and load requirements.

  • If Oracle Traffic Director is configured with content caching, then the virtual memory size must be increased based on how much memory is allocated for caching static content. For more information about content caching, see the Oracle Traffic Director Administrator's Guide.

• Java runtime environment (JRE): JRE 6, included in the installer.

• Oracle VM Servers for SPARC hosting global zones or non-global zones within Oracle SuperCluster.

  Note:

  If you wish to configure Oracle Traffic Director for high availability, it must be installed on two global zones. In addition, all administration nodes must be running on the global zone.

  You can install Oracle Traffic Director on a single global or non-global zone if you do not wish to configure it for high availability. For more information about configuring Oracle Traffic Director for high availability, see "Configuring Oracle Traffic Director for High Availability" section of the Oracle Traffic Director Administrator's Guide.

• If you intend to configure Oracle Traffic Director for high availability, a floating/virtual IP address within the network interface is required. The virtual IP address can be an address that is not being used within the same subnet.