Handling and Deployment of Custom OAK index | Readiness for AEM as Cloud Service | Community
Skip to main content
NehaMa
Level 4
Mar 10, 2021 11:38 AM UTC
Solved

Handling and Deployment of Custom OAK index | Readiness for AEM as Cloud Service

Hi Team,

We are currently using custom oak indexes and using Ensure Oak Index to have mapping and deployment from /apps/site/oak-index mapped to oak:index.

 

While checking readiness for AEM as cloud service, its mentioned that Ensure OAK index is incompatible with AEM as cloud service. https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-oak-index/index.html

 

What is the recommended way to manage and deploy custom oak:indexes in this scenario. let us know your thoughts.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Vijayalakshmi_S
    Vijayalakshmi_SAccepted solution
    Level 10
    Mar 10, 2021 2:27 PM UTC

    Hi @nehama,

    Custom oak index in AEM as a cloud service has to be with specific naming convention and it is to be part of ui.apps module.

    Complete details of index management is available in https://experienceleague.adobe.com/docs/experience-manager-cloud-service/operations/indexing.html?lang=en

     

    View reply

    12 replies

    cc96470700
    cc96470700
    Level 2
    Mar 11, 2022 8:09 PM UTC

    Was there a solution to the ticket you raised? I am experiencing the same issue and the documentation provided in the accepted solution isn't helpful.

     

    Thanks!

    Translate
      abera
      Level 2
      Apr 5, 2022 8:08 PM UTC

      Is there a solution for this ? I am also having the same issue. 

      Translate
        cc96470700
        cc96470700
        Level 2
        Apr 6, 2022 3:41 PM UTC

        Yes, we were able to solve this issue by updating the tika section to this: 

        <tika jcr:primaryType="nt:unstructured">
            <config.xml jcr:primaryType="nt:file" >
                <jcr:content jcr:primaryType="nt:unstructured" />
            </config.xml>
        </tika>
        Translate
          Vijayalakshmi_S
          Vijayalakshmi_SAccepted solution
          Level 10
          Mar 10, 2021 2:27 PM UTC

          Hi @nehama,

          Custom oak index in AEM as a cloud service has to be with specific naming convention and it is to be part of ui.apps module.

          Complete details of index management is available in https://experienceleague.adobe.com/docs/experience-manager-cloud-service/operations/indexing.html?lang=en

           

          Translate
            RahulMohan
            Level 3
            Feb 7, 2022 11:35 AM UTC

            Hi Vijayalakshmi,

            We are using AEM as cloud. While we make the custom index as part of our code and try to deploy, the deployment fails in the code scanning, saying 'The index /oak:index/damAssetLucene-7-custom-1 is a customization of the out of the box index /oak:index/damAssetLucene which requires a config.xml file under the child node named tika'. But we already have the tika folder as part of our source code and the config.xml inside it. Do you know how to resolve this? Any suggestion would be greatly appreciated.

            Thanks,
            Rahul

            Translate
              Vijayalakshmi_S
              Vijayalakshmi_S
              Level 10
              Feb 7, 2022 3:09 PM UTC

              @rahulmohan 

              Can you confirm if tika node is saved/available as nt:unstructured node (as opposed to a folder)

              You can cross check with OOTB damAssetLucene-7 as available in cloud service instance. (and use the same node type)

              Translate
                Terms & ConditionsAccessibility statement

                Loading footer...