since ‎15-10-2015
‎02-04-2021
kartheekd203042
Level 2
Re: GraalVM in AEM 6.4+
Avatar

kartheekd203042

kartheekd203042
- Adobe Experience Manager
Thanks for the links Kiran V however I am specifically looking for anyone who have used the GraalVM within AEM and how it was used especially on Oracle JDK 8?

Views

172

Likes

0

Replies

0
Re: Editable Templates not displayed
Avatar

kartheekd203042

kartheekd203042
- Adobe Experience Manager
Recreated the instance which solved the issue as it was likely caused by a corrupted repository.

Views

185

Likes

2

Replies

0
Re: Enabling non html files in Touch UI
Avatar

kartheekd203042

kartheekd203042
- Adobe Experience Manager
Thanks Jaideep for the quick response.Yes we already have evaluated that and are aware of such options however there are legacy dependencies that we are trying to overcome and the query is that if such an option is present in Classic UI then the Touch UI might as well provide an option via config.This is the query we are trying to check upon in case this forum can guide in uncovering such a config to enable/disable this feature for non html files.

Views

512

Like

1

Replies

0
Re: content insight servlet
Avatar

lmha

Employee

lmha
- Adobe Experience Manager
Hi Kartheek,Apologies for the delay, I was confirming if the information is fine to release to public.The workaround instead of installing the patch is to:Change the “Whitelist” value from .*/api[0-9]*.omniture.com/.* to https?:\/\/api(\d+)?\.omniture\.com(:\d+)?\/rs\/0\.5\/.* within /system/console/configMgr/com.adobe.cq.contentinsight.impl.servlets.ReportingServicesProxyServlet configuration.Please make sure to upgrade to latest official patch when possible.Regards,Lisa

Views

1.1K

Likes

0

Replies

0
Re: Siteminder AEM Webserver Integration
Avatar

Jörg_Hoh

Employee

Total Posts

3.1K

Likes

1.1K

Correct Reply

1.1K
Jörg_Hoh
- Adobe Experience Manager
Hi,Regarding 1: If I understood you right, the siteminder agent is scanning all requests coming into that Apache instance, not only the ones which are hitting the vhost the agent is configured in. That looks like an issue with the siteminder agent and should be solved on the siteminder side. I don't see a way how this can be solved on httpd or dispatcher side;Regarding 2: Also I don't see a chance to handle this outside of the siteminder agent. If you were able to limit the agent to a single vho...

Views

359

Likes

0

Replies

0
Likes given to
Likes from