AEM 6.2 - 'nosamplecontent' == 'productionready' - why?

[timlwhite]

It appears from a support ticket that I opened, that in AEM 6.2 installing a server with the runmode of 'nosamplecontent' also forces the 'productionready' stuff, including disabling crx/de.

If I'm understanding this correctly, there is now no way to build out a development environment without all the Geometrixx stuff?  Am I missing something?

I could see adding a 'productionready' runmode that included 'nosamplecontent', but essentially the ability to 'just' not have Geometrixx has been removed.

[smacdonald2008]

Do you happen to know your ticket number so they can investigate this further. 

[timlwhite]

Thanks, Scott!

Yes, ticket number is 90121, they referred me to to this page: https://docs.adobe.com/docs/en/aem/6-2/administer/security/production-ready.html

[user2797012]

So, it looks that all security practices will be incorporated when this nosamplecontent run mode is used. But you can enable CRX-DE by following: https://docs.adobe.com/docs/en/aem/6-1/administer/security/security-checklist/enabling-crxde-lite.ht.... 

In case, you need to only remove geometrixx content, I do not see an option by run mode. I will verify internally and let you know. 

[Tuhin_Ghosh]

From the url provided it looks like now these runmodes are the same. :)

[kmrobin]

This change to nosamplecontent was made in AEM 6.1 itself and carried over in 6.2, see [1].

To enable crx/de back, there are simple steps as Kanika also mentioned.

But if you're only looking to get rid of geometrixx and do not require other security settings enforced by nosamplecontent, you may want to try a normal run mode and uninstall only the geometrixx super package form crx package manager: cq-geometrixx-all-pkg-5.9.222.zip

[1] https://docs.adobe.com/docs/en/aem/6-1/administer/security/production-ready.html

[timlwhite]

So, I have installed AEM 6.1 many times with nosamplecontent, and never encountered this issue.  So, if it was implemented in AEM 6.1, it was not in the same way.

I will try the geometrixx super package removal - in the past it was impossible to completely remove them once they were installed.

I would still be curious to know why the nosamplecontent runmode was changed, rather than just adding a 'productionready' runmode....just doesn't seem to logically make sense. :)

[smacdonald2008 · Accepted solution]

More infor from AEM Support: 

“nosamplecontent” had this change since AEM 6.1 and therefore carried over in 6.2 as well, see [1][2].

Of course crx/de can be enabled back as well by following couple of simple steps which are mentioned on the same doc pages and explicitly documented at [3].

[1] https://docs.adobe.com/docs/en/aem/6-1/administer/security/production-ready.html

[2] https://docs.adobe.com/docs/en/aem/6-2/administer/security/production-ready.html

[3] https://docs.adobe.com/docs/en/aem/6-2/administer/security/security-checklist/enabling-crxde-lite.ht...

[darrellw8102156]

Just to back up what timlwhite was saying...  nosamplecontent in AEM 6.1 was SUPPOSED to enforce all the suggested security, including the disabling of webDav, thus disabling crx/de, but it didn't do that.  Yes, it did enforce most of the recommended security features, but not the dav security feature.  We had 6.1 installed with nosamplecontent as a fresh install and crx/de was right there and working.  It wasn't until we upgraded to 6.2 that crx/de disappeared from the publisher, but mysteriously it's still working on the 6.2 author.