To deploy or update a JSP project on a hosting account, you usually need a separate FTP account with access only to the application files and deploy path. In a Plesk-based Java hosting environment, this is the safest way to upload WAR files, JSP pages, static assets, configuration files, and supporting resources without giving full access to the whole subscription.
If your hosting plan includes My App Server, you can use FTP together with the private Tomcat/JVM setup to manage your Java application files more efficiently. This is especially useful for JSP hosting, servlet hosting, and smaller Java applications that are deployed through Plesk and a controlled file structure.
Why create a separate FTP account for a JSP project
A dedicated FTP account gives you more control over who can access the project directory. Instead of using the main subscription login, you can create an account that is limited to a specific folder such as the application root, deploy path, or web content directory. This is useful when:
- you want to separate development and production access;
- multiple team members need file upload access;
- an external developer needs to deploy JSP, HTML, CSS, JS, or image files;
- you want to reduce risk by restricting access to only one project folder;
- you need a simple workflow for updating a WAR deployment or static resources.
For JSP projects, FTP is often used to upload source files, web assets, and deployment packages to the exact path where Tomcat or your Plesk application setup expects them. In a managed hosting environment, this helps keep file handling organized and predictable.
Before you start
Make sure you have access to the hosting control panel and that your subscription already has the correct Java hosting setup enabled. In an ITA hosting environment, this may mean that My App Server is installed and your Tomcat version is already selected or configured for the site.
You should also know the target folder for the project. Common examples include:
- a document root used by the web application;
- a deploy path for WAR files;
- a directory mapped to the application in Plesk;
- a folder for JSP source files and static resources.
If you are not sure which path is correct, check the application settings in Plesk or the deployment instructions for your JSP project.
How to create an FTP account in Plesk
The exact menu names can vary slightly depending on the hosting platform, but the process is usually straightforward.
1. Log in to Plesk
Sign in to your Plesk control panel using your hosting account credentials. If you are working under a managed hosting setup, you may already see your domain and application tools in the main dashboard.
2. Open the FTP accounts section
Find the section for FTP access or FTP accounts. In many Plesk interfaces, this is available under the domain management area or file management tools.
3. Click to add a new FTP account
Select the option to create a new FTP user. You will usually need to define the following:
- FTP username - the login name for the account;
- Password - a strong password for secure access;
- Home directory - the folder the account will be allowed to access;
- Permissions or access scope - depending on the control panel structure.
4. Set the correct home directory
This is the most important step for a JSP project. Choose the exact directory that contains your application files or deployment package. Depending on your setup, this may be:
- the application root;
- the web application folder;
- a deploy directory used by Tomcat;
- a shared folder for project assets.
For security and clarity, avoid giving FTP access to the whole subscription unless it is really necessary. A limited folder structure helps prevent accidental changes outside the project.
5. Save the FTP account
After entering the details, save the account. Plesk will create the user and apply the directory restrictions you selected. You can now use this login in an FTP client such as FileZilla, Cyberduck, or another SFTP/FTP tool supported by your workflow.
Recommended folder structure for JSP hosting
When you manage JSP hosting through FTP, a clear folder structure makes deployment easier. A practical layout may look like this:
- /app - application files;
- /WEB-INF - Java web application configuration and classes;
- /public or /web - visible front-end resources;
- /static - CSS, JavaScript, and images;
- /deploy - WAR files or build output, if your setup uses a separate deploy path.
The exact structure depends on how My App Server and Tomcat are configured for your subscription. In many cases, the project is deployed into a path connected to the Tomcat instance, while static files and JSP pages are uploaded to the corresponding application directory.
How FTP works with My App Server and Tomcat
In a Java hosting environment with My App Server, FTP is typically used to manage the files that your private Tomcat instance serves. The control panel handles the service side, while FTP handles the file side. Together, they provide a practical setup for JSP hosting without requiring direct server administration.
This is useful when you need to:
- upload a WAR archive for deployment;
- update JSP pages after a code change;
- replace configuration files or resource bundles;
- publish static content used by the Java application;
- prepare build output from your local development environment.
If your project uses a private JVM and a dedicated Tomcat version, FTP lets you push files into the correct application path while the service remains controlled from Plesk. This keeps your deployment process simple and avoids unnecessary access to lower-level server tools.
Security best practices for FTP accounts
Because FTP accounts can access live application files, it is important to configure them carefully.
Use a separate account for each person or project
Do not share one FTP login across multiple developers if you can avoid it. Separate accounts make it easier to track changes and revoke access when needed.
Limit access to the smallest possible directory
Give the account access only to the JSP project folder or deploy path. This reduces the chance of accidental file changes elsewhere in the hosting account.
Use strong passwords
Create a password that is difficult to guess and avoid reusing credentials from other services.
Prefer encrypted file transfer if available
If your hosting platform supports SFTP or FTPS, use it instead of plain FTP. Encrypted transfer helps protect login details and file contents during upload.
Review access after deployments
When a project is handed over or a temporary developer leaves the team, remove or disable that FTP account. Keeping only active accounts reduces unnecessary exposure.
Common use cases for JSP project FTP access
FTP is practical for everyday tasks in JSP and Tomcat hosting. Typical uses include:
- uploading a new build of a JSP application;
- editing template files or view pages;
- replacing static resources such as CSS, fonts, and images;
- updating web.xml or other configuration files when needed;
- moving a packaged application into a deploy directory for Tomcat to load.
For small and medium-sized Java projects hosted in Plesk, this is often enough to manage releases without needing a more complex CI/CD pipeline.
Troubleshooting FTP account issues
If the new FTP account does not work as expected, check the following points.
The username or password is incorrect
Make sure the login details were entered exactly as created in Plesk. Passwords are case-sensitive.
The home directory points to the wrong folder
If you can connect but cannot see your application files, the account may be mapped to the wrong directory. Update the home folder in the FTP settings and test again.
Permissions are too restrictive
In some hosting setups, the account may be able to log in but not upload files. Check directory permissions and make sure the project folder allows write access where necessary.
The project is deployed elsewhere
For JSP hosting, the upload folder may not be the same as the live application path. Verify whether your Tomcat deployment uses a separate deploy directory or a mapped application root.
The Tomcat service has not reloaded the latest files
If you uploaded updated JSP or configuration files but do not see the changes, the application may need a reload or restart from the service control area in Plesk. In My App Server setups, service control is often managed from the panel rather than manually on the server.
FTP account setup example for a JSP application
Here is a practical example. Suppose you have a JSP project called myapp and the application files are stored in a folder used by your Tomcat deployment. You can create an FTP account such as:
- Username: myapp-deploy
- Password: strong unique password
- Home directory: /httpdocs/myapp or the configured deploy path
With this setup, the developer can upload updated JSP files, static assets, and build artifacts directly to the correct project folder, while the rest of the hosting account stays protected.
When to use FTP and when to use the control panel
FTP is best for file transfer and routine project updates. The control panel is better for application-level tasks such as:
- starting or stopping the Java service;
- choosing a Tomcat version;
- managing the private JVM;
- reviewing service limits;
- configuring the application server environment.
In a Plesk-based Java hosting setup, these two layers work together. Use Plesk for service and deployment settings, and use FTP for the actual file upload process.
Frequently asked questions
Can I create more than one FTP account for the same JSP project?
Yes. In most Plesk hosting environments, you can create multiple FTP accounts and point them to the same project folder or to different subfolders. This is useful when different people handle development, testing, or content updates.
Should I give FTP access to the full hosting account?
Usually no. For a JSP project, it is better to limit access to the application directory or deploy path. Full access is only necessary in special cases and should be used carefully.
Can I upload JSP files directly with FTP?
Yes, if your deployment structure supports it. Many JSP hosting setups allow direct upload of JSP pages and related files. However, some projects use WAR deployment or a specific Tomcat path, so the correct folder matters.
Do I need FTP if I already have My App Server?
My App Server handles the Java runtime and service control, but FTP is still needed for file management in many workflows. It is the practical way to upload application files, assets, and deployment packages.
What is the difference between FTP and SFTP?
FTP is the traditional file transfer protocol, while SFTP transfers files over SSH and adds encryption. If your hosting platform supports SFTP, it is generally the safer choice. If not, use the secure file transfer option available in your account.
Why can I connect but not see the live application files?
Most likely the FTP account is pointed to a different folder. Check the home directory and confirm it matches the actual JSP project path or deploy directory used by Tomcat.
Best practices for deploying JSP projects through FTP
To keep your deployment process clean and predictable, follow these simple practices:
- upload only the files you changed, when possible;
- keep a local backup before replacing live files;
- test permissions after creating the FTP account;
- document the correct deploy path for your project;
- restart or reload the application service only when necessary;
- remove temporary accounts after the project handover.
These habits help reduce errors and make the hosting environment easier to maintain, especially when several people work on the same JSP application.
Conclusion
Creating a dedicated FTP account for a JSP project is one of the simplest ways to manage file uploads safely in a Plesk-based hosting environment. It lets you restrict access to the correct application folder, work more efficiently with Tomcat or My App Server, and keep deployment tasks organized.
For JSP hosting, the key is to match the FTP home directory to the real deploy path and use the control panel for service-related actions. Once that structure is in place, uploading and updating your Java web application becomes much more straightforward.