Mindbreeze GmbH, A-4020 Linz, 2024.
All rights reserved. All hardware and software names used are brand names and/or trademarks of their respective manufacturers.
These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services and service outcomes, or any other protected rights. The dissemination, publication, or reproduction hereof is prohibited.
For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.
Generally, Mindbreeze supports centralized configuration of services for multiple nodes in one master node. All configuration changes are performed on one master node. All other nodes periodically fetch their configurations directly from master. In some network infrastructures the direct communication between master and nodes is not always guaranteed. In such network infrastructures the services on one node may not to be able to start if the master node is not reachable. The solution to this problem is that each node has its own local master which is always available. The configuration master node persists the configuration on a Windows file share and the local masters synchronizes their configuration from there.
In order to enable the configuration synchronization over Windows File Share the SharedConfigDirectory Windows Registry Key should be configured in all nodes.
The value of this registry key should be the path of the Windows File Share. The node ID of the supposed configuration master should be provided in a file naming masternodeid inside this Windows File Share. All configuration changes performed on configuration master will be persisted in this directory. The local masters synchronize their configurations from this directory.