Try OpenEdge Now
skip to main content
Developing AppServer Applications
Programming the AppServer : Accessing the connection ID

Accessing the connection ID

As described in ABL for programming AppServer procedures, OpenEdge creates a unique ID for each connection to an AppServer. For session-managed applications, there is a connection ID mechanism especially for an AppServer running in stateless operating mode. This is the SERVER-CONNECTION-ID attribute on the SESSION handle, a read-only CHARACTER attribute for which OpenEdge generates a unique value for each connection to a session-managed AppServer. For information on how the AppServer generates the value for a client connection ID, see the information on the AppServer connection-based model and physical connection IDs in OpenEdge Getting Started: Application and Integration Services.
For both session-managed and session-free applications, you can use the ClientContextId property on the Progress.Lang.OERequestInfo object to identify a single client context. This client context identifier can be used to identify a single user login session, especially for multiple AppServer sessions running in a stateless or state-free operating mode. By default, OpenEdge provides a globally unique value for the ClientContextId property that can also be managed by the application across multiple AppServer sessions.
For more information on using the SERVER-CONNECTION-ID, see Managing stateless connection context. For more information on using the ClientContextId property, see Managing state-free and stateless client context.