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.
Starting a remote <strong>Data</strong><strong>Server</strong><br />
Starting a remote <strong>Data</strong><strong>Server</strong><br />
This section describes how to start and stop a remote <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong>. Starting<br />
a remote <strong>Data</strong><strong>Server</strong> involves starting the processes that make up the remote <strong>Data</strong><strong>Server</strong>.<br />
To start a remote <strong>Data</strong><strong>Server</strong>:<br />
1. Start the <strong>Data</strong><strong>Server</strong> broker process on your host machine. For details, see:<br />
• The “Starting and stopping a broker process from the command line” section on<br />
page 6–6<br />
• The “Starting and stopping a broker process from the <strong>OpenEdge</strong> Explorer and<br />
Progress Explorer and connecting a client” section on page 6–3<br />
2. Start an <strong>OpenEdge</strong> client process on a UNIX machine or in a PC running Windows that<br />
connects to the schema holder and the MS <strong>SQL</strong> <strong>Server</strong> database.<br />
Starting and stopping a broker process from the<br />
<strong>OpenEdge</strong> Explorer and Progress Explorer and<br />
connecting a client<br />
You can use the Progress Explorer to administer the server module (_msssrv.exe) of the<br />
<strong>Data</strong><strong>Server</strong> in Windows.<br />
Per<strong>for</strong>ming from the Windows host<br />
Be<strong>for</strong>e you attempt to start the <strong>Data</strong><strong>Server</strong> in the Explorer, be sure that you have configured it<br />
completely. After starting the broker from the Progress Explorer, you start your <strong>OpenEdge</strong><br />
client as you would in any remote <strong>Data</strong><strong>Server</strong> configuration.<br />
To start and stop the <strong>Data</strong><strong>Server</strong> from the Explorer, see the Progress Explorer online help.<br />
Per<strong>for</strong>ming on the client<br />
After you start the broker on the host machine from the Progress Explorer, you can connect your<br />
UNIX or Windows client. Use the same parameters that you would use to connect to the schema<br />
holder and MS <strong>SQL</strong> <strong>Server</strong> database in a standard ProBroker configuration. In addition:<br />
• Include the -Dsrv SVUB,1 parameter. This parameter allows you to connect to the broker<br />
administered by the Explorer.<br />
• Include the -<strong>Data</strong>Service data–service parameter to connect through a Name<strong>Server</strong> to<br />
the broker. The value <strong>for</strong> data–service must specify a valid name from the <strong>Data</strong>Service<br />
list registered to this Name<strong>Server</strong> as defined by your appServiceNameList entry in the<br />
broker properties file. If a default <strong>Data</strong>Service has been defined <strong>for</strong> your broker instance,<br />
you can omit this parameter and connect using the default service.<br />
6–3
Change language