When you upload a Tomcat application on a managed hosting account, the main goal is to place the correct files in the right deploy path and keep the application structure compatible with the Tomcat service that runs under Plesk. In most cases, you will work with a WAR file, a JSP/Servlet application, or an unpacked application folder. If your hosting plan includes My App Server, you can manage a private Tomcat instance and deploy your Java application without needing full server administration access.
For UK hosting customers, the process is usually simple: connect through the Plesk File Manager or through FTP, upload the application package, and place it in the correct directory for the selected Tomcat service. If you use a ready-made Java/Tomcat version installed through My App Server, the platform already provides the deploy structure and service control needed for day-to-day application deployment.
Where Tomcat application files should be uploaded
The correct upload location depends on how your Tomcat instance is configured in Plesk. On managed Java hosting, the deploy path is typically linked to a specific application service and may be different from a normal website document root.
- WAR deployment folder - used for packaged Java web applications.
- Application root folder - used for unpacked web app files such as
WEB-INF, JSP pages, static assets, and configuration files. - Private JVM or custom app server path - used when My App Server creates a separate runtime for the account or subscription.
If you are not sure where your files should go, check the service details in Plesk first. With My App Server, the selected Tomcat service usually shows the relevant application path, control options, and any service-specific limits.
Upload Tomcat files through Plesk File Manager
Plesk File Manager is the safest option if you want to upload files directly through the control panel. It is useful for small deployments, hotfixes, or when you need to check paths before transferring the full application.
Steps to upload using Plesk
- Log in to your Plesk control panel.
- Open the subscription or domain that uses the Tomcat service.
- Go to Files or File Manager.
- Navigate to the deploy path assigned to your Tomcat application.
- Click Upload and select the WAR file or application files from your computer.
- Wait for the upload to finish completely.
- If needed, extract the archive or replace the existing files carefully.
For a WAR-based application, upload the WAR package into the folder expected by the Tomcat service. In some setups, Tomcat will deploy the application automatically after the upload. In others, you may need to trigger a restart or redeploy through the service control area.
When to use File Manager instead of FTP
- When you only need to upload a small update.
- When you want to confirm the correct deploy folder before transferring files.
- When you do not have an FTP client available.
- When you need a quick fix for a configuration or JSP change.
File Manager is convenient, but for larger Java applications or frequent updates, FTP is usually more efficient.
Upload Tomcat files through FTP
FTP is the preferred method for larger file sets, repeated deployments, and direct control over application structure. It is especially useful when your Java project contains many static assets, JSP pages, libraries, or unpacked web application directories.
Before you connect by FTP
Make sure you have the following details from your hosting account:
- FTP server hostname
- FTP username
- FTP password
- FTP port, if your hosting setup uses a non-default value
You can use any standard FTP client supported by your workflow. If SFTP is available in your hosting plan, it is generally a better choice for secure file transfer.
FTP upload steps
- Open your FTP client and connect to the hosting account.
- Go to the Tomcat application deploy path shown in Plesk or in My App Server.
- Upload the WAR file or the unpacked application folder.
- Preserve the directory structure of the application.
- Check that file names, folder names, and case-sensitive paths are correct.
- Wait for the transfer to complete before restarting the service or testing the app.
When uploading unpacked files, be careful not to place the application one level too deep. A common problem is uploading the full project folder instead of the actual web root contents. In Tomcat deployments, that can break JSP resolution, servlet mappings, and access to the WEB-INF directory.
WAR file vs unpacked application files
Both deployment styles are supported in many Tomcat hosting setups, but each one has different advantages.
WAR file deployment
A WAR file is the simplest option for most Tomcat applications.
- Easier to upload and replace.
- Cleaner deployment process.
- Good for repeatable releases.
- Often supported by automatic Tomcat deployment.
Use a WAR file if your application is built and packaged through Maven, Gradle, or another build system.
Unpacked application deployment
An unpacked deployment is useful when you need direct file access for JSP pages, static files, configuration changes, or debugging.
- Better for quick edits during development or troubleshooting.
- Useful when you want to inspect the directory structure.
- Allows manual adjustment of specific files.
However, if you upload unpacked files, you must be more careful with paths, permissions, and folder structure. Incorrect placement is one of the most common reasons Tomcat applications fail to start correctly.
How My App Server affects file upload and deployment
My App Server is the Plesk extension used by ITA for Java hosting and private JVM management inside a shared hosting account. It allows you to install and control a Tomcat instance, choose from available Java versions, and deploy application files in a controlled environment.
When you use My App Server, the application files are usually linked to a specific service rather than to a generic website folder. This provides a more predictable deployment process for Java hosting, JSP hosting, and servlet hosting.
Typical workflow with My App Server
- Open the service in Plesk.
- Check the selected Tomcat or Java runtime version.
- Confirm the application path or deploy directory.
- Upload the application files through Plesk or FTP.
- Restart or reload the service if the application requires it.
- Test the site through the configured domain or application URL.
This approach is practical for small and medium Java applications that need a private runtime without the complexity of full enterprise application server administration.
File structure requirements for Tomcat applications
Tomcat expects a clear and valid web application structure. If your upload does not match that structure, the app may deploy but still return errors, or it may fail to start entirely.
Common structure for an unpacked web app
WEB-INF/WEB-INF/web.xmlWEB-INF/classes/WEB-INF/lib/- JSP files in the application root or in defined subfolders
- Static assets such as CSS, JavaScript, and images
If your application uses a WAR file, Tomcat handles much of this structure automatically during deployment. If you upload the files manually, keep the layout exactly as your application expects.
What not to upload into the wrong folder
- Source code folders that are not part of the deployable web application.
- Build output mixed with local development files.
- Extra project-level folders above the web root.
- Files intended only for your build server or IDE.
Uploading the wrong project tree can cause missing resources, invalid servlet mappings, or class loading problems.
Permissions and ownership checks after upload
After uploading Tomcat application files, verify that the files can be read by the service account running the application. On managed hosting, permissions are usually handled for you, but incorrect manual uploads can still create problems.
Check the following
- The uploaded files are visible in the correct deploy directory.
- The application owner matches the hosting account or service context.
- File permissions are not too restrictive.
- Executable or runtime files are not blocked by a bad upload mode.
If the application fails after deployment, check the log files in Plesk. Logs often reveal whether the issue is a missing file, a permission problem, a bad classpath, or a deployment error from Tomcat.
Updating an existing Tomcat application
When replacing an existing deployment, do not simply upload new files on top of an unknown structure. A clean update process reduces the risk of stale classes, cached JSP output, and conflicting library versions.
Recommended update process
- Back up the current application files.
- Stop or pause the Tomcat service if the application requires it.
- Remove or archive the previous version if the deployment method calls for a clean replacement.
- Upload the new WAR file or updated application folder.
- Restart the service.
- Check the application logs and test key pages.
If the application uses a WAR file, replacing the WAR may be enough. If you use unpacked files, verify that outdated files are removed, especially when classes, libraries, or JSP pages have changed.
Common upload problems and how to avoid them
The application opens a default page instead of Tomcat app content
This usually means the files were uploaded to the wrong directory, or the web root does not match the Tomcat deploy path. Confirm the folder shown in Plesk or My App Server.
Tomcat does not detect the new version
The service may need a restart or redeploy. Some managed environments cache the deployed application until the service is reloaded.
JSP pages return errors after upload
Check file placement, encoding, and whether the JSP files are inside the correct application root. Also verify that dependencies and libraries were uploaded correctly.
Static files load, but servlets fail
This often points to an issue in WEB-INF, servlet mapping, or a missing class in WEB-INF/classes or WEB-INF/lib.
Old content still appears after replacement
Clear browser cache and, if needed, restart the Tomcat service. For unpacked deployments, remove obsolete files so the old version is not still being served.
Best practice for Tomcat file deployment in Plesk
For most UK hosting customers, the most reliable workflow is:
- Use Plesk to confirm the correct deploy path.
- Upload via FTP for large releases and File Manager for quick fixes.
- Keep a clean WAR build for production-style deployments.
- Use unpacked files only when you need direct access to application content.
- Check the Tomcat service after upload and review logs if anything behaves unexpectedly.
This approach works well with private JVM hosting and small to medium Java applications where control panel access, simple deployment, and practical service management are more important than complex enterprise architecture.
FAQ
Can I upload a Tomcat application through Plesk?
Yes. If your hosting plan includes My App Server or another Tomcat-enabled setup, you can upload the application through Plesk File Manager and place it in the assigned deploy path.
Is FTP better than File Manager for Tomcat files?
FTP is usually better for larger applications or frequent updates because it is faster and easier to manage. File Manager is useful for smaller uploads and quick changes.
Should I upload a WAR file or unpacked files?
A WAR file is usually the simplest and safest choice for standard Tomcat deployment. Unpacked files are useful when you need to edit JSP pages or inspect the application structure directly.
Do I need to restart Tomcat after uploading files?
Sometimes yes. If the application does not redeploy automatically, restart or reload the service in Plesk or My App Server to apply the changes.
Where can I find the correct upload path?
Check the service details in Plesk. My App Server usually shows the application path, deployment location, and service control options for the selected Tomcat instance.
What should I do if the application uploads successfully but does not work?
Check the Tomcat logs, confirm the file structure, verify permissions, and make sure the application was uploaded to the correct deploy directory.
Conclusion
Uploading Tomcat application files through Plesk or FTP is straightforward once you know the correct deploy path and deployment format. For hosted Java applications, the safest method is to use the Tomcat service configured in Plesk, upload either a WAR package or a properly structured application folder, and confirm that the runtime picks up the changes.
With My App Server, you can manage a private Tomcat instance, choose an appropriate Java version, and handle application deployment from a single control panel. That makes it a practical option for JSP hosting, servlet hosting, and Java web apps that need simple control without heavy server administration.