> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Monitoring for Apache Tomcat

> Deploy the GermainUX components needed to monitor Apache Tomcat, its JVM, hosted applications, logs, infrastructure, and real-user experience.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)

Availability
2017-01-01

> **[Deploying GermainUX for Comprehensive Monitoring of Apache Tomcat and Its Components](#deploying-germainux-for-comprehensive-monitoring-of-apache-tomcat-and-its-components)**
>
> Full Tomcat stack monitoring

> **[Prerequisites](#prerequisites)**
>
> Identify Tomcat requirements

> **[Deploy JMX Access](#deploy-jmx-access)**
>
> Expose Tomcat JVM metrics

> **[Validate Deployment](#validate-deployment)**
>
> Verify before production

## Deploying GermainUX for Comprehensive Monitoring of Apache Tomcat and Its Components

Deploy the GermainUX components required to monitor Apache Tomcat, its JVM, hosted applications, logs, infrastructure, real-user experience, and critical application workflows.

### Deployment Architecture

Tomcat monitoring can combine several GermainUX components.

| Monitoring Area | Component / Method |
| - | - |
| Tomcat and JVM metrics | Engine + JMX |
| Java transactions and methods | GermainUX Code Profiler |
| Tomcat and application logs | Engine |
| Host operating system | Engine or Agent |
| HTTP/HTTPS availability | Engine |
| Real-user experience | RUM JS |
| Session Replay | RUM JS |
| Synthetic application journeys | RPA Bot Recorder + Engine |
| Prometheus-compatible metrics | Engine |

Deploy only the components required for the desired monitoring depth.

## Prerequisites

Before deployment, identify:

* Tomcat servers and clusters
* Tomcat version
* Java version
* Deployed applications
* HTTP and HTTPS connectors
* Monitored endpoints

> **Show all 15**
>
> * Business-critical services
> * Required monitoring methods
> * JMX availability
> * Tomcat log locations
> * Application log locations
> * JVM log locations
> * Databases and other dependencies
> * Target environments
> * Security requirements

### Deploy or Select a GermainUX Engine

Use a GermainUX Engine that can reach the Tomcat servers and required supporting services.

The Engine may need connectivity to:

* JMX endpoints
* HTTP/HTTPS endpoints
* Log directories
* Databases
* APIs
* Messaging systems
* Other monitored dependencies

Verify that the Engine can communicate with GermainUX.

### Configure Network Access

Depending on the selected monitoring methods, allow access to the required:

* JMX ports
* HTTP ports
* HTTPS ports
* SSH ports
* Log locations
* Monitoring endpoints

Use only the network access required for the selected monitoring configuration.

## Deploy JMX Access

Use JMX when Tomcat, connector, session, data-source, and JVM metrics are required.

### Verify JMX Availability

Confirm:

* JMX is enabled.
* The JMX endpoint is reachable.
* Authentication is enabled where required.
* TLS or other approved security is configured.
* Firewall rules permit access from the selected GermainUX Engine.

### JMX Security

For production environments:

* Prefer authenticated and encrypted JMX access.
* Restrict access to authorized GermainUX Engines.
* Use a dedicated least-privilege monitoring account.
* Avoid exposing JMX ports to untrusted networks.
* Do not disable authentication or TLS solely for monitoring.
* Store credentials in GermainUX credential configuration.

If remote JMX cannot be secured according to organizational requirements, use another approved collection method.

## Deploy GermainUX Code Profiler — Optional

Deploy GermainUX Code Profiler when Java transaction and code-level analysis is required.

Use it for visibility into:

* Servlet transactions
* Java methods
* Exceptions
* SQL
* Database calls
* External HTTP requests
* Integration calls
* Slow execution paths

Before production deployment:

**1. Confirm compatibility with the application's Java version**

**2. Confirm compatibility with the Tomcat version**

**3. Validate the instrumentation in a non-production environment**

**4. Follow your organization's change-management process**

## Deploy Log Monitoring — Optional

Configure access to the Tomcat and application logs that need to be monitored.

Examples include:

* Catalina logs
* Manager logs
* Host Manager logs
* Application logs
* Access logs
* Garbage-collection logs
* Startup and shutdown logs

Verify that the selected GermainUX monitoring component has read access to the required files.

Do not collect passwords, authentication tokens, session identifiers, or other sensitive application data unless explicitly required and approved.

## Deploy Infrastructure Monitoring — Optional

Extend monitoring to the operating system or platform hosting Tomcat.

Depending on the environment, deploy monitoring for:

* Linux
* Windows
* AIX
* Docker
* Kubernetes
* Network

This enables Tomcat activity to be correlated with:

* CPU
* Memory
* Disk
* Network
* Processes
* Services

> **Show all 9**
>
> * Containers
> * Pods
> * Resource limits

## Deploy RUM JS — Optional

For browser-based applications hosted by Tomcat, deploy GermainUX RUM JS.

RUM JS enables:

* Real User Monitoring
* User interactions
* Browser performance
* Network monitoring
* JavaScript error detection
* Business-process monitoring
* Session Replay

Before production deployment, configure appropriate privacy, masking, exclusions, consent, and retention requirements.

## Deploy Synthetic Monitoring — Optional

Use GermainUX RPA Bot Recorder to create approved synthetic application journeys.

Examples include:

Open Application
Sign In
Execute Critical Workflow
Validate Result

or:

Open Application
Load Critical Page
Validate Content

Use dedicated test accounts and approved test data.

Avoid synthetic actions that unintentionally modify production data.

## Validate Deployment

Before configuring production monitoring, verify:

* Engine is online.
* Tomcat servers are reachable.
* JMX is reachable when enabled.
* Authentication succeeds.
* Required HTTP/HTTPS endpoints are reachable.
* Required log directories are accessible.

> **Show all 10**
>
> * Code Profiler is active when deployed.
> * RUM JS loads when deployed.
> * Synthetic scenarios can execute when configured.
> * Supporting infrastructure is reachable when included.

Once the required components are deployed and reachable, continue with **Configure Monitoring for Apache Tomcat**.

### Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Tomcat environment.

[Contact GermainUX Support](https://docs.germainux.com/main/support.md).

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.