ManageEngine® Applications Manager


Application Servers

<< Prev

Home

Next >>

Application Servers

 

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.

 

Applications Manager monitors these servers and applications to detect such problems affecting the business process management.

 

The following are the different Application Servers supported by Applications Manager:

Microsoft .NET

 

To create Microsoft .NET Monitor

  1. Click on New Monitor link.

  2. 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 Monitor Group from the combo box with which you want to associate .NET Monitor (optional).

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

 

Note:
This monitor type is not supported in the Cloud Starter Edition. Compare Editions.


Top

GlassFish Server

 

To create GlassFish Application Server Monitor

  1. Click on New Monitor link.

  2. 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 GlassFish Server.

  7. Enter the JNDI path.

  8. Set the Polling Interval.

  9. Choose the Monitor Group from the combo box with which you want to associate GlassFish Monitor (optional).

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

 

Note:
This monitor type is not supported in the Cloud Starter Edition. Compare Editions.


Top

JBoss Server

Supported versions of JBoss Server: 3.2.x, 4.x, 4.0.x, 5, 5.1, 6.0, 7.x


For Applications Manager to monitor JBoss, it should be able to access the host where JBoss server runs and vice versa. 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. Click on New Monitor link.

  2. Select JBoss.

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

  4. Choose the JBoss version.

  5. Enter the port number for eg., 8080.

  6. Check the Is Domain option, if you are using JBoss version 7.x and above.

  7. Provide the name of the Host Controller and the JBoss Server Instance name.

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

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

  10. Set the Polling Interval.

  11. Choose the Monitor Group from the combo box with which you want to associate JBoss Server Monitor (optional).

  12. Click Add Monitor(s). This discovers 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

Supported version of Oracle Application Server: 10g

 

Applications Manager uses the Dynamic Monitoring Service(DMS) provided by Oracle Application Server to monitor the same. For this reason, the DMS Servlet has to be made accessible to the system where the Applications Manager is running. Refer Prerequisites Section.


To create a Oracle Application Server Monitor

  1. Click on New Monitor link.

  2. Select Oracle AS.

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

  4. Enter the SubNetMask of the network.

  5. Enter the Port number for eg., 7200.

  6. Choose the Monitor Group from the combo box with which, you want to associate Oracle Application Server Monitor (optional).

  7. Click Add Monitor(s). This discovers Oracle Application Server from the network and starts monitoring them.

 

Note:
This monitor type is not supported in the Cloud Starter Edition. Compare Editions.

Top

SilverStream

To create a SilverStream Server Monitor

  1. Click on New Monitor link.

  2. Select SilverStream.

  3. Give the Display name.

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

  5. Enter the Port number.

  6. Set the Polling interval.

  7. Choose the Monitor Group from the combo box with which, you want to associate SilverStream Server Monitor (optional).

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

 

Note:
This monitor type is not supported in the Cloud Starter Edition. Compare Editions.

Top

 

Tomcat Server

The supported versions of Tomcat Servers are 3.x, 4.x, 5.x, 6.x, 7.x. For Tomcat Server 3.x and 4.x, 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 <Applications Manager Home>/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 <Applications Manager Home>/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.


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

  1. Download the Tomcat4Agent.Zip from the <Applications Manager Home>/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. Click on New Monitor link.

  2. 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 user name and password.

Note: Tomcat 3.x and 4.x needs no user name and password. In case of Tomcat 5.x and above, an application named Manager must be running in it for Applications Manager to monitor the Tomcat server. By default, this application will be running in the server.If you have customized the manager application (Eg., \qamanager), then you can use the option "Tomcat Manager Application URI" in the client, for Applications Manager to monitor the Tomcat server. The user role to access the server must be manager (versions 5.x & 6.x) / manager-gui (version 7.x).

 

