Performance Tuning for Content Manager

386 Performance Tuning for Content Manager

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.

Chapter 13. Case study 387

Our exercise consists of the following steps:

1. Open a command prompt window and go to the location where icmserver.log

resides.

2. Launch the Document Manager client by typing:

echo Launching the Document Manager client.>icmserver.log

3. Log in to Document Manager as John Doe by typing:

echo The Document Manager client is now launched.>>icmserver.log

echo Logging into Document Manager as John Doe.>>icmserver.log

4. Perform a simple search. Type:

echo Log in completed.>>icmserver.log

echo Perform a search.>>icmserver.log

5. Perform the same search:

echo Search is done.>>icmserver.log

echo Search again.>>icmserver.log

6. Type:

echo 2nd search is done.>>icmserver.log

We extract part of the icmserver.log file when we perform a search in

Example 13-1. For simplification, we reduced some of the white spaces, and use

an ellipsis (...) to represent the repetitive numbers for the log entries.

Example 13-1 icmserver.log: log of searches in a Document Manager desktop with Content Manager

Perform a search.

ICMPLSLG ICMLOGON 00672 04/10 18:17:34.609 GMT ; ... ? JOHN.DOE

Library server code built < Mar 1 2006 17:20:53 >

ICMPLSLG ICMLOGON 01907 04/10 18:17:34.609 GMT ; ... ? JOHN.DOE 9 msec

ICMPLSGA ICMGETATTRTYPE 00412 04/10 18:17:34.609 GMT ; ... JOHN.DOE 1 msec

ICMPLSGT ICMGETITEMTYPE 00919 04/10 18:17:34.640 GMT ; ... JOHN.DOE 21 msec

ICMPLSLX ICMLISTXDOOBJECT 00335 04/10 18:17:34.640 GMT ; ... JOHN.DOE 1 msec

ICMPLSGA ICMGETATTRTYPE 00412 04/10 18:17:34.640 GMT ; ... JOHN.DOE 1 msec

ICMPLSQU ICMSEARCH 00482 04/10 18:17:34.796 GMT ; ... JOHN.DOE 65 msec

ICMPLSGI ICMGETITEM 04346 04/10 18:17:34.796 GMT ; ... JOHN.DOE 2 msec

ICMPLSLK ICMLISTNLSKEYWRD 00860 04/10 18:17:34.796 GMT ; ... JOHN.DOE 0 msec

ICMPLSLF ICMLOGOFF 00200 04/10 18:17:34.906 GMT ; ... ? JOHN.DOE 0 msec

Search is done.

Search again.

ICMPLSLG ICMLOGON 00672 04/10 18:19:19.390 GMT ; ... ? JOHN.DOE

Library server code built < Mar 1 2006 17:20:53 >

ICMPLSLG ICMLOGON 01907 04/10 18:19:19.390 GMT ; ... ? JOHN.DOE 10 msec

ICMPLSGA ICMGETATTRTYPE 00412 04/10 18:19:19.406 GMT ; ... JOHN.DOE 2 msec