Set -DincludeDispatcherConfig="n". This works for me in Mac. In case, somehow it does not work for you. Simply delete dispatcher folder in the project generated and remove sub-module inclusion in pom.xml.    

Have you checked this- https://exchange.adobe.com/apps/ec/107741/sprinklr-integration-for-adobe-experience-manager. What is your problem and approach? This is a good doc to start with - https://d1a2d0h96mvhgv.cloudfront.net/3/107741/e1d42a58-e025-48bc-9d22-0c120bae9205.pdf

Just replicating /etc/truststore does not solve this. You must copy the hmac/master keys files physically  from the filesystem (/crx-quickstart/launchpad/felix/bundle25/data) too to the other instance. So the steps are:1. Replicate /etc/truststore 2. Copy the hmac/master keys files physically from t...

Just replicating /etc/truststore does not solve this You must copy the hmac/master keys were physically copied from the filesystem (/crx-quickstart/launchpad/felix/bundle25/data) to the other instance.

Anyone facing this issue should note that the "client code" expected in this dialog is actually the org id or the tenant id. For example if your cloud product URL is https://experience.adobe.com/#/@aes1448/target or https://aes1448.experiencecloud.adobe.com/ Then your "client code" is "aes1448" for ...

This is correct answer. The agent must have this - property = { "name=akamai", "service.ranking:Integer=1001" }

Hi Abhay,There was some embed-dependency issue with the repo that I shared. I have updated the code at - GitHub - vivekanand-mishra/app-insights . Now, It should be running fine and request tracking should work properly with AEM just make sure to provide correct instrumentation key. Can you try out ...

Hi Abhay,I hope you are following this article- Performance monitoring for Java web apps in Azure Application Insights | Microsoft Docs I have not tried this. But I suggest modify your AEM start up script and change this line to include java-agent:if not defined CQ_JVM_OPTS set CQ_JVM_OPTS=-Xmx1024m...

kiranv43511543​ Overlaying of OOTB should be avoided to reduce tech debt to AEM upgrades . Recommended way is to create a separate client lib with just one css as mentioned by arunpatidar26​. Just make sure, the client lib category is same as of the OOTB client lib which you want to change. As long ...

Agreed with Arun. Instead of overlaying file, creating a custom clientlib is cleaner approach. That way you would be upgrade safe.