Prerequisites: You must have the IndaGate package.

In the IndaGate configuration, you can enable redundancy mode to ensure service continuity in the event of a server failure.

This mode allows you to assign two servers on the same network: a primary server and a secondary server. If the primary server encounters an issue, the secondary server is immediately notified and takes over, ensuring a seamless transition without any service disruption.

There will be two servers communicating on the same network. The primary server is responsible for managing the PlcReader and CloudUploader services.

As long as it is functioning normally, the secondary server remains on standby :

In the event of a primary server failure, the secondary server takes over and ensures the operation of the services :

When the primary server becomes available again, the secondary server goes back to standby. The system then returns to the initial setup :

Note : If a communication issue between the servers occurs, both servers will launch the PlcReader and CloudUploader services.

Note : If the secondary server encounters a problem, the primary server will continue to ensure the service normally :

To activate redundancy mode, open your IndaGateConfig.json configuration file, located in the IndaGate package (see the article on Presentation and Access to IndaGate).

The following configuration file opens :

The first step is to activate redundancy mode by setting the "ActivateRedundancy" parameter to 'true' :

Next, specify the IP addresses of your primary and secondary servers :

Enter the port that allows both servers to communicate over the network :

Note : When redundancy mode is activated, the 'StartingMode' parameter highlighted below is not taken into consideration.

Save the changes made to the configuration file.

Redundancy mode is now activated.

Open the IndaGate application on the primary server's machine.

As long as the primary server is functioning properly, it ensures the operation of the PlcReader and CloudUploader services.

If you open IndaGate on the secondary server's machine, you can see that there are no services running :

As soon as the primary server encounters a problem and stops functioning, the secondary server is alerted, as they are communicating on the same network :

The secondary server then takes over by launching the PlcReader and CloudUploader services, which were managed by the primary server :

Once the primary server is operational again, the secondary server stops:

Thus, continuous operation is ensured.