The last line above sets the SGID bit on the folder. Our regular user should already be member of this group and can thus read log files.

$ sudo mkdir /var/log/tomcatĪdm is a group for local system monitoring tasks. $ sudo useradd -r -s /usr/sbin/nologin tomcatĪdministrators expect services to log to a dedicated folder under /var/log, so let's create one for Tomcat. This user will be running the Tomcat process. $ sudo ln -s /usr/local/apache-tomcat-8.0.32/ /usr/local/tomcatĬreate a system user and group named tomcat. We can switch this link to another version of tomcat without having to change Systemd's unit file (that we create in a later section) and environment variables that reference the folder. $ sudo mv apache-tomcat-8.0.32 /usr/localĬreate a symbolic link /usr/local/tomcat pointing to the installation folder. It is only a first step to lock down permissions in the installation folder, there will be more work on this later. A umask of 022 strips write permission from group and other users. Setting umask affects the permissions of newly created files when we unpack the Tar file. Set the umask, then unpack Tomcat and move it to /usr/local. At the time of writing it's apache-tomcat-8.0.32.tar.gz. Head over to and download the latest Tomcat 8 tar.gz. I'm going to assume that Oracle's Hotspot JVM is already installed. So instead we are going to install Tomcat's binaries directly from Apache Software Foundation.

The security team at Canonical is not responsible for sync'ing these packages with security patches from their upstream Debian maintainers. Installing Tomcat from Ubuntu's package repository would be very convenient, but the Tomcat package lives in the Universe repository which means that it is community maintained. When the installation is done, Tomcat will be running as a service that is managed with Systemd. In this post we go through the installation of Tomcat 8 on Ubuntu 15.10 for production use.

Localhost port for apache tomcat 8