Agents Administration - Tests
 

Configuration of HybDataSrcTest

The SAP Hybris can be run in multi-tenant mode. In this mode several distinct sets of data is maintained on one single SAP Hybris instantiation. Each set of data is represented as a data source. This test monitors the connectivity with data sources for each tenant. eG Enterprise monitors various metrics like state of connectivity, speed, number of connections etc., which provide valuable insights to administrators about the health of the data source connectivity.

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 HOST for which this test is to be configured.

  • In the PORT text box, specify the port at which the specified host listens.

  • Specify the port in the JMX REMOTE PORT text box, at which the JMX listens for requests from remote hosts. Ensure that you specify the JMX remote port number of the SAP Hybris monitoring application. The default is 12002.

  • 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.
  • If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX in the JMX USER AND JMX PASSWORD text box.
  • Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the Provider as value “default” in the PROVIDER text box.

  • Specify the duration (in seconds) in the TIMEOUT text box, for which this test should wait for a response from the target Java application. If there is no response from the target beyond the configured duration, the test will timeout. By default, this is set to 1000 seconds if the Mode is JMX.

  • To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. 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 bad and normal 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.