- Apache Tomcat® requires cPanel & WHM version 76 or higher.
- We strongly recommend that only experienced Tomcat administrators use Tomcat.
Tomcat runs as a per-user private instance. This allows each cPanel account user to manage their own Tomcat services and configuration.
Each user's instance of Tomcat runs its applications as the user. The user can stop and start services, and manage their Tomcat configuration to suit their needs. This differs from the EasyApache 3 implementation, where users shared the Tomcat implementation.
The private instance approach increases the security of your system and operates on the user's designated ports.
A cPanel user must possess shell access to perform these actions.
When you enable Tomcat for a user account, the system sets up a blank environment for the user. The system creates the environment in the following location, where
user represents the user's username:
EasyApache 4 makes the following configuration changes from the default Tomcat 8.5 behavior to the
- Disables the shutdown port by default.
- Sets the
xpoweredByattribute of all Connectors to a
- Adds the
ErrorReportValueclass to all hosts with the
showServerInfovalue set to a
- Sets the following host attributes to a
To use the Tomcat instance, configure the desired applications in the
/home/user/ea-tomcat85/webapps directory. You can also set up a proxy to point to the app's location. For more information about proxies, read our Tomcat Proxies documentation.
We provide the
/opt/cpanel/ea-tomcat85/test.jsp test script that the user can use to test whether their Tomcat configuration works.
If you migrated from EasyApache 3 to EasyApache 4, the system configured each Tomcat user's domains in the user's
~/ea-tomcat85/conf/server.xml file. It also set up include files with a proxy to duplicate the EasyApache 3 proxy behavior.
You must set up Apache proxies manually. You can also configure Tomcat to mimic the EasyApache 3 proxy behavior in a personal instance. For more information, read our Tomcat Proxies documentation.
Manage services as a user
To manage services in Tomcat, users can use the the
cpuser_service manager and Ubic subsystem. This script adds services and allows users to easily stop and restart their services.
For example, run the following command on the command line to restart your Tomcat service:
If Ubic does not exist in your PATH, you must add it to your configuration. For example, you might add the following line to your
Jailshell users cannot see the status of their previously started Tomcat service. The default jailshell permissions only allow users to view their current session's processes. If they attempt to restart an already active service with Ubic, the system will launch a duplicate process.
If your desired Tomcat applications support it, we strongly recommend that you enable Tomcat's Security Manager. This adds extra security, but may break some applications. For more information, read Tomcat's Security Manager How To documentation.
There is no content with the specified labels