Skip to main content
Mario248
Mario248
Level 7
September 8, 2023
Solved

How to Include 3rd party aem package for AEM cloud

I have an installable AEM package(external-app-1.0.7.zip) and I am able to  install this in my local AEM by uploading it in the package manager. In cloud I can not install as it contains /app/mypackage since it is an un-mutable AEM cloud instance and could not install the package through package manager. Hence I am planning to keep the external-app-1.0.7.zip in the resource folder like ...all/src/main/resources/external-app-1.0.7.zip as part of the codebase itself. I am planning to use the <embedded> feature to embed this package. 

 

<embedded>
<groupId>com.adobe.cq</groupId>
<artifactId>lorum</artifactId>
<type>zip</type>
<target>/apps/mypro/application/install</target>
</embedded>
 
But I don't have artifact and groupid for this package. Is there any way I can install external-app-1.0.7.zip as part of maven deployment 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
aanchal-sikka
aanchal-sikkaAccepted solution
Community Advisor
September 8, 2023

Hello @mario248 

 

Glad that it had helped you a bit.

 

Have you tried local repo as well?

 

Once you have the details, please refer to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-3rd-party-aem-pa...

It explains how to use Local filesystem repo to deploy packages that are not public

 
 
Aanchal Sikka
View in thread

10 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
September 8, 2023

Hello @mario248 

 

We can get the artifactID and groupID by unzipping the package.

  • Unzip the package
  • Go to \META-INF\maven folder
    • Follow the folder structure underneath it until you reach pom.xml
      • First folder is groupID
      • Second is artifactID
    • Or just reach pom.xml and all information is in there

 

Example: acs-aem-commons-all-6.0.14\META-INF\maven\com.adobe.acs\acs-aem-commons-all

 

 

 

You should be able to use the recommended <embedded> way

 

Once you have the details, please refer to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-3rd-party-aem-package-for-cloud-manager-build/td-p/445201

It explains how to use Local filesystem repo to deploy packages that are not public

Translate
Aanchal Sikka
    Mario248
    Mario248Author
    Level 7
    September 8, 2023

    Thank you for your input. I got the artifactID and groupID by using your steps. I have prepared below embed and deployed the code into my local, the build is success but I dont see package in /apps/myproject/application/install in crxde.

     

     

     

     

     

    <embedded> <groupId>com.green.grass</groupId> <artifactId>com.green.grass.digital</artifactId> <type>zip</type> <target>/apps/myproject/application/install</target> </embedded>

     

     

     

     
    I have kept the zip in resource folder( ...all/src/main/resources/external-app-1.0.7.zip ). Can you tell me where do I specify location of the zip file ?
    Translate
      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity AdvisorAccepted solution
      Community Advisor
      September 8, 2023

      Hello @mario248 

       

      Glad that it had helped you a bit.

       

      Have you tried local repo as well?

       

      Once you have the details, please refer to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-3rd-party-aem-pa...

      It explains how to use Local filesystem repo to deploy packages that are not public

       
       
      Translate
      Aanchal Sikka
        Mahedi_Sabuj
        Community Advisor
        Mahedi_SabujCommunity Advisor
        Community Advisor
        September 8, 2023

        Hi @mario248, 

        You can refer to the LinkedIn Article, which provides detailed step-by-step instructions.

        https://www.linkedin.com/pulse/how-add-third-party-bundle-you-aem-package-veena-vikraman/ 

        Translate
        Mahedi Sabuj
          EstebanBustamante
          Adobe Champion and Community Advisor
          EstebanBustamanteAdobe Champion and Community Advisor
          Adobe Champion and Community Advisor
          September 8, 2023

          Please take a look at this article: https://www.albinsblog.com/2015/06/deploying-bundlespackages-to-different-env-maven-adobecq5-adobeaem.html where It shows how to use the "content-package-maven-plugin" plugin. By specifying the packageFile property I think you should be able to achieve what you need. 

          Reference:
          https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developer-tools/maven-plugin.html?lang=en#install 

          Translate
          Esteban Bustamante
            Sanjay_Bangar
            Community Advisor
            Sanjay_BangarCommunity Advisor
            Community Advisor
            September 9, 2023

            Hi @mario248 ,

            Please follow below steps

            steps to include a third-party package in AEM as a Cloud Service:

            1. Check the Adobe Experience Manager as a Cloud Service - Supported Integrations documentation to ensure that the third-party package you want to include is supported in the cloud environment. Adobe maintains a list of supported integrations and packages that are tested and verified to work with AEM as a Cloud Service.

            2. Create a Maven project for your custom code and dependencies. Use Maven as the build tool to manage your project's dependencies and package them into an AEM package.

            3. Add the third-party package as a dependency in your Maven project's pom.xml file. Specify the appropriate version of the package that is compatible with AEM as a Cloud Service.

            4. Build your Maven project to generate an AEM package that includes your custom code and the third-party package as dependencies.

            5. Deploy the AEM package to your AEM as a Cloud Service instance using the Cloud Manager or the Package Manager in AEM. Follow the recommended deployment practices provided by Adobe for AEM as a Cloud Service.

            6. Test your custom code and the integration with the third-party package in the AEM as a Cloud Service environment.

            Translate
              kautuk_sahni
              Adobe Employee
              kautuk_sahniAdobe Employee
              Adobe Employee
              September 12, 2023

              @mario248 Do you find the suggestions from users useful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. 

               

              Translate
              Kautuk Sahni
              aanchal-sikka
              Community Advisor
              aanchal-sikkaCommunity Advisor
              Community Advisor
              September 27, 2023

              Sharing a blog which explains how to use Third-party bundles when:

              • Hosted in restricted Maven repo 
              • Local repo (i.e. when maven repositories cannot be used)

               

              https://techrevel.blog/2023/09/27/managing-third-party-dependencies-in-aem/

               

              It also explains the configurations needed to deploy via cloud manager

              Translate
              Aanchal Sikka
              Terms & ConditionsAccessibility statement

              Loading footer...