Kbase 19968: How to set up a secondary login broker to attend SQL-92 connections for Progress 9.1C and below
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
How to set up a secondary login broker for SQL-92 connections for Progress 9.1A, 9.1B and 9.1C
GOAL:
Creating a secondary login broker for SQL-92
GOAL:
How to create a secondary login brokers
GOAL:
How to spawn multiple brokers for a database
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.0x
Progress 9.1A
Progress 9.1B
Progress 9.1C
FIX:
The solution applies to Progress 9.0x, Progress 9.1A, 9.1B and 9.1C. A secondary login broker is used to address following issues which cannot be solved by using a single broker:
The need to establish the maximum number of remote 4GL and SQL-92 connections.
The need to allocate a specific pool of remote servers for 4GL (_mprosrv) and SQL-92 connections (_sqlsrv2).
The need to specify a different range of TCP/IP ports for SQL-92 remote servers.
The exhaustion of remote server caused by extra SQL-92 connections.
To configure a second login broker first define the total number of remote servers that the database will use. Use the formulas below to calculate the number of servers for the database (the value for the parameter -Mn) and the maximum number of connected processes ( users) :
-Mn = Max. 4GL servers + Max. SQL-92 servers + number of Secondary Login Brokers
-n = includes all local users, remote users, background writers (APWs, BIWs, and AIWs), PROWDOG processes, PROMON sessions, plus 1 for the secondary login broker.
For versions 9.1C and prior:
- The maximum number of SQL-92 servers is the maximum number of SQL-92 client.
- Remote SQL-92 servers can handle only one connection at a time.
- The primary broker has to be used for SQL-92 connection, because the polling feature of the SQL-92 servers is only active for the primary broker.
Configure the startup parameters on the database use the Progress Explorer tool or add the parameters to the database startup command.
To use the Explorer tool:
1. At database configuration (defaultConfiguration), select Properties