IBM Content Navigator, Version 2.0.3

Event counters for IBM Content Navigator

You can use two types of event counters to measure the frequency and duration of tasks on your IBM® Content Navigator server. You can use this information to monitor and tune your server or database accordingly.

The event counters for IBM Content Navigator are categorized into two groups in IBM Content Navigator:

Event counters for Remote Procedure Call requests
Event counters for common document-centric tasks

Event counters for Remote Procedure Call Requests

These event counters measure the frequency and duration of incoming action requests to the IBM Content Navigator server. An action request is sent from a client when it asks the IBM Content Navigator server to perform some task on behalf of a user. A set of counters is created for each type of request the first time that it is received by the IBM Content Navigator server; then, the containers are cached. The IBM Content Navigator server looks for patterns in each request and handles them accordingly.

Event counters for common document-centric requests

These event counters monitor tasks that are commonly performed by users and organize those tasks by repository. The system dashboard displays these counters under the USER node. Information about the following actions is captured:

IBM FileNet® P8, IBM CMIS, and IBM Content Manager Version 8 repositories:
- Add Document
- Add Folder
- Check Out
- Check In
- Modify Properties
- Delete Item (both folders and documents)
- Download as Original
- Download as PDF
- Search
- Preview
- Generate Thumbnail
- Generate Page - PDF, thumbnail, and simple text
- Generate Page - Other document types
IBM Content Manager OnDemand repositories
- Modify Properties
- Download as Original
- Download as PDF
- Search

The Remote Procedure Call counters measure from when a request is first received to when the request is almost complete. The USER counters are at a lower level in the code specific to that action. Because these two types of counters are measuring from different points of the code, the durations that are captured for the two types of events are not the same.