richieasir
Member
Hi,
Could You Please Explain In Detail About '-mn','-mpb','-m3'
Waiting For Your Reply
Could You Please Explain In Detail About '-mn','-mpb','-m3'
Waiting For Your Reply
Explain Pls!!
- Thread starter richieasir
- Start date
richieasir
Member
Hi,
they haven't mentioned in detail about -Mn n,-Mpb n,-M3.
-Mpb
-m3Starts the secondary login broker.
Eg:
explain in detail please.
they haven't mentioned in detail about -Mn n,-Mpb n,-M3.
-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
Eg:
proserve db -S demosv1 -H myhost -Mn 9 -Mpb 4
proserve db -S demosv2 -H myhost -Mpb 4 -m3explain in detail please.
richieasir
Member
hi
i want to know abt broker as well as secondary login brokers...their characteristics etc...... relation between -mn,-mpb,-m3
hw it has been used in the above Eg....(pls explain the example)
i want to know abt broker as well as secondary login brokers...their characteristics etc...... relation between -mn,-mpb,-m3
hw it has been used in the above Eg....(pls explain the example)
TomBascom
Curmudgeon
A broker is a "listener". It listens for connection requests ("logins") of a certain type (4gl, SQL or both if the type is not specified) on the port specified by -S.
When a request is received the broker looks for an available server of the needed type. If it cannot find one it spawns a new one. It then tells the remote client and the server what ports they are going to communicate on and gets out of the way.
The various parameters control the total number of servers (-Mn) how many servers a broker will spawn (-Mpb), how many clients can connect to each server (-Ma), how clients are assigned to servers (-Mi 1 = round robin), what sort of servers get spawned (-ServerType) and what sort of broker it is (-m3).
A typical basic database startup with remote connections enabled would be more like:
This would allow up to 50 remote connections out of a total of 60 (-n). (You need a few extras for the broker, APWs, AIW, BIW, WDOG and so forth.) This broker is a "both" broker.
Alternatively you might want to start distinct 4GL and SQL brokers. To do that:
This will start the database and allow 25 remote 4gl connections. The second "proserve" then starts a secondary broker that supports 25 SQL connections.
When a request is received the broker looks for an available server of the needed type. If it cannot find one it spawns a new one. It then tells the remote client and the server what ports they are going to communicate on and gets out of the way.
The various parameters control the total number of servers (-Mn) how many servers a broker will spawn (-Mpb), how many clients can connect to each server (-Ma), how clients are assigned to servers (-Mi 1 = round robin), what sort of servers get spawned (-ServerType) and what sort of broker it is (-m3).
A typical basic database startup with remote connections enabled would be more like:
Code:
proserve dbname -S myService -Ma 5 -Mi 1 -n 60 -Mn 10 -B 100000 -spin 3000This would allow up to 50 remote connections out of a total of 60 (-n). (You need a few extras for the broker, APWs, AIW, BIW, WDOG and so forth.) This broker is a "both" broker.
Alternatively you might want to start distinct 4GL and SQL brokers. To do that:
Code:
proserve dbname -S 4glService -ServerType 4GL -Mpb 5 -Ma 5 -Mi 1 -n 60 -Mn 10 -B 100000 -spin 3000
proserve dbname -S SQLService -ServerType SQL -Mpb 5 -Ma 5 -Mi 1 -m3This will start the database and allow 25 remote 4gl connections. The second "proserve" then starts a secondary broker that supports 25 SQL connections.