Exporting an AEM Site | Community
Skip to main content
A
aradhyakasat
Level 2
August 11, 2020
Solved

Exporting an AEM Site

  • August 11, 2020
  • 4 replies
  • 3243 views

So I have an AEM website with the entire folder structure including the core package with java files. The way I'm currently exporting it to be able to run on any other machine is that I download the "samplewebsite.all.SNAPSHOT " through CRXDE and upload the same on the other machine through CRXDE. For the core package, I do a maven build and then upload the "samplewebsite.core.SNAPSHOT" jar through system/console/bundles. I'm curious to know if this process can be reduced down to just one package upload which contains the core package files as well? 

@briankasingli 

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 BrianKasingli

@aradhyakasat 

When you have an AEM content package, with a bundle (JAR FILE) within the /apps/my-site/install folder, the when the AEM content package is installed into AEM, the bundle will be atomically installed by the OSGI installer, documentation: https://sling.apache.org/documentation/bundles/jcr-installer-provider.html; taking a look at the ui.apps (AEM content package) artefact produced by the aem-project-archetype, you can see the core bundle is embedded in the /apps/my-site/install folder. 

Reducing down to one package for release is simple, you can follow how the AEM-project-archetype implements the "all" maven module, https://github.com/adobe/aem-project-archetype/tree/master/src/main/archetype/all 

 

4 replies

L
Adobe Employee
leoberliantAdobe Employee
Adobe Employee
August 11, 2020

As per the maven archetype 23, the "all" package includes both content and core packages. For your use-case, it should be enough to deploy only "samplewebsite.all.SNAPSHOT" package.

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    August 11, 2020

    Please check apps package, ui.apps package include the jar file inside /apps/proj/install. If jar is present then check filter.xml

    You don't need to install jar separately. if your apps package is getting installed.

    Arun Patidar
      A
      aradhyakasatAuthor
      Level 2
      August 12, 2020

      @arunpatidarI navigated to ui.apps package and could see the jar present there inside apps/proj/install. The issue was that it contained an older version of the core jar for some reason. I deleted it and did a clean maven install which got the latest core jar in there. Thanks for your help. 🙂

      BrianKasingli
      Community Advisor and Adobe Champion
      BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
      Community Advisor and Adobe Champion
      August 11, 2020

      @aradhyakasat 

      When you have an AEM content package, with a bundle (JAR FILE) within the /apps/my-site/install folder, the when the AEM content package is installed into AEM, the bundle will be atomically installed by the OSGI installer, documentation: https://sling.apache.org/documentation/bundles/jcr-installer-provider.html; taking a look at the ui.apps (AEM content package) artefact produced by the aem-project-archetype, you can see the core bundle is embedded in the /apps/my-site/install folder. 

      Reducing down to one package for release is simple, you can follow how the AEM-project-archetype implements the "all" maven module, https://github.com/adobe/aem-project-archetype/tree/master/src/main/archetype/all 

       

        A
        aradhyakasatAuthor
        Level 2
        August 12, 2020
        @briankasingli I navigated to ui.apps package and could see the jar present there inside apps/proj/install. The issue was that it contained an older version of the core jar which was then flowing as is into the all.snapshot. I deleted it and did a clean maven install which got the latest core jar in there. Thanks for your help. 🙂
        R
        rahulmengji
        Level 3
        August 12, 2020

        if you are working with the latest archetype, it should happen with "all" package automatically. If you still have issues, see if you have mistakenly install a versioned package/jar file that is causing problems.

          A
          aradhyakasatAuthor
          Level 2
          August 12, 2020
          Yes, that was the issue. The version of core jar in ui.apps was an older version which is why I couldnt see my servlets in action. Thanks for your help 🙂
          Terms & ConditionsAccessibility statement

          Loading footer...