Kbase P4552: Setting up distributed WebSpeed Config; Connecting WS Msngr to NameServer & WS Broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
How to set up a Webspeed distributed environment
GOAL:
Msngr: the specified service name does not exist or has a bad format. (5825)
GOAL:
WebSpeed error from messenger process (6019)
GOAL:
The Nameserver with which this messenger is associated is not running WebSpeed error from messenger process.(6019)
GOAL:
Name Server at Host localHost Port 5163 is not responsive. (8239)
GOAL:
Unable to access NameServer at host (localHost), port (5163) cs_status = (-4008)
GOAL:
Msngr: the specified service name does not exist or has a bad format. (5825): wsbroker1
GOAL:
How to set up a Distributed WebSpeed Configuration?
GOAL:
Distributed WebSpeed Configuration.
GOAL:
How to configure WebSpeed to have Messenger on one server and NameServer and Broker on a separate server?
GOAL:
How to configure Standalone Webspeed messenger?
GOAL:
How to configure standalone messenger?
GOAL:
How to setup standalone webspeed messenger?
GOAL:
How to setup standalone messenger?
FACT(s) (Environment):
WebSpeed 3.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
Distributed Environment
a) WebServer & Messengers (machine A).
b) NameServer & Broker (machine B).
In a name server environment, the key to distributed configuration is for the messenger and the broker all resolve to the same name server. For example, the broker needs to register with a Name server called "NS1", then the messenger needs to access the same name server to be able to locate the information for the broker. the goal is for the messenger to be able to get broker information so it could connect to the broker later.
In a non name server environment (direct connect), the messenger configuration points directly to the broker.
Machine A
1. In the ubroker.properties files change the definition of the NameServer "NS1" as follows:
[NameServer.NS1]
location=remote
hostName={IP or hostName of machine B}
portNumber=(TCP port of NameServer.NS1 on machine B}
autoStart=0
2. The Messenger is currently setup to use NameServer.NS1 as the controlling Name Server:
[WebSpeed.Messengers]
controllingNameServer=NS1
This will allow the Messengers to connect to "NS1" on machine B. Please note if another NameServer is being used, please specify the correct NameServer.
Machine B:
The broker also has its controlling name server defined as NS1 which is local to the machine.
1. Start the AdminServer:
2. Start the instance of the NameServer
Note: If the attribute for the NameServer (on machine B) has been set to autoStart=1, then there is no need to start the instance. Here there NameServer is startedautomatically when the Adminserver is started.
3. Start an instance of a WebSpeed Broker