OpenEdge Data Management: DataServer for Microsoft SQL Server

Configuring a remote DataServer
4. From the console’s left pane, select the MSS DataServer folder and
double-click. The list of existing DataServer brokers for MS SQL Server appears
in the right pane.
5. Select the DataServer instance whose properties you want to create or edit, and
click Configuration so that the DataServer properties appear.
6. Click Edit.
Note: The DataServer for MS SQL Server installation provides one predefined
DataServer Broker (mssbroker1) and one predefined NameServer (NS1).
(The NameServer is located in the NameServer folder.) Each broker is
referred to as an instance. See the OpenEdge Management or OpenEdge
Explorer online help for more information. You can use these predefined
components as a starting point for creating and configuring additional
DataServer Brokers, and, if needed, NameServers. (See OpenEdge
Getting Started: Installation and Configuration for information about the
NameServer’s role in a configuration.).
7. Configure the DataServer broker by setting the Broker properties, Server
properties and Environment Variables. For details on these settings, see the
OpenEdge Management or OpenEdge Explorer online help.
Proceed to Step a to use the DataServer for MS SQL Server broker instance with
a controlling NameServer (as provided by a default Data Service). Otherwise,
proceed to Step b to use the broker instances or without the NameServer (using
the -DirectConnect parameter option):
a. To use the controlling NameServer to manage your broker instances, use the
Data Service (This is the default and recommended option. For syntax and
examples, see the “Connecting to a MS SQL Server DataServer broker using
the NameServer” section on page 188.). As a result, the DataServer client’s
initial connection is to the NameServer.
b. To connect the DataServer directly to the broker instance, do one of the
following:
• Set the -DataService value to none in the connection parameters of
your schema holder.
If you plan to always use a -DataService value of none, remove the
controlling NameServer from your broker instance definition.
• Add the -DirectConnect parameter to override your -DataService
parameter.
See the “Starting and stopping a broker process from OpenEdge
Management/OpenEdge Explorer and connecting a client” section on page 211
for more information about connecting the DataServer to the NameServer and the
broker.
OpenEdge Data Management: DataServer for Microsoft SQL Server 187