Kbase P104795: How is the default application service used with Webspeed brokers?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/08/2005 |
|
Status: Unverified
GOAL:
How is the default application service used?
GOAL:
Why do I see a default wsbroker1 listing under the Namserver status menu?
GOAL:
Why do I see a default asbroker listing under the Namserver status menu?
FIX:
The default application service is a entry in ubroker.properties file under the ubrokers section (defaultService=). When the value is set to 1( defaultService=1), the default application service is supported, as well as any other application services listed.
The Webspeed broker registers with the controlling Nameserver that supports the default application service. If the Nameserver receives a request from a Webspeed Messenger that does not specify an application service, the Nameserver directs the request to a WebSpeed Broker that supports the default application service.
By default the defaultService = is set to 0.
# Default properties for all unified broker instances
#
[UBroker]
infoVersion=9010
workDir=@{WorkPath}
srvrLogFile=@{WorkPath}\server.log
brokerLogFile=@{WorkPath}\broker.log
PROPATH=@{WinChar Startup\PROPATH};@{WorkPath}
initialSrvrInstance=5
minSrvrInstance=1
maxSrvrInstance=10
maxClientInstance=512
priorityWeight=0
registrationRetry=30
userName=
password=
defaultService=0
appserviceNameList=
autoStart=0
controllingNameServer=
srvrMinPort=3202
srvrMaxPort=3502
environment=
uuid=
brkrLoggingLevel=2
brkrLogAppend=1
srvrLoggingLevel=2
srvrLogAppend=1
srvrStartupTimeout=3