22 Lotus Workplace Web Content Management and Content Manager Working Together
Highlighting of search terms in the search result (the NSE Fixpack 4 and
Content Manager Fixpack 6 are needed or else this is not enabled)
2.3 Content Manager architecture overview
In this section, we provide an overview of the IBM DB2 Content Manager
(Content Manager) architecture and a brief introduction to the main components
and features of Content Manager.
A Content Manager system contains a Library Server, one or more Resource
Managers and client applications (see Figure 2-3 on page 23). Depending on the
Enterprise Content Management solution which is implemented, additional
products from the Content Manager product portfolio can be integrated as
needed; see 2.2, “Content Manager product portfolio components” on page 17.
Library Server (LS) is a database application that manages users, user groups,
access control, data modeling, and document routing processes. Library Server
manages the storage and retrieval of all objects’ metadata using stored
procedures (SP). It is optionally installed with DB2 Net Search Extender to
provide text search capabilities on the stored objects. It has its own database.
Resource Manager (RM) is a Web application that runs on IBM WebSphere
Application Server. Resource Manager is a repository for physical files (objects)
stored in a Content Manager system. It is a storage management system
responsible for storing and retrieving the physical file objects. It has its own
database, separate from the Library Server database.
Content Manager clients include System Administrator Client, out-of-the-box
clients, and custom clients.
System Administrator Client is used to set up and
configure a Content Manager system. Out-of-the-box clients include Client for
Windows® and eClient.
Client for Windows (also called Windows Client) is an
out-of-the-box thick client, running on Windows, which enables the end users to
search, retrieve, and manage Content Manager metadata and objects.
an out-of-the-box think client, running on a Web browser, which enables the end
users to search, retrieve, and manage Content Manager metadata and objects.
You can also use C++ APIs or Java APIs provided by Information Integrator for
Content to write your own custom client applications.