This can be done by running SummaryTimings Logs and reading them with the Performance Analyzer. To turn onthe Summary Timings add the following line in the [options] section of theopentext.ini file:
wantSummaryTimings=TRUE
Stop the Livelink Server service. Clear the logs directory. Restart the Livelink Server service. Youwill need to do this for all of your front-end servers. Collect theselogs for about a week or two (depending on the number of users and amount ofactivity on your system).
Then stop the Livelink server service andcollect the timings logs. Restart the Livelink Server service and run thetimings logs through Performance Analyzer and look at the thread tab and selectbusiest hour. You can break that down to the busiest minute and get arough idea of your concurrency. Unfortunately there is no simple way thatI know of to calculate concurrency any other way.
--
Greg Kellogg
(361) 815-8950
From: eLink Discussion:Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Thursday, March 06, 20089:48 AMTo: eLink RecipientSubject: Report for ConcurrentUsers
Report for Concurrent Users
Posted by thomas.martindale@generaldynamics.uk.com (Martindale, Thomas) on 03/06/2008 10:44 AM
Does anyone know of a way to count the peak number of concurrent users at a point in time? The company I work for are upgrading from LL9.1 to 9.7 and I'm trying to collate usage stats, this one is proving very difficult to get. Thanks to anyone who can help!