Starts the DataServer broker. To use the DataServer from a remote client, you must first start the broker. Once you start the broker, it can receive the client requests and spawn the DataServer.

Syntax

Operating system Syntax
Windows 
 _probrkr.exe -S service-name [ -H host-name ]
UNIX 
 _probrkr -S service-name [ -H host-name ]

Parameters

service-name
Specifies the name of the broker process service on the host machine.
host-name
Specifies the name of the machine where the DataServer broker is installed. The default value is the local host.

Notes

  • See Startup Command and Parameter Reference for more details on the Server Name (-S), Host Name (-H) startup parameters.
  • You can use any of the startup parameters with the PROBRKR command. See Startup Command and Parameter Reference for details.
  • You must start the remote broker in the same machine where your ODBC data source names (DSNs) are defined because the servers spawned by the broker inherit the setup of the environment from the broker. For example, set the environment variable MSSSRV to the name of the executable (including the path) of the DataServer for MS SQL Server. Be sure to set this variable on the host machine. Also, in the same environment, make sure you have set all MS SQL Server environment variables required to connect to the data source. See Configuring the DataServer for examples of required variables.
  • To set the Message Buffer Size (-Mm) startup parameter for the broker to a value different from the 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 and value that you are passing before you start the broker. This approach ensures that your value is recognized and therefore used by the broker when it starts. Only Windows clients must use this technique.
  • Start the broker on a server that is locally connected to the disk containing the data source.
  • Starting with OpenEdge 12.6, the Unix-based Probroker is no longer shipped with the setuid bit. In rare cases, certain operating environments may require granting elevated privileges to Probroker or the DataServers it spawns. For better security, Progress recommends granting such privileges through group authority rather than granting root user authority on the binary object.