Using Search and Indexing in AEM as a Cloud Service | AEM Community Blog Seeding

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,204 likes

Total Posts

6,410 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,204 likes

Total Posts

6,410 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

24-02-2021

BlogImage.jpg

Using Search and Indexing in AEM as a Cloud Service by James Talbot

Abstract

AEM supports running queries against the JCR repository, which is very similar to running queries against a relational database. Full text queries are also supported. Customers can write their own queries and define their own indexes, and many AEM customers do this.

Changing the index definitions is needed to speed up queries. With blue-green deployments, the challenge is that multiple application versions can exist at the same time, but each version might require a different index configuration.

With AEM as a Cloud Service, instead of configuring and maintaining these indices on single AEM instances, the index configuration has to be specified before an actual deployment. Let’s review some of the changes in AEM as a Cloud Service:

Indexing Changes in AEM as a Cloud Service
1. Users will not have access to the Index Manager (http://localhost:4502/libs/granite/operations/content/diagnosistools/indexManager.html) of a single AEM Instance anymore to debug, configure or maintain indexing. It is only used for local development and for on-prem deployments.

Read Full Blog

Using Search and Indexing in AEM as a Cloud Service

Q&A

Please use this thread to ask the related questions.