tc Server 4.1 has many changes. For a complete list of changes please see the tc Server 4.1 Release Notes
The most significant changes are
tcservercommand to make it even easier to manager
tc Runtime(Tomcat) instances.
.debpackages in addition to
.tar.gz, and .
tcservercommand now requires a minimum of Java 8 to run.
If you are unfamiliar with the new features of VMware tc Server 4.0 please see What's new in tc Server 4.0.
We have made enhancements to ease the use of VMware tc Server with Kubernetes. These include the following:
tc Runtime(Tomcat) instance may be created, an application deployed, and run with a single invocation of the
YAMLFile format support for an instance descriptor file - Previously, the instance descriptor file format was only a java
.propertiesfile. We have added
YAMLas a supported format.
tc Runtime(Tomcat) instance.
tc Runtime(tomcat) version is specified that isn't found locally the version will be checked for in the remote
tc Runtime Repositoryand if found that version will be downloaded and installed as part of the
tc Runtime(tomcat) instance creation process. Similarly, if a template name is specified that doesn't exist locally the
tc Server Template Repositoryis checked for that template and if found it is downloaded and installed as part of instance creation.
Please see our Kubernetes Howto
The following new commands have been added:
See tcserver Command Reference for a list of all commands.
We now provided
.deb packages for VMware tc Server and Runtimes. These are only available for download via VMware Tanzu Network
We have previously offered multiple options for obfuscating properties. These methods were difficult to use and may have required installing additional java software. We have have removed those methods (s2enc and tcenc) from
4.1.0. The only supported method is
tcserver command now requires a minimum of a Java 8 JVM to run. It is still possible to run an instance with a Java version older by specifying the
--java-home option and pointing to a Java 6 or 7 JRE.