Note: End of General Support occurred on December 31st 2020 and End of Technical guidance will end on June 30th, 2021. Please refer to the 3.x End of Life Timeline.
This document describes the tc Server supported configurations and system requirements.
The following table shows all supported configurations for Pivotal tc Server.
Operating System | Processor Architecture | Production or Developer Support? |
---|---|---|
RedHat Enterprise Linux (RHEL) 8 Oracle Linux 8 CentOS 8 |
x86_64 (64 bit only) |
Production |
RedHat Enterprise Linux (RHEL) 7 Oracle Linux 7 CentOS 7 |
x86_64 (64 bit only) |
Production |
RedHat Enterprise Linux (RHEL) 6 Oracle Linux 6 CentOS 6 |
i686, x86_64 (32 or 64 bit) |
Production |
SUSE Linux Enterprise Server (SLES) 12 SUSE Linux Enterprise Server (SLES) 11.4 |
x86_64 (64 bit only) |
Production |
Ubuntu 18.04 LTS Ubuntu 16.04 LTS Ubuntu 14.04 LTS |
x86_64 (64 bit only) |
Production |
Oracle Solaris 11 Oracle Solaris 10 |
amd64, USparc III+ (64 bit only) |
Production |
Microsoft Windows Server 2016 Microsoft Windows Server 2012 |
x86_64 (64 bit only) |
Production |
Microsoft Windows 10 | x86_64 (64 bit only) |
Developer |
Apple OS X 10.9+ | x86_64 (64 bit only) |
Developer |
Note about supported JVMs:
Pivotal tc Server allows multiple versions of tc Runtimes (Apache Tomcat runtimes) installed. Pivotal tc Server provides the same supported JVM versions for our tc Runtimes versions as Apache Tomcat's JVM versions. We do recommend using at a minimum Java 8, since there are limitations to using Java 6 and Java 7.
Pivotal tc Server runtimes are tested on the following JVMs with OpenJDK and Oracle JDK builds:
There are various providers of Java SE implementations. We recommend you choose an implementation of Java SE specification with long-term support (LTS). Also, be sure to select a JVM version that is supported by your operating system and processor architecture.
Note about OS patch levels: Follow the guidance of your operating system or JVM vendor when deciding which patch levels should be applied to your computer. In general, the latest patch update levels are recommended.
See the Pivotal tc Server release notes for information about supported tc Runtime versions:
Pivotal tc Server supports the following specifications:
The following related Pivotal product versions are supported with tc Server:
Pivotal GemFire HTTP Session Manager. Available for download by using tcruntime-admin
utility (3.2+). Also available from the Pivotal GemFire product page, click Download.
Redis. Use a Redis server for session management and replication. Available for download by using tcruntime-admin
utility (3.2+).
All tc Server editions require you to download a JDK or JRE.
Prerequisites
Procedure
JAVA_HOME
environment variable to point to your installation, and update your PATH
environment variable to point to the JAVA_HOME/bin
directory.Note: While tc Server requires a JDK to run, Pivotal does not provide the JDK nor any technical support for the JDK. You are responsible for providing and supporting your chosen JDK. Please keep this in mind when selecting a JDK or JRE, as available vendor support for the chosen JDK may be a factor when making a selection.
If you are installing tc Server on Solaris from a tarball, use GNUtar
instead of the system tar
.
For Solaris 11, use /usr/gnu/bin/tar
where tc Server documentation references tar
.
For Solaris 10, use /usr/sfw/bin/gtar
where tc Server documentation references tar
. If /usr/sfw/bin/gtar
does not exist, it can be installed from the Solaris 10 installation CDs.
If you do not have the ability to install from the Solaris 10 installation CDs, a GNUtar
implementation can be downloaded and installed from OpenCSW. When using this approach, use /opt/csw/bin/gtar
where tc Server documentation references tar
.