Handling and Deployment of Custom OAK index | Readiness for AEM as Cloud Service | Community
Skip to main content
N
NehaMa
Level 4
March 10, 2021
Solved

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

  • March 10, 2021
  • 2 replies
  • 5056 views

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.
    Best answer by Vijayalakshmi_S

    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

     

    2 replies

    Vijayalakshmi_S
    Vijayalakshmi_SAccepted solution
    Level 10
    March 10, 2021

    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

     

      R
      RahulMohan
      Level 3
      February 7, 2022

      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

        R
        RahulMohan
        Level 3
        February 8, 2022

        Can you check on the below and let know your inputs. I don't have access to cloud service to reproduce this myself. 

        • Amend on top of the index definition from Cloud Service instance
          • package the OOTB definition from Cloud service instance
          • Include the desired customization -> build/deploy in local SDK instance (Check how tika is getting persisted in local SDK)
          • Observe build logs during ui.apps module build.
        • ui.apps has the respective content under jcr_root folder (_oak_index till config.xml)
        • Contents of config.xml is the latest (tika/config.xml)

        Hi Vijayalakshmi,

         

        Performed the same steps as you listed and cross verified.

        • Amend on top of the index definition from Cloud Service instance
          • package the OOTB definition from Cloud service instance --> DONE
          • Include the desired customization -> build/deploy in local SDK instance (Check how tika is getting persisted in local SDK) --> Yes, the new index node is getting created under "oak:index" node in my local CRX DE.
          • Observe build logs during ui.apps module build. --> No specific errors
        • ui.apps has the respective content under jcr_root folder (_oak_index till config.xml) --> Available as part of the source code.
        • Contents of config.xml is the latest (tika/config.xml) --> Yes, it's the same as that of the latest OOB index definition damAssetLucene-7.

        Thanks,
        Rahul

          cc96470700
          cc96470700
          Level 2
          March 11, 2022

          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!

            A
            abera
            Level 2
            April 5, 2022

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

              cc96470700
              cc96470700
              Level 2
              April 6, 2022

              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>
                Terms & ConditionsAccessibility statement

                Loading footer...