Alfresco software

Installation

The latest GA release of Alfresco Community Edition is available from the Alfresco Community Edition product page.

Download this release from Alfresco Community Edition file list 201612.

For download and installation instructions, refer to the Download and Install Alfresco page.

The Alfresco supplied installers will install all you need to run Alfresco on your machine; which includes JDK, Tomcat, SOLR, and LibreOffice. It also includes interfaces and extensions such as Share, the Google Docs integration, and the AOS module.

Notes:

  • JVM memory defaults to half system memory, minimum of 2GB.
  • Latest OS patches are always recommended.

Notable New Features in this Release

As a Generally Available release, the focus of this release has been on stability and not on new features.

The page dedicated to Alfresco Community Edition 5.2 lists all the features in the 5.2 line of Alfresco releases.

Branding

You will see some new branding in the product. This is a step in preparing new branding for a future release of our Enterprise products. This will affect some artifact naming, log messages, error messages and administration screens.

Platform

REST API Explorer

An updated release of the REST API Explorer (v5.2.e) is available (Github — alfresco-rest-api-explorer) to navigate the details. This is included in the SDK, or can be installed by adding the WAR to your Alfresco install and configuring CORS.

See also Alfresco public REST APIs to find links to more information about the new REST APIs.

Share

No incremental updates since last month’s Alfresco Community Edition 201612 GA Release.  The notes for the previous community release are .

Mobile

We provide an Early Access release of an Alfresco Java Client SDK which contains a Java lib project to easily consume Alfresco Public REST APIs. It includes a set of APIs that allows developers to quickly build Alfresco-enabled Java & Android applications:

Localisation

This release includes: French, German, Italian, Spanish, Japanese, Dutch, Norwegian (Bokmål), Russian, Brazilian Portuguese and Simplified Chinese versions.

No features have been removed in this release.

Docker Volumes

In order to enable persistent storage, several Docker Volumes are configured by default. When using from Linux, some permissions on your local folders need to be set.

Identifying the right UID for every folder can be obtained by starting Docker Compose without the volumes declaration. Following lines should be commented in file.

Once the volumes have been commented, start Docker Compose.

After that, you can find the SOLR Docker Image and the UID of the user owning data folders ( by default).

Stop Docker Container and set the right permissions on your host folder.

You could need to adjust also the permissions for user inside PostgreSQL Docker Image. By default the UID is 999, but you can perform similar operations as above to guess this number.

Uncomment the lines in your for the volumes declaration and your Docker Compose should be ready to use.

Windows volumes

For instance, for an installation in a folder named , following volumes are created.

You need to take care of this volumes for backup and other operations.

In case you want to clean your environment (loosing all the data inside), you can remove all this Docker containers to start from scratch.

For instance, for an installation in a folder name , following command will remove all the information persisted.

Описание

Alfresco ECM — система управления корпоративными данными, которая занимает лидирующие позиции на мировом рынке Open Source бизнес-приложений.

Особенности Alfresco

  • Alfresco сочетает бесплатность и открытость СПО (свободного программного обеспечения) с возможностью покупки поддержки высокого уровня, что является важным фактором для современного бизнеса при выборе корпоративного программного обеспечения.
  • Alfresco имеет широкие возможности для организации электронного документооборота, такие как загрузка и хранения неограниченного количества любых файлов и документов (через WEB-интерфейс, WebDav, CIFS), контроль доступа пользователей и версионность, хранение карточек документов и категоризация, полнотекстовый поиск и организация бизнес-процессов для работы с документами.
  • Система имеет современный Web-интерфейс для организации совместной работы. При этом все данные загружаются в основное хранилище и доступны также через стандартные интерфейсы. Alfresco позволяет создавать виртуальные сайты с возможностью разграничения прав доступа к старому и новому контенту, что очень удобно для организации проектной деятельности. Основной функционал: общие документы, календарь, закладки и форумы.
  • В системе Alfresco реализована возможность создания базы знаний на основе модуля Wiki и модуля ведения электронных дневников (Blogs). При этом нет необходимости знать wiki-разметку, создание страниц осуществляется с помощью удобного Web-интерфейса.

