When a composed attribute plugin is created in the server, it takes effect immediately
and starts creating values for any appropriate
Existing entries are not automatically populated with generated values. To populate existing entries with generated values, export the data to LDIF and then re-import it. This requires temporarily taking each instance out of service, since importing into a single instance has no effect on the data in other instances. The LDIF import option is only feasible when you are starting from scratch, not when you have existing data. To address this need, a “populate composed attribute values” task is provided. The populate composed attribute values task iterates through all entries in one or more backends and generates values as appropriate for any entries.
This task provides several number of configuration attributes, including the following:
- An optional, multi-valued attribute that can be used to specify the names or distinguished
names (DNs) of the composed attribute plugin configuration entries for which
values should be generated.Note:
If this attribute is omitted, then values are generated for all defined and enabled composed attribute plugin instances.
- An optional, multi-valued attribute that can be used to specify the backend IDs of the
backends in which values should be generated.Note:
If this attribute is omitted, then an appropriate set of backends is determined based on the include and exclude base DNs for the selected plugins.
- An optional, single-valued integer attribute that can be used to specify the maximum number
of entries to be updated per second.Note:
If this attribute is omitted, then no rate limit is imposed.
The task uses the same logic that the plugin uses for entries imported from LDIF when deciding what values to include in the entry, but it uses internal modify operations to make any updates to the entry. These changes are replicated to other servers in the topology, so the task only needs to be invoked on a single instance. However, you should only run it after the composed attribute plugins have been configured on all instances in the topology because this ensures that no entries, including those added or updated while the task is running, are overlooked.
To invoke the task and monitor its progress, use the populate-composed-attribute-values command-line tool. This processing is not expected to be needed on a regular basis, so it is not offered as a recurring task.