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 integration/automation. The final goal of this suite to provide the ability to simply upload files, answer questions only you know about your environment, and then let the tools determine all of the data they can through the logs. This release sees the following major milestones toward that goal:

1. Support for compressed file (gzip) upload -- well, actually you could always upload it but now the tool will automatically decompress and use the file directly BUT that is not as good as it sounds as very large gzipped files are processed very inefficiently. Nonetheless, this change effectively provides the ability to work with over 2 million transactions while staying within the 25MB upload limit
   
2. Support for automatically decompressing uploaded gzipped files, and keeping the same file ownership while uploading them to the database making them available for your use. This usually happens within 2 minutes of the file finishing the upload process. Thus all you need to do is refresh the "Select File" page and you will see the original gzipped version as well as the uncompressed version.
3. Support for pulling the timestamps and time intervals directly from the uploaded data --- you can still change them via the Usage Profile Scenario form but the values they are created with come from the Usage Profile Dataset
4. The calculator now uses the actual time interval within the Dataset rather than hard-coded to 3600 seconds (one hour)
   • NOTE: the calculator's formulas expect that the uploaded data is from the single busiest hour within a typical business day ... the formulas may underestimate the required resources if a less busy time is chosen and both over- and under-estimated resources are possible if too short a timeline is provided.
   • NOTE: An excellent approach is to concatenate 1 full week of the same "busiest hour", the calculator will notice that multiple days are spanned but will only use the largest span in seconds from the times provided (no dates are used).
5. The Usage Profile Scenario's times now accept seconds (but to do so the calendar-based date picker has been removed)
6. The Session Activity within the Usage Profile Scenario is now "Number of Active Users / Session" and is calculated from the uploaded data (if the appropriate column exists), the Thread Calculator still uses Session Activity Percent but now calculates it using this number and the "Active Accounts" field provided by user input
7. The User Activity or transaction count per user per session is now calculated from the Usage Profile Dataset where the data exists (the appropriate column was provided and mapped during the Usage Profile Generation phase)

As always, your feedback is important to us, please do Submit Them Here