How to configure Tomcat Monitor for JBoss 3.2.5?

How to configure Tomcat Monitor for JBoss 3.2.5?


Steps to configure Tomcat Monitor for JBoss 3.2.5 :


1. Append the following script in the 'web.xml' file, present under 'JBoss_Home\server\deploy\jbossweb-tomcat50.sar\ROOT.war\WEB-INF' folder  :

<servlet-mapping>
<servlet-name>Status Servlet</servlet-name>
<url-pattern>/manager/status</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>Status Servlet</servlet-name>
<url-pattern>/manager/</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>Status Servlet</servlet-name>
<url-pattern>/manager/status/</url-pattern>
</servlet-mapping>


2. Restart the JBoss server. 
3. In AppManager, go to the monitor creation page for Tomcat monitors.
4. Select the version as 5.x and create the monitor. This will create a monitor for the Tomcat web server running in JBoss3.2.5.


                  New to ADSelfService Plus?

                    • Related Articles

                    • Is JBoss Monitor Safe to Add in Applications Manager Despite the Need to Open the Console Port?

                      Why Open the JBoss Console Port? To monitor JBoss servers, ManageEngine Applications Manager requires access to the JBoss Management Console via its exposed port. This access allows AppManager to collect critical performance and health metrics using ...
                    • How to configure Output Settings for Script Monitor?

                      Below are the details on how to configure Script Monitor Output Settings and expected output format, Output Configuration: Expected Output File Format: In the output file, Scalar data should be separated by scalar delimiter, here name, cpu, javaHeap ...
                    • Troubleshooting URL Monitor

                      When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...
                    • 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 ...
                    • 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) ...