OpenEdge Data Management: DataServer for Microsoft SQL Server

DataServer configurations
DataServer configurations
The DataServer for MS SQL Server can run in a variety of configurations. Depending on its
configuration, it is either a single OpenEdge executable or a set of OpenEdge executables that
you can distribute across operating systems. There are two general types of
configurations—local and remote—with variations on each type:
• Local DataServer — All of the DataServer software components, the schema holder, the
ODBC software, and MS SQL Server client software run on one machine.
• Remote DataServer — The DataServer software components run on different machines.
Typically, the OpenEdge client component runs on one machine, while the OpenEdge
server component runs on another machine called the host machine. Note that the ODBC
software and any data source client software required run on the same machine as the
DataServer software modules. In the remote DataServer configuration, this is the host
machine. The host machine and the machine on which the client runs communicate
through TCP/IP networking. A remote configuration exists within the framework of a
distributed application, whereby DataServers are spawned on the host machine using the
ProBroker executable or broker in the Progress Explorer administration framework.
The local DataServer configuration
Figure 1–4 shows the local DataServer configuration.
Schema
holder
OpenEdge client
DataServer
ODBC driver
Data-source client software
Figure 1–4: The local DataServer for MS SQL Server
Data
source
In the local DataServer configuration, all of the DataServer software components, the schema
holder, and data source client software run on the same machine. Depending on the ODBC and
data source client software implementation, the actual target database can be local or remote to
the machine where the local OpenEdge DataServer for MS SQL Server executes.
1–11