Clearly indicated in the "Java" requirements section that DS requires Java 11.0.6 or later.
Updated "Troubleshooting" to clarify that proxied authorization as an anonymous user is supported, but not recommended.
Updated "Manual Initialization" to clarify the limitations of alternative methods for manually initializing replicas.
Added "Back Up Using Snapshots" and "Restore From a Snapshot" to explain the constraints when using file system snapshots for backing up and restoring directory data.
Updated "Restore" to clarify that even a single directory server replica replays changes after you restore data, and to link to the procedure for restoring data to a known state, should you choose to prevent this.
Added "Remove a Bootstrap Replication Server" to demonstrate how to purge a bootstrap replication server from other servers' configurations.
DS servers now purge replica state from memory and from changelogs when a replica disappears for longer than the replication purge delay. This happens without any administrative action. They do not purge bootstrap replication servers from their configurations, however. You must do that manually after retiring a bootstrap replication server.
Updated Known Issues to mention the issue OPENDJ-7905. Follow the link to the issue to find suggested workarounds.
Release of Directory Services 7.0.2 software.
Adapted the Upgrade Guide to make it easier to use:
When Adding New Servers reiterates that replication configuration now happens at setup time, and clarifies that the new replica cannot initially connect to an existing standalone replication server.
The existing server must be a directory server, not a standalone replication server.
After You Upgrade describes how to manually update LDAP schema after upgrade.
Release of Directory Services 7.0.1 software.
The following changes were made to the documentation:
Fix Javadoc search box.
Initial release of Directory Services 7 software.
In addition to the changes described elsewhere in these notes, the following important changes were made to the documentation:
- Best Practices
Updated "Java Settings" to reflect current recommendations for JVM settings.
Added "Linux Page Caching" to explain how to avoid long pauses when the kernel flushes dirty pages to disk.
Added "Disaster Recovery".
Added On Load Balancers with recommendations for your deployment.
Added "Tune Settings" to underline the importance of revisiting tuning settings during major version upgrades.
Added "Custom Schema" to demonstrate how to add a custom attribute with an enumeration syntax.
Updated "Server Commands" to explain that commands that change server files must run as a user who has the same filesystem permissions as the user who installs and runs the server.
Updated Groups to more strongly recommend dynamic groups over static groups.
Updated Authentication (Binds) to emphasize the role of identity mappers.
- Better Examples
Many more examples throughout the documentation now use secure connections to servers.
Examples in the documentation use the hostname
localhost to contact local DS servers. Trust in the examples depends on the use of a deployment key and password when setting up servers. A server certificate generated from a deployment key and password has
localhost as the default hostname. By using the
--hostname localhost option with a DS command-line tool, you simplify the secure connection process. When the tool validates the specified hostname against the hostname in the server certificate, they match. There is no need to add the server's hostname to the server certificate.
When making a secure connection to a remote server, be sure the FQDN in the
--hostname fqdn option matches a valid hostname in the server certificate. If the server certificate is generated with a deployment key and password, you can easily renew the certificate to change or add a hostname. For examples, see "Replace a TLS Key Pair" or "Generate a Key Pair (Wildcard Certificate)".
Adapt the examples as necessary when using your own certificates, keys, and PKI.
Updated Getting Started to include Windows PowerShell examples alongside the Bash examples.
Updated HTTP-Based Monitoring and LDAP-Based Monitoring to add examples showing how to monitor operation and work queue statistics, database size, and active users.