How to upload Tomcat application files through Plesk or FTP

If you are deploying a Java web application on a hosting account with Plesk, the two most common ways to upload your Tomcat application files are through the File Manager in Plesk or by using FTP. In both cases, the goal is the same: place your application package in the correct deploy path so Tomcat can read it and start the app successfully.

This guide explains where to upload files, how to handle WAR packages, how to upload source files when needed, and what to check if the application does not start after deployment. It is written for shared hosting and managed hosting environments where a Tomcat service or private JVM is controlled from Plesk, such as a Java hosting setup with a custom extension like My App Server.

Where Tomcat application files should be uploaded

Before uploading anything, identify the deployment method used by your hosting account. In a typical Tomcat hosting setup, the application can be deployed as:

  • a WAR file;
  • an unpacked application directory;
  • application resources such as JSP, class files, configuration files, or static content;
  • a custom deploy package prepared for a specific Java version or Tomcat instance.

The correct destination depends on how the service is configured in Plesk. In managed Java hosting, the deploy path is usually shown in the control panel or defined by the hosting platform. Always use the path provided for your Tomcat instance instead of uploading files into a random web root.

In general, the most common deploy locations are:

  • the application deploy folder, where Tomcat watches for WAR files or unpacked apps;
  • the web application root, if the service expects files to be placed directly into the deployed directory;
  • a staging folder, if you upload first and then move or publish the package.

If you are using a Plesk-based Java hosting service with a dedicated Tomcat instance or private JVM, the extension may expose the deploy path directly. If you do not see it, check the service details or hosting documentation before uploading.

Upload methods: Plesk File Manager vs FTP

There are two practical ways to upload Tomcat application files on a hosting platform:

1. Upload through Plesk File Manager

Plesk File Manager is the easiest option when you want to upload a WAR file, a small application package, or a few configuration files. It works directly in the browser and does not require an FTP client.

Use File Manager when you:

  • need a quick upload without installing extra software;
  • are replacing a small application package;
  • want to verify folders and file names visually;
  • need to upload a single WAR file or small set of files.

2. Upload through FTP

FTP is usually the better choice when your Tomcat application contains many files or a larger directory structure. It is also useful for repeated deployments and local development workflows.

Use FTP when you:

  • need to transfer an unpacked web application;
  • have many JSP, HTML, CSS, image, or property files;
  • prefer a file transfer client for faster bulk uploads;
  • manage updates frequently and want more control over file synchronization.

Both methods are valid. The right choice depends on the package size, deployment style, and the way your Tomcat service is configured in Plesk.

How to upload a Tomcat WAR file through Plesk

A WAR file is the most common way to deploy a Java web application on Tomcat. If your hosting account supports automatic deployment, uploading a WAR file to the correct directory may be enough for Tomcat to unpack and start the app.

  1. Log in to Plesk.
  2. Open the subscription or domain where the Tomcat application is hosted.
  3. Go to Files or the file manager section.
  4. Navigate to the deploy path for your Tomcat application.
  5. Click Upload and select the WAR file from your computer.
  6. Wait for the upload to finish completely.
  7. If your platform requires it, rename the file according to the application context rules.

After upload, Tomcat may need a short time to unpack and deploy the application. In some managed hosting environments, the service may refresh automatically. In others, you may need to restart the Tomcat service from the Plesk extension or the service control screen.

If the application is deployed under a custom context path, make sure the WAR file name matches the desired URL path. For example, a file named app.war often deploys as /app, while ROOT.war may be used for the site root, depending on the hosting configuration.

How to upload Tomcat application files through FTP

FTP is suitable when you want to upload the full content of a web application rather than a single WAR package. This is common when you work with unpacked application files, custom resources, or a deployment structure prepared locally.

Step 1: Collect your FTP details

Before connecting, make sure you have the following information from your hosting account:

  • FTP host name or server address;
  • FTP username;
  • FTP password;
  • port number, usually 21 for standard FTP or a different port for secure transfer methods;
  • the target folder for your Tomcat application.

If your hosting provider supports secure file transfer, use the recommended secure method whenever possible.

Step 2: Connect with an FTP client

Open your FTP client and connect using the credentials provided in Plesk or the hosting control panel. Once connected, navigate to the application deploy folder.

It is important to confirm that you are in the correct directory before uploading. On a Java hosting account, the Tomcat deploy path is often separate from the regular website document root.

Step 3: Upload the application files

Upload the full application structure exactly as your Tomcat project expects it. Typical files and folders may include:

  • WEB-INF;
  • WEB-INF/web.xml;
  • JSP pages;
  • static assets such as CSS, JavaScript, and images;
  • configuration files such as .properties or XML files;
  • the unpacked output of your build process.

Keep the directory structure intact. Tomcat depends on correct placement, especially for WEB-INF and related runtime files.

Step 4: Verify file permissions and ownership

After the upload, review permissions if the platform exposes them. A Tomcat application usually needs to read the deployed files, and in some setups it may need write access to specific folders such as logs, upload directories, or temporary storage.

Do not set overly broad permissions unless your hosting provider explicitly recommends them. If you are unsure, use the defaults for the hosting platform and contact support for the expected permission model.

Uploading a source-based Java web app versus a WAR package

The upload process can differ depending on whether you are deploying a ready-built WAR file or an unpacked project.

WAR deployment

A WAR file is usually the simplest option. It bundles the web application into a single archive and is easy to upload through Plesk or FTP. For many small and medium Java hosting projects, this is the preferred format.

Advantages of WAR deployment:

  • single file upload;
  • simpler version replacement;
  • cleaner deployment flow;
  • Tomcat can unpack the app automatically in many setups.

Unpacked deployment

