Coding with the Hub #4 - Deploying Alfresco Repository incrementally

cancel
Showing results for 
Search instead for 
Did you mean: 

Coding with the Hub #4 - Deploying Alfresco Repository incrementally

angelborroy
Alfresco Employee
1 1 2,287

ACS is deployed by default including many different services. This blog post describes an Alfresco Repository deployment starting from the minimal configuration and adding services one by one to understand the features provided by each of them. This will guide you on the desing of your own deployment, depending on the requirements of your use case.

Source code is available in https://github.com/aborroy/alfresco-incremental-deployment

Minimal configuration

Alfresco repository can be started only with "alfresco" and "postgres" components. This configuration allows the Repository to be accessed by using the REST API with the Core API. However, Search API is not available at all.

services: alfresco:
  image: alfresco/alfresco-content-repository-community:7.2.0
postgres:
  image: postgres:13.3

Reference Docker Compose: docker-compose.yml

Configuration with metadata search

When adding the "search" service, Search API is available but it will provide limited features when searching for content.

services: alfresco:
  image: alfresco/alfresco-content-repository-community:7.2.0
postgres:
  image: postgres:13.3
solr6:
  image: alfresco/alfresco-search-services:2.0.3

Reference Docker Compose: docker-compose.yml

Configuration with metadata and content search

To enable content searching, transform service is required. This service is the one extracting text from documents, so that content can be indexed by SOLR.

services: alfresco:
  image: alfresco/alfresco-content-repository-community:7.2.0
postgres:
  image: postgres:13.3
solr6:
  image: alfresco/alfresco-search-services:2.0.3
transform-core-aio:
  image: alfresco/alfresco-transform-core-aio:2.5.7

Reference Docker Compose: docker-compose.yml

Configuration to be used for Out Of Process SDK

When consuming events from ActiveMQ, this component needs to be added to the configuration. The component, when using Community Edition, is not required for any other feature provided by the repository. Enable this component only if you're planning to use this integration pattern.

services: alfresco:
  image: alfresco/alfresco-content-repository-community:7.2.0
postgres:
  image: postgres:13.3
solr6:
  image: alfresco/alfresco-search-services:2.0.3
transform-core-aio:
  image: alfresco/alfresco-transform-core-aio:2.5.7
activemq:
  image: alfresco/alfresco-activemq:5.16.4-jre11-centos7

Reference Docker Compose: docker-compose.yml

 

See that working live in this recording!

About the Author
Angel Borroy is Hyland Developer Evangelist. Over the last 15 years, he has been working as a software architect on Java, BPM, document management and electronic signatures. He has been working with Alfresco during the last years to customize several implementations in large organizations and to provide add-ons to the Community based on Record Management and Electronic Signature. He writes (sometimes) on his personal blog http://angelborroy.wordpress.com. He is (proud) member of the Order of the Bee.
1 Comment