Application Servers

This section is common to all the editions of IT360 - Professional Edition, Enterprise Edition (Probes only) and MSP Edition (Probes only).

The Application Servers are designed to develop Web services and Web applications. Failure in diagnosing any problem in these Services / Applications results in poor productivity and performance. ManageEngine IT360 monitors these Servers and Applications, to detect such problems affecting the Business process. management.

The following are the different Application Servers supported by IT360;


Microsoft .NET:

To create Microsoft .NET Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select Microsoft .NET Monitor.

  3. Enter the IP Address or Hostname of the host, where .NET runs.

  4. Enter the SubNetMask of the network.

  5. Set the Polling Interval.

  6. Enter the User Name / Domain Name and Password of the system.

  7. Choose the Business Service Group from the combo box, with which you want to associate the .NET Monitor;

  8. Click Add Monitor(s). This discovers .NET from the network and starts monitoring them.

Top

GlassFish Server:

To create GlassFish Application Server Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select GlassFish.

  3. Give the Display name.

  4. Enter the Hostname of the host, where GlassFish runs.

  5. Enter the Port.

  6. Enter the User Name and Password of the GlassFish Server.

  7. Enter the JNDIpath.

  8. Set the Polling Interval.

  9. Choose the Business Service Group from the combo box, with which you want to associate the Glassfish Server Monitor;
  1. Click Add Monitor(s). This discovers the GlassFish Servers from the network and starts monitoring them.

Top

JBoss Server:

For ManageEngine IT360 to monitor JBoss, it should be able to access the host, where the JBoss server runs and vice-versa. Supported versions of JBoss Server are: 3.2.x, 4.0.x, 4.2.2 GA. For more information, refer to Online Troubleshooting section.

Prerequisite: To monitor JBoss, the 'http-invoker.sar' should be deployed in the JBoss Server. Know more in the Prerequisite section.

To create a JBoss Server Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select JBoss Server.

  3. Enter the IP Address or Hostname of the host, where JBoss runs.

  4. Enter the SubNetMask of the network.

  5. Enter the Port number, e.g., 8080.

  6. Choose SSL option, if SSL is enabled in JBoss server.

  7. Choose the JBoss version.

  8. Set the Polling Interval.

  9. Enter the User Name and Password, if JBoss has authentication information.

  10. Choose the Business Service Group from the combo box, with which you want to associate the JBOSS Server Monitor;
  1. Click Add Monitor(s). This discovers the JBoss server from the network and starts monitoring them.

Troubleshoot: Having trouble in monitoring JBOSS server? Refer to the Online Troubleshooting section.

Top

Oracle Application Server:

ManageEngine IT360 uses the Dynamic Monitoring Service(DMS), provided by the Oracle Application Server, to monitor the same. For this reason, the DMS Servlet has to be made accessible to the system, where the IT360 is running. Refer Prerequisites Section. Supported version of Oracle Application Server is: 10g.

To create an Oracle Application Server Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select Oracle AS.

  3. Enter the IP Address or Hostname of the host, where the Oracle Application Server runs.

  4. Enter the SubNetMask of the network.

  5. Enter the Port number, e.g., 7200.

  6. Enter the Polling interval.

  7. Choose the Business Service Group from the combo box, with which you want to associate the Oracle Application Server Monitor;
  1. Click Add Monitor(s). This discovers the Oracle Application Server from the network and starts monitoring them.

Top

SilverStream:

To create a SilverStream Server Monitor:

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select SilverStream.

  3. Give the Display name.

  4. Enter the Hostname of the host, where the SilverStream Server runs.

  5. Enter the Port number.

  6. Set the Polling interval.

  7. Choose the Business Service Group from the combo box, with which you want to associate the Silverstream Monitor;

  8. Click Add Monitor(s). This discovers SilverStream Server from the network and starts monitoring them.

Top

Tomcat Server:

