You cannot cache the touch UI request because otherwise you are not able to use the new version of css or js if you install a new SP or CFP. And you need to delete the generated cache manually after the update of your instance.

It's not the same approach.By using the dispatcher you could disable it without give access to the AEM instance.An other point is that in a typical architecture you cannot expose directly the AEM instance in internet but you need to use an Apache.In fact the AEM instance need to be used in VPN and t...

Hi,the purpose of the dispatcher for an author instance is not only for balancing but also for security (e.g. Https [0]) .You need to consider that if you have a dispatcher in front of the author instance, you could disable the access of CRXDe and SystemConsole for the authors. Without a dispatcher,...

Hi,just a simple question. You cannot use a different workflow name for the different sites?Thanks,Antonio

Hi,could you post the stacktrace? It seems an interesting behavior.Thanks,Antonio

Hi,is not very clear which is the result that you need.Do you mean that you want to run a different workflow, based on the selected site, after the "Request Publication" action?Let us know.Thanks,Antonio

Hi,could you share a screen of the error?Just to be sure.Thanks,Antonio

Hi,which kind of issue are you facing? Could you add more details regarding the issue?Thanks,Antonio

Hi,Have you already checked if you can find all your scheduler from the OSGi Console?http://localhost:4502/system/console/status-slingscheduler Let us know.Thanks,Antonio

Hi,if you try to use a ReplicationListener i think that you are sure that the element is already published on the publish instance.I put here a snippet that I use for my project:package com.adobe.cq.listeners;import com.day.cq.replication.*;public class MyReplicationHandler implements ReplicationLis...