For Administrators

MongoDB 3.2

8.2 MongoDB 3.2 is now supported as a storage backend.

S3 Configuration via Extension Point

8.1 Customers needing to connect to more than one S3 binary managers with different configurations are now able to do so using the new configuration extension point of org.nuxeo.ecm.core.blob.BlobManager . Previously only one bucket could be configured in nuxeo.conf .

<extension point="configuration" target="org.nuxeo.ecm.core.blob.BlobManager">
    <blobprovider name="default">
        <class>org.nuxeo.ecm.core.storage.sql.S3BinaryManager</class>
        <property name="awsid">your_AWS_ACCESS_KEY_ID</property>
        <property name="awssecret">your_AWS_SECRET_ACCESS_KEY</property>
        <property name="region">us-west-1</property>
        <property name="bucket">your_s3_bucket_name</property>
        <property name="bucket.prefix">myprefix/</property>
        <property name="directdownload">true</property>
        <property name="directdownload.expire">3600</property>
        <property name="cachesize">100MB</property>
        <property name="crypt.keystore.file">/my/keystore.jks</property>
        <property name="crypt.keystore.password">password</property>
        <property name="crypt.key.alias">mykey</property>
        <property name="crypt.key.password">password</property>
        <property name="connection.max">50</property>
        <property name="connection.retry">3</property>
        <property name="connection.timeout">50000</property>
        <property name="socket.timeout">50000</property>
    </blobprovider>
</extension>

Server-Side Encryption with S3

8.1 Support for Server-Side Encryption (SSE-S3) has been added as an alternative to Client-Side Encryption (CSE) as documented in the S3 Java SDK . This is enabled through the property nuxeo.s3storage.crypt.serverside=true .

GridFS as Part of the Default Distribution

8.1 GridFS is now part of the base distribution, in nuxeo-core. It will have to be activated explicitly using the gridfsbinaries template. There is no need to install an additional Nuxeo Package anymore. Read our MongoDB documentation for more information.

SAML Addon Compatible with ADFS

8.2 After adjusting a few blind parts of the specification, the SAML plug-in has been successfully used with Active Directory Federation Services.

Elasticsearch Indexing Operations

8.1 Elasticsearch indexing operations are now available from Nuxeo Automation in addition to the Admin Center. Using a REST call you can now:

Re-index an entire repository
Re-index documents that match an NXQL query
Re-index a document and its children
Wait for indexing and perform an index refresh

Allow Separate Repository DDL Generation

8.1 Nuxeo can now start with a new nuxeo.vcs.ddlmode parameter that specifies how the DDL for repository initialization should be executed at startup. Depending on the chosen mode, the DDL may not be executed at all and instead dumped to the log/ddl-vcs-default.sql log file. Possible values for nuxeo.vcs.ddlmode are:

ignore: no DDL detected or executed. Replaces nuxeo.vcs.noddl=true.
compat: compatibility mode with previous version. Always executes DDL that recreates stored procedures (and does not attempt to detect existing ones). Replaces nuxeo.vcs.noddl=false.
execute: executes the DDL and starts Nuxeo normally.
dump: dumps the DDL (if any) to the file but still executes it and starts Nuxeo normally.
dump,ignore: dumps the DDL (if any) to the file but does not execute it and starts Nuxeo normally (will likely result in errors).
dump,abort: dumps the DDL (if any) to the file, and if not empty aborts startup.

For Nuxeo Platform 6.0 and Nuxeo Platform 7.10 the default was nuxeo.vcs.ddlmode=compat . For Nuxeo 8.2 the default is nuxeo.vcs.ddlmode=execute .

Note that all this applies to the DDL for the document repository, but not DDL used by other users of SQL in the platform (directories, quartz, JPA persistence).

Redis

Cluster Invalidation with Redis in `nuxeo.conf`

8.1 Using Redis to process cluster invalidation instead of database can be configured in nuxeo.conf using repository.clustering.invalidation=redis (it used to be in the repository contribution).

Less Memory Footprint for Redis

8.2 Some work has been done to optimize the size of serialized works, hence lowering the requirements in terms of memory size for Redis.

Redis Pool Size Configuration

8.2The Redis connection pool size can be configured using the new nuxeo.conf options:

nuxeo.redis.maxTotal (default 16)
nuxeo.redis.maxIdle (default 8)

Retry Logic For Redis Calls

8.2Nuxeo now uses a failover executor with an exponential delay policy: 1ms, 2ms, 4ms, 8ms, 16ms, 32ms .. until the timeout has reached 5min by default.

Work Manager and Shutdown

8.2There was some clean up in the way jobs were processed, especially at server's shutdown. When server is shutdown, works being processed are finished before real shutdown. If server's process is killed, job will be restarted as the system is transactional.

Web App Optimizations

8.2 Since 6.0 and migration to JSF2, some regressions on the performance of the webapp were found, especially on heavy load. Some optimization work has been done. On a commodity hardware benchmarks shows after optimization that we are able to server 25% more requests.