At the center of GENESIS64 is the FrameWorX application. FrameWorX is the core GENESIS64 product that, among other things, handles aliasing, security, and data exchange between GENESIS64 applications. There is just one communication means between the client applications and the FrameWorX Server. By default, the FrameWorX Server is local on each GENESIS64 node. You must configure the default FrameWorX Server using the Platform Services Configuration option.
|
|
Note. In the Workbench is a Tools option called FrameWorX Server Location. This option is used to configure redundancy for the default FrameWorX Server. For more information about this menu option, refer to the Configuring Redundant Clients for GENESIS64 Viewers topic. |
There are four significant features of FrameWorX you may want to use to improve connectivity and data exchange in GENESIS64. They are:
Data Aggregation which pools together OPC tag requests from clients to reduce I/O traffic to a hardware device.
Data Prefetch which polls and collects output from a hardware device in anticipation of incoming client requests .
Data Bridging which sends a device’s output to another device.
Data Tunneling which sends data through a firewall.
Configuration of these features is done using registers in the Unified Data Manager. One of the key functions of Unified Data Manager registers is to provide a mechanism for defining variables and making them available to all GENESIS64 clients. You can use Unified Data Manager registers to help take some of the load off your inputs and outputs, to manage traffic more efficiently, and to improve the speed of your data communication.
See Also:
