Job PreloadUserData

Purpose

The PreloadUserData job preloads selected, cost-intensive user data for persons who successfully logged in on the last working day. This allows subsequent views and actions to respond faster.

In the descriptor that ships with the product, the job is currently not active, but it is configurable.

Selection of persons

Successful logins on the last working day within the configured time window are taken into account. If the job is assigned to a client, only persons of that client are taken into account. Default values for missing times are 7:45 a.m. to 9:00 a.m.

Preloaders and processing

• The available UserDataPreloader beans are determined from the Spring context at startup.
• With Use all available preloaders?, all preloaders found are used. Otherwise only the selected preloaders are used.
• With Maximum number of persons, the number of persons processed is limited. A value less than or equal to 0 is technically treated as 2000.
• The preloaders are executed one after another for each person. A progress status is logged every 100 persons.
• At the end, the job logs the total runtime, the number of persons processed and the average runtime for each preloader.

Configuration

• Time window for users logged in on the last working day: Fields for start and end in the format HH:mm.
• Use all available preloaders?: Uses all preloaders registered in the application context or only the selection.
• Preloader selection: Multiple selection of the available UserDataPreloader implementations if not all are used.
• Maximum number of persons: Maximum number of persons per run; the initial value in the form is 2000.

Which specific preloaders are available depends on the installed modules and their Spring registration. The general job parameters such as trigger and mail notification apply as described in the central job management.