Возможности Alfresco

  • Хранение файлов любых форматов, в т.ч. аудио и видео;
  • Контроль версий документов и истории изменений;
  • Разграничение прав доступа к документам;
  • Поддержка иерархической структуры архива;
  • Полнотекстовый поиск по загруженным документам, включая файлы MS Word, Excel, PDF и тд.;
  • Предпросмотр документов через WEB-интерфейс, в т.ч. через защищенное соединение через Интернет;
  • Работа с документами через сетевой диск, непосредственно из программ MS Office, через интерфейс почтового клиента, через WEB-интерфейс;
  • Возможности классификации документов;
  • Возможности создания и выполнения бизнес-правил, к примеру, автоматическое перемещение истекшего договора в раздел «Архив»;
  • Возможность создания разных типов документов с различными полями в карточке документа;
  • Управление справочниками (создание, изменение, удаление записей);
  • Расширенный поиск по полям карточки документа;
  • Создание и печать отчетов на основе загруженных документов;
  • Создание и запуск бизнес-процессов работы с документами, таких как: утверждение документов (процесс согласования), управление и контроль исполнения поручений и другие произвольные процессы;
  • Уведомления об этапах выполнения процесса документооборота по электронной почте и СМС;
  • Просмотр истории выполнения бизнес-процессов, к примеру, истории согласования документа;
  • Регистрация входящей и исходящей корреспонденции;
  • Создание в системе организационной структуры компании
  • Работы с общими папками и документами как внутри компании в целом, так и внутри отделов;
  • Распределение и контроль доступа;
  • Интеграция с LDAP и MS Active Directory.

Goals for this Release

Our focus while developing Alfresco Community Edition 5.2 has been to strengthen Alfresco as a content platform by building a new set of REST APIs that are used by the Alfresco Application Development Framework.  This release builds on last month’s initial Community Edition GA release.  This release contains bug fixes and library upgrades with focus on improving stability rather than adding new features.

We believe that this release is ready for the GA label because:

  • It has all of the features we expect to add in the 5.2 series of releases.
  • We have received positive feedback on the last few releases suggesting that people are successful with them.
  • Our testing team has hit their second checkpoint of thorough testing of the 5.2.0 release of Enterprise Edition, which shares most of its code with this Community Edition release.
  • There is an upgrade path from this release to an Early Access release of Alfresco Enterprise Edition 5.2.0.

We expect this to be the penultimate 5.2 Community GA release that is focused on fixing bugs and polishing the product before we return to new development. Our goal is to continue with monthly releases.

Notes on Specific Release Components

  • Solr4 is included as the default search provider in this release. Interested administrators can download and configure Alfresco Search Services which includes Solr6.
  • Records Management: We identified some incompatibilities between Records Management and the 5.2 series of Share and Platform releases, and therefore we removed the RM module from this release.  We expect to have a compatible version of the Records Management Module available at the end of February 2017.
  • Alfresco SDK: We are working on releasing a version of the Alfresco SDK that is compatible with the 5.2 series of Share and Platform releases.

Issues Addressed

This release contains all bug fixes since the Community Edition 5.0.d release.

The issues addressed specifically in this release are available in JIRA projects for the components of this release. Please to get a complete list of issues addressed since the previous GA release (5.0.d). Note that JIRA behaves inconsistently with these queries when you are not logged in.

  • ALF: Improvements to Alfresco requested by open source collaborators. Most issues are linked to another project to get assigned to a team.
  • ACE: Improvements to Alfresco requested by product management.
  • MNT: Fixes to Alfresco requested by customers (many are private).
  • SHA: Improvements to Alfresco Share.
  • REPO: Improvements to the Alfresco ECM Repository.
  • AKU: Improvements to the Aikau UI library used by Share and other interfaces.
  • RM: Changes to Records Management.
  • SEARCH: Fixes to Search and Discover

Important fixes in this GA release:

  • MNT-16259: Some installs need to change the ‘admin’ user password after upgrading. See SA-8.
  • ACE-5661: CAS is not working in some scenarios.

Notable New Features in this Release

As a Generally Available release, the focus of this release has been on stability and not on new features.

The page dedicated to Alfresco Community Edition 5.2 lists all the features in the 5.2 line of Alfresco releases.

Platform

Slowdown of Brute Force Attacks — REPO-1489

This release contains a simple mechanism for temporarily locking user accounts when there are multiple consecutive failed attempts at authentication. During the lockout period, all authentication attempts are denied and a warning is printed to the logs. This will significantly slow down attempts to guess passwords and allow administrators to take defensive measures. The number of failed attempts that trigger a lockout and the length of the lockout are configurable.

New REST APIs

New and updated endpoints (since Community 201611) include:

  • Permissions for a node can now be retrieved via GET /nodes/{nodeId} and GET /nodes/{nodeId}/children
  • Permissions for a node can now be updated via PUT /nodes/{nodeId}
  • Option to set an expiry date when creating a shared link with POST /shared-links

These APIs are browse-able in the REST API Explorer v1.4 (GitHub — alfresco-rest-api-explorer) to navigate the details. This is included in the SDK, or can be installed by adding the WAR to your Alfresco install and configuring CORS.

See also Alfresco 5.2 REST APIs to find links to more information about the new REST APIs.

Share

No incremental updates since last month’s Alfresco Community Edition 201611 EA Release.  The notes for the previous community release are .

Search

Version store index — SEARCH-228/ SEARCH-250

