OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 1: Introduction
Figure 1 illustrates how the DataServer components are organized.
Selfservice
MSS
client
ODBC
driver
Data source manager
Data source
OpenEdge or Webspeed
application
OpenEdge DataServer
for SQL server
ODBC driver manager
ODBC
driver
Data source manager
Data source
Figure 1: Architecture for DataServer for MS SQL Server
Client-Server
MSS
client
Client-
Server MSS
server
As shown in Figure 1, the components for the self-service DataServer for MS SQL
Server are organized similarly to the client-server configuration except that the
DataServer is embedded in the client rather than executing separately. With a
client-server configuration, the components can be deployed so that the DataServer
resides on the same machine as the client (loop back), on the server for efficiency and
close proximity to the database, or distributed to a separate third tier.
The ODBC driver manager must reside on the same machine as the DataServer
“server.” To ODBC, the “server” half of a client-server configuration, or the self-service
DataServer appears as an ODBC client. In either case, an OpenEdge or WebSpeed
application uses the DataServer to work with the ODBC Driver Manager, which
accesses the desired ODBC driver. The driver then accesses the MS SQL Server
database.
Some of the DataServer components are linked with elements of the standard
OpenEdge architecture, as described in the “DataServer configurations” section on
page 45.
38 OpenEdge Data Management: DataServer for Microsoft SQL Server