13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Syntax<br />

Parameters service–name<br />

PROBRKR command<br />

Non-Progress Explorer command line utilities <strong>for</strong> the <strong>Data</strong><strong>Server</strong><br />

Starts the <strong>Data</strong><strong>Server</strong> broker. To use the <strong>Data</strong><strong>Server</strong> from a remote client, you must first start<br />

the broker. Once you start the broker, it can receive the client requests and spawn the<br />

<strong>Data</strong><strong>Server</strong>.<br />

Operating<br />

system Syntax<br />

Windows _probrkr.exe -S service-name [ -H host-name ]<br />

Specifies the name of the broker process service on the host machine.<br />

host–name<br />

Specifies the name of the machine where the <strong>Data</strong><strong>Server</strong> broker is installed. The default<br />

value is the local host.<br />

Notes • See <strong>OpenEdge</strong> Deployment: Startup Command and Parameter Reference <strong>for</strong> more details<br />

on the <strong>Server</strong> Name (-S), Host Name (-H) startup parameters.<br />

• You can use any of the startup parameters with the PROBRKR command. See <strong>OpenEdge</strong><br />

Deployment: Startup Command and Parameter Reference <strong>for</strong> details.<br />

• You must start the remote broker in the same machine where your ODBC data source<br />

names (DSNs) are defined because the servers spawned by the broker inherit the setup of<br />

the environment from the broker. For example, set the environment variable MSSSRV to the<br />

name of the executable (including the path) of the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong>. Be sure<br />

to set this variable on the host machine. Also, in the same environment, make sure you<br />

have set all MS <strong>SQL</strong> <strong>Server</strong> environment variables required to connect to the data source.<br />

See Chapter 5, “Configuring the <strong>Data</strong><strong>Server</strong>,” <strong>for</strong> examples of required variables.<br />

• To set the Message Buffer Size (-Mm) startup parameter <strong>for</strong> the broker to a value different<br />

from the default buffer size of 1024, you must set the PROSTARTUP environment variable<br />

equal to the path and name of the .pf file that contains the -Mm parameter and value that<br />

you are passing be<strong>for</strong>e you start the broker. This approach ensures that your value is<br />

recognized and there<strong>for</strong>e used by the broker when it starts. Only Windows clients must use<br />

this technique.<br />

• Start the broker on a server that is locally connected to the disk containing the data source.<br />

B–11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!