Lotus Workplace Web Content Management and Content Manager Working Together for LWWCM Java Edition V2 and CM V8 Only

Lotus Workplace Web Content Management and Content Manager Working Together for LWWCM Java Edition V2 and CM V8 Only

Lotus Workplace Web Content Management and Content Manager Working Together for LWWCM Java Edition V2 and CM V8 Only Using CM as a repository for LWWCM Publishing CM content to LWWCM Covering search, security, VideoCharger integration, and migration Wei-Dong Zhu Stephan Bolten Ziad Hakim Maria Elena de Leon Walter Mayer ibm.com/redbooks International Technical Support Organization Lotus Workplace Web Content Management and Content Manager Working Together September 2004 SG24-6368-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. 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). © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . ix Notices . xiii Trademarks . xiv Preface . xv The team that wrote this redbook. xv Become a published author . xvii Comments welcome. xviii Part 1. Introduction . 1 Chapter 1. Lotus Workplace Web Content Management overview. 3 1.1 Introduction . 4 1.2 LWWCM architecture . 5 1.2.1 LWWCM user interface . 7 1.3 Creating and updating Web sites . 9 1.3.1 Information Architecture (IA) . 9 1.3.2 Web page design . 9 1.3.3 Collaboration for content management and distribution . 10 1.3.4 Versioning . 11 1.3.5 Syndication . 12 1.4 Retrieving data from different sources . 12 Chapter 2. Content Manager overview . 15 2.1 Why implement an Enterprise Content Management infrastructure? . 16 2.2 Content Manager product portfolio components . 17 2.2.1 IBM Lotus Workplace Web Content Management (LWWCM) . 17 2.2.2 IBM DB2 Document Manager . 18 2.2.3 IBM DB2 Records Manager . 18 2.2.4 IBM DB2 Content Manager Information Integrator for Content. 18 2.2.5 IBM DB2 Content Manager OnDemand . 20 2.2.6 IBM VideoCharger (bundled with Content Manager) . 20 2.2.7 IBM Tivoli Storage Manager . 20 2.2.8 IBM DB2 CommonStore . 20 2.2.9 IBM Electronic Media Management System (EMMS) . 21 2.2.10 IBM DB2 UDB Net Search Extender (NSE) . 21 2.3 Content Manager architecture overview . 22 2.3.1 Library Server . 23 © Copyright IBM Corp. 2004. All rights reserved. iii 2.3.2 Resource Manager . 26 2.3.3 System Administration Client . 29 2.3.4 Content Manager clients . 30 2.3.5 How they work together . 31 2.3.6 Working with LWWCM . 32 Chapter 3. Why and when to integrate . 35 3.1 Reasons to integrate . 36 3.2 Benefits of integration . 36 3.2.1 Integrating using Content Manager as the repository . 37 3.2.2 integration of external resources. 37 3.3 Value propositions. 38 3.3.1 LWWCM . 38 3.3.2 Content Manager . 39 3.3.3 Integrated solution. 39 3.4 Advantages of CM compared to other repositories . 39 3.5 Sample scenario . 40 Chapter 4. Case study. 41 4.1 Introduction . 42 4.2 Adding the insurance option into the navigator . 43 4.2.1 Creating new options under the insurance option. 46 4.3 Creating content for the new insurance options . 48 4.3.1 Insurance workflow . 48 4.3.2 Content templates . 49 4.3.3 Insurance page design . 53 4.3.4 Creating insurance content . 56 4.4 Retrieving data from external sources into insurance content . 58 4.5 Troubleshooting. 59 Part 2. Integration . 61 Chapter 5. Before you begin integration: pre-integration validation . 63 5.1 Introduction . 64 5.1.1 Important log files and configuration files . 64 5.1.2 Some network considerations . 65 5.2 Software requirements and case study setup . 67 5.2.1 Software requirements for LWWCM . 67 5.2.2 Software requirements for Content Manager . 68 5.2.3 Case study setup . 70 5.2.4 How to check installed software versions . 71 5.3 Validation checklist . 72 5.3.1 WebSphere Application Server and IBM HTTP Server. 72 5.3.2 LWWCM . 73 iv Lotus Workplace Web Content Management and Content Manager Working Together 5.3.3 DB2 and NSE . 74 5.3.4 IBM Content Manager and Information Integration for Content . 75 5.4 Problem determination and troubleshooting . 78 5.4.1 General hints and tips . 78 5.4.2 WebSphere Application Server . 79 5.4.3 DB2 and NSE . 80 5.4.4 IBM Content Manager and Information Integration for Content . 83 5.4.5 LWWCM . 87 Chapter 6. Using CM as a repository for LWWCM . 91 6.1 Configuring LWWCM to use CM as a data repository. 92 6.1.1 Prerequisites . 92 6.1.2 Modifying the WebSphere Application Server JVM setting. 92 6.1.3 Modifying LWWCM’s aptrixjpe.properties file . 94 6.1.4 Deleting existing indexes from the LWWCM server . 96 6.1.5 Starting LWWCM and running the initial setup . 96 6.1.6 Troubleshooting . 96 6.2 Accessing a remote Library Server database . 97 6.3 LWWCM server routing information to access CM . 99 6.3.1 The aptrixjpe.properties file. 101 6.3.2 Files cmbicmsrvs.ini and cmbds.ini. 103 6.3.3 Testing the ICM and FED connectors . ..

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    348 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us