Prerequisites for Monitoring Applications and Servers

Discussed below are the prerequisites for managing the various monitors:

  1. JBoss
  2. Tomcat
  3. WebLogic Integration Server
  4. WebLogic
  5. WebSphere
  6. SAP Server, SAP CCMS
  7. PHP
  8. Apache
  9. NTLM Authenticated URLs
  10. Oracle Applications Server
  11. J2EE Web Transactions Monitor
  12. Java Runtime Monitor
  13. IBM WebSphere MQ
  14. Oracle EBS
  15. PostgreSQL
  16. Hyper-V Server

1. Prerequisites for monitoring JBoss

To monitor JBoss, the 'http-invoker.sar' should be deployed in the JBoss Server. The application ('http-invoker.sar') is, by default, deployed in the JBoss server.

If the http port of the JBoss server is changed then the port number in the attribute 'InvokerURLSuffix' should also be modified in 'jboss-3.2.0/server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml' file.

 To monitor JBoss 5.0.0 version and above, 'jbossagent.sar' should be deployed in JBoss server.

To deploy, follow the steps below:

Copy 'jbossagent.sar' from location '<IT360 -Home>/working/resources' and paste under '<JBOSS_HOME>/server/default/deploy'. If you are running JBoss in different domain like all, then deployment target folder would be '<JBOSS_HOME>/server/all/deploy'.

Top

2. Prerequisites for monitoring Tomcat

Zoho Corp Agent has to be deployed in Tomcat Servers 3.x and 4.x. More.

In case of Tomcat 5.x, an application named Manager must be running in it for 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 to make changes in 'tomcat-users.xml' file, located in the '<IT360-Home>/conf' directory.

Click the link to view an example: tomcat-users.xml, which has user tomcat with role as Manager.

Top

3. Prerequisites for monitoring WebLogic Integration Server

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

For monitoring WebLogic Integration Server 8.x, you should set the weblogic.disableMBeanAuthorization and weblogic.management.anonymousAdminLookup system variable to true, for enabling data collection. Follow the steps given below:

  1. Edit 'startWLS.cmd\sh' present in the '<WLS_HOME>/server/bin' directory and add the following argument:

    -Dweblogic.disableMBeanAuthorization=true and
    -Dweblogic.management.anonymousAdminLookupEnabled=true

  1. Click here to view the sample startWLS.cmd\sh file.

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

  3. Copy 'weblogic.jar' from folder '/weblogic81/server/lib' in Remote WebLogic server version 8 and place it under 'D:\manageengine\dbuild\apr2\IT360\applications\working\classes\weblogic\version8' folder in ManageEngine IT360 - Applications machine.

Top

4. Prerequisites for monitoring WebLogic

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.

  3. Copy to '<IT360 Home>\applications\working\classes\weblogic\version6folder' in the machine, where IT360 is running.

To monitor WebLogic 7.x: You should set the 'weblogic.disableMBeanAuthorization' and 'weblogic.management.anonymousAdminLookupEnabled' variables to be '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

  2. Click here for Sample startWLS.cmd/sh.

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

  4. Copy 'Weblogic.jar' from folder '<Weblogic Home>/weblogic70/server/lib' in Remote WebLogic server version 7.

  5. Copy to '<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 be '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

  2. Cick here for Sample startWLS.cmd/sh.

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

  4. Copy 'Weblogic.jar' from folder '<Weblogic Home>/weblogic81/server/lib' in Remote WebLogic server version 8.

  5. Copy to '<IT360 Home>\applications\working\classes\weblogic\version8' folder in the machine, where IT360 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 '<IT360 Home>\Applications\working\classes\weblogic\version9' folder in the machine, where IT360 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 '<IT360 Home>\Applications\working\classes\weblogic\version10' folder in machine, where IT360 is running.

Top

5. Prerequisites for monitoring WebSphere Application Server

For base deployment:

You have to modify the Performance Monitor Interface (PMI) Specification Level from "None" to "Standard". Then deploy the perfServletApp.ear file, which uses the PMI infrastructure to retrieve the performance information from WebSphere Application Server, in the WebSphere. Restart WebSphere Application Server.

For Network deployment:

You have to modify the PMI Sepcifictaion Level from "None"to "Standard" in all the WebSphere Servers in Network Deployment. Then deploy the perfServletApp.ear file, which uses the PMI infrastructure to retrieve the performance information from WebSphere Application Server, in any one of the WebSphere Servers in the Network Deployment. Restart WebSphere Application Server.

Note: Go through the steps to check whether WebSphere monitor has been correctly set.

To modify PMI specification level:

To deploy perfServletApp.ear:

Steps to Check whether Websphere monitor has been correctly set

For Base Deployment:

To ensure whether the PMI & perfServletApp are configured properly in WebSphere, invoke the below URL & check whether the data is returned in XML format:

'http://WebSphereHost:Port/wasPerfTool/servlet/perfservlet?connector=SOAP&port=SOAP-PORT'

where,

WebSphere Host -> Host in which WebSphere Application Server is running

WebSphere Port -> HTTP Transport port of the WebSphere Application server [How to locate HTTP Port]

SOAP Port -> SOAP Port of WebSphere [How to locate SOAP Port]

For Network Deployment:

To ensure whether the PMI & perfServletApp are configured properly in WebSphere, invoke the below URL & check whether the data is returned in XML format.

'http://WebSphereHost:Port/wasPerfTool/servlet/perfservlet?connector=SOAP&port=NetworkDeployerSOAP-PORT&HOST=NetworkDeployerHost'

where,

WebSphere Host -> The host of the websphere application server in which the perf servlet application is installed

Websphere Port -> HTTP Transport port of the Websphere server in which the perf servlet application is installed [How to locate HTTP Port]

NetworkDeployer SOAP PORT -> The SOAP port of the domain manager (DMGR) [How to locate SOAP Port]

Network Deployer Host -> The host in which the domain manager is running.

Note: Also check whether WebSphere admin user is added to the monitor group of the perfservletApp.

 

How to locate SOAP Port?

1. Login to Admin console

2. Expand the 'Server' link on left side tree. Click on 'Application Servers'.

3. In Base mode, various WebSpheres will be listed down. Click on the 'WebSphere's name' and under Additional Properties, click on 'End Points link' and 'SOAP connector address'. You can get the SOAP port from there.

4. In Network Deployment mode, click 'DMGR', and under Additional Properties click on 'End Points' link and 'SOAP connector address' - You can get the SOAP port from there.

 

How to find the HTTP Transport port?

1. Login to Admin console.

2. Expand the 'Server' link on left side tree and click on 'Application Servers'.

3. Various WebSpheres will be listed down. Click on the WebSphere's name, and under Additional Properties, click on 'Web Container' link and 'HTTP Transports' link. You can get the HTTP port from there.

Top

6. Prerequisites for monitoring SAP Server, SAP CCMS

SAP Server Monitoring and SAP CCMS Monitoring requires SAP JavaConnector ( JCo) to be present in IT360's classpath.

For Windows:

  1. Download latest SAP JavaConnector [sapjco-ntintel-2.1.8] from http://service.sap.com/connectors. Unzip the file.

  2. In the machine, where IT360 is running, Copy librfc32.dll to C:\WINDOWS\system32 directory.

  3. Copy sapjcorfc.dll and sapjco.jar to <IT360_Home>/applications/working/lib directory.

  4. Verify msvcr71.dll and msvcp71.dll exist in the Windows system directory. The DLL files must be added to the Windows system directory if they do not already exist.

  5. Restart IT360 by running 'IT360\bin\startIT360.bat' file.

Tip:

i) Not able to add SAP Monitor in Windows Vista? The reason is that 'msvcr71.dll' and 'msvcp71.dll' files are not present in the Windows Vista machine. Copy those dlls from any other windows XP machine to the Vista machine (c:windowssystem32).

ii) While creating a SAP monitor, you need a SAP user profile with the following authorization objects: S_RFC, S_XMI_LOG and S_XMI_PROD, which are minimum prerequisities for adding the SAP monitor.

Still not able to add? Create a Support Information File and send it across to: it360-eval@manageengine.com.

Top

7. Prerequisites for monitoring PHP

Kindly place the 'phpstats.php' file in the webserver's document root. The 'phpstats.php' can be found in '<IT360 Home>/Applications/working/resources' directory.

Top

8. Prerequisites for monitoring Apache

Enabling the Server status and the Extended-status will give additional information for the Apache server.

To enable the Server Status, follow the steps given below:

To enable the Extended-status, follow the steps given below:

Top

9. Prerequisites for monitoring NTLM Authenticated URLs

To monitor NTLM authenticated URLs:

Top

10. Prerequisites for monitoring Oracle Applications Server

IT360 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 IT360 is running. To enable the access, please follow the instructions provided below:

