I have multiple Tomcat Servers and also a separate Apache Server running. In this scenario, I'm not able to discover or monitor a Tomcat Server.

I have multiple Tomcat Servers and also a separate Apache Server running. In this scenario, I'm not able to discover or monitor a Tomcat Server.

Monitoring of Tomcat Server depends on its deployment. This section explains the possible deployment scenarios of Tomcat. Your configuration of host name and the port depends on these scenarios. Also, for Tomcat Server versions 3.x and 4.x, you have to deploy an agent for monitoring.

1.  Standalone Tomcat Server

This is a general scenario wherein you have a Tomcat server that has the HTTP (apache) within its deployment. In this case, specify the host name of the Tomcat server and the HTTP port when configuring a tomcat monitor.

2. One Tomcat Server (with HTTP) and one external instance of Apache

There is one Tomcat server with HTTP (Apache) instance running in it and another external Apache running outside.

Example: Tomcat server name: Tomcat A; HTTP (in Tomcat server) port: 8080; External Apache server port: 80

In this case, while configuring a Tomcat monitor, specify the host name as 'Tomcat A' and specify the HTTP port that runs with the Tomcat and not the external Apache, i.e., specify the port as 8080 and not 80.

3. One Tomcat Server (without HTTP) and one external instance of Apache

There is one Tomcat server without HTTP in it and another external Apache running.

Example: Tomcat server name: Tomcat A; HTTP (in Tomcat server) port: Not available; External Apache server port: 80

In this case, while configuring a Tomcat monitor, specify the host name as 'Tomcat A' and specify the port of the external Apache, i.e., 80.

4. Multiple Tomcat Servers (with HTTP instances in each of these servers) and one external instance of Apache

There are multiple Tomcat servers, say 3, with HTTP instances in each of them and another external Apache running.

Example: Tomcat Server names: Tomcat A, Tomcat B, Tomcat C; HTTP (in Tomcat servers) port: 8070, 8080, 8090 respectively; External Apache server port: 80

In this case, you need to create tomcat server monitors individually for Tomcat A, Tomcat B, and Tomcat C and specify their ports as 8070, 8080, and 8090 respectively.

5. Multiple Tomcat Servers (without HTTP instances in these servers) and one external instance of Apache

There are multiple Tomcat servers, say 3, without HTTP instances in them and another external Apache running.

Example: Tomcat Server names: Tomcat A, Tomcat B, Tomcat C; HTTP (in Tomcat servers) port: Not available; External Apache server port: 80

You can monitor only one of the instances in this case.

                  New to ADSelfService Plus?

                    • Related Articles

                    • Self monitor Applications Manager using Real User Monitoring

                      We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...
                    • Troubleshooting - Apache Solr

                      To troubleshoot Apache Solr Monitor, follow the below steps: Verify Accessibility: Ensure that the Apache Solr instance is accessible from the Applications Manager server. Check Host and Port: Make sure you’ve entered the correct host and port number ...
                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...
                    • Troubleshooting - Apache Server

                      Troubleshooting - Apache Server monitor If you're encountering issues in Apache Server monitor in Applications Manager, follow these steps to diagnose and resolve the problem: 1. Verify the Server is an Apache Server: Open Command Prompt on the ...