Installing VMware tc Server

Installation options vary according to your operating system.

Note: Previous versions of Tanzu tc Server had separation of tc Server and tc Runtimes. As of VMware Tanzu tc Server 10.1.20.A this is no longer the case.

Install Tanzu tc Server from a ZIP or TAR File

See Quick Start for information on manually installing Tanzu tc Server

RHEL - Install Tanzu tc Server from an RPM

You can also download the RPM from the Tanzu Network download page and install it on your RHEL compatible computer using the rpm command, as described in Install Tanzu tc Server from a Downloaded RPM. For detailed information on obtaining tc Server please see obtaining tc Server.

Install Tanzu tc Server From a Downloaded RPM

You can install Tanzu tc Server on RHEL by downloading the RPM from the VMware download center and executing the rpm command.

Prerequisites

Verify that your system meets the supported configurations and installation requirements. See Supported Configurations and System Requirements.

Procedure

Log in to the RHEL computer on which you will install Tanzu tc Server as the root user (or as an unprivileged user who has sudo privileges).
See Obtaining tc Server for instructions on how to download tc Server.
Download the tc Server RPM file to a directory on your computer. The RPM file is called tanzu-tc-server-10.1.20.A.RPM.
Start a terminal and change to the directory in which you downloaded the RPM.
Execute the following rpm command to install tc Server and tc Runtime:
```
rpm -Uvhf tanzu-tc-server-10.1.20.A.noarch.rpm
```
If necessary, use sudo to run the preceding command if you are not logged in as the root user. For example:
```
sudo rpm -Uvhf tanzu-tc-server-10.1.20.A.noarch.rpm
```
In the previous section, see What the yum install command does for post-installation information, such as the installation directory and the user that is automatically created by the RPM installation. (The yum install command corresponds to the rpm command in this procedure.)

tc Server Variables

tc Server uses the following variables:

CATALINA_HOME . Root directory of your tc Runtime installation.

The CATALINA_HOME variable points to the directory /opt/tc-server/5.0.x/runtimes/tomcat-<version>, where /opt/tc-server/5.0.x is the directory in which you installed tc Server.; <version> refers to the tc Runtime (Apache Tomcat) version, such as 10.1.18.A.RELEASE.
CATALINA_BASE . Root directory of a particular tc Runtime instance.

This directory contains the instance-specific files, such as the conf/server.xml file that configures this particular instance. If you created a tc Runtime instance called myserver and you are using the recommended directories, then the CATALINA_BASE of the instance is /opt/tc-server/10.1/instances/myserver by default.

The following variables are "exposed" by tc Runtime, which means that you can set them or use them in your environment (or in the bin/setenv.sh file of your tc Runtime instance) to achieve the specified results:

CATALINA_OUT . Unix only. Use this environment variable to specify a file to which a tc Runtime instance writes stdout and stderr messages. If you do not set this environment variable explicitly, the tc Runtime instance writes stdout and stderr messages to the file CATALINA_BASE/logs/catalina.out.

For example, to specify that the tc Runtime instance write its stdout and stderr messages to /opt/tanzu/tc-server/10.1/instances/example/log/tcruntime-instance-6.log, set the variable in your environment or setenv.sh as follows:
```
CATALINA_OUT=/opt/tanzu/tc-server/10.1/instances/example/log/tcruntime-instance-6.log
```
INSTANCE_NAME . Name of the tc Runtime instance. You can use this variable to create other unique variables within configuration scripts.

For example, on Unix platforms you can update the bin/setenv.sh file to use the name of the tc Runtime instance when defining the CATALINA_OPTS variable as follows:
```
CATALINA_OPTS="-Dinstance.name=$INSTANCE_NAME"
```
INSTANCE_BASE . Specifies the parent directory of the tc Runtime instance. The full pathname of the tc Runtime instance directory would be $INSTANCE_BASE/$INSTANCE_NAME.

You can use the INSTANCE_BASE variable in the same way as the INSTANCE_NAME variable, as described in the preceding bullet.

tc Runtime Instance Directory Structure

After you create a new tc Runtime instance, its CATALINA_BASE directory contains the following subdirectories:

