Practitioner Level

Configure Logging in Tomcat

30 minutes

4 Learning Objectives

Welcome to this hands-on lab, where we’ll configure logging in Tomcat.

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 and ensure that logging is enabled and operational, and that logs are going to the correct location.

You will check that accessing the Manager App in the GUI is logging to the correct log files.

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 in a web browser by visiting the server’s public IP address on port 8080. The username and password there are the same as what’s provided for CLI access.

For example, if the server’s IP address was 3.92.152.3, then this is the URL you’d type into the browser:

http://3.92.152.3:8080

You should see the Tomcat GUI.

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.

Examine the logging.properties File and Check for Any Incorrect Entries

The logging.properties file contents instruct Tomcat to log several items. For some reason not all the logs are being placed into the /usr/local/tomcat9/logs folder.

If you examine the /usr/local/tomcat9 directory, you will see that an incorrect folder is receiving some of the logs.

Fix Any Incorrect Entries in the logging.properties File

Fix any entries in the logging.properties file so that all the logs are being placed into the /usr/local/tomcat9/logs folder.

Do what is required to ensure new log entries are routed correctly.

Test to Make Sure Your Tomcat Server Is Logging Correctly

Test and ensure that all logs are now going to the correct location.

Additional Resources

You have been tasked with enabling the logging for the Tomcat Manager Application. Someone noticed that logs recording users signing into the application were not showing up in the correct place.

Automated tools that capture the logs should be putting them in /usr/local/tomcat9/logs. If logs go anywhere else, that needs to be resolved, because it is both a security and an audit issue.

Performing all of the tasks that are laid out will accomplish this. A successful hands-on lab will have you able to see that when you access pages on the Tomcat Manager App via the GUI, the access is being logged into the correct log file under /usr/local/tomcat9/logs.

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 page, and log in to the provided server as cloud_user. Note that this is for connecting to the server and also to 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?

Myself My Organization

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

Welcome Back!

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