ManageEngine® Applications Manager Prerequisites for Applications Manager |
||
Discussed below are the prerequisites for managing the various monitors:
Application Servers
Database Servers
Cloud Apps
ERP
Java / Transactions
Middleware / Portal
Web Server / Services
Glassfish
While monitoring Glassfish application servers, make the following changes in the domain.xml file and then restart it:
Change the "accept-all" property to "true" for the "jmx-connector" node : <jmx-connector accept-all="true"
The configuration line should look like this :
<jmx-connector accept-all="true" address="0.0.0.0" auth-realm-name="admin-realm" enabled="true" name="system" port="8686" protocol="rmi_jrmp" security-enabled="false"/>
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 <Applications Manager 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.
Oracle Application 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://docs.oracle.com/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:
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.
For example,
%opmnctl restartproc process-type=HTTP_Server
or
%opmnctl stopproc process-type=HTTP_Server
%opmnctl startproc process-type=HTTP_ServerAfter performing the above steps, please ensure that you are able to access the url http://<host>:7200/dmsoc4j/AggreSpy from the Applications Manager system.
Tomcat
AdventNet agent has to be deployed in Tomcat Servers 3.x and 4.x. More
In case of Tomcat 5.x and 6.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
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. Copy to <AppManager Home >\working\classes\weblogic\version6 folder in the machine where Applications Manager is runningTo monitor WebLogic 7.x:
You should set the weblogic.disableMBeanAuthorization and weblogic.management.anonymousAdminLookupEnabled variables to 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 Click here for Sample startWLS.cmd/sh
2) Restart the WebLogic Server for the changes to take effect
3) Copy Weblogic.jar from folder <Weblogic Home>/weblogic70/server/lib in Remote WebLogic server version 7. Copy to <AppManager Home>\working\classes\weblogic\version7 folder in the machine where Applications Manager is runningTo monitor WebLogic 8.x
You should set the weblogic.disableMBeanAuthorization and weblogic.management.anonymousAdminLookupEnabled variables to 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 Click here for Sample startWLS.cmd/sh
2) Restart the WebLogic Server for the changes to take effect
3) Copy Weblogic.jar from folder <Weblogic Home>/weblogic81/server/lib in Remote WebLogic server version 8 Copy to <AppManager Home>\working\classes\weblogic\version8 folder in the machine where Applications Manager 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 <AppManager Home>\working\classes\weblogic\version9 folder in the machine where Applications Manager 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 <AppManager Home>\working\classes\weblogic\version10 folder in machine where Applications Manager is running.
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:
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
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- > 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.
MS SQL Database Server
For monitoring a MS SQL database server the user should be permitted to access the MASTER and MSDB databases. He must log in using either the Public and Db_datareader roles for both MASTER and MSDB databases.
For SQL 2005, 2008 and 2012 servers the 'View Server State' permission should be also present. If you would like to monitor SQL Server using SQL named instance, you need to ensure that the 'SQL Browser Service' is running in the system.
To grant View Server State, you can use any of the following methods :
1) Execute the following query
GRANT VIEW SERVER STATE TO username;
2) In SQL management studio for user choose Properties -> Securables -> Click Add ( under securables ) -> choose "All objects of the Types..." -> choose Servers -> choose Grant for "View server state" permission.
Note:
The collation option for Applications Manager's backend MS SQL Database is case-insensitive.
MySQL Database Server
While monitoring a MySQL database server ensure that you assign a user name that has permission to access the MySQL database from the host where Applications Manager is running. An alternate way is to add a relevant user who has the privileges to do the same.
The user should have privileges to execute SELECT, SHOW DATABASES, REPLICATION commands in the MySQL server.
For enabling these privileges, execute the following commands in the remote MySQL Server:
INSERT INTO user (Host,User) VALUES('<host>','<user>');
GRANT SELECT,SHOW DATABASES,REPLICATION CLIENT ON *.* TO '<user>'@'<host>';
FLUSH PRIVILEGES; (Use the host name - Applications Manager machine).
PostgreSQL
Applications Manager 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:
- Open postgresql.conf under <postgres home>/data
- 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
- Open pg_hba.conf under /data
- 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
Windows Azure
To add Windows Azure in Applications Manager, you must first export file of your Windows Azure Managed Certificates (eg., testcertificate.pfx) and password of the pfx file.
To monitor Windows Azure in Applications Manager, invoke the batch script exportCertificateToAppManager.bat in the <Applications Manager Home>\bin directory.
Oracle EBS
Applications Manager uses the Dynamic Monitoring Service (DMS) to monitor performance and availability of Oracle E-Business Suite.For this reason, the DMS Servlet has to be made accessible to the system where the Applications Manager is running.
By default, the dms0/AggreSpy URL 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 running the Oracle EBS.
This can be done as follows:
Step 1: Open the trusted.conf file under $ORACLE_HOME/Apache/Apache/conf on UNIX, or %ORACLE_HOME%\Apache\Apache\conf\ on Windows systems and add the Applications Manager Hostname and IPaddress in the "Allow from" list.
<Location ~ "/(dms0|DMS|Spy|AggreSpy)">
Order deny,allow
Deny from all
Allow from localhost
Allow from <list of TRUSTED IPs>
</Location>
Step 2: Now open the httpd.conf and httpd_pls.conf file and check if the trusted.conf file is included. The best way is to check if the word trusted.conf is available in these files. If not add the following lines and save the files:
# Include the trusted.conf file
include $ORACLE_HOME/Apache/Apache/conf/trusted.conf
Step 3: Restart Oracle E-Business Suite and ensure that you are able to access the url http://<host>:<port>/dms0/AggreSpy from the Applications Manager system.
Note:
Modifying trusted.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 EBS Server internal status and runtime information.
SAP Server, SAP CCMS
SAP Server Monitoring and SAP CCMS Monitoring requires SAP JavaConnector ( JCo) to be present in Applications Manager's classpath.
For Windows:
- Download SAP JavaConnector [sapjco-ntintel-2.1.10] from https://websmp104.sap-ag.de/~sapidb/011000358700007415502002E/JCoDownload.htm#4. Depending on whether Applications Manager is running on a 32 or 64 bit machine, make sure you download the respective zip file.
- Unzip the file.
- In the machine, where Applications Manager is running, Copy librfc32.dll to C:\WINDOWS\system32 directory. Copy sapjcorfc.dll and sapjco.jar to AppManager_home/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 Applications Manager.
Note:
In case you are using the 32 bit version of Applications Manager in a 64 bit machine, then :
Copy the 32 bit version of librfc32.dll file to directory C:\Windows\SysWOW64.
Right click on my computer and open the system properties
Then click on the advanced tab and edit the environmental variables
Next edit the path and add the entry %SystemRoot%\SysWOW64\ in that path
Save the settings.
For Linux:
- Download latest SAP JavaConnector [sapjco-linuxintel-2.1.10] from https://websmp104.sap-ag.de/~sapidb/011000358700007415502002E/JCoDownload.htm#4. Depending on whether Applications Manager is running on a 32 or 64 bit machine, make sure you download the respective zip file.
- Unzip the file.
- In the machine, where Applications Manager is running, copy libsapjcorfc.so, sapjco.jar and librfccm.so under AppManager_home/working/lib directory.
- Verify if libstdc++-libc6.2-2.so.3 is available under /usr/lib/ directory.
- Restart Applications Manager.
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.
APM Insight
APM Insight includes a remote monitoring agent which has to be deployed in your application instances. Know more about APM Insight Agent.
Java Runtime Monitor
To monitor a JDK1.5 JVM and above, add the following JVM arguments 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
To monitor IBM JDK1.5 JVM and above, add the following JVM arguments to your application:
-Djavax.management.builder.initial= -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..
IBM WebSphere MQ Monitor
For monitoring IBM Websphere MQ version 5 and version 6, three jar files are required- com.ibm.mq.jar, com.ibm.mq.pcf-6.x.jar and connector.jar. For monitoring Version 7, three more jar files should be added.
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 linkhttp://www-1.ibm.com/support/docview.wss?uid=swg24000668 . From this support pac, you can get the com.ibm.mq.pcf-6.x.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.
4) For monitoring Version 7, additionally you need to copy the following jar files from <websphere mq series installation>\java\lib directory to <AppManager Installation>\working\jre\lib\ext directory
i)com.ibm.mq.headers.jar
ii)com.ibm.mq.commonservices.jar
iii)com.ibm.mq.jmqi.jar
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
/weblogic81/server/lib in Remote WebLogic server version 8 and place it under <AppManager Home >\working\classes\weblogic\version8 folder in the machine where Applications Manager is running.
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 Applications Manager Home\lib\ext.
Restart Applications Manager.
PHP
Place the phpstats.php file in the webserver's document root. The phpstats.php can be found in <Applications Manager Home>/working/resources directory.
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.
For any further support please contact appmanager-support@manageengine.com. You can visit Troubleshooting details. |
Understanding Application Manager |
Working with Applications Manager |