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

[Achim Westermann]

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,

Achim