Performance Tuning for Content Manager

120 Performance Tuning for Content Manager

archived documents will continue to grow at about the rate new documents enter

the system.

This can provide performance benefits in several ways. The active documents

item type can be tuned from maximum performance. It might be feasible to create

additional indexes on this item type that were too costly on all the data. This new,

active data tends to be updated more frequently and that can lead to

fragmentation of the database tables. If this is a smaller database table, it takes

less time to re-organize. Because these tables are smaller and more frequently

accessed, they can be retained in the system memory. The item type can be

separated into a new table space and have a dedicated buffer pool. Poor queries

that cause table scans will not have as dramatic an effect on performance

because these tables will be of limited sizes.

Note that information from previous versions of an item is not transferred across

when the item type is changed.

5.5.4 Document routing

Document routing is a fast and efficient method of managing document-centric

work flows. Because it is built into the Content Manager system, no additional

program layers are required to connect to the work flow and synchronize

operation. If document routing offers enough function to meet your business

requirements, then it is the simplest and most efficient work flow tool to use.

Note that the work flow APIs and user exists enable you to extend the functionality

of document routing if required. For example, parallel routing can be emulated by

sending the same item through two different processes at the same time.

5.6 Resource Managers

How we use Resource Managers can play an important part in overall system

performance. The Resource Manager provides the resource object storage

management functions. It receives, stores, and sends images and document files

from and to the client applications. New in Version 8 is the use of standard Web

ports and protocols to send and receive requests. The Resource Manager acts

like a Web server, serving resource objects on request. However, the request

must have a valid token supplied by the Library Server.

Behind the scene, the Resource Manager runs in a Web application host:

WebSphere Application Server, which is a Java application that holds control

data in the Resource Manager database and stores the resource objects on the

file systems connected to the server, and in an optional TSM backup archive.