Kbase 18685: WebSpeed 3.x Distributed Configuration
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/29/2009 |
|
Solution ID: 18685
GOAL:
How to set up a Webspeed distributed environment
FACT(s) (Environment):
WebSpeed 3.x
SYMPTOM(s):
Msngr: the specified service name does not exist or has a bad format. (5825)
WebSpeed error from messenger process (6019)
The Nameserver with which this messenger is associated is not running WebSpeed error from messenger process.(6019)
Name Server at Host localHost Port 5163 is not responsive. (8239)
Unable to access NameServer at host (localHost), port (5163) cs_status = (-4008)
Msngr: the specified service name does not exist or has a bad format. (5825): wsbroker1
FIX:
Components concerning this solution:
1) Webspeed Messenger
2) Transaction Server
3) NameServer
The NameServer provides location transparency and load balancing. This means the client does not (have to) know where the brokers are installed. Browsers connect to a specific messenger on a Web server. WebSpeed messengers and brokers are now required to register with a NameServer. When both the messenger and the broker register with the same NameServer, the browser is able to make a good connection.
When a controlling NameServer for a WebSpeed broker is changed, the messenger that is used for this broker should also be changed to point to that same NameServer. When the controlling nameserver for wsisa.dll or wsnsa.dll messenger is changed, the Web server must be stopped and restarted because the messengers are loaded persistently by the Web server.
In a distributed configuration, a NameServer replaces the Webspeed Version 2.x dispatcher functionality. Load balancing can be accomplished only when there is a license for the NameServer.
Unified brokers can support multiple services. Each broker registers with a NameServer and specifies what service(s) it supports. The NameServer can then perform load balancing according to the PriorityWeight property in the ubroker.properties file.
If there are no error messages in the browser, but the NameServer still cannot be reached, it could be that there is Network address translation (NAT), more than one IP Address, or more than one NIC card in use. Refer to Progress Solution 19720 for further information on these topics.