[The instructions are referred from the Oracle website: http://docs.oracle.com/]

Example: Sample 'dms.conf' File for localhost Access for DMS Metrics

# proxy to DMS AggreSpy

Redirect /dms0/AggreSpy http://localhost:7200/dmsoc4j/AggreSpy

#DMS VirtualHost for access and logging control

Listen 127.0.0.1:7200

OpmnHostPort http://localhost:7200

<VirtualHost 127.0.0.1:7200>

ServerName 127.0.0.1

Caution: Modifying 'dms.conf' has security implications. Modify this file, only if you understand the security implications for your site. By exposing metrics to systems other than the localhost, you allow other sites to potentially view critical Oracle Application Server internal status and runtime information.

To view metrics from a system other than the localhost (127.0.0.1), do the following:

Example:

%opmnctl restartproc process-type=HTTP_Server

or

%opmnctl stopproc process-type=HTTP_Server
%opmnctl startproc process-type=HTTP_Server

After performing the above steps, please ensure that you are able to access the url 'http://<host>:7200/dmsoc4j/AggreSpy' (replace <host> with the appropriate HostName) from the IT360 system.

Top

11. Prerequisites for monitoring J2EE Web Transactions

J2EE Web Transaction Monitor requires an agent to be plugged in the application server (like JBoss) to be monitored. Know more about the J2EE Web Transactions Agent.

Top

12. Prerequisites for monitoring Java Runtime Monitor

To monitor a JDK1.5 JVM and above, the following java runtime options needs to be added to your application.

Note : Port number '1099' can be replaced with the actual port number of the JMX agent.

Top

13. Prerequisites for monitoring IBM WebSphere MQ Monitor

To monitor IBM Websphere MQ Series following jar files need to be added.
For IBM Websphere MQ Series version 5.x/6.x:
For IBM Websphere MQ Series version 7:
The following jars are required in addition to above mentioned jar files.
Follow the below given steps to get the jar files:
  1. Download the supportpac MS0B : WebSphere MQ Java classes for PCF from the following link http://www-1.ibm.com/support/docview.wss?uid=swg24000668. com.ibm.mq.pcf-6.0.jar file is available in this support pac.
  2. com.ibm.mq.jar and connector.jar are located at <Websphere MQ Home Directory>\Java\lib directory.
  3. Copy the three jar files to D:\manageengine\dbuild\mar26\IT360\jre\lib\ext directory.
    Note: Copy these jar files to <JavaHome>\jre\lib\ext directory if external JDK is configured for IT360.
  4. Restart ManageEngine IT360 and try adding the monitor.

Top

14. Prerequisites for monitoring Oracle E-Business Suite

IT360 uses the Dynamic Monitoring Service (DMS) provided by Oracle E-Business Suite to monitor the same. For this reason, the DMS Servlet has to be made accessible to the system where the IT360 is running. To enable the access, please follow the instructions provided below:

[The instructions are referred from the Oracle website: http://docs.oracle.com/]

Example: Sample 'dms.conf' File for localhost Access for DMS Metrics

# proxy to DMS AggreSpy

Redirect /dms0/AggreSpy http://localhost:7200/dmsoc4j/AggreSpy

#DMS VirtualHost for access and logging control

Listen 127.0.0.1:7200

OpmnHostPort http://localhost:7200

<VirtualHost 127.0.0.1:7200>

ServerName 127.0.0.1

Caution: Modifying 'dms.conf' has security implications. Modify this file, only if you understand the security implications for your site. By exposing metrics to systems other than the localhost, you allow other sites to potentially view critical Oracle Application Server internal status and runtime information.

To view metrics from a system other than the localhost (127.0.0.1), do the following:

After performing the above steps, please ensure that you are able to access the url 'http://<host>:7200/dmsoc4j/AggreSpy' (Replace the <host> with your HostName) .from the IT360 system.

15. Pre-requisites for monitoring PostgreSQL

 IT360 uses PostgreSQL's subsystem statistics collector to monitor PostgreSQL server activity. By default, the statistics collector is accessible.

 If you have problems in adding a new PostgreSQL server, follow the steps given below:

  1. Open postgresql.conf under <postgres home>/data
  2. Check value of configuration parameter listen address it has to be "*", if not change it to "*". Click here for more details on configuring postgresql.conf
  3. Open pg_hba.conf under /data
  4. Add a new line host all all 0.0.0.0/0 md5 to allow all machines with proper password authentication to access PostgreSQL DB server. Click here for more details on configuring pg_hba.conf

For any further support, please contact it360-eval@manageengine.com.

Top

16. Pre-requisites for monitoring Hyper-V Server

When a firewall is present between IT360 and the Hyper-V server to be monitored, the following ports will have to be opened in the firewall to enable access from IT360:

Ports: 135, 443, 1025

Also, the User Permissions should be with 'Administrator' privileges to the root OS

Top



Copyright © 2014, ZOHO Corp. All Rights Reserved.