The remote, client/server, DataServer configuration
The following figure shows the remote DataServer configuration.
Figure 5. The remote, client/server, DataServer for MS SQL Server
In the remote configuration, the OpenEdge client runs on a client machine and the OpenEdge server components and any MS SQL Server client software run on a remote server machine. The actual target database can be local or remote to the machine where the OpenEdge DataServer for MS SQL Server executes. With the MS SQL Server client software supplied modules that manage networked database communications, a remote database configuration is possible. The DataServer cares only about the data source definition on its machine. Remote database access is transparent to the DataServer. In addition, the schema holder can be accessed locally or remotely depending upon your OpenEdge database configuration.
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.
The following table lists the supported configurations for setting up a remote DataServer. It contains possible client-server combinations and networking options.
Table 2. Supported configurations
Client
Networking
Server
OpenEdge client in Windows
None
The server, client, ODBC client, and data source are on the same machine.
OpenEdge client in Windows or on UNIX
OpenEdge
The client can reside in Windows or on UNIX. The server, ODBC driver, and data source are on a Windows server machine.