A standard search usually looks at the most recent version of a document. It is now possible to tell Alfresco to index every version of a document by choosing to index the version store. This will enable the option to search all previous versions of documents. When selected, all matching versions will be returned.

Admin improvements

Improvements to the admin screens to enable complete Solr configuration.

Mobile

This Early Access Alfresco Java Client SDK contains a Java lib project to easily consume Alfresco Public REST APIs. It includes a set of APIs that allows developers to quickly build Alfresco-enabled Java & Android applications:

Localisation

This release includes: French, German, Italian, Spanish, Japanese, Dutch, Norwegian (Bokmål), Russian, Brazilian Portuguese and Simplified Chinese versions.  The section on Support Tools is still in English.

No features have been removed in this release.

Known Issues

  • The Alfresco Records Management Module is known to not be compatible with Alfresco Platform 5.2 and Alfresco Share 5.2. We expect to include a compatible Records Management Module in the next release of Alfresco Community Edition.
  • The Alfresco SDK compatible with the Alfresco 5.2 series of releases is still under development.
  • Though publicly available, the documentation is still under development. It is particularly missing information about Alfresco Search Services and Solr6.
  • The Alfresco Support Tools section of the Repository Administration Console is not yet localized.
  • ACE-5661: CAS is not working in some scenarios. This is expected to be fixed in the next release. 

Goals for this Release

Our focus while developing Alfresco Community Edition 5.2 has been to strengthen Alfresco as a content platform by building a new set of REST APIs that are used by the Alfresco Application Development Framework. We are also rolling out some nice improvements to Alfresco Share, and laying the foundation for future improvements by allowing Solr 6 to be used for search indexes. This release also contains many bug fixes and library upgrades.

We believe that this release is ready for the GA label because:

  • It has all of the features we expect to add in the 5.2 series of releases, with only a few relatively small new features added since the previous release.
  • We have received positive feedback on the last few EA releases suggesting that people are successful with them.
  • Our testing team has hit their first checkpoint of thorough testing of the 5.2.0 release of Enterprise Edition, which shares most of its code with this Community Edition release.
  • There is an upgrade path from this release to an Early Access release of Alfresco Enterprise Edition 5.2.0.

We expect this to be the first of a few GA releases that are focused on fixing bugs and polishing the product. Our goal is to continue with monthly releases.

Notes on Specific Release Components

  • Solr4 is included as the default search provider in this release. Interested administrators can download and configure Alfresco Search Services which includes Solr6. There is currently no difference between the Alfresco Search Services included in Alfresco Community Edition and Alfresco Enterprise Edition. This releases contains alfresco-search-services-1.0-EA, which is the same artifact as was included in the Alfresco Enterprise Edition 5.2.0 EA program. It contains a handful of bug fixes and features since the alfresco-search-services-1.0.a which was included in the previous release of Alfresco Community Edition.
  • Records Management: We identified some incompatibilities between Records Management and the 5.2 series of Share and Platform releases, and therefore we removed the RM module from this release. We are working to include the Records Management module in our next release of Alfresco Community Edition.
  • Alfresco SDK: We are working on releasing a version of the Alfresco SDK that is compatible with the 5.2 series of Share and Platform releases.

Issues Addressed

This release contains all bug fixes since the Community Edition 5.0.d release.

The issues addressed specifically in this release are available in JIRA projects for the components of this release. Please to get a complete list of issues addressed since the previous GA release (5.0.d). Note that JIRA behaves inconsistently with these queries when you are not logged in.

  • ALF: Improvements to Alfresco requested by open source collaborators. Most issues are linked to another project to get assigned to a team.
  • ACE: Improvements to Alfresco requested by product management.
  • MNT: Fixes to Alfresco requested by customers (many are private).
  • SHA: Improvements to Alfresco Share.
  • REPO: Improvements to the Alfresco ECM Repository.
  • AKU: Improvements to the Aikau UI library used by Share and other interfaces.
  • RM: Changes to Records Management.
  • SEARCH: Fixes to Search and Discovery

Important fixes since the last GA release:

  • MNT-16259: Some installs need to change the ‘admin’ user password after upgrading. See SA-8.
  • MNT-15795: CAS authentication via the external auth subsystem no longer works. This issue contains a patch.
  • ALF-21607: Problems with SSO via Kerberos. This issue contains a patch to a number of related issues.
  • MNT-16221 Infinite 302 HTTP redirect loop when using External Authentication with uppercase usernames/username case sensitivity
  • MNT-15376 NTLM authentication sometimes fails with IE10+
  • SHA-1717 The «Hide Getting Started» panel settings icon was missing.
  • ALF-21398: Advanced Search Yields No Results When Using Hyphens in Custom Property Values (Thank you to Cory Solovewicz for helping us to track it down.)
  • MNT-16638: Folder access in ‘private’ sites using site path url fails versus repository url path (see also SHA-1682)
  • MNT-16517 cmwner Aspect is missing from the folder details page
  • MNT-15838 Filmstrip view in share crashes the browser when a folder contains many large images
  • MNT-16532 DojoDependencyHandler — cached generated resources use significant amount of heap memory
  • MNT-15708 Direct Share Admins to the Repo Admin Tools

Issues Addressed

This release contains all bug fixes since the Alfresco Community Edition 5.0.d release.

The issues addressed specifically in this release are available in JIRA projects for the components of this release. Please to get a complete list of issues addressed since the previous GA release (5.0.d). Note that JIRA behaves inconsistently with these queries when you are not logged in.

  • ALF: Improvements to Alfresco requested by open source collaborators. Most issues are linked to another project to get assigned to a team.
  • ACE: Improvements to Alfresco requested by product management.
  • MNT: Fixes to Alfresco requested by customers (many are private).
  • SHA: Improvements to Alfresco Share.
  • REPO: Improvements to the Alfresco Content Repository.
  • AKU: Improvements to the Aikau UI library used by Share and other interfaces.
  • RM: Changes to Records Management.
  • SEARCH: Fixes to Search and Discover

Important fixes in this GA release:

  • MNT-17113: Preview not updated after new versions, AOS and manual upload. Issue contains a patch.
  • ACE-5753: CMIS browser binding root URL is broken.
  • ACE-5748: Hibernate errors: Unusable connection proxy was constructed. (Could not be reproduced)
  • REPO-1818: alfresco-platform-distribution POM for 5.2.d / 201612 GA includes incorrect version for Share artifacts.

Running

Create a folder where Docker Compose template files are going to be produced and run the generator.

Several options are provided in order to build the configuration.

You can use Alfresco 6.1 or 6.2

Alfresco platform could work with less than 8 GB RAM, but it’s recommended to provide at least 8 GB in your Docker server. This generator will limit the amount of memory for every service in order to match your resources.

This option enables HTTPs for every service. Default SSL certificates (public and private) are provided in folder. These certificates are not recommended for prod environments, so it’s required to replace these files with your own certificates.

If you are deploying on a server different than , include in this option the name of your server. For instance:

HTTP port to be used by every service. If you are running on a Linux computer, you’ll need to specify a port greater than 1024 when not starting as user.

Enable configuration for FTP, using by default port 2121.

Alfresco uses PostgreSQL by default, but alternatively can be used as database.

By default, many organisations are storing document in different languages or the users are accessing the platform with browser configured in different languages. If this is your case, enable this configuration.

This service provides an internal OpenLDAP server (for authentication). If you want to use your own LDAP or AD server, you can configure it manually after the generation of the Docker Compose template.

A small catalog of trusted addons is provided by default, but you can install any other using the deployment folders.

The wrapper script for the docker-compose file allows nice features as a wait for alfresco to finish the boot and much more. Use «./start.sh -h» for more information.

Known Issues

  • The Alfresco Records Management Module is known to not be compatible with Alfresco Platform 5.2 and Alfresco Share 5.2. We expect to have a compatible version of the Records Management Module available at the end of February 2017.
  • The Alfresco SDK compatible with the Alfresco 5.2 series of releases is still under development.
  • Though publicly available, the documentation is still under development. It is particularly missing information about Alfresco Search Services and Solr6.
  • The Alfresco Support Tools section of the Repository Administration Console is not yet localized.
  • MNT-17113: Preview not updated after new versions, AOS and manual upload. Issue contains a patch.
  • ACE-5753: CMIS browser binding root URL is broken
  • ACE-5748: Hibernate errors: Unusable connection proxy was constructed

Installation

The latest GA release of Alfresco Community Edition is available from the Alfresco Community Edition product page.

Download this release from Alfresco Community Edition file list 201701‌.

For download and installation instructions, refer to the Download and Install Alfresco page.

The Alfresco supplied installers will install all you need to run Alfresco on your machine; which includes JDK, Tomcat, SOLR, and LibreOffice. It also includes interfaces and extensions such as Share, the Google Docs integration, and the AOS module.

Notes:

  • JVM memory defaults to half system memory, minimum of 2GB.
  • Latest OS patches are always recommended.

Installation

This program has following dependencies:

  • Node.js
  • Yeoman

You can download and install from official web page:

Or you can use any of the package managers provided by the product:

$ npm install -g yo

And finally, you can install this generator:

$ npm install --global generator-alfresco-docker-installer

Deployment is provided for Docker Compose, so following dependencies must be satisfied by the server used to run the generated configuration:

  • Docker
  • Docker Compose

You can install Docker Desktop for Windows or Mac and Docker Server for Linux.

You need also to add Docker Compose program to your installation.

Оцените статью
Рейтинг автора
5
Материал подготовил
Андрей Измаилов
Наш эксперт
Написано статей
116
Добавить комментарий