Batch Configuration

Within Anjana Data Platform there are multiple batch processes that run unattended automatically according to the frequency configured in the system variables (AppConfiguration) table of the Configuration Portal. Some examples are the cross-role check batch or the expiration batch.

To configure the schedule, Spring cron expressions are used. These expressions consist of 6 elements that determine the execution frequency:

• The first element refers to seconds (can take values between 0 and 59).

  • Accepts * to indicate that it runs for all possible values.

• The second element refers to minutes (can take values between 0 and 59).

  • Accepts * to indicate that it runs for all possible values.

• The third element refers to hours (can take values between 0 and 23).

  • Accepts * to indicate that it runs for all possible values.

• The fourth element refers to the day of the month (can take values between 1 and 31).

  • Accepts ? to leave the field free if the day of the week has already been defined.

  • Accepts * to indicate that it runs for all possible values.

• The fifth element refers to the month of the year (can take values between 1 and 12).

  • Accepts * to indicate that it runs for all possible values.

• The sixth element refers to the day of the week (can take values between 0 and 7; both 0 and 7 represent Sunday, the remaining numbers go from 1=Monday to 6=Saturday).

  • Accepts ? to leave the field free if the day of the month has already been defined.

  • Accepts * to indicate that it runs for all possible values.

Other conventions followed:

• Commas can be used to separate the elements of a list (for example: 1,15 means the 1st and the 15th).

• A hyphen (-) can be used to express a range of elements (for example: 8-10 means from 8 to 10, both inclusive). The range always includes the endpoints.

For more examples see the official documentation: Spring Cron Expressions.

License About to Expire

The batch for the license-about-to-expire notification is configured in the AppConfiguration table via the property:

anjana.scheduling.licenseNotification is used to configure the scheduled task for sending notifications for a license that is about to expire or has already expired (default = 0 0 0 ? * * ).

The application field in the AppConfiguration table must be ‘zeus’.

User Synchronisation

The batch for synchronising users from providers to the Anjana Data database via the property:

anjana.scheduling.synchronizeUsers is used to configure the scheduled task for synchronising in the database the users coming from authentication providers (default = 0 0 0 ? * * ).

The application field in the AppConfiguration table must be ‘zeus’.

Expiration

The expiration batch is configured in the AppConfiguration table via the property:

anjana.scheduling.expiration is used to configure the expiration of objects (default: 0 45 7 ? * *).

The application field in the AppConfiguration table must be ‘kerno’.

Expiration Pre-notice

The expiration pre-notice batch is configured in the AppConfiguration table via the following properties:

• anjana.scheduling.notification is used to configure the notification for objects about to expire (default: 0 45 7 ? * *).

• anjana.notification.expiration is used to configure, in number of days, the objects that will expire within that range (default: 4).

The application field in the AppConfiguration table must be ‘kerno’.

Indexing

The batch for indexing all objects (entities and relationships) is configured in the AppConfiguration table via the following property:

anjana.scheduling.indexAll is used if periodic indexing of all application objects is to be configured (with the exceptions mentioned in the User Guide). This configuration is disabled by default.

The application field in the AppConfiguration table must be ‘minerva’.