Performance Tuning for Content Manager

Chapter 1. Content Manager 5

Figure 1-1 shows the Content Manager system with its components.

Figure 1-1 Content Manager system

All access to Library Server is through the database query language SQL.

Results from the queries are passed back to the client with object tokens,

locators for requested content that the user is authorized to access. The client

then directly communicates with the Resource Manager using the Internet

protocols HTTP, FTP, and FILE.

In the following sections, we explore the Content Manager system components,

discuss the communication among the system components, and introduce the

APIs used by Content Manager.

1.2.1 Library Server

The Library Server is the key component of a Content Manager system. It is

where you define the information that you store in Content Manager.

The Library Server has the following functions:

 Storing, managing, and providing access control for objects stored on one or

more Resource Managers. (For Resource Manager information, see 1.2.2,

“Resource Manager” on page 7.)

 Processing requests (such as update or delete) from one or more clients.

System

Admini str ati on

Client

Web Application

Server

Resource

Manager

Tivoli Storage

Manager

DASD

Optical Tape

Client

for

Windows

Information Integrator

for Content System

Administration Client

Clients

eClient

(Browser)

Web Application

Server

Library

Server

6 Performance Tuning for Content Manager

 Maintaining data integrity between all of the components in a Content

Manager system.

 Directly controlling user access to objects stored on any Resource Manager

in the system.

 Managing the content and performing parametric searches, text searches,

and combined (parametric and text) searches, using a relational database

management system such as DB2 Universal Database™.

Figure 1-2 shows a Library Server component.

Figure 1-2 Library Server component

You can directly access the Library Server database using SQL (Structured

Query Language) or a relational database client. A Library Server contains a

Library Server database and is implemented as a set of stored procedures. All

tasks carried out by Library Server are performed via stored procedures on the

Library Server database.

Each Content Manager system can have only one Library Server, which can run

on Windows, AIX, Linux, Solaris, and z/OS. Notice, if you use Oracle instead of

IBM DB2, you cannot run the Library Server on Linux, Linux for s/390, and z/OS.

The Library Server requires the following software:

 IBM DB2 Universal Database or Oracle Database

 IBM DB2 Runtime Client or Oracle Client

 IBM DB2 NetSearch Extender or Oracle Text (optional)

 C++ Compiler (optional)

IBM DB2 Universal Database or Oracle Database

The IBM DB2 Universal Database (provided in the Content Manager package) or

Oracle Database are required to run with the Library Server and must be

installed on the same system or workstation as the Library Server. The Library

Database

Library

Server

Stored

Procedures