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.
eClient is
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.
Chapter 2. Content Manager overview 23
Figure 2-3 Content Manager architecture overview
2.3.1 Library Server
The main component in the Content Manager system is the Library Server (LS).
The Library Server is a database application which is implemented with DB2
stored procedures (SP). All the information managed by Library Server is stored
in DB2 tables within a Library Server database. Some examples of this
information include user definitions, user group definitions, access control
information, data modeling definitions, and document routing process definitions.
The Library Server application and the Library Server database are always
installed on the same machine. The default name of this database is ICMNLSDB.
All client access requests to objects stored in a Content Manager System are
controlled by the Library Server. Access to the Library Server is through the
database query language SQL. On a remote client workstation, the DB2 runtime
client needs to be installed to access the Library Server.
Content Manager also includes DB2 Net Search Extender (NSE) to enable a full
text search on documents or text metadata in Content Manager.
DB2
SP SPSP SP
Net Search
Extender
WebSphere
Application Server
Resource Manager
web Application
WebSphere
Application Server
Resource Manager
web Application
WebSphere
Application Server
Resource Manager
web Application
Resource Manager
Library Server
C++ OO API
Java OO API
http / https
SQL
http/https
eClient
24 Lotus Workplace Web Content Management and Content Manager Working Together
Figure 2-4 shows the Library Server component.
Figure 2-4 Library Server
The System Administration Client is used to specify and configure the Library
Server parameters. Use the System Administration Client to define
authentication, authorization, data modeling, and document routing.
Authentication
In a Library Server, you define users and user groups that can access a Content
Manager system. You can use the Lightweight Directory Access Protocol (LDAP)
to import user and group information. Content Manager supports the following
LDAP servers:
򐂰 IBM Directory Server
򐂰 Microsoft Active Directory
򐂰 Lotus Domino Directory Notes Address Book
Authorization
When users are defined in a Library Server, they are assigned a privilege set,
which is a group of privileges. A
privilege is a permission to perform an action on
an item or object. Some examples of permissions for actions are reading,
DB2
SP SPSP SP
Net Search
Extender
Library Server

Get IBM Workplace Web Content Management Java Edition V2 and IBM DB2 Content Manager V8 Working Together now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.