Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

osgiconfig and install folders are not visible in aem cloud

Avatar

Level 8

I have osgiconfig folder inside /apps/kb and I have install folder inside /apps/kb-packages. I could see these folders and files(config, jar, zip) files in local as below (local AEM )

Mario248_0-1695798564577.png

 

But when I deploy the code to AEM cloud, I dont see "osgiconfig" folder and install folder is not appearing in aem cloud as like below 

AEM cloud instance

Mario248_1-1695799040720.png

 

Also I have installed wcm core components in the cloud and I don't see any entry for /apps/core/wcm/components but I have this hierarchy present in my local aem. Can anyone explain what are the folders that will not appear in aem cloud ? is there any to check ? It is really confusing whether wcm core component is present or not and osgiconfig is present or not.

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi, 

 

The important thing here is that AEM SDK is not a mirror to the AEM Cloud instance, although there are some "changes" to make it more likely the Cloud, it is not exactly the same.

 

Now, the core components in AEM Cloud are located under "/libs" because they are available ootb[1]. In regards to the packaging process, I think this documentation can add some light to such behavior: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploy... If you are trying to check if one of your OSGI config "was taken" you should use the "Developer Console" to check which configuration is being used in the instance instead. 

 

Hope this helps.

 

[1]. https://github.com/adobe/aem-core-wcm-components

EstebanBustamante_0-1695818864385.png

 



Esteban Bustamante

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi, 

 

The important thing here is that AEM SDK is not a mirror to the AEM Cloud instance, although there are some "changes" to make it more likely the Cloud, it is not exactly the same.

 

Now, the core components in AEM Cloud are located under "/libs" because they are available ootb[1]. In regards to the packaging process, I think this documentation can add some light to such behavior: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploy... If you are trying to check if one of your OSGI config "was taken" you should use the "Developer Console" to check which configuration is being used in the instance instead. 

 

Hope this helps.

 

[1]. https://github.com/adobe/aem-core-wcm-components

EstebanBustamante_0-1695818864385.png

 



Esteban Bustamante

Avatar

Community Advisor

This is expected behaviour , you will not see the osgiconfig folder in AEMaaCS crxde.

you can see the osgi config from developer console.



Arun Patidar