Queued synchronization functionality introduced in OpenIDM 6.5.0 relies on a new Lock Service within the product. Although the LockService is present in the product, customers upgrading from 6.0.0 will need to:
1. Add the necessary object type to their existing repo.XYZ.json configuration files
2. Create the necessary tables within their existing repository
For #1 above, the customer must add the following to the genericmapping section of their JDBC repo configuration file:
or if they are using DJ as a repo, the following:
For #2 above, the customer must create the lockobjects and lockobjectproperties tables within their existing JDBC repository. See the OOTB openidm.sql for the relevant SQL for each of our supported JDBC repositories.
If the customer is using DJ as a repo, they must create the locks organizational unit below dc=openidm,dc=forgerock,dc=com within their existing DJ repository.