OpenEdge Management and OpenEdge Explorer: Configuration

Working with the NameServer
NameServer configuration and administration
To work with a NameServer instance, select the NameServer folder from the management
console's list pane. There is one pre-defined default NameServer (NS1).
You can perform the following NameServer actions:
• Configuring a NameServer
• Editing a NameServer configuration
• Creating a NameServer
• Starting a NameServer
• Stopping a NameServer
• Deleting a NameServer
• Configuring fault tolerance and load balancing
• Viewing the status of a NameServer
• Handling UDP and firewall issues
• Viewing the NameServer log file
NameServer as an optional client connection request
handler
Configuring a NameServer to work with the AppServer, a DataServer, a SonicMQ Adapter, or
a WebSpeed Transaction Server is optional. Depending on the way you configure and use the
OpenEdge product, you can decide if you want to specify a controlling NameServer. For
example, your configuration might be simple and not require location transparency or load
balancing, or it might be more complex and, therefore, dependent on those features.
Local and remote NameServers
Before configuring a NameServer, you must know the network location where it is to run. For
any network host, you can configure two types of NameServer instances:
• Local — An instance that runs locally on the host where it is defined
• Remote — An instance that references a NameServer that is defined and runs on a
machine that is remote from the host where the reference is defined
The purpose of defining a remote NameServer instance is to provide an easy way of having
multiple Unified Broker products refer to a controlling NameServer that runs on another
machine. You cannot start, stop, obtain status, or modify any properties of a remote NameServer
instance other than the host name and port number that it references.
4–3