The clock is the implementation of executing a specific task for a specific service. For example, the clock for the Email Marketing service triggers the email at the pre-determined date and time.

The listed clocks are those belonging to the services registered in the portal. Once the service's registration is removed, its corresponding clock or clocks will also be automatically removed from the Task Manager.

Custom services can use clocks. To do this, they must implement a java class that extends GenericServiceClock. The clock implementation class must also be defined in the servicedefinition.xml of the custom service. Upon registering the service, the clock is listed in the scheduled task manager.

It is also possible through the Manager to Enable, Disable, and Reset a clock. By default, clocks are already enabled and have predefined intervals in minutes for executing certain tasks. From then on, they can be disabled so they no longer execute such tasks, until they are enabled again.

The predefined execution intervals can be changed by adding environment properties in the Environment Configuration Manager. These properties are:

• lumis.clock.[clockId].tickInterval - integer value (for example, 3)
• lumis.clock.[clockId].tickIntervalType - string value representing one of the defined time interval types, which are: seconds, minutes, hours, or days.

In this scenario, [clockId] is the identifier of the service clock, shown on the screen of the scheduled task manager as shown in the figure below. If an execution interval of a service has been changed using these properties, its new value will be displayed in the table with a * next to the interval. Upon removing the environment properties, the value will revert to the predefined default and the * will not appear.

Through the Executing column, it is possible to check the clocks that are marked in the database as "executing." It is possible that due to some error, the process may no longer be executing but is marked in the database as "executing." In these cases, the clock remains stuck until its execution times out. Thus, the execution of the clock will be automatically released. If the administrator is already certain that the clock thread is not executing and does not want to wait for the timeout, they can click the Reset button, which marks the clock's state in the database as not executing.

In most cases, clocks execute their tasks quickly. Therefore, the information "Yes" for Executing is almost imperceptible when the date and time of the Next Execution is reached.

Each clock has a maximum execution duration. If a clock stays in the executing state for too long, when the maximum duration time is reached, the thread that executes it is automatically restarted (similar to the Reset function).

Features

• It is an administration interface

Screens

Data

Permissions

• Manage service instance: Allows managing all the data of this service instance, including deleting it entirely.

Actions

• Enable
• Disable
• Reset