Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server

> ## Starting and stopping a broker process from the Progress Explorer and connecting a client

> You can use the Progress Explorer to administer the server module (`_msssrv.exe`) of the DataServer in Windows.

> ##### In the Windows host

> Before you attempt to start the DataServer in the Explorer, be sure that you have configured it completely. After starting the broker from the Progress Explorer, you start your OpenEdge client as you would in any remote DataServer configuration.

> To start and stop the DataServer from the Explorer, see the Progress Explorer online help.

> ##### On the client

> After you start the broker on the host machine from the Progress Explorer, you can connect your UNIX or Windows client. Use the same parameters that you would use to connect to the schema holder and MS SQL Server database in a standard ProBroker configuration. In addition:

> - Include the `-Dsrv` `SVUB,1` parameter. This parameter allows you to connect to the broker administered by the Explorer.

> - Include the `-DataService` `data–service` parameter to connect through a NameServer to the broker. The value for `data–service` must specify a valid name from the DataService list registered to this NameServer as defined by your `appServiceNameList` entry in the broker properties file. If a default DataService has been defined for your broker instance, you can omit this parameter and connect using the default service.

> For diagnostic purposes only, it is acceptable to bypass the NameServer connection and connect directly to the broker instance. To do this, specify the reserved DataService name “none” or add the `-DirectConnect` parameter as follows:

>     -DataService none

> Or

>     -DirectConnect

> - Set the `-S` parameter to one of the following:

> - The port number assigned to the controlling NameServer (when the `-DataService` value is not “none”) or the port number of the broker instance that you started in the Explorer (when the `-DataService` value is “none”).
> - The service name in your `services` file whose associated port matches the port of the controlling NameServer (when the `-DataService` value is not “none”) or the broker instance that you started in the Explorer (when the `-DataService` value is “none”).
> - Set the `-H` parameter to the name of the machine where the NameServer and/or broker instance are running.

> If you do not set the required `-Dsrv` `SVUB,1` and optional `-DataService` `data–service` connection parameters as described in this section, the client is assumed to be configured for a standard OpenEdge broker and the `-H` and `-S` parameters are used to locate a ProBroker executable on the appropriate host machine. By setting the `SVUB` parameter on, you redirect the `-H` and `-S` parameters to locate the appropriate NameServer and/or broker on the host machine. The following example illustrates how to use these connection parameters for a client that connects to a NameServer:

>     CONNECT mssholder -db mssdemo -dt MSS -U bob -P bobpass -H host1
>     -S mssport -DataService mssbroker1 -Dsrv SVUB,1.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095