Try OpenEdge Now
skip to main content
DataServer for Microsoft SQL Server
Configuring the DataServer : Configuring a remote DataServer : Configuring from the command line

Configuring from the command line

You can configure a remote DataServer broker process from the command line. You can use the _probrkr.exe executable or use the mssman.bat utility within OpenEdge Management or OpenEdge Explorer, the command line equivalent of using OpenEdge Management or OpenEdge Explorer.
Before you start the configuration tasks, make sure that you have installed your ODBC software and any data source-specific client software on your host machine. Also make sure that you have registered all of your data sources. See Configuring an ODBC driver and registering the data source for details.
To configure from the command line:
*When using the OpenEdge broker (_probrkr.exe), you set the environment variables described in this section from the command line using environment-variable commands at the DOS shell prompt.
*When using the mssman.bat utility within OpenEdge Management or OpenEdge Explorer, set the environment variables described in this section in the environment section of your broker properties file for the specific broker instance definition.
*You must set your environment variables in the same environment (DOS shell) from which you plan to run the DataServer.
The following table describes the environment variables that you must set.
Table 29. Environment variables for the remote DataServer
The pathname of the log file that OpenEdge uses to keep track of DataServer processes and error messages. By default, OpenEdge writes to %DSLOGDIR%\dataserv.lg where %DSLOGDIR% is resolved to directory path of the log file dataserv.lg.
The pathname of the OpenEdge server executable. This variable is required only when the DataServer is spawned using the OpenEdge broker (_probrkr.exe). When using mssman, this setting is satisfied by the srvrExecFile setting in the broker properties file.
The pathname of the broker executable. When using the OpenEdge broker (_probrkr.exe), set this variable on the host machine to the broker executable name. When using mssman.bat, this setting is satisfied by the broker instance definition in the broker properties file.
The pathname of your default OpenEdge startup (.pf) file.
To set the Message Buffer Size (-Mm) startup parameter for the broker to a value different from the 1024 default buffer size, you must set the PROSTARTUP environment variable equal to the path and name of the .pf file that contains the -Mm parameter.
This approach ensures that your value is recognized and therefore used by the broker when it starts. Only Windows clients must use this technique.
Note: If you use the command line utility and intend to set the -Mm startup parameter to a value other than 1024, you must use the .pf file with the PROSTARTUP variable set.
Used to generate unique log file name on the server with dataserv_pid.lg, where pid is the process-id of server. When set, the designated DataServerlog log file name becomes a root name. Can be disabled by unsetting the environment variable.
Once you have completely set up your environment, you can build the schema holder for your MS SQL Server database and connect using the client executable. See Creating a schema holder for instructions.
* The file
* Editing the file
* Validating content
* Configuring multiple brokers
* Using the NameServer