The supported versions of Tomcat Servers are 3.x, 4.x, 5.x and above. For Tomcat Server 3.x and 4.x, an agent has to be deployed for monitoring.

Note: You can check whether the Agent is deployed, by connecting to the following URL in Tomcat Server.

'http://<Tomcat-Host>:<Tomcat-Port>/adventnet/DataServlet'

To deploy the agent for Tomcat Server 3.x;

  1. Download the 'Tomcat3Agent.Zip from <IT360 HOME>/applications/working/classes directory.

  2. Unzip it in the <Tomcat Home> directory of the host in which the Tomcat server is running.

  3. Restart the Tomcat Server.

To deploy the agent for Tomcat Server 4.x;

  1. Download the Tomcat4Agent.Zip from the <IT360 HOME>/applications/working/classes directory.

  2. Unzip it in the <Tomcat Home> directory of the host in which the Tomcat server is running.

  3. Add the following tag in server.xml file located in the <Tomcat Home>/conf directory below the Engine tag).

    <ValveclassName="com.adventnet.appmanager.tomcatagent.ver4.valve.AdventNetHostValve"/>

    [Click the link to view an example server.xml]

  4. Restart the Tomcat Server.

To deploy the agent for Tomcat Server 4.x and Apache server combined;

  1. Download the 'Tomcat4Agent.Zip' from the '<IT360 HOME>/applications/working/classes' directory.

  2. Unzip it in the '<Tomcat Home>' directory of the host, in which the Tomcat server is running.

  3. Add the following tag in 'server.xml' file, located in the '<Tomcat Home>/conf' directory (below the Engine tag).

    '<Valve className="com.adventnet.appmanager.tomcatagent.ver4.valve.AdventNetHostValve"/>'

    [Click the link to view an example server.xml]

  4. Restart the Tomcat Server.

  5. Apache:

    In 'Apache mod_jk.conf' file of Apache Server, add the following entry:


  6. Restart Apache server.
To create a Tomcat Server Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select Tomcat Server.

  3. Enter the IP Address or Hostname of the host.

    [Note: Also refer to Configurations based on Tomcat Deployments section]

  4. Enter the SubNetMask of the network.

  5. Enter the Port number, in which the monitor is running. [Default port number is 8080]

  6. Choose SSL option, if SSL is enabled in Tomcat server.

  7. Enter the Polling interval time in minutes.

  8. Provide the monitor-specific authentication information, such as Username and Password.

    9. Note: Tomcat 3.x and 4.x does not need Username and Password. In case of Tomcat 5.x and/or above, an application named Manager must be running in it, for ManageEngine IT360 to monitor the Tomcat server. By default, this application will be running in the server. Moreover, the user role to access the server must also be Manager.

    To add a role as "Manager" for any of the users such as tomcat, role1, or both, you need make changes in 'tomcat-users.xml' file, located in the '<TOMCAT-HOME>/conf' directory.

    Example:

    Default configurations in 'tomcat-users.xml' in Tomcat Server.

    <tomcat-users>
    <user name="tomcat" password="tomcat" roles="tomcat" />
    <user name="role1" password="tomcat" roles="role1" />
    <user name="both" password="tomcat" roles="tomcat,role1" />
    </tomcat-users>

    After adding the roles for the "tomcat" user, the modified entries will be as follows:

    <tomcat-users>
    <user name="tomcat" password="tomcat" roles="tomcat,manager" />
    <user name="role1" password="tomcat" roles="role1" />
    <user name="both" password="tomcat" roles="tomcat,role1" />
    </tomcat-users>

    After making the configuration, restart the Tomcat Server.

    Now, when adding a new Tomcat (5.x and above) monitor, specify the Username/Password as tomcat/tomcat, when discovering the Tomcat Server.

    [Click the link to view an example tomcat-users.xml]

  9. Choose the Business Service Group from the combo box, with which you want to associate the Tomcat Server Monitor;

  10. Click Add Monitor(s). This discovers Tomcat server from the network and starts monitoring them.

