Main/backup: support for clients, interfaces and modules
Here, the main/backup synchronization capabilities of all available interfaces and modules are listed.
Supported clients
If a main/backup solution is used, the clients that are used within such a project have to support main/backup, too. The clients from NETxAutomation support main/backup in the following way:
PC-based visualization: main/backup is fully supported. Within the server configuration, the connection details of the backup server can be configured. Switching between main/backup server is done automatically. Please note that a connection is only possible to the active server. The visualization is not able to connect to servers in standby mode.
Web-based visualization: main/backup is supported. The switch-over behavior depends on the used client software:
NETx Vision: Within the profile settings, the connection details of the backup server can be configured. Switching between main/backup server is done automatically. Please note that a connection is only possible to the active server. The visualization is not able to connect to servers in standby mode.
Standard web browser: if a server is inactive state, the web visualization port is no longer reachable. Main/backup switching has to be resolved via appropriate DNS entries. More information can be found here.
Web Manager: main/backup is supported. The user is able to login to both, active and standby, servers. However, if the server is in standby mode, access to the Web Manager interface is read-only.
The use of third-party clients (OPC DA, OPC UA , BACnet, MQTT, oBIX clients, ...) in combination with our main/backup solution is possible, too. However, in order to function properly, the third-party client software must provide the appropriate mechanisms. Please contact the vendor of the third-party software for more details.
Supported interfaces and modules
Column description:
M/B relevant: A main/backup synchronization makes sense at all.
M/B possible: A synchronization for this kind of interface or modules is available within our main/backup solution.
Field level interfaces
Interface | M/B relevant | M/B possible | Notes |
|---|---|---|---|
KNX |
| ||
BACnet |
| ||
Modbus |
| ||
Fidelio/Opera | Main/backup is possible. However, the issue of main/backup must be discussed with Fidelio/Opera integrator since issues may occur when not set up properly. | ||
Protel | Our Protel driver supports main/backup. However, it has not been tested with Protel, yet. | ||
VingCard | Not possible from VingCard side since VingCard software does not support main/backup. | ||
Kaba | Not possible from Kaba side since Kaba software does not support main/backup. | ||
Salto | Not possible from Salto side since Salto software does not support main/backup. | ||
GridVis |
| ||
OPC DA client interface | In addition to the internal main/backup mechanism, it is possible to define foreign backup OPC DA servers that are used if the foreign OPC DA servers are failing. | ||
OPC UA client interface |
| ||
Http |
| ||
MQTT |
| ||
NexusRF | Implementation available on request | ||
Infor | Implementation available on request | ||
CharPMS | Implementation available on request – needs to be clarified whether it is possible from CharPMS side. |
Enhanced modules
Interface | M/B relevant | M/B possible | Notes |
|---|---|---|---|
LaMPS |
| ||
Metering | Server Item values are only available in main server. If backup server becomes active, they will be available there, too. If a server becomes inactive, the respective items are removed. | ||
Messenger | Inactive server does not send any messages like e-mail or telegram messages | ||
Shutter Control | Implementation available in future releases |