Hi,
I'm using CMDBuild 2.0 (07/02/2013) with two instances to increase service availability. Almost operations are executed through SOAP.
When I modify data model in one CMDBuild instance I have to restart CMDBuild the other instance to get data model updated which until now was not a problem, however, today I noticed that when I add a new Lookup entry to a specific Lookup type, in an instance, it will not take effect in the other instance.
So I have two questions:
- CMDBuild is not supposed to be used with several instances in the same database?
- If so, how can I solve this problem?
Thanks in advance,
Pedro
Dear Pedro,
each instance of CMDBuild (single webapp running in its own container) must have it's own database. Sharing a database between multiple instances can easily take to data loss/corruption. You can solve the problem setting up the replication of the cluster. See here some links:
Best regards.
-- Davide Pavan
Previously Pedro wrote:
Hi,
I'm using CMDBuild 2.0 (07/02/2013) with two instances to increase service availability. Almost operations are executed through SOAP.
When I modify data model in one CMDBuild instance I have to restart CMDBuild the other instance to get data model updated which until now was not a problem, however, today I noticed that when I add a new Lookup entry to a specific Lookup type, in an instance, it will not take effect in the other instance.
So I have two questions:
- CMDBuild is not supposed to be used with several instances in the same database?
- If so, how can I solve this problem?
Thanks in advance,
Pedro