Database connections in PAS for OpenEdge
- Last Updated: January 16, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
The OpenEdge database network connection policy did not change in PAS for OpenEdge. Like the classic AppServer, it is one private network connection per ABL session in the multi-session agent. Therefore, the application code and PROMON monitoring are the same for both servers.
However, the self-service database connection policy changes considerably.
Self-service connections are a shared resource in PAS for OpenEdge. Each multi-session
agent creates a single self-service connection that appears in PROMON as its own user
connection. Therefore, each ABL session that executes with a database connection
parameter -db or that executes an ABL CONNECT statement shares the self-service connection from
its managing multi-session agent and shows up on PROMON with its own user connection.
Each ABL session user connection is specific to that session. A single ABL session user
connection does not bind the user connection of any other ABL session.
Two new Type values, specific to PAS for OpenEdge, are in the PROMON display:
SELF/PASA— A multi-session agent's shared self-service database connectionSELF/PASN— Individual ABL session users that share the multi-session agent's connection
SELF/PASA results in
disconnecting all ABL session users that were using the shared
self-service database connection, which causes all database connectivity to be
dropped.