Configuring FrameWorX Redundancy

You can set up FrameWorX redundancy in Workbench in two steps:

• Creating and configuring an individual FrameWorX connection for each FrameWorX server, either direct or reverse. You usually set up the connections in Servers and Redundancy > Server Connections. Learn more

  However, you can also create a new connection directly from Unified Redundancy (see step 3).

• Creating and configuring a redundancy cluster.

To create and configure a FrameWorX redundancy cluster:

1. Open Workbench and in Project Explorer, expand your project > Servers and Redundancy > Unified Redundancy.
2. In the Connections panel on the left, select the desired FrameWorX connection and drag-and-drop it to a free space in the Unified Redundancy Graph panel. This creates a new cluster.

3. Drag and drop redundant connections to the newly created FrameWorX box (cluster). You can change the priority by moving the connection up or down.

   

   To create a new connection, select Click here to add a new item , then select the FrameWorX connection type and click OK. Click the newly added item to open the Connection Settings dialog in the right panel. The dialog is identical to the one in Servers and Redundancy > Server Connections.

4. When you have added all desired connections, click the cluster heading to open the Cluster Settings dialog in the right panel, and in Alias Name, enter the cluster name. The name will be displayed in Data Browser as a new network connection.

   

5. Configure the remaining settings, and then click Apply.

   • Primary Target Also Identifies Cluster: When selected, any point subscribed to the primary server becomes subscribed to the cluster, making the connection redundant without the need to re-subscribe all the points to the new cluster name. This is useful if you already have displays and other setups with subscriptions to the OPC UA server before making it redundant.

   • Auto-Switching Behavior: Determines the strategy of switching back after the primary (higher priority) server goes back online.

     • Sticky: The current connection stays active as long as the server is online, even though the primary or higher-priority server comes back online.
     • Back to Primary: The connection switches to the primary server as soon as it comes back online.

     • Best Available: When the cluster has more than two connections, it always switches to the highest priority connection that is available.

   • Enable Hot Switching: When enabled, all data points are constantly subscribed to all servers in the cluster, which creates a buffer that covers the data loss caused by the switching time. However, it doubles the traffic (or more than that, if the cluster contains more than two connections). When disabled (default), the data points only subscribe to the failover connection after the switch, causing a gap in the data flow.
   • Timeout: Specifies how long after receiving no heartbeat from the active server the connection switches over, and the server is considered offline.
   • Online Expression: Enables you to specify additional conditions for considering a server online or offline. For example, when a server is in maintenance mode, the connection does not switch to it, even though it is technically online.
   • Use as default Cluster for Standard Clients: When enabled, clients download the cluster's configuration and use it for switching between the specified FrameWorX servers. That setting is called client redundancy.
   • Use as default Cluster for Services: When enabled, services download the cluster's configuration and use it for switching between the specified FrameWorX connections.

6. In the right panel in Workbench, open Data Browser and expand Network Connections. You should see the cluster name in the list of connections. When expanded, it contains the same properties as the individual connections.