A stores application data in a pluggable database. ds-cfg-pluggable-backend ds-cfg-local-backend presence aci equality entryUUID equality objectClass ordering ds-sync-hist equality ds-sync-conflict equality substring cn equality substring givenName equality substring mail equality substring sn equality substring telephoneNumber equality member equality uid equality uniqueMember cn=Index cn=VLV Index enabled Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets. Note that this property applies only to the entries themselves and does not impact the index data. Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data. true ds-cfg-compact-encoding Indicates whether the backend should attempt to compress entries before storing them in the database. Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry. Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data. false ds-cfg-entries-compressed Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained. This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit. If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit. 4000 ds-cfg-index-entry-limit Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized. The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load. 0s ds-cfg-preload-time-limit Indicates whether to gather statistical information about the search filters processed by the directory server while evaluating the usage of indexes. Analyzing indexes requires gathering search filter usage patterns from user requests, especially for values as specified in the filters and subsequently looking the status of those values into the index files. When a search requests is processed, internal or user generated, a first phase uses indexes to find potential entries to be returned. Depending on the search filter, if the index of one of the specified attributes matches too many entries (exceeds the index entry limit), the search becomes non-indexed. In any case, all entries thus gathered (or the entire DIT) are matched against the filter for actually returning the search result. false ds-cfg-index-filter-analyzer-enabled The maximum number of search filter statistics to keep. When the maximum number of search filter is reached, the least used one will be deleted. 25 ds-cfg-index-filter-analyzer-max-filters Indicates whether the backend should make entries in database files readable only by Directory Server. Confidentiality is achieved by enrypting entries before writing them to the underlying storage. Entry encryption will protect data on disk from unauthorised parties reading the files; for complete protection, also set confidentiality for sensitive attributes indexes. The property cannot be set to false if some of the indexes have confidentiality set to true. false ds-cfg-confidentiality-enabled Specifies the cipher for the directory server. The syntax is "algorithm/mode/padding". The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding. Changes to this property take effect immediately but only affect cryptographic operations performed after the change. AES/CBC/PKCS5Padding ds-cfg-cipher-transformation Specifies the key length in bits for the preferred cipher. Changes to this property take effect immediately but only affect cryptographic operations performed after the change. 128 ds-cfg-cipher-key-length Specifies the amount of off-heap memory dedicated to the online operation (import-ldif, rebuild-index). Use only heap memory. ds-cfg-import-offheap-memory-size