Performance Tuning for Content Manager

110 Performance Tuning for Content Manager

Indexes

Indexes are vital to the performance of the databases as they grow. When a table

grows to more than a few thousand rows, it is much faster to access the data by

an index than by looking at each row in the table. The index is maintained as an

ordered list of column entries with pointers to the corresponding database table

row. Ideally, all access to the indexing data in Content Manager is via an index.

Indexes come at a cost. There is a minor performance cost associated with

updating the indexes every time a change is made to table data. Additional

storage is required to hold each index, which can, in the extreme, be as large as

the table itself.

Indexes are also accessed in the buffer pools and can be placed into separate

table spaces and therefore different buffer pools. By separating the index data

into a separate table space and buffer pool, it can be protected from being

swamped by the table data. This is not done by default and you would need to

modify the Content Manager database manually.

The Content Manager administration tool provides a point-and-click interface to

create database indexes for your application. Refer to 5.5.3, “Data model” on

page 115 for more information.

For a great deal more information about designing and configuring your

databases refer to the DB2 Administration Guide: Planning.

5.5.1 Library Server configuration

Configuration and design options in the Library Server database have

performance ramifications. You can use the administration interface or the

administration APIs to set and change configuration parameters, turn functions

on or off, and define entities to the system.

To get to the Library Server Configuration, open the system administration client.

From the left-side pane, click the Library Server database → Library Server

Parameters → Configurations. From the right-side pane, double-click Library

Server Configuration.

We discuss several configuration options in the Library Server Configuration that

might influence system performance.

Definition tab

You can set the following configuration in the Library Server Configuration

Definition window.

Chapter 5. Designing and configuring for performance 111

Max users

Content Manager enables administrators to enforce client licensing restrictions,

either rigidly or more loosely. The Max user action parameter allows three options:

Reject logon Rigidly deny access to users in excess of the

license.

Allow logon with warning Allow the additional users (in excess of the

license) in with a warning message.

Allow logon without warning Allow the additional users in without any

warning message.

The second and third options assume that sufficient additional client licenses will

be acquired as soon as possible to accommodate these additional users.

An alternative configuration option is to set the maximum number of users to

zero. This bypasses license checking although it does not bypass the

requirement to abide by the license agreement. License compliance checking

requires processing at the Library Server. Bypassing the check removes this

load.

For a client to be considered concurrent in the Content Manager Version 8 client

licensing scheme, the user must have had an interaction with the Library Server

within the past 30 minutes. Users may be logged on, which will make them active

for the first 30 minutes. If they have no further interaction with the Library Server,

for example, they did not store or retrieve any information for the next 30 minutes,

then they are no longer considered a concurrent user for licensing purposes.

Tracking this level of user activity places a load on the system and is proportional

to the number of users and their activity. Bypassing this checking reduces the

load on the server.

If you choose to bypass checking, you should periodically check your license

compliance. This can be turned back on by setting the max users to the number

of client licenses held.

Features tab

You can set the following options in the Feature tab.

Text Information Extender (now Net Search Extender)

New in Content Manager Version 8 is the internal text search capability. Text

search works across both index fields and document text content, and is

provided by the Net Search Extender (NSE) in Content Manager Version 8.2.

The new text search capabilities are tightly integrated with the Library Server

database that enables automatic synchronization of the Library Server data and

the text index data. It also simplifies and controls user access to the text index.