Performance Tuning for Content Manager

106 Performance Tuning for Content Manager

enables customers to move to bigger, higher-capacity servers and operating

environments. For example, customers can move from Windows systems to AIX,

SUN, or Linux systems.

Clients

The client machines. including the machines supporting browser clients, also

need sufficient hardware resources to give the users the response time they

require. For these clients, memory and CPU speed are the main requirements to

manipulate and display the images. Refer to your favorites browser’s hardware

requirements, and allow extra resources to support the client side of the Web

application and viewer applets if you plan to use them.

Content Manager provides the client APIs on a range of platforms. Client APIs are

available in Java on Windows 32-bit operating systems, AIX, Linux, and Sun

Solaris, and the C++ APIs are supported on Windows 32-bit OSs and AIX. This

increases your options for where and how to deploy client applications. Having the

OO APIs available on Sun and AIX enables you to deploy thick clients or mid-tier

servers on these platforms for performance, scalability, or server consolidation.

5.5 Library Server

The Library Server is the heart of the Content Manager system. The Library

Server controls the system configuration, indexing data, and user access. The

Library Server in Content Manager Version 8 is now an extension of the

database. It is primarily a set of database tables and stored procedures that hold

the data and respond to client requests.

Because it is the single point of control, almost all activities on the system

interact with the Library Server. Optimizing the performance of the Library Server

can improve response time for almost every user and process in the system.

Stored procedures

The Client API calls are translated by the OO API layer and the DB2 client into

SQL and sent to the Library Server database. The generated SQL makes calls to

the Library Server stored procedures. The stored procedures run on the server,

perform a number of actions on the Library Server database, then return a

response to the DB2 client, the OO APIs, and the client application. This model

has the distinct advantage of being able to make a single call across the network

to perform a range of database searches, updates, and retrieves.

The stored procedures are dynamically linked libraries (DLLs) or programs that

run on the server and are called by the database engine in response to the client

calls. The stored procedures perform system functions such as checking for