Hi, For my project which is on AEM 6.5 we discovered that the cache is not getting created under /content/{project}/ path.If we hit page with .html extension the cache is getting created but under the /var/www/html directory, but pages without html extension the cache is not at all getting created. ...

Hi @georhe6 , I have tried both the approaches, Git sub module approach though worked fine but we faced some limitation while syncing code from Azure repo to Adobe repo. Finally I have used the git actions to merge multiple repos into a parent repo and push it to Adobe repo, as below. https://experi...

Hi @kalyanchakravarthych  Have you tested after the deployment ?A 200 response means the user has access to retrieve the file directly from the dispatcher cache.  Other than 200 means the request is not served from cache. Check the Dispatcher log to see the requested url has cache hit statements wit...

Thank you @HrishikeshKa, though it is an open discussion and we have multiple ways to approach this, your answer would definitely help.

Thanks @HrishikeshKa for the response. How can we share the components as per the 2nd point in case of multiple repos?If a component is used by Tenant 1 and is developed in Repo1 but later it needs to be reused.  If we are using Azure repos then what are the ways repos can be created and pipeline jo...

Hi @AMANATH_ULLAH  Replication API can be used to programatically activate pages. Get the reference of the API@ReferenceReplicator replicator; replicator.replicate(session, ReplicationActionType.ACTIVATE, pagePath); Refer this https://experienceleague.adobe.com/en/docs/experience-manager-cloud-servi...

Hi, We are in the process of hosting multiple projects in a shared environment on AEM Cloud.The requirement can be:Single repo for all customermultiple repo (individual repo for each) can share components or other resource I have gone through the documentation for the best practices and challenges.h...

Hi Nivetha, The error means that the jcr:content node under the page node /content/test/en_US/demoPage is not there. If this error is in publish then check if the jcr:content node is present in author and activate the page it will resolve the issue.If this error is in author then you can create the ...

Hi Raja, Can you elaborate or give more examples for point 2 and 3?If I enable SAML setup on preview environment aswell how to do that.How do we set up user access policy on preview env?Are you suggesting customize the saml authentication to accomodate the whitelisting of domain, any example?Note: t...

Hi Suresh, I know that the url is accessible like and doesn't require any access, that is why we need to add user permission to the preview environment. I was thinking to have the same SAML setup enabled as we do for the publish environments but then how that can be configured.