Try OpenEdge Now
skip to main content
Configuring NameServers : NameServer configuration and administration

NameServer configuration and administration

You can optionally use the NameServer to mediate client connections for instances of OpenEdge Unified Broker products that you configure with OpenEdge Management or OpenEdge Explorer. The Unified Broker products include all OpenEdge resources that are managed through the AdminServer. For more information on the Unified Broker products and the AdminServer, see OpenEdge Getting Started: Installation and Configuration.
When you choose to use the NameServer, each component instance registers with only one NameServer, which is known as the instance's controlling NameServer. Each time an instance starts up, it registers with its controlling NameServer by sending its location and other configuration information. The NameServer uses this information to help resolve client connection requests. A particular NameServer can accept registrations from any number of instances, including instances of more than one type of component.
Depending on the way you configure and use the OpenEdge product, you can decide to specify a controlling NameServer to handle client connection requests. For example, your configuration might be simple and not require the location transparency the NameServer provides, or it might be more complex and, therefore, dependent on this and other NameServer features.
The OpenEdge Unified Broker products that you can optionally choose to register with the NameServer include:
*AppServer Internet Adapters
*DataServers for Oracle and MS SQL Server configured to use the NameServer
*SonicMQ Adapters
*WebSpeed Transaction Servers
* NameServer features
* Working with the NameServer
* NameServer as an optional client connection request handler
* Local and remote NameServers