Kbase P66192: Can a specific client session (userID or node) be identified via the 9.1D Progress AppServer log fil
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/8/2005 |
|
Status: Verified
GOAL:
Can a specific client session (userID or node) be identified via the 9.1D Progress AppServer log files or any other method?
FACT(s) (Environment):
UNIX
FACT(s) (Environment):
Windows
FACT(s) (Environment):
Progress 9.1D
FIX:
In earlier Progress versions, the connection-id was logged automatically in the AppServer log files for each entry written at verbose logging level. This made it possible to see which AppServer process executed each request. Unfortunately that functionality was dropped.
The connection-id was designed for this purpose. It is generated by the AppServer broker when a user connects. It is an accessible attribute from the Progress 4GL on both the client and AppServer.
As a workaround, the Progress 4GL "Activate Procedure" can now be used to fetch and log the connection-id attribute. If this development process hasn't been completed, specific client sessions (userID's or nodes) can not be identified.
To learn more about the Activate Procedure please refer to the "Progress Building Distributed Applications Using the Progress AppServer" manual.