Chapter 10. Technical Information
- Table of Contents
- 10.1. How Cascade Connect works
- 10.2. The Cascade DataHub
- 10.3. When to use the Cascade DataHub
- 10.4. If not using the Cascade DataHub
- 10.5. Start-up sequence
This section presents terminology and technical descriptions that give more details about how Cascade Connect and the Cascade DataHub work. The following topics are discussed:
How Cascade Connect works.
The Cascade DataHub.
Multiple connections.
10.1. How Cascade Connect works
Cascade Connect is started from the Windows computer, since that computer is the client, and the Windows operating system is generally considered to be a less stable environment than the data server operating systems that Cascade Connect supports.
After start-up, the Connect Server attaches itself to a specified Cascade DataHub running on any non-Windows node of the network, and registers with it for all point changes. Messages are passed from any node on the network to the Cascade DataHub, then immediately to the Windows client via the Connect Server and Cascade Connect. When a message is sent from the Windows client, it travels the same route in reverse to the Cascade DataHub, which in turn distributes the new information to all of its registered clients.
The Connect Server can also be configured to simply start and declare a name for itself. In this mode, it will wait to receive messages from other data server tasks, or it will send messages it receives (from the Windows client) to the data server task named in the Cascade Connect configuration file.
 | If the Cascade DataHub is not used, the data distribution program used in its place should communicate with the Connect Server running in this mode. |