Agents Administration - Tests

Configuration of EgDBPartitionTest This test monitors the eG backend database and reports if the database partitioning feature is supported on the database. If this database partitioning feature is supported, this test additionally reports the count of tables that were partitioned and were not partitioned. Further, the detailed diagnostics lists the tables that were partitioned and were not partitioned. The default parameters associated with this test are: The TEST PERIOD list box helps the user to decide how often this test needs to be executed. In the HOST text box, specify the IP address of the target server that is being monitored. In the PORT text box, specify port number at which the specified host listens. In the JMX REMOTE PORT text box, specify the port at which the JMX listens for requests from remote hosts. In the \manager directory (on Windows; on Unix, this will be the /opt/egurkha/manager directory) of the eG manager, you will find a management.properties file. Set the port defined against the com.sun.management.jmxremote.port parameter of the file as the JMX Remote Port. By default, JMX requires no authentication or security. Therefore, the JMX USER, JMX PASSWORD , and CONFIRM PASSWORD parameters are set to none by default. The JNDINAME is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same. This test uses a JMX PROVIDER to access the MBean attributes of the eG manager and collect metrics. Specify the package name of this JMX Provider in the given text box. By default, this is set to com.sun.jmx.remote.protocol. In the TIMEOUT text box, specify the duration (in seconds) for which this test should wait for a response from the eG manager. If there is no response from the eG manager beyond the configured duration, the test will timeout. By default, this is set to 240 seconds. Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 6:1. This indicates that, by default, detailed measures will be generated every sixth time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY. To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0. If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type. Once the necessary values have been provided, clicking on the UPDATE button will register the changes made. When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.