Multi-instance setups

In case of a stand-alone nevisIDM instance, the indexes are automatically updated as soon as an entity is modified. In setups where multiple nevisIDM instances use the same database and a Lucene (file system level indexing; the default one) backend, the indexes have to be kept in sync. To keep the indexes up-to-date, each nevisIDM instance runs a batch job that periodically queries all the entities that have been created, modified or deleted since the last run, and updates the indexes accordingly.

To enable this batch job in multi-instance setups,

• Set the application.queryservice.cronjob.enabled parameter in the nevisidm-prod.properties file to true.

To configure the interval between two runs of the batch job,

• Specify an appropriate time period by means of the application.queryservice.cronjob.interval parameter in the nevisidm-prod.properties file.

In version 2.83.0, the Elasticsearch backend introduced. When your system uses Elasticsearch, the previously mentioned job is not needed, you need to switch it off. This means set the application.queryservice.cronjob.enabled parameter to false.