Configuring DataServer applications with a self-service OpenEdge AppServer or Progress AppServer

The figure below shows an example of a DataServer application that is configured with an AppServer. The figure illustrates how to combine clients and servers that run on different platforms.

In the figure above, the OpenEdge client runs on a client machine (either in Windows or in UNIX) and can access a remote machine that has OpenEdge Management or OpenEdge Explorer to manage the AppServer instance. The connection between the OpenEdge client and the AppServer residing in the remote machine is established using the AppServer networking.

With the OpenEdge 11.6 release, the DatServer for MS SQL Server is a candidate module Progress multi-threaded AppServer.

The remote machine has a Unified Broker AppServer instance with multiple AppServer agents in it or it has a Progress AppServer instance with multiple AppServer agent threads. For every self-service AppServer Agent process or thread, the connection between the DataServer component of the agent process and the Data source is established on the same computer as the AppServer using the respective DataServer source linkage. Data Source Linkage specifies how the DataServer component of the agent processes use the ODBC driver to locate and connect to the data source.

The DataServer for MS SQL Server can be accessed from agent processes of the OpenEdge AppServer or from agent threads of the Progress Application Server for OpenEdge. The Progress Application Server for OpenEdge can only manage DataServer sessions fully within the Progress Application Server for OpenEdge if those sessions are self-service. The Progress Application Server for OpenEdge does not support distributed DataServer components although a DataServer client component in the Progress Application Server for OpenEdge can access a server component configured in a DataServer instance of the Unified Broker or a server process spawned from ProBroker.