|
|
Discussed below are the prerequisites for managing the various monitors:
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'.
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.
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:
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
Click on the link to view the sample startWLS.cmd\sh file.
Restart the WebLogic Integration Server for the changes to take effect.
Copy 'weblogic.jar' from folder
Prerequisites for monitoring WebLogic:
To monitor WebLogic 6.1: Follow the steps given below:
Provide only Admin user name.
Copy Weblogic.jar from folder '<Weblogic Home>/weblogic61/server/lib' in Remote WebLogic server version 6.
- 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:
Edit 'startWLS.cmdsh' present in the '<WLS_HOME>/server/bin' directory and add the following arguments:
-Dweblogic.disableMBeanAuthorization=true
-Dweblogic.management.anonymousAdminLookupEnabled=trueClick here for Sample startWLS.cmd/sh.
Restart the WebLogic Server for the changes to take effect.
Copy 'Weblogic.jar' from folder '<Weblogic Home>/weblogic70/server/lib' in Remote WebLogic server version 7.
- 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:
Edit startWLS.cmdsh present in the <WLS_HOME>/server/bin directory and add the following arguments:
-Dweblogic.disableMBeanAuthorization=true
-Dweblogic.management.anonymousAdminLookupEnabled=trueCick here for Sample startWLS.cmd/sh.
Restart the WebLogic Server for the changes to take effect.
Copy 'Weblogic.jar' from folder '<Weblogic Home>/weblogic81/server/lib' in Remote WebLogic server version 8.
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.
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:
Connect to the Admin console - 'http://<Host>:<Port>/admin/ '
On the left-side tree, expand the Servers node.
Click on 'Application Servers' link. This will display the list of servers running in the node.
Click on the 'Server' for which data collection has to be enabled.
In the Additional Properties table, click on 'Performance Monitoring Service'.
Change the Initial specification level to 'Standard' and then apply the changes. Also enable (select) Startup.
In the Admin console, on the left-side tree, click 'Applications' node.
Click on 'Enterprise Applications'.
The right-side table lists all the installed applications. Check if 'perfServletApp' is already available. If not, click 'Install' to install the 'perfServletApp.ear' file (which is available by default under WebSphere installation directory).
Restart WebSphere Server.
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.
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.
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:
Download latest SAP JavaConnector [sapjco-ntintel-2.1.8] from http://service.sap.com/connectors. Unzip the file.
In the machine, where IT360 is running, Copy librfc32.dll to C:\WINDOWS\system32 directory.
Copy sapjcorfc.dll and sapjco.jar to <IT360_Home>/applications/working/lib directory.
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.
Restart IT360 by running 'IT360\bin\startIT360.bat' file.
|
Tip: 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 Vista machine (c:\windows\system32). Still not able to add? Create Support Information File and send it to it360-eval@manageengine.com. |
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.
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:
In Apache's 'httpd.conf' file, locate 'Location /server-status' tag.
Remove the comment in the 'Location/Server-status' tag, to enable 'SetHandler server-status'.
Change the attribute 'deny from all' to 'Allow from all'.
Remove the comment in 'LoadModule status_module modules/mod_status.so'.
Save the 'conf' file and restart the Apache Server.
To enable the Extended-status, follow the steps given below:
Locate 'ExtendedStatus' Attribute in 'httpd.conf' file.
Remove the comment to enable the status.
Save the 'conf' file and restart the Apache Server.
Prerequisites for monitoring NTLM Authenticated URLs:
To monitor NTLM authenticated URLs:
Download cryptix-jce-20050328-snap.zip file from http://www.cryptix.org/cryptix-jce-20050328-snap.zip
Extract the contents of the cryptix-jce-20050328-snap.zip file to any location and copy the cryptix-jce-provider.jar file under ..\bin\ folder to <IT360-Home>\lib\ext.
Restart IT360.
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/]
By default, the 'dms0/AggreSpy' URL is redirected and the redirect location is protected, allowing only the localhost (127.0.0.1) to access the AggreSpy Servlet.
To view metrics from a system other than the localhost, you need to change the DMS configuration for the system that is running the Oracle Application Server that you want to monitor by modifying the file '$ORACLE_HOME/Apache/Apache/conf/dms.conf' on UNIX, or '%ORACLE_HOME%\Apache\Apache\conf\dms.conf' on Windows systems.
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:
Modify dms.conf by changing the entries with the value for localhost "127.0.0.1" shown in Example to the name of the server providing the metrics (obtain the server name from the ServerName directive in the httpd.conf file, for example tv.us.oracle.com).
Find below a sample updated dms.conf that allows access from a system
other than the localhost (127.0.0.1).
Example: Sample dms.conf File for Remote Host Access for DMS Metrics
# proxy to DMS AggreSpy
Redirect /dms0/AggreSpy http://tv.us.oracle.com:7200/dmsoc4j/AggreSpy
#DMS VirtualHost for access and logging control
Listen tv.us.oracle.com:7200
OpmnHostPort http://tv.us.oracle.com:7200
<VirtualHost tv.us.oracle.com:7200>
ServerName tv.us.oracle.com
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.
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.
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.
Prerequisites for monitoring IBM WebSphere MQ Monitor:
For monitoring IBM Websphere MQ, three jar files are required- com.ibm.mq.jar, com.ibm.mq.pcf-6.0.jar and connector.jar.
Follow the below steps to get these jar files and copy them to the product.
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. From this support pac, you can get the com.ibm.mq.pcf-6.0.jar file.
2) com.ibm.mq.jar and connector.jar can be located at <Websphere MQ Home Directory>\Java\lib directory.
3) Copy the three jar files to <IT360_Home>\jre\lib\ext directory and restart IT360 and try adding the monitor again.
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/]By default, the 'dms0/AggreSpy' URL is redirected and the redirect location is protected, allowing only the localhost (127.0.0.1) to access the AggreSpy Servlet.
To view metrics from a system other than the localhost, you need to change the DMS configuration for the system that is running the Oracle Application Server that you want to monitor by modifying the file '$ORACLE_HOME/Apache/Apache/conf/dms.conf' on UNIX, or '%ORACLE_HOME%\Apache\Apache\conf\dms.conf' on Windows systems.
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:
Modify 'dms.conf' by changing the entries with the value for localhost '127.0.0.1' shown in Example to the name of the server providing the metrics (obtain the server name from the ServerName directive in the 'httpd.conf' file, for example 'tv.us.oracle.com').
Find below a sample updated 'dms.conf' that allows access from a system
other than the localhost (127.0.0.1).
Example: Sample 'dms.conf' File for Remote Host Access for DMS Metrics
# proxy to DMS AggreSpy
Redirect /dms0/AggreSpy http://tv.us.oracle.com:7200/dmsoc4j/AggreSpy
#DMS VirtualHost for access and logging control
Listen tv.us.oracle.com:7200
OpmnHostPort http://tv.us.oracle.com:7200
<VirtualHost tv.us.oracle.com:7200>
ServerName tv.us.oracle.com
Restart, or stop and start the Oracle HTTP Server using Application Server Control Console or using the Oracle Process Manager and Notification Server 'opmnctl' command.
Example: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.
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:
For any further support, please contact it360-eval@manageengine.com.
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
|
|