chap-whats-new.xml revision 3b574cd1ee8b7536278db5241e8aef5155e371d3
<?xml version="1.0" encoding="UTF-8"?>
<!--
! CCPL HEADER START
!
! This work is licensed under the Creative Commons
! Attribution-NonCommercial-NoDerivs 3.0 Unported License.
! To view a copy of this license, visit
! or send a letter to Creative Commons, 444 Castro Street,
! Suite 900, Mountain View, California, 94041, USA.
!
! You can also obtain a copy of the license at legal-notices/CC-BY-NC-ND.txt.
! See the License for the specific language governing permissions
! and limitations under the License.
!
! If applicable, add the following below this CCPL HEADER, with the fields
! enclosed by brackets "[]" replaced with your own identifying information:
! Portions Copyright [yyyy] [name of copyright owner]
!
! CCPL HEADER END
!
! Copyright 2011-2015 ForgeRock AS.
!
-->
<chapter xml:id='chap-whats-new'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://docbook.org/ns/docbook
xmlns:xlink='http://www.w3.org/1999/xlink'>
<title>What's New in OpenDJ <?eval ${docTargetVersion}?></title>
<para>Compared to the OpenDJ <?eval ${docPreviousVersion}?> release, OpenDJ
<?eval ${docTargetVersion}?> provides the following new features.</para>
<itemizedlist>
<listitem>
<para>TODO</para>
</listitem>
<listitem>
<para>
OpenDJ directory server now provides alternative backend types
for backends that use embedded databases for storage
(<link
xlink:show="new"
>OPENDJ-1602</link>).
</para>
<para>
Alternative backend types continue to provide
the same high-performance full LDAPv3 compliance
and the same ease of use as previous choices.
</para>
<para>
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.
</para>
</listitem>
<listitem>
<para>
The <command>dsconfig</command> command now supports
a <option>--batch</option> option for reading subcommands from standard input
(<link
xlink:show="new"
>OPENDJ-1840</link>).
</para>
</listitem>
<listitem>
<para>
OpenDJ directory server now requires a privilege,
<literal>changelog-read</literal> to read and search entries
under <literal>cn=changelog</literal>
(<link
xlink:show="new"
>OPENDJ-1351</link>).
</para>
</listitem>
<listitem>
<para>
OpenDJ directory server now provides a mechanism
to reference password validators from subentry password policies
(<link xlink:show="new"
>OPENDJ-1295</link>).
</para>
</listitem>
<listitem>
<para>
OpenDJ directory server has
an improved replication changelog implementation
(<link
xlink:show="new"
>OPENDJ-1215</link>).
The configuration refers to the previous implementation
as <literal>je</literal> because it uses Berkeley DB Java Edition,
and to the new implementation
as <literal>log</literal> because it uses log files.
</para>
<para>
When you install a replicated directory server,
the new implementation is selected by default.
</para>
<para>
After upgrading a replicated directory server,
you can use the new implementation
by changing the advanced replication server configuration property
<literal>replication-db-implementation</literal>
to <literal>log</literal> using the <command>dsconfig</command> command.
</para>
</listitem>
<listitem>
<para>Debian and RPM packages now provide service management scripts so
that you can manage the server with the <command>service</command>, and
(<link xlink:show="new"
>OPENDJ-1068</link>, <link xlink:show="new"
>OPENDJ-1114</link>).</para>
</listitem>
<listitem>
<para>OpenDJ REST LDAP gateway now supports SSL and StartTLS connections
to directory servers (<link xlink:show="new"
>OPENDJ-1033</link>).</para>
</listitem>
</itemizedlist>
</chapter>