Hi Kareem! Normally, each magnolia instance uses its own database/repositories.
Clustering the repositories can make sense in the following situations: 1. When you have more than one public instance, you could cluster the repositories so they are all running with the same content. This is especially true for the repositories where user-generated submissions are stored (like data or comments), since you want user-generated content created on one public server to be available on the other public instances as well. 2. For the same reason it can make sense to cluster a repository between author and public, for example a forum repository - content is generated by users on the public instances, moderation is done by admins on the author instance, all using the same repository, so there is only one copy of the data. In theory, clustering could be used to share content (website and documents) repositories between all public instances in a load-balanced setup. This way, activation would only be needed to one public instance, and through the shared repo, all public instances would receive the update. However, setting it up in this way makes the clustered repo a single-point-of-failure for all public instances, not to mention concentrating all the load back to the one database, and since magnolia supports transactional activation to multiple public instances, I would use that instead. Clustering content repositories (website, dms) between public and author instances does not really make sense... After all, a key feature of magnolia is the separation of authoring and public systems, with activation in-between. Note that the settings in the configuration repository differ between public and authoring instances, so this repository can't be clustered anyway! So completely sharing the repositories between authoring and public systems is not possible, as far as I can tell. Regards from Vienna, Richard Von: [email protected] [mailto:[email protected]] Im Auftrag von Kareem Al Jabr Gesendet: Mittwoch, 05. Jänner 2011 10:49 An: Magnolia User-List Betreff: [magnolia-user] Does each public and author instances require different MySQL databases Hi Magnolian, I have managed to make Author instance use a clustered MySQL DB as a repository. And I can see all the tables created when the setup process is done. But now do I have to create a separate database for the public instance!? Because I tried to make the public instance point to the same database but it was not succeeding throwing an exception saying record already exists. But when I created a separate database for it like <param name="url" value="jdbc:mysql://127.0.0.1:5000/Magnolia_Public<http://127.0.0.1:5000/Magnolia_Public>" /> it is not creating such trouble. But I can see the same number of tables created in both author and public instances 51 tables: For Author I am using <param name="url" value="jdbc:mysql://127.0.0.1:5000/Magnolia_Author<http://127.0.0.1:5000/Magnolia_Author>" /> For Public I am using <param name="url" value="jdbc:mysql://127.0.0.1:5000/Magnolia_Public<http://127.0.0.1:5000/Magnolia_Public>" /> Please let me know if I am following a correct approach or not. Thanks, Kareem ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
