The Open Text Content Server (formerly the Livelink Enterprise Server) can produce a great deal of transactional information, much of which includes performance data, but only one type of file is really suitable for modeling the performance of running system. Most of the log files are intended to assist developers and support personnel in diagnosing and troubleshooting transactional issues. The overhead placed on the system by these logs can be quite significant as the details being written increases.

One of the big problems with "Archiving" of data that software vendors must understand is that it is handled by IT and so costs and Return On Investment are focused around infrastructure like Tier

• What is a Usage Profile?
• What is the Usage Profile of my Livelink system?
• What is a "Livelink thread"?
• How many Livelink threads does my system require to meet average

Thanks mostly to the excellent programming environment provided by GATE Village, the Online Livelink Performance Suite is ready to be upgraded to include both new functionality and deeper integrati

1. What is the transactional load of your Livelink (Open Text Content Server) system?
2. What transactions are your users performing?
3. How many Livelink threads do you need to meet the average load?
4. What about peak bursts of activity?
5. What is the Usage Profile of your Livelink system?
6. And why should you want to know?