Before you start configuring the secondary login broker (-m3), you must set few parameters. These parameters include defining:
  • The total number of remote servers.
  • The total number of users (processes) that can connect concurrently to the database.
  • The type of servers that each login broker starts.
  • The number of remote users connected to a server.

Define the total number of remote servers (-Mn)

Define the total number of remote servers for the database specified by the -Mn parameter using the formula:

-Mn = Maximum ABL servers (-Mpb) + maximum SQL Servers (-Mpb) + number of Secondary Login Brokers (-m3)

The extra server is needed because each additional login broker (-m3) uses an entry on the server list, so add 1 for each broker started with the -m3 parameter.

Define the total number of users (processes) that can connect concurrently to the database (-n)

This parameter represents the maximum number of users and processes that connect concurrently to the database, including (but not limited to) PROMON sessions, APWs, BIWs, AIWs, WDOG, AIMGT, RFUTIL (for AI handling), background writers, batch jobs, self-service, and remote user connections.

Ensure that these values are balanced, so that the following is true for all login brokers: 
-n >= sum(-Mpb x -Ma)

Define the type of servers that each login broker will start (-ServerType)

The value can be 4GL, SQL, or Both.
Value specification Description
4GL The login broker supports ABL servers only.
SQL The login broker supports SQL servers only.
Both The login broker supports both ABL and SQL servers.

If OpenEdge Management or OpenEdge Replication is used, then the ABL Broker is required to be started as the primary login broker for the database, so the value of -ServerType needs to be either 4GL or Both.

Define the number of remote users connected to a server (-Mi)

This database broker startup parameter specifies the number of remote users connected to a server before the broker spawns another server. For the SQL server, it is recommended to set the -Mi parameter to the same value as the -Ma parameter to reduce memory consumption if all the remote servers are not needed.

If performance is an issue test set -Ma for SQL to 5 and -Ma for ABL to 10. These are starting recommendations you can adjust to achieve the desired resource allocation. When the database is shutdown, all login brokers are terminated as part of the shutdown process.

To configure database startup parameters, use the OpenEdge Explorer tool if databases are managed by the AdminServer or manually add each parameter to the database startup scripts.