Troubleshoot: Having trouble in monitoring JBoss server? Refer to the online Troubleshooting section.
|
ManageEngine® Applications Manager 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:
To create Microsoft .NET Monitor
Click on New Monitor link.
Select Microsoft .NET Monitor.
Enter the IP Address or hostname of the host where .NET runs.
Enter the SubNetMask of the network.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Enter the User Name / Domain Name and Password of the system.
Choose the Monitor Group from the combo box with which you want to associate .NET Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers .NET from the network and starts monitoring them.
To create GlassFish Application Server Monitor
Click on New Monitor link.
Select GlassFish.
Give the Display name.
Enter the Hostname of the host where GlassFish runs.
Enter the Port
Enter the User Name and Password of GlassFish Server.
Enter the JNDI path.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate GlassFish Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers GlassFish Servers from the network and starts monitoring them.
Supported versions of JBoss Server: 3.2.x, 4.x, 4.0.x, 5, 5.1, 6.0, 7.x, Wildfly_8.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
Click on New Monitor link.
Select JBoss.
Enter the IP Address or hostname of the host where JBoss runs.
Choose the JBoss version.
Enter the port number for eg., 8080.
Check the Is Domain option, if you are using JBoss version 7.x and above.
Provide the name of the Host Controller and the JBoss Server Instance name.
Choose SSL option , if SSL is enabled in JBoss server.
Enter the User Name and Password , if JBoss has authentication information.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate JBoss Server Monitor (optional). You can choose multiple groups to associate your monitor.
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. |
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
Click on New Monitor link.
Select Oracle AS.
Enter the IP Address or hostname of the host where Oracle Application Server runs.
Enter the SubNetMask of the network.
Enter the Port number for eg., 7200.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which, you want to associate Oracle Application Server Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Oracle Application Server from the network and starts monitoring them.
To create a Resin Server Monitor:
Click on New Monitor link.
Select Resin Server under Application Servers.
Give the Display name.
Enter the Hostname of the server where Resin Application Server is running.
Enter the JMX Port. For default installations of Resin, the JMX port number is 9999.
You can enter your own credential details or select preconfigured credentials from details in Credentials Manager. If you wish to enter your own credentials, specify enter the JMX User Name and Password of Resin Server. If no authentication is required, then leave the fields blank.
Enter the JNDI path. For example:- JNDIPATH for default installations of Resin is /jmxrmi.
Set the Polling interval.
Choose the Monitor Group from the combo box with which, you want to associate Resin Server Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers your Resin Server from the network and starts monitoring it.
To create a SilverStream Server Monitor
Click on New Monitor link.
Select SilverStream.
Give the Display name.
Enter the Hostname of the host where SilverStream Server runs.
Enter the Port number.
Set the Polling interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which, you want to associate SilverStream Server Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers SilverStream Server from the network and starts monitoring them.
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
Download the Tomcat3Agent.Zip from <Applications Manager Home>/working/classes directory.
Unzip it in the <Tomcat Home> directory of the host in which the Tomcat server is running.
Restart the Tomcat Server.
To deploy the agent for Tomcat Server 4.x
Download the Tomcat4Agent.Zip from the <Applications Manager Home>/working/classes directory
Unzip it in the <Tomcat Home> directory of the host in which the Tomcat server is running.
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]
Restart the Tomcat Server.
To deploy the agent for Tomcat Server 4.x and Apache server combined
Download the Tomcat4Agent.Zip from the <Applications Manager Home>/working/classes directory
Unzip it in the <Tomcat Home> directory of the host in which the Tomcat server is running.
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]
Restart the Tomcat Server.
In Apache mod_jk.conf file of Apache Server , add
the following entry
Restart Apache server
To create a Tomcat Server Monitor
Click on New Monitor link.
Select Tomcat Server.
Enter the IP Address or hostname of the host. [Note: Also refer to Configurations based on Tomcat Deployments section]
Enter the SubNetMask of the network.
Enter the port number in which the monitor is running. [Default port number is 8080]
Choose SSL option , if SSL is enabled in Tomcat server.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
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.
Default configurations in tomcat-users.xml in 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] |
Choose the Monitor Group from the combo box with which you want to associate Tomcat Server Monitor (optional). You can choose multiple groups to associate your monitor.
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. |
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.
The supported versions of VMware vFabric tc Server are 2.6 to 2.9
To create VMware vFabric tc Server Monitor
Click on New Monitor link.
Select VMware vFabric tc Server.
Provide the Display name of the monitor.
Enter the Host Name in which the vFabric tc Server is running.
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.
Enter the User Name and Password of the vFabric tc Server.
Specify the JNDIPath. For example, JNDIPath for default installations of vFabric tc Server is /jmxrmi.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate vFabric tc Server Monitor (optional). You can choose multiple groups to associate your monitor.
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]. |
The supported versions of WebLogic Servers are 6.1, 7.x, 8.x, 9.x, 10.x, 11g, 12C.
Know the Prerequisites that are required to monitor WebLogic.
To create a WebLogic Server Monitor
Click on New Monitor link.
Select WebLogic Server.
Enter a Display Name for the monitor.
Enter the IP Address/ hostname of the host.
Select the version of your Weblogic Server from drop-down menu.
From the box, select whether SSL is enabled or not.
Enter the port number in which WebLogic is running.
You can enter your own credential details or select preconfigured credentials from details in Credentials Manager. If you wish to enter your own credentials, specify WebLogic version, username and password details for this monitor.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the monitor-specific authentication information, such as user name and password.
Choose the Monitor Group from the combo box with which you want to associate WebLogic Server Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers WebLogic server from the network and starts monitoring them.
Note:
The ports that need to be opened when the Weblogic Monitor is behind the firewall: Two-way communication between WebLogic listening port (default : 7001) and Applications Manager web server port (default : 9090).
WebLogic Server needs some additional configuration and conditions to be followed for monitoring.
|
|
Troubleshoot: Having trouble in monitoring WebLogic server? Refer to the online Troubleshooting section. |
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
Click on New Monitor link.
Select WebSphere Server.
Select the Deployment Mode as Base or Network Deployment.
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.
Enter the SubNetMask of the network.
Enter the HTTP Transport Port (9080 by default).
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Select the version of the WebSphere to be monitored - 5.x, 6.x, 7.x and 8.x.
Enter the port number of the SOAP Connector (8880 by default).
If you want to monitor WebSphere through SSL mode, select the SSL is enabled checkbox.
Enter the User Name and Password, if Global Security is enabled.
In Network Deployment Mode, Enter the Network Deployer's Host and SOAP Port (Default : 8879).
Choose the Monitor Group from the combo box with which you want to associate WebSphere Server Monitor (optional). You can choose multiple groups to associate your monitor.
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 |
Supported versions of Jetty Server: Jetty 3.1 and above.
Prerequisites for monitoring Jetty Server: Click to know about the user previleges and other necessary prerequisites to monitor Jetty Server.
To create a Jetty Server Monitor:
Click on New Monitor link.
Select Jetty Server under Application Servers.
Give the Display name.
Enter the Hostname of the server where Jetty Server is running.
Enter the JMX Port. For default installations of Jetty, the JMX port number is 9999.
You can enter your own credential details or select preconfigured credentials from details in Credentials Manager. If you wish to enter your own credentials, specify enter the JMX User Name and Password of Jetty Server. If no authentication is required, then leave the fields blank.
Enter the JNDI path. For example:- JNDIPATH for default installations of Jetty is /jmxrmi.
Set the Polling interval.
Choose the Monitor Group from the combo box with which, you want to associate Jetty Server Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers your Jetty Server from the network and starts monitoring it.
See Also
Monitor Information - Application Servers | Create Other New Monitors
Creating New Monitor |
Cloud Application Monitors |