OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 6: Connecting the DataServer
Performing on the client
After you start the broker on the host machine from OpenEdge Management or
OpenEdge 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 OpenEdge Management or OpenEdge 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:
Or
-DataService none
-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 OpenEdge Management or OpenEdge 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 OpenEdge Management or
OpenEdge 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.
212 OpenEdge Data Management: DataServer for Microsoft SQL Server