Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

What's the best way to install new Indexes into my AEM Project?

Avatar

Level 6

We have a multi-tenant website, and in particular, we are working on 1 project specifically. This project was created using the AEM Maven Archetype. This project was pretty much worked on for an entire year. Now we are focusing on searchability. We have a couple of Apache Lucene indexing rules, but where should we store the configuration to be installed into the AEM environment per code deployment?

ui.apps

ui.core 

ui.content

ui.config?

We think it should be ui.config, but what should the node structure look like?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi,

 

Yes, you are correct that the configuration should be stored in the ui.config module.

In terms of the node structure, you can create a new node under /apps/<your-project-name>/install with the name of the package you want to create, for example, "search-indexes". Then, you can add a sub-node named "filter.xml" which contains the indexing rules in the format defined by Apache Lucene. You can also add any other necessary configuration files or folders under the package node.

 

Here's an example of the node structure:

/apps/<your-project-name>/install/search-indexes/ /apps/<your-project-name>/install/search-indexes/filter.xml

 

Once you have the configuration stored in the ui.config module, you can package it into a content package and deploy it to your AEM environment as part of your code deployment process.

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

Hi,

 

Yes, you are correct that the configuration should be stored in the ui.config module.

In terms of the node structure, you can create a new node under /apps/<your-project-name>/install with the name of the package you want to create, for example, "search-indexes". Then, you can add a sub-node named "filter.xml" which contains the indexing rules in the format defined by Apache Lucene. You can also add any other necessary configuration files or folders under the package node.

 

Here's an example of the node structure:

/apps/<your-project-name>/install/search-indexes/ /apps/<your-project-name>/install/search-indexes/filter.xml

 

Once you have the configuration stored in the ui.config module, you can package it into a content package and deploy it to your AEM environment as part of your code deployment process.

Avatar

Community Advisor

ui.apps will be best for custom indexes.