Licensing an Additional Node
After purchasing an additional node, you need to activate the license for that node, and then you can connect it to the base node of your system. The process of activating an additional node license is the same as activating the license for the base node. Learn more
You can connect additional nodes to the base node and configure them together in what is referred to as a single system. To work together as a system, the nodes apply the following rules.
-
Base (parent) nodes and additional (child) nodes communicate with each other to confirm their license status and distribute license updates.
Unlicensed nodes running in demo mode can only communicate with the base node regarding the license updates; other communication is not allowed between nodes with licenses of different tiers.
-
The update rate for license status is 1 minute in the demo mode and 5 minutes in a licensed system. Base nodes expect to receive updates at least every 30 minutes.
-
The distribution of license updates from the base node does not work for a reverse FrameWorX connection with an unlicensed additional node because such nodes are not allowed to create any connections. Once the node is licensed individually, it can get updates even from a node connected via reverse communication.
-
A base node rejects the connection of an additional node if it is not of the same system. This is defined within the license programmed to the nodes.
-
Duplicate node license numbers in a system are identified as a license violation.
To connect an additional node to the base node:
-
Open Workbench and in Project Explorer, expand your project > Servers and Redundancy > Server Connections .
-
Add a FrameWorX connection to the parent machine. Learn more
Depending on your network settings, you may prefer creating a reverse FrameWorX connection. Learn more
-
In the Connection Settings dialog, select Set as a connection to the base node of the system, and then click Apply.
Within five minutes, the node will try to connect to the parent (base node) and validate the license. The node checks the connectivity with the parent periodically and ensures that the license is always validated.
What's Next?