bin . Contains the setenv.* scripts. The *.sh Unix files are functional duplicates of the *.bat Windows files.
conf . Contains the configuration files for the tc Runtime instance, such as server.xml, catalina.properties, web.xml, context.xml, and so on.
lib . Contains resources shared by all Web applications deployed to the tc Runtime instance.
logs . Location of the logs files.
webapps . Deployment directory for the Web applications deployed to the tc Runtime instance.
work . Temporary work directory for all deployed Web applications.
temp . Directory used by the JVM for temporary files.

tc Runtime Instance Configuration Files

You configure a particular tc Runtime instance by changing its configuration files. Other topics in this documentation describe how to do this. All the configuration files for a tc Runtime instance are located in its CATALINA_BASE/conf directory. The most important configuration files are as follows:

server.xml . Main configuration file for a tc Runtime instance. It configures the behavior of the servlet/JSP container.

By default, the server.xml file for a tc Runtime instance uses variable substitution for configuration properties that must be unique across multiple tc Runtime instances on the computer, such as HTTP and JMX port numbers. These variables take the form ${var}. For example, the variable for the HTTP port that the tc Runtime instance listens to is ${http.port}. The specific values for these variables for a particular tc Runtime instance are stored in the catalina.properties file, in the same directory as the server.xml file.
catalina.properties . Properties file that contains the tc Runtime instance-specific values for variables in the server.xml file.
context.xml . Configures the context that is loaded by all Web applications deployed to the tc Runtime instance.
web.xml . Default web.xml file that is loaded by all deployed Web applications, in addition to their individual web.xml files.
wrapper.conf . Windows only. Configures the Java Service Wrapper from Tanuki Software used to install the tc Runtime instance as a Windows service. The Wrapper correctly handles user log outs under Windows, service dependencies, and the ability to run services that interact with the desktop.
jmxremote.access and jmxremote.password . Configures the JMX users and passwords. The default JMX user, added at instance creation time unless you specify something different, is called admin with a password made up of a list of random characters.
logging.properties . Configures the logging system of the tc Runtime instance.

Setting Up Unix Users for tc Server

Subtopics

Creating Users and Groups for tc Server

The following procedure shows how to create a group and add user to it for tc Server on Red Hat Linux. The exact commands may be different on other operating systems.

Procedure

Log in as root and start a terminal session.
Use the groupadd command to create a new group. The following example creates a tcserver group:
```
groupadd tcserver 
```
Note that if you installed from RPM on RHEL, the tcserver group may already exist.
Use the useradd command to create a user to run tc Server instances. The following example creates a tcserver user in the tcserver group:
```
useradd tcserver -g tcserver 
```
You can include the -M option to prevent creating a home directory for the user and the -s /sbin/nologin option to prevent anyone from logging in as the tcserver user. If specifying /sbin/nologin as a shell to su to this user later -s /bin/bash needs to be added to the su command.
```
su - tcserver -s /bin/bash
```
Create the tc Server instance and run it as this user.
If you want to run multiple tc Runtime instances under separate user accounts on the same computer, repeat the previous step to create additional tc Server users.

Uninstalling tc Server - Typical Steps

You can uninstall one or more of the following components:

tc Runtime

Uninstallation of tc Server mostly entails removing the directories that contain the component files, although a few extra steps might be required, as described below.

Each section covers both Unix and Windows commands. The documentation uses Unix-like forward slashes (/) for directories; if you are on a Windows platform, change these to back slashes (\).

Warning: The procedures in this section describe how to completely remove the components of tc Server from your computer.

Uninstalling tc Server

The following procedure describes how to uninstall the tc Runtime and all its associated instances.

If currently running, stop all tc Runtime instances. See Starting and Stopping tc Runtime Instances.
Start a terminal window (Unix) or Command Prompt (Windows).
Windows only. Uninstall the service using the following command:
```
tcserver uninstall demo-instance
```
Remove the main tc Server installation directory. For example, if you installed Standard Edition, the delete command might look something like the following:
```
rm -rf /opt/vmware/tc-server 
```
Remove the instances by deleting the instances directory. This will remove the instances and any web apps and configuration swell.