AdventNet ManageEngine® Applications Manager

<< Prev

Chapter 3.2 Prerequisites for Applications Manager

Next >>

 

Prerequisites for Applications Manager

 

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.

 

Prerequisites for monitoring Tomcat:


AdventNet 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 Applications Manager 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 /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.

 

Prerequisites for monitoring WebLogic:


For WebLogic 6.1, provide Admin user name.


For monitoring WebLogic 7.x, 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:


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

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- > Under Additional Properties, click on End Points link -> click on SOAP connector address. You can get the SOAP port from there.

4. In Network Deployment mode, Click DMGR - > Under Additional Properties, click on End Points link -> click on 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, Click on Application Servers

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

 

Prerequisites for monitoring SAP Server:


SAP Server Monitoring requires SAP JavaConnector ( JCo) to be present in Applications Manager'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 AppManager is running, Copy librfc32.dll to C:\WINDOWS\system32 directory. Copy sapjcorfc.dll and sapjco.jar to AppManager8/working/lib directory.

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

4. Restart Applications Manager by running startApplicationsManager.bat file.

 

Note: 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 support@appmanager.com.


For Linux:


1. Download latest SAP JavaConnector [sapjco-linuxintel-2.1.8.tar] from http://service.sap.com/connectors. Unzip libsapjcorfc.so, sapjco.jar and librfccm.so under AppManager8/working/lib directory. Verify if libstdc++-libc6.2-2.so.3 is available under /usr/lib/ directory.

2. Restart Applications Manager by running startApplicationsManager.sh file.

 

Note: The user name provided while adding SAP monitor should have sufficient privileges to access CCMS metrics. To check this, the user can execute RZ20 transaction in the SAP GUI and see if the CCMS monitor sets can be displayed.

 

Prerequisites for monitoring PHP:

 

Kindly place the phpstats.php file in the webserver's document root. The phpstats.php can be found in <Applications Manager Home>/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:

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


Prerequisites for monitoring NTLM Authenticated URLs:

 

To monitor NTLM authenticated URLs,

 

Prerequisites for monitoring Oracle Applications Server:

 

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.


To enable the access, please follow the instructions provided below
[The instructions are referred from the Oracle website :

http://download-west.oracle.com/docs/cd/B14099_16/core.1012/b14001/monitor.htm#sthref86]

 

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.

 

The following example shows a sample default configuration from dms.conf. This configuration limits AggreSpy to access metrics on the localhost (127.0.0.1). The port shown, 7200, may differ on your installation.

 

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

 

By changing the dms.conf configuration to specify the host that provides, or serves DMS metrics, you can allow users on systems other than the localhost to access the DMS metrics from the location http://host:port/dms0/AggreSpy.

 

Caution: Modifying dms.conf has security implications. Only modify this file 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

from the Applications Manager 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

-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

 

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 <ProductHome>\working\jre\lib\ext directory and restart Applications Manager and try adding the monitor again.

 

For any further support please contact support@appmanager.com. You can visit Troubleshooting details.

 

 

 

<< Prev

Home

Next >>

Understanding Application Manager

 

Working with Applications Manager

 

Performance Management Solutions [ Application Management | Load Testing | Website Monitoring Service]
Copyright © 2008, AdventNet Inc. All Rights Reserved. | Product Website: www.appmanager.com