Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

AEM Environment Indicator in AEMaaCS

Avatar

Level 9
It's quite common to access multiple environments in the same browser while working with AEM, which makes it confusing which environment to change. My understanding is that AEMaaCS cannot change the author's name. ACS AEM Environment Indicator is not compatible to use. Would it be possible to make some sort of indicator that shows which AEM Cloud environment is?
 
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

The ACS AEM commons should be pushed via code base.

 

Example: By adding following via "filevault-package-maven-plugin" in all module.

 

<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.apps</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.content</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>

 


Aanchal Sikka

View solution in original post

7 Replies

Avatar

Community Advisor

You can configure "ACS AEM commons' AEM Environment Indicator"

 

https://adobe-consulting-services.github.io/acs-aem-commons/features/environment-indicator/index.htm...

 

Once configured, each environment can have a different color bar for easy visual identification. 

 

aanchalsikka_0-1671518417156.png

 


Aanchal Sikka

Avatar

Level 9

Is ACS AEM Environment Indicator works in AEMaaCS? my understanding is that ACS AEM Commons is not compatible in AEMaaCS

Avatar

Community Advisor

You are right. Not all features work on Cloud. In some cases, its explicitly mentioned if it works/does not work on AaaCS.

 

Environment Indicator should.


Aanchal Sikka

Avatar

Level 9

AEM Cloud is not allowing me to upload acs-aem-commons-content-5.4.0 package. I get below error while uploading the zip file. Error - "Package (or it's subpackage(s)) contains application content which isn't supported at runtime.

 

Looks like it is ACS Common is not compatible to AEM Cloud 

Mario248_0-1671532571799.png

 

Avatar

Correct answer by
Community Advisor

The ACS AEM commons should be pushed via code base.

 

Example: By adding following via "filevault-package-maven-plugin" in all module.

 

<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.apps</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-ui.content</artifactId>
<type>zip</type>
<target>/apps/abc-vendor-packages/application/install</target>
</embedded>

 


Aanchal Sikka

Avatar

Level 9

Thanks for your response. We also need to add below dependency in oder to embed ACS Common 

 

<dependency>
<groupId>com.adobe.acs</groupId>
<artifactId>acs-aem-commons-content</artifactId>
<version>5.4.0</version>
<type>zip</type>
</dependency>