Deploy a Tomcat Application Statically

30 minutes
  • 3 Learning Objectives

About this Hands-on Lab

Welcome to this hands-on lab, where we’ll deploy an application on Tomcat via the CLI in a static manner.

We are using Apache’s Tomcat, a Java-based application platform built around deploying and managing Java Web Applications. The server provided in this lab environment is running Red Hat Enterprise 8 and has Tomcat 9 pre-installed for you. The Tomcat instance is available for you on port **8080**.

You will log into the server via the CLI and deploy an application after first stopping Tomcat, then starting Tomcat again and noting what happens.

After stopping Tomcat a second time, you will deploy a second version of the application, then start Tomcat yet again. The application’s web page should show the new version of the application.

Both of the applications will be provided in a folder on the Tomcat server for your use.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Test to Ensure You Can Access the Preconfigured Tomcat Instances on Port 8080.

Connect to the Tomcat GUI and log in. To access the server, visit the external IP address provided in the hands-on lab page, and append :8080 to it.

For example, if an IP address shown was 3.92.152.3, then you would put the following into your web browser:

http://3.92.152.3:8080

You should see the GUI.

Note: It may take from 3 to 10 mins after the hands-on lab has started before you can access the Tomcat server on port 8080.

Stop Tomcat, Deploy Version 1 of `sample.war` via the CLI, Then Start Tomcat

You must deploy the sample.war via the CLI. To complete this task you are not to use the GUI and you must stop Tomcat first.

The file is located here: /files/version1/sample.war.

Once the application is in the correct place, start the Tomcat server.

Go to the application via a browser and test to see if it’s working. It can be found by going to the server’s external IP address with :8080/sample at the end of the URL.

For example, if the IP address shown for the lab was 3.92.152.3 then you would put the following into your web browser:
http://3.92.152.3:8080/sample

Stop Tomcat, Deploy Version 2 of `sample.war` via the CLI, Then Start Tomcat

You must deploy the sample.war via the CLI. To complete this task you are not to use the GUI and you must stop Tomcat first.

The file is located here: /files/version2/sample.war.

Once the file is in place restart Tomcat.

Go to the application via a browser and test to see if it’s working. It can be found by going to the server’s external IP address with :8080/sample at the end of the URL.

For example, if the IP address shown for the lab was 3.92.152.3 then you would put the following into your web browser:
http://3.92.152.3:8080/sample

The application will have different text than the original application. It shows version 2.

Additional Resources

You have been tasked with deploying an application on your Tomcat server. Just after you have deployed it though, a new version has been given to you and you need to deploy that version.

There are issues with your company's load balancers, so the management process in your organization is to stop the Tomcat server before deploying a new application or updating an existing one.

First you must stop the Tomcat server, then deploy the application located in /files/version1/sample.war and start the Tomcat server.

Test to make sure you can see the application on your Tomcat server.

Then, to deploy the updated application, you must stop the Tomcat server again. Use the updated file, located in /files/version2/sample.war, for the new deployment.

Once the updated file is in the correct location, start the Tomcat server again.

Test to make sure you can see that the application's front page has changed. You may need to refresh the cache if your browser has it cached.

A successful hands-on lab will have you able to see the updated Tomcat application on the server. The new application will be running and the old application will have been undeployed.

Note: It may take 3 to 10 minutes after the hands-on lab has started before you are able to log into the server. This is fine and will not affect the performance of the tasks for the hands-on lab.

Logging In

Use the credentials provided on the hands-on lab overview page, and log in to the provided server as cloud_user. Note that this is for connecting to the server and also for the Tomcat GUI.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Get Started
Who’s going to be learning?

How many seats do you need?

  • $499 USD per seat per year
  • Billed Annually
  • Renews in 12 months

Ready to accelerate learning?

For over 25 licenses, a member of our sales team will walk you through a custom tailored solution for your business.


$2,495.00

Checkout
Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!