Hybris Task Engine Execution Test

The SAP Hybris Task engine enables you to schedule time-based or event-based actions, even in a cluster environment. Tasks are a method of scheduling actions. With tasks, it is possible to define Spring-based actions which are triggered at defined times or upon triggering of certain events. The information regarding tasks and task execution conditions is stored in the Task Engine database.

Task engine sits at the core of SAP Hybris and is used to perform key functions like loading product data in databases, moving out unused data, basic housekeeping, etc. It is important to gather and monitor task execution-related statistics and take any remediation action if there is anything out of normal.

This test monitors task execution and collects statics that provides insights to administrators about the functioning of tasks.

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

Execution hit rate

Indicates the number of task executions per min during the last measurement period.


If the number is going down over a range of measurements, it might point to reducing processing power due to failing of execution nodes.

Execution lock time

Indicates average execution lock time due to various reasons during the last measurement period.


Lock time should be minimal. High lock time may point to issue like high instances of deadlocks etc. which needs to be resolved.

Execution time

Indicates the average execution time of task execution during lat measurement period.


Average execution time should remain steady over a range of measurements. In case it is going up, there could be an issue with underlying infrastructure.