Configuring distributed DataServer applications using ProBroker
The following image shows an example of a distributed DataServer configuration that uses ProBroker. The figure illustrates how to combine clients and servers that run on different platforms.
Figure 6. The distributed DataServer for ODBC using ProBroker
In the above figure, the client runs on a client machine (either Windows or UNIX) and can access a remote server on any supported OpenEdge DataServer for ODBC platform. Multiple brokers may be running simultaneously on one server machine. The client connects initially to the ProBroker executable by locating the host and port of the executing broker. It is then automatically reconnected to a DataServer established for it by the broker. Each executing broker may spawn a multitude of DataServer processes. A spawned DataServer process uses ODBC drivers to locate and connect to a data source. Depending on the ODBC and data-source software implementation, the actual target database might be either local or remote to the host machine. Note that in this example, the schema holder also runs on the Windows client; however, you can optionally locate it on any host that is accessible on your network. Each spawned DataServer can service database requests for the same database or for a different database than those of other spawned servers.
In remote DataServer configurations, OpenEdge handles the communication between the client and the server. The client and server processes that make up the DataServer adapt to a variety of network configurations.
