Replicate an existing Content Services 7.1 (and above) deployment - Replicate an existing Content Services 7.1 (and above) deployment - Alfresco - Alfresco Search Enterprise - Alfresco/Alfresco-Search-Enterprise/3.2/Alfresco-Search-Enterprise/Alfresco-Search-Enterprise/Upgrade-to-Search-Enterprise/Replicate-an-existing-Content-Services-7.1-and-above-deployment - 3.2

Alfresco Search Enterprise

Platform
Alfresco
Product
Alfresco Search Enterprise
Release
3.2
ft:lastPublication
2026-05-06T19:34:57.842000
ft:locale
en-US
ArchiveStatus
Archived

Your current Content Services stack can continue to run while you are indexing the repository to Elasticsearch. This means you can continue to use the 'old' service until the process completes. It's recommended you create a read replica of the database so the indexing process won't affect service performance.

replicated-environment

  1. Create a read-only Replica for your database.

  2. Configure Alfresco Repository Search Subsystem to use elasticsearch and switch database configuration to the read-only replica database.

  3. Install the Elasticsearch server.

  4. Install Elasticsearch connector.

  5. Once everything is up and running, use the Elasticsearch connector Re-indexing application to populate the Elasticsearch index. This operation may take a while, depending on the number of documents in your Repository and on the indexing options selected (metadata, content and path).

  6. Test the replicated environment is working as expected in terms of searching and indexing operations.

  7. Switch the existing production environment to the replicated environment by using the original database and removing the previous Search Services components based on SOLR.

upgraded-environment

Note

You may need to use the Elasticsearch Re-indexing application to update to the latest changes. After that, new and updated documents will be uploaded to the Elasticsearch index by the Elasticsearch connector service using ActiveMQ messages.