ManageEngine® Applications Manager


Database Servers

<< Prev

Home

Next >>

Database Servers

 

Database servers are robust, enterprise-class database management system. Applications Manager provides Database Server monitoring that monitors database resources. This database server monitoring involves connecting to the database resource, collecting data, and representing its attribute details as graphs.

 

The following are the different Database servers supported by Applications Manager:


MySQL Database Server

Note: In the MySQL database (that you are trying to monitor), ensure that the user name assigned to Applications Manager has the permission to access the MySQL database from the host where Applications Manager is running. Else, give a relevant user who has the privileges to do the same.

 

Minimum User Privileges : The user should have privileges to execute SELECT, SHOW DATABASES, REPLICATION commands in the MySQL server. Also, Applications Manager machine should be allowed to access the MySQL database server.

 

For enabling the privileges, execute the below 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;

 

(Host -> Applications Manager machine) /

 

 

 

To create a MySQL database server Monitor, follow the given steps:

  1. Click on New Monitor link.

  2. Select MySQL DB Server.

  3. Enter the IP Address or hostname of the host.

  4. Enter the SubNetMask of the network.

  5. Enter the port number in which MySQL is running.

  6. Enter the polling interval time in minutes.

  7. If you are adding a new monitor from an Admin Server, select a Managed Server.

  8. Provide the user name and password of user who has permission to access the MySQL database.

  9. Specify the database name. Please note that the Database name must be valid. Also, the database name is associated with the user name. Hence, provide the database name corresponding to the user name given in the above field.

  10. Choose the Monitor Group from the combo box with which you want to associate MySQL database server Monitor (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers MySQL database server from the network and starts monitoring them.

 

Troubleshoot: Having trouble in monitoring MySQL database server? Refer to the online Troubleshooting section.

 

Top

Oracle Database Server

 

Follow the given steps to create a Oracle database server monitor:

 

Note: For you to create a new Oracle database monitor, you should have admin privileges. Minimum User Privileges -> user with CONNECT and SELECT_CATALOG_ROLE roles

  1. Click on New Monitor link.

  2. Select Oracle DB Server.

  3. Enter the IP Address or hostname of the host.

  4. Enter the SubNetMask of the network.

  5. Enter the port number in which the Oracle is running.

  6. Enter the polling interval time in minutes.

  7. If you are adding a new monitor from an Admin Server, select a Managed Server.

  8. Provide the user name of the admin user ('system' is the default username) and its corresponding password.

  9. Provide a valid System Identifier / Host Connection String.

  10. Choose the Monitor Group from the combo box with which you want to associate Oracle database server Monitor (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers Oracle database server from the network and starts monitoring them.

 

Oracle NoSQL Server

 

Follow the given steps to create a Oracle NoSQL server monitor:

 

Note:


  1. Click on New Monitor link.

  2. Select Oracle NoSQL.

  3. Enter the Display Name of the monitor
  4. Enter the IP Address or hostname of the host.

  5. Enter the JMX Port in which the JMX is running.

  6. Enter the Additional JMX Port in which the JMX is already running in any of the other machine of the same cluster.
  1. Choose the Credential Details either use below credentials or select from credential list
  2. Enter the Username and Password of the Oracle NoSQL.

  3. Enter JNDI Path ex. /jmxrmi
  4. Enter the polling interval time in minutes.

  5. Choose the Monitor Group from the combo box with which you want to associate Oracle database server Monitor (optional). You can choose multiple groups to associate your monitor.

  6. Click Add Monitor(s). This discovers Oracle database server from the network and starts monitoring them.

 

Setting up JMX for Oracle NoSQL monitoring


Oracle NoSQL Database allows Java Management Extensions (JMX) or Simple Network Management Protocol (SNMP) agents to be optionally available for monitoring, in addition to the native monitoring provided by the Admin CLI and the Admin Console. These agents provide interfaces on each storage node that allow management clients to poll them for information about the status, performance metrics, and operational parameters of the storage node and its managed services, including replication nodes and admin instances. Both these management agents can also be configured to push notifications about changes in the status of any of the services, and for violations of preset performance limits. The JMX interface can be enabled in either the Community Edition or the Enterprise Edition. To use SNMP, however, you must have the Enterprise Edition. The JMX service exposes MBeans for the three types of components. These MBeans are the java interfaces StorageNodeMBean, RepNodeMBean, and AdminMBean in the package oracle.kv.impl.mgmt.jmx. For more information about the status reported for each component, see the javadoc for these interfaces.


The same information that is reported via JMX can also be reported through SNMP. In this case, the information is organized according to the Management Information Base (MIB) named OracleNosqlMIB, which is included with the Enterprise Edition, in the file lib/nosql.mib.

Simple Network Management Protocol (SNMP) and Java Management Extensions (JMX)


Both the SNMP and JMX agents in NoSQL Database are read-only interfaces and allow you to poll the storage nodes for information about the storage node and about any replication nodes or admins that are hosted on the storage node. The available information includes service status (such as, RUNNING, STOPPED etc.), operational parameters, and performance metrics. SNMP and JMX traps/notifications are also delivered for particular events. Notifications are sent for every service status state change; and for violations of performance limits.

Enabling Monitoring

Monitoring can be enabled on a per-storage node basis in two different ways:

In the Bootfile

You can specify that you want to enable JMX or SNMP in the storage node's boot configuration file. Usually, these files are created by using the makebootconfig utility, which has the following options to control these features:

  • [-mgmt {snmp|jmx|none} -pollport <snmp poll port>]
    
  • -traphost <snmp trap/notification hostname>]
    
  • -trapport <snmp trap/notification port>]
    

