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.
Configuring the <strong>Data</strong><strong>Server</strong><br />
5–10<br />
Table 5–2 describes the environment variables that you must set.<br />
Table 5–2: Environment variables <strong>for</strong> the remote <strong>Data</strong><strong>Server</strong><br />
DSLOGDIR<br />
(Optional)<br />
Variable Description<br />
Once you have completely set up your environment, you can build the schema holder <strong>for</strong> your<br />
MS <strong>SQL</strong> <strong>Server</strong> database and connect using the client executable. See the “Creating a schema<br />
holder” section on page 5–15 <strong>for</strong> instructions.<br />
The ubroker.properties file<br />
The pathname of the log file that <strong>OpenEdge</strong> uses to keep<br />
track of <strong>Data</strong><strong>Server</strong> processes and error messages. By<br />
default, <strong>OpenEdge</strong> writes to %DSLOGDIR%\dataserv.lg<br />
where %DSLOGDIR% is resolved to directory path of the log<br />
file dataserv.lg.<br />
MSSSRV The pathname of the <strong>OpenEdge</strong> server executable. This<br />
variable is required only when the <strong>Data</strong><strong>Server</strong> is spawned<br />
using the <strong>OpenEdge</strong> broker (_probrkr.exe). When using<br />
mssman, this setting is satisfied by the srvrExecFile<br />
setting in the broker properties file.<br />
PROBRKR<br />
(Optional)<br />
The pathname of the broker executable. When using the<br />
<strong>OpenEdge</strong> broker (_probrkr.exe), set this variable on the<br />
host machine to the broker executable name. When using<br />
mssman.bat, this setting is satisfied by the broker instance<br />
definition in the broker properties file.<br />
PROSTARTUP The pathname of your default <strong>OpenEdge</strong> startup (.pf) file.<br />
To set the Message Buffer Size (-Mm) startup parameter <strong>for</strong><br />
the broker to a value different from the 1024 default buffer<br />
size, you must set the PROSTARTUP environment variable<br />
equal to the path and name of the .pf file that contains the<br />
-Mm parameter.<br />
This approach ensures that your value is recognized and<br />
there<strong>for</strong>e used by the broker when it starts. Only Windows<br />
clients must use this technique.<br />
Note: If you use the command line utility and intend to set<br />
the -Mm startup parameter to a value other than 1024, you<br />
must use the .pf file with the PROSTARTUP variable set.<br />
UNIQUE_DSLOG Used to generate unique log file name on the server with<br />
dataserv_.lg, where pid is the process-id of server.<br />
When set, the designated <strong>Data</strong><strong>Server</strong>log log file name<br />
becomes a root name. Can be disabled by unsetting the<br />
environment variable.<br />
When using the Progress Explorer administration framework, you configure the <strong>Data</strong><strong>Server</strong> <strong>for</strong><br />
MS <strong>SQL</strong> <strong>Server</strong> by editing the <strong>OpenEdge</strong>-install-dir\properties\ubroker.properties<br />
file. This file stores configuration definitions <strong>for</strong> instances of many <strong>OpenEdge</strong> products. For a<br />
complete list of products and a detailed discussion of the Unified Broker Framework, see<br />
<strong>OpenEdge</strong> Getting Started: Installation and Configuration.