In screenshot you provided you set the run mode of the trigger to Publish. When you set the run mode to Publish that means that workflow will on be kicked off on a server that includes the Publish run mode. Since you author server has a run mode of Author that workflow trigger will never start a wor...

They used in specific cases where you are off loading workflows or jobs to other AEM author instances. So for example if you have a large DAM implementation with frequent asset uploads you might choose to off load the creation of renditions to dedicated server in order to better scale you authoring ...

The reality is that anytime you load new content into a page client side (which is what the personalization code does) you can end up with flicker. Whether or not you see flicker is influenced by any number issues including your custom HTML/JS, network latency, and the end users browser performance ...

The personalization tag library is defined in cq-personalization bundle (<groupId>com.day.cq</groupId> - <artifactId>cq-personalization</artifactId>). The right version depends on which version of AEM you are running - you can find the version by looking at the bundle list in Felix. Making that a de...

I am not sure if this is a copy and paste issue but you have a space in the URL - is that present in your code? I assume that you code that looks like      <%@taglib prefix="personalization" uri="http://www.day.com/taglibs/cq/personalization/1.0" %> at that top of you JSP page?

When you say you have created a configurable OSGI bundle do you mean you have a service or component in that bundle that is configurable? I am assuming that's what you mean. In that case you need to define getters for any configurable values on your service's interface. Then your use bean gets a ref...

Are you interested in controlling the configurations that are managed on the component's definition node (things like component group or sling resource super type) or configurations for the custom code you write in the JSP/Sightly of the component? I agree with Scott that you can't do that for the c...

You can't install AEM 6 with 1.8. First you have install it with 1.7 and then apply service pack 1 or 2 which both support 1.8. After you have applied the service packs you can shut down and then restart using 1.8. The compilation error is what happens when you try to run a base AEM 6 with 1.8 witho...

So is your concern hard coding or what happens at runtime? If your concern is hard coding then in addition to Jörg's suggestion of using an load balancer or a web server as the proxy you could also manage the host and port names in AEM (either as an author managed value or as an OSGI configuration)....

I can't speak for Adobe, but what I can say is I think I first heard that the allowed paths template property was being deprecated back in 5.2.1. I'd say that's been the message for going on 4 or 5 years now but Adobe has yet to actually remove support for it. I have continued to use it on my implem...