Connection to the Job Management Database Schema

In the job management database schema, Cadenza saves jobs that are regularly executed at a specific time. Such jobs are created for the subscription function, for example, in order to send the associated notification e-mail.

In addition, Cadenza automatically cleans up unused self-service data every night. There is also a job in the job management database for this clean-up work.

Configuration and Prerequisites (Overview)

The following requirements must be met in order to use the Job Scheduler:

  • The "JobScheduling" plugin must be activated.

  • A database schema in which the jobs are managed must be prepared.

  • The number of threads that check for new jobs and execute them (e.g. executing a database request for the event-driven sending of emails) must be configured.

The corresponding jobs config must be adapted.

The connected authenticators serve as sources for the addressees of the automatically sent emails. The combined use of several sources is possible - supported authenticators are: LDAP user management and Cadenza user management in Cadenza Desktop as well as XML user management for test purposes. When connecting multiple authenticators, the following applies: To display the list of users or to determine the e-mail address of a user for sending, Cadenza goes through all authenticators in the configured order and uses the first matching entry found.

When using Single Sign-on (SSO), event-driven sending of emails is currently not supported. If this functionality is required, please contact us.

Optional:

  • The Job Scheduler instance regularly checks every minute whether a new job needs to be created and the Cadenza instances regularly check every minute whether executable jobs are available. The interval for these checks can be customized.

  • An idle thread is automatically terminated after one day. This period can be customized.

  • Cadenza regularly runs a cleanup job every 24 hours to clean up the transient and orphaned elements of a repository in the Cadenza Data Store (CDS). The interval for running the cleanup job can be customized.

Notes for Technical Operation

If Cadenza is operated in a cluster (several Cadenza instances are operated in a network via load balancing), there can be any number of Cadenza instances that execute jobs in addition to the job scheduler instance. These instances are instructed by the job scheduler instance to execute jobs. Cadenza automatically determines which instance is the job scheduler instance.

Further recommendations for operation in a cluster:

  • The job scheduler instance and the other Cadenza instances can share the configuration and repository directories.

  • For the subscription function: The URI of the load balancer must be entered as defaultBaseResultUrl in the subscriptions config and work with sticky sessions.

Prepare Database Schema for the Job Scheduler

Information on preparing database schemas

We recommend separating the database schema for the job scheduler from the database schema for the attribute/geodata and user administration in order to better map the different load profiles.

Adapt Configuration File

The corresponding configuration jobs config must be adapted. See the jobs config reference for details.