Kbase P6234: How to connect to the AppServer without the NameServer ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/30/2006 |
|
Status: Verified
GOAL:
How to connect to the AppServer not using the NameServer.
GOAL:
How to deploy without the NameServer.
FACT(s) (Environment):
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
FIX:
Starting with the Progress 9.1D it is possible to connect to the AppServer without using the 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.
To connect to the AppServer without using the NameServer you can use the explicit or URL specification in the connection parameters.
The connection string using the NameServer looks like:
-AppService appservice -H nameserverhost -S nameserverport
The connection string without the NameServer looks like:
-DirectConnect -H appserverhost -S appserverport
Example for the explicit specification of connection parameters:
lRet = hAS:CONNECT("-H localhost -S 3090 -DirectConnect").
Example for the URL specification of connection parameters:
lRet = hAS:CONNECT("-URL AppServerDC://localhost:3090").
If the DirectConnect parameter is specified, or AppServerDC protocol used, then the AppService parameter is ignored.
A given AppServer 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.