Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

How can I access AEM as Cloud service system console for both author and publish instance

Avatar

Level 1
 
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Ashish_Mittal ,

 

We can't access system console directly in AEMaaCS. If it's for any OSGI configuration it has to be deployed via code.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/conf...

 

If we need to debug anything like to check the status of bundles, configuration etc we can make use of developer console.

 

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-a...

 

 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @Ashish_Mittal ,

 

We can't access system console directly in AEMaaCS. If it's for any OSGI configuration it has to be deployed via code.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/conf...

 

If we need to debug anything like to check the status of bundles, configuration etc we can make use of developer console.

 

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-a...

 

 

Avatar

Community Advisor

Hi @Ashish_Mittal 

 

AEM as a Cloud Service provides a Developer Console for each environment that exposes various details of the running AEM service that are helpful in debugging.

Each AEM as a Cloud Service environment has it’s own Developer Console.

 

To access and use the Developer Console the following permissions must be given to the developer’s Adobe ID via Adobe’s Admin Console.

 

  1. Ensure the Adobe Org that has effected Cloud Manger and AEM as a Cloud Service products is active in the Adobe Org switcher.
  2. The developer must be a member of the Cloud Manager Product’s Developer - Cloud Service Product Profile.
    If this membership does not exist, the developer will not be able to log in to Developer Console.
  3. The developer must be a member of the AEM Users or AEM Administrators Product Profile on AEM Author and/or Publish.
    If this membership does not exist, the status dumps will timeout with a 401 Unauthorized error.

 

Status provides options for outputting specific AEM runtime state in text or JSON output. The Developer Console provides similar information as the AEM SDK’s local quickstart’s OSGi Web console, with the marked difference that Developer Console is read-only.

 

asutosh_jena_2-1629518210429.png

Detailed info here:

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/conf...

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-a...

 

Thanks!