Anjana Data includes a series of batches whose execution depends on the implemented configuration.
User synchronization
This process retrieves users from external authentication providers and loads them into the database to facilitate authorization management.
This process is located in the Zeus service.
License about to expire
This process sends a notification to the platform administrator when the license is about to expire or has already expired.
This process is located in the Zeus service.
Expiration
This process checks all application objects with an expiration date earlier than the current date and marks them as expired objects. In the case of physical assets over which Anjana has active governance, it will end up revoking access permissions if they are managed by Anjana.
This process is located in the Kerno service.
Expiration pre-notice
This process notifies all objects that are about to expire within a time period defined in the application configuration, alerting owner and subscribed users.
This process is located in the Kerno service.
Full element indexing
This process clears the Kerno Solr collection and re-indexes all Anjana objects so they are kept up to date.
All entities are indexed, and only non-native relationships, while the following cases are also excluded:
-
if an object has a null name
-
if an object has an incorrect subtype (one that is not configured)
-
if a relationship has an incorrect ARI for its source and/or target
These cases will not be indexed.
These indexing errors are recorded in the Kerno service log, where this process resides.