Hi Krishna,you should try and see if you can add your properties to existing OOTB indexes. From what I have heard anecdotally, try and avoid having multiple indexes for the same type, in this case you have two cq:template indexes defined. See if it helps and let us know.Regards,Opkar

Hi Sandeep,recently when I set up AEM6.1 and SAML, I did not create the node at /etc/key/saml, I did follow the instructions at http://www.aemstuff.com/blogs/july/saml.html. Also, we created users in AEM(no auto-create). Please make sure when you add anything to the SAML OSGI configuration, you do n...

When reading through the documentation I noticed that the SlingGetServlet does not allow anonymous requests that retrieve html pages, this could be the cause of my problem.Can you provide the link for this please. The publish instance is set up to give anonymous access, so not sure why you are requi...

Is there any reason you have to do this using AEM forms? As Scott mentioned, there are better ways to implement this.Regards,Opkar

The Scheduler is a service that uses a cron expression to schedule other services/jobs. Here is an example [2].You could run code that runs on a schedule to check for the replicated property, but depending on how many pages you have and how often the job is run, this could place a load on the system...

For any new components you create, you simply make sure they include the property: cq:disableTargeting="true" as part of your review process.Scott's point about a tool/script was for adding this property to existing components, if you wanted you could add them to new components, but it is simpler to...

Hi Sudheer,as Scott implied this is not a typical use case. With AEM you can either create the personalisation in AEM, or use DTM/Target to do it from the marketing cloud. If you did want to use an external source, then you would have to write the integration yourself which I'm not sure might even b...

Hi Sudheer,when using an IDP, you must have a user account AEM. Either created before or auto created on login. If you wish to extend the authentication handler you could create a generic user that all your users get mapped to. After login, you would then call a backend system (e.g. CRM) and get the...

Hi Balu,as you have no doubt done, if you search google there seems to be many reasons for this type of error. Recently I came across this when I migrated some AEM5.6.1 code to AEM6.1The issue was resolved for me by making sure the import was for the actual class, rather than the package. In your ca...

Have a look at your error.log file as your instance starts, make sure there are no exceptions during startup.Next check to see if you get any errors/exceptions when you try and log in.Regards,Opkar