How to Deploy a Java Web Application on a Web Server

Finding a Host That Doesn’t Hate Java

Not every hosting provider gets along with Java—it’s like trying to fit a square peg in a round hole with some budget hosts. Here’s what I look for when picking a home for my Java apps:

• Java-Friendly Setup: You need a host that supports servlet containers like Apache Tomcat, Jetty, or GlassFish. I’ve had great luck with Hostiserver, A2 Hosting, and Kamatera—they’re built for Java’s quirks. A generic shared host? That’s a recipe for frustration.
• No Downtime Nightmares: Java apps can be resource hogs. I once had a client’s app crash because the host skimped on uptime. Aim for 99.9% reliability to keep things smooth.
• Room to Scale: Imagine your app’s a small blog today but a viral hit tomorrow. Your host should let you bump up CPU or RAM without a fuss. Need more tips on picking a host? I wrote about it here: How to Choose the Best Web Hosting: Is a More Expensive Server Always Better Than a Cheaper One?
• Support That Saves You: Java errors can be brutal—think ClassNotFoundException at midnight. Choose a host with a support team that’s seen it all and can talk you off the ledge.

A solid host is like a good coffee shop—reliable, ready for your needs, and there when you’re in a pinch.

Prepping Your Server for Action

Got a host? Sweet. Now let’s turn that server into a Java-running machine.

Installing the Java Development Kit (JDK)

Your app’s heart beats with Java, so you need a fresh JDK. On Ubuntu, it’s a quick job:

sudo apt update
sudo apt install openjdk-21-jdk

Run this to make sure it’s working:

java -version

If you see openjdk 21 or similar, you’re in business. Once, I skipped this check, and my app failed because I had an old JDK version—don’t be me.

Setting Up Apache Tomcat

Tomcat’s my go-to for Java apps—it’s like a trusty pickup truck, not flashy but gets the job done. Install it on Ubuntu like this:

sudo apt install tomcat10
sudo systemctl start tomcat10
sudo systemctl enable tomcat10

Now, open your browser and go to http://your-server-ip:8080. If you see Tomcat’s welcome page with that goofy cat logo, you’re golden. No logo? Run sudo systemctl status tomcat10 to see what’s up—maybe the service didn’t start.

Getting Your App Live

Now for the fun part—making your app available to the world.

1. Package Your App as a WAR File

   Java web apps get bundled into WAR files (Web Application Archive). If you’re using Maven, it’s as simple as:

   mvn clean package

   This creates a file like your-application.war in the target folder. I once spent hours debugging because I forgot this step and uploaded an empty file. Trust me, double-check your WAR.

2. Upload to the Server

   Move that WAR file to Tomcat’s webapps folder:

   scp your-application.war username@your-server-ip:/var/lib/tomcat10/webapps/

   Tomcat’s smart enough to unpack and deploy it automatically. It’s like dropping a pizza in the oven—it just starts cooking.

3. Check If It Works

   Open your browser and head to:

   http://your-server-ip:8080/your-application

   If your app loads, pop the champagne—you did it! If it’s a blank page or an error, dive into the logs at /var/log/tomcat10/catalina.out. I’ve found NoClassDefFoundError hiding there more times than I’d like to admit.

Customizing Your Setup

Want your app to feel like it’s yours? Here’s how to tweak things:

• Ditch the Default Port: Port 8080 is fine, but it’s not sexy. Edit /var/lib/tomcat10/conf/server.xml:

  <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />

  Swap 8080 for 80 to make URLs cleaner—no port needed.

• Nicer URLs: To change /your-application to something cool like /myapp, add a META-INF/context.xml file to your WAR:

  <Context path="/myapp" />

• Add HTTPS for Security: Nobody wants their users’ data floating around unencrypted. Set up SSL to keep things safe. I covered the details here: How to Switch to HTTPS and HTTP/2.

Testing to Avoid Disaster

Launching an untested app is like jumping into a pool without checking the water. Here’s how to test smart:

• Click Everything: Test every button, form, and link. I once missed a broken login page, and users were not happy.
• Stress It Out: Use Apache JMeter to throw 100 or 1,000 fake users at your app. I learned this the hard way when my client’s app crashed during a traffic spike.
• Hunt Down Errors: If something breaks, check the logs:
  

  cat /var/log/tomcat10/catalina.out

An OutOfMemoryError means your JVM’s starving—give it more memory in Tomcat’s settings.

Keeping Your App in Fighting Shape

Your app’s live, but you’ve got to keep it healthy. Here’s my routine:

• Watch It Closely: Tools like Prometheus or Grafana are like fitness trackers for your server. If CPU or memory spikes, you’ll know it’s time to scale up.
• Back Up Like It’s Your Job: Automate backups for your database and WAR files. I’ve saved projects with this habit—check out How to Create a Backup of a MySQL Database.
• Stay Up to Date: Old JDK or Tomcat versions are hacker bait. Update regularly to keep the bad guys out.

Conclusion

Getting a Java web app live isn’t rocket science—it’s just a few well-placed steps. Pick a host that loves Java, set up Tomcat, package your app as a WAR, and test it like your life depends on it. Add HTTPS and monitoring, and you’re ready to roll. We, Hostiserver, simplify this process with Java-compatible servers and fast support.

Take it one step at a time, and your app will be out there winning hearts in no time.

FAQ