Troubleshoot: Having trouble in monitoring Tomcat server? Refer to the Online Troubleshooting section.

 

Note: Steps to configure Tomcat Monitor for JBoss 3.2.5

  1. Append the following in the 'web.xml' file, present in the '<JBOSS_SERVER_HOME>\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. Configure a tomcat monitor. Go to'Admin -> Servers & Applications -> New Monitor' and select Tomcat Server from the combo box.

  4. Select the version as 5.x and create the monitor. This will create a monitor for the Tomcat webserver, running in JBoss3.2.5.

Configurations based on Tomcat Server Deployment:

Monitoring of Tomcat Server depends on its deployment. This section explains the possible deployment scenarios of Tomcat. Your configuration of Hostname and the Port depends on these scenarios.

1. Standalone Tomcat Server:

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

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 for a Tomcat monitor, specify the Hostname as 'Tomcat A' and specify the Port of the HTTP 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 for a Tomcat monitor, specify the Hostname as 'Tomcat A' and specify the Port of the external Apache, i.e., 80.

4. Multiple Tomcat Server (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 monitor individually for Tomcat A, Tomcat B, and Tomcat C and specify their Ports as 8070, 8080, and 8090, respectively.

5. Multiple Tomcat Server (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. Please contact it360-eval@manageengine.com, if you would like to add it.

Top

VMware vFabric tc Server

To create VMware vFabric tc Server Monitor:

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. Select VMware vFabric tc Server.

  3. Provide the Display name of the monitor.

  4. Enter the Host Name, in which the vFabric tc Server is running.

  5. Enter the Port number, in which the JMX Agent is running (6969 by default). The port in which JMX agent is running; is defined in the 'catalina.properties' file.

  6. Enter the User Name and Password of the vFabric tc Server.

  7. Specify the JNDIPath. For example, JNDIPath for default installations of vFabric tc Server is /jmxrmi.

  8. Specify the Polling Interval in minutes.

  9. Choose the Business Service Group from the combo box, with which you want to associate the VMware vFabric tc Server monitor:

  10. Click Add Monitor(s). This discovers the vFabric tc Server from the network and starts monitoring it.

Note:To enable JMX in the tc Server, you have to define a JMX port in the file 'catalina.properties' and then give an entry in a server.xml.

[Click the link to view an example server.xml file and also a snippet of catalina.properties which shows how to set values for the variables used in the server.xml file].

WebLogic Server:

The supported versions of WebLogic Servers are 6.1, 7.x, 8.x, 9.x and 10.x. Know the Prerequisites that are required to monitor WebLogic.

To create a WebLogic Server Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select WebLogic Server.

  3. Enter the IP Address / Hostname of the host.

  4. Enter the SubNetMask of the network.

  5. Enter the Port number, in which WebLogic is running.

  6. Enter the Polling interval time in minutes.

  7. Provide the monitor-specific authentication information, such as Username and Password.

    8. Note: WebLogic Server needs some additional configuration and conditions to be followed for monitoring.

    To monitor WebLogic 6.1:

    1. Provide only Admin user name.

    2. Copy 'Weblogic.jar' file from the folder '<Weblogic Home>/weblogic61/server/lib' in Remote WebLogic server version 6. Copy to the '<IT360 Home >\applications\working\classes\weblogic\version6' folder in the machine, where IT360 is running.

    To monitor WebLogic 7.x:

    You should set the 'weblogic.disableMBeanAuthorization' and 'weblogic.management.anonymousAdminLookupEnabled' variables to TRUE, for enabling data collection. Then, follow the steps given below;

    1. Edit 'startWLS.cmdsh' present in the '<WLS_HOME>/server/bin' directory and add the following arguments
      -Dweblogic.disableMBeanAuthorization=true
      -Dweblogic.management.anonymousAdminLookupEnabled=true       (click on the link to view the sample startWLS.cmd\sh file).

    2. Restart the WebLogic Server for the changes to take effect.

    3. Copy 'Weblogic.jar' file from the folder '<Weblogic Home>/weblogic70/server/lib' in the Remote WebLogic server version 7. Copy to the '<IT360 Home>\applications\working\classes\weblogic\version7' folder in the machine, where IT360 is running.

    To monitor WebLogic 8.x:

    You should set the 'weblogic.disableMBeanAuthorization' and 'weblogic.management.anonymousAdminLookupEnabled' variables to TRUE, for enabling data collection. Then, follow the steps given below;

    1. Edit 'startWLS.cmdsh' present in the '<WLS_HOME>/server/bin' directory and add the following arguments
      -Dweblogic.disableMBeanAuthorization=true
      -Dweblogic.management.anonymousAdminLookupEnabled=true       (click on the link to view the sample startWLS.cmd\sh file).

    2. Restart the WebLogic Server for the changes to take effect.

    3. Copy 'Weblogic.jar' file from the folder '<Weblogic Home>/weblogic81/server/lib' in the Remote WebLogic server version 8. Copy to the '<IT360 Home>\applications\working\classes\weblogic\version8' folder in the machine, where IT360 is running.

    To monitor WebLogic 9.x:

    Copy the 'Weblogic.jar' file from the folder '<Weblogic Home>/weblogic92/server/lib' in the Remote WebLogic server version 9. Copy to the '<IT360 Home>\applications\working\classes\weblogic\version9' folder in the machine, where IT360 is running.

    To monitor WebLogic 10.x:

    Copy the 'Weblogic.jar', 'wlclient.jar', 'wljmsclient.jar' files from the folder '<Weblogic Home>/wlserver_10.0/server/lib in Remote WebLogic server version 10. Copy to the '<IT360 Home>\applications\working\classes\weblogic\version10' folder in machine, where IT360 is running.

       

  8. Choose the Business Service Group from the combo box, with which you want to associate the Weblogic Monitor;\

  9. Click Add Monitor(s). This discovers WebLogic server from the network and starts monitoring them.

Troubleshoot: Having trouble in monitoring Weblogic server? Refer to the Online Troubleshooting section.

Top

WebSphere Server:

The supported versions of WebSphere Servers are 5.x and 6.x.


Prerequisites for Websphere Monitoring: For ManageEngine IT360 to be able to collect data from WebSphere Application Server, proper configurations are required at the Performance Monitoring Infrastructure (PMI) specification level. Refer Prerequisites Section for configuration details.

To create a WebSphere Server Monitor;

  1. Go to 'Admin -> Servers & Applications' and click on New Monitor link.

  2. From the drop down menu, select WebSphere Server.

  3. Select the Deployment Mode as Base or Network Deployment.

  4. For Base Mode, Enter the Host name / IP Address of the host in which websphere application server is running. For Network Deployment, enter the Host name/IP Address of the websphere application server in which the perf servlet is installed. This will automatically discover all the WebSphere servers in Network Deployment.

  5. Enter the SubNetMask of the network.

  6. Enter the HTTP Transport Port (9080 by default).

  7. Enter the polling interval time in minutes.

  8. Select the version of the WebSphere to be monitored - 5.x or 6.x.

  9. Enter the Port number of the SOAP Connector (8880 by default).

  10. Enter the User Name and Password, if Global Security is enabled.

  11. In Network Deployment Mode, Enter the Network Deployer's Host and SOAP Port (Default : 8879).

  12. Choose the Business Service Group from the combo box with which you want to associate Websphere Monitor;

  13. Click Add Monitor(s). This discovers WebSphere server from the network and starts monitoring them.

Note: ManageEngine IT360 has been tested for WebSphere versions only for English language.

Troubleshoot: Having trouble in monitoring Weblogic server? Refer to the online Troubleshooting section.

Top

See Also: Monitor Information - Application Servers | Create Other New Monitors

Copyright © 2013, ZOHO Corp. All Rights Reserved.