AEM cloud | Run mode folders deployment not working | Community
Skip to main content
P
pradeepdubey
June 30, 2022
Solved

AEM cloud | Run mode folders deployment not working

  • June 30, 2022
  • 5 replies
  • 2362 views

Hi Folks,

 

I am keeping the run mode folders in ui.config in cloud maven project.

Everything is working fine in local.

When we deploy the application using adobe cloud manager deployment pipeline, I don't see osgiconfig folder and child run mode folders in content tree.

In filter.xml all run mode folders added properly. 

 

Some adobe forums is suggesting to keep rumode/osgiconfig folders in ui.apps that also I tried. It is not even  compiling the code if we keep the run  mode folders in ui.apps.

 

I would highly appreciate if anyone has come across similar issue and has fixed the same.

 

Thanks,

Pradeep

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 arunpatidar

Hi,

You will not see the config node from in crx or content tree on cloud.

You should be checking config from developer console.

5 replies

T
Adobe Employee
Tushar_GuptaAdobe Employee
Adobe Employee
June 30, 2022

I think you need to look at the Cloud Service project structure - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure.html?lang=en 

 

Also, for best practice you can refer the arch type where we have sample code structure and you should refer that: 

https://github.com/adobe/aem-project-archetype 

    manpreetk908
    manpreetk908
    Level 4
    June 30, 2022

    I hope you are just not focusing on checking the run mode node in the content tree in the cloud env and you have confirmed that your run modes are not working as expected?

     

    Regards,

    Manpreet

      Mohit_KBansal
      Adobe Employee
      Mohit_KBansalAdobe Employee
      Adobe Employee
      June 30, 2022

      Make sure you are following correct runmode structure as per [1]. Please be informed that runmodes on cloud are supported in json format [2].

       

      [1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploying/overview.html?lang=en#runmodes

      [2] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploying/configuring-osgi.html?lang=en 

        P
        pradeepdubeyAuthor
        June 30, 2022

        Yes all configurations in the format of cfg.json

        Still these are not working. Local everything looking good. No code change in local  and what we  have in cloud pipeline. 

        I think cloud manager has different process and treats run mode differently. If anyone can  share some  insights will help.

          SantoshSai
          Community Advisor
          SantoshSaiCommunity Advisor
          Community Advisor
          June 30, 2022

          Hi @pradeepdubey , 
          If those are custom runmodes - 

          "AEM 6.x supports custom runmodes, however AEM as a Cloud Service does not. AEM as a Cloud Service support an exact set of runmodes. Any variation in OSGi configurations between AEM as a Cloud Service environments must be handled using OSGi configuration environment variables."

          Please visit these articles may help:

          Hope that helps!

          Regards,
          Santosh

           

          Santosh Sai
            arunpatidar
            Community Advisor
            arunpatidarCommunity AdvisorAccepted solution
            Community Advisor
            July 1, 2022

            Hi,

            You will not see the config node from in crx or content tree on cloud.

            You should be checking config from developer console.

            Arun Patidar
              P
              pradeepdubeyAuthor
              July 1, 2022

              Hi Arun,

               

              Very weird but it is true. 

              Yes I can see the configuration in developer console. But I am no able to see the run modes in cloud instance. Usually we can see in status --> sling settings in OSGI console in regular AEM instance.

               

              Where should I check the run mode in AEM cloud? Status json is not showing the run mode.

               

              Thanks,

              Pradeep

               

                arunpatidar
                Community Advisor
                arunpatidarCommunity Advisor
                Community Advisor
                July 1, 2022

                Run modes that are defined typically include the service (author and publish) and the environment (dev, stage, prod). This can be checked from Cloud Manager and based on instance type dev orr stage or prod.

                Pattern
                <service>.<environment_type>

                Fr eg: author.dev or publish.prod

                The supported runmode configurations in AEM as a cloud service are:

                • config ( The default, applies to all AEM Services )
                • config.author ( Applies to all AEM Author service )
                • config.author.dev ( Applies to AEM Dev Author service )
                • config.author.stage ( Applies to AEM Staging Author service )
                • config.author.prod ( Applies to AEM Production Author service )
                • config.publish ( Applies to AEM Publish service )
                • config.publish.dev ( Applies to AEM Dev Publish service )
                • config.publish.stage ( Applies to AEM Staging Publish service )
                • config.publish.prod ( Applies to AEM Production Publish service )
                • config.dev (*Applies to AEM Dev services)
                • config.stage (*Applies to AEM Staging services)
                • config.prod (*Applies to AEM Production services)


                ** OSGI configuration that has the most matching runmodes is used.

                 

                Please check this as well https://medium.com/adobetech/custom-runmodes-on-aem-as-a-cloud-service-79b757f51a6b 

                Arun Patidar
                  Terms & ConditionsAccessibility statement

                  Loading footer...