13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring the <strong>Data</strong><strong>Server</strong><br />

<strong>Data</strong><strong>Server</strong> components<br />

5–2<br />

The <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> can run in a variety of configurations. Some configurations<br />

involve a single process running on one machine. Others involve multiple processes running on<br />

different machines across multiple plat<strong>for</strong>ms.<br />

<strong>Data</strong><strong>Server</strong> configuration prerequisites<br />

Be<strong>for</strong>e you configure a <strong>Data</strong><strong>Server</strong>, you must:<br />

• Register your MS <strong>SQL</strong> <strong>Server</strong> database as an ODBC data source. For details, see the<br />

“Registering your data source” section on page 5–4.<br />

• Determine which components you need on which plat<strong>for</strong>ms and then set up the appropriate<br />

executables on those plat<strong>for</strong>ms.<br />

Table 5–1 lists the possible combinations and describes which executables you must set<br />

up on each machine. In this table, the term local indicates that the <strong>Data</strong><strong>Server</strong> component<br />

runs on the same machine as the client, while the term remote indicates that the component<br />

runs on a different machine than the client.<br />

Table 5–1: Installing the <strong>Data</strong><strong>Server</strong> components (1 of 2)<br />

Client <strong>Data</strong><strong>Server</strong><br />

Installing and<br />

configuring<br />

Windows Local Windows Use the default <strong>OpenEdge</strong><br />

client executable<br />

(prowin32.exe). The<br />

server component is<br />

embedded in the client<br />

executable.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!