Try OpenEdge Now
skip to main content
Developing AppServer Applications
Connecting to AppServers Using a URL : Connecting over an intranet : Connecting through a NameServer

Connecting through a NameServer

When you connect over a company intranet using a NameServer, the NameServer process coordinates access to multiple AppServers. Each AppServer identifies the application procedures it supports using an application service name, which it registers with a particular NameServer. The AppServer connection parameter provides the network address of a NameServer and the name of an application service. The specified NameServer locates an AppServer that supports the specified application service and provides the network address of that AppServer to the client. The client then connects your application to this AppServer. Using the NameServer also provides location transparency and load balancing capabilities for an AppServer.
This is the URL syntax for connecting an AppServer (or BrokerConnect) through a NameServer over an intranet using the AppServer protocol (ignore line breaks):
The client uses a NameServer to connect to the AppServer.
The client uses a NameServer to connect to an Secure Sockets Layer (SSL)-enabled AppServer as an SSL client. When the NameServer provides an SSL connection to the client, the communications between the client and NameServer is in clear text (no SSL encryption) because the NameServer only passes a connection to the client and no application data is broadcast that can be intercepted. For more information on using an SSL-enabled AppServer, see the sections on using SSL in Design and Implementation Considerations.
TCP/IP host address or host name of the NameServer that holds the service registration.
TCP/IP port address for the NameServer specified with name-server-port.
Name of the application service (AppServer or BrokerConnect).
For example, the following three URLs connect to a warehouse inventory service or a financial portfolio management service through an OpenEdge NameServer. In the first example, the NameServer is located at the default UDP port, 5162; in the second, at a non-standard UDP port, 4099; and in the third, an SSL connection is established, as shown: