We have a portlet, in which some variables are profiled. What we want to do is to set these profile values at runtime via API. This is similar to the "Configure/Edit shared settings" feature that portal provides, but due to some constraints, we are having to implement this functionality inside the portlet.
Our environment is clustered with multiple nodes. If I update the profileset at runtime, will it be reflected across nodes?
Pinned topic Profileset modification in a cluster
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-21T16:57:04Z at 2012-11-21T16:57:04Z by SystemAdmin
mburati 060000VQ202587 Posts
Re: Profileset modification in a cluster2012-11-19T21:22:39ZThis is the accepted answer. This is the accepted answer.When you expose a profile set for use with Portal's edit/configure modes, it then uses the portal's support for portlet preferences set in one of those modes, and the portal manages those preferences for you. The original profile set in the WAR is just a file in the WAR, so no it won't be reflected across nodes on different servers if you update one of them.
If you must set profile values within a portlet itself to customize the portlet (instead of in one of the portlet modes made for that use), then you may want to look into the Web Experience Factory's custom value handler support for profile values (eg, to build one to read profile set value settings out of a DB during regen).
Here are a couple of WEF product documentation pages on profile selection value handlers:
I hope that info helps,
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
SystemAdmin 110000D4XK9029 Posts
Re: Profileset modification in a cluster2012-11-21T16:57:04ZThis is the accepted answer. This is the accepted answer.
- mburati 060000VQ20
Thanks for the information. Using the custom value setter seems to be a feasible solution, as we can read the values from a centralized DB. I was just curious as to how Portal handles the preferences across nodes.