Sun Directory product experts from all over the world will meet on April 3rd and 4th, 2008 at the Grenoble Engineering Center, France.

The Directory Masters Event brings together a highly technical community of experts in the Directory space, to share the product knowledge and best practices, enabling sales and deployments of the Sun Directory Server Enterprise Edition product. This event is opened to Sun employees and partners and there are already 40 registered attendees.

Why Grenoble, France ? Because this is where most of the development of Directory Services is taking place, and has been since 1996.

If you read this, you’re probably interested in LDAP and Sun Directory Services. So are you registered ?

See you in a couple of weeks !

And for those who cannot cross the Atlantic, we will repeat the event in the US, in the Sun facilities in Somerset NJ on May 12th and 13th, 2008. So I’ll see you there.

Technorati Tags: directory-server, enterprise, France, GEC, java-enterprise-system, ldap, Sun

As Mark already pointed out, a proposed roadmap for OpenDS has been published on the OpenDS Wiki.

It covers the coming OpenDS 1.0 release as well as proposed features and extensions for the next major release.

The OpenDS roadmap is informational and expected (like all wiki based pages) to change as developers and users are proposing and working on new ideas.

If you have ideas or projects for future releases of OpenDS, please bring them now.

Technorati Tags: java, ldap, opends, opensource, Sun

Tomonori Shioda has translated to Japanese and posted on his blog some OpenDS tutorials: Building OpenDS on the NetBeans IDE, OpenDS and LDAP port for non root users, Sun Java System WebServer 7.0 and OpenDS, Monitoring OpenDS with JConsole…

Thanks Shioda-san.

Should we start a Japanese section on the OpenDS wiki ?

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

We have just uploaded OpenDS 1.0.0-build013, built from revision 3938 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/89596/OpenDS-1.0.0-build013.zip

The direct link to download the DSML gateway is: https://opends.dev.java.net/files/documents/4926/89598/OpenDS-1.0.0-build013-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://www.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://www.opends.org/promoted-builds/1.0.0-build013

Major changes incorporated since OpenDS 1.0.0-build012 include:

