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 SP SP 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

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

SP

SP

SP

Net Search Extender

Chapter 2. Content Manager overview 25

modifying, searching, and deleting an item or object. A

privilege set

defines the maximum rights a user has to access a Content Manager system. See Data modeling for information on items.

The

Access Control List

(ACL) defines the maximum rights that can be given to

any user against a specific object, where privilege sets represent the maximum privileges granted to a specific user. ACL cannot grant a user more rights than are defined in the user’s privilege set, but it can restrict a user’s rights. For example, ACL may deny a user the access right to a specific item type object.

Data modeling

The objects stored in a Content Manager system are represented as items. Items are created using templates called

item types

.

Item types

are used to define, import, query and retrieve objects in a Content Manager system.

There are four different

item type classifications

which can be used when creating new item types: item, resource, document part, and document.

Item

This item type is used to store attributes only. There are no objects (such as photos or videos) stored on a Resource Manager. For example, in an insurance company, an item type classified as an item can be used to store the name, address, phone number of all life insurance agents of the company. All item type classifications in Content Manager can have multiple levels of child components within the same classification type as the root component.

Resource

This item type is used for objects with attributes and one and only one corresponding object to store on a Resource Manager. For example, in an insurance company, a resource item type Life_Insurance_Policy can be defined with attributes describing the customer details such as address, phone number, credit card number, insurance policy number and one text document object. You can use this to store the individual contract of a customer.

Document part

This item type stores metadata/attributes and textual, videos, images, photos, notelogs or annotations objects. There are predefined document parts: ICMBase, ICMBaseText, ICMBaseStream, ICMNotelog, ICMAnnotaions. For example, annotations can be used to add graphical highlights to an image object. If your application needs this capability, you should define a document part of ICMAnnotations. If predefined parts are not sufficient to design and set up your solution, you can define additional document parts.

Document

This is the item type classification used by LWWCM to store LWWCM objects. It is also

the only item type

supported by the out-of-the-box Content Manager client applications Client for Windows and eClient. A document contains multiple document parts. For example, in an insurance company scenario, we can define a new item type for life insurance contracts named Contracts and add the three predefined document parts, ICMBaseText, ICMStream, and ICMBase. You can import contract objects via Client for Windows, eClient or your own business applications. Contract documents which are text-searchable are stored in the ICMBaseText document part, videos containing additional life insurance policy movies can be stored in the ICMStream document part, and images from the customer can be stored in the ICMBase document part.

Document routing

Document routing is a workflow process that moves documents or folders through predefined steps (work nodes). Users of an integrated solution perform actions to move documents or folders through the process or move them to another process. A defined process needs, at a minimum, a starting work node, one action to be taken by users or an application and an ending work node. To set up the data model for your solutions, you create new item type(s), set the Item type classification, define metadata, and add the system-managed storage system (SMS) collection. Other things you need to specify include the access control list for the item type, versioning enabling or disabling, logging level, foreign keys, and auto-linking.

To get a better understanding of the Content Manager data modeling, please refer to Content Manager Implementation and Migration Cookbook, SG24-7051.

In document Lotus Workplace Web Content Management and Content Manager Working Together (Page 43-46)