Kbase 22063: Webspeed 3.1D: Configuring with NameServer is Now Optional
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/3/2002 |
|
SUMMARY:
This Solution applies to WebSpeed 3.1D. It clarifies how to configure without the NameServer option for the WebSpeed broker.
EXPLANATION:
In the WebSpeed 3.1D release, using the NameServer is optional. In earlier versions, the WebSpeed Messenger requires connecting to a server instance using a NameServer.
Reasons why you might want to eliminate the NameServer from your configuration:
A) The NameServer allows for location transparency and load balancing.
Simple or static configurations might not require those features.
B) The communications protocol employed by the NameServer is the User
Datagram Protocol (UDP). Some sites have restrictions that
prohibit the use of UDP.
SOLUTION:
Concerning how to configure this feature, the documentation says:
"If you choose not to use the NameServer, you will need to do the following:
1. Configure your server in Progress Explorer to indicate that the server should not register with a NameServer. In Progress Explorer, deselect the Connect Using NameServer check box in the properties dialog for WebSpeed Messenger. You must also deselect the Register With NameServer check box in the properties dialog for the WebSpeed Broker.
2. Connect clients directly to the server by specifying the server's TCP/IP host and port. There is a new connection parameter DirectConnect (-DirectConnect) that specifies that no NameServer should be used when the client connects to the server."
This is not completely accurate; users only need to accomplish step 1 to use this feature. -DirectConnect is an AppServer connection parameter which will cause a GPF when used as a WebSpeed agent startup parameter.
References to Written Documentation:
Version 3.1D WebSpeed Installation and Configuration Guide