Hyland Connect

alee · ‎02-04-2019

These release notes provide information for the 201901 GA release of Alfresco Community Edition.

This is the GA release of Alfresco Community Edition containing the Alfresco Content Repository 6.1.2-ga. This release contains all fixes completed from the release of Alfresco Content Services through January of 2019, including a number of fixes contributed by the open source community.

Care should be taken when upgrading from any previous version of Alfresco Community Edition. Before upgrading, test that you have a functional backup of your Alfresco Repository, and read the documentation.

Goals for this Release

The main goal of this release is to get feedback on our latest GA release. You can leave that feedback in comments on this page, or by Reporting an Issue.

Please report issues with this release in the issue tracker. You can collaborate on this release by using the discussion tools in this social community. Other feedback can be provided by emailing community@alfresco.com.

Notable New Features in this Release

ActiveMQ:

We have bundled ActiveMQ now with the repository to handle raw events
Alfresco ActiveMQ Docker images: GitHub Repo DockerHub Repo

Alfresco Benchmark Framework:

The benchmark framework project provides a way to run highly scalable, easy-to-run Java-based load and benchmark tests on an Alfresco instance.
It comprises the following: Alfresco BM Manager and Alfresco BM Drivers.
The currently provided drivers are:

Java 11 support

ACS is now runnable with OpenJDK 11.0.1. It still remains compatible with JDK 1.8

Anonymous usage metrics

Alfresco Content Services collects anonymised usage metrics through the heartbeat component. This means we do not store collect or store any information that links to an identifiable person.These metrics are sent based on a pre-configured time period and include: version information, numbers of users and groups, numbers of models, aspects and types, whether smart folders are enabled or not as well as the JVM total, max and free memory size. On the receiving side, we detect the country where the data is sent from, but we do not store the IP address of reports coming from our open source products.

acs.repository.configuration -> REPO-3597
acs.repository.info -> REPO-3594
acs.repository.usage.system -> REPO-3595
acs.repository.renditions -> REPO-3681
acs.repository.usage.sessions -> REPO-3599

Alfresco is using this data to better target new features and their prioritization to actual usage patterns. We also track the adoption of new versions and features in our install base. To see exactly what is being sent, feel free to look at the log output generated by

log4j.logger.org.alfresco.heartbeat.datasender.internal.HBDataConsumer=DEBUG

If you wish to deactivate this data transmission, then you just need to add

heartbeat.enabled=false

to your configuration, either as value in alfresco-global.properties or as part of the JAVA_OPTS environment variable in the docker-compose file.

Release Contents

Alfresco Content Repository 6.1.2-ga (SCM tag)
Alfresco Share 6.1.0-RC3 (SCM tag)
Alfresco File Transfer Receiver 6.2.1 (SCM tag)
Alfresco Search Services 1.3.0-RC2 (SCM tag)
Google Docs 3.1.0 (SCM tag)
AOS Module 1.2.2 (SCM tag)
alfresco-pdf-renderer 1.1

3rd Party Components installed in the docker containers:

CentOS 7.5
Java 11.0.1
Tomcat 8.5.34
LibreOffice 5.4.6
PostgreSQL 10.1
ImageMagick 7.0.7-27

Additional docker containers used in docker-compose file:

docker.io/library/postgres:10.1

Artifacts

o alfresco-content-services-community-distribution-6.1.2-ga.zip

o alfresco-file-transfer-receiver-6.2.1.zip

o alfresco-search-services-1.3.0-RC2.zip

Content Repository

The source code for the packaging project that is used to create and run docker images and build the distribution zip can be found here.

REST API Explorer

