Hybris Data Sources Test

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.

Target of the test : A SAP Hybris system

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for data sources for each tenant

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed


The host for which the test is to be configured.


Specify the port at which the specified host listens. By default, this is 9002.

JMX Remote Port

Specify the port 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.

JMX User and JMX Password

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.

Confirm Password

Confirm the password by retyping it here.


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


Specify the duration (in seconds) 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

Detailed Diagnosis

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.

Measures made by the test
Measurement Description Measurement Unit Interpretation


This indicates the status of the Data source in last measurement period.


The status of 0 indicates the data source is offline. Usually this means either the data source has failed or has been taken offline manually. In either case you should immediately start the investigation because the whole user service would be unavailable for given tenant.

The values that this measure can report and their corresponding numeric values are tabulated below:

Measure Value Numeric Value
Active 100
Inactive 0


By default, this measure reports the above-mentioned Measure Values while indicating the status. However, in the graph of this measure, the same will be represented using the corresponding numeric equivalents only.

Connection Rate

This indicates the number of connections opened per minute in last measurement period.


If the connection rate in low, it means connections are lasting too long. Too many open connections will lead to reaching of open connection limit and can adversely affect system performance.

Open Connections

This indicates the number of open connections in the last measurement period.


If there are too many open connections, it may soon reach the limit and new connections will not be available until open connections are closed. The waiting period for new connections will impact user experience. You should start the investigation before system performance is impacted in case any of these numbers are concerning.





Used connections

This indicates the number of used connections in last measurement period.


Maximum allowed open connections

This indicates the maximum number of connections that are allowed to be open at any given time.


Percentage of open Connections

Indicates the open connections as a percentage of maximum allowed open connections.


Percentage of used connections

Indicates the used connections as a percentage of maximum allowed open connections.


Average waiting time for connections

Indicates the average time system has to wait before a new connection is available to be open.