[MGNLPUR-43] User replication alternatives Created: 06/Apr/10  Updated: 04/Apr/14  Resolved: 16/Apr/10

Status: Closed
Project: Magnolia Public User Registration
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Andrei Rugina Assignee: Magnolia International
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.modules.observation.config.listenerConfigurations.activateChangedPURUsers.xml    
Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

When there are multiple public instances it might be useful to have another solution besides clustering for user replication.
This way, when clustering is broken for various reasons (jackrabbit, magnolia and jackrabbit integration) like it is for magnolia v 3.6.3 , there will be a solution that can be used.
Another usage could be something like reporting/management from the author instance. Some kind of user reports/statistics could be available on the author instance, user content being replicated from the public instances (For now we understand that clustering between public and author instances is not possible)



 Comments   
Comment by Zdenek Skodik [ 16/Apr/10 ]

It can be achieved with observation module when the one Public can subscribe its content to the remaining Publics and vice versa. This configuration listens to PROPERTY_CHANGED event (you might want to observe also another events).

Generated at Mon Feb 12 06:42:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.