This document provides insight into what may be done to report usage of IBM Lotus Quickr for both the IBM Lotus Domino and IBM WebSphere Portal implementations.
Presently, the IBM internal Lotus Quickr deployment, which for this document is used as an example, uses an enterprise view to monitor and plan the deployment. The IBM internal Lotus Quickr deployment is implemented with both Lotus Quickr services for Lotus Domino and Lotus Quickr services for WebSphere Portal. End users can create places from a list of templates and the system chooses the appropriate server based on the template chosen. The user sees a list of their places (those they own and those they have access to) from a single portlet. IBM uses a variety of methods for monitoring and planning, including tools such as the Wily tools offered by Computer Associates (primary tool), and an Open Source product, Nagios (secondary tool), as well as information provided by the back end servers themselves. We are evaluating replacing both tools with the IBM Tivoli Monitoring tool. The following information outlines the statistics that we collect and monitor for each of the Lotus Quickr deployment environments:
Lotus Quickr services for WebSphere Portal
For Lotus Quickr services for WebSphere Portal, the following basic statistics can be gathered by customer-written database queries:
- # of Places
- # of 'documents'
- # of Wiki/Blog pages and comments
- Size of all documents
Today, Lotus Quickr internally collects the following information which can be referenced by customer administrator-written database queries:
- Number of new documents were created today, last week, last month, and so on.
- Users who created the most documents today, last week, last month, and so on.
- Total number of documents in total, Number of users, or Total documents and users per teamspace, and so on.
We collect the following meta-data for all teamspaces and documents. Simple queries can be run against the system for reporting:
- Each document belongs to a teamplace, has an author, and timestamps for creation and lastupdate operations
- Each teamspace has an author and a timestamp for when it was created.
- Each teamspace knows the list of users and groups it can access; one caveat, there isn't any group expansion, so counting group membership would have to be a separate LDAP query if you need exact person count for teamspaces
since Lotus Quickr doesn't collect any statistics on chronological personalized click-through data, it isn't possible to report any of that data.
Lotus Quickr services for Lotus Domino
For Lotus Quickr services for Lotus Domino, the following basic statistics can be gathered by customer-written queries:
- # of places
- Total size of all places
- CPU/Disk IO rates
The Domino Place catalog which is part of Lotus Quickr, and maintained by the Lotus Quickr application is also available to provide more granular data on a "Per Place" basis. Information for the Place Catalog is available online at the following URL:
Please refer to the Services for Lotus Domino -> Administering -> Maintaining Servers -> Updating statistics in the Place Catalog
Reporting Metrics published
Additional information is available from the monitoring tools described above. All information is at the deployment level and permits us to report the following metrics:
- Number of Registered Users - Obtained from our LDAP
- Number of Places Created - Obtained from the Nagios tool with DB2 Queries
- CPU usage - Obtained from both tools Wily and Nagios
- Disk usage and growth statistics - Collected from the Nagios tool
- Concurrent Active User Session - Average active server sessions - Obtained using the Wily tool
- Total User Session Capacity - Server Session throughput - Obtained using the Wily tool
- Average Server requests - Requests to the Portal Server - Obtained using the Wily tool
- Average transaction response times - Portal Server Request response times - Obtained using the Wily tool
Lotus Quickr acknowledges the requirement to collect more personalized metrics (such as "who viewed what, and when"). This requirement is a candidate for the next feature release of Lotus Quickr. Customers with an interest in this capability may participate in the definition and clarification of this requirement by updating the online forum located at this URL: http://www-10.lotus.com/ldd/quickplace.nsf