Portlet store -- how is this done in AEM? (so it works like Liferay, WebCenter, etc.) | Community
Skip to main content
J
Jeff_Stieglitz
New Participant
January 9, 2018
Solved

Portlet store -- how is this done in AEM? (so it works like Liferay, WebCenter, etc.)

  • January 9, 2018
  • 12 replies
  • 4399 views

Folks, I am evaluating Adobe Experience Manager and I'm impressed by the power and and user interface of the overall solution.

A primary requirement of my project is allowing B2B end-users to customize what they see on their landing page.  With traditional portal products like Liferay, Oracle WebCenter, and IBM Websphere portal, a user can access a slide-out "store" of portlets, and then add them to their landing page, and then to a certain extent can re-arrange tiles or regions on their landing page.

I see that AEM can run portlets, but I wonder if I would have to code the end-user portlet selection capability on my own.    Please share your advice and links to examples; I've looked through the documentation but did not see anything which addresses this.

The portlets would be free and the list would be filtered by the end-user's role.

Jeff

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

The frontend part (the drag&drop if widgets) is something a good UX team can implement pretty fast, that's the least of my concerns :-)

But for me it looks like you are not that familiar with AEM, so I will go more into details.

* The general AEM architecture splits between the authoring and publish (public, internet-facing) part. I assume that these 100k users are working on the publish system (they are rather consuming than creating content).

* The standard, default and recommended architecture for AEM publish is the farming approach. That means, that you have a number of independent publish instances in a shared nothing approach. Every AEM publish instance is self-containing and hosts a full copy of all content.

* This also means that any change which happens solely on one publish instance (someone changes its profile) must be synchronized to all other publish instances.

With Sling Distribution there is a mechanism available which is designed for that usecase, it is hardly used (it's part of AEM Communities). I still would not call it "mainstream". But you could have a look at AEM Communities if it caters your needs.

Serverside personalization is a hard topic, as every AEM architect will tell you to personalize as much as possible on client side, because it scales much better. And use the dispatcher to cache as much HTML as possible (at best: 100%).

Jörg

12 replies

Show previous replies
Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
New Participant
January 9, 2018

Hi Jeff,

Each of the platforms will have its own architecture and Adobe AEM is not built on portlets model as primary like Liferay or WebSphere portals.

All these portals come with the capabilities of portlets as primary and have the CMS capabilities to it while AEM has CMS as the primary capabilities but can support the architecture of portlets. The link provided by @Scott talks about the same. Not sure if there are many implementations of that as a case study. https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/aem-as-portal.html

smacdonald2008
smacdonald2008
New Participant
January 9, 2018

Getting internal ppl's thoughts on this question.  Did you look here (i assume you have) -- AEM Portals and Portlets

Terms & ConditionsAccessibility statement

Loading footer...