• Revision 3885 (Issue #2953) — Fix an issue causing concurrent modification exceptions when the server was under heavy stress.
• Revision 3886 (Issue #2904) — Enable replication between servers of different builds.
• Revision 3893 (Issue #2886) — Provide certain status information without requiring authentication, whether the server is running or not.
• Revision 3895 (Issue #2969) — Fix an issue that caused operations with both an online and off-line mode always to be run with the default Java arguments for the online mode (client JVM and a small initial heap set).
• Revision 3896 (Issue #2970) — Ensure that an offline export returns an error code (1) if the export fails or is unsupported.
• Revision 3898 (Issue #2968) — Fix an issue that was causing dependent ADD operations to generate conflicting entries incorrectly.
• Revision 3899 (Issue #2962) — Improvements to the way in which the server selects a port during setup and replication configuration.
• Revision 3900 (Issue #2972) — Correct the usage of the stop-ds.bat command.
• Revision 3916 (Issues #2983 & #2984) — Limit the number of times that the uninstall command prompts for confirmation, and remove a Java exception that occurred with the uninstall command in some corner cases.
• Revision 3919 (Issue #2994) — Fix a Java exception that occurred an interactive upgrade was canceled.
• Revision 3921 (Issue #2998) — Do not set the OPENDS_JAVA_HOME variable in the create-rc-script command, unless the user explicitly sets the Java home.
• Revision 3922 (Issue #2809) — Add the -V option to certain command line utilities for which this option was missing.
• Revision 3930 (Issue #3005) — Fix an issue that was causing dsframework set-admin-user-properties to fail when setting the administrator password.
• Revision 3936 (Issue #3009) — Fix an issue that was causing the server to hang after several days under stress.

Note that Upgrade from OpenDS 1.0.0-build012 works 🙂

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

Brad Diggs also known as Mr. ZoneManager, one of the top experts in Sun Directory Services, pointed me to his blog post where he explains how to automatically install for testing purpose, DSEE 6 in a Solaris Container using the ZoneManager project.

It looks so easy to deploy again and again Directory Server, the Directory Service Control Center and set them all up with a single command !

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

The OpenDS project reached a new step towards the release of its final 1.0 release yesterday. After an intensive period of tests, the OpenDS 1.0.0-build012 has been promoted as OpenDS 1.0 Milestone 1.

OpenDS 1.0 Milestone 1 delivers a full LDAPv3 compliant server supporting many standard and work-in-progress extensions, with access controls, multi-master replication and much more. It has been intensively tested by a dedicated team. It is accompanied with a snapshot of the user documentation. You can read the release notes for additional details.

Now that OpenDS 1.0 Milestone 1 is done, we’re focusing our efforts on the last remaining features and on stressing the server for its reliability and stability. We’re aiming at releasing OpenDS 1.0 in May.

We’re also starting discussion on the roadmap and the features that the OpenDS community would like to see in OpenDS 2.0. If you have feedback or ideas, please join us on our next OpenDS monthly conference call on Tuesday March 4th 2008, 9m PST, 5pm GMT, 6pm CET (details have been posted on the OpenDS mailing lists). Or leave me a comment…

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

We have just uploaded OpenDS 1.0.0-build012, built from revision 3883 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/86642/OpenDS-1.0.0-build012.zip

The direct link to download the DSML gateway is: https://opends.dev.java.net/files/documents/4926/86643/OpenDS-1.0.0-build012-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://www.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://www.opends.org/promoted-builds/1.0.0-build012

Beware of one limitation: Upgrade/revert can not be supported for this build due to a flag day introduced between build-011 and build-012.

Major changes incorporated since OpenDS 1.0.0-build011 include:

• Revision 3818 (Issue #2825) — Fix an issue in which the dsconfig command output the incorrect information when listing properties in interactive mode.
• Revision 3819 (Issue #2901) — Fix a compilation issue with LDAPManagedObject.java.
• Revision 3820 (Issue #2894) — Fix an issue that caused disabling a privilege not to work correctly for unauthenticated clients.
• Revision 3821 (Issue #2413) — Add the –certnickname option to the ldappasswordmodify command so that users can specify a certificate.
• Revision 3824 (Issue #2902) — Fix an issue that caused the stop-ds -R command to restart the server with a client JVM.
• Revision 3826 (Issue #2865) — Add a ds-cfg-key-wrapping-transformation property to enable providers that do not have the current default "RSA/ECB/OAEPWITHSHA-1ANDMGF1PADDING" to specify one in the configuration.
• Revision 3828 (Issue #1459) — Fix an issue that was causing an error when replacing the userCertificate attribute.
• Revision 3832 (Issue #2249) — Fix an issue that caused some attributes to be in pending mode after running setup with secure arguments.
• Revision 3833 (Issue #2910) — Fix an issue that caused a Java exception when an incorrect admin DN was specified during the uninstall process.
• Revision 3849 (Issue #2885) — Repair the window mechanism from a replication server to an LDAP server.
• Revision 3851 (Issue #2931) — Ensure that nested groups are reloaded after an import.
• Revision 3852 (Issue #2924) — Change the setup so that the root user password is no longer visible in the setup log.
• Revision 3853 (Issue #2130) — Add support for internationalization of CLI usage.
• Revision 3854 (Issue #2922) — Fix a problem that caused error messages from the setup command to return the incorrect property name.
• Revision 3855 (Issue #2923) — Fix an issue that caused a null pointer exception if a null value was provided for the key store pin.
• Revision 3859 (Issue #2919) — Fix a problem that caused the translation of version-related properties to generate an error.
• Revision 3860 (Issue #2918) — Use standard output to display the usage and update the return codes of the status-panel command.
• Revision 3863 (Issue #2925) — Relax the required status of the digest-uri directive to maintain compatibility/interoperability with legacy client implementations.
• Revision 3867 (Issue #2921) — Ensure that CLI error messages retain the case of argument names as provided by the user.
• Revision 3869 (Issue #2911) — Fix an issue that prevented the dsreplication command from clearing all the change logs.
• Revision 3870 (Issue #2652) — Add support for the -t, –stopTime options in the stop-ds command so that the command can be executed as a task.
• Revision 3873 (Issues #2813 and #2578) — Make DN string representations more user-friendly when they contain non-ASCII characters.
• Revision 3874 — Improve error logging on monitor data.
• Revision 3878 (Issue #2877) — Fix an issue that allowed more than one LDAP connection handler to be configured with the same port.
• Revision 3881 (Issues #2906 and #2909) — Fix a problem that prevented indexed searches from returning a referral if the base entry was a referral entry.
• Revision 3883 — Improvements to replication monitoring.

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

We have uploaded OpenDS 1.0.0-build011, built from revision 3813 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/85139/OpenDS-1.0.0-build011.zip

The direct link to download the DSML gateway is: https://opends.dev.java.net/files/documents/4926/85140/OpenDS-1.0.0-build011-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-build011

Beware of one limitation:

1. Upgrade/revert can not be supported due to an incompatibility introduced between build-010 and build-011.

Major changes incorporated since OpenDS 1.0.0-build010 include:

• Revision 3661 (Issue #2446) — Add a default ordering index for the ds-sync-hist attribute. This index is required for replication.
• Revision 3664 (Issue #2814) — Fix an issue that caused dsreplication enable to fail when a user attempted to enable replication between a server with a global administrator and a server with no global administrator.
• Revision 3666 (Issue #2640) — Add support for installation from RPM packages.
• Revision 3669 — Add support to the administration framework for retrieving an internationalized description of the constraints applicable to an aggregation property.
• Revision 3670 (Issue #2805) — Fix an issue in which changes to the replication purge delay parameter were not taken into account until after the server was restarted.
• Revision 3671 (Issue #2823) — Fix an issue that was causing the replication heartbeat monitor thread to die suddenly.
• Revisions 3674 & 3675 (Issue #2806) — Avoid using the com.sun.management.OperatingSystemMXBean class within the org.opends.server.util.RuntimeInformation class (which broke compatability with the IBM JDK on AIX).
• Revision 3680 (Issue #2830) — Improvements to the build "test" target. This change modifies the "test" target so that it is as lightweight as possible but forgiving for first-time users.
• Revision 3686 (Issue #2499) — Remove the option to use nanosecond etime resolution as a JVM property. It is now a global configuration property (etime-resolution).
• Revision 3687 (Issue #2811) — Make dsreplication enable and dsreplication disable symmetric. When the last replicated suffix is disabled, replication on cn=schema and cn=admin data are also disabled and the registration information is updated.
• Revision 3689 (Issue #2004) — Automatically generate HTML-based configuration documentation.
• Revision 3695 (Issue #1288) — Make the number of listener threads for synchronization configurable.
• Revision 3700 (Issue #2822) — Update the permissions of the root file of the installation so that files such as the configuration file are read-protected.
• Revision 3703 (Issue #2499) — Additional enhancements to the ability to use nanosecond etime resolution.
• Revision 3706 (Issue #2855) — Include a reference to the log file created by the setup in the event that the user requires more information than what is displayed.
• Revision 3708 (Issues #2831 and #1948) — Change the local DB backend configuration so that the db-directory and import-temp-directory properties now name a parent directory within which a sub-directory is created having the same name as the backend-id. This simplifies configuration and reduces the risk of name collisions.
• Revision 3709 (Issue #2850) — Fix a problem that was causing the server to hang after several abandons.
• Revision 3714 (Issue #2861) — Fix an error in the logger configuration manager that was causing duplicate log messages.
• Revision 3715 (Issue #2862) — Fix an error that was causing the online backup to consider errors as warnings.
• Revision 3720 (Issue #1302) — Change the connection algorithm of an LDAP server so that each LDAP server chooses the replication server that is most up to date regarding changes received across the topology.
• Revision 3727 — Fix an issue that was causing exception errors when running an import on an empty backend.
• Revision 3735 — Fix an issue that caused LDAP connections to be performed on the local host, even if a specific listen-address was specified in the config.ldif file.
• Revision 3738 (Issue #2602) — Index definition is no longer required to change an object’s configuration. A severe warning is now logged in the error log instead of preventing the configuration change.
• Revision 3740 (Issue #2781) — Fix an unchecked exception during database transaction by updating the JE to version 3.2.70.
• Revision 3743 (Issue #2863) — Fix an issue that caused processes to continue running when all replication servers were stopped simultaneously.
• Revision 3745 (Issue #2353) — Improve the error handling in logger retention policy enforcement.
• Revision 3755 (Issue #2872) — Simplify and improve the usage of the dsjavaproperties command.
• Revision 3773 (Issue #2232) — Log a message when the back end is taken offline.
• Revision 3774 (Issue #2358) — Add progress information to the verify-index command.
• Revision 3786 (Issue #2870) — Provide the ability for the status and dsreplication status commands to show replication monitoring.
• Revision 3801 (Issue #2887) — Fix an issue that was causing the status command to exit with 0 despite connection errors being reported. Now, if there is an error reading the configuration, a specific error code is returned.
• Revision 3806 (Issue #2772) — Change the logging mechanism so that, if the preload value is set, the following items are logged automatically: the backend being preloaded, its individual databases as they are being preloaded, completion or interruption status and interruption reason.
• Revision 3810 (Issue #2820) — Fix an issue in which an uncaught deadlock exception caused a fatal replication failure.
• Revision 3812 (Issue #2598) — Provide the ability to monitor replication globally.

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

Jerome Cambon, one of the developers who recently joined the OpenDS project, has just published a tutorial for “Building and Running OpenDS with NetBeans“.
I’ve been using NetBeans on my MacBook Pro since OpenDS day one, and I’ve started this same tutorial… But got distracted by other projects.
I’m glad that Jerome took the time to write and publish this. It’s one less item on my ToDo list. And it will benefit to the developers that want to start doing development with OpenDS and with award winner NetBeans 6.0.

Technorati Tags:
sun, opends, netbeans, tutorial, opensource

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

The direct link to download the DSML gateway is:
https://opends.dev.java.net/files/documents/4926/82506/OpenDS-1.0.0-build010-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-build010

Major changes incorporated since OpenDS 1.0.0-build009 include:

• Revision 3598 (Issues #2366 and #2186) — Update indexes to order the keys before inserting them into the database. This ensures that no deadlocks occur between multiple add and modify operations. Also, disable lock timeouts for add and modify operations since deadlocks can not occur. This prevents transaction aborts and operation retry expiration due to lock timeouts of add and modify operations when the server is under high write load.
• Revision 3607 (Issue # 1862) — Provide verbosity options for the "upgrade" "setup" and "uninstall" commands.
• Revision 3608 — Increase the default value of the JVM heap size to 256Mb for building the server.
• Revision 3610 — Fix the permissions for Java Application Stubs used in MacOS X application bundles so that they are usable from within the WebStart installation.
• Revision 3611 — Set a fair ordering policy for the cacheLock and provide a better concurrency overall.
• Revision 3612 (Issue #2785) — Upgrade the Berkeley DB Java Edition version from 3.2.44 to 3.2.68.
• Revision 3614 (Issue #2345) — Provide the ability to monitor replication across a topology. Before this change, monitoring information for replication was restricted to the replication server itself, and the LDAP servers currently connected to it. With this change, each replication server exposes the delay for all replication servers in the topology.
• Revision 3615 — Provide a default "java.properties" file that includes information about setting the different java properties.
• Revision 3616 (Issue #2787) — Fix an issue in which replication sessions sometimes failed when a server disconnected and re-connected to the replication server in quick succession.
• Revision 3617 (Issue #2794) — Fix an issue in which delete operations were sometimes not replicated if they immediately followed a modify DN operation.
• Revision 3619 (Issue #2107) — Log publishers now prevent changing the log file permissions to an invalid value. The listeners will now reject changes that would prevent OpenDS from writing to the log files.
• Revision 3621 — Various improvements to the java properties tools.
• Revision 3622 (Issue #2791) — The "dsreplication enable" command always assumed that the administrator did not exist. This fix checks whether the specified administrator exists before creating it. Also fix an issue that caused "dsreplication enable" to fail if a user tried to enable a suffix between two servers that were already replicated.
• Revision 3625 (Issue #2506) — Fix a problem that caused "upgrade -r" not to work.
• Revision 3626 (Issue #2797) — The "cn" for the replication repair logger was incorrect.
• Revision 3629 (Issue #2508) — Fix a problem that caused "upgrade -a" not to work.
• Revision 3630 (Issue #2650) — The "import-ldif" command now provides information about JRE version and settings.
• Revision 3631 (Issue #2778) — Fix a null pointer exception that sometimes occurred when stopping replicated servers.
• Revision 3637 (Issue #2482) — Improve client-side referential integrity performance.
• Revision 3638 (Issue #2799) — Fix a null pointer exception that occurred when reverting an upgrade in interactive mode.
• Revision 3639 (Issue #2780) — Fix a problem in which "start-ds" did not work after reverting an upgrade from build 9 to build 8.
• Revision 3644 (Issue #2647) — Fix an issue in which the upgrade tool did not take into account the "99-user.ldif" file.
• Revision 3651 (Issue #2784) — Fix an issue in which the upgrade tool did not back up the "upgrade.bat" file, causing problems when reverting to a previous version, then attempting the upgrade again.
• Revision 3654 (Issues #2786 and #2774) — Fixes to the DSML Gateway war file.

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

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