OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Typical configuration scenarios<br />
<strong>Data</strong><strong>Server</strong> configurations<br />
In a distributed client-server configuration, the <strong>OpenEdge</strong> client runs on a client machine (either<br />
in Windows or on UNIX) and accesses a remote server on a Windows server where the broker<br />
<strong>for</strong> the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> is running. Multiple Name<strong>Server</strong>s and/or brokers can be<br />
running simultaneously on one server machine. The <strong>Data</strong><strong>Server</strong> client connects to a broker <strong>for</strong><br />
Progress Explorer either directly or through a controlling Name<strong>Server</strong>. (See the important<br />
caution that follows.) It is then automatically reconnected to a <strong>Data</strong><strong>Server</strong> established <strong>for</strong> it by<br />
the broker. Each executing broker can spawn a multitude of <strong>Data</strong><strong>Server</strong> processes. A spawned<br />
<strong>Data</strong><strong>Server</strong> process uses the ODBC driver to locate and connect to the data source. The actual<br />
target database might be either local or remote to the host machine. The schema holder can run<br />
on the client or you can locate it on any host that is accessible on your network. Each spawned<br />
<strong>Data</strong><strong>Server</strong> can service database requests <strong>for</strong> the same database or <strong>for</strong> a different database than<br />
those of other spawned servers.<br />
In remote <strong>Data</strong><strong>Server</strong> configurations, <strong>OpenEdge</strong> handles the communication between the client<br />
and the server. Progress Explorer supports only the TCP/IP network configuration.<br />
Caution: In a run-time configuration, all <strong>Data</strong><strong>Server</strong> clients should attach consistently either<br />
to a set of Name<strong>Server</strong>s or to a set of brokers. Do not run brokers under controlling<br />
Name<strong>Server</strong>s <strong>for</strong> one client while another client simultaneously attaches directly to<br />
a broker.<br />
For more in<strong>for</strong>mation, about configuring and connecting the <strong>Data</strong><strong>Server</strong>, see:<br />
• The “Configuring with the <strong>OpenEdge</strong> Explorer and Progress Explorer” section on<br />
page 5–6<br />
• The “Starting and stopping a broker process from the <strong>OpenEdge</strong> Explorer and Progress<br />
Explorer and connecting a client” section on page 6–3<br />
For more in<strong>for</strong>mation about the Unified Broker Framework, its elements, and how Unified<br />
Broker products such as the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> work within the framework, see<br />
<strong>OpenEdge</strong> Getting Started: Installation and Configuration.<br />
1–15
Change language