13.1 Document Manager overview IBM DB2 Document Manager addresses the origination, approval, distribution, and revision of unstructured information. In the simplest terms, Document Manager enables electronic files to be reused or repurposed by multiple individuals. Document Manager applies a discipline called library sciences to catalog corporate information, which could be in the form of hard copy (physical documents), electronic files generated by desktop applications, or just metadata or XML information created internally or externally. In any form, Document Manager is an application that enables users to index and file corporate information in a uniform and centralized way. Document Manager is a client for Content Manager hosted by Microsoft Internet Explorer. A Document Manager system is built on a three-tiered, scalable computing model. You can deploy the system’s components as needed and distribute them across multiple servers or clients. Document Manager is built on a three-tier model: Document Manager clients tier Document Manager server and services tier Content repository tier In this case study, the content repository for the Document Manager system is Content Manager.
13.2 A search scenario This case study illustrates a way to identify potential problems in your custom application and show how you can use cache setting to improve the performance of a Document Manager - Content Manager system. We start with a plain system that uses Document Manager as a client and Content Manager as the content repository. Document Manager cache is not configured initially. When users use the system, they complain that the logging time and system search response time seem to be slow. To identify the problem, we turn on Content Manager Library Server performance trace. See 13.3, “Enabling Library Server trace� on page 389 for details. We use echo to insert text into the icmserver.log, so that we will know at every step what actions we, as user, performed on the system, and what Content Manager operations have been triggered due to that action.
386
Performance Tuning for Content Manager