VMware tc Server 5.0.x has many changes. For a complete list of changes please see the tc Server 5.0 Release Notes

The most significant changes are

  • Windows Service Wrapper Replaced - The service wrapper on Windows has been replaced. Please carefully read the notes on this change.
  • tc Runtime 10.1.x - tc Server now ships with tc Runtime 10.1.x which is compatible with ASF Tomcat 10.1.x
  • tcserver Command Line Options Changes - The --instances-directory, ``--templates-directory, and --runtimes-directory` command line options have been removed.
  • Java 11 Requirements for tcserver command - The tcserver command now requires a minimum of Java 11 to run. Note: In versions before 5.0.9 Java 17 was required, however, we lowered the minimum version to 11 based on customer feedback in 5.0.9.
  • JMX Changes - The JMXSocketListener class used by previous versions of VMware tc Server have been removed.
  • tcserver.properties - Changes to the configuration file used by tcserver

Windows Service Wrapper Replaced

The Tanuki Service Wrapper used in previous versions of VMware tc Server has been replaced with Apache Commons Daemon, which is the same wrapper provided by ASF Tomcat.

This is a major change and every attempt was made to reduce the impact of this change. It is highly recommended to perform testing prior to production upgrades to VMware tc Server 5.0.x.

The tcserver commands which interact with the wrapper service are

  • install
  • uninstall
  • start
  • stop
  • restart
  • status
  • info

tc Runtime instances created and installed with versions of tc Runtime prior to 5.0.0 will need to be uninstalled and recreated on Windows. There is not an automatic upgrade available.

tc Runtime Versions

The VMware tc Server 5.0.x distribution contains both tc Runtime 10.1.x and 9.0.x. ASF Tomcat 10.1.x has the javax.* to jakarta.* package rename.

tcserver Command Line Options Changes

The --instances-directory and --runtimes-directory command liine options have been removed. These properties should be set in tcserver.properties. If desired to set these properties on the command line the --tcs-property command line option can be used and using property names instances.directory or runtimes.directory.

Java 17 Requirements

The tcserver command now requires a minimum of a Java 17 JVM to run. While it is still possible to run an instance with a Java version older by specifying the --java-home it is highly recommended that all new instances be created with at least Java 17.

JMX Changes

The JMXSocketListener class used by previous versions of VMware tc Server have been removed. Replacement templates are offered

  • jmx-jaas
  • jmx-jaas-ssl

By default no JMX listener is provided.

These new templates use the JVMs built in JMX code and adds a JAAS provider which utilizes tc Server's property decoding for passwords. If encrypted passwords are not desired these templates do not need to be applied and standard JVM JMX properties can be used.

tcserver.properties changes

The default conf/tcserver.properties file has been renamed to conf/tcserver.default.properties. This allows users to know the conf/tcserver.properties customizations made to the file.

The user home directory location of tcserver.properties is $HOME/.tcserver/tcserver.properties

check-circle-line exclamation-circle-line close-line
Scroll to top icon