Kbase P180457: Is every connection to a secondary login broker a network connection?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/12/2011 |
|
Status: Unverified
GOAL:
Can clients connect via shared memory to a secondary login broker?
GOAL:
Is is possible to have clients connect to a secondary login broker via shared memory?
GOAL:
Can a client connect to a secondary login broker via shared memory?
GOAL:
Is every connection to a secondary login broker a network connection?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
OpenEdge Category: Database
OpenEdge Database Category: Configuration
FIX:
Yes. Every connection to the secondary broker is a network connection because they are communicating via a port (-S). A shared memory connection does not make use of the -S parameter. Therefore they are local / shared memory clients. They can be your clients/WebSpeed Brokers/Agents and AppServer Brokers/Agents. The dependency is where you have these clients running and how they access the database as well as where your database resides.
If you start a secondary broker, then the only way to access that secondary broker is via the -S parameter. If your clients or Web speed or AppServer brokers are on the same local machine, there is no need to specify the -H parameter because they will connect to anything listening on the port being specified with the -S parameter. But if they are making use of the -S parameter, they are still communicating via a port and therefore they are still remote clients.
If your clients/WebSpeed Brokers/Agents and AppServer Brokers/Agents are on a different physical machine, then you need to specify the -H hostname and -S port/service name. This is so that they know to bind to the appropriate port on the specified host machine.