Progress
Version 9
Product Update Bulletin
Overview Of the Optional NameServer
The Optional NameServer accommodates some configurations that do not require the NameServer as well as configurations that do not use the User Datagram Protocol (UDP). In Progress versions earlier than Version 9.1D, the NameServer is required, not optional, and as a result, users had to use UDP.
Using the NameServer provides location transparency and load balancing capabilities to servers that use it, namely AppServer, WebSpeed Transaction Server, Sonic Adapter, and DataServers. (Unlike other servers, DataServers only use the NameServer when they are configured and started up using Progress Explorer.)
In versions earlier than Progress Version 9.1D, all servers that support the NameServer do so as a required component. That is, as part of configuring the component using Progress Explorer, a controlling NameServer must be specified. A client that wants to access the server must specify the appropriate connection parameters such that the request to locate the required server is sent to the specified NameServer.
There are two benefits to making the NameServer optional:
- Some configurations are simple and static. They do not need location transparency or load balancing. For these configurations, taking advantage of the optional NameServer means that they have less to configure and manage.
- Since the NameServer uses UDP and some customers have restrictions that prohibit using UDP, using the optional NameServer eliminates this dependency.
For customers who want to take advantage of the optional NameServer and choose not to use the NameServer in Progress Version 9.1D, they need to do the following:
- Configure their server in Progress to indicate that the server should not register with a NameServer. See "Administration" in this bulletin for more information about using Progress Explorer.
- Connect their 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.NOTE: A given server should be configured to not register with the NameServer only if all clients will not be using the NameServer to connect to the server. You should not have a server simultaneously support both clients that use the NameServer and clients that do not use the NameServer. Either all clients should use the NameServer or all clients should not use the NameServer.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |