Host Multiple Databases from One Web Server
See Advanced Topics.
One data center might want to host databases for multiple Open Dental customers. These databases may be on the same physical machine if care is taken to isolate the customers from having access to each other's data.
Also see: Multiple Locations
We do not recommend hosting multiple databases from one web server (e.g., third-party hosted server, such as Amazon RDS) unless a capable IT is involved and they fully understand what is required during updates.
The current recommendation is for each customer to have a separate virtual machine (VM) with its own instance of MySQL and its own A to Z folders. There can be some economies of scale compared to a traditional server because multiple customers can share the same hardware. There are also some advantages in disaster recovery because a VM can be easily moved to a different physical server.
When clients connect to the server over the internet, the data must be encrypted. The current recommendation is for the VM to be connected to the physical office by VPN.
The three workstation connection options are direct, RDP, or Middle Tier. This still applies to multi-tenant scenarios, so the workstation connections must be considered as part of the complete solution.
A different MySQL User will need to be set up for each customer (MySQL Security). If, for example, a customer database is called od_springfield_4932, then, set up the MySQL user for that customer to have full access to od_springfield_4932*. Notice the * wild card character. This allows Open Dental to make backups of the database during the update process. The MySQL user must also have full privileges, including create table and drop table.
If wanting to work from particular devices or IP address ranges, information about setting up usernames for specific devices or network segments is available in the MySQL Documentation or MariaDB Documentation . Open Dental does not provide advice or direct support on setting up usernames for particular devices or network segments. Open Dental is functional as long as the specified MySQL user has the correct (full) permission set.
If the customers are bridging to eCW using HL7 (eClinicalWorks HL7), multiple instances of the HL7 service will need to be set up, each with a different service name, exe folder, FreeDentalConfig.xml file, and database connection. Different customers may be on different versions of Open Dental. Each HL7 service can be shut down independently as needed.
We recommend HL7 TCP/IP ports instead of HL7 folders. This will eliminate any HL7 folder sharing issues (Generic HL7).
Each database will require it's own A to Z Folder. See Paths for more information.
Different versions of the Middle Tier can be hosted on one server.
For advanced IT professionals only.
Multiple Open Dental Directories
Multiple eConnector Folders