are responsible for providing access to the underlying data presented by the server. The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available). ds-cfg-backend top Indicates whether the backend is enabled in the server. If a backend is not enabled, then its contents are not accessible when processing operations. ds-cfg-enabled Specifies the fully-qualified name of the Java class that provides the backend implementation. org.opends.server.api.Backend ds-cfg-java-class Specifies a name to identify the associated backend. The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server. ds-cfg-backend-id Specifies the behavior that the backend should use when processing write operations. Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability-mode property is also enabled). Causes all write attempts to fail. Causes external write attempts to fail but allows writes by replication and internal operations. ds-cfg-writability-mode Specifies the base DN(s) for the data that the backend handles. A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN. No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. ds-cfg-base-dn