Using the command-line interface to start multiple brokers

Installation and Configuration

Configuration : Starting and Running OpenEdge : Running OpenEdge clients and servers on a network : Starting multiple brokers using the same protocol : Using the command-line interface to start multiple brokers

Use the following commands to start two brokers that use TCP and start multiple servers each:

proserve db-name -S server-name -N network-type -H host-name -Mn n -Mpb n
proserve db-name -S server-name -N network-type -H host-name -Mpb n -m3

db-name

Specifies the database you want to start. If the database is not in the current directory, you must specify the full pathname of the database.

-S service-name

Specifies the database server or broker process service name. You must specify the service name in a TCP network.

-N network-type

Specifies the network protocol, which is TCP.

-H host-name

Specifies the machine where the database server runs.

-Mn n

Specifies the maximum number of remote client servers and login brokers that the broker process can start.

-Mpb n

Specifies the number of servers that the login broker can start to serve remote users. This applies to the login broker that is being started.

-m3

Starts the secondary login broker.

To start two brokers that use TCP and start four servers each, use the following commands:

proserve db -S demosv1 -N tcp -H myhost -Mn 9 -Mpb 4
proserve db -S demosv2 -N tcp -H myhost -Mpb 4 -m3

As the example shows, the -Mn value must be large enough to account for each additional broker and all servers. If you do not specify -Mpb, the value of -Mn becomes the default.

You must include the -m3 parameter with every secondary broker startup command. While the -Mpb sets the number of servers a broker can start, the -m3 parameter actually starts the secondary broker.

If you start multiple brokers, you should also run the Progress Watchdog process (PROWDOG). PROWDOG enables you to restart a dead secondary broker without shutting down the database server.