Note

When you specify -mgmt snmp, you must also specify -pollport. The SNMP agent listens for connections from SNMP management clients on this port. You may also optionally specify -traphost and -trapport to indicate the destination address for notifications. This would be the hostname and port number of an SNMP management service that is configured to receive notifications at that address.

Note

When you specify -mgmt jmx, you do not have to specify -pollport. A storage node's JMX agent uses the RMI registry at the same port number as is used for all other RMI services managed by the storage node. (This port number is specified as the -port argument to makebootconfig.)

By Changing Storage Node Parameters

You can still enable JMX or SNMP after a store is deployed, by changing the storage node parameters "mgmtClass", "mgmtPollPort", "mgmtTrapHost", and "mgmtTrapPort". Similar to configuring via makebootconfig, the "mgmtPollPort", "mgmtClass", "mgmtTrapHost", and "mgmtTrapPort" are used only for SNMP; and the parameter "mgmtPollPort" must be set when enabling SNMP.

The value of the "mgmtClass" parameter may be one of the following class names:

  • To enable JMX:

    oracle.kv.impl.mgmt.jmx.JmxAgent
  • To enable SNMP:

    oracle.kv.impl.mgmt.snmp.SnmpAgent
  • To enable neither JMX nor SNMP:

    oracle.kv.impl.mgmt.NoOpAgent

For example, you could issue the following command in the Admin CLI to enable SNMP on a storage node:

plan change-parameters -service sn1 -wait -params \
mgmtClass=oracle.kv.impl.mgmt.snmp.SnmpAgent \
mgmtPollPort=5002 mgmtTrapHost=192.168.26.42
mgmtTrapPort=32767

Note

Only a single implementation of the management agent may be enabled at a particular time. If you enable SNMP on a storage node where JMX is already enabled; the JMX agent shuts down, and the SNMP agent takes its place.


Displaying the NoSQL DB MBeans

To view the NoSQL Database JMX Mbeans in a monitoring tool such as JConsole, connect using the hostname and registry port for each Storage Node that you would like to view. This is the port that is named by the "-port" argument to the java -jar kvstore.jar makebootconfig command. It is also used in the deploy-sn plan during configuration. The documentation examples use 5000 as the registry port.

For example, you would specify localhost:5000 to the JConsole Remote Process connection box in the New Connection tab.



Top


MS SQL Database Server

