since ‎10-11-2016
‎10-12-2019
swapnan73983825
Level 1
AEM 6.1 to AEM 6.3 Upgrade
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi All,We have to update our application from AEM 6.1 to AEM 6.3. Need some pointers and suggestions or challenges faced in upgrading from 6.1 to 6.3.Thanks In Adavance.Regards,Swapna

Views

1.0K

Likes

0

Replies

2
Re: Require AEM Architect certification materials
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Thanks

Views

4.0K

Likes

0

Replies

0
Require AEM Architect certification materials
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi All,I am planning to give AEM architect certification. Kindly provide any useful links or materials for preparation.Thanks,Swapna

Views

12.0K

Likes

3

Replies

9
Re: Resource dumped by HtmlRendererServlet error while moving the Parsys Component
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi Anay,Ya, the issue is solved.We have created custom parsys component. We will get the HTMLRendererServlet if we try to drag and drop the parsys component inside another parsys component. There are few restrictions for parsys component. So in the design mode of custom parsys we have restricted the same custom parsys to be dragged and dropped (Click on Desgin mode from side kick -> Edit the custom parys component -> Uncheck the parsys component from the opened window). This makes sure that the ...

Views

1.3K

Likes

0

Replies

0
Spring dependencies are not registering in the AEM services
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi All,We are using spring related API's in our AEM bundle. The below services needs to be registered as Services in Felix console. As the springframework API's are not getting registered as Services, we are getting Service java.lang.NullPointerException: Specified service reference cannot be null. DelegatedExecutionOsgiBundleApplicationContext springContext = (DelegatedExecutionOsgiBundleApplicationContext) ViewHelperUtil.getService(DelegatedExecutionOsgiBundleApplicationContext.class); We also...

Views

381

Likes

0

Replies

0
Re: AEM Upgradation from 5.5 to 6.2. Which API to be used for Collab dependency
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Thanks JK. Very useful information.

Views

836

Likes

0

Replies

0
Re: AEM Upgradation from 5.5 to 6.2. Which API to be used for Collab dependency
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Thanks Scott for providing the latest doc link. I am not finding much upgraded documentation for com.day.cq.collab.commons.Rating and com.day.cq.collab.commons.RatingSystem. Do you have any pointer on this API, what should be the alternative api used for the Review and Ratings?Thanks

Views

715

Likes

0

Replies

0
AEM Upgradation from 5.5 to 6.2. Which API to be used for Collab dependency
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi All,We are upgrading our CQ instance from 5.5 to AEM 6.2. We are basically using the below com.day.cq.collab : cq-collab-commons : 5.5.2 dependency in CQ 5.5. Since the collab API is deprecated in higher versions (https://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/day/cq/collab/commons/CollabUser.html), what is the alternative API's which can be used?We are extensively using the below API's in the project. Since we are upgrading to AEM 6.2, we need to find out the alternative API's for the s...

Views

1.7K

Likes

0

Replies

6
Re: Dispatcher | Cache invalidation not working locally
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Thanks Thuong. But this dispatcher flush works fine for few days and it stops suddenly after 5th or 6th day. Did you faced this issue any time. Thanks,Swapna

Views

1.2K

Likes

0

Replies

0
Re: Dispatcher | Cache invalidation not working locally
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
tinyt6510512 wrote... Dear smacdonald2008, edubey, Thanks for your support. I resolved by re-configuration httpd.conf Thank, Thuong. Hi TinyT,We are also facing the same issue in our application. But the issue is not frequent. Replication works fine for 5 days and it stops after 5th or 6th day. We observed that the replication is blocked at the dispatcher level and we also got the same issue. Can you please let us know how you have fixed the issue. What configuration changes you have done in htt...

Views

1.2K

Likes

0

Replies

0
Re: Dispatcher | Cache invalidation not working locally
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi TinyT,We are also facing the same issue in our application. But the issue is not frequent. Replication works fine for 5 days and it stops after 5th or 6th day. We observed that the replication is blocked at the dispatcher level and we also got the same issue. Can you please let us know how you have fixed the issue. What configuration changes you have done in httpd.conf? Thanks,Swapna

Views

1.2K

Likes

0

Replies

0
Re: Resource dumped by HtmlRendererServlet error while moving the Parsys Component
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Thanks Kautuk. Will have a look into the links.

Views

1.4K

Likes

0

Replies

0
Re: Resource dumped by HtmlRendererServlet error while moving the Parsys Component
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi Scott,Please find the attached screenshots of the error and the components.We are getting this error only for the component which has resourcesuperType as /libs/foundation/components/parsys, and we are trying to move that component multiple times inside other parsys.Thanks,Swapna

Views

1.3K

Likes

0

Replies

0
Resource dumped by HtmlRendererServlet error while moving the Parsys Component
Avatar

swapnan73983825

swapnan73983825
- Adobe Experience Manager
Hi Community,We are getting the below error when we are trying to move the custom parsys component (which has other components configured inside this parsys ) to another parsys. It is an intermittent issue. When we are trying to move the parsys, sling:resourceType- foundation/components/parsys property is not getting copied to the moved node. Since the resourcetype is not found the sling is throwing the below error.Resource dumped by HtmlRendererServletResource path: /content/xx/yy/en_us/testing...

Views

4.5K

Likes

0

Replies

6