The Nuxeo development team is happy to announce the release of Nuxeo EP and DM 5.3.2, the open source ECM Platform and Document Management application.
As you can guess from the version number, this is a maintenance release
that includes mainly bug fixes, but also numerous improvements, and some refactoring. Some of these improvements provide the power behind the upcoming new versions of Nuxeo Case Management Framework (Nuxeo CMF 1.1) and Nuxeo Digital Asset Management (Nuxeo DAM 1.1) that are built upon Nuxeo EP and DM.
Nevertheless, more than 300 Jira tickets have been resolved between Nuxeo DM 5.3.1 (that was released exactly 4 months ago) and 5.3.2.
The main new features of Nuxeo DM 5.3.2 include:
- a new configuration system (to make upgrade and administration easier);
- a new Tag Service implementation (complete integration with VCS backend);
- content automation integration;
- VCS improvements (better Oracle support and optimizations);
- new packaging options and installers;
- more translations.
For a more detailed description of these improvements, please see below.
You can download the packages for Windows, Linux, Mac OS on the download page on nuxeo.com.
The upgrade from 5.3.1 to 5.3.2 should be easy, see the upgrade notes below for more details.
A limitation of the configuration system in Nuxeo 5.3.1 and prior versions was
that each platform upgrade needed the system administrator to reconfigure the
data sources and other system-level configuration files.
We have listened to our own sys admin (who was complaining about that when
upgrading Nuxeo Cloud instances) and have changed the way configuration resources are handled.
Basically, the software packages (EAR or WAR for DM, DAM, CMF ...)
don't include anymore resources for system level configuration.
These configuration files are now handled by a template system that:
- allows you to easily change configuration (for example change the
storage configuration from a given database brand to another one);
- allows for easy upgrades (since the new EAR or WAR won't overwrite
your custom config).
One of the direct advantages of this new system is that you can now very easily switch from the default embedded storage to a production-ready storage (for instance, PostgreSQL or Oracle).
You can find a detailed description of the new configuration system here.
The Tag Service has been completely integrated with the VCS (repository) core.
As a side effect, this means that Nuxeo Core can now handle low level
relations and this opens the way for more efficient queries on the Tags
These changes will be leveraged in the 5.4 release of DM.
Content Automation is now part of the Nuxeo DM default distribution.
Content Automation provides a high level API for operations that can be used:
- from Java code
- from HTTP reuqests (via the built-in REST API)
- from Nuxeo Studio Content Automation Chains
Based on extensive benchmarks we did with 10s of millions and 100s of millions of documents in one repository, we've introduced new low level optimizations inside our VCS repository implementation.
We've also worked to improve Oracle database support and have ported our
security optimizations (already available on PostgeSQL) to Oracle.
Some of the VCS improvements won't be fully visible until we ship version 5.4 in Q4 2010, but the infrastructure work has been done and this opens the way for new features in the next release.
We have also worked on improving the way Nuxeo DM is delivered to the
end users that want to test the platform.
These improvements includes:
- a new MS Windows installer including a small monitor and new Nuxeo control panel;
- Debian and Ubuntu packages;
- a ready to run virtual machine image (to run Nuxeo DM in VirtualBox or VMWare).
Thanks to the help of our community, we have a new translation to Polish (by Adam Lozy), as well as many improvements to the translations we had before: Arabic, Basque, Catalan, Chinese, English, French, Galician, German, Italian, Japanese, Polish, Portuguese, Brazilian, Russian, Spanish and Vietnamese.
5.3.2 is fully backward compatible with 5.3.1 (no compat package is needed).
So, you should have no issues with running your custom code against 5.3.2. If you have any problems, you can contact Nuxeo Support.
The packaging system is basically the same as the one used in 5.3.1.
The only change that may have an impact involves resources that are now managed by
the new template system.
This means that resources are no longer embedded inside the EAR but
handled in a separated templates directory.
This makes changing configurations easier (like switching from H2 to
PostgreSQL) and will also allow for upgrades without having to redo all
custom system configurations.
The only changes done between 5.3.1 and 5.3.2 are the way tags are stored.
Because the Tag Service is now directly part of VCS, some small changes
have been done.
Nevertheless, migration should be automatic and transparent.
If you have any problems, you can contact Nuxeo Support.
We have changed the way Nuxeo starts OpenOffice.
This is an intermediate solution before we upgrade to JODConverter 3.
The new OOolauncher (that replaces OOodeamon) should:
- be more stable.
- be easier to set up (removed the dependencies on JNI UNO libs).