An unpacked application means the files are already expanded into folders and files. This can be useful when you need to update only certain parts of the app or when your build process generates a directory tree instead of a single archive.

Advantages of unpacked deployment:

  • easy to inspect individual files;
  • simple to replace specific resources;
  • useful for debugging JSP and static content;
  • compatible with FTP workflows.

In a managed Tomcat hosting environment, WAR deployment is usually the safer and more predictable method. Use unpacked files when the platform documentation or your application requirements call for them.

Recommended file upload workflow for Plesk hosting

To avoid deployment issues, follow a controlled workflow when uploading Tomcat files.

  1. Prepare the build locally. Make sure the application compiles and the WAR or folder structure is valid.
  2. Back up the existing version. If the application is already live, download or archive the current files before replacing them.
  3. Choose the deploy method. Use Plesk File Manager for a single WAR or FTP for larger uploads.
  4. Upload to the correct deploy path. Confirm that you are using the Tomcat application folder, not the generic web root.
  5. Check the file name and context path. The file name may determine the URL path.
  6. Restart or refresh the service if needed. Some setups redeploy automatically, while others require a manual service action.
  7. Test the application. Open the site in a browser and review logs if the app does not start.

How My App Server and Plesk fit into the deployment process

In a Java hosting setup with a Plesk extension such as My App Server, the hosting platform typically gives you a practical way to manage Tomcat without handling a full enterprise application server environment. You can choose a supported Java version, run your own Tomcat instance, and deploy application files within the limits of the hosting plan.

This is useful when you need:

  • simple control over a private JVM;
  • Tomcat service management from Plesk;
  • deployment of WAR or JSP-based applications;
  • a separate runtime environment for your site or app;
  • basic service control without managing a full server stack.

In this model, file upload is only one part of the process. The selected Java version, service state, and deployment path all affect whether the application works correctly after upload.

Common mistakes when uploading Tomcat application files

Many deployment problems come from a small number of predictable mistakes. Check the following if your application does not work after upload.

  • Uploading to the wrong directory — Tomcat cannot deploy files that are placed in the regular website folder instead of the application deploy path.
  • Incorrect file name — The WAR name may define the application context.
  • Broken folder structure — Missing WEB-INF or incorrect nesting can prevent the app from starting.
  • Incomplete upload — A partial transfer can leave the application in an invalid state.
  • Wrong permissions — Tomcat may not be able to read or write the required files.
  • Using the wrong Java version — The app may depend on a specific Java runtime not selected in the hosting control panel.
  • Leaving old files behind — Stale classes or resources can interfere with the new version.

When replacing an application, it is often safer to remove the old deployment before uploading a new one, unless your platform supports clean redeploying automatically.

Best practices for uploading Tomcat files on hosting platforms

Use these best practices to make deployment smoother and reduce downtime:

  • keep a local copy of every deployed version;
  • prefer WAR uploads for standard Tomcat deployments;
  • use FTP when the application has many files or frequent updates;
  • avoid changing the deploy path unless you know the hosting layout;
  • test on staging first if your hosting plan includes it;
  • match the application’s Java version with the selected runtime;
  • review Tomcat or application logs after every deployment;
  • restart the service only when needed and according to the control panel instructions.

For managed hosting, a stable file-upload routine is more important than complex automation. Small, controlled changes are easier to troubleshoot and less likely to break a live application.

How to check whether the upload worked

After uploading the files, confirm that the application is deployed correctly.

  1. Open the application URL in a browser.
  2. Check whether the expected homepage or JSP page loads.
  3. Review Tomcat or application logs for deployment errors.
  4. Confirm that the application context path matches the deployed package name.
  5. Verify that any database, configuration, or environment settings are present.

If the site returns an error, the problem may not be the file upload itself. It could be a Java version mismatch, a missing dependency, an incorrect context, or a service that is not running yet.

FAQ

Can I upload a Tomcat application through Plesk without FTP?

Yes. If your hosting account includes Plesk File Manager and the correct deploy path is available, you can upload a WAR file or application files directly in the browser.

Is FTP better for Tomcat application deployment?

FTP is usually better for larger or unpacked applications because it handles many files more comfortably. For a single WAR file, Plesk File Manager is often faster and simpler.

Should I upload the WAR file or the unpacked folder?

For most Tomcat hosting setups, a WAR file is the preferred method. Use an unpacked folder if your application build or hosting instructions require it.

Where should I place the application files?

Place them in the Tomcat deploy path shown in your Plesk hosting environment. Do not assume the regular website root is the correct folder for Java applications.

Will Tomcat deploy the app automatically after upload?

In many hosting setups, yes. In others, you may need to refresh, redeploy, or restart the service from Plesk. Check the service control screen after upload.

What if my app uses JSP and servlet classes?

Make sure the full web application structure is uploaded correctly, including WEB-INF and all required runtime files. JSP hosting and servlet hosting still rely on the correct Tomcat deploy layout.

Can I use this method for private JVM hosting?

Yes. If your hosting account provides a private JVM and Tomcat service through Plesk, the same upload principles apply. The exact folder and service control steps may differ by account configuration.

Conclusion

Uploading Tomcat application files through Plesk or FTP is straightforward once you know the correct deploy path and the preferred packaging format. For most Java hosting accounts, a WAR file uploaded through Plesk is the simplest method, while FTP is better for unpacked applications and larger file sets.

The key points are to use the correct Tomcat folder, keep the application structure intact, match the Java version to the app, and verify the deployment after upload. In a managed hosting environment with a Plesk-based Java service such as My App Server, this approach gives you practical control over your Tomcat application without unnecessary complexity.

  • 0 Users Found This Useful
Was this answer helpful?