Remark to AEM CS: members of the "administrators" group can do it there.

The underlying repository is quite flexible, and also the authorization mechanism is extensible (although rarely done). But the authorization is implemented on the repository level; that means if you have read access to a resource, you can read it for whatever purpose you need to access it. That mea...

AEM does not have an implicit concept of a site (as in a specific Site class/object). "Sites" are normally represented by pages into a project-specific hierarchy structure. Also, AEM does not manage sites as an entity, but only knows of pages, which can be updated individually or in bulk. That means...

I would start at https://business.adobe.com/products/experience-manager/adobe-experience-manager.html# and check from there the linked solutions and customer stories.

The ResourceChangeListener is the recommended approach, as sending all repository changes as OSGI events is not scalable enough. Also you need to handle all requests, you cannot limit your listener be called only for a certain path(s).

You should establish a procedure for such cases, which records a number in information from the runtime before the system is restarted. For example: do 5 thread-dumps in 2 second interval and also a heapdump. Then you have more data you can check, as the logs often do not show what actually is going...

It's just a warning.(I have seen to often code, which assumes that every page as jcr:content child node. According to the number of warnings I see this is not always the case.)

this property has to have the type Date, otherwise the ordering is not what you want.

isn't it possible to fetch the userprofile from the system where this profile is stored, instead of importing it into AEM and process it on a server-side there?  In that case the client (browser) will can fetch the data and insert it into the page where required.

This approach of using a server-side session will cause problems, as the AEM default architecture forsees a clustering approach only on the author side, and on the publish side there is a farm (independent systems which do not know of each other). In all cases the server-side HTTP-sessions are not s...