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 M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • 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 ...

                    • 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) ...

                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...

                    • 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 ...

                      Related Products