REST API Explorer is now integrated into alfresco-repository-community docker image. It is accessible via the link provided in the /alfresco page either via using /api-explorer context on alfrescoServerPath (alfrescoScheme://alfrescoHost:alfrescoPort).

An updated release of the REST API Explorer (6.1.0-RC4) is available on GitHub - rest-api-explorer to navigate the details of the new REST API endpoints. This version includes a new API definition for Alfresco Insight Engine.

Share/

The latest version of Share is 6.1.0.-RC3. For further details please consult the list of share issues fixed in this release at the bottom of the page under Issues Addressed.

Search Services

The latest version of Alfresco Search Services is 1.3-RC2.

Governance Services

AGS 3.0 is the latest GA edition but compatibility with ACS 6.1 is targeted at AGS 3.0.1 in the March 2019 time frame. Additional details are available in the release blog post: Alfresco Governance Services 3.0.

Mobile

The latest version of Content Services for Android is version 1.8.5 which contents a number of minor improvements and fixes.

The next version of Content Services for iOS will be version 2.7 will support iPhone X and is expected to be released in February 2019.

SDK

A beta version of SDK4.0 has been release tested for compatibility with ACS 6.0. SDK 4.0 GA will be released in parallel with ACS6.1 Enterprise GA release, once testing has been completed.

Documentation

The documentation has been refreshed for this release. The documentation is currently published at docs.alfresco.com: Alfresco Community Edition

Localisation

This release includes: French, German, Italian, Spanish, Japanese, Dutch, Norwegian (Bokmål), Russian, Brazilian Portuguese and Simplified Chinese versions. We are working on additional localisations into Danish, Finnish, Swedish, Polish and Czech. Soon we will also be offering User Help and a Getting Started guide in French, German, Italian, Spanish and Japanese.

Feature Removals and Deprecations

TransformService and RenditionService:

All Java APIs related to TransformService and RenditionService have been deprecated; the ability to perform arbitrary transformations will be phased out as our new Out of Process Transform Service takes effect. Renditions can be triggered using the existing repository REST API but will be processed asynchronously using the new services.

Installation

Alfresco Community Edition is available both as a distribution zip file containing the war files and as docker images that are deployed using docker-compose.

The Alfresco Community Edition docker images are available on DockerHub.

To run this GA release with docker:

You need to have Docker installed on your machine
Make sure that the ports 5432, 5672, 8080, 8082, 8083, 8161, 61616, 61613 are available on your machine
Get the docker-compose.yml file from this release tag.
Run docker-compose up
Check that everything starts up with the browser: http://localhost:8082/alfresco and http://localhost:8082/api-explorer and http://localhost:8080/share and http://localhost:8083/solr/ and http://localhost:8161/admin

Please refer to the "Docker-compose & Kubernetes" instructions on Github - acs-community-packaging for additional details. See also the notes below (Dockerized Deployment) that covers acs-community-deployment.

Notes:

The latest GA release of Alfresco Community Edition is available from the Alfresco Community Edition product page .
It is recommended to have at least 8GB of RAM available on the system.
Latest OS patches are always recommended.

Dockerized deployment

This release comes with a set of docker images instead of a GUI installer. These docker images produce a deployment that is more closely aligned with production best practices than the previous installers were capable of creating. The docker-compose and helm charts can be found in a separate project acs-community-deployment and for this release the changes were tagged with 6.1.2-ga.

To configure Alfresco Community Edition, it is recommended to add -Dkey=value properties to the JAVA_OPTS environment variable in the docker-compose.yml file. In this EA release, all the data is still stored inside the docker containers. This is sufficient for test and development purposes. For production like environments however, it is recommended to mount locations on the host machine into the containers so that all the data (content store, DB and SOLR indexes) gets stored on the host.

Prerequisites for Manual Install

DB: MySQL or PostgreSQL
Apache Tomcat
Java JDK
LibreOffice
ImageMagick

You should use the same versions as we have in the docker containers (see above).

Issues Addressed

The issues addressed specifically in this release are available in JIRA projects for the components of this release. Note that JIRA behaves inconsistently with these queries when you are not logged in.

ALF: Improvements to Alfresco's products requested by open source collaborators. Most issues are linked to another project to get assigned to a team.
REPO: Improvements to the Alfresco Content Repository.
RM: Changes to Records Management.
SHA : Improvements in Share.

We also addressed a number of bugs since the release of Alfresco Community Edition 201808.

Known Issues

· Due to the changes to the RenditionService the Media Management AMP is not supported yet.

Please refer to the Alfresco issue tracker for other known issues in this release.