[opencms-dev] Can different installations of OpenCms connect to the same db schema?

Shency Revindran Shency.Revindran at monitisegroup.com
Fri Jan 29 12:19:25 CET 2010

Hi Edwin / Achim / Jordi,

Thanks a lot for sharing your valuable thoughts and experience in this regard. That is lot of stuff for me to think about

Achim, I am getting your point in saying that I need to make sure /sites/contentset_X is only served from the very same server. Currently we have separate db schema for separate opncms instances which is increasing day by day. So we are thinking of options to reduce the number of opencms db schema instances.

One final question, suppose if I decide to go with the option1 in my initial mail (i.e., single opencms instance with multiple sites - sites/contentset_X, sites/contentset_Y.. connecting to the same db schema, controlled user privilege to restrict users to see only their corresponding site content) --> Will this solution work fine with out any issues? Is there any issues that I should expect with this solution as well?


-----Original Message-----
From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Achim Westermann
Sent: 29 January 2010 11:09
To: The OpenCms mailing list
Subject: Re: [opencms-dev] Can different installations of OpenCms connect to the same db schema?

Hi Edwin,

thx for the answer.

> In addition, my own solution has the following limitation on hand:
> 1. Only Master OpenCms workplace enabled. If Slave OpenCms workplace also
> enable, it will crush the MySQL one-way replication.

That is true also if you use OCEE Cluster. You cannot write to master and slave. I once set up a backup master tomcat connected to the same
db as the original master but was turned off. In case the original master would crash this was an option to allow editing on the slave.
Once I saw a client who had enabled the workplace on the cluster slave (where both servers were connected to the same db) and then
complained about "CmsResourceAlreadyExistsExceptions". What had happened was: The logged in at A and created and published a.html. Then they
logged in at B and tried to create a.html. They did not see it as the resource view is cached. But it was in the db with the same name but a
different UUID.

--> Also it's better for editors just to have one single URL the are able to log in to to avoid confusion.

> 2. Static Export won't work.

This works with OCEE.

> 3. Flexcache out of sync between Master and Slave machine within polling
> period.

I understand.

kind regards,


This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit

This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email

Please note, we have moved. Our new address is Monitise plc, Warnford Court, 29 Throgmorton Street, London EC2N 2AT

This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying, disclosure or taking of any action in reliance upon it by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy.

The Monitise group comprises: Monitise plc (Reg. No. 6011822), Monitise Group Limited (Reg. No. 5590897), Monitise International Limited (Reg. No. 5556711), Monilink Limited (Reg. No. 4831976) and Monitise Business Solutions Limited (Reg. No. 5814266). These companies are registered in England and Wales and their registered office address is: Warnford Court, 29 Throgmorton Street, London, EC2N 2AT United Kingdom.

More information about the opencms-dev mailing list