Kbase 20662: When Does location equal 'remote' or 'local' within ubroker.properties
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
When to set component location to "remote" or "local" when working with distributed WebSpeed configuration?
GOAL:
How to set "location" entry in ubroker.properties file?
FACT(s) (Environment):
WebSpeed
WebSpeed 3.x
Progress 9.x
FIX:
Usally in a distributed configuration, the Messenger and Name Server reside on one machine and the webspeed broker is installed onto another backend machine. At times, the messenger and the Name Server can not be installed into the same installation directory (location), hence will not share a ubroker.properties file. In this event, the LOCATION of the components are not local to each other but rather remote. Setting the location to "local", is incorrect.
The "location" field in the NameServer area of the ubroker.properties file does not represent the actual or the physical location of the NameServer. It indicates whether the NameServer (or that component) is being configured in the same ubroker.properties file.
Remember to set both sections in their respective ubroker.properties files for each installation appropriately.
The NameServer section for the Messenger's ubroker.properties file should appear as follows:
[NameServer.NS1]
srvrLogFile=$WRKDIR/NS1.ns.log
environment=NS1
autoStart=0
hostName=localHost
location=remote <========
portNumber=XX
(The location section should be set to "remote".)
The NameServer section of it's own ubroker.properties File should appear as follows:
[NameServer.NS1]
srvrLogFile=$WRKDIR/NS1.ns.log
environment=NS1
autoStart=0
hostName=localHost
location=local <========
portNumber=XX
(The location section should be set to "local".)