You can start multiple brokers that use the same protocol. The -Mn parameter and the Maximum Servers per Broker (-Mpb) parameter, determine the number of servers a broker can start. In addition, you can use OpenEdge Explorer or OpenEdge Management to manage and configure server groups.
Use the following commands to start two brokers that use TCP and start multiple servers each:
proserve db-name -S service-name -H host-name -Mn n -Mpb n proserve db-name -S service-name -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.
-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.
For example, you would use the following commands to start two brokers that use TCP and start four servers each:
proserve db -S demosv1 -H myhost -Mn 9 -Mpb 4
proserve db -S demosv2 -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 parameter 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 Watchdog process (PROWDOG). PROWDOG enables you to restart a dead secondary broker without shutting down the database server. For more information on PROWDOG, see PROWDOG command.