To add a role as "manager" (versions 5.x & 6.x) / "manager-gui" (version 7.x) 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>
<role rolename="tomcat" />
<role rolename="role1" />
<user username="tomcat" password="tomcat" roles="tomcat" />
<user username="role1" password="tomcat" roles="role1" />
<user username="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>
<role rolename="tomcat" />
<role rolename="role1" />
<role rolename="manager" />
<user username="tomcat" password="tomcat" roles="tomcat,manager" />
<user username="role1" password="tomcat" roles="role1" />
<user username="both" password="tomcat" roles="tomcat,role1" />
</tomcat-users>


On 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 for versions 5.x / 6.x and tomcat-users.xml for versions 7.x]

  1. Choose the Monitor Group from the combo box with which you want to associate Tomcat Server Monitor (optional).

  2. 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 present in <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 by clicking New Monitor --> Select Tomcat Server in 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 host name 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 host name 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 host name 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 host name 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 appmanager-support@manageengine.com if you would like to have it added.

Top

 

 

VMware vFabric tc Server

 

The supported versions of VMware vFabric tc Server are 2.6 to 2.9

 

To create VMware vFabric tc Server Monitor

  1. 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 Monitor Group from the combo box with which you want to associate vFabric tc Server Monitor (optional).

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

Top

WebLogic Server

The supported versions of WebLogic Servers are 6.1, 7.x, 8.x, 9.x, 10.x.

Know the Prerequisites that are required to monitor WebLogic.

 

To create a WebLogic Server Monitor

  1. Click on New Monitor link.

  2. 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 user name and password.

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

  • To monitor WebLogic 6.1 ,

    Follow the steps given below:

    1) Provide only Admin user name.
    2) Copy Weblogic.jar from folder <Weblogic Home>/weblogic61/server/lib in Remote WebLogic server version 6. Copy to <AppManager Home >\working\classes\weblogic\version6 folder in the machine where Applications Manager is running


    To monitor WebLogic 7.x ,

    You should set the weblogic.disableMBeanAuthorization and weblogic.management.anonymousAdminLookupEnabled variables to true for enabling data collection.


     

    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 here for Sample startWLS.cmd/sh
    2) Restart the WebLogic Server for the changes to take effect
    3) Copy Weblogic.jar from folder <Weblogic Home>/weblogic70/server/lib in Remote WebLogic server version 7. Copy to <AppManager Home>\working\classes\weblogic\version7 folder in the machine where Applications Manager is running


    To monitor WebLogic 8.x

    You should set the weblogic.disableMBeanAuthorization and weblogic.management.anonymousAdminLookupEnabled variables to true for enabling data collection.

     

    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 here for Sample startWLS.cmd/sh
    2) Restart the WebLogic Server for the changes to take effect
    3) Copy Weblogic.jar from folder <Weblogic Home>/weblogic81/server/lib in Remote WebLogic server version 8 Copy to <AppManager Home>\working\classes\weblogic\version8 folder in the machine where Applications Manager is running.

    To monitor WebLogic 9.x ,

    Copy Weblogic.jar from folder <Weblogic Home>/weblogic92/server/lib in Remote WebLogic server version 9 . Copy to <AppManager Home>\working\classes\weblogic\version9 folder in the machine where Applications Manager is running.


    To monitor WebLogic 10.x ,

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

  1. Choose the Monitor Group from the combo box with which you want to associate WebLogic Server Monitor (optional).

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

Note:
This monitor type is not supported in the Cloud Starter Edition. Compare Editions.

 

Top

WebSphere Server

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


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

To create a WebSphere Server Monitor

  1. Click on New Monitor link.

  2. 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, 6.x, 7.x and 8.x.

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

  10. If you want to monitor WebSphere through SSL mode, select the SSL is enabled checkbox.

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

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

  13. Choose the Monitor Group from the combo box with which you want to associate WebSphere Server Monitor (optional).

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

Note: Applications Manager has been tested for WebSphere versions of English, German, Japanese and Chinese languages.

 

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

Note:
This monitor type is not supported in the Cloud Starter Edition. Compare Editions.

Top

See Also

Monitor Information - Application Servers | Create Other New Monitors

 

 

<< Prev

Home

Next >>

Creating New Monitor

Cloud Application Monitors