Hello there,
Am trying to find the list of users who are currently logged into the Content Server application, in a livereport.
Any pointers ?
Thanks,
Arun
Hi Arun,
Content server don't keep the current user details in DB as per I know. But in every login and logout event Content server stores the details in DAuditNew table.
You can try to get the login users details depending on the logon time.
Although the user session is active or not, you will not be identify from that data.
Let me know if this helps you or not.
Thanks.
Thanks Abir.
Just wondering how "func=admin.threadstatus&clean", for instance is able to fetch the user transaction details. Using the same logic, should'nt the currently logged in user info be retrievable?
Hopefully someone is able to shed some light on the available options.
I have a LiveReport I created to see who has logged in based on a date range:
select distinct d.PerformerID, (select k.firstname ||' '|| k.lastname from KUAF k where k.ID = d.PerformerID) as Name, d.AuditDate as "Date Last Logged in"
from DAuditNew d where d.AuditDate >= %1 and AuditDate <= %2+1 and AuditStr = 'Login'
order by d.AuditDate desc
%1 = Start Date (User Input 1)
%2 = End Date (user Input 2)
Report Format: Auto LiveReport
I think the "func=admin.threadstatus&clean" is showing the current executing thread details from System,
And If you check on that details closely, you can find that the thread status details is showing the current executing thread and who executing that specific function.
Let's say for the indexing and document extraction process, in threadstatus it will show as admin, as the admin user is executing that job in the back ground, Yes, the admin have an active session, but that process is running in the background. Similarly if you have any xECM connection with impersonate user or any other REST API/ CWS implementation with a static user, you will find all the activities from those application has been done through that user, as expected.
Hence, what you are calling active user session/ logged in users that is totally depend on your scenario.
Anyone please correct me if I am wrong.
Thanks Kelly.
Per my understanding, this is typically for an in-house Admin/Super user for trackability of concurrent users in the system, during specific "busy times" of the month (or maybe other reasons as well).
It would have been more intuitive from a user perspective, to get the details for the very specific time at which the report is run; having the logged in time info does not guarantee that the user is "currently in an active session".