Introduction
The instructions in this guide show you how to install Connect’s supporting software,
which must be completed before you install Connect.
Pre-installation Software Requirements
Make sure that the appropriate versions of the operating system software and
supporting software are installed. The following list provides information about the
required operating system software and supporting software for your platform. Where
applicable, software download information is provided.
Note: Connect is certified to run with only the version numbers provided. Uninstall
other versions before installing certified versions of any of the supporting
software.
If the Connect Tracker will be installed on more than node, a software or
hardware-based HTTP load balancing solution will be required to distribute incoming
traffic to the Tracker nodes.
Operating System Software
Connect 10R5 is certified to run under Sun Solaris 10
on SPARC hardware, IBM AIX 6.1 on pSeries hardware, and 64-bit Linux on x86 hardware.
Connect may be run on virtual machines based on Solaris Zones, AIX WPARs/LPARs, VMWare or Xen.
The following Linux distributions are supported:
- RedHat Enterprise Linux 5/6 and compatible distributions
- SUSE Linux Enterprise 11 and compatible distributions
Note that only 64-bit Linux distributions are supported.
Supporting Software
UNIX systems generally do not require additional software to be installed in order to run Connect.
Depending on deployment configuration, however, the following additional infrastructure may be required:
- External mail servers (message transfer agents or MTAs) may be required
to serve as outbound mail farms or as inbound mail proxies.
- A software or hardware-based HTTP load balancing solution may be required to distribute
incoming traffic to the Tracker nodes if the Connect Tracker will be installed on more than node.
Unpack the Connect Software Distribution
On UNIX, Connect is distributed in two files: the platform-independent Connect software
and the platform-dependent Java Virtual Machine (JVM). Connect provides a separate JVM
for each architecture:
- java_sun.tar.gz for Solaris / SPARC
- java_aix.tar.gz for AIX / pSeries
- java_linux.tar.gz for 64-bit Linux
- Typically, Connect will be deployed under a dedicated user account. In this
document, we will assume the user name of this account is brickst.
- On the Connect install node, create a directory for the Connect
installation directory (e.g. /opt/connect.install).
In the Connect installation directory, uncompress and unpack the platform-independent
Connect software. This will create a kc directory. Then unpack the platform-dependent
JMV. This will create a java directory. Inside the java directory, there will be a script
named untar.jre.sh. Run this script on the install node to unpack the JVM so that
it can be used by the Connect install utilities.
The kc directory is the Connect home directory $KCHOME.