Deploy a Tomcat Application Dynamically

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 dynamic 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 on port **8080**.

You will log into the server via the CLI and deploy an application. You will then test whether the application automatically deployed by going to the application’s web page.

Next you will deploy a second version of the application, which should also deploy automatically. You will test that by going to the application’s web page, which 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

Use the Tomcat server’s public IP address and port 8080 to connect to the Tomcat GUI and log in. The username and password to use are the same as what’s provided for CLI access.

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. This is to test that the Tomcat is up and running and the lab is ready for you to perform the tasks.

Note: It may take from 3 to 10 mins after the Hands-On Lab has started before you can access the Tomcat servers on Port 8080.

Deploy Version 1 of the sample.war via the CLI

You must deploy /files/version1/sample.war via the CLI, not the GUI.

Once the application is in the correct place, check to make sure it is deployed. Check to see if the application has been exploded in the folder.

Go to the application via a browser and make sure it is working. It can be found by visiting the server’s external IP address with :8080/sample appended to 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

Deploy Version 2 of the sample.war via the CLI

You must deploy Version 2 of the application (located in /files/version2/sample.war) via the CLI, not the GUI.

Once the application is in the correct place, check to make sure it deployed.

Go to the application via a browser and make sure it is working. It can be found by going to the server’s external IP address with :8080/sample appended to 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

You should see text on the webpage showing that it is Version 2. If the webpage is unchanged, troubleshoot the issue.

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.

The Tomcat server has been set up to automatically deploy an application. You must perform the tasks via the CLI. Do not stop the Tomcat server during these tasks.

Deploy the application located in /files/version1/sample.war and check to make sure it starts.

Test whether or not you can see the application on your Tomcat server.

Next, deploy the updated application, which is located under /files/version2/sample.war.

Test whether or not 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!