We have just uploaded OpenDS 1.0.0-build009, built from revision 3597 of our source tree, to our promoted builds folder. The direct link to download the core server is: https://opends.dev.java.net/files/documents/4926/80019/OpenDS-1.0.0-build009.zip

The direct link to download the DSML gateway is: https://opends.dev.java.net/files/documents/4926/80022/OpenDS-1.0.0-build009-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL http://www2.opends.org/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more information.

Detailed information about this build is available at

http://www2.opends.org/promoted-builds/1.0.0-build009

Major changes incorporate since OpenDS 1.0.00-build08 include:

• Revision 3468 (Issue #2214) — Add the ability to accept certificates permanently in the graphical user interface. Fix an issue where the Subject DN of the certificate was not parsed correctly and and reported a host name mismatch.
• Revision 3469 (Issue #1902) — Fix an issue where dsconfig set-backend-prop did not check whether values provided exceeded the maximum value for a property.
• Revision 3470 — Add checks to avoid problems with DN comparison in the QuickSetup code.
• Revision 3473 (Issue #2347) — Fix an issue in which the dsconfig command would exit of no JE indexes were configured and a user attempted to view or edit them.
• Revision 3485 (Issue #2613) — Fix a problem with the upgrade commands which were breaking the replication mechanism.
• Revision 3486 (Issue #2618) — Fix an issue in which the dsframework register-server command was failing.
• Revision 3487 (Issue #2617) — Fix a NullPointerException in the dsreplication status command.
• Revision 3488 (Issue #2085) — Partial fix for a problem in which dsconfig did not close connections properly. This fix applies to dsconfig interactive mode only.
• Revision 3489 — Add two targets (run-server and run-dsconfig) that enable you to run the server or dsconfig without using a shell script, for example, from Netbeans. Also add two targets (nb-debug-server and nb-debug-dsconfig") that enable you to debug the server and dsconfig from Netbeans.
• Revision 3492 (Issue #2614) — Allow the ldif-directory property of an LDIF connection handler to be a relative path.
• Revision 3493 — Add nodetach to get server output when using the run-server and nb-debug-server targets. Enable debugging in the nb-debug-server target. Add a new nb-profile-server target for one click server profiling from NetBeans.
• Revision 3499 (Issue #2565) — Fix a Java Exception that occurred during replication conflict resolution.
• Revision 3504 (Issue #2630) — Fix a problem in in which the dsreplication pre-external-initialization command did not work correctly with a binary copy.
• Revision 3507 (Issue #1732) — Provide bundled installation documentation in an html file called install.html at the top level install directory.
• Revision 3511 (Issue #2319) — Protect access to the dc=replicationChanges suffix by default, using a global ACI that denies all operations for all users other than the Directory Manager.
• Revision 3513 (Issues #2007 and #2049) — Provide a generic mechanism for using multiple caches and fix an issue in which dsconfig was unable to configure the entry cache.
• Revision 3519 (Issue #2615) — Fix a deadlock in the change log trimming that caused a subsequent deadlock of the replication server.
• Revision 3522 (Issue #2331) — Fix an issue in which the manage-tasks command was always run interactively.
• Revision 3525 (Issue #2655) — The class org.opends.server.replication.server.ReplicationCache has been renamed as org.opends.server.replication.server.ReplicationServerDomain.
• Revision 3528 (Issue #2633) — Fix an issue in which new updates were not replicated when initializing a topology with dsreplication initialize-all, unless the server on which the data was originally imported was restarted.
• Revision 3529 (Issue #2658) — Fix a problem causing unexpected behavior when monitoring the entry cache.
• Revision 3532 (Issue #2587) — Fix an issue in which dsreplication enable failed to initialize the schema of a secondary server if the user schema contained a new object class dependent on a new attribute type.
• Revision 3536 (Issue #2661) — Make the classes in org.opends.messages public so that they can be referenced from other public APIs.
• Revision 3538 (Issue #2086) — Make FIFO the default entry cache instead of Soft Reference.
• Revision 3543 (Issue #2599) — Fix an issue in which the replication mechanism added the modifiersName and modifyTimestamp to schema updates, introducing an inconsistency between the schema on replicated instances.
• Revision 3555 (Issue #2612) — Fix an issue in which initialization of the ADS failed when both servers were configured for replication separately.
• Revision 3557 (Issue #2648) — Ensure that the dsconfig and dsreplication commands support IPv6 addresses.
• Revision 3559 (Issue #2742) — Add the objectClass attribute to the Root DSE operational attributes global ACI.
• Revision 3572 (Issues #2730 and #2620) — Provide a way for users to set specific JAVA arguments (and use a specific JVM) for every command-line utility.
• Revision 3574 (Issue #2751) — Fix an issue in which the account status notification handler could not be enabled if the template files were referenced with a relative path.
• Revision 3575 (Issue #2767) — Fix an issue in which using the entryDN attribute with userattr inheritance was broken.
• Revision 3576 (Issue #2759) — Add the objectClass attribute to the list of target attributes in the global ACI that grants anonymous read access – this issue prevented anonymous users from seeing cn=schema.
• Revision 3577 — Fix a bug which prevented the Java WebStart installer from setting the JAVA_HOME environment variable.
• Revision 3582 (Issue #1862) — Provide a verbose option with the setup command. By default, the graphical setup and the command-line setup run in non-verbose mode.
• Revision 3585 (Issue #2446) — (Partial fix). Add support to the administration framework for specifying one or more "default" managed objects which should be created automatically when a parent managed object is created. This is the first step in creating default indexes automatically when a new backend is created.
• Revision 3586 (Issue #2446) — Define default indexes that should be created when a new Local DB Backend is created. The default indexes are aci (presence), objectClass (equality), and entryUUID (equality).
• Revision 3591 (Issue #2451) — It is now possible to override the default naming argument for dsconfig sub-commands using the CLI profile in the XML definitions. To do this add the naming-argument-override attribute to a relation’s CLI profile relation element.
• Revision 3592 (Issue #2451) — The CLI naming argument for virtual attributes has been over-ridden and is now name.
• Revision 3595 (Issue #2741) — Fix an issue in which adding and removing ACIs made the server unstable.
• Revision 3596 (Issue #138) — Various fixes and improvements to the DSML gateway.

Technorati Tags: directory-server, java, ldap, opends, opensource, Sun

Thanks to Sebastien Bertholet, an esteemed engineer in the Directory services quality engineering team, for producing this amazing picture of a fully partially connected topology of 150 Master Directory Servers (each master is connected to 5 other servers).

Click on the picture for the full size version for the details, but be patient the image is huge.

Technorati Tags: directory-server, ldap, Sun

We have just uploaded OpenDS 1.0.0-build008, built from revision 3463 of our source tree, to our weekly builds folder. The direct link to download the core server is: https://opends.dev.java.net/files/documents/4926/77176/OpenDS-1.0.0-build008.zip

The direct link to download the DSML gateway is: https://opends.dev.java.net/files/documents/4926/77177/OpenDS-1.0.0-build008-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL

http://builds.opends.org/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more information.

Detailed information about this build is available at http://builds.opends.org/weekly-builds/1.0.0-build008/.

Major changes incorporated since OpenDS 1.0.0-build007 include:

• Revision 3369 (Issue #2509) — Fix a problem where a non-global ACI containing an “extop” keyword target was erroneously being evaluated for all operations, instead of for extended operations only.
• Revision 3370 — Fix the computation of the replication generationID when a backend contains multiple suffixes.
• Revision 3371 (Issue #2487) — Fix a problem where the server was not updating the task entry when trying to initialize cn=schema between two servers.
• Revision 3384 (Issue #2350) — Fix error messages on replicationChanges database and null pointer exceptions when doing export-ldif without running as a task.
• Revision 3388 — Provide the ability to configure workflows manually. Up to now, a workflow was created automatically for each base DN in the backends. When new suffixes or backends were added, the associated workflows were created. Workflows were deleted as suffixes or backends were removed. In this new manual mode, every workflow in the server must be defined explicitly in the configuration. By default, the server runs in automatic configuration mode.
• Revision 3395 — Fix issues where the JE backend did not handle attributes with options and subtypes correctly when they were being indexed.
• Revision 3397 (Issue #2499) — Add a server property to allow the use nanoseconds instead of milliseconds in etime measurements.
• Revision 3398 — Ensure consistency between the status and dsconfig command-line utilities.
• Revision 3399 (Issue #2321) — Fix an issue where replication initialization was terminating with “STOPPED_BY_ERROR”.
• Revision 3400 (Issue #2520) — Fix an issue where the heartbeat monitor was causing connections to be closed too soon.
• Revision 3401 — Update the build script so that it correctly sets the maximum amount of memory available when running the compileadmin target.
• Revision 3403 (Issue #2492) — Fix a problem in which the server would refuse to allow an entry to be modified if it was associated with an invalid or nonexistent password policy.
• Revision 3404 (Issue #2559) — Update the server root DSE to include the supportedLDAPVersion attribute.
• Revision 3405 (Issue #2263) — Provide the ability to initialize the schema between two servers.
• Revision 3407 — Ensure consistency between the setup, status and dsconfig command-line utilities.
• Revision 3408 — Ensure consistency between the CLI and GUI setup with regard to proposed LDAP ports.
• Revision 3411 (Issue #2263) — Setup now automatically initializes the schema of the local server with the schema of the remote server. A new argument has been added to dsreplication enable to allow the user to specify which server should be used to initialize the schema of the other.
• Revision 3419 — Update the installer and dsreplication commands to correctly handle the case where an instance was uninstalled, but the registry was not properly cleaned up.
• Revision 3420 (Issue #2572) — Fix the case where dsreplication initialize completed but entries were missing.
• Revision 3422 — Add consistency between the dsreplication and setup commands with regard to the value proposed for the local host fully qualified name.
• Revision 3423 — Add consistency between the interactive installer and the dsconfig, setup and status commands in the format used to present certificates.
• Revision 3426 (Issue #2575) — Fix a problem in which a timeout occurred when reading monitoring information on the server. The timeout has been increased from 10 to 30 seconds to give it sufficient time to read the topology.
• Revision 3427 (Issue #2577) — Fix a problem where the replication generationID was not correctly saved in the schema backend files and provide the ability to store user attributes in the schema backend.
• Revision 3428 — Amend the dsreplication command to state explicitly that a fully qualified host name is required.
• Revision 3429 (Issue #2574) — Fix an issue in which the properties file was not taking the value of the bindPasswordFile into account.
• Revision 3433 (Issue #2580) — Update the internal operations API so that it is easier to include controls in internal operations. These changes are fully backward compatible, so that any existing code that used the internal operations API will still work without the need to update anything.
• Revision 3434 (Issues #1979, 2581, and 2420) — Fix several issues related to the JEB backend.
  
  The db directory is now created automatically if it does not already exist. When changing the db directory, a message is now displayed to let the user know the files will have to be manually moved and the backend restarted.
  
  The backend no longer uses the Database.count method in JE. The count is now obtained from the id2subtree index. If the count is not maintained or the index is corrupt, it will fall back to using Database.count.
• Revision 3435 — Update the dsreplication command to be consistent with dsconfig in the use of menus and in the order in which connection parameters are requested. Update the upgrade command to use the same menus as the other commands. Add minor changes in the uninstall command to be more consistent with dsconfig in the order in which connection parameters are provided. Fix a bug in ApplicationTrustManager related to the accepted certificates when there is a mismatch between the certificate and the host name.
• Revision 3436 — Do not add adminUidArg to the list of attributes by default. Leave this up to the tools using this attribute.
• Revision 3443 — Fix an issue with the uninstall and dsreplication commands in which all certificates were accepted automatically. Now the user is prompted to accept non trusted certificates.
• Revision 3444 — Add an administrative action for log file modifications.
• Revision 3447 (Issue #2582) — Enable support for a properties file in the setup, uninstall, and dsreplication commands.
• Revision 3449 (Issue #2588) — Fix a NullPointer exception when enabling replication.
• Revision 3452 (Issue #2424) — Add the capability to clear the generation ID in a replicated topology.
• Revision 3453 (Issue #2597) — Fix exception errors generated when restarting a replication server.
• Revision 3454 (Issue #2424) — Ensure that LDAP server that has already sent changes cannot replicate with an empty replication server.
• Revision 3455 (Issue #2424) — Add two subcommands to the dsreplication command: pre-external-initialization and post-external-initialization. These subcommands are used to ensure that a replicated topology continues to work when the entire data set is changed by using import-ldif, or binary copy.
• Revision 3456 — Phase 1 of support for Advanced Properties. Tag advanced properties and clean up various XML definitions.
• Revision 3460 (Issue #1829) — Provide additional support for Advanced Properties. Update the admin framework and dsconfig to support tagging of component definitions as advanced and customizable:
  
  – advanced components: these will not be displayed by default in dsconfig. Examples include the various system backends.
  
  – customizable components: these components are tagged as intended for customization using the CLI XML profile. Customizable components are usually the top level components previously referred to as “generic” by dsconfig. This term confused users who would, for example, mistake a “generic” backend for a JE backend.
• Revision 3461 (Issue #1618) — Fix a problem on windows where it was not possible to install to a folder with DN syntax.
• Revision 3462 (Issue #1829) — Tag components as advanced or intended for customization.

Technorati Tags: directory-server, java, ldap, opends, opensource, Sun

For the last couple of days, the OpenDS web site has not been accessible.

The domain name is being transfered from one registrar to another one, and we expect the situation to be temporary, hopefully solved after this long Thanksgiving week-end.

Meanwhile, the web site is still accessible at http://www.opends.net. Some of the links are still referring to the opends.org domain, and so does the QuickSetup.jnlp file. But once on the wiki, all links should work.

Sorry for the inconvenience.

Update on Nov 26th 2007.

http://www.opends.org is now back to normal.

Technorati Tags: ldap, opends, opensource

We have just uploaded OpenDS 1.0.0-build007, built from revision 3367 of our source tree, to our weekly builds folder. The direct link to download the core server is: https://opends.dev.java.net/files/documents/4926/73254/OpenDS-1.0.0-build007.zip

The direct link to download the DSML gateway is: https://opends.dev.java.net/files/documents/4926/73255/OpenDS-1.0.0-build007-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL

http://builds.opends.org/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more information.

Detailed information about this build including the complete changes log is available at http://builds.opends.org/weekly-builds/1.0.0-build007/.

Technorati Tags: directory-server, ldap, opends, opensource, build, Sun

We have just uploaded OpenDS 1.0.0-build006, built from revision 3294 of our source tree, to our weekly builds folder. The direct link to download the core server is https://opends.dev.java.net/files/documents/4926/71845/OpenDS-1.0.0-build006.zip. The direct link to download the DSML gateway is https://opends.dev.java.net/files/documents/4926/71848/OpenDS-1.0.0-build006-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL http://builds.opends.org/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more information.

NOTE: — Even though it is displayed as an option in the QuickSetup installer, we do not support upgrading from previous OpenDS builds to the 1.0.0-build006 release. There are some changes in this release that are not backward compatible with the configuration used by previous releases, and these changes may cause upgrade to fail.

Detailed information about this build is available at http://builds.opends.org/weekly-builds/1.0.0-build006/.

The biggest change in this build is a renaming of properties and their associated configuration attributes. The documentation wiki has been updated to reflect the changes.

We recognize that we’ve been having a little hiccup with regular builds. We’re expecting to come back to more regular builds now.

Technorati Tags: directory-server, ldap, opends, Sun

As Terry pointed out, there is a new article on BigAdmin on installing DS 6.x as an LDAP Naming Service. This goes a little bit over the basic simple developer settings as the article describes how to secure the whole system and even provide high availability with multi-master replication.

Technorati Tags: directory-server, java-enterprise-system, ldap, naming, security, Sun

This morning, Jonathan Schwartz, Sun’s CEO, was on stage for the general session at the Sun CEC 2007.

He was explaining the adoption of Open Source Software, showing places in the world where OpenSolaris was downloaded from. He then showed the same map for Glassfish and then moved to growing communities, taking as example OpenDS.

That made my day !

Technorati Tags: directory-server, glassfish, opends, opensource, Sun, suncec2007