We use a very stateless communication model with the server which means that although there is a login "action" in our clients, the client machine doesn't actually keep an active connection to the server. We use this to bootstrap some client side data, but that is it. This means that at the RTC application level the server doesn't know who is "logged-in". However, what we do track is who if perform which operation on the server at a current point in time.

Your options for tracking server load and connections are the following:

1. The RTC admin web page provides an "Active Services" page which shows the active open services being run.

2. Use the tooling in your application server (tomcat or WAS) that allows tracking session and connection activity.

Cheers,
Jean-Michel

Another possibility is to track the license usage. This works at least for floating licenses quite well.

You have to enable the Advance License Logging in the JTS Advanced Properties:

com.ibm.team.repository.service.internal.license.FloatingLicenseService

The file will then get for each license request and extend a time stamp with the userID. You know can simply search for the last entry for a user, or filter and sort it.

Example of such a license log file (csv):
Server, Start Time, Expiration Date, Policy Id, Lease Id, User Id, Operation Id, Description
https://clmserver01.domain.com/jts/, 2012-07-18T14:50:53Z, 2012-07-18T16:50:53Z, com.ibm.team.rtc.developer.floating-v3_b92a5960-cb65-11df-bd3b-0800200c9a66, _-Rzp8NDnEeGNXZb8cHYYbA, userID, com.ibm.team.reports.ide.ui.domain.ReportsDomain, checkout