...
The Connexion Cluster, shown above, consists of 2 physical, or virtual, machines, which are bound to the same Connexion Configuration Database. The Connexion Cluster operates in an Active/Passive mode where the Active node performs work, and the Passive node is idle until the Active node fails, or a user manually changes the Active node.
Since many of the Connections coming into Connexion will be HL7, a network switch (hardware, or software) must be used to route the network traffic to the active node in the cluster. Connexion can be configured to have the active node periodically ping the Network Switch to notify the switch which node in the cluster the network traffic should be directed to.
...
Configuring Database Mirroring
Connexion version 14 can be deployed in active-passive pairs in order to provide hot fail-over. In order to provide a fully automatic fail-over using Sql Server Mirroring, the following components are required:
Two instances of Connexion, running on two separate physical machines.
- An automatic fail-over deployment of SQL Server.
- A fail-over capable switch/router.
The simplest hot fail-over topology requires three physical machines. Two machines each have Connexion and SQL Server, and a third machine is required as a witness server for SQL Server replication. The witness role does not require any system resources, and so can be served by an existing server with a few spare cycles:
Info |
---|
More information on configuring Sql Server mirroring can be found on the Microsoft website here: Setting Up Database Mirroring (SQL Server). There is a good YouTube video with step-by-step instructions here YouTube Step-by-Step setup of Sql Server Mirroring. Another Step-by-Step article can be found here: Configure Sql Server Database Mirroring Using SSMS. |
Creating a Cluster
Install Sql Server
...