16 KiB
7.1.0 Community
New Features
With the offloading of both transforms and metadata extraction to T-Engines a number of 3rd party libraries are no longer needed within the content repository. They do still exist within the T-Engines performing the same tasks. Any AMPs that where making use of these will need to provide these libraries themselves. This will reduce the footprint of the repository and allow more frequent releases of the T-Engines to take advantage of new functionality or security patches in these libraries.
- PdfBox org.apache.pdfbox:pdfbox:2.0.21 removed - transforms are now performed in T-Engines
- PdfBox org.apache.pdfbox:fontbox:2.0.21 removed - transforms are now performed in T-Engines
- PdfBox org.apache.pdfbox:pdfbox-tools:2.0.21 removed - transforms are now performed in T-Engines
7.0.0 Community
New Features
- Metadata Extract
The out of the box extraction of metadata is now generally performed asynchronously via a T-Engine connected to the repository either as part of the Alfresco Transform Service or as a Local transformer. This provides better security, scalability and reliability. The framework used for metadata extraction within the content repository remains, allowing custom extractors / embedders of metadata to still function, as long as they don't extend the extractors that have been removed. Ideally such custom code should be gradually moved into a T-Engine. For more information see Metadata Extractors.
- Removal of Legacy transformers
In ACS 6, the Alfresco Transform Service and Local transformers where introduced to help offload the transformation of content to a separate process. In ACS 7, the out of the box Legacy transformers and transformation framework have been removed. This helps provide greater clarity around installation and administration of transformations and technically a more scalable, reliable and secure environment.
- Custom Transforms and Renditions
ACS 7 provides a number of content transforms, but also allows custom transforms to be added.
It is possible to create custom transforms that run in separate processes known as T-Engines. The same engines may be used in Community and Enterprise Editions.
For more information, see Custom Transforms and Renditions
- Core All-In-One (AIO) Transform Engine
We have previously used T-Engines for Community and Enterprise Editions that run in separate processes. (https://docs.alfresco.com/transform-service/latest/)
The Core All-In-One (AIO) Transform Engine combines the current 5x core T-Engines (LibreOffice, imagemagick, Alfresco PDF Renderer, Tika) packaged together into a single Docker image. Enterprise deployments require greater scalability and we anticipate in these situations the individual T-Engines will be preferable.
For Community deployments the AIO T-Engine, running it in a single JVM is recommended. In addition the AIO solution has been updated at with the option to build a single AIO T-Engine.
- Events related to node and association actions
With Alfresco Content Services 7.0, the Content Repository publishes events related to an initial set of actions to nodes and associations. This is the first time that this feature is introduced as part of the ACS Core Services, and it will be used in many use cases, as an example by the Alfresco SDK 5. For the moment the supported events are related to node creation/update/deletion, secondary child association creation/deletion, peer association creation/deletion.
- New REST API Endpoints:
File Rendition Management API is now available under /s POST '/nodes/{nodeId}/s/{Id}/renditions' GET '/nodes/{nodeId}/s/{Id}/renditions' GET '/nodes/{nodeId}/s/{Id}/renditions/{renditionId}' GET '/nodes/{nodeId}/s/{Id}/renditions/{renditionId}/content' Site Membership Management API is now available under /sites GET '/sites/{siteId}/group-members' POST '/sites/{siteId}/group-members' GET '/sites/{siteId}/group-members/{groupId}' PUT '/sites/{siteId}/group-members/{groupId}' DELETE '/sites/{siteId}/group-members/{groupId}' Model API: https://develop.envalfresco.com/api-explorer/?urls.primaryName=Model API - Recommended Database Patch
ACS 7 contains a recommended database patch, which adds two indexes to the alf_node table and three to alf_transaction. This patch is optional, but recommended for larger implementations as it can have a big positive performance impact. These indexes are not automatically applied during upgrade, as the amount of time needed to create them might be considerable. They should be run manually after the upgrade process completes.
To apply the patch, an admin should set the following Alfresco global property to “true”. Like other patches it will only be run once, so there is no need to reset the property afterwards.
system.new-node-transaction-indexes.ignored=falseUntil this step is completed, you will see Schema Validation warnings reported in the alfresco.log on each startup. The log will also indicate that the patch was not run.
INFO [org.alfresco.repo.domain.schema.SchemaBootstrap] [...] Ignoring script patch (post-Hibernate): patch.db-V6.3-add-indexes-node-transaction ... WARN [org.alfresco.repo.domain.schema.SchemaBootstrap] [...] Schema validation found ... potential problems, results written to ... - [MNT-20436] - “POST /nodes/{nodeId}/children” RestAPI does not create a node without having a mandatory value object, but it outputs the 201 successful response.
- [MNT-20714] - [HotFix] /nodes/{nodeId}/content REST API fails for content created by a deleted user
- [MNT-20770] - Share non responsive during direct download from S3 if content store selector is also configured
- [MNT-20863] - Changing cm:name with REST API /nodes/{nodeId} does not update Primary Path
-
Custom Transforms and Renditions
Alfresco Content Services (ACS) provides a number of content transforms, but also allows custom transforms to be added.
It is now possible to create custom transforms that run in separate processes known as T-Engines (short for Transformer Engines). The same engines may be used in Community and Enterprise Editions. They may be directly connected to the ACS repository as Local Transforms, but in the Enterprise edition there is the option to include them as part of the Transform Service which provides more balanced throughput and better administration capabilities.
For more information see Custom Transforms and Renditions
-
Open-source Transformation Engines
The core T-Engine images can now be used in Community Edition.
T-Engines code has been Open-Sourced and is available on Github:
Images are available on Docker Hub:
-
Removal of external executables from docker image
With the introduction of the new Local Transform Service in Alfresco Community Edition, the capability of executing remote transformations on T-Engines was enabled. Because of this, the external executables (Alfresco-Pdf-renderer, Libreoffice and Imagemagick) have been removed from the docker container to facilitate the usage of out-of-process transformations.
- [ALF-22013] - Docker Image for Base Tomcat locale is POSIX
- [ALF-22060] - Reader on the backing store is obtained twice in CachingContentStore
- [ALF-22056] - onCopyCompleteBehaviour not called in order of copy-action
- [ALF-22073] - MailActionExecutor doesn't consider email bodies with a HTML doctype as HTML
- [ALF-21988] - Tab order for number ranges not ok
- [ALF-22097] - T Engine - add source nodeId parameter
- [REPO-4318] - [COMPLETE] Extraction of transformers and metadata extractors
-
ActiveMQ:
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.
- [ALF-22049] - Alfresco does not start
- [ALF-22041] - EKS deployment - SOLR_ALFRESCO_HOST set to wrong host name
- [ALF-22031] - REST API calls silently rollback after the returning a success status
- [ALF-21963] - Workflow - backslash in nodeRef properties url.
- [ALF-21803] - Unable to add users to sites whose 'short name' is a substring of 'site'
- [ALF-21664] - Exception on workflow image by REST API
- [ALF-20854] - webdav error opening Spanish Accent files
- [REPO-3668] - Renditions: Transform event consumer
- [REPO-7] - Embed ActiveMQ in the Platform
- [REPO-1957] - Transformations Improvement Plan
-
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 the new DBP Transform Service takes effect. Renditions can be triggered using the existing repository REST API but will be processed asynchronously using the new services.
-
Due to the changes to the RenditionService the Media Management AMP is not supported yet.
- [ALF-21783] - ScriptAuthorityService: No way to get more than 100 results with some methods
- [ALF-21917] - Document list edit metadata incorrect url escaping
- [ALF-22001] - Faceted search does not work in Japanese
- [ALF-22030] - ADF UI freezes noticeably on a periodic basis during KeyCloak auth requests
- [REPO-2491] - Renditions: Rendition Testing
- [REPO-3651] - AWS Load Tests: Infrastructure and Revamp
- [REPO-3663] - AWS Load Tests: Initial AWS Cost Estimation with BMF
- [REPO-3667] - Renditions: Transform event producer
- [REPO-3677] - AWS Services: Basic Deployment
- [REPO-3703] - AWS Services: Native Services of ACS
- [ALF-21992] - BehaviourFilterImpl.isEnabled(NodeRef, QName) is checking wrong QName in case of subClass
- [ALF-22006] - VersionServicePolicies cannot be disabled on a specific node
- [ALF-22007] - TransactionListeners are executed in unpredictable order
- [ALF-22011] - Upgrade to XMLBeans 3.0.0