To create a MS SQL database server Monitor, follow the given steps:

  1. Click on New Monitor link.

  2. Select MS SQL DB Server.

  3. Enter the IP Address or Hostname of the host.

  4. Enter the SubNetMask of the network.

  5. Enter the Port number in which the MS SQL is running.

  6. Enter the Polling interval time in minutes.

  7. If you are adding a new monitor from an Admin Server, select a Managed Server.

  8. Provide the User Name and Password of user who has permission to access the MS SQL database. The user name specified for collecting the data from MS SQL Server should have either System Administrator role or the user should be the DB owner for master database. Alternatively, you can provide the Windows Authentication details (give the User Name like domainname\username) also.

  9. If you want to connect using a Named Instance, check the Connect using Named Instance checkbox and specify the InstanceName.

  10. Choose the Monitor Group from the combo box with which you want to associate MS SQL database server Monitor (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers MS SQL database server from the network and starts monitoring them.

Note:

Minimum User Privileges: User should be permitted to access MASTER database & MSDB database.

Roles: public + db_datareader should be selected for both MASTER and MSDB databases.

For MS SQL 2005, 2008 and 2012 user roles:
Database Accessed: Master

Permit in Database Role: db_datareader & Requires VIEW SERVER STATE permission on the server.

 

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.

 



IBM DB2 Database Server

To create a IBM DB2 database server Monitor, follow the given steps:


Note: IBM DB2 ver.8 and ver.9 monitoring is supported. A DB2 user with SYSMON instance level authority is required for monitoring DB2 server.

  1. Click on New Monitor link.

  2. Select DB2 DB Server.

  3. Enter the IP Address or hostname of the host.

  4. Enter the SubNetMask of the network.

  5. Enter the port number in which DB2 is running.

  6. Enter the polling interval time in minutes.

  7. If you are adding a new monitor from an Admin Server, select a Managed Server.

  8. Provide the user name and password of user who has permission to access the DB2 database. The user name specified for collecting the data from DB2 Server should have either System Administrator role or the user should be the DB owner for master database.

  9. Specify the Database Name.

  10. Choose the Monitor Group from the combo box with which you want to associate DB2 database server Monitor (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers DB2 database server from the network and starts monitoring them.

 

Top

 

Sybase Database Server

To create a Sybase database server Monitor, follow the given steps:


Note: Sybase ASE ver.12.5.3 and above monitoring is only supported.

  1. Click on New Monitor link.

  2. Select Sybase.

  3. Enter the IP Address or Host Name of the host.

  4. Enter the SubNetMask of the network.

  5. Enter the port number in which sybase is running.

  6. Enter the polling interval time in minutes.

  7. If you are adding a new monitor from an Admin Server, select a Managed Server.

  8. Provide the user name and password of user who has permission to access the Sybase database. The user name specified for collecting the data from Sybase should have either System Administrator role or the user should be the DB owner for master database.

  9. Specify the Database Name.

  10. Choose the Monitor Group from the combo box with which you want to associate Sybase database server Monitor (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers Sybase database server from the network and starts monitoring them.

 

Top

PostgreSQL Database Server

To create a PostgreSQL database server monitor, follow the steps given below:

  1. Click on New Monitor link.

  2. Select PostgreSQL.

  3. Enter the Display Name of the database server.

  4. Enter the IP Address or Host Name of the host.

  5. Enter the port number in which PostgreSQL is running.
  6. Provide the user name and password of user who has permission to access the PostgreSQL database.

  7. Specify the DBName.
  8. Enter the polling interval time in minutes.
  9. If you are adding a new monitor from an Admin Server, select a Managed Server.

  10. Choose the Monitor Group with which you want to associate the PostgreSQL database server to, from the combo box (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers PostgreSQL database server from the network and starts monitoring them.

 

Top

Memcached Server

To create a Memcached database server monitor, follow the steps given below:

  1. Click on New Monitor link.

  2. Select Memcached under Cloud Computing/Virtualization category.

  3. Specify the Display Name of the memcached server

  4. Enter the HostName or IP Address of the host where Memcached server runs.

  5. Enter the Port where the server is running.

  6. If you want to enable Transaction test, select 'Yes' radio button, otherwse select 'No' button.

  7. Set the Polling Interval.

  8. If you are adding a new monitor from an Admin Server, select a Managed Server.

  9. Choose the Monitor Group with which you want to associate the Memcached server to, from the combo box (optional). You can choose multiple groups to associate your monitor.

  10. Click Add Monitor(s). This discovers the Memcached server from the network and starts monitoring it.

Top

Cassandra Server

To create a Cassandra database server monitor, follow the steps given below:

  1. Click on New Monitor link.

  2. Select Cassandra .

  3. Specify the Display Name of the Cassandra monitor

  4. Enter the HostName or IP Address of the host where Cassandra server runs.

  5. Enter the JMX Port where the server is running.By default, it will be 7199 or else check in cassandra-env.sh file for the JMX_PORT.

  6. If you want to discover only this node, disable the option Discover all nodes in the Cluster. By default, it is enabled which means all the nodes in the cluster are discovered by default.

  7. Check the Is Authentication Required field, to give the JMX credentials to be used to connect to the Cassandra server. Now enter the UserName and Password of the credential.

  8. Specify the Polling Interval in minutes.

  9. If you are adding a new monitor from an Admin Server, select a Managed Server.

  10. Choose the Monitor Group with which you want to associate the Cassandra server to, from the combo box (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers the Cassandra server from the network and starts monitoring it.

Top

 

CouchBase Server

To create a CouchBase server monitor, follow the steps given below:

  1. Click on New Monitor link.

  2. Select CouchBase from Database Servers.

  3. Specify the Display Name of the Mongo monitor

  4. Enter the HostName or IP Address of the host where CouchBase process runs.

  5. Enter the Port where the server is running.By default, it will be 8091.

  6. Specify the Polling Interval in minutes.

  7. Choose the Monitor Group with which you want to associate the CouchBase server to, from the combo box (optional). You can choose multiple groups to associate your monitor.

  8. Click Add Monitor(s). This discovers the CouchBase server from the network and starts monitoring it.

 

Top

Mongo Server

To create a Mongo database server monitor, follow the steps given below:

  1. Click on New Monitor link.

  2. Select Mongo.

  3. Specify the Display Name of the Mongo monitor.

  4. Enter the HostName or IP Address of the host where MongoDB/mongo process runs.

  5. Enter the Port where the server is running.By default, it will be 27017.

  6. To discover only this node and not all nodes in the ReplicaSet / Sharding disable the option Discover all nodes in the ReplicaSet / Sharding. By default, it is enabled.

  7. Check the Is Authentication Required field, to give the credentials to be used to connect to the MongoDB server. Now enter the UserName and Password of the credential.

  8. Specify the Polling Interval in minutes.

  9. If you are adding a new monitor from an Admin Server, select a Managed Server.

  10. Choose the Monitor Group with which you want to associate the MongoDB server to, from the combo box (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers the MongoDB server from the network and starts monitoring it.

Top

Redis Server

To create a Redis database server monitor, follow the steps given below:

  1. Click on New Monitor link.

  2. Select Redis.

  3. Specify the Display Name of the Redis monitor

  4. Enter the HostName or IP Address of the host where Redis server runs.

  5. Enter the Port where the server is running.By default, it will be 6379. Or else you can also check it in the redis.conf file.

  6. To discover only this node and not all nodes in the cluster disable the option Discover all nodes in the cluster. By default, it is enabled.

  7. Check the Is Authentication Required field, to give the credentials to be used to connect to the Redis server. Now enter the Password of the credential.

  8. Specify the Polling Interval in minutes.

  9. If you are adding a new monitor from an Admin Server, select a Managed Server.

  10. Choose the Monitor Group with which you want to associate the Redis server to, from the combo box (optional). You can choose multiple groups to associate your monitor.

  11. Click Add Monitor(s). This discovers the Redis server from the network and starts monitoring it.

If you have added Monitors and not associated them with a Monitor Group, you can do this manually anytime. For information on associating a Monitor with a Monitor Group, refer to Associating Monitor with Monitor Groups topic.

Top

 

HBase

Follow the given steps to create a HBase server monitor:

 Only HBase version 1.x is supported.

  1. Click on New Monitor link.

  2. Select HBase.

  3. Enter the Display Name of the monitor
  4. Enter the IP Address or hostname of the host.

  5. Enter the JMX Port in which the JMX is running. For default installations of HBase, the JMX port number is 10101 for Master and 10102 for RegionServer.

  1. Enter the Username and Password of the HBase. If no authentication is required, then leave the fields blank.

  2. Enter JNDI Path ex. /jmxrmi
  3. Enter the polling interval time in minutes.

  4. Choose the Monitor Group from the combo box with which you want to associate HBase database server Monitor (optional). You can choose multiple groups to associate your monitor.

  5. Click Add Monitor(s). This discovers HBase database server from the network and starts monitoring them.


Setting up JMX for Oracle Coherence monitoring

JMX MBeans are used to collect HBase metrics. To enable JMX, open hbase/conf/hbase-env.sh and uncomment/add the below JVM arguments.

export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10101"
export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10102"


Top

 

IBM Informix

 

Supported versions of Informix Server: Informix 10.x & above.

 

Prerequisite: Click to know about the user previleges and other necessary prerequisites to monitor IBM Informix database.

To create an Informix Server Monitor

  1. Click on New Monitor link.

  2. Select Informix under Database Servers.

  3. Specify the Display Name of the Informix monitor

  4. Enter the HostName or IP Address of the host where Informix server is installed.

  5. Enter the port number for eg., 1526.

  6. Enter the Database Server name i.e the name of the Informix database server to which you want to connect.

  7. You can enter your own credential details or select preconfigured credentials from Credentials Manager. If you wish to enter your own credentials, specify Informix username and password details for this monitor.

  8. Set the Polling Interval.

  9. If you are adding a new monitor from an Admin Server, select a Managed Server.

  10. Choose the Monitor Group from the combo box with which you want to associate Informix Server Monitor (optional). You can choose multiple groups to associate your monitor.

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

Top


SAP HANA

 

To create an SAP HANA Server Monitor

  1. Click on New Monitor link.

  2. Select SAP HANA under Database Servers.

  3. Specify the Display Name of the SAP HANA monitor

  4. Enter Host Name of HANA server.

  5. If Using SAP HANA Cloud Platform,

  6. Enter Port as IndexServer port, default port is 30015.

  7. You can enter your own credential details or select pre-configured credentials from Credentials Manager. If you wish to enter your own credentials, specify SAP HANA username and password details for this monitor.
  8. Enter Database Username and Database Password.

  9. Enter Instance Name.

  10. Set the Polling Interval.

  11. If you are adding a new monitor from an Admin Server, select a Managed Server.

  12. Choose the Monitor Group from the combo box with which you want to associate SAP HANA Server Monitor (optional). You can choose multiple groups to associate your monitor.

  13. Click Add Monitor(s). This discovers Informix server from the network and starts monitoring them.

Prerequisites:

  1. Need to copy ngdbc.jar into the location /working/classes.
    ngdbc.jar can be copied from installed SAP HANA Client folder.
    Click here to download SAP HANA Client
  2. If HANA is running ondemand, in addition to the above SAP Cloud Platform SDK is needed, this is not needed for HANA On premise.
    Click here to download SAP Cloud Platform SDK.
    The downloaded zip should be extracted under APM_HOME/working/hanacloud folder. After extracting need to verify whether APM_HOME/working/hanacloud/tools folder is available.
  3. Need to restart APM after performing the above steps.
  4. To effectively monitor SAP HANA, the SAP HANA DB User must have the below privileges,
    • System privilege CATALOG READ.
    • Object privilege SELECT on the schema _SYS_STATISTICS.
    To grant these privileges to the user, execute the below statements in SAP HANA SQL console.(Replace USER_NAME with actual HANA DB Username)

Top


See Also

Monitor Information - Database Server | Create Other New Monitors

 

 

<< Prev

Home

Next >>

Database Query Monitor

Oracle E-Business Suite