Kbase P105087: What does "priority weight" for Unified broker mean?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/9/2006 |
|
Status: Unverified
GOAL:
What does "priority weight" for Unified broker mean?
GOAL:
How is load balancing achieved by AppServer brokers sharing the application service?
GOAL:
How is load balancing achieved by WebSpeed brokers sharing the application service?
GOAL:
Where is priority weight set for load balancing with Unified broker?
GOAL:
Where is priority weight set for load balancing with AppServer broker?
GOAL:
Where is priority weight set for load balancing with WebSpeed broker?
GOAL:
Where is priority weight set for load balancing with DataServer broker?
GOAL:
How is the work load distributed among AppServer brokers sharing the same application service and NameServer?
GOAL:
How is the work load distributed among WebSpeed brokers sharing the same application service and NameServer?
FIX:
The load balancing or distribution is determined by the priority weight that is assigned to the AppServer broker instances. The default is zero (0). Setting all AppServer brokers to the same value will evenly distribute the load. If all brokers have the value of zero (0), the default, the load will be evenly distributed over a period of time. It will NOT go in a round-robin fashion for each client request.
A higher priority value given to one broker will give that broker higher priority. Setting a value for some brokers and leaving one broker at zero priority weight means the broker set at zero will be excluded from the load distribution process.
The range of values is 1 to 100 with 100 being the highest priority. The default is 0. Priority weight is required. It may be left at the default value of zero, but it may not be left blank.
Priority weight is set in the ubroker.properties file under the UBroker section. The ubroker.properties file may be edited manually or, as preferred, using Progress Explorer Tool.
To set the priority weight for AppServer brokers using Progress Explorer:
1. Select the AppServer broker instances
2. Click on Properties
3. Click on Broker
4. Select Advanced.
Below is the UBroker section from the ubroker.properties file showing the priority weight.
[UBroker]
appserviceNameList=
autoStart=0
autoTrimTimeout=1800
brkrLogAppend=1
brkrLogEntries=0
brkrLoggingLevel=2
brkrLogThreshold=0
brokerLogFile=@{WorkPath}\broker.log
collectStatsData=0
connectingTimeout=60
controllingNameServer=
defaultService=0
description=
environment=
flushStatsData=255
hostName=
infoVersion=9010
initialSrvrInstance=5
jvmArgs=@{JAVA\JVMARGS}
maxClientInstance=512
maxSrvrInstance=10
minSrvrInstance=1
password=
priorityWeight=0
PROPATH=@{WinChar Startup\PROPATH};@{WorkPath}
registerNameServer=1
registrationMode=Register-IP
registrationRetry=30
requestTimeout=15
srvrLogAppend=1
srvrLogEntries=0
srvrLogFile=@{WorkPath}\server.log
srvrLoggingLevel=2
srvrLogThreshold=0
srvrMaxPort=3502
srvrMinPort=3202
srvrStartupTimeout=3
userName=
uuid=
workDir=@{WorkPath}