Compared to the OpenDJ release, OpenDJ provides the following new features. TODO OpenDJ directory server now provides alternative backend types for backends that use embedded databases for storage (OPENDJ-1602). Alternative backend types continue to provide the same high-performance full LDAPv3 compliance and the same ease of use as previous choices. If you do choose to make the change to a new backend type, note that you must import the data again into the new backend. This is necessary because you are effectively changing underlying storage implementations. You can make the move for example by exporting LDIF from the old backend and then importing the LDIF into the new backend, or simply through OpenDJ replication by initializing a server using the new backend from an existing replica. The dsconfig command now supports a --batch option for reading subcommands from standard input (OPENDJ-1840). OpenDJ directory server now requires a privilege, changelog-read to read and search entries under cn=changelog (OPENDJ-1351). OpenDJ directory server now provides a mechanism to reference password validators from subentry password policies (OPENDJ-1295). OpenDJ directory server has an improved replication changelog implementation (OPENDJ-1215). The configuration refers to the previous implementation as je because it uses Berkeley DB Java Edition, and to the new implementation as log because it uses log files. When you install a replicated directory server, the new implementation is selected by default. After upgrading a replicated directory server, you can use the new implementation by changing the advanced replication server configuration property replication-db-implementation to log using the dsconfig command. Debian and RPM packages now provide service management scripts so that you can manage the server with the service, and include documentation files under /usr/share/doc/opendj* (OPENDJ-1068, OPENDJ-1114). OpenDJ REST LDAP gateway now supports SSL and StartTLS connections to directory servers (OPENDJ-1033).