Tomcat Manager – Control-WebPanel Documentation

Java Apps (Tomcat) gives your account its own private Apache Tomcat instance for running Java web applications (.war files and JSP sites). The instance runs under your account — isolated from every other account on the server — so your Java apps, their memory and their files are yours alone.

Where to find it: Addons → Java Apps (Tomcat) (also shown under Domains on some themes).

Your hosting provider must install the CWP Tomcat engine and at least one Tomcat version, and enable Tomcat in your hosting package. If you see Tomcat is not available in your package, ask your provider.

Turn on your Tomcat

On the Your Tomcat card, choose a Tomcat version and click Enable. The panel starts a private instance that belongs to your account and shows it as Running on its own port. From then on you can deploy apps into it. Use Disable Tomcat to stop and (optionally) remove the instance when you no longer need it.

Deploy an app (.war)

In the Deploy an app card:

Application name (URL path) — the path the app will live under, for example myapp (served at /myapp). Leave it as the root to deploy the app at the top level.
WAR file — choose the .war file from your computer.

Click Deploy. The file is placed in your own Tomcat’s webapps folder and your instance unpacks and starts it automatically. Deployed apps appear in the Deployed apps list, where you can remove any of them.

Point a domain at an app

By default the app is reached on your Tomcat’s own port. To publish it on one of your domains, use the Point a domain at an app card:

Domain — one of your domains or sub-domains.
App — the application to serve, or leave it empty to serve the whole Tomcat at the domain root.

Click Bind. The panel points the domain to your Tomcat instance; after a short moment the web server reloads and the domain serves your Java app. Changes to the web server can take a few seconds to take effect.

Good to know

Each account’s Tomcat runs as that account — one account can never see or reach another account’s Java apps or files.
A running Java instance uses real memory and processes; your provider may limit how many Java apps your package can run.
If a deploy or bind fails right after you enable Tomcat, give it a moment and try again — the instance may still be starting.