How to upload JSP application files through Plesk or FTP in the UK

When you need to deploy a JSP application on a Plesk-based hosting account, the main task is to place the files in the correct document root or application directory, then make sure the Tomcat or Java runtime picks them up from the right path. In a managed hosting environment, this usually means using either the Plesk File Manager or FTP/SFTP, depending on how you prefer to upload and maintain your application package.

For JSP hosting, the upload method is only one part of the process. You also need to understand where the web root is, how WAR or application files are deployed, and how your Java service is connected to the domain. If you are using a hosting platform with a custom Java extension such as My App Server, you can typically manage the service, Java version, and application path directly from Plesk without needing full server access.

Where JSP application files should be uploaded

Before you transfer anything, confirm the deploy path for your domain or subdomain. In most Plesk setups, the website root is located under the subscription’s document root, often something similar to httpdocs or an application-specific folder configured for Tomcat deployment. For JSP applications, the correct location depends on whether you are uploading:

a plain web application with JSP, HTML, CSS, and static resources;
a packaged WAR file;
an exploded application directory;
supporting libraries, configuration files, or assets used by your app.

If you are using a hosted Java service with a private JVM or Tomcat instance, the application directory may be separate from the normal website files. In that case, the deploy path shown in Plesk or in the Java management extension should be used exactly as provided. Uploading to the wrong folder is one of the most common reasons JSP pages do not load correctly.

Upload JSP files through Plesk File Manager

Plesk File Manager is the simplest option when you want to upload a small number of files, test a deployment, or replace a few JSP pages quickly. It is useful for day-to-day file management, especially when you do not want to open an FTP client for a minor change.

Steps to upload through Plesk

Sign in to your Plesk control panel.
Open the subscription, domain, or application space linked to your JSP site.
Go to Files or File Manager.
Navigate to the deploy path for the application, such as the website document root or the Tomcat application directory.
Use Upload to add your files, or upload a ZIP/WAR archive and extract it if the platform allows it.
Check file names, folder structure, and permissions after upload.

For JSP hosting, structure matters. If your application expects resources in a specific folder layout, preserve that layout during upload. For example, the JSP files may need to sit next to WEB-INF, WEB-INF/lib, WEB-INF/classes, or other required directories. If the structure changes, the application may deploy but still fail at runtime.

When File Manager is the best choice

you are uploading a small application or a few updated JSP files;
you need to replace a file quickly without using a desktop client;
you want to inspect the server folder structure before deploying;
you are checking whether a WAR file unpacked correctly.

Upload JSP application files through FTP or SFTP

FTP is the preferred method when you are uploading a larger Java application, many static assets, or a full source tree. It is also better for repeated deployments because it is easier to manage from a local development environment. In modern hosting setups, SFTP is usually the safer option when available.

What you need before connecting

FTP or SFTP hostname;
username and password for the hosting account;
port number, if different from the default;
the correct remote folder for the application;
an FTP client such as FileZilla, WinSCP, or a similar tool.

If you are on a managed hosting account with Plesk, the FTP user is often created from the control panel. Make sure the account has access to the folder where the JSP application must be deployed. If you are using a My App Server setup, confirm whether the deployment target is the website root, a Tomcat webapps folder, or another path defined by the extension.

Steps to upload through FTP or SFTP

Open your FTP client and create a new connection.
Enter the host, username, password, and port.
Connect to the account and wait for the directory listing.
Browse to the application deploy path on the server.
Upload the JSP files, web folders, libraries, and configuration files.
Verify that the transfer completed successfully.

For repeated deployments, many developers upload from the local build output rather than from the source folder. This helps avoid unnecessary files such as IDE metadata, temporary build outputs, or test resources that should not go live.

How to handle WAR files, exploded apps, and plain JSP directories

JSP applications can be uploaded in different formats, and the best method depends on how your Java hosting environment is set up. In a Plesk environment with Tomcat, the most common options are a packaged WAR file or an unpacked application directory.

Uploading a WAR file

A WAR file is a standard Java web application archive. It is often the cleanest way to deploy a JSP application because it keeps the application bundled in a single file. In many Tomcat-based setups, uploading a WAR file to the correct deploy path triggers automatic deployment.

Use a WAR file when:

you want a single deployment artifact;
your build process already generates WAR packages;
the hosting platform supports WAR-based deployment through Tomcat;
you want to avoid manually placing many files one by one.

After upload, check whether the application is unpacked automatically and whether the expected context path appears in Plesk or in the Java service management area.

Uploading an exploded application directory

Some applications are deployed as a folder structure rather than as a WAR file. This can be useful when you need to change a few files often or when the application is designed to run from a directory. In that case, keep the exact directory layout required by your application server.

Typical contents may include:

JSP pages;
static content such as CSS, JavaScript, images, and downloads;
WEB-INF and its subfolders;
compiled classes or libraries;
configuration files and environment-specific resources.

Uploading plain JSP files

If your site is a simple JSP-based application or a smaller managed web app, you may only need to upload individual JSP files and supporting folders. Even in that case, the files should still be placed in the correct runtime path. Plain JSP pages are not usually enough on their own unless the server is already configured to interpret them in the chosen web root or app context.

Using My App Server for JSP and Tomcat deployment

If your hosting account includes a Java extension such as My App Server, you can usually manage the application more cleanly from Plesk. This is useful for JSP hosting, Tomcat hosting, servlet deployment, and private JVM use cases where you want separate runtime control inside a shared hosting account.

In this model, the control panel may let you:

install a ready-made Tomcat version with one click;
choose a Java version supported by the application;
set or view the deploy path;
start, stop, or restart the service;
upload application files into the configured application root;
manage a private JVM for that site or subdomain.

This approach is practical for small and medium Java applications that need reliable deployment without building a full enterprise Java infrastructure. It gives you more control than a basic static website hosting account, while keeping the workflow manageable from Plesk.

Typical deployment flow with My App Server

Install or activate the Java service from the Plesk extension.
Select the required Java or Tomcat version.
Confirm the application path for the domain.
Upload the WAR, JSP files, or application directory.
Restart the service if required.
Test the application in the browser and review logs if needed.

File permissions and ownership checks

After uploading JSP files, always verify file permissions. Incorrect permissions can prevent Tomcat or the web server from reading your application files. In a managed hosting platform, the exact permission model depends on how the account is configured, but the general rule is that the web service must be able to read the files and the application must be able to write only where necessary.

Check the following:

the uploaded files are readable by the application runtime;
directories have the correct execute/search permission;
temporary or upload folders are writable only if the application needs them;
ownership matches the hosting account policy.

If you are unsure, avoid changing permissions broadly. In a Plesk environment, it is better to follow the platform’s standard file management behavior rather than applying manual settings that may break the application.

Common deployment mistakes

Most JSP upload problems are caused by path errors or incomplete application packaging rather than by the upload tool itself. The following issues are the most common:

Wrong folder uploaded — files are placed in the website root instead of the Java deploy path, or vice versa.
Incorrect app structure — WEB-INF or required classes are missing or nested one level too deep.
Mixed old and new files — an incomplete overwrite leaves outdated classes or JSP pages in place.
WAR uploaded but not deployed — the archive is present on the server, but Tomcat has not unpacked or reloaded it.
Permission issues — the runtime cannot read the application files or write to its working folders.
Version mismatch — the app requires a different Java version than the one currently selected.

If the application worked locally but not after upload, compare the local build structure with the files on the server. Even small differences in path, case sensitivity, or library placement can affect JSP applications.

How to verify that the upload worked

After the files are uploaded, test the site carefully. Do not assume that a successful transfer means the application is deployed correctly. A JSP application may upload without errors and still fail due to context path, runtime, or configuration issues.

Check these points:

open the site or application URL in a browser;
confirm that the expected JSP page loads;
test a page that depends on backend logic, not only static content;
review Tomcat or application logs if the page does not respond correctly;
restart the Java service if your hosting setup requires it after a file change.

If your hosting plan includes service control in Plesk, use it to restart the app server when needed. That can help the runtime pick up new files, new classes, or updated configuration after deployment.

Recommended workflow for UK hosting customers

For UK-based customers using Plesk hosting for Java and JSP applications, a practical workflow is to use File Manager for small changes and FTP or SFTP for full deployments. This gives you flexibility without making the process more complex than necessary.

A simple workflow is:

develop locally and build the application into a WAR or deployable folder;
confirm the correct deploy path in Plesk;
upload the package through FTP/SFTP or File Manager;
check permissions and ownership if needed;
restart the service if the platform requires it;
test the live JSP pages and any related servlets or static assets.

This approach works well for small and medium JSP hosting projects that need clear control over files and application paths, without requiring advanced enterprise deployment features.

FAQ

Can I upload JSP files directly to the website root?

Only if your hosting setup is configured to serve JSP from that location. In many Java hosting environments, JSP files should be deployed to a Tomcat application path or a specific app directory shown in Plesk. Always follow the deploy path provided by the control panel or Java extension.

Is FTP better than File Manager for JSP deployment?

FTP or SFTP is usually better for full application uploads, large file sets, or regular deployments. File Manager is convenient for small edits, quick replacements, or checking folders inside Plesk. Both methods are valid, but they serve different tasks.

Should I upload a WAR file or the extracted files?

If your hosting platform supports WAR deployment through Tomcat, a WAR file is often the easiest option. If your application is designed for a folder-based deploy path, then upload the extracted files exactly as required. Use the method that matches your build output and server setup.

Do I need to restart the Java service after uploading?

Sometimes yes. If your platform caches the application, or if the app server does not auto-reload changes, a restart may be needed. In Plesk with My App Server, service control is typically available from the extension, making this straightforward.

What if my JSP page uploads but shows an error in the browser?

Check the deploy path, Java version, folder structure, permissions, and application logs. A browser error after upload often means the files are present but the runtime cannot load them correctly.

Can I manage different Java versions for different apps?

In a hosting setup with My App Server or a similar Plesk extension, you may be able to install and manage specific Java/Tomcat versions for a given application. That is useful when different projects require different runtime levels.

Conclusion

Uploading JSP application files through Plesk or FTP is straightforward once you know the correct deploy path and the expected application structure. For small changes, Plesk File Manager is often the fastest option. For full JSP or Tomcat deployments, FTP or SFTP is usually more efficient and easier to repeat.

In a Java hosting environment with My App Server, you gain additional control over the Java version, Tomcat service, and application path, which makes deployment more practical for JSP, servlet, and WAR-based applications. The key is to upload to the right folder, preserve the application structure, and verify the service after deployment. That simple workflow prevents most common issues and keeps your Java site running reliably.

How to upload JSP application files through Plesk or FTP in the UK