- User – This corresponds to the rich client (Ax32.exe) i.e.
the type User is the real user logged in into the AX client.
- Worker – This session type is overloaded to represent different session types but it is primarily seen in the context of the Business Connector. When BC is used to connect to an AOS, 2 sessions are initially created. The Worker session type corresponds to the main session that is used to represent the BC process. Each time a Logon related method is called a Business Connector session is created, when LogOff is called then the Business Connector session type is removed from the AOS memory and in the database. But the Worker session will be present as long as the BC process is active. This is the reason why there are 2 sessions shown in the Online users form when connecting using BC. It is possible that a person itself logged out from AX, but the worker session has its own alive state. This session type is indicating that e.g. a connection with SSRS was created on behalf of the user. The alerts feature creates threads for each users that has an alert rule in place, and they appear as worker sessions as well.
- Business Connector – This is used to represent the session that is
established when the Logon or LogonAs methods are called using the
Business Connector (BC).
- Web user – that is created when using EP is actually a Worker session inside the AOS but it is represented as a Business Connector session in the database because of the way licenses are counted for EP sessions. One thing to note is that the web user sessions are transient in nature because EP uses session caching and the web user sessions have a very short lifetime as they often map to web page based requests.
useful links:
No comments:
Post a Comment