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.

Starting a remote <strong>Data</strong><strong>Server</strong><br />

For example, a command line <strong>for</strong> an <strong>OpenEdge</strong> client process that you use to access an MS <strong>SQL</strong><br />

<strong>Server</strong> database might look like this:<br />

prowin32 mssholder -RO -db demo -dt MSS -ld demo -H host1 -S oserviceA<br />

-U bob -P bobpass<br />

Create a program icon <strong>for</strong> each unique set of connection parameters. See the “Connecting a<br />

schema holder at startup” section on page 6–9 <strong>for</strong> command-line in<strong>for</strong>mation and more<br />

examples.<br />

Starting the UNIX client process<br />

After starting the remote broker, you start the <strong>OpenEdge</strong> client process on a UNIX machine by<br />

running this executable:<br />

pro<br />

You can supply the connection parameters required by the <strong>Data</strong><strong>Server</strong> when you start the client<br />

process, or you can include them in the Connection Parameters field when you create a<br />

schema holder.<br />

For example, this command starts the <strong>OpenEdge</strong> client, connects a read-only schema holder<br />

named mssholder, and connects the MS <strong>SQL</strong> <strong>Server</strong> demo database using the mssdemo DSN<br />

with the user bob whose password is bobpass:<br />

pro mssholder -RO -db demo -dt MSS -ld mssdemo -H host1 -S oserviceA<br />

-U bob -P bobpass<br />

See the “Connecting a schema holder at startup” section on page 6–9 <strong>for</strong> descriptions of the<br />

required command line.<br />

6–7

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

Saved successfully!

Ooh no, something went wrong!