OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 1: Introduction<br />
Typical configuration scenarios<br />
In a distributed client-server configuration, the <strong>OpenEdge</strong> client runs on a client<br />
machine (either in Windows or on UNIX) and accesses a remote server on a Windows<br />
server where the broker <strong>for</strong> the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> is running.<br />
Multiple Name<strong>Server</strong>s and/or brokers can be running simultaneously on one server<br />
machine. The <strong>Data</strong><strong>Server</strong> client connects to a broker <strong>for</strong> <strong>OpenEdge</strong> <strong>Management</strong> or<br />
<strong>OpenEdge</strong> Explorer either directly or through a controlling Name<strong>Server</strong>. (See the<br />
important caution that follows.) It is then automatically reconnected to a <strong>Data</strong><strong>Server</strong><br />
established <strong>for</strong> it by the broker. Each executing broker can spawn a multitude of<br />
<strong>Data</strong><strong>Server</strong> processes. A spawned <strong>Data</strong><strong>Server</strong> process uses the ODBC driver to locate<br />
and connect to the data source. The actual target database might be either local or<br />
remote to the host machine. The schema holder can run on the client or you can locate<br />
it on any host that is accessible on your network. Each spawned <strong>Data</strong><strong>Server</strong> can<br />
service database requests <strong>for</strong> the same database or <strong>for</strong> a different database than those<br />
of other spawned servers.<br />
In remote <strong>Data</strong><strong>Server</strong> configurations, <strong>OpenEdge</strong> handles the communication between<br />
the client and the server. <strong>OpenEdge</strong> <strong>Management</strong> or <strong>OpenEdge</strong> Explorer supports only<br />
the TCP/IP network configuration.<br />
Caution: In a run-time configuration, all <strong>Data</strong><strong>Server</strong> clients should attach consistently<br />
either to a set of Name<strong>Server</strong>s or to a set of brokers. Do not run brokers<br />
under controlling Name<strong>Server</strong>s <strong>for</strong> one client while another client<br />
simultaneously attaches directly to 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 <strong>OpenEdge</strong> <strong>Management</strong> or <strong>OpenEdge</strong> Explorer” section on<br />
page 186<br />
• The “Starting and stopping a broker process from <strong>OpenEdge</strong><br />
<strong>Management</strong>/<strong>OpenEdge</strong> Explorer and connecting a client” section on page 211<br />
For more in<strong>for</strong>mation about the Unified Broker Framework, its elements, and how<br />
Unified Broker products such as the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> work within the<br />
framework, see <strong>OpenEdge</strong> Getting Started: Installation and Configuration.<br />
50 <strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong>
Change language