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. Their arrangement is as shown here.

  1. Microsoft .NET

  2. APM Insight

  3. GlassFish Server

  4. Java Runtime

  5. JBoss Server

  6. Oracle Application Server

  7. SilverStream

  8. Tomcat Server

  9. VMware vFabric tc Servers

  10. WebLogic Server

  11. WebSphere Server

  12. J2EE Web Transactions

Top

1. Microsoft .NET

Note:

1. To monitor Microsoft .Net Framework the user must have "Administrator" privileges.

2. Firewall access for monitoring: If the firewall is present between the IT360 and the .Net installed, ports 135,443,1025 must be opened in firewall to enable access.

3. Microsoft .Net Framework 3.5/2.0 Sp1: If .Net Framework 3.5/2.0 sp1 is installed, please go through the hotfix issued by Microsoft.

To create Microsoft.NET Monitor:

  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click Microsoft.NET under Application Servers. In the Add Monitor wizard displayed, do the following:

  1. Enter a Display Name for the server.

  2. Enter the 'Host Name / IP Address', where .NET runs.

  3. Enter the SubNetMask of the network. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name.

  4. Set the Polling Interval, in minutes. (The time interval to monitor the different parameters configured for a Monitor)

  5. Enter the User Name and Password of the system.

  6. Choose the Business Service Group from the combo box, with which you want to associate the .NET Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

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

Top

2. GlassFish Server

To create GlassFish Application Server Monitor:

  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click GlassFish under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Give the Display name.

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

  8. Enter the Port. For default installations of GlassFish, the JMX port number is 8686.

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

  10. Enter the JNDIpath. e.g. JNDIPATH for default installations of GlassFish is /jmxrmi. (Note: To verify if JMX Connection Use jconsole Remote Connection, give the same Hostname ,Port and Credentials for jconsole connection to GlassFish).

  11. Set the Polling Interval. (The time interval to monitor the different parameters configured for a Monitor)

  12. Choose the Business Service Group from the combo box, with which you want to associate the Glassfish Server Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.
  1. Click Add Monitor(s). This discovers the GlassFish Servers from the network and starts monitoring them.

Top

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

Things to Know About JBoss:

To create a JBoss Server Monitor:

  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click JBoss Server under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Enter a Display Name for the server.

  7. Enter the 'Host Name / IP Address', where JBoss runs.

  8. Enter the SubNetMask of the network. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name.

  9. Choose the JBoss version (e.g. 3.2x, 4x, etc).

  10. Enter the Port number, default is 8080.

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

  12. Set the Polling Interval. (The time interval to monitor the different parameters configured for a Monitor)

  13. Enable the Authentication is enabled checkbox, if JBoss has authentication information. Then enter the User Name and Password.

  14. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the JBOSS Server Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

  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

5. 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. After performing the above steps please ensure that you are able to access the url http://<host>:7200/dmsoc4j/AggreSpy from the IT360 system.

Note: Supported version of Oracle Application Server is: 10g.

To create an Oracle Application Server Monitor:
  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click Oracle Application Server under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Enter a Display Name for the server.

  7. Enter the 'Host Name / IP Address', where the Oracle Application Server runs.

  8. Choose the Oracle Version (e.g. 10.1.2).

  9. Enter the SubNetMask of the network. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name.

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

  11. Enter the Polling interval. (The time interval to monitor the different parameters configured for a Monitor)

  12. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the Oracle Application Server Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

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

Top

6. SilverStream

SilverStream servers are monitored based on the attributes such as memory, thread, etc.

To create a SilverStream Server Monitor:
  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click SilverStream under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Give the Display name.

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

  8. Enter the Port number.

  9. Set the Polling interval. (The time interval to monitor the different parameters configured for a Monitor)

  10. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the Silverstream Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

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

Top

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

In case of Tomcat 5.x & above:

To create a Tomcat Server Monitor:
  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click Tomcat Server under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Enter a Display Name for the server.

  7. Enter the 'Host Name / IP Address', where JBoss runs.

Note: Also refer to Configurations based on Tomcat Deployments section

  1. Enter the SubNetMask of the network. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name.

  2. Enter the Port number, default is 8080.

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

  4. Select the Tomcat Version (e.g. 3.x, etc)

  5. Enter the Polling interval time in minutes. (The time interval to monitor the different parameters configured for a Monitor)

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


  7. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the Tomcat Server Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.
  1. 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

8. VMware vFabric tc Server

To create VMware vFabric tc Server Monitor:

  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click VMware vFabric tc Server under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Enter a Display Name for the server.

  7. Enter the 'Host Name / IP Address', where JBoss runs.

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

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

  10. Specify the JNDIPath. For example, JNDIPath for default installations of vFabric tc Server is /jmxrmi. (Note: To verify the JMX Connection, use jconsole with the vFabric tc Server's Host Name, Port and credentials.

  11. Specify the Polling Interval in minutes. (The time interval to monitor the different parameters configured for a Monitor)

  12. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the VMware vFabric tc Server monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

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

9. WebLogic Server

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:
  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click WebLogic Server under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Enter a Display Name for the server.

  7. Enter the 'Host Name / IP Address', where JBoss runs.

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

  9. Enter the SubNetMask of the network. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name.

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

  11. Choose the WebLogic Version (e.g. 6.1, 7.0, etc)

  12. Enter the Polling interval time in minutes. (The time interval to monitor the different parameters configured for a Monitor)

  13. Provide the monitor-specific authentication information, such as Username and Password.
Note: WebLogic Server needs some additional configuration and conditions to be followed for monitoring. To monitor a WebLogic Server weblogic.jar has to be placed under D:\manageengine\dbuild\mar26\IT360\applications\ working\classes\weblogic\ (Corresponding version folder) in IT360 machine. Apart from placing this jar, WebLogic Server needs some additional configuration and conditions to be followed for getting data from the server for monitoring, as below:

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.

  1. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the Weblogic Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

  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.

Top

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

 

By default, the Performance Monitoring Infrastructure (PMI) specification level in WebSphere Servers is "None". This has to be changed to "Standard". Also, the perfServletApp.ear file which uses the Performance Monitor Interface (PMI) infrastructure to retrieve the performance information from WebSphere Application Server needs to be installed.

To modify PMI specification level:

1) Connect to the Admin console - http://<Host>:<Port>/admin/

2) On the left-side tree expand the Servers node, click on the Applications Servers link. This will display the list of servers running the node.

4) Click on the server for which data collection has to be enabled.

5) In the Additional Properties table, click on the Performance Monitoring Service.

6) Change the Initial specification level to "Standard" and Apply the changes. Also enable (select) Startup.

To install perfServletApp.ear:

1) In the Admin console, on the left-side tree, click Applications node.

2) Click Enterprise Applications.The right-side table lists all the installed applications.

3) Check if perfServletApp is already available. If not, click Install to install the perfServletApp.ear file (which is available by default under the WebSphere installation directory).

4) Restart the WebSphere Server for the changes to take effect.


To create a WebSphere Server Monitor:

  1. Login to IT360 console with the Username and Password of an Admin user.

  2. Click the Admin tab in the header pane.

  3. Click Discover/Add under Discovery.

  4. Choose the option Add from the Discover / Add type dropdown and select the Application radio button.

  5. In the Add New Monitor wizard displayed, click WebSphere Server under Application Servers. In the Add Monitor wizard displayed, do the following:

  6. Enter a Display Name for the server.

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

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

  9. Enter the SubNetMask of the network. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name. Click the Advanced link and enable the checkbox "Do not resolve DNS name", in case you have multiple system IP addresses configured with single DNS name.

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

  11. Enter the polling interval time, in minutes. (The time interval to monitor the different parameters configured for a Monitor)

  12. Select the Version of the WebSphere to be monitored (e.g. 5.x or 6.x).

  13. Enter the SOAP Connector Port (8880 by default).

  14. Enable the checkbox if SSL is enabled for the WebSphere Server.

  15. Enable the Global Security is enabled checkbox and enter the User Name and Password.

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

  17. Check the Advanced Options and list the App Servers to Monitor in the text field.

  18. Now, Associate the above Monitor Instances to a Business Service. i.e. choose the Business Service, to which you want to associate the Websphere Monitor. If no Business Service is found, Create one by clicking the Create New Business Service link.

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