lotus workplace web content management and content manager ... · content management and content...

ibm.com/redbooks

Lotus Workplace Web Content Management andContent Manager Working Togetherfor LWWCM Java Edition V2 and CM V8 Only

Wei-Dong ZhuStephan Bolten

Ziad HakimMaria Elena de Leon

Walter Mayer

Using CM as a repository for LWWCM

Publishing CM content to LWWCM

Covering search, security, VideoCharger integration, and migration

http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/

Lotus Workplace Web Content Management and Content Manager Working Together

September 2004

International Technical Support Organization

SG24-6368-00

© Copyright International Business Machines Corporation 2004. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

First Edition (September 2004)

This edition applies to Version 2 Release 1 of Lotus Workplace Web Content Management Java Edition (product number 5724-I29), Version 8, Release 2 of IBM DB2 Content Manager for Multi-platforms,IBM DB2 Content Manager Information Integrator for Content for Multiplatforms (product numbers 5724-B19, 5724-B43).

Note: Before using this information and the product it supports, read the information in “Notices” on page xiii.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Lotus Workplace Web Content Management overview. . . . . . . 31.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 LWWCM architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2.1 LWWCM user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Creating and updating Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.1 Information Architecture (IA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.2 Web page design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.3 Collaboration for content management and distribution . . . . . . . . . . 101.3.4 Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.5 Syndication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.4 Retrieving data from different sources . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2. Content Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1 Why implement an Enterprise Content Management infrastructure? . . . . 162.2 Content Manager product portfolio components . . . . . . . . . . . . . . . . . . . . 17

2.2.1 IBM Lotus Workplace Web Content Management (LWWCM) . . . . . 172.2.2 IBM DB2 Document Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2.3 IBM DB2 Records Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2.4 IBM DB2 Content Manager Information Integrator for Content. . . . . 182.2.5 IBM DB2 Content Manager OnDemand . . . . . . . . . . . . . . . . . . . . . . 202.2.6 IBM VideoCharger (bundled with Content Manager) . . . . . . . . . . . . 202.2.7 IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2.8 IBM DB2 CommonStore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2.9 IBM Electronic Media Management System (EMMS) . . . . . . . . . . . . 212.2.10 IBM DB2 UDB Net Search Extender (NSE) . . . . . . . . . . . . . . . . . . 21

2.3 Content Manager architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.1 Library Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

© Copyright IBM Corp. 2004. All rights reserved. iii

2.3.2 Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.3 System Administration Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.3.4 Content Manager clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.5 How they work together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.3.6 Working with LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 3. Why and when to integrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.1 Reasons to integrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.2 Benefits of integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.1 Integrating using Content Manager as the repository . . . . . . . . . . . . 373.2.2 integration of external resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.3 Value propositions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.3.1 LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.3.2 Content Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.3.3 Integrated solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.4 Advantages of CM compared to other repositories . . . . . . . . . . . . . . . . . . 393.5 Sample scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 4. Case study. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.2 Adding the insurance option into the navigator . . . . . . . . . . . . . . . . . . . . . 43

4.2.1 Creating new options under the insurance option. . . . . . . . . . . . . . . 464.3 Creating content for the new insurance options . . . . . . . . . . . . . . . . . . . . 48

4.3.1 Insurance workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.3.2 Content templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.3.3 Insurance page design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.3.4 Creating insurance content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.4 Retrieving data from external sources into insurance content . . . . . . . . . 584.5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Part 2. Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5. Before you begin integration: pre-integration validation . . . . 635.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.1.1 Important log files and configuration files . . . . . . . . . . . . . . . . . . . . . 645.1.2 Some network considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.2 Software requirements and case study setup . . . . . . . . . . . . . . . . . . . . . . 675.2.1 Software requirements for LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . 675.2.2 Software requirements for Content Manager . . . . . . . . . . . . . . . . . . 685.2.3 Case study setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.2.4 How to check installed software versions . . . . . . . . . . . . . . . . . . . . . 71

5.3 Validation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.3.1 WebSphere Application Server and IBM HTTP Server. . . . . . . . . . . 725.3.2 LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

iv Lotus Workplace Web Content Management and Content Manager Working Together

5.3.3 DB2 and NSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.3.4 IBM Content Manager and Information Integration for Content . . . . 75

5.4 Problem determination and troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 785.4.1 General hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.4.2 WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.4.3 DB2 and NSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.4.4 IBM Content Manager and Information Integration for Content . . . . 835.4.5 LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 6. Using CM as a repository for LWWCM . . . . . . . . . . . . . . . . . . . 916.1 Configuring LWWCM to use CM as a data repository. . . . . . . . . . . . . . . . 92

6.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926.1.2 Modifying the WebSphere Application Server JVM setting. . . . . . . . 926.1.3 Modifying LWWCM’s aptrixjpe.properties file . . . . . . . . . . . . . . . . . . 946.1.4 Deleting existing indexes from the LWWCM server . . . . . . . . . . . . . 966.1.5 Starting LWWCM and running the initial setup . . . . . . . . . . . . . . . . . 966.1.6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

6.2 Accessing a remote Library Server database . . . . . . . . . . . . . . . . . . . . . . 976.3 LWWCM server routing information to access CM . . . . . . . . . . . . . . . . . . 99

6.3.1 The aptrixjpe.properties file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016.3.2 Files cmbicmsrvs.ini and cmbds.ini . . . . . . . . . . . . . . . . . . . . . . . . . 1036.3.3 Testing the ICM and FED connectors . . . . . . . . . . . . . . . . . . . . . . . 107

6.4 How LWWCM objects are stored in CM . . . . . . . . . . . . . . . . . . . . . . . . . 1086.4.1 Viewing AJPEData and AJPEResources item types . . . . . . . . . . . 1096.4.2 Storing LWWCM objects in AJPEData/AJPEResources objects . . 1096.4.3 Viewing AJPEData and AJPEResources items . . . . . . . . . . . . . . . 1106.4.4 Viewing AJPEData XMLContent data . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter 7. Publishing Content Manager content . . . . . . . . . . . . . . . . . . . 1157.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

7.2.1 LWWCM server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177.2.2 Content Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187.2.3 Content Manager data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

7.3 Federated content component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237.3.1 What is a federated content component? . . . . . . . . . . . . . . . . . . . . 1237.3.2 Why use federated content components?. . . . . . . . . . . . . . . . . . . . 1247.3.3 Setting up a federated content component . . . . . . . . . . . . . . . . . . . 1247.3.4 Putting it all together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

7.4 Connect tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.4.1 What are connect tags? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.4.2 Setting up connect tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.4.3 Putting it all together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Contents v

7.5 JSP component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517.5.1 What is a JSP component?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517.5.2 Why use the JSP component? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527.5.3 Setting up a new JSP component . . . . . . . . . . . . . . . . . . . . . . . . . . 1527.5.4 Sample code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567.5.5 Putting it all together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

7.6 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647.6.1 Log files and trace levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647.6.2 Basic connection testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1657.6.3 Executing the JSP program outside of LWWCM . . . . . . . . . . . . . . 165

Chapter 8. System architecture considerations . . . . . . . . . . . . . . . . . . . . 1678.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

8.1.1 Using Content Manager as the repository for LWWCM objects . . . 1698.1.2 Using Content Manager as the repository for external resources. . 1698.1.3 Server operating system considerations . . . . . . . . . . . . . . . . . . . . . 169

8.2 LWWCM and Content Manager on the same machine. . . . . . . . . . . . . . 1698.2.1 LWWCM considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1708.2.2 Content Manager considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 1718.2.3 Security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1718.2.4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1718.2.5 Advantages and disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

8.3 LWWCM and CM on different machines . . . . . . . . . . . . . . . . . . . . . . . . . 1728.3.1 LWWCM considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728.3.2 Content Manager considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 1738.3.3 Security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738.3.4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748.3.5 Advantages and disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

8.4 Integration scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748.4.1 One LWWCM server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748.4.2 Several LWWCM servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1778.4.3 Using Content Manager as a repository for external resources . . . 185

8.5 Mixed operating systems (Windows and AIX). . . . . . . . . . . . . . . . . . . . . 185

Chapter 9. Portal integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1879.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

9.1.1 Content creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889.1.2 Content storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889.1.3 Content management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889.1.4 Content delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

9.2 Why integrate LWWCM in WebSphere Portal Server? . . . . . . . . . . . . . . 1909.3 Levels of integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919.4 LWWCM portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

vi Lotus Workplace Web Content Management and Content Manager Working Together

9.4.1 Typical LWWCM portal page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1939.4.2 User management and security . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

9.5 Content Manager portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2019.5.1 Content Manager/Information Integrator for Content portlets . . . . . 2029.5.2 Information Integrator for Content portlets . . . . . . . . . . . . . . . . . . . 204

Part 3. Advanced topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Chapter 10. Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20910.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

10.1.1 Content Manager search possibilities . . . . . . . . . . . . . . . . . . . . . . 21010.1.2 NSE integration within Content Manager . . . . . . . . . . . . . . . . . . . 21210.1.3 Federated search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21510.1.4 LWWCM search module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

10.2 Integrating a search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21910.2.1 Leveraging the CM/II for Content Java APIs . . . . . . . . . . . . . . . . . 22010.2.2 IFrame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23110.2.3 LWWCM internal search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

10.3 Other search approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23410.3.1 Portal search engine (PSE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23410.3.2 Domino Extended Search (DES) . . . . . . . . . . . . . . . . . . . . . . . . . 234

Chapter 11. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23711.1 LWWCM security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

11.1.1 Access levels and security sections . . . . . . . . . . . . . . . . . . . . . . . 23811.1.2 Default users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24011.1.3 How it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

11.2 Content Manager security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24811.2.1 Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24911.2.2 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24911.2.3 How it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

11.3 How security types work together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25111.3.1 Security in general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25111.3.2 Security with connect tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25211.3.3 Security with federated content component . . . . . . . . . . . . . . . . . 25211.3.4 Security with the JSP component . . . . . . . . . . . . . . . . . . . . . . . . . 253

Chapter 12. VideoCharger integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25512.1 VideoCharger and how it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25612.2 Integration of VideoCharger and Content Manager . . . . . . . . . . . . . . . 259

12.2.1 Configuring a Resource Manager storage managed system . . . . 26012.2.2 Creating a video insurance item type . . . . . . . . . . . . . . . . . . . . . . 26112.2.3 Importing, searching for and playing videos . . . . . . . . . . . . . . . . . 262

12.3 Integrating Content Manager videos to a Web site . . . . . . . . . . . . . . . . 267

Contents vii

12.3.1 Why integrate Content Manager videos to a Web site? . . . . . . . . 26712.3.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26712.3.3 Creating video components in LWWCM . . . . . . . . . . . . . . . . . . . . 26812.3.4 Incorporating video within a Web page . . . . . . . . . . . . . . . . . . . . . 269

Chapter 13. Data migration through syndication . . . . . . . . . . . . . . . . . . . 27113.1 Syndication overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

13.1.1 Setting up the syndication tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 27213.1.2 Using unique Content Manager repository . . . . . . . . . . . . . . . . . . 27513.1.3 Using different repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

13.2 Migrating content repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27813.2.1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

13.3 Upgrading LWWCM V1.1 content to LWWCM V2.0 . . . . . . . . . . . . . . . 28713.3.1 File system to file system upgrade . . . . . . . . . . . . . . . . . . . . . . . . 28713.3.2 File system to Content Manager migration . . . . . . . . . . . . . . . . . . 28813.3.3 Enabling LWWCM version control . . . . . . . . . . . . . . . . . . . . . . . . 289

Chapter 14. Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29314.1 Versioning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29414.2 Versioning of repository objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

14.2.1 Versioning in LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29514.2.2 Versioning in Content Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 302

14.3 Versioning external resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30314.3.1 Versioning in federated, JSP components and connect tags . . . . 30414.3.2 Versioning using Content Manager. . . . . . . . . . . . . . . . . . . . . . . . 304

Appendix A. Installation supplement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Accessing a remote LS database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Cleaning up a Windows system prior to installation . . . . . . . . . . . . . . . . . . . . 311

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

viii Lotus Workplace Web Content Management and Content Manager Working Together

Figures

1-1 Authors and Web page designers working separately. . . . . . . . . . . . . . . 51-2 LWWCM architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61-3 LWWCM user interface with left-side navigator . . . . . . . . . . . . . . . . . . . . 81-4 Page design and components for a Web page . . . . . . . . . . . . . . . . . . . . 91-5 Workflow stages sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111-6 LWWCM architecture sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132-1 Content Manager product portfolio . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172-2 Information Integrator for Content architecture . . . . . . . . . . . . . . . . . . . 192-3 Content Manager architecture overview . . . . . . . . . . . . . . . . . . . . . . . . 232-4 Library Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242-5 Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272-6 Resource Manager manages the storage of the objects . . . . . . . . . . . . 282-7 System Administration Client interface . . . . . . . . . . . . . . . . . . . . . . . . . 302-8 Clients access to Library Server and Resource Manager . . . . . . . . . . . 312-9 LWWCM and Content Manager working together . . . . . . . . . . . . . . . . . 334-1 IT Jumpstart original main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434-2 New site area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444-3 Site area properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454-4 Navigator with insurance products option . . . . . . . . . . . . . . . . . . . . . . . 454-5 Insurance parent site area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464-6 Insurance sub-menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474-7 Group plans sub-menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474-8 Save workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484-9 Workflow stages update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494-10 New workflow content template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504-11 Component Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514-12 Add component in Component Manager . . . . . . . . . . . . . . . . . . . . . . . . 514-13 Result of after adding all components in insurance template . . . . . . . . 524-14 First part of the content template components. . . . . . . . . . . . . . . . . . . . 524-15 Insurance Web page with components added in insurance template . . 534-16 Site area properties setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564-17 Life insurance Web page with navigator in the left hand side . . . . . . . . 585-1 WebSphere Application Server administration console . . . . . . . . . . . . . 735-2 Zone Labs Integrity desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836-1 DB2 Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996-2 LWWCM configuration to use Content Manager as repository . . . . . . 1016-3 II for Content ICM and FED connector installation. . . . . . . . . . . . . . . . 1036-4 Server configuration utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

© Copyright IBM Corp. 2004. All rights reserved. ix

6-5 AJPEData and AJPEResources item type attributes. . . . . . . . . . . . . . 1086-6 AJPEResource document management definition . . . . . . . . . . . . . . . 1096-7 How LWWCM objects are stored in Content Manager . . . . . . . . . . . . 1106-8 Content Manager AJPEData items after LWWCM-Content Manager setup1116-9 Windows client AJPEResources search result . . . . . . . . . . . . . . . . . . 1116-10 LWWCM component library. image component . . . . . . . . . . . . . . . . . 1127-1 Installation II for Content: development workstation . . . . . . . . . . . . . . 1177-2 Installation Information Integrator for Content: local connectors . . . . . 1187-3 New attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207-4 New Item Type window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217-5 Item Type attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217-6 Item Type Document Management window. . . . . . . . . . . . . . . . . . . . . 1227-7 Define new resource back-end server: Content Manager V8 server . . 1267-8 Test connection to the newly defined content server. . . . . . . . . . . . . . 1267-9 Refresh server inventory for the newly defined content server . . . . . . 1277-10 Mapped attributes for the insurance case study . . . . . . . . . . . . . . . . . 1287-11 Query with the Insurance Type search template . . . . . . . . . . . . . . . . . 1307-12 Query results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307-13 Federated Component form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317-14 Federated component added within a LWWCM content page . . . . . . 1327-15 Resulting Web page of publishing CM content using federated components

1387-16 Process connect tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407-17 HTML option in Rich Text component . . . . . . . . . . . . . . . . . . . . . . . . . 1407-18 IBM developerWorks Web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457-19 Connect tag to strip partial Web page” . . . . . . . . . . . . . . . . . . . . . . . . 1467-20 Result of stripping partial Web page content to Insurance Web site . . 1467-21 Create a new content with connect tag . . . . . . . . . . . . . . . . . . . . . . . . 1507-22 Resulting Web page of publishing CM content using connect tags . . . 1517-23 JSP component - CM - integration approach. . . . . . . . . . . . . . . . . . . . 1527-24 JSP component configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557-25 Output of CMContentList.jsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607-26 WCM tag sample page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1627-27 Item Type and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637-28 Setting up new site area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1648-1 Necessary component for one and many boxes . . . . . . . . . . . . . . . . . 1688-2 LWWCM and Content Manager on the same box . . . . . . . . . . . . . . . . 1708-3 LWWCM and Content Manager on different boxes . . . . . . . . . . . . . . . 1728-4 Secure architecture example: LWWCM/CM in separate boxes. . . . . . 1738-5 Integration details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758-6 Configuration of the AJPEResources to point to another RM. . . . . . . . 1778-7 Multi-environment, multi-machines setup . . . . . . . . . . . . . . . . . . . . . . 179

x Lotus Workplace Web Content Management and Content Manager Working Together

8-8 Multiple LWWCM servers/machines scenario architecture . . . . . . . . . 1808-9 Different LWWCM using the same Content Manager . . . . . . . . . . . . . 1818-10 Several LWWCM servers using the same Content Manager . . . . . . . 1828-11 Multi-LWWCM using multi-Resource Managers . . . . . . . . . . . . . . . . . 1848-12 Multi-LWWCM to multi-Content Manager via syndication . . . . . . . . . . 1859-1 WPS/LWWCM / Content Manager architecture. . . . . . . . . . . . . . . . . . 1889-2 Sample LWWCM portal page layout . . . . . . . . . . . . . . . . . . . . . . . . . . 1939-3 Insurance navigator definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1949-4 Insurance navigator portlet configuration - content . . . . . . . . . . . . . . . 1959-5 Insurance navigator portlet configuration - links . . . . . . . . . . . . . . . . . 1959-6 Importing text document into Content Manager. . . . . . . . . . . . . . . . . . 1969-7 Component manager for content Insurance Name 1. . . . . . . . . . . . . . 1969-8 Selecting content for the federated content component . . . . . . . . . . . 1979-9 Insurance content portlet configuration - content . . . . . . . . . . . . . . . . . 1989-10 Insurance content portlet configuration - links . . . . . . . . . . . . . . . . . . . 1989-11 Insurance menu portlet configuration - content . . . . . . . . . . . . . . . . . . 1999-12 Portal page layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1999-13 Insurance portal page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2009-14 User credentials flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2019-15 Content Manager portlet start page . . . . . . . . . . . . . . . . . . . . . . . . . . . 2029-16 Content Manager portlet items types . . . . . . . . . . . . . . . . . . . . . . . . . . 2039-17 Content Manager portlet search entry . . . . . . . . . . . . . . . . . . . . . . . . . 2039-18 Content Manager portlet search result. . . . . . . . . . . . . . . . . . . . . . . . . 2049-19 Federated search portlet - query screen . . . . . . . . . . . . . . . . . . . . . . . 2059-20 Federated search portlet - result screen . . . . . . . . . . . . . . . . . . . . . . . 20510-1 Parametric search on the InsuranceType attribute IT_Name . . . . . . . 21110-2 Parametric search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21110-3 Text search option settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21310-4 Import a text searchable document form Content Manager eClient . . 21510-5 LWWCM Web site development with federated search objects . . . . . 21610-6 JSP with federated search APIs integrated in a Web site . . . . . . . . . . 21710-7 NSE / federated search integration . . . . . . . . . . . . . . . . . . . . . . . . . . . 22110-8 The content object including the JSP component . . . . . . . . . . . . . . . . 22810-9 Site area properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22910-10 NSE and search result Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23010-11 Federated search and search result Web page. . . . . . . . . . . . . . . . . . 23010-12 eClient integrated through an iFrame . . . . . . . . . . . . . . . . . . . . . . . . . 23211-1 LWWCM object security setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23811-2 Workflow buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24011-3 Default author for content created using this template . . . . . . . . . . . . 24311-4 Add group1 so that the members of this group can see this site . . . . . 24411-5 Authors field inherit from Content Template’s Author field. . . . . . . . . . 24511-6 Security is from the workflow stage and the author is added. . . . . . . . 246

Figures xi

11-7 Workflow Security setting in stage1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 24711-8 Workflow security setting for content test 1 after moveing to stage2. . 24811-9 ACL security process flow chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25111-10 Federated content component setting has the first priority . . . . . . . . . 25312-1 VideoCharger installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25712-2 VideoCharger configuration and administration. . . . . . . . . . . . . . . . . . 25812-3 View and run the sample IBM video . . . . . . . . . . . . . . . . . . . . . . . . . . 25912-4 VideoCharger storage managed system configuration . . . . . . . . . . . . 26012-5 Set up VideoCharger SMS configuration . . . . . . . . . . . . . . . . . . . . . . . 26112-6 Selected attributes for the InsuranceVideo Item type . . . . . . . . . . . . . 26212-7 Importing some videos from Content Manager Windows Client . . . . . 26312-8 Error while importing a video if IBM LUM is not installed. . . . . . . . . . . 26412-9 Running a basic search against the InsuranceVideo item type . . . . . . 26412-10 Launching the VideoCharger player application . . . . . . . . . . . . . . . . . 26512-11 Open an InsuranceVideo item to play the video . . . . . . . . . . . . . . . . . 26612-12 Federated content component for video search . . . . . . . . . . . . . . . . . 26813-1 Crossed information between Syndicator and Subscriber . . . . . . . . . . 27413-2 Content Manager AJPEData table. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27613-3 Subscriber enable option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27613-4 Syndication using the one Content Manager repository . . . . . . . . . . . 27713-5 Syndication using two different repositories. . . . . . . . . . . . . . . . . . . . . 27813-6 Migration approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27913-7 Application assembly for temporary LWWCM server. . . . . . . . . . . . . . 28213-8 Syndicator and subscriber for migration . . . . . . . . . . . . . . . . . . . . . . . 28413-9 AJPEData search result in Content Manager after syndication . . . . . . 28413-10 Deleting the temporary LWWCM application . . . . . . . . . . . . . . . . . . . . 28613-11 Updating the LWWCM Web application. . . . . . . . . . . . . . . . . . . . . . . . 28813-12 Migrated content before and after version enablement . . . . . . . . . . . . 29114-1 Different LWWCM versions in Content Manager . . . . . . . . . . . . . . . . . 29714-2 Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29714-3 Save version of a content object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29914-4 Version all process status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30014-5 Version management in LWWCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30114-6 Comparison of LWWCM and Content Manager versioning . . . . . . . . . 30214-7 Set the versioning policy for the InsuranceVideo item type . . . . . . . . . 30614-8 Supplemental version policy for specific document parts . . . . . . . . . . 307

xii Lotus Workplace Web Content Management and Content Manager Working Together

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2004. All rights reserved. xiii

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

Eserver®Eserver®Redbooks (logo) ™developerWorks®ibm.com®iSeries™AIX®Cloudscape™Domino.Doc®

Domino®DB2 Universal Database™DB2®Everyplace®Informix®IBM®Lotus®Notes®PAL®

Redbooks™Redbooks (logo)™SLC™Tivoli®VideoCharger™VisualAge®WebSphere®

The following terms are trademarks of other companies:

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

xiv Lotus Workplace Web Content Management and Content Manager Working Together

Preface

In this IBM® Redbook, we explore various ways of integrating IBM Lotus® Workplace Web Content Management (LWWCM) V2 and IBM DB2® Content Manager (Content Manager) V8.

In Part 1 of the redbook, we provide brief overviews of LWWCM and Content Manager. We discuss why we might want to integrate both products and when to do so. We also introduce the case study of an insurance company, which we will be using throughout this redbook to show sample integration steps, procedures, and coding.

In Part 2, we cover various areas that you need to be familiar with, aware of, and have set up to achieve a successful integration. We show you how to use Content Manager as a repository for LWWCM, and how to publish existing Content Manager content to LWWCM using federated content components, connect tags, and JSP components. Having covered the basics of how to integrate, we address some of the issues you need to consider when planning the entire integration system architecture. This includes covering different scenarios of having LWWCM and Content Manager in one machine, having multiple LWWCMs using syndication, and having multiple Resource Managers in the setup. The part concludes with a discussion of portal integration.

In Part 3, we cover advanced topics including search, security, integrating VideoCharger™ videos, data migration, and versioning.

This IBM Redbook is intended for IT architects and specialists working on LWWCM and/or Content Manager who will be in charge of an LWWCM and Content Manager integration project.

The team that wrote this redbookThis redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center.

Wei-Dong Zhu (Jackie) is a Content Manager Project Leader with the International Technical Support Organization at the Almaden Research Center in San Jose, California. She has more than ten years of software development experience in accounting, image workflow processing, and digital media distribution. She holds a Master of Sciences degree in Computer Science from

© Copyright IBM Corp. 2004. All rights reserved. xv

the University of Southern California. Jackie joined IBM in 1996. She is a certified Solution Designer for IBM DB2 Content Manager.

Stephan Bolten is an Advisory IT Specialist of the IBM Software Services department in Zurich, Switzerland. He has more than five years of experience in IT, particularly in the development of IBM Lotus Domino® solutions and IBM WebSphere® Portal Server and IBM Lotus Workplace related applications. His further areas of expertise include Web Content Management solutions with IBM Lotus Workplace Web Content Management for Domino and Java™, enterprise integration and enterprise search approaches. He has worked extensively on projects involving those topics since he joined IBM in 2000.

Ziad Hakim is a consultant with ebf-EDV Beratung Foellmer GmbH in Cologne, Germany. He is an IBM Certified Professional for Lotus and WebSphere. He has over six years of experience in solution design and architecture, as well as in system consulting and integration. He has extensive Lotus and WebSphere installation, deployment and application developer skills and has been working with Lotus Workplace Web Content Management since its first release.

Maria Elena de Leon is a CLP (Certified Lotus Professional). She holds a degree in Computer Science from the Facultad de Ingeniería, Universidad de la Republica, Montevideo, Uruguay. She has been working at ISA Ltda, an IBM Business Partner, since 1999. Her areas of expertise include Aptrix, Lotus Workplace Web Content Management, Domino applications, and Java applications for WML technology. She has more than five years of experience in the development of IBM Lotus Domino solutions and has worked as a consultant on many different kinds of projects, particularly projects related to quality assurance that follow ISO standards. She has also developed customized solutions for international companies in foreign countries like Costa Rica, where one of the main goals was the integration of Lotus Domino Solutions and Siebel.

Walter Mayer is a technical consultant for IBM Content Management Technical Enablement Channels and a member of the IBM DB2 Information Management EMEA team in Germany. He holds a degree in Physics. He has several years of experience in the software development and customer services area as a technical consultant for Enterprise Information Portal and Text Mining. Between 2001 and 2003 he worked as a DB2 and Pervasive Computing (PvC) consultant and DB2 Everyplace® project leader in EMEA. He has published several papers on mobile computing and has taught DB2 Everyplace, PvC and, since 2004, IBM CM Certification workshops throughout EMEA. He has worked on numerous IBM BP projects since he joined the IBM BP EMEA Enablement team in 2000.

xvi Lotus Workplace Web Content Management and Content Manager Working Together

Thanks to the following people for their contributions to this project:

Mahesh GargDavid SandersJerald SchoudtArya AdeliBasuki SoetarmanIBM Sillicon Valley Lab, US

Jason HatchRob EnrightIBM Software Services for Lotus, UK

Christoph RuppIBM Software Services for Lotus, Switzerland

Stefan MommaJuergen MetterHolger KoenigIBM Boeblingen Lab, Germany

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Preface xvii

http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html

Comments welcomeYour comments are important to us!

We want our Redbooks™ to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways:

� Use the online Contact us review redbook form found at:

ibm.com/redbooks

� Send your comments in an Internet note to:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099

xviii Lotus Workplace Web Content Management and Content Manager Working Together

http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.html

Part 1 Introduction

In this part, we provide brief overviews of LWWCM and Content Manager. We discuss why we might want to integrate both products and when to do so. We also introduce a case study, for an insurance company, which we will be using throughout this redbook to show sample integration steps, procedures, and coding.

Part 1

© Copyright IBM Corp. 2004. All rights reserved. 1

2 Lotus Workplace Web Content Management and Content Manager Working Together

Chapter 1. Lotus Workplace Web Content Management overview

This chapter describes LWWCM’s features and benefits and the importance of quick and easy Web site maintenance.

The topics addressed in this chapter are as follows:

� Introduction to LWWCM

� Architecture of LWWCM

� How to create and update Web sites:

– Information architecture– Web page design– Collaboration teams for distribution and management of contents– Versioning– Syndication

� Retrieval of data from different sources

1


1.1 IntroductionIBM Lotus Workplace Web Content Management (LWWCM) provides an end-to-end solution that allows users with non-technical skills to easily publish their documents in a Web site. Content creation is simplified and streamlined by allowing users to use reusable components and pre-built templates.

LWWCM separates the design and presentation from content creation. This allows the creation of content once, and the display of the same content with a different look and feel. You can easily create and maintain your Web site without worrying about the impact of the contents on the Web site’s look and feel. This also guarantees a consistent presentation because the contents remain unchanged even when the Web site design changes.

Using LWWCM, the development and delivery of information is accelerated; consequently, this drives down the cost of creating and managing Web site contents, which usually exist in different forms and formats within companies. With LWWCM, the information can be freely distributed and instantly updated across all existing applications, including Internet, intranet, and extranet Web sites.

In addition, LWWCM provides the following benefits:

� Easy-to-use features, allowing users to deploy a Web site faster

� Scheduled publishing and expiring of Web pages

� Scalability from mid-sized to large enterprises

� Collaborative functionalities, including workflow, personalization, and caching services

� Security settings to control user access to different areas of the Web site

� Syndication, allowing the back-up and restoring of the published business information

� Versioning of content, which could be helpful through the document review and approval process

� Cost reduction of managing sites, while ensuring that information on the sites always remains up-to-date

Figure 1-1 on page 5 shows how content authors and Web page designers can work separately to create the Web page(s) that appear on a Web site.


Figure 1-1 Authors and Web page designers working separately

1.2 LWWCM architectureLWWCM includes team collaboration, messaging, document management, and a variety of other business processes and applications. Within the Workplace environment, LWWCM provides collaborative Web content design, approval, caching, and staging.

Within a Web page, the information can come from multiple repositories. Figure 1-2 on page 6 shows an example of a Web page where information comes from three different sources:

� The A data is populated from the LWWCM application client and is stored in the LWWCM repository that could be IBM DB2 Content Manager CM, IBM DB2, or XML.

� The B data is populated from an external Content Manager application.

� The C data is populated from an external DB2 database.

DesignerAuthor

Page Design

ContentWeb Page

Content

Chapter 1. Lotus Workplace Web Content Management overview 5

Figure 1-2 LWWCM architecture

LWWCM is available for Lotus Domino and the Java Edition for WebSphere Application Server (including Portal server).

The Domino edition consists of a group of Notes databases where the Web page content of the Web site and the Web page design are stored as Domino documents in a publishing database and are rendered when a page is requested.

The Java edition consists of a Web application that is installed in a Web application server. The Java edition can use one or more of the following external repositories: IBM DB2 Content Manager (Content Manager), IBM DB2, and Oracle.

Table 1-1 on page 7 compares the differences in features between the Domino and Java editions.

web page

Websphere Application Server

LWWCM Java edition

Enterprise Information Portal

DB2 OtherCM

C

A

B

Business Applications (MsWord, Dreamweaver,

etc)

CM

XML

DB2

Repositories

A

BC


Table 1-1 Comparison between LWWCM Domino edition and Java edition

Since the main topic of this redbook is how to deal with the integration of LWWCM with Content Manager, for the remainder of this redbook, we cover LWWCM, the Java edition, V2.0, with Content Manager as the repository.

1.2.1 LWWCM user interfaceLWWCM user interface (sometimes also called the LWWCM administration user interface) shows a navigator on the left, and is divided into the following modules: Content Management, Design and Development, Site Management, Security and Workflow, Version Management, and Syndication and Deployment.

The Content Management module stores the contents within its Content Library.

The Design and Development module stores the design elements and components such as page designs, images, files, content templates and search rules.

The Site Management is composed of Site Framework and the Category Management. The Site Framework comprises the site structure definition, that is, the Web site map. The Category Management comprises the category taxonomy, which is the classification of content in categories.

The Security and Workflow module stores the users and groups as well as the workflows, stages and actions.

The Version Management module contains the Version Library, which is used to store multiple copies of an object as versions.

Feature Domino Java 1.1 Java 2.0

Version control Yes No Yes

Batch edition Yes No No

Export site to HTML No Yes Yes

Multi-lingual content Yes Yes Yes

Multi-lingual translation workflows

Yes No Yes

Complex templates No Yes Yes

Multiple content clients Yes No No

Content import Yes No Via API


The Syndication and Deployment module contains the syndicator and subscriber objects to achieve syndication among different servers.

Figure 1-3 LWWCM user interface with left-side navigator

The Design and Development module contains components that are mainly used during the design phase of the Web site presentation. These components are configurable and reusable objects such as content menus (based on a search by attribute), navigators, menus, and images. Some of these components are mainly used during the design phase of each Web page, such as page design or content templates. Other components are directed to the common users during the content creation phase.

For example, a component page design contains the skeleton for a Web page and is included within a site area. When a user creates content, the user only has to choose the specific content template and site area. The templates are used to store certain types of default information that are common to all the contents created with the same template. For this reason, the content templates, along with the page’s design, help to ensure that the published content is uniform and has the same look and feel throughout.


1.3 Creating and updating Web sitesThe components that we must consider in order to create a Web page are the site area, workflow, and page design. As the first step, the Web site developer must create site areas. After that, the Web site developer creates page designs, content templates (which will be included within the proper site area) and workflows. Once they are ready to be used, content creators select the proper content templates, choose an appropriate site area, and create their Web pages.

1.3.1 Information Architecture (IA)The first thing we need to keep in mind when building a Web site is how the information in our Web site will be organized. This is known as the Information Architecture (IA). The IA determines how information on a Web site should be organized and linked in such a way that people find it easy to use and to understand.

In LWWCM, this IA structure is defined in the Site Framework and represents the Web site hierarchy. Each entry (site area) in the Site Framework dynamically creates a link to the page representing the proper entry point of a Web site. From the Site Framework, the navigators can be created to be included in the target Web site.

1.3.2 Web page designA Web page is mostly made up of components and content. The components are referenced by the underlying page design that builds the basic layout and the default properties (for example: background color, images, and frames) of the Web page. Figure 1-4 shows the page design and components that make up a Web page.

Figure 1-4 Page design and components for a Web page

CONTENT

Application

Com

pone

nt

CONTENT

Application

Com

pone

ntC

ompo

nent

Page Design Web Page


LWWCM provides its own content creation tool. You can either enter your content as rich text or as HTML directly. There are no out-of-the-box import filters for document types like MS Word, Dreamweaver, etc. You can still create your content with these tools but you would have to save it as HTML and copy/paste it into the editor LWWCM provides.

The contents created with all these different tools are presented on a Web site with little or no modification to the source documents. In fact, LWWCM can present multiple content types on the same Web page.

A Content Template contains the data entries for the content components, such as title, summary, and central content body. The only content components that authors can create are those which were defined in the Content Template.

A Page Design is composed of HTML code that layout the structure of a Web page and provide some of the general page properties. A Page Design also uses LWWCM tags to reference other specific components.

Components may be divided into design components (for example: menus, page design, and navigators) and content components (for example: content main body text, content summary, and title).

Design components reside under the Component Library of the LWWCM user interface tree view, which is part of the Design and Development module, while the content components reside under the the Content Library of the LWWCM user interface tree view, within the Content Management module.

1.3.3 Collaboration for content management and distributionLWWCM provides an authorization flow (workflow) for each content to be published. Applying this collaborative approval process implies an interactive integration between people and contents. The author is responsible for each content; there is no third party participant who might make mistakes in the edition or publication process.

These workflows enable the collaborative process of creating, maintaining and deploying Web content over Web sites to ensure accuracy, authenticity, timeliness and effectiveness of content. It also allows users to create and maintain consistent and interactive content representing large amount of rapidly changing information.

This solution facilitates large teams to work together, jointly where necessary, but independently enough so that they can manage changes to content in their respective work groups until they are ready to share them with the extended contribution team.


A workflow can be composed of one or more workflow stages. The number of stages are defined by an administrator according to each company’s needs. All workflows must have at least one workflow stage. Every content must go through all the selected workflow stages before it is published on a Web page.

As a content moves through the workflow stages, its status changes from “Draft” to “Live” (viewable on a live Web site) and eventually to "Expired" (when it reaches the expiration date).

A workflow stage also determines the access level of users and groups for Web pages in that stage. Figure 1-5 shows some samples of the workflow stages.

Figure 1-5 Workflow stages sample

When an activity within a workflow is completed, the next activity appears on the task list of the people responsible for that stage in the workflow. This process continues until all the stages in the workflow are completed. At the end of a workflow, the resulting file or document is promoted and published. The approved content then becomes published on the Web site and can be viewed by readers.

1.3.4 VersioningWhen you create or update content, you may want to save versions of each item. LWWCM provides the versioning capability for this purpose. If required, you can

Type title

1. Type text

Type text

Type text

Approve

ApproveType text

Approve

Type text

Decline

Publish Expire

Draft


return to a previous version of any piece of content. These units are easy to store and to restore.

This topic is described in detail in Chapter 14, “Versioning” on page 293.

1.3.5 SyndicationThe LWWCM syndication feature is used to replicate data from one server to another.

Syndication is recommended if you have any of the following requirements:

� Maintain two separate servers for development and production stages, allowing for greater flexibility in development and possibly more efficiency in production without affecting each other.

� Distribute content across different servers.

� Migrate content from one repository to another.

1.4 Retrieving data from different sourcesLWWCM has the ability to retrieve data from different sources. These sources can be external databases, Content Manager system, file systems, as well as other Web sites. LWWCM can format the retrieved data and display it as part of its own content.

There are different ways to retrieve data from other sources: one can be made in the form of URL request; another way is using Connect Tags that can be embedded in Page Designs or Component designs. Data Providers are used to retrieve data for display only and this data cannot be modified. The content is dynamic, because when the source document changes, LWWCM dynamically updates the content displayed on this page without any intervention.

A Web page can be built from content that is taken from different sources and shown in the same Web page. Note that LWWCM does not take care of the formating of the source files.

To improve the content’s look and feel, LWWCM also allow us to add content and change the presentation of existent content contained in multiple file formats.

Data from Content Manager can be retrieved using either LWWCM Federated Content Components or by URL. The Federated Content Components are used to retrieve and store files from federated data sources.


Apart from the federated components, there are JSP Components, which are used to store paths to JSP. When JSP Components are included within a page design or other component design, and a Web page using this design is rendered, a request to JSP is generated and processed.

For more information about the retrieving data from different sources, refer to Chapter 7, “Publishing Content Manager content” on page 115.

Figure 1-6 shows an LWWCM architecture sample that breaks down to four area:

� Creation: Content creation can be implemented using either existing business application tools or with the LWWCM text editor.

� Storage: Use Content Manager and Tivoli® Storage Manager for content storage.

� Management: Use LWWCM to manage the content and design of Web pages following approval workflow stages.

� Delivery: Use LWWCM to publish and deliver the content to Web sites.

Figure 1-6 LWWCM architecture sample

DELIVERYMANAGEMENTSTORAGECREATIONBusiness applications

MS WORD

Browser Rich Text

Websphere Studio

OTHER

CONTENT MANAGER

TIVOLI STORAGE MANAGER

LOTUS WORKPLACE CONTENT MANAGEMENT

WEB PAGE

Content

Websphere Portal Server Page

Web Page


Chapter 2. Content Manager overview

In this chapter, we provide an overview of IBM DB2 Content Manager (Content Manager). We explain why implementing an Enterprise Content Management infrastructure becomes a very important issue for all enterprises in industries and in the public area. We describe the Content Manager product portfolio and Content Manager architecture. We also cover the main functions and features of Content Manager.

Specifically, we cover the following topics in this chapter:

� Why implement an Enterprise Content Management infrastructure?� Content Manager product portfolio components� Content Manager architecture overview

2


2.1 Why implement an Enterprise Content Management infrastructure?

Every day, we search, retrieve and store information which is important to us in our workplace infrastructure. Important information could be a document such as an electronic file or set of files. It could be a large collection of images, videos, audio, computer output, XML and HTML files or electronic records where each record contains a set of electronic and/or physical objects. Mostly, a company infrastructure is designed, collected, built and accumulated over time. Applications and services are bought or written on top of the infrastructure and together they support the Enterprise Content Management (ECM) needs. Over time, many systems have emerged to manage content, to store and access daily data chunks of structured or unstructured information to get business done. The storage of content is rarely designed for efficiency. In public and government areas, the demand for methods of governance and administration leads to an increasing demand on infrastructure. There is a consistent increase in numbers of guidelines, specifications and standards. Some of the existing record management standards in the public area are:

� US 5015.2, Records Management toolkit definition for the US government

� DOMEA, Document Management and Archiving Requirements for German governmental organizations

� VERS, Victorian Electronic Record Standard

� UK PRO2, Archival Records Management definition for the UK government

The need to implement robust content management is steadily increasing. The trend is to move away from a string of disparate projects and environments to an infrastructure approach, integrating content with the line of business, Web Content Management, Digital Asset Management, distance learning, mobile Sales Force Automation (SFA), Enterprise Resource Planning (ERP) solutions or other applications to accelerate the benefits across the enterprise. From the financial point of view, as content grows exponentially, it becomes important to reduce the storage costs and the maintenance costs of overlapping, and to deliver content in a controlled manner to the end users. To address this challenge, IBM offers the IBM DB2 Content Manager product portfolio as described below:

� IBM DB2 Content Manager (Content Manager)– Optionally using VideoCharger as one type of Resource Manager– Optionally using DB2 UDB Net Search Extender (NSE)

� IBM DB2 Content Manager Information Integrator for Content� IBM Lotus Workplace Web Content Management (LWWCM)� IBM DB2 Document Manager


� IBM DB2 Records Manager� IBM DB2 Content Manager OnDemand� IBM Tivoli Storage Manager� IBM DB2 CommonStore� IBM Electronic Media Management System (EMMS)

Figure 2-1 provides an overview of the Content Manager product portfolio.

Figure 2-1 Content Manager product portfolio

2.2 Content Manager product portfolio componentsIn this section, we describe, at a high level, the different components that make up the Content Manager product portfolio as shown in Figure 2-1.

2.2.1 IBM Lotus Workplace Web Content Management (LWWCM)IBM Lotus Workplace Web Content Management (LWWCM) enables the easy creation of Web sites and Web content. Refer to Chapter 1, “Lotus Workplace Web Content Management overview” on page 3 for an overview of LWWCM.

IBM DB2 Content Manager

- VideoCharger

- Net Search Extender

IBM DB2 Content

Manager Product Portfolio

e-mail ArchiveIBM DB2 CommonStore - SAP - Exchange - Domino

RecordsManagement

IBM DB2 RecordsManager

Digital RightsManagement

IBM Electronic Media Management SystemEMMS*

IBM DB2 Information Integrator for Content

InformationIntegration

Imaging

DocumentManagement

COLD

Digital AssetManagement

NSE

IBM Lotus Workplace Web Content Management (LWWCM), Java Edition

Web ContentManagement

IBM Tivoli Storage Manager TSM

DB2 OnDemand

IBM DB2 DocumentManager

Chapter 2. Content Manager overview 17

2.2.2 IBM DB2 Document ManagerIBM DB2 Document Manager (Document Manager) manages the various states and transitions that occur throughout a document’s life cycle, from creation to final disposition. Document Manager supports collaborative document creation and management for dispersed user groups, such as creators, reviewers, approvers and contributors. Content Manager can be used as a repository for Document Manager.

The capabilities of Document Manager include the following:

� Compound document support � Bulk document loading � Rules-based document life cycle management� Desktop application integration � Support for engineering file formats � Rendition services � Remote printing/plotting � Process management � Automated notification (via e-mail or instant message)

Since Document Manager manages the complete life cycle of business documents, it becomes part of government (e-government) solutions. Document Manager helps government departments reduce paper-based processes and redundant data entries.

2.2.3 IBM DB2 Records ManagerIBM DB2 Record Manager (Record Manager) is used to supply record management solutions through file planning and record life cycle support.

A generic record structure can be considered as a file containing the following:

� Label� Primary electronic and/or physical objects� Metadata with pointers to the objects � Status and processing information such as status notes and/or annotations

A generic record can be used, for example, to implement a virtual city hall identity card service.

2.2.4 IBM DB2 Content Manager Information Integrator for Content IBM DB2 Content Manager Information Integrator for Content (Information Integrator for Content) is used to access real time content from distributed sources and deliver that information through a federated interface for applications


or through client solutions. The connection to different back ends is implemented through connectors. The Information Integrator for Content framework has a consistent programming interface across all supported connectors for search and access. The connectors include the federated connector (FED connector) that searches against all federated content and the Content Manager connector (ICM connector) that searches against Content Manager content. With Information Integrator for Content System Administration Client, you can define federated search templates which can be used by the Content Manager application and LWWCM application along with the federated connector to access federated content, including Content Manager data. Refer to Chapter 7, “Publishing Content Manager content” on page 115 for more details on how LWWCM publishes Content Manager content with the connectors and the search templates.

Figure 2-2 shows the architecture for Information Integrator for Content.

Figure 2-2 Information Integrator for Content architecture

CM Commonstore for SAP& Notes

Browser Client

Java/C++Notes Client

Backend

Workstation

DB2DataJoiner

ODBCJDBC

Extended Search:Notes,Files,Web

IP/390 VI/400Domino.Doc

BIInformation

CatalogSAP

FileNETDocumentum

OthersMQSWFCMv7

TIE

RMLS

Version 8Content Manager

Exch

ang e

CMOnDemand

Lotu

s N

o te s

BusinessObjectOLAP

Content ConnectConnectors

Domino Extended Search

LSX, Domino ServerPages

extended search links

Java, C++, ActiveX, Dynamic Server PagesCC/DESLink

Connector Connector ... ConnectorConnector

Federated Search (Connector) Workflow

Information Mining

Java, Beans, Servlets, JSP C++, ActiveX*, ASP

Categorization Clustering

Summarization Feature Extraction

...

Connector

Search RetrieveUpdateView Workpacket Worklist

Workflow SearchWorknodeMiddle -Tier


2.2.5 IBM DB2 Content Manager OnDemandIBM DB2 Content Manager OnDemand (OnDemand) is used to archive the output of “computer output to laser disk” (COLD) solutions/systems. OnDemand stores print spool files and billing reports with efficient query and retrieval capabilities. OnDemand includes the capability to store and manage different document formats for object management along with a company reporting system. Content Manager clients can also search and access the documents archived by OnDemand.

2.2.6 IBM VideoCharger (bundled with Content Manager)IBM VideoCharger (VideoCharger), bundled with Content Manager for Multiplatforms, is considered one type of Resource Manager in a Content Manager system. VideoCharger manages large media files in the Content Manager system. It stores these files as assets and handles the streaming of these files.

The media types supported by VideoCharger include MPEG1, MPEG2, MPEG, AV, QuickTime, WAV, MJPEG, H263, G723, and LBR.

In our scenario, we use Content Manager as a repository for LWWCM and for video files. In addition, we integrate VideoCharger in the solution such that within a LWWCM hosted Web site, streamed videos can be viewed.

2.2.7 IBM Tivoli Storage ManagerIBM Tivoli Storage Manager (TSM) is a client/server program. TSM is used as an automated, centrally-scheduled, policy-managed archive, back-up and space management facility for workstations and file servers. Within Content Manager, if you plan to provide long-term storage on devices other than fixed disks, TSM is required. For example, if you would like to store objects on an optical jukebox or tape drive, TSM should be installed.

2.2.8 IBM DB2 CommonStoreIBM DB2 CommonStore (CommonStore) archives e-mails, documents, and data from different applications (SAP R/3, Microsoft® Exchange, and Lotus Domino) into different back-end servers (such as Content Manager, OnDemand, and Tivoli Storage Manager). Within Content Manager, the archived e-mails, documents, and data can be retrieved or changed from Content Manager clients. Also, they can still be accessed from within the original application using CommonStore.


2.2.9 IBM Electronic Media Management System (EMMS)IBM Electronic Media Management System (EMMS) offers digital rights management. EMMS provides an industry-independent foundation for delivery of digital assets that creates new business models, enables flexible digital rights management (DRM) and helps to protect the assets through their entire life cycle.

2.2.10 IBM DB2 UDB Net Search Extender (NSE)IBM DB2 UDB Net Search Extender (NSE) is an IBM DB2 UDB feature. It is optionally used in Content Manager to add text search capabilities on objects and metadata stored in Content Manager. By using NSE, Content Manager clients or applications can perform searches on document content or Content Manager attributes and other metadata. See 10.1.2, “NSE integration within Content Manager” on page 212 for more details.

NSE search functions (supported by the Content Manager Java and C++ APIs) are:

� Word or phrase search

� Boolean search, AND, OR, NOT

� Proximity search, in the same sentence or in the same paragraph

� Fuzzy search

These are searches on similarly spelled search terms. The degree of fuzziness can be specified. The first three characters must match.

For example, a fuzzy search on “Shakespere” can return anything with “Shakespeare.”

� Wildcard search

Use this carefully. It may have a performance impact. There is an internal limit of 1000 for search term expansion.

For example, a wildcard search for “House of p%" can result in 0 hits while a wildcard search for "House of pa%" returns hits that are fewer than 1000.

� Free text search

� Ranking

� Thesaurus search

This is based on a user-defined thesaurus built with the included thesaurus tool.

� Structured document search (such as XML, HTML, GPP)


� 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 overviewIn 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.


Figure 2-3 Content Manager architecture overview

2.3.1 Library ServerThe 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





Resource ManagerLibrary Server

C++ OO API Java OO API

http / httpsSQL

http/https

eClient


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.

AuthenticationIn 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

AuthorizationWhen 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


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 modelingThe 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.

ItemThis 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

lotus workplace web content management and content manager ... · content management and content...

Documents