IBMWebSphere Portal Document Manager migration tool · IBMWebSphere Portal Document Manager...

IBM WebSphere Portal Document Manager migration tool

WebSphere Portal Document Manager migration tool

Version 1.2

��

Third Edition (June 2009)

This edition applies to the IBM WebSphere Portal Document Manager migration tool and to all subsequent releasesand modifications until otherwise indicated in new editions.

A form for readers’ comments appears at the back of this publication. If the form has been removed, address yourcomments to:

International Business Machines CorporationDepartment 6R4AP.O. Box 12195Research Triangle Park, North Carolina27709-2195

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 2009.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Introduction to the migrationtool. . . . . . . . . . . . . . . . . 1Migrating to Lotus Quickr services for WebSpherePortal. . . . . . . . . . . . . . . . . 1Entitlement to the migration tool . . . . . . . 3Downloading the migration tool . . . . . . . . 3Ensuring you have the latest version . . . . . . 5

Chapter 2. Planning to use the migrationtool. . . . . . . . . . . . . . . . . 7Migration environment . . . . . . . . . . . 7Hardware and software requirements . . . . . . 8User IDs and security . . . . . . . . . . . 9Performance considerations . . . . . . . . . 11Limitations of the migration tool . . . . . . . 12

Chapter 3. Installing the migration tool 15Installing on Linux . . . . . . . . . . . . 15

Installation overview . . . . . . . . . . 15Installing the proxy connectors . . . . . . . 16Installing Tivoli Directory Integrator . . . . . 17Installing the migration tool . . . . . . . . 18Starting the servers . . . . . . . . . . . 19Verifying the installation . . . . . . . . . 20Stopping the servers . . . . . . . . . . 21Removing the migration tool . . . . . . . 22Removing the proxy connectors . . . . . . 22

Installing on Windows. . . . . . . . . . . 23Installation overview . . . . . . . . . . 23Installing the proxy connectors . . . . . . . 24Installing Tivoli Directory Integrator . . . . . 25Installing the migration tool . . . . . . . . 27Starting the servers . . . . . . . . . . . 28Verifying the installation . . . . . . . . . 28Stopping the servers . . . . . . . . . . 30Removing the migration tool . . . . . . . 30Removing the proxy connectors . . . . . . 31

Installing manually . . . . . . . . . . . . 32Installing the proxy connectors manually . . . 32Installing the migration tool manually . . . . 33Installing the Lotus Quickr migration templatemanually . . . . . . . . . . . . . . 34

Chapter 4. Configuring the migrationtool . . . . . . . . . . . . . . . . 35Setting up the administration and monitoringconsole . . . . . . . . . . . . . . . . 35Creating a Config View . . . . . . . . . . 36

Creating a Config View with a wizard . . . . 36Creating a Config View manually . . . . . . 37

Editing the properties . . . . . . . . . . . 38The properties file . . . . . . . . . . . 40

Chapter 5. Migrating content with themigration tool. . . . . . . . . . . . 49Overview of the migration process . . . . . . 49Before you migrate . . . . . . . . . . . . 59

Migration best practices . . . . . . . . . 59Extending the MIME types for WebSphere PortalV5.1 . . . . . . . . . . . . . . . . 60Cleaning the Lotus Quickr repository. . . . . 61Disabling Lotus Quickr indexing . . . . . . 62Configuring the WebSphere Portal V5.1 JCRresources . . . . . . . . . . . . . . 62Editing the parameter files . . . . . . . . 63

Using the migration tool dashboard . . . . . . 67The migration tool dashboard . . . . . . . 67Suspending a migration . . . . . . . . . 69Resuming a migration . . . . . . . . . . 69

Using the administration and monitoring console. . 70Starting a migration . . . . . . . . . . 70Stopping a migration . . . . . . . . . . 71Restarting a migration . . . . . . . . . . 72

Verifying a migration . . . . . . . . . . . 72Content metadata . . . . . . . . . . . . 73

WebSphere Portal Document Manager library toQuickr place . . . . . . . . . . . . . 74WebSphere Portal Document Manager folder toLotus Quickr folder. . . . . . . . . . . 74WebSphere Portal Document Manager documentto Lotus Quickr document . . . . . . . . 75WebSphere Portal Document Manager draft toLotus Quickr draft . . . . . . . . . . . 76WebSphere Portal Document Manager view toLotus Quickr view . . . . . . . . . . . 77

Chapter 6. Troubleshooting themigration tool. . . . . . . . . . . . 79System logs . . . . . . . . . . . . . . 79Tivoli Directory Integrator logs . . . . . . . . 79WebSphere Portal logs . . . . . . . . . . . 81Lotus Quickr logs . . . . . . . . . . . . 82Proxy connector logs . . . . . . . . . . . 83Checking the version numbers . . . . . . . . 83Changing the Tivoli Directory Integrator port . . . 84Contacting IBM support . . . . . . . . . . 84

© Copyright IBM Corp. 2009 iii

iv Migration Guide

Chapter 1. Introduction to the migration tool

The IBM® WebSphere® Portal Document Manager migration tool is a solutiondesigned to migrate library content from IBM WebSphere Portal DocumentManager V5.1 or V6.0.

Refer to the online version of this document to ensure that you have the latestupdates and information for the migration tool. You can find the online version ofthis documentation at the following URL: http://www-10.lotus.com/ldd/portalwiki.nsf/archive?openview&title=WebSphere%20Portal%20Document%20Manager%20migration%20tool&type=cat&cat=WebSphere%20Portal%20Document%20Manager%20migration%20tool&sort=I

This document provides instructions for using the migration tool to migrate fromWebSphere Portal Document Manager to Lotus® Quickr™ services for WebSpherePortal. The migration tool does not support the migration of content to LotusQuickr services for Lotus Domino®.

Additionally, this document does not provide instructions for migrating librarycontent from WebSphere Portal Document Manager to Lotus Web ContentManagement. If you use Lotus Web Content Management to integrate your librarycontent in WebSphere Portal Document Manager, you should not plan to migrateto Lotus Quickr 8.1 services for WebSphere Portal. If you are a Lotus Web ContentManagement user and would like to use an IBM migration tool solution to restorethe links to library content from WebSphere Portal Document Manager, contactyour IBM account representative for more information.

Migrating to Lotus Quickr services for WebSphere PortalYou should plan to use the WebSphere Portal Document Manager migration tool ifyou are upgrading WebSphere Portal V5.1 or V6.0 to WebSphere Portal V6.1.

Migration considerations

WebSphere Portal V6.1 no longer includes WebSphere Portal Document Manageras part of the IBM strategy to consolidate several document management solutionsinto Lotus Quickr 8.1. For this reason, the migration tool is designed to migrateyour existing WebSphere Portal Document Manager to Lotus Quickr 8.1 servicesfor WebSphere Portal.

Migrating your content to Lotus Quickr 8.1 not only provides high-performancedocument management capabilities but lets you:

Get better scaling and improved performance for WebSphere PortalBecause WebSphere Portal Document Manager runs on the same Java™

Virtual Machine (JVM) as WebSphere Portal, removing this componentimproves server performance for WebSphere Portal.

Create a specific Lotus Quickr environmentBecause WebSphere Portal Document Manager integrates into WebSpherePortal as an embedded component, it is not possible to create a separateenvironment for your document management system. However, you candesign an environment for Lotus Quickr that is independent of your

© IBM Corporation 2009 1

http://www-10.lotus.com/ldd/portalwiki.nsf/archive?openview&title=WebSphere%20Portal%20Document%20Manager%20migration%20tool&type=cat&cat=WebSphere%20Portal%20Document%20Manager%20migration%20tool&sort=I




WebSphere Portal environment. Having Lotus Quickr installed in aseparate environment provides several advantages, such as improvedperformance and increased reliability.

Have more deployment options and increased modularityLotus Quickr gives you more deployment options and increasedmodularity than WebSphere Portal Document Manager. After you installLotus Quickr, you can deploy it as a document management solution tothe users of your choice, whether your entire network or a specific groupof users.

Participate in future improvements of Lotus QuickrLotus Quickr is a product for which IBM has a long-term strategy andcommitment to further development. Migrating to Lotus Quickr gives youaccess to the Lotus Quickr community and provides you with the option toupgrade, extend, or improve as new features and benefits becomeavailable. Because Lotus Quickr is built on open architecture and services,you can take advantage of published services, solutions, and otherresources available to IBM customers and business partners.

Upgrade to the full version of Lotus Quickr easilyIBM offers a limited version of Lotus Quickr 8.1 to replace WebSpherePortal Document Manager as a document management system. However,after you install Lotus Quickr 8.1, you can easily upgrade to the fullversion of Lotus Quickr to take advantage of all the features this producthas to offer.

Access a range of capabilities with Lotus Quickr services for WebSphere PortalLotus Quickr is team collaboration software that delivers the followingcapabilities:v Robust content libraries that let you organize and share content for your

projects, your teams, or yourself.v Places where teams can collaborate using documents, blogs, wikis, tasks,

and feed generation.v A My Places page that gives users a single point of access to all the

places they can access.v Templates, themes, and skins that you can create and use to customize

your places.v Connectors that enable users to manage documents through several

applications, including IBM Lotus Notes®, IBM Lotus Sametime®, IBMLotus Symphony™, and Microsoft® Windows® Office applications.

v Document management features such as checkin and checkout, drafts,versioning, workflow, and access control.

v Extensions for custom application development.

Note: Refer to your software license agreement to review your entitlementto Lotus Quickr 8.1 and determine which features you have accessto.

Lotus Web Content Management considerations

If you use Lotus Web Content Management to integrate your library content inWebSphere Portal Document Manager, you should not plan to migrate to LotusQuickr 8.1 services for WebSphere Portal. If you are a Lotus Web ContentManagement user and would like to use an IBM migration tool solution to restorethe links to library content from WebSphere Portal Document Manager, contact

2 Migration Guide

your IBM account representative for more information.

Migration scenario

There are four IBM software offerings involved in the process of setting up themigration tool:v WebSphere Portal V5.1 or V6.0

Note: You are not required to have both WebSphere Portal V5.1 and V6.0. Themigration tool supports the migration of library content from eitherversion of WebSphere Portal.

v Lotus Quickr 8.1

Restriction: The migration tool only supports migration to Lotus Quickr 8.1services for WebSphere Portal. The migration tool does not migratelibrary content to Lotus Quickr 8.1 services for Lotus Domino.

v Tivoli® Directory Integrator V6.1.1v WebSphere Portal Document Manager migration tool

The following steps outline a typical scenario in which you use the migration toolbefore upgrading to WebSphere Portal V6.1:1. Install Lotus Quickr 8.1 services for WebSphere Portal.2. Download the WebSphere Portal Document Manager migration tool.3. Download the software to upgrade WebSphere Portal V5.1 or V6.0 to

WebSphere Portal V6.1.0.1.4. Download Tivoli Directory Integrator V6.1.1.5. Install Tivoli Directory Integrator V6.1.1.6. Install the required Tivoli Directory Integrator fix pack.7. Install the migration tool.8. Migrate all library content from either WebSphere Portal V5.1 or V6.0 to Lotus

Quickr 8.1.9. Upgrade to WebSphere Portal V6.1.0.1.

Entitlement to the migration toolThe WebSphere Portal Document Manager migration tool is intended for use byexisting WebSphere Portal customers who want to migrate library content fromeither WebSphere Portal V5.1 or V6.0 to Lotus Quickr 8.1 services for WebSpherePortal. The migration tool is not generally available as an all-purpose migrationtool. Contact IBM support for any licensing and availability queries.

Downloading the migration toolDownloading the migration tool involves selecting a download component that issuitable for your operating system. You can select the installation program foreither Linux® or Windows. Alternatively, you can download an archive thatcontains all the components necessary to install the migration tool manually.

About this task

The steps in this task provide instructions for downloading the migration tool only.Tivoli Directory Integrator and Lotus Quickr are available as separate downloadpackages. You must download Tivoli Directory Integrator and Lotus Quickr from

Chapter 1. Introduction to the migration tool 3

IBM Passport Advantage® Online. Refer to the following download documents forthe appropriate part number for Tivoli Directory Integrator or Lotus Quickr.

Note: Tivoli Directory Integrator is included in the Tivoli Directory Serverdownload.

v Windows: http://www-01.ibm.com/support/docview.wss?rs=1070&uid=swg24019671

v Linux: http://www-01.ibm.com/support/docview.wss?rs=1070&uid=swg24019661

Complete the following steps to download the migration tool:1. Open the following URL in any browser: http://www.ibm.com/support/

docview.wss?uid=swg240220832. Select the component you want to download.

v pdmmigrationtool.binSelect this component if you plan to install the migration tool on a Linuxoperating system.

v pdmmigrationtool.exeSelect this component if you plan to install the migration tool on a Windowsoperating system.

v pdmmigrationtool.zipSelect this component if you plan to perform a manual installation or areusing an operating system other than Linux or Windows. This archive filecontains the following:– PDMMigService51EAR.ear: This Enterprise Archive (EAR) file is the proxy

connector for WebSphere Portal V5.1.– PDMMigService60EAR.ear: This Enterprise Archive (EAR) file is the proxy

connector for WebSphere Portal V6.0– quickr81contentservice.ear: This Enterprise Archive (EAR) file is the proxy

connector for Lotus Quickr 8.1.– tdi4pdm2quickr.zip: This archive contains the following:

- etc: This folder contains log4j.properties.- HTML: This folder contains several files for the Web user interface.- lib: This folder contains several Java Archive (JAR) files.- param: This folder contains the following two parameter files: start.txt

and exclude.txt.- Reports: This folder contains the following two report files: report.csv

and summary.csv.- pdmmigration.properties: This properties file contains all the

configuration values for the migration tool.- pdmmigration.xml: This file contains configuration information for

Tivoli Directory Integrator.- pdmmigration-LangPack-EN.lang: This file contains error messages for

Tivoli Directory Integrator.- solution.properties: This properties file configures the Tivoli Directory

Integrator server and the Tivoli Directory Integrator administration andmonitoring console server.

- version.properties: The migration tool adds the version numbers of allthe migration components to this file when you start a migration.

v IBM_PDM_migration_tool.pdf

4 Migration Guide

http://www-01.ibm.com/support/docview.wss?rs=1070&uid=swg24019671




http://www.ibm.com/support/docview.wss?uid=swg24022083

http://www.ibm.com/support/docview.wss?uid=swg24022083

Select this component to download the migration tool documentation.v readme.txt

Select this component to download a list of the fixes and enhancementsincluded in the latest version of the migration tool.

What to do next

You are now ready to install and configure the migration tool.

Ensuring you have the latest versionThe WebSphere Portal Document Manager migration tool version 1.2 replaces allprevious versions and includes several fixes and enhancements for the migrationtool. If you have not installed the migration tool, you do not need to make anychanges. However, you should verify that the migration tool you download isversion 1.2. If you have installed a previous version of the migration tool,download and install version 1.2 to ensure that your migration from WebSpherePortal Document Manager to Lotus Quickr is successful.

Verifying the version of the migration tool

After you download the migration tool, verify the version to ensure that youinstall the latest release.

To verify the version of the migration tool in the installation program:1. Download the installation program.

v Linux: pdmmigrationtool.binv Windows: pdmmigrationtool.exe

2. Run the installation program.

The version number displays in the installation program title as follows: IBMWebSphere Portal Document Manager migration tool 1.2. If a different versionnumber displays, download the latest version online at: http://www-01.ibm.com/support/docview.wss?uid=swg24022083

To verify the version of the migration tool in the manual installation archive:1. Download the manual installation archive: pdmmigrationtool.zip.2. Extract pdmmigrationtool.zip with any compression program.3. Locate and extract tdi4pdm2quickr.zip.4. Locate the following file: version.properties.5. Open version.properties with any compression program.

The version number displays in version.properties as follows: appversion=1.2. If adifferent version number displays, download the latest version online at:http://www-01.ibm.com/support/docview.wss?uid=swg24022083

You can also verify the version of the migration tool if you have already installedand configured the migration tool and have started a migration. For instructions,refer to the following topic in this document: Checking the version numbers.

Replacing previous versions

If you have installed a previous version of the migration tool, you must removeand install the following components:

Chapter 1. Introduction to the migration tool 5

http://www-01.ibm.com/support/docview.wss?uid=swg24022083



v The WebSphere Portal V5.1 or V6.0 proxy connector.v The Lotus Quickr proxy connector.v The migration tool.

You can remove and install each of the preceding components either by using theinstallation program or by manually removing and installing the components. Thefollowing steps provide an overview of the steps necessary to remove and installthe components. Refer to the documentation for instructions to complete each ofthese steps.1. Start the Tivoli Directory Integrator config editor to populate the solutions

directory.You must start the Tivoli Directory Integrator config editor to populate thesolutions directory before you install the migration tool. The solution filesdescribe the systems, data flows, and events that define the solution. Theinstallation of the migration tool overwrites the original solution files withfiles that are required to perform a migration.

2. Stop Tivoli Directory Integrator V6.1.1.3. Stop the Tivoli Directory Integrator administration and monitoring console.4. Remove the migration tool.5. Install version 1.2 of the migration tool.6. Start Tivoli Directory Integrator V6.1.1.7. Start the Tivoli Directory Integrator administration and monitoring console.8. Remove the proxy connector for either WebSphere Portal V5.1 or V6.0.9. Install the proxy connector for either WebSphere Portal V5.1 or V6.0.

10. Remove the proxy connector for Lotus Quickr.11. Install the proxy connector for Lotus Quickr.

You are now ready to configure the migration tool and start migrating content toLotus Quickr.

6 Migration Guide

Chapter 2. Planning to use the migration tool

Planning to use the migration tool includes learning about the migrationenvironment, hardware and software requirements, and limitations of themigration tool.

Migration environmentThe process of migrating library content from WebSphere Document Manager ineither WebSphere Portal V5.1 or V6.0 to Lotus Quickr involves installing andconfiguring several components.

The following diagram illustrates a typical environment for migrating content fromWebSphere Portal Document Manager V5.1 or V6.0 to Lotus Quickr:

The illustration of the migration environment features the following components:

WebSphere Portal Document ManagerWebSphere Portal Document Manager is the source repository withinWebSphere Portal. The migration tool supports migration from WebSpherePortal Document Manager V5.1 or V6.0.

Lotus Quickr 8.1Lotus Quickr 8.1 is the target server where you migrate library contentusing the migration tool.

© IBM Corporation 2009 7

Restriction: The migration tool only supports migration to Lotus Quickr8.1 services for WebSphere Portal. The migration tool does notmigrate library content to Lotus Quickr 8.1 services for LotusDomino.

Tivoli Directory Integrator V6.1.1Tivoli Directory Integrator is the engine that the migration tool integratesinto. Tivoli Directory Integrator V6.1.1 can be deployed on the sourceserver, the target server, or on a separate server. The Tivoli DirectoryIntegrator administration and monitoring console is the user interfacethrough which you edit the solution properties and administer migrations.

WebSphere Portal Document Manager migration toolThe migration tool uses Tivoli Directory Integrator AssemblyLines to map,transform, and create attributes and objects from WebSphere PortalDocument Manager to Lotus Quickr. During installation, the migration toolalso deploys two components inside both WebSphere Portal DocumentManager and Lotus Quickr:v HTTP servlet / client

The HTTP servlet and client work together to transfer all binary filesdirectly from WebSphere Portal Document Manager to Lotus Quickr. TheHTTP servlet sends the files from WebSphere Portal Document Manager.The HTTP client receives the files and saves them in the appropriateLotus Quickr place.

v migration tool proxy connector

The proxy connectors are Web services that enable communicationbetween the source server to the migration tool and the migration tool tothe target server.

LDAP serverThe Lightweight Directory Access Protocol (LDAP) server contains lists ofusers and groups that can access the libraries and files. The LDAP servermust be shared between WebSphere Portal and Lotus Quickr to ensure alluser groups and access control permissions are restored successfully. Referto the User IDs and security topic in this document for more information.

Hardware and software requirementsBefore installing the migration tool, review the hardware and softwarerequirements.

Supported operating systems

The migration tool is supported on the following operating systems:v Microsoft Windows Server 2003 with Service Pack 2v Linux Red Hat Enterprise Version 4

Space requirements

The migration tool has the following space requirements for installation:v 50 MB to install the migration toolv 1 MB in the Tivoli Directory Integrator solutions directoryv 1 MB for the Lotus Quickr 8.1 proxy connectorv One of the following depending on your version of WebSphere Portal:

– 616 KB for the WebSphere Portal V6.0 proxy connector

8 Migration Guide

– 45 KB for the WebSphere Portal V5.1 proxy connector

Supported software versions

The migration tool supports the following software versions:v WebSphere Portal V5.1 with fix pack 5v WebSphere Portal V6.0 with fix pack 6.0.1.5v IBM WebSphere Application Server V6.0 with fix pack 6.0.2.29 is required if you

are using WebSphere Portal V6.0.v Lotus Quickr 8.1 with PK60132

Restriction: The migration tool only supports migration to Lotus Quickr 8.1services for WebSphere Portal. The migration tool does not migratelibrary content to Lotus Quickr 8.1 services for Lotus Domino.

LDAP server requirements

The migration tool requires a shared Lightweight Directory Access Protocol(LDAP) server. You must use a shared LDAP server to successfully migrate allusers, groups, and access control permissions from WebSphere Portal DocumentManager.

The recommended LDAP server to use with the migration tool is:v IBM Tivoli Directory Server V5.2.

Refer to your product documentation for supported LDAP servers for WebSpherePortal V5.1 or V6.0 and Lotus Quickr.

Tivoli Directory Integrator requirements

In addition to reviewing the hardware and software requirements for the migrationtool, you should also review the minimum product levels required for TivoliDirectory Integrator. Refer to the following site for detailed information on systemrequirements: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_6.1.1/adminguide10.htm

The migration tool requires the following fix packs for Tivoli Directory Integrator:v Tivoli Directory Integrator fix pack 5 at: http://www-01.ibm.com/support/

docview.wss?rs=697&context=SSCQGF&dc=D400&uid=swg24021727&loc=en_US&cs=UTF-8&lang=en&rss=ct697tivoli

v Tivoli Directory Integrator LA0014 at: http://www-01.ibm.com/support/docview.wss?rs=697&context=SSCQGF&q1=amc&uid=swg1IO09313

User IDs and securityBefore you migrate any content, review the information in this topic to help youensure that you do successfully migrate all user IDs and user groups and do notcompromise any confidential information.

Using a shared LDAP

The users and user groups that exist in WebSphere Portal Document Managermust also exist in Lotus Quickr. For this reason, you must use a sharedLightweight Directory Access Protocol (LDAP) server to successfully migratecontent from WebSphere Portal Document Manager to Lotus Quickr.

Chapter 2. Planning to use the migration tool 9

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_6.1.1/adminguide10.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_6.1.1/adminguide10.htm

http://www-01.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=D400&uid=swg24021727&loc=en_US&cs=UTF-8&lang=en&rss=ct697tivoli



http://www-01.ibm.com/support/docview.wss?rs=697&context=SSCQGF&q1=amc&uid=swg1IO09313


If the same set of user IDs and user groups do not exist in both WebSphere PortalDocument Manager and Lotus Quickr, users cannot access private content, such asdrafts, in the new Lotus Quickr place. In addition, users are able to access librarycontent for which they are not authorized to access.

The migration tool does not create user IDs and user groups in the target server.The migration tool only transfers the user IDs and user groups to the target server.For example, during a migration the migration tool creates a new Lotus Quickrthat corresponds to an existing library in WebSphere Portal Document Manager.The migration tool adds several user roles to the new Lotus Quickr place, such asthe manager user role. The migration tool transfers all the user IDs that areassigned to the manager role from WebSphere Portal Document Manager to thenew Lotus Quickr place. If these user IDs do not exist in the LDAP server forLotus Quickr before the migration takes place, the migration tool cannot add theuser IDs to the user role. In this case, the resulting Lotus Quickr place does notcontain the same user roles that exist in the WebSphere Portal Document Managerlibrary.

Changing the default user ID and password

After you install and first start the Tivoli Directory Integrator administration andmonitoring console, you must enter the default user ID and password. The defaultuser ID is superadmin. The default password is secret. For security reasons youshould change the password after you log in the first time. To change the defaultpassword, do the following:1. Log in to the administration and monitoring console with the default user ID

and password.

Note: You must first install Tivoli Directory Integrator and start theadministration and monitoring console server. Refer to the Installing themigration tool section in this document for detailed information.

2. Select User Preferences → Change Password.3. Enter the password and click OK.

Specifying administrator user IDs

To successfully migrate content, the migration tool requires two differentadministrator user IDs in the file: pdmmigration.properties. You must specify anadministrator user ID for the version of WebSphere Portal that you are using andan administrator user ID for Lotus Quickr.

The administrator user ID for WebSphere Portal must have sufficient privileges toread, write, create, and delete any content in the libraries you want to migrate.

The administrator user ID for Lotus Quickr must also have sufficient privileges toread, write, create, and delete any content in the Quickr place that the migrationtool creates during a migration. The administrator user ID that you specify forLotus Quickr becomes the default user ID for certain metadata attributes that donot exist in the source server, but must exist in the target server. In addition, theadministrator user ID that you specify for Lotus Quickr becomes the default userID for dormant users whose content still resides in the source library, but whoseuser IDs no longer exist in the LDAP server.

10 Migration Guide

Protecting property values

When you edit the migration properties file (pdmmigration.properties) in theadministration and monitoring console, select Protect this value to encrypt allpasswords. After you protect the password values, the passwords display asencrypted strings in the properties file.

Protecting sensitive information in the logs

Depending on the logging level that you specify, the logs for the migration toolmight contain sensitive information such as user IDs, file names, and directorypaths. However, log files never contain passwords. Do not reveal logginginformation to unauthorized users to ensure the protection of sensitive information.

Ensuring content security after a migration

Completely removing the migration tool and all components ensures security ofyour library content after a migration is complete. The migration tool proxyconnectors might enable unauthorized users to connect and make calls to either theWebSphere Portal server or the Lotus Quickr server if you do not remove themafter you finish migrating content.

Another important step towards ensuring content security after a migration isstopping both the Tivoli Directory Integrator server and the administration andmonitoring console server before you remove each server. By stopping theseservers before you remove them, you ensure that the servers do not keep anycopies of the project files in the system memory.

Refer to the Installing the migration tool section in this document for moreinformation.

Performance considerationsPerformance considerations help you in plan to use the migration tool efficiently.Review the information in this topic to learn about the time required for anaverage migration and other considerations that impact the performance of themigration tool.

Calculating the time for a migration

Calculating the time for a migration helps you determine how long your migrationwill take. Based on an average document size of 100KB to 2MB, the migration tooltransforms and transfers approximately 2,000 documents per hour. This migrationrate equates to 1.8 seconds per document. However, the amount of time necessaryto migrate your content from WebSphere Portal Document Manager to LotusQuickr depends on many variables such as your server configuration, networkconditions, the amount of content in the source repository, and the average size ofyour documents.

Disabling Lotus Quickr indexing

By default, Lotus Quickr has a maintenance task to index the content repositoryevery 60 minutes. When Lotus Quickr indexes the content repository, thedocuments and other files become available to display in the search results. If yourmigration is likely to take several hours, you should disable this maintenance taskso that indexing of the Lotus Quickr repository does not occur during a migration.


Otherwise, the indexing task increases the time that it takes to complete amigration. Refer to the Disabling Lotus Quickr indexing topic in this document forinstructions.

Note: It may take some time to rebuild the indexes when you enable indexingafter the migration completes.

Limitations of the migration toolReview the limitations of the migration tool before first use to avoid errors andprevent the loss of data.

The migration tool installation program cannot install the proxy connector onmultiple instances of Lotus Quickr in a clustered environment.

The migration tool installation program can install the proxy connector ononly a single instance of Lotus Quickr. If you have a clustered LotusQuickr environment, you must install the proxy connector manually. Referto the Installing the proxy connectors manually topic in this document forinstructions.

The migration tool does not synchronize library content between Lotus Quickrand WebSphere Portal.

The migration tool does not automatically synchronize library content ifyou move, delete, or rename documents in WebSphere Portal DocumentManager after a migration. If you move or rename a document inWebSphere Portal Document Manager after a migration and include thepath to the document in a second migration, the document is created twicein the Lotus Quickr place. If you change a library description aftermigrating that library and include that library in a second migration, thelibrary is created twice in Lotus Quickr.

When performing subsequent migrations, the migration tool overwritesolder versions of documents that you update in WebSphere PortalDocument Manager. If you edit and approve document drafts inWebSphere Portal Document Manager so that the draft becomes the activeversion of the document, the migration tool overwrites the older version ofthe document in the target server. However, because the migration tooldoes not synchronize library content, the document draft from the previousmigration remains in the target server. To prevent the loss of data,manually delete document drafts in the target server if a document draft isupdated and approved in the source server.

Propagation and inheritance blocks do not restore for the manager role.

Because Lotus Quickr does not allow propagation and inheritance blockson the manager role, the migration tool does not migrate these blocks.

The migration tool does not migrate custom metadata for WebSphere PortalV5.1.

The migration tool only supports migration of the metadata attributeslisted in this document.

The migration tool provides the default user ID for dormant users.

A dormant user is a user ID that is specified as a value in an attribute, butdoes not exist in the LDAP directory. For example, documents might havea dormant user ID that is specified in the Last modifier attribute, whichmeans that the last user to modify the document no longer exists in the

12 Migration Guide

LDAP directory. The migration tool replaces the dormant user ID with thedefault user ID, which is the user ID of the administrator who performsthe migration. Refer to the Overview of the migration process and Contentmetadata topics in this document for more information.

The migration tool does not synchronize deleted users in WebSphere PortalDocument Manager after a migration.

The migration tool does not update user roles in WebSphere PortalDocument Manager when you delete users from a user role after amigration. If you delete a user from a user role in WebSphere PortalDocument Manager after a migration, you must manually delete that userfrom the role in Lotus Quickr.

The migration tool does not update changes to submitted drafts when anapprover, who is not the draft creator, makes changes to a draft.

If a draft approver changes a submitted draft, and that approver is not thecreator of the draft, the migration tool does not update the changes to thedraft in subsequent migrations. For example, if you migrate a submitteddraft successfully, then the creator makes changes to the draft inWebSphere Portal Document Manager and you migrate the same draft asecond time, the changes are migrated successfully. However, if anapprover, who is not the creator, changes a submitted draft that you havealready migrated successfully, the changes to the draft do not migratesuccessfully.

The migration tool does not change the status of a draft from submitted torejected in subsequent migrations if you do not add the default user ID to theapprover group.

If you successfully migrate submitted drafts, then reject a submitted draftin WebSphere Portal Document Manager and perform a subsequentmigration, the draft appears as a submitted draft, not a rejected draft, inLotus Quickr. To resolve this limitation, the migration tool uses the defaultuser ID, which is the user ID of the administrator who performs themigration, to reject the drafts during the migration. However, you mustadd the administrator user ID to the approver group before you performany subsequent migrations.

The migration tool overwrites all previously migrated content when you restart amigration or perform subsequent migrations.

When you restart a migration because the migration tool encounters anerror, or when you perform a subsequent migration, the migration toolstarts migrating all content from the root of the WebSphere PortalDocument Manager repository. The migration tool does not compare theversions of documents in WebSphere Portal Document Manager and LotusQuickr for changes. If you have made any changes or edits to migrateddocuments in Lotus Quickr, the migration tool overwrites the changes withthe version of the document as it exists in WebSphere Portal DocumentManager.

To prevent the migration tool from overwriting content or from migratingthe entire source repository, you can use the start or exclude parameterfiles. The start parameter file lets you specify a particular path within alibrary to start a migration. The exclude parameter file lets you specifylibrary paths to content that you want to exclude from a migration. Referto the following topics in this document for more information: The startparameter file and The exclude parameter file.


During a migration the last modified attribute becomes the date when youperform the migration, rather than the date when the document was lastchanged in WebSphere Portal Document Manager.

For all documents that you migrate, Lotus Quickr updates the lastmodified date to the date when you perform the migration, replacing thedate when users last edited or changed the documents in WebSpherePortal Document Manager.

14 Migration Guide

Chapter 3. Installing the migration tool

Installing the migration tool involves installing and setting up prerequisitesoftware and following steps in an installation program. You can install themigration tool on either Linux or Windows to migrate content from WebSpherePortal V5.1 or V6.0 to Lotus Quickr 8.1.

Installing on LinuxThe topics in this section provide detailed instructions to guide you throughinstalling the migration tool on Linux.

Installation overviewReview the following information before you begin installing any of the migrationtool components to ensure a successful installation.

Steps to install the WebSphere Portal Document Managermigration tool

The following list shows each step of the installation process:1. Install the proxy connector on WebSphere Portal.2. Install the proxy connector on Lotus Quickr.3. Install Tivoli Directory Integrator.4. Start the Tivoli Directory Integrator Config Editor.5. Install the WebSphere Portal Document Manager migration tool.6. Start the Tivoli Directory Integrator administration and monitoring console.7. Start the Tivoli Directory Integrator server.8. Verify the installation.

Migration tool components

To successfully install the migration tool, you must install the followingcomponents:v WebSphere Portal proxy connector

The migration tool supports the migration of content from either WebSpherePortal V5.1 and V6.0. You should choose the proxy connector that corresponds tothe version of WebSphere Portal that you have installed. You do not need toinstall both proxy connectors.

v Lotus Quickr proxy connectorv The migration tool

Important:

1. The migration tool does not let you install all the components at thesame time. You must install each component individually.

2. You cannot install the proxy connectors from a remote server.Before you install the proxy connector you must copy theinstallation program to the server where you want to install theproxy connector. For example, before you can install a proxyconnector on WebSphere Portal, you must copy the installation

© Copyright IBM Corp. 2009 15

program to the server where you have WebSphere Portal installed.You cannot install the proxy connector for WebSphere Portal fromthe server where you have Lotus Quickr installed.

Installing the proxy connectorsInstalling the proxy connectors involves using a wizard that guides you throughthe installation process. Follow the steps in this section to install the migration toolproxy connectors on a Linux operating system.

Before you begin

Ensure that you have the following servers configured and running:v WebSphere Portal V5.1 or V6.0v Lotus Quickr 8.1v Lightweight Directory Access Protocol (LDAP)

About this task

The following steps provide detailed instructions to guide you through the processof installing the migration tool proxy connectors with the installation program. Ifyour environment is very complex, you may need to install the proxy connectorsmanually. Refer to the Installing manually topics in this document for instructions.1. Launch the installation program: pdmmigrationtool.bin2. Review the introduction page and click Next.3. Specify an installation directory and click Next. The default directory is:

root/PDM2QuickrMigrationTool 1.2 The installation program creates IBMlicense files, uninstaller program, and log files in the installation directory.

4. Select one of the following components to install and click Next:v WebSphere Portal V6.0 proxy connector

This component installs the Web service Enterprise Archive (EAR) file onWebSphere Portal V6.0.

v WebSphere Portal V5.1 proxy connector


v Lotus Quickr 8.1 proxy connector

This component installs the Web service Enterprise Archive (EAR) file onLotus Quickr 8.1.

5. Specify the directory where IBM WebSphere Application Server is installedand click Next. For example, /opt/IBM/WebSphere/AppServer

6. Enter an administrator user ID with sufficient access rights to install the EARfile on WebSphere Application Server and click Next. For example, wpsadmin.

7. Enter the password that corresponds to the user ID and click Next.8. Specify a valid port number for the SOAP connector if it is different from the

default value.9. Select Yes if you want to make the EAR file available in the installation

directory on your system and click Next. Selecting this option lets you easilylocate the appropriate EAR file if it becomes necessary to install the proxyconnector manually. Manually installing the proxy connector involves loggingin to the WebSphere Application Server administration console and selectingthe EAR file on your system directory. The Pre-Installation Summary pagedisplays.

16 Migration Guide

10. Review the Pre-Installation Summary page, and if all information is correct,click Install. An Install Progress page displays and, after the installation iscomplete, the Install Complete page displays.

11. Click Done.

Results

The proxy connector becomes available in the list of applications in the WebSphereApplication Server administration console.

Note: The proxy connector might not display in the list of applications if you arelogged in to the WebSphere Application Server administration consoleduring installation. You must close the WebSphere Application Serveradministration console and log in again.

What to do next

You are now ready to install Tivoli Directory Integrator.

Installing Tivoli Directory IntegratorThe migration tool uses the Tivoli Directory Integrator administration andmonitoring console as the user interface for performing a migration. Before youinstall the migration tool, you must install Tivoli Directory Integrator and fixpack5. You must also start the Tivoli Directory Integrator config editor to populate thesolutions directory with files and folders.

Before you begin

Ensure that you have the following servers configured and running:v WebSphere Portal V5.1 or V6.0v Lotus Quickr 8.1v Lightweight Directory Access Protocol (LDAP)1. Install Tivoli Directory Integrator V6.1.1.

a. Download the Tivoli Directory Integrator installation program.b. Start the installation program.c. Select Custom installation when the installation program prompts you.d. Select all installation options, including the Administration and Monitoring

Console.e. Select the option to install Embedded WebSphere Express when the

installation program prompts you.f. Enter a solutions directory when the installation program prompts you. For

example, /opt/TDI/solutions

Important: You must specify a solutions directory other than the TivoliDirectory Integrator installation directory.

g. Follow the instructions in the installation program to complete the TivoliDirectory Integrator installation.

Refer to the Tivoli Directory Integrator V6.1.1 Information Center for detailedinstallation instructions at: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_6.1.1/welcome.htm

2. Install Tivoli Directory Integrator V6.1.1 fix pack 5.

Chapter 3. Installing the migration tool 17

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_6.1.1/welcome.htm


a. Go to: http://www-01.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=D400&uid=swg24021727&loc=en_US&cs=UTF-8&lang=en&rss=ct697tivoli

b. Download 6.1.1-TIV-TDI-FP0005.c. Follow the installation instructions on the support site to install the fix pack.

Note: If you are unable to install fix pack 5, installing fix pack 4 first mightsolve this problem.

3. Install Tivoli Directory Integrator 6.1.1 LA0014.a. Go to: http://www-01.ibm.com/support/docview.wss?rs=697

&context=SSCQGF&q1=amc&uid=swg1IO09313b. Download 6.1.1-TIV-TDI-LA0014.c. Follow the installation instructions on the support site to install LA0014.

4. Start the Tivoli Directory Integrator config editor.a. Open a terminal window.b. Run the following command from the Tivoli Directory Integrator installation

directory: ./ibmditk5. Required: Click Yes when you are prompted to create the solution files.

Important: You must start the Tivoli Directory Integrator config editor andcreate the solution files before you can install the migration tool.The solution files describe the systems, data flows, and events thatdefine the solution. The installation of the migration tool overwritesthe original solution files with files that are required to perform amigration.

6. Select File → Quit to stop the Tivoli Directory Integrator config editor.7. Navigate to the Tivoli Directory Integrator solutions directory. For example,

opt/TDI/solutions8. Required: Ensure you can locate the following file: solution.properties

Important: If you cannot locate solution.properties, repeat step 3. You cannotinstall the migration tool if solution.properties does not exist in theTivoli Directory Integrator installation directory. The migration toolinstallation program looks for solution.properties in the installationdirectory. The migration tool overwrites the defaultsolution.properties file with a solution.properties file that iscustomized for the migration. If you start the config editor for thefirst time after you install the migration tool, the config editoroverwrites the customized solution.properties file, which prevents asuccessful migration.

What to do next

Now you are ready to install the migration tool.

Installing the migration toolFollow the steps in this section to install the migration tool on a Linux operatingsystem.

Before you begin1. Install the proxy connectors.2. Install Tivoli Directory Integrator V6.1.1 and fix pack 5.

18 Migration Guide






3. Start the Tivoli Directory Integrator config editor.4. Ensure WebSphere Portal is running.5. Ensure Lotus Quickr is running.

About this task

The steps in this task guide you through the process of installing the migrationtool with the installation program. If your environment is very complex, you mayneed to install the migration tool manually. Refer to the Installing manually topics inthis document for instructions.1. Launch the installation program: pdmmigrationtool.bin

Restriction: You must install the migration tool on the same machine whereyou have Tivoli Directory Integrator installed.

2. Review the introduction page and click Next.3. Specify an installation directory for the migration tool and click Next. The

default directory is: root/PDM2QuickrMigrationTool 1.2 The installationprogram creates IBM license files, uninstaller program, and a readme file at theinstallation directory.

4. Select WebSphere Portal Document Manager migration tool and click Next.This component installs files and folders, such as solution.properties, in theTivoli Directory Integrator installation directory.

5. Enter the solutions directory. For example, /opt/TDI/solutions6. Review the Pre-Installation Summary page and if all information is correct,

click Install. An Install Progress page is displayed and, after installation iscomplete, the Install Complete page displays.

7. Click Done.

What to do next

You are now ready to start the servers and verify the migration tool installation.

Starting the serversAfter you install the migration tool, run a shell script to start the Tivoli DirectoryIntegrator administration and monitoring console. You must also run a shell scriptto start the Tivoli Directory Integrator server. Running the shell scripts starts theservers and enables communication between the components. When you run theshell script to start the Tivoli Directory Integrator server, you also enter acommand to configure the server to perform a migration.1. Run the shell script to start the administration and monitoring console.

a. Open a terminal window.b. Customize the following command to comply with your system: <tdi

installation directory>/bin/amc/start_tdiamc.sh

c. Run the command.

Tip: When you first start the administration and monitoring console the URLwhere you open the console displays. Bookmark this URL for futurereference.

2. Run the shell script to start the Tivoli Directory Integrator server.a. Open a terminal window.


b. Customize the following command to comply with your system: <tdiinstallation directory>/ibmdisrv.sh -c pdmmigration.xml

v ibmdisrv.sh starts the Tivoli Directory Integrator server.v -c pdmmigration.xml configures and starts the server.

Note: If you change the solutions directory, you must update the fileibmdisrv.sh with the new directory.

c. Run the command. A message displays to inform you that the server startedsuccessfully.

What to do next

You are now ready to verify the installation.

Verifying the installationVerifying the installation ensures that the migration tool is completely installed onyour system.

About this task

The steps in this task guide you through the process of verifying the installation ona Linux operating system.1. Log in to the WebSphere Application Server administration console.2. Select Applications → Enterprise Applications.3. Locate the appropriate Enterprise Archive (EAR) file and ensure it is started.

v PDMMigService51EARThis EAR file is required for the WebSphere Portal V5.1 proxy connector.


v quickr81contentserviceThis EAR file is required for the Lotus Quickr 8.1 proxy connector.

Notes:

a. The migration tool requires two EAR files. You must installwhichever EAR files corresponds to your version of WebSpherePortal. You must also install and the EAR file for Lotus Quickr. Forexample, if you are using WebSphere Portal V5.1 you should locatethese two EAR files: PDMMigService51EAR andquickr81contentservice.

b. A green arrow in the Status column indicates that the EAR file isstarted. A red ’X’ indicates that the EAR is not started. Each EAR filemust be started to ensure that the migration tool is successfullyinstalled and running. To start an EAR file, select it and click Start.

4. Log out of the WebSphere Application Server Administration Console.5. Verify the Web Services Description Language (WSDL) endpoint for the proxy

connector on the WebSphere Portal and Lotus Quickr servers.a. Build the URL to the WSDL based on the values that you specified in

pdmmigration.properties. The URL should conform to the following format:http://<server_name>:<port_number><WSDL_address>. For example, to buildthe URL to the WSDL on the Lotus Quickr server, http://<server_name>corresponds to the following property: quickr.server.base. <port_number>

20 Migration Guide

corresponds to quickr.server.port and <WSDL_address> corresponds toquickr.webservice.wsdl. Using the example property values inpdmmigration.properties, the URL to the WSDL on the Lotus Quickr serveris: http://example_server.ibm.com:10038/quickr81contentservice/services/QuickrWebService/wsdl/QuickrWebService.wsdl.

b. Paste the URL into any Web browser. The WSDL XML displays in thebrowser if it is installed successfully. Otherwise, an error message displays.If you cannot access the WSDL XML, ensure that you have installed andstarted the corresponding EAR file. Also ensure that the URL to the WSDLis correct.

6. Navigate to the solutions directory on the server where you installed TivoliDirectory Integrator and the migration tool. For example, /TDI/solutions

7. Locate the following files and folders that the migration tool created duringinstallation:v etc: This folder contains log4j.properties.v HTML: This folder contains several files for the Web user interface.v lib: This folder contains several Java Archive (JAR) files.v param: This folder contains the following two parameter files: start.txt and

exclude.txt.v Reports: This folder contains the following two report files: report.csv and

summary.csv.v pdmmigration.propertiesv pdmmigration.xmlv pdmmigration-LangPack-EN.langv solution.propertiesv version.properties

Results

If you can locate the two EAR files in the WebSphere Application ServerAdministration Console, and access the WSDL for WebSphere Portal and LotusQuickr, and locate the files and folders in the solutions directory, the migration toolis successfully installed on your system.

Stopping the serversBefore you remove the migration tool, you must stop the servers. Stopping theservers ensures that the migration tool completely stops running and ensures youcan remove all project files when you remove the migration tool.

About this task

The following steps provide detailed instructions to stop both the Tivoli DirectoryIntegrator server and the administration and monitoring console server:1. Log in to the Tivoli Directory Integrator administration and monitoring console

to stop the Tivoli Directory Integrator server.

Restriction: You must stop the Tivoli Directory Integrator server before youstop the administration and monitoring console server.

a. Select Console Administration → Manage TDI Servers.b. Select the Tivoli Directory Integrator server.


c. Click Shutdown Server. A message confirms that you want to stop theserver.

d. Click OK to stop the server. The status of the Tivoli Directory Integratorserver changes to Stopped in the administration and monitoring console.

2. Run the shell script to stop the administration and monitoring console server.a. Open a terminal window.b. Customize the following command to comply with your system: <tdi

installation directory>/bin/amc/stop_tdiamc.sh

c. Run the command. A message informs you if the server has stoppedsuccessfully.

What to do next

Now you are ready to remove the migration tool.

Removing the migration toolRemoving the migration tool involves opening a terminal window from theinstallation directory to select and remove the migration tool. Because you mustcannot install all of the migration tool components on the same system, you mustuninstall each of the components one at a time.

Before you begin

Stop the following servers:v Tivoli Directory Integratorv Tivoli Directory Integrator administration and monitoring console

About this task

The steps in this topic guide you through the process of removing the migrationtool on a Linux operating system.1. Navigate to the installation directory of the migration tool.2. From a terminal window, run the uninstallation program.3. When the uninstall program displays, click Uninstall.4. An uninstalling page displays the progress of the uninstallation.5. Click Done.

Removing the proxy connectorsRemoving the migration tool involves opening a terminal window from theinstallation directory to select and remove the migration tool proxy connectors.Because you must cannot install the proxy connectors on the same system, youmust uninstall each proxy connectors one at a time from the server where it isinstalled.

About this task

The steps in this topic guide you through the process of removing the migrationtool proxy connectors on a Linux operating system.1. Navigate to the installation directory of the migration tool. The default

directory is: root/PDM2QuickrMigrationTool 1.2.2. From a terminal window, run the uninstallation program.

22 Migration Guide

3. When the uninstallation program displays, click Uninstall.4. An uninstalling page displays the progress of the uninstallation.5. Click Done.6. Log in to the WebSphere Application Server administration console.7. Select Applications → Enterprise Applications.8. Ensure that the proxy connector that you removed no longer exists in the list of

applications. Depending on which proxy connector you want to remove, theproxy connectors are listed in the administration console as follows:v PDMMigService51EAR

This name corresponds to the WebSphere Portal V5.1 proxy connector.v PDMMigService60EAR

This name corresponds to the WebSphere Portal V6.0 proxy connector.v quickr81contentservice

This name corresponds to the Lotus Quickr 8.1 proxy connector.If the proxy connector does not display in the administration console, then youhave successfully removed the proxy connector. If the proxy connector stilldisplays in the administration console, complete the following steps tomanually remove the proxy connector:a. In the WebSphere Application Server administration console, select the

appropriate proxy connector from the list and click Uninstall.b. Click OK to remove the proxy connector. A message informs you if the

proxy connector was uninstalled successfully.

Installing on WindowsThe topics in this section provide detailed instructions to guide you throughinstalling the migration tool on Windows.

Installation overviewReview the following information before you begin installing any of the migrationtool components to ensure a successful installation.

Steps to install the WebSphere Portal Document Managermigration tool

The following list shows each step of the installation process:1. Install the proxy connector on WebSphere Portal.2. Install the proxy connector on Lotus Quickr.3. Install Tivoli Directory Integrator.4. Start the Tivoli Directory Integrator config editor.5. Install the WebSphere Portal Document Manager migration tool.6. Start the Tivoli Directory Integrator administration and monitoring console.7. Start the Tivoli Directory Integrator server.8. Verify the installation.

Migration tool components

To successfully install the migration tool, you must install the followingcomponents:v WebSphere Portal proxy connector


The migration tool supports the migration of content from either WebSpherePortal V5.1 and V6.0. You should choose the proxy connector that corresponds tothe version of WebSphere Portal that you have installed. You do not need toinstall both proxy connectors.

v Lotus Quickr proxy connectorv The migration tool

Important:

1. The migration tool does not let you install all the components at thesame time. You must install each component individually.

2. You cannot install the proxy connectors from a remote server.Before you install the proxy connector you must copy theinstallation program to the server where you want to install theproxy connector. For example, before you can install a proxyconnector on WebSphere Portal, you must copy the installationprogram to the server where you have WebSphere Portal installed.You cannot install the proxy connector for WebSphere Portal fromthe server where you have Lotus Quickr installed.

Installing the proxy connectorsInstalling the proxy connectors involves using a wizard that guides you throughthe installation process. Follow the steps in this section to install the migration toolproxy connectors on a Windows operating system.

Before you begin

Ensure that you have the following servers configured and running:v WebSphere Portal V5.1 or V6.0v Lotus Quickr 8.1v Lightweight Directory Access Protocol (LDAP)

About this task

The following steps provide detailed instructions to guide you through the processof installing the migration tool proxy connectors with the installation program. Ifyour environment is very complex, you may need to install the proxy connectorsmanually. Refer to the Installing manually topics in this document for instructions.1. Launch the installation program: pdmmigrationtool.exe2. Review the introduction page and click Next.3. Specify an installation directory and click Next. The default directory is:

C:\Program Files\PDM2QuickrMigrationTool 1.2 The installation programcreates IBM license files, uninstaller program, and log files in the installationdirectory.

4. Select one of the following components to install and click Next:v WebSphere Portal V6.0 proxy connector





24 Migration Guide

This component installs the Web service Enterprise Archive (EAR) file onLotus Quickr 8.1.

5. Specify the directory where IBM WebSphere Application Server is installedand click Next. For example, C:\Program Files\IBM\WebSphereApplicationServer

6. Click Next to proceed.7. Enter an administrator user ID with sufficient access rights to install the EAR

file on WebSphere Application Server and click Next. For example, wpsadmin.8. Enter the password that corresponds to the user ID and click Next.9. Specify a valid port number for the SOAP connector if it is different from the

default value.10. Select Yes if you want to make the EAR file available in the installation

directory on your system and click Next. Selecting this option lets you easilylocate the appropriate EAR file if it becomes necessary to install the proxyconnector manually. Manually installing the proxy connector involves loggingin to the WebSphere Application Server administration console and selectingthe EAR file on your system directory. The Pre-Installation Summary pagedisplays.

11. Review the Pre-Installation Summary page, and if all information is correct,click Install. An Install Progress page displays and, after the installation iscomplete, the Install Complete page displays.

12. Click Done.

Results

The proxy connector becomes available in the list of applications in the WebSphereApplication Server administration console.

Note: The proxy connector might not display in the list of applications if you arelogged in to the WebSphere Application Server administration consoleduring installation. You must close the WebSphere Application Serveradministration console and log in again.

What to do next

You are now ready to install Tivoli Directory Integrator.

Installing Tivoli Directory IntegratorThe migration tool uses the Tivoli Directory Integrator administration andmonitoring console as the user interface for performing a migration. Before youinstall the migration tool, you must install Tivoli Directory Integrator and fixpack5. You must also start the Tivoli Directory Integrator config editor to populate thesolutions directory with files and folders.

Before you begin

Ensure that you have the following servers configured and running:v WebSphere Portal V5.1 or V6.0v Lotus Quickr 8.1v Lightweight Directory Access Protocol (LDAP)1. Install Tivoli Directory Integrator V6.1.1.

a. Download the Tivoli Directory Integrator installation program.


b. Start the installation program.c. Select Custom installation when the installation program prompts you.d. Select all installation options, including the Administration and Monitoring

Console.e. Select the option to install Embedded WebSphere Express when the

installation program prompts you.f. Enter a solution directory when the installation program prompts you. For

example, C:\TDI\solutions

Important: You must specify a solutions directory other than the TivoliDirectory Integrator installation directory. If you do not specify asolutions directory, the default directory on Microsoft WindowsXP is: C:\Documents and Settings\Administrator\MyDocuments\TDI.

g. Follow the instructions in the installation program to complete the TivoliDirectory Integrator installation.

Refer to the Tivoli Directory Integrator V6.1.1 Information Center for detailedinstallation instructions at: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDI.doc_6.1.1/welcome.htm

2. Install Tivoli Directory Integrator V6.1.1 fix pack 5.a. Go to: http://www-01.ibm.com/support/docview.wss?rs=697

&context=SSCQGF&dc=D400&uid=swg24021727&loc=en_US&cs=UTF-8&lang=en&rss=ct697tivoli

b. Download 6.1.1-TIV-TDI-FP0005.c. Follow the installation instructions on the support site to install the fix pack.

Note: If you are unable to install fix pack 5, installing fix pack 4 first mightsolve this problem.

3. Install Tivoli Directory Integrator 6.1.1 LA0014.a. Go to: http://www-01.ibm.com/support/docview.wss?rs=697

&context=SSCQGF&q1=amc&uid=swg1IO09313b. Download 6.1.1-TIV-TDI-LA0014.c. Follow the installation instructions on the support site to install LA0014.

4. Start the Tivoli Directory Integrator config editor.a. Select Start → Programs → IBM Tivoli Directory Integrator 6.1.1 → Start

Config Editor

5. Required: Click Yes when you are prompted to create the solution files.

Important: You must start the Tivoli Directory Integrator config editor andcreate the solution files before you can install the migration tool.The solution files describe the systems, data flows, and events thatdefine the solution. The installation of the migration tool overwritesthe original solution files with files that are required to perform amigration.

6. Select File → Quit to stop the Tivoli Directory Integrator config editor.7. Navigate to the Tivoli Directory Integrator solutions directory. For example,

C:\TDI\solutions8. Required: Ensure you can locate the following file: solution.properties

Important: If you cannot locate solution.properties, repeat step 3. You cannotinstall the migration tool if solution.properties does not exist in the

26 Migration Guide








Tivoli Directory Integrator installation directory. The migration toolinstallation program looks for solution.properties in the installationdirectory. The migration tool overwrites the defaultsolution.properties file with a solution.properties file that iscustomized for the migration. If you start the config editor for thefirst time after you install the migration tool, the config editoroverwrites the customized solution.properties file, which prevents asuccessful migration.

What to do next

Now you are ready to install the migration tool.

Installing the migration toolFollow the steps in this section to install the migration tool on a Windowsoperating system.

Before you begin1. Install the proxy connectors.2. Install Tivoli Directory Integrator V6.1.1 and fix pack 5.3. Start the Tivoli Directory Integrator config editor.4. Ensure WebSphere Portal is running.5. Ensure Lotus Quickr is running.

About this task

The steps in this task guide you through the process of installing the migrationtool with the installation program. If your environment is very complex, you mayneed to install the migration tool manually. Refer to the Installing manually topics inthis document for instructions.1. Launch the installation program: pdmmigrationtool.exe

Restriction: You must install the migration tool on the same machine whereyou have Tivoli Directory Integrator installed.

2. Review the introduction page and click Next.3. Specify an installation directory for the migration tool and click Next. The

default directory is: C:\Program Files\PDM2QuickrMigrationTool 1.2 Theinstallation program creates IBM license files, uninstaller program, and areadme file at the installation directory.

4. Select WebSphere Portal Document Manager migration tool and click Next.This component installs files and folders, such as solution.properties, in theTivoli Directory Integrator installation directory.

5. Click Next to proceed.6. Enter the solutions directory. For example, C:\TDI\solutions7. Review the Pre-Installation Summary page and if all information is correct,

click Install. An Install Progress page is displayed and, after installation iscomplete, the Install Complete page displays.

8. Click Done.

What to do next

You are now ready to start the servers and verify the migration tool installation.


Starting the serversAfter you install the migration tool, run a batch file to start the Tivoli DirectoryIntegrator administration and monitoring console. You must also run a batch file tostart the Tivoli Directory Integrator server. Running the batch files starts theservers and enables communication between the components. When you run thebatch file to start the Tivoli Directory Integrator server, you also enter a commandto configure the server to perform a migration.1. Run the batch file to start the administration and monitoring console.

a. Open a command line prompt.b. Customize the following command to comply with your system: <tdi

installation directory>/bin/amc/start_tdiamc.bat

c. Run the command.

Tip: When you first start the administration and monitoring console the URLwhere you open the console displays. Bookmark this URL for futurereference.

2. Run the batch file to start the Tivoli Directory Integrator server.a. Open a command line prompt.b. Customize the following command to comply with your system: <tdi

installation directory>/ibmdisrv.bat -c pdmmigration.xml

v ibmdisrv.bat starts the Tivoli Directory Integrator server.v -c pdmmigration.xml configures and starts the server.

Note: If you change the solutions directory, you must update the fileibmdisrv.bat with the new directory.

c. Run the command. A message displays to inform you that the server startedsuccessfully.

What to do next

You are now ready to verify the installation.

Verifying the installationVerifying the installation ensures that the migration tool is completely installed onyour system.

About this task

The steps in this task guide you through the process of verifying the installation ona Windows operating system.1. Log in to the WebSphere Application Server administration console.2. Select Applications → Enterprise Applications.3. Locate the appropriate Enterprise Archive (EAR) file and ensure it is started.



v quickr81contentserviceThis EAR file is required for the Lotus Quickr 8.1 proxy connector.

28 Migration Guide

Notes:

a. The migration tool requires two EAR files. You must installwhichever EAR files corresponds to your version of WebSpherePortal. You must also install and the EAR file for Lotus Quickr. Forexample, if you are using WebSphere Portal V5.1 you should locatethese two EAR files: PDMMigService51EAR andquickr81contentservice.

b. A green arrow in the Status column indicates that the EAR file isstarted. A red ’X’ indicates that the EAR is not started. Each EAR filemust be started to ensure that the migration tool is successfullyinstalled and running. To start an EAR file, select it and click Start.

4. Log out of the WebSphere Application Server Administration Console.5. Verify the Web Services Description Language (WSDL) endpoint for the proxy

connectors on the WebSphere Portal and Lotus Quickr servers.a. Build the URL to the WSDL based on the values that you specified in

pdmmigration.properties. The URL should conform to the following format:http://<server_name>:<port_number><WSDL_address>. For example, to buildthe URL to the WSDL on the Lotus Quickr server, http://<server_name>corresponds to the following property: quickr.server.base. <port_number>corresponds to quickr.server.port and <WSDL_address> corresponds toquickr.webservice.wsdl. Using the example property values inpdmmigration.properties, the URL to the WSDL on the Lotus Quickr serveris: http://example_server.ibm.com:10038/quickr81contentservice/services/QuickrWebService/wsdl/QuickrWebService.wsdl.

b. Paste the URL into any Web browser. The WSDL XML displays in thebrowser if it is installed successfully. Otherwise, an error message displays.If you cannot access the WSDL XML, ensure that you have installed andstarted the corresponding EAR file. Also ensure that the URL to the WSDLis correct.

6. Navigate to the solutions directory on the server where you installed TivoliDirectory Integrator and the migration tool. For example, C:\TDI\solutions

7. Locate the following files and folders that the migration tool created duringinstallation:v etc: This folder contains log4j.properties.v HTML: This folder contains several files for the Web user interface.v lib: This folder contains several Java Archive (JAR) files.v param: This folder contains the following two parameter files: start.txt and


summary.csv.v pdmmigration.propertiesv pdmmigration.xmlv pdmmigration-LangPack-EN.langv solution.propertiesv version.properties

Results

If you can locate the two EAR files in the WebSphere Application ServerAdministration Console, and access the WSDL for WebSphere Portal and Lotus


Quickr, and locate the files and folders in the solutions directory, the migration toolis successfully installed on your system.

Stopping the serversBefore you remove the migration tool, you must stop the servers. Stopping theservers ensures that the migration tool completely stops running and ensures youcan remove all project files when you remove the migration tool.

About this task

The following steps provide detailed instructions to stop both the Tivoli DirectoryIntegrator server and the administration and monitoring console server:1. Log in to the Tivoli Directory Integrator administration and monitoring console

to stop the Tivoli Directory Integrator server.

Restriction: You must stop the Tivoli Directory Integrator server before youstop the administration and monitoring console server.

a. Select Console Administration → Manage TDI Servers.b. Select the Tivoli Directory Integrator server.c. Click Shutdown Server. A message confirms that you want to stop the

server.d. Click OK to stop the server. The status of the Tivoli Directory Integrator

server changes to Stopped in the administration and monitoring console.2. Run the batch file to stop the administration and monitoring console server.

a. Open a command line prompt.b. Customize the following command to comply with your system: <tdi

installation directory>/bin/amc/stop_tdiamc.bat

c. Run the command. A message informs you if the server has stoppedsuccessfully.

What to do next

Now you are ready to remove the migration tool.

Removing the migration toolRemoving the migration tool involves opening the Windows control panel to selectand remove the migration tool. Because you must cannot install all of themigration tool components on the same system, you must uninstall each of thecomponents one at a time.

Before you begin

Stop the following servers:v Tivoli Directory Integratorv Tivoli Directory Integrator administration and monitoring console

About this task

The steps in this topic guide you through the process of removing the migrationtool on a Windows operating system.1. From the Windows start menu, select Control panel → Add or Remove

Programs. The Add or Remove Programs window displays.

30 Migration Guide

2. Select WebSphere Portal Document Manager migration tool from the list andclick Change/Remove.

3. When the Uninstall page displays, click Next.4. Review the uninstallation details and click Next. An uninstalling page displays

the progress of the uninstallation.5. Click Done.

Removing the proxy connectorsRemoving the migration tool proxy connectors involves opening the Windowscontrol panel to select and remove each of the proxy connectors. Because you mustcannot install the proxy connectors on the same system, you must uninstall eachproxy connectors one at a time from the server where it is installed.

About this task

The steps in this topic guide you through the process of removing the proxyconnectors on a Windows operating system.1. From the Windows start menu, click Control panel → Add or Remove

Programs.2. Select the following proxy connector from the list and click Change/Remove.




If you cannot locate the proxy connector that you want to remove in the list,navigate to the installation directory. For example, C:\ProgramFiles\PDM2QuickrMigrationTool 1.2. Locate the uninstallation program for theproxy connector and start the program.

3. When the Uninstall page displays, click Next.4. Review the uninstallation details and click Next to uninstall the proxy

connector. An uninstalling page displays the progress of the uninstallation.5. Click Done.6. Log in to the WebSphere Application Server administration console.7. Select Applications → Enterprise Applications.8. Ensure that the proxy connector that you removed no longer exists in the list of

applications. Depending on which proxy connector you want to remove, theproxy connectors are listed in the administration console as follows:v PDMMigService51EAR

This name corresponds to the WebSphere Portal V5.1 proxy connector.v PDMMigService60EAR

This name corresponds to the WebSphere Portal V6.0 proxy connector.v quickr81contentservice

This name corresponds to the Lotus Quickr 8.1 proxy connector.If the proxy connector does not display in the administration console, then youhave successfully removed the proxy connector. If the proxy connector stilldisplays in the administration console, complete the following steps tomanually remove the proxy connector:a. In the WebSphere Application Server administration console, select the

appropriate proxy connector from the list and click Uninstall.


b. Click OK to remove the proxy connector. A message informs you if theproxy connector was uninstalled successfully.

Installing manuallyThe topics in this section provide detailed instructions to guide you throughinstalling the migration tool manually.

Installing the proxy connectors manuallyIf you experience problems installing the proxy connectors while using theinstallation program, follow the steps in this topic to manually install eachEnterprise Archive (EAR) file for the proxy connector. Installing the EAR filesmanually involves logging in to the WebSphere Application Server administrationconsole on both the WebSphere Portal and Lotus Quickr servers and browsing tothe appropriate EAR file on your system directory.

Before you beginv Download and extract the software bundle.v Ensure that the WebSphere Portal server is running.v Ensure that the Lotus Quickr server is running.

About this task

The EAR files are required to enable the proxy connectors for communicationbetween each component and the migration tool. The steps involved in manuallyinstalling an EAR file are the same for WebSphere Portal V5.1 and V6.0 and LotusQuickr 8.1. You must repeat each step to install the EAR file individually onWebSphere Portal and Lotus Quickr.1. Log in to the WebSphere Application Server administration console.2. Select Applications → Install New Application

3. In the Path to the new application section, browse to the location of the EARfile and click Next.Locate the EAR file either in the installation directory on your system or at theroot directory of the extracted software bundle.

WebSphere Portal V5.1Select PDMMigService51EAR.ear.

WebSphere Portal V6.0Select PDMMigService60EAR.ear.

Lotus Quickr 8.1Select quickr81contentservice.ear.

4. If you are deploying the EAR file for the first time, select Generate DefaultBindings and click Next. The Install New Application window displays.

5. In the Select installation options section, select Deploy Web services andclick Next.

Tip: You must select Deploy Web services. If you do not select Deploy Webservices, an error occurs during installation.

6. In the Map modules to servers section, select WebSphere Portal from the listof servers. If you also have IBM HTTP Server installed, you must also selectthis server from the list.

32 Migration Guide

Tip: Use the Ctrl key to select multiple servers.7. Select the appropriate module for the EAR file.8. Click Apply, then Next to proceed.9. In the Map virtual hosts for Web modules section, select the appropriate Web

module and click Next.10. In the Provide options to perform the WebServices deployment section,

specify any options and click Next.11. Review the summary information and click Finish. A window displays the

progress of the installation.12. If the installation is successful, select Save to master configuration.13. Click Save.14. If you are using WebSphere Portal V6.0 or Lotus Quickr, select Applications →

Enterprise Applications and start the appropriate Web service.15. If you are using WebSphere Portal V5.1, you must restart the server using the

command line to start the Web service.

What to do next

Now, you are ready to install the migration tool.

Installing the migration tool manuallyIf you experience problems installing the migration tool while using the installationprogram, follow the steps in this topic to manually install the migration tool.

Before you beginv Download and extract the software bundle.v Install Tivoli Directory Integrator V6.1.1 and fix pack 5.v Start the Tivoli Directory Integrator config editor.

You must start the Tivoli Directory Integrator config editor to populate thesolutions directory before you begin. Refer to the Installing Tivoli DirectoryIntegrator topic in this document for more information. You should refer to thetopic in the section that is relevant to your operating system.

About this task

The following steps provide detailed information to guide you through the processof manually installing the migration tool:1. Extract the following file from the software bundle with any decompression

program: tdi4pdm2quickr.zip. The following files and folders are extracted fromthe archive:v etc: This folder contains log4j.properties.v HTML: This folder contains several files for the Web user interface.v lib: This folder contains several Java Archive (JAR) files.v param: This folder contains the following two parameter files: start.txt and


summary.csv.v pdmmigration.propertiesv pdmmigration.xmlv pdmmigration-LangPack-EN.lang


v solution.propertiesv version.properties

2. Navigate to the Tivoli Directory Integrator solutions directory. For example,C:\TDI\solutions

3. Open the folder etc in the extracted archive.4. Copy log4j.properties from the extracted archive into the folder etc in the Tivoli

Directory Integrator solutions directory.5. Copy the remaining files and folders from the extracted archive into the

solutions directory. By copying these files and folders, you configure TivoliDirectory Integrator to perform a migration.

What to do next

Now you are ready to start the servers. Refer to the Starting the servers topic in thisdocument for instructions relevant to your operating system.

Installing the Lotus Quickr migration template manuallyIf you experience problems installing the Lotus Quickr migration template, followthe steps in this topic to manually install the migration template.

Before you begin

Install the Enterprise Archive (EAR) file on the server where Lotus Quickr isinstalled.

About this task

The following steps provide detailed information to guide you through the processof manually installing the Lotus Quickr migration template:1. Log in to Lotus Quickr as an administrator.2. Select Work with Templates. The Manage Templates window displays.3. Select import.4. Browse to the following directory: <portal_server_root>/wp_profile/

installedApps/<node_name>/quickr81contentservice.ear/quickr81contentservice.war/WEB-INF/classes/com/ibm/pdm2quickr/quickr81/service

5. Select PDMMigrationTemplate.xml and click OK. PDMMigrationTemplatedisplays in the list of templates in the Manage Templates window.

34 Migration Guide

Chapter 4. Configuring the migration tool

Configuring the migration tool includes setting up the Tivoli Directory Integratoradministration and monitoring console, creating a Config View, and editing aproperties file. You must complete the steps in this section before you migratecontent from WebSphere Portal Document Manager to Lotus Quickr.

Setting up the administration and monitoring consoleWhen you log in to Tivoli Directory Integrator administration and monitoringconsole for the first time, you should follow several steps to ensure that yourenvironment is ready for migration and optimized for use.

Before you begin

Before you set up the administration and monitoring console, do the following:v Install Tivoli Directory Integrator V6.1.1 and Tivoli Directory Integrator fix pack

5.v Run the migration tool installation program.v Start the Tivoli Directory Integrator server.v Start the Tivoli Directory Integrator administration and monitoring console.1. Log in to the administration and monitoring console.

a. Open the administration and monitoring console in a Web browser. Forexample, http://<servername>:<portnumber>/tdiamc

Tip: When you first start the administration and monitoring console theURL where you open the console displays. For example,http://example_server.ibm.com:13100/tdiamc

b. Enter the user ID and password.v The default user ID is superadmin.v The default password is secret.

Important: For security reasons you should change the password after youlog in for the first time.

Tip: If you cannot log in to the administration and monitoring console, run thebatch files to stop and restart the console.a. Navigate to the Tivoli Directory Integrator installation directory. For

example, <TDI_install_dir>\bin\amc.b. Run stop_tdiamc.bat to stop the console.c. Run start_tdiamc.bat to start the console.

2. Ensure that the Tivoli Directory Integrator server is running.a. Select Console Administration → Manage TDI Servers.b. Ensure that Local TDI Server is running.

Important: The Manage TDI Servers window displays all the servers thatare connected to Tivoli Directory Integrator. The administrationand monitoring console is normally installed on the same serveras Tivoli Directory Integrator. If the administration and


monitoring console is not on the same server as Tivoli DirectoryIntegrator, ensure that the Tivoli Directory Integrator server islisted in the Manage TDI Servers window and is running.

c. Optional: Click Add to add the server that the administration andmonitoring console is on, if different to Local TDI Server.

3. Optimize the administration and monitoring console properties.a. Select Console Administration → Manage Console Properties.b. Optional: Select Set Monitor Status as the start up page. Setting Monitor

Status as the start up page brings you directly to the page where youperform and monitor migrations when you log in.

c. In the Monitor screen refresh rate field, enter 1 to change the default valueof 10 minutes. Specifying a smaller value increases the screen refresh rate,which lets you monitor the status of the migration more closely.

What to do next

Now you are ready to create a Config View.

Creating a Config ViewBefore you can migrate content to Lotus Quickr for the first time, you must createa Config View, which is a user interface that contains the components required toperform a migration. In Tivoli Directory Integrator, a Config View exposes thesolution configuration information through the user interface. When users log in toTivoli Directory Integrator administration and monitoring console to migratecontent, they open a Config View and select an AssemblyLine and start amigration. Users can also edit the solution configuration properties and monitorthe status of a migration through a Config View. Administrators can also createConfig Views for different users and restrict access to the various AssemblyLinesand properties.

The topics in this section include detailed instructions to guide you throughcreating a Config View.

Creating a Config View with a wizardUse the Quick Create Options wizard to quickly create a Config View andstreamline the task of configuring the migration tool. Using the Quick CreateOptions wizard accesses all the AssemblyLines and properties in theadministration and monitoring console. Use the Quick Create Options wizard ifyou are the administrator and the only user migrating content from WebSpherePortal Document Manager.

About this task

The steps in this task guide you through the process of creating a Config Viewwith the Quick Create Options wizard.1. Select Config Administration → Create Config Views.2. In the Enter View Details window, enter a unique name for the Config View.3. Optional: Enter an description to help you identify this Config View.4. Click Next. The Select Server/Config window displays.5. In the Server field, select Local TDI Server if you are using the local server.

Otherwise, select the appropriate server.6. In the Configs field, select Migration Tool.

36 Migration Guide

7. In the Quick Create Options section, select one of the following:v Create Config View from published solution.

This default option provides and features every component that you need tomake the migration.

v Create Config View with all AssemblyLines exposed.

This option creates a Config View that lets users perform a migration butdoes not let users edit the solution properties.

v Create Config View with all AssemblyLines and all properties exposed.

This option creates a Config View that lets users run, control, and view eachAssemblyLine and each of the solution properties.

8. Select Quick Create. An information window informs you that the ConfigWindow was created successfully.

9. Click OK.

What to do next

Now you are ready to update the properties file.

Creating a Config View manuallyYou can manually create a Config View if you do not want to use the QuickCreate Options wizard. You might choose to manually create a Config View if youplan to create Config Views for multiple users and want to restrict access tovarious AssemblyLines or properties.

About this task

The steps in this task guide you through the process of manually creating a ConfigView.1. Select Config Administration → Create Config Views.2. In the Enter View Details window, enter a unique name for the Config View.3. Optional: Enter a description to help you identify this Config View.4. Click Next. The Select Server/Config window displays.5. In the Server field, select Local TDI Server if you are using the local server.

Otherwise, select the appropriate server.6. In the Configs field, select Migration Tool.7. Click Next. The Select AssemblyLines window displays.8. Select the AssemblyLines that you want to make available in the Config View.

v WebServer

Select this AssemblyLine if you want to access the migration tooldashboard. The migration dashboard is a Web page that you use to suspendand resume migrations. The migration dashboard also provides otheradministrative functions, such as generating a list of paths to library contentin WebSphere Portal Document Manager that you can enter in theparameter files. During installation the WebServer AssemblyLine startsautomatically. By selecting this AssemblyLine, you can confirm that it isrunning through the administration and monitoring console. By selectingthe WebServer AssemblyLine, you can also stop and restart the migrationdashboard and view the log files for the migration dashboard through theadministration and monitoring console. Refer to the following topic in thisdocument for detailed information: The migration tool dashboard.

v PDM_60_Migrator

Chapter 4. Configuring the migration tool 37

Required for WebSphere Portal V6.0: Select this AssemblyLine to migratecontent from WebSphere Portal V6.0.

v PDM_51_Migrator

Required for WebSphere Portal V5.1: Select this AssemblyLine to migratecontent from WebSphere Portal V5.1.

9. Click Next. The Select Properties window displays.10. In the Select property store field, select pdmmigration-Properties. These

properties are required to perform the migration from WebSphere PortalDocument Manager to Lotus Quickr. To find out more about these properties,refer to the The properties file topic in this document.

11. Select the properties that you want to make available in the Config View andclick Next.

Required properties: To successfully migrate content, you must select all theproperties for the appropriate version of WebSpherePortal Document Manager and all the properties forLotus Quickr. For instance, if you plan to migrate fromWebSphere Portal Document Manager V5.1 you mustselect all properties that begin with both pdm.51 andquickr.

The Select Health AssemblyLine window displays.12. Select the AssemblyLine to monitor the status of the migration. Alternatively,

select None if you do not want to make a health AssemblyLine available inthe Config View.

13. Click Finish to create the Config View. An information window displays toinform you that the Config View was created successfully.

14. Click OK.

What to do next

Now you are ready to update the properties file.

Editing the propertiesAfter you create a Config View, you must edit the properties through theadministration and monitoring console. By editing the properties file, you specifycertain values that the migration tool requires to perform a migration, such as theuser IDs and passwords, the location of files, URLs for the source and targetservers, and so on.

About this task

You must edit several properties to conform with your environment before you canmigrate any content. You only need to edit the values of the properties thatcorrespond to the version of WebSphere Portal that you are using. For example, ifyou plan to migrate content from WebSphere Portal V5.1, you do not need to editthe properties for WebSphere Portal V6.0.

You do not need to edit most of the default values for the properties. However,every property must have a value. Do not delete values for a property. Otherwise,the WebSphere Portal Document Manager migration tool cannot successfullymigrate content.

38 Migration Guide

At a minimum, you must specify a value for the following properties tosuccessfully set up themigration tool:

Required properties for Lotus Quickr 8.1:v quickr.server.base

v quickr.server.port

v quickr.userID

v quickr.userPassword

Required properties if you are migrating from WebSphere Portal V5.1:v pdm.51.userID

v pdm.51.userPassword

v pdm.51.server.base

v pdm.51.server.port

Required properties if you are migrating from WebSphere Portal V6.0:v pdm.60.userID

v pdm.60.userPassword

v pdm.60.server.base

v pdm.60.server.port

Notes:

1. All Config Views on a Tivoli Directory Integrator server share the sameproperties. The changes that you make for a property are reflected ineach of the Config Views.

2. Restart the Tivoli Directory Integrator if your changes to the propertiesdo not appear to take effect.

Backup the properties file: Create a copy of pdmmigration.properties before youmake any changes. If any errors occur as a result ofthe editing process, you can replace the corruptproperties file with the copy. Otherwise, you mustrepeat the installation process. To locate the propertiesfile, navigate to the solutions directory on the serverwhere you have Tivoli Directory Integrator installed.For example, C:\TDI\solutions.

1. Log in to the Tivoli Directory Integrator administration and monitoring console.2. From the Monitor Status window, select a Config View.

Important: If this is the first time to edit the properties, ensure that you editthe properties in a Config View where all properties are available.

3. In the top right of the Config View Details window, click Manage Properties.The Manage Property Store window displays.

4. From the menu on the left, select User Property Stores. The Property storeswindow displays.

5. Select the property that you want to edit and click Edit.6. Enter a value in the Property value field and click OK.

Protecting the property value: Select Protect this value to encrypt the propertyvalue. You should select this field to protect allyour passwords.


What to do next

After you edit the properties, you are ready to migrate content from WebSpherePortal Document Manager to Lotus Quickr.Related tasks

“Setting up the administration and monitoring console” on page 35When you log in to Tivoli Directory Integrator administration and monitoringconsole for the first time, you should follow several steps to ensure that yourenvironment is ready for migration and optimized for use.

The properties fileThe properties file contains sets of name-value pairs that you must edit to conformto your environment before you migrate content from WebSphere Portal DocumentManager. You should edit the properties through the administration andmonitoring console. This topic lists and describes all the name-value pairs in theproperties file for you to reference. Refer to the Editing the properties topic in thisdocument for detailed instructions.

The name of the main properties file is as follows: pdmmigration.properties. Thename-value pairs in this file are grouped into sections according to the componentthat they correspond to. For example, the properties that Tivoli Directory Integratorrequires to connect to WebSphere Portal Document Manager V6.0 are in theWebSphere Portal Document Manager V6.0 section.

You should edit the properties through the administration and monitoring console.

Every property must have a value. If you edit the properties file, ensure that youspecify a value for each property to avoid any errors. You only need to edit thevalues for any properties that correspond to the version of WebSphere Portal thatyou are using. If you are migrating from WebSphere Portal Document ManagerV5.1, you must provide a value for all properties except for the properties thatbegin with pdm.60.*. If you are migrating from WebSphere Portal DocumentManager V6.0, you must provide a value for all properties except for the propertiesthat begin with pdm.51.*.

Note: Restart the Tivoli Directory Integrator if your changes to the properties donot appear to take effect.

The following tables list all the name-value pairs in pdmmigration.properties andprovide a description of each property:

40 Migration Guide

Table 1. General / Application

Property name Default property value Description

application.systemLog.level OFF The value of this propertydetermines whether TivoliDirectory Integrator systemlogging is enabled or not.The default value OFFdisables system logging. Ifyou want to enable TivoliDirectory Integrator systemlogging, specify one of thefollowing values other thanOFF:

v DEBUG

v INFO

v WARN

v ERROR

v FATAL

v OFF

By default, the migration toolcreates a set of rolling logfiles in the solutionsdirectory. This log file isnamed pdmmigration.log.However, you should enableTivoli Directory Integratorsystem logging if you wantto generate system logs thatyou can view remotelythrough the Tivoli DirectoryIntegrator administration andmonitoring console.

Refer to the Troubleshootingsection in this document formore information on logfiles.Level of log detail: Thelevels appear in decreasingorder of verboseness wheredebug provides the mostdetailed logging.

The size of the log fileincreases significantly withthe level of log detail thatyou specify. Depending onthe amount of content thatyou plan to migrate, log filescan quickly reach sizes ofseveral gigabytes (GB).


Table 1. General / Application (continued)


application.suspendCheck.sleep

10 Enter the number of secondsfor Tivoli DirectoryIntegrator to wait beforechecking if it can resumewhen a migration issuspended. If you suspend amigration through themigration tool dashboard,this value is the maximumamount of time you mustwait before Tivoli DirectoryIntegrator resumes themigration.

If you specify the INFO levelof logging or higher, TivoliDirectory Integrator adds aline to the log file each timeit tries to resume themigration. Therefore, if TivoliDirectory Integrator checksevery 10 seconds, it adds aline to the log file every 10seconds.

language EN Specify the language for theproperties file.Note: At present, English isthe only available languageoption.

42 Migration Guide

Table 1. General / Application (continued)


application.log.xmlString FALSE Set this property to TRUE ifyou want to include theXML-based SOAP requests inthe default logging that themigration tool. Set thisproperty to FALSE if you donot want to include theXML-based SOAP requests inthe default logging.

The XML-based SOAPrequests are the requests andresponses from the Webservices, or proxy connectors.

Do not set this property toTRUE when you specify theINFO level for systemlogging. When you specifythe INFO level for systemlogging, these XML-basedSOAP requests areautomatically recorded in thelog files. If you set thisproperty to TRUE and use theINFO level for systemlogging, the XML-basedSOAP requests are logged inthe files twice, whichincreases the size of the logfiles significantly.

migration.report.file reports\report.csv

Note: This path is relative tothe Tivoli DirectoryIntegrator solutions directory.For example,C:\TDI\solutions.

Do not change this property.The Comma SeparatedVariable (CSV) file is used togenerate a report for themigration.

applicat.webserver.port 80 Specify a port number forthe Web server. The Webserver is also known as themigration tool dashboard.The dashboard startsautomatically when you startthe Tivoli DirectoryIntegrator administration andmonitoring console.

You should change this valueif you want to use a differentport number for themigration tool dashboard.


Table 2. WebSphere Portal Document Manager V6.0

Property name Example property value Description

pdm.60.userID example_user Enter the user ID required tolog in to the WebSpherePortal Document Managerrepository. This credentialmust be valid and present inthe LDAP directory.

pdm.60.userPassword example_password Enter the password thatcorresponds to the user ID.This credential must be validand present in the LDAPdirectory.

pdm.60.server.base http://example_server.ibm.com Enter the server name forWebSphere Portal V6.0.

This property value mustinclude a protocol. Forexample, http:// or https://.

pdm.60.server.port 10038 Enter the Web service, orproxy connector, portnumber for WebSpherePortal V6.0.

pdm.60.webservice.home /PDMMigService60/services/ContentModelService

Edit this property to matchthe URL for the Web service,or proxy connector, onWebSphere Portal DocumentManager V6.0.Tip: Copy and paste thisURL into a browser. A Webservice message displays ifthe URL is valid.

pdm.60.webservice.wsdl /PDMMigService60/services/ContentModelService/wsdl/ContentModelService.wsdl

Edit this property to matchthe URL for the Web ServicesDescription Language(WSDL) file on WebSpherePortal Document ManagerV6.0.Tip: Copy and paste thisURL into a browser. The.wsdl file displays if the URLis valid.

pdm.60.http.servlet /PDMMigService60/services/ContentModelService/HttpFileServlet

Edit this property to matchthe URL of the HTTP servleton WebSphere PortalDocument Manager V6.0.

pdm.60.start param\start.txt


Specify the location ofstartPath.txt.

startPath.txt contains thepath of the subtree that youplan to migrate fromWebSphere Portal DocumentManager V6.0.

44 Migration Guide

Table 2. WebSphere Portal Document Manager V6.0 (continued)


pdm.60.exclude param\exclude.txt


Specify the location ofexclude.txt.

exclude.txt contains the pathsin WebSphere PortalDocument Manager V6.0 thatyou want to exclude fromthe migration.

Table 3. Quickr


quickr.server.base http://example_server.ibm.com Enter the server name forLotus Quickr 8.1.


quickr.server.port 10038 Enter the Web service, orproxy connector, portnumber for Lotus Quickr 8.1.

quickr.webservice.home /quickr81contentservice/services/QuickrWebService

Edit this property to matchthe URL of the Web service,or proxy connector, on LotusQuickr 8.1.Tip: Copy and paste thisURL into a browser. A Webservice message displays ifthe URL is valid.

quickr.webservice.wsdl /quickr81contentservice/services/QuickrWebService/wsdl/QuickrWebService.wsdl

Edit this property to matchthe URL of the Web ServicesDescription Language(WSDL) file on Lotus Quickr8.1.Tip: Copy and paste thisURL into a browser. The.wsdl file displays if the URLis valid.

quickr.userID example_user Enter the user ID required tolog in to Lotus Quickr. Thiscredential must be valid andpresent in the LDAPdirectory.

quickr.userPassword example_password Enter the password thatcorresponds to the user ID.This credential must be validand present in the LDAPdirectory.


Table 4. WebSphere Portal Document Manager V5.1


pdm.51.userID example_user Enter the user ID required tolog in to the WebSpherePortal Document Managerrepository. This credentialmust be valid and present inthe LDAP directory.

pdm.51.userPassword example_password Enter the password thatcorresponds to the user ID.This credential must be validand present in the LDAPdirectory.

pdm.51.server.base http://example_server.ibm.com Enter the server name forWebSphere Portal V5.1.


pdm.51.server.port 10038 Enter the Web service, orproxy connector, portnumber for WebSpherePortal V5.1.

pdm.51.webservice.home /PDMMigService51/services/ContentWebService

Edit this property to matchthe URL of the Web service,or proxy connector, onWebSphere Portal DocumentManager V5.1.Tip: Copy and paste thisURL into a browser. A Webservice message displays ifthe URL is valid.

pdm.51.webservice.wsdl /PDMMigService51/services/ContentWebService/wsdl/ContentWebService.wsdl

Edit this property to matchthe URL of the Web ServicesDescription Language(WSDL) file on WebSpherePortal Document ManagerV5.1.Tip: Copy and paste thisURL into a browser. The.wsdl file displays if the URLis valid.

pdm.51.http.servlet /PDMMigService51/services/ContentWebService/HttpFileServlet

Edit this property to matchthe URL of the HTTP servleton WebSphere PortalDocument Manager V5.1.

pdm.51.start param\start.txt


Specify the location ofstartPath.txt.

startPath.txt contains thepath of the subtree that youplan to migrate fromWebSphere Portal DocumentManager V5.1.

46 Migration Guide

Table 4. WebSphere Portal Document Manager V5.1 (continued)


pdm.51.exclude param\exclude.txt


Specify the location ofexclude.txt.

exclude.txt contains the pathsin WebSphere PortalDocument Manager V5.1 thatyou want to exclude fromthe migration.


48 Migration Guide

Chapter 5. Migrating content with the migration tool

Migrating content with the migration tool involves using the administration andmonitoring console to select an AssemblyLine to extract and transform contentfrom the source server to transfer to the target server.

Overview of the migration processThe process of migration from WebSphere Portal Document Manager to LotusQuickr services for WebSphere Portal involves transforming and transferringlibraries, folders, documents, and other content from the source server to the targetserver. This topic explains how the migration tool transforms and transfers yourcontent.

The migration tool can migrate all of the following library entities from WebSpherePortal Document Manager:v Foldersv Documentsv Versionsv Draftsv Views

In addition, the migration tool migrates locks, user roles, access controlpermissions, and metadata from WebSphere Portal Document Manager.

The Lotus Quickr migration template

The migration tool deploys a library template to Lotus Quickr during the firstmigration. Each time a library is migrated, the migration tool verifies that themigration template exists and deploys it to migration tool if it does not exist. Themigration template contains the custom user roles that the migration tool uses tomigrate the user roles and access control permissions from WebSphere PortalDocument Manager. Refer to the Migration of user roles and access control permissionssection in this topic for more information.

To ensure that the migration template is updated with any updates or newversions of the migration tool, the migration template uses a version number as thetemplate description. Before migrating a library the migration tool verifies thistemplate description as the most current version. For example, a new version ofthe migration tool becomes available before you finish migrating content fromWebSphere Portal Document Manager, the migration tool checks the migrationtemplate description that exists on Lotus Quickr. If the migration templatedescription that is on Lotus Quickr is older than the migration template availablewith the updated migration tool, the migration tool overwrites the existingmigration template on Lotus Quickr. When you restart migrating libraries, themigration tool applies the new migration template. However, any libraries that youmigrated previously keep the older migration template.

To manually verify the migration template version:1. Log in to Lotus Quickr as an administrator.


2. Select Work with Templates → PDMMigrationTemplate → Edit TemplateProperties

The version displays in the Description field.

Refer to the Installing the Lotus Quickr migration template manually topic in thisdocument for detailed instructions on manually installing the Lotus Quickrmigration template if you encounter any problems.

The main migration and migration of folders

The first step in the main migration is for the migration tool to create a list of allthe libraries that exist in WebSphere Portal Document Manager. The migration toolthen works through that list migrating each library in sequence bycompleting themigration of one library before moving on to the next.

When the migration tool migrates a library, it first creates a new Lotus Quickrplace that corresponds to the library. Then the migration tool migrates all theentities in a folder, starting from the library root. The migration tool migrates allthe entities in a folder in a single call, transforming and transferring all the entitiesin that path.

To migrate the contents in a folder, the migration tool creates the folder entity inthe appropriate Lotus Quickr place and adds the folder path to the migrationqueue. The migration tool continues migrating the other entities on the same pathas the folder. When all the entities on that path complete the migration process, themigration tool goes to the next path in the migration queue to transform andtransfer all the entities on that path.

The following diagram provides a simple example of a library:

50 Migration Guide

The following steps represent the sequence in which the migration tool transformsand transfers the contents of the library in the preceding diagram.1. The library becomes a Lotus Quickr place.2. All the entities at the root path (folder A, folder B, doc 1, doc 2, and draft 1)

migrate to the Lotus Quickr place in a single call.3. The folder A path joins the migration queue.4. The folder B path joins the migration queue.5. The migration continues from the folder B path.6. All the entities in the folder B path (doc 4 and doc 5) migrate to the Lotus

Quickr place in a single call.7. The migration continues from the folder A path.8. All the entities in the folder A path (folder C, doc 3) migrate to the Lotus

Quickr place in a single call.9. The folder C path joins the migration queue.

Chapter 5. Migrating content with the migration tool 51

10. The migration continues from the folder C path.11. All the entities in the folder C path (doc 6, doc 7, ver 1, ver 2, doc 8, and doc

8 draft) migrate to the Lotus Quickr place in a single call.12. The migration either continues with the next library or stops.

In this example, the contents in the Folder B path migrate before the Folder A pathbecause the migration tool processes the migration sequence as a stack. Stacksoperate on the principle of first in, last out. Therefore the first path that themigration tool adds to the stack is the last path that it processes.

The migration of documents

The migration tool transfers all document types from WebSphere Portal DocumentManager to Lotus Quickr. A single document can have several versions and onedraft. Versions and drafts exist as subnodes of a published document. Duringmigration, the migration tool transfers documents beginning with all the versionsof the document, then the published document, and then the draft.

For every type of document there is a corresponding MIME type. A MIME type isa specific code that identifies a particular file or type of content. For example, animage with the file extension .jpeg has the following MIME type: image/jpeg. InLotus Quickr, all documents have a metadata attribute where the MIME type isspecified. WebSphere Portal Document Manager V6.0 provides this metadataattribute for MIME types. If you are using WebSphere Portal Document ManagerV6.0, the metadata attributes for all documents migrate to Lotus Quickr. However,WebSphere Portal Document Manager V5.1 does not provide the metadataattribute for MIME types. If you are using WebSphere Portal Document ManagerV5.1, the migration tool creates the metadata attributes for MIME types based onthe document’s file extension for the following document types:

.txt Plain text

.ort Rich Text Editor

.doc Microsoft Word

.xls Microsoft Excel

.ppt Microsoft PowerPoint

.odp Open Document Presentation

.ods Open Document Spreadsheet

.odt Open Document Text

The preceding list of document types are the only document types that aresupported in WebSphere Portal Document Manager V5.1. For this reason, themigration tool only creates the MIME type metadata attribute for these documenttypes.

If you are using WebSphere Portal Document Manager V5.1 and plan to migratedocument types other than the preceding document types, specify the MIME typefor those documents before you migrate. Otherwise you might not be able to editthe documents in Lotus Quickr after you migrate. Refer to the Extending the MIMEtypes for WebSphere Portal V5.1 topic in this document for instructions.

52 Migration Guide

The migration of document versions

Document versions allow users to change documents while preserving the originalcontent. Users can create as many versions of a document as they like, so a singledocument in WebSphere Portal Document Manager often has multiple versions.

When the migration tool migrates document versions, it starts with the oldestversion of the document first. The migration tool then sequentially migrates eachof the other versions of the document. After a particular version of a documentcompletes migration, it becomes the active version of the document on the targetserver and the previous version becomes an archived version of the document. Themigration tool continues migrating versions and then lastly migrates the activeversion of the document from the source server.

One of the differences between WebSphere Portal Document Manager and LotusQuickr is that Lotus Quickr does not support multiple versions of a document thathave the same content, whereas, in WebSphere Portal Document Manager, you cancreate multiple versions of a document that have exactly the same content. Whenyou migrate multiple versions of a document that have the same content, only oneversion appears on Lotus Quickr.

The migration of document drafts

A document draft is a document in WebSphere Portal Document Manager that isnot published. Users can create a private draft and then submit the draft forapproval. After the draft successfully completes the approval process, the draftbecomes a public document.

Drafts exist as subnodes of documents in the WebSphere Portal DocumentManager Java Content Repository (JCR). These subnodes contain the actual draftinformation and replace the document when the draft is approved for publication.A user can create and save a new private draft without submitting it for approvalfor publication. In this case, the draft exists as a subnode of a skeleton documentthat is not visible in the user interface. In the preceding diagram of a library, draft1 is shown as a subnode of a skeleton document. If a user creates a private draft ofa document, the migration tool migrates the skeleton document and draft. Themigration tool also migrates the approval workflow status of the draft, regardlessof whether the user has submitted the draft for approval.

A user can also create a private draft of a published document. For example, a usermight publish a private draft and then make changes to the document and save itagain as a private draft. In this case, the draft exists as a subnode of the documentthat is publicly visible. In the preceding diagram of a library, doc 8 draft is shownas a draft of doc 8, which is a published document. If a user creates a private draftof a public document, the migration tool first transfers the public document thentransfers the private draft as a subnode of that document.

If a document in WebSphere Portal Document Manager has several versions and adraft, as represented in the preceding diagram of a library with doc 8, themigration tool migrates the versions first, then it migrates the document, and thenit migrates the draft.

The migration of workflows

Workflows refer to the process by which a draft is approved and published to thelibrary. You can enable an approver group in WebSphere Portal Document


Manager for a single library. The approver group that you enable for a libraryapplies to all drafts in that library. However, in Lotus Quickr, you can enable oneor more approval groups or users for specific document types. For example,Microsoft Word is one document type for which you can enable workflows. InLotus Quickr, approver groups can be either serial or parallel. Serial approvergroups are lists of users who must approve a draft in a sequence. Parallel approvergroups are lists of users who can approve a draft in any order.

The migration tool creates the following document type in Lotus Quickr:PDMMigrationDocumentType. This default document type uses a serial approvaltype by default. When you migrate drafts from a library that have workflowsenabled, the migration tool assigns PDMMigrationDocumentType as thedocument type to the draft. The migration tool also migrates the approver groupto Lotus Quickr for each draft and specifies serial as the approval type for theapprover group.

If you migrate libraries that have workflows enabled from WebSphere PortalDocument Manager to Lotus Quickr, the migration tool cannot migrate anychanges to documents that you make in WebSphere Portal Document Managerafter the migration. Ensure that changes are committed to all documents in alibrary that has workflows enabled before you migrate from WebSphere PortalDocument Manager to Lotus Quickr. If the library does not have workflowsenabled, the migration tool can migrate changes to documents.

The migration of views

A view is a search query that automatically shows you a related set of files. Youcreate a view by selecting certain parameters. For example, if you want to view alldocuments that are about cats, you can enter cat as a parameter. If you want toview all documents authored by John Smith, you can enter John Smith as aparameter. If you want to view all documents that are about cats and authored byJohn Smith, you can enter cat and John Smith as parameters. The more criteriayou add to a view, the more refined the result.

Both WebSphere Portal Document Manager and Lotus Quickr support views.However, Lotus Quickr has two types of views: private and shared. By default themigration tool migrates views to Lotus Quickr as shared views. You can make anymigrated views private after migration if you so choose.

During migration, the migration tool translates views so that they conform to theLotus Quickr environment. For example, a view in WebSphere Portal DocumentManager might display as follows: icm:like(icm:title, ″Example_Title″) Aftermigration, this view might display in Lotus Quickr as follows: <like><name>title</name> <value>Example_Title</value> </like>

The migration of locks

Users can lock documents in WebSphere Portal Document Manager to preventother users from modifying the content. The migration tool ensures that documentsretain the lock attribute so that a locked document in WebSphere Portal DocumentManager becomes a locked document in Lotus Quickr.

54 Migration Guide

The migration of user roles and access control permissions

Access control permissions determine whether users can create, read, update, ordelete library content and vary according to role. For example, if you assign a userto the role of Reader, you grant that user read only access to library content.

The following information explains the differences between user roles inWebSphere Portal Document Manager V5.1 and V6.0 and Lotus Quickr before andafter a migration. The main difference between the user roles in WebSphere PortalDocument Manager and Lotus Quickr exists at application level. User roles atapplication level are roles that you can edit or assign users to through the userinterface. The user roles at application level apply to the library and are inheriteddown to all the folders and documents below library level. However, there are alsodifferences between the user roles in WebSphere Portal Document Manager andLotus Quickr at Portal Access Control (PAC) level. User roles at Portal AccessControl (PAC) level are predefined roles that exist in the WebSphere Portal serverand apply to all portal resources. Because Lotus Quickr is an application that youdeploy to a WebSphere Portal server, the PAC roles apply to Lotus Quickr.However, you cannot add or edit the PAC roles.

The following lists show the user roles that are available in WebSphere PortalDocument Manager and Lotus Quickr at application level and PAC level before amigration:

Default user roles in WebSphere Portal Document Manager V5.1:

v Managerv Editorv Userv Administratorv Security Administratorv Privileged Userv Delegator

Default user roles in WebSphere Portal Document Manager V6.0:

v Managerv Editorv Contributorv Userv Administratorv Security Administratorv Privileged Userv Delegator

Default user roles for document libraries in Lotus Quickr at application level:

v Managerv Editorv Contributorv Reader

Default user roles in Lotus Quickr at Portal Access Control (PAC) level:

v Managerv Editor


v Contributorv Readerv Administratorv Security Administratorv Privileged Userv Delegator

User roles in WebSphere Portal Document Manager that do not exist in LotusQuickr document libraries at application level:

v Administratorv Security Administratorv Privileged Userv Delegator

In order to migrate and restore all the user roles from WebSphere Portal DocumentManager, the migration tool template creates four custom roles that arecombinations of user roles from Lotus Quickr application level and PAC level.Each custom user role inherits from a role at application level and is given accesscontrols at PAC level. The following table shows the four custom user roles, theinherited roles at application level, and the user roles assigned at PAC level:

Table 5. Custom user roles in Lotus Quickr at application level and PAC level

Custom user roles that themigration tool templatecreates

Inherited role at applicationlevel

Access control given at PAClevel

Administrator Manager Administrator

Security Administrator Manager Administrator

Privileged User Manager Administrator

Delegator Contributor Contributor

The migration tool template creates the four custom roles for all users and usergroups that you migrate who belong to the Administrator, Security Administrator,Privileged User, or Delegator user roles in WebSphere Portal Document Manager.The custom roles that the migration tool template creates exist at application, orlibrary, level and the inherited role at application level applies to all folders anddocuments that exist below library level.

The custom user roles in the migration template are applied to all migrations bydefault. However, you can edit each of the custom roles after a migration if youwant to make any changes. To access or edit a custom role in the migrationtemplate:1. Log in to Lotus Quickr as an administrator.2. Select Work with Templates → PDMMigrationTemplate → Manage Roles.3. Select the role you want to access or edit.4. Locate the Pages and Components Access Settings section.5. In the Library field, specify one of the default roles at application level role.6. In the All Application Pages field, specify one of the default roles at PAC level.7. In the Library (page) field, specify one of the default roles at PAC level.8. Click OK.

56 Migration Guide

In addition to the creation of custom user roles, the following actions occur to userroles and access control permissions during a migration:

Blocks on user roles migrate from WebSphere Portal Document Manager toLotus Quickr.

Any blocks that you set for user roles in WebSphere Portal DocumentManager also apply in the new Lotus Quickr place. You can also manuallyblock inheritance for each entity in the Lotus Quickr place.

Restriction: Access to each Lotus Quickr place is restricted to users andgroups on the member list. You must add users to themember list at the Lotus Quickr place level before you assignroles to the users.

The migration tool adds empty contributor roles to Quickr places whenmigrating from WebSphere Portal Document Manager V5.1.

The contributor role does not exist in WebSphere Portal DocumentManager V5.1. However, the migration tool automatically adds an emptycontributor role to the Quickr place. You can assign users to this role aftermigration.

After a migration, users who belong to the User role in WebSphere PortalDocument Manager are added to the Reader role in Lotus Quickr.

The Reader role in Lotus Quickr replaces the User role in WebSpherePortal Document Manager.

The migration tool assigns the default user ID to user roles that belong to adormant user.

If a dormant user exists for one of the default user roles for Lotus Quickrat application level, the migration tool assigns the default user ID to thatrole. A dormant user is a user ID that is specified as an attribute, but doesnot exist in the LDAP directory. The default user ID belongs to the personwho performs the migration. The default user ID corresponds to the LotusQuickr user ID and password that you specify in pdmmigration.properties.

The following tables show how migrated user roles map between application leveland Portal Access Control (PAC) level for Portal Document Manager V5.1 andV6.0:

Table 6. Role mapping for Portal Document Manager V5.1

RolePortal DocumentManager V5.1

Lotus Quickr atapplication level

Lotus Quickr at PAClevel

Administrator Administrator Administrator Administrator

SecurityAdministrator



Administrator

Delegator Delegator Delegator Contributor

Manager Manager Manager Administrator

Editor Editor Editor Editor

Priviledged user Priviledged user Priviledged user Administrator

User User Reader User

Contributor The Contributor roledoes not exist inPortal DocumentManager V5.1.

The migration tooladds an emptyContributor role.

Contributor


Table 7. Role mapping for Portal Document Manager V6.0

RolePortal DocumentManager V6.0

Lotus Quickr atapplication level

Lotus Quickr at PAClevel

Administrator Administrator Administrator Administrator




Administrator

Delegator Delegator Delegator Contributor

Manager Manager Manager Administrator

Editor Editor Editor Editor

Priviledged user Priviledged user Priviledged user Administrator

User User Reader User

Contributor Contributor Contributor Contributor

The preceding tables show the user roles as they exist at library level and as theyinherit down to folders and documents that exist on paths below library level.However, in Portal Document Manager, when you add new users to a particularrole for a folder or document on a path below library level and migrate those usersto Lotus Quickr, the user roles map on a 1 to 1 basis between the roles. Forexample, if you add a user to the Security Administrator role for a documentbelow library level in Portal Document Manager, that user becomes a SecurityAdministrator in Lotus Quickr.

For more information about user roles and access control permissions, refer to thefollowing Information Center topics:

Managing access, users, and groups at the Lotus Quickr 8.1 Information Center:http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/topic/com.ibm.lotus.quickr.admin.wpv81.doc/wpf/sec_con.htmlAssigning user access at the WebSphere Portal V5.1 Information Center:http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/doc_pap_assign.htmlDocument Manager access roles at the WebSphere Portal V6.0 Information Center:http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/doc_pdm_roles.html

The migration of propagation and inheritance

In both WebSphere Portal Document Manager and Lotus Quickr, access control isbased on user roles. Propagation refers to when a library entity acquires user roleaccess from the parent entities, which are folders or other entities that reside on thepath above another entity. Inheritance refers to when a library entity extends userrole access to the child entities, which are folders or other entities that reside onthe path below another entity. You can allow or block propagation and inheritancefor all entities, including folders, documents, and drafts.

The migration tool migrates the propagation and inheritance settings that exist inWebSphere Portal Document Manager to Lotus Quickr.

Because you cannot block propagation and inheritance on the Manager user role inLotus Quickr, the migration tool does not migrate any blocks on that exist onManager user roles in WebSphere Portal Document Manager.

58 Migration Guide

http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/topic/com.ibm.lotus.quickr.admin.wpv81.doc/wpf/sec_con.html

http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/topic/com.ibm.lotus.quickr.admin.wpv81.doc/wpf/sec_con.html

http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/doc_pap_assign.html

http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/doc_pap_assign.html

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/doc_pdm_roles.html

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/doc_pdm_roles.html

For more information on working with library content in Lotus Quickr services forWebSphere Portal, refer to the Lotus Quickr Information Center at:http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/topic/com.ibm.lotus.quickr.admin.wpv81.doc/welcome_admin.html

Before you migrateBefore you migrate any content from WebSphere Portal Document Manager toLotus Quickr, complete any appropriate tasks in this section. The tasks in thissection help ensure that your environment is prepared and that your migration issuccessful.

Migration best practicesMigration best practices include tips to help you successfully migrate content fromWebSphere Portal Document Manager. You should review this topic before youstart your first migration.

Perform the migration with a user ID with administrative privileges for bothWebSphere Portal and Lotus Quickr.

To ensure all library content migrates successfully and all library content issecure, a single user with administrator rights should perform themigration. This user ID must also exist in the shared LDAP directory.

Synchronize the time on the servers.

Synchronize the time on the servers in the migration environment beforeyou migrate to ensure that you can verify a migration accurately.Synchronizing the time on the servers also helps you find errors whencomparing log files.

Certain library content, such as documents and drafts, displays in the userinterface when the value in the effective date attribute takes effect. Theeffective date attribute corresponds to the date and time when a userpublishes a document or draft. If the time on the servers is notsynchronized, you might have to wait until the effective date attributetakes effect for certain library content to display in the user interface aftera migration is complete. Use Network Time Protocol to synchronize thetime on the servers. Refer to the relevant documentation for your operatingsystem for instructions on setting the time.

Approve and publish all drafts in WebSphere Portal Document Manager beforemigrating to Lotus Quickr.

Before you migrate library content, approve and publish all drafts in thelibrary to avoid errors or the loss of data.

Use the start parameter file to increase the efficiency and speed of a migration.

When you restart a migration that has stopped, or perform a subsequentmigration, the migration tool migrates all the library content in WebSpherePortal Document Manager beginning from the root of the repository. Tosave time, you can specify all of the library paths that have successfullyand completely migrated before the migration stopped. By specifying theselibrary paths, the migration tool does not process them again, but onlyprocesses the library content that has not already migrated successfully.Refer to the following topics in this document for more information: Thestart parameter file and Using the migration tool dashboard.

Clean the Lotus Quickr repository with the XML script before you migrate.


http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/topic/com.ibm.lotus.quickr.admin.wpv81.doc/welcome_admin.html

http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/topic/com.ibm.lotus.quickr.admin.wpv81.doc/welcome_admin.html

Cleaning the Lotus Quickr repository ensures that the target server iscompletely empty and ready for you to begin the migration. Refer to theCleaning the Lotus Quickr repository in this document for instructions.

Restrict access to the WebSphere Portal Document Manager repository beforemigrating to Lotus Quickr.

Restricting access to the source repository ensures that you successfullymigrate all library content in the repository. If a user has a document thatexists in the source server open during migration, that document will notbe migrated. Also, if any changes are made to library content during amigration, those changes might not be migrated to the target server.

Ensure that Lotus Quickr does not have any libraries with the same names anddescriptions as the libraries in WebSphere Portal Document Manager.

Ensuring that there are no duplicate library names and descriptions beforeyou migrate ensures that no files are duplicated or overwritten.

Plan to migrate content outside normal business hours.

Migrating content often takes several hours. Plan to migrate contentovernight or on the weekend to ensure no users are accessing the sourcecontent.

Check all the migration log files for errors before leaving a migration to rununattended.

If you plan to start a migration and leave the migration tool runningunattended, check the migration log files to ensure no errors haveoccurred.

Verify that content is migrating successfully before leaving a migration to rununattended.

If you plan to start a migration and leave the migration tool runningunattended, open the target server and verify that content has startedmigrating.

Save the exclude and start parameter files as Unicode encoding.To ensure that the parameter files work you must save them as Unicodeencoding, not ASCII encoding.

Extending the MIME types for WebSphere Portal V5.1Before you migrate content from WebSphere Portal Document Manager V5.1 toLotus Quickr 8.1, extend the MIME types to include any non-supported documenttypes that exist in the WebSphere Portal Document Manager V5.1 repository.Otherwise, users might not be able to edit these document types in Lotus Quickrafter the migration.

Before you begin

Install the Lotus Quickr proxy connector.

About this task

The following steps provide instructions to guide you through specifying MIMEtypes if you are migrating from WebSphere Portal Document Manager V5.1. Referto the Overview of the migration process topic in this document for more informationon why you should perform this task.1. Stop the Lotus Quickr proxy connector.

60 Migration Guide

a. Log in to the WebSphere Application Server administration console on theLotus Quickr server.

b. Locate the migration tool proxy connector for Lotus Quickr:quickr81contentservice.

c. Select quickr81contentservice and click Stop.2. Navigate to the following directory on the Lotus Quickr server:

wp_profile/installedApps/<node_name>/quickr81contentservice.ear/quickr81contentservice.war/WEB-INF/classes/com/ibm/pdm2quickr/quickr81/service.

3. Locate the following file: project.properties.4. Open project.properties with any text editor.5. Enter the file extension and MIME type using this format: file extension=MIME

type. For example, for an .html file enter the following: html=text/html.

Note: Do not enter a period (.) before the file extension.6. Save and close project.properties.7. Create a backup copy of project.properties. If you reinstall the Lotus Quickr

proxy connector for any reason, the installation overwrites project.properties.8. Start quickr81contentservice in the WebSphere Application Server

administration console on the Lotus Quickr server.

Cleaning the Lotus Quickr repositoryCleaning the Lotus Quickr repository ensures that the target server is completelyempty and ready for you to start the migration. By cleaning the Lotus Quickrrepository you clear out any deleted libraries or resources that are kept persistentin the database and scheduled for deletion.

About this task

Cleaning the Lotus Quickr repository involves using an XML script through theWebSphere Portal XML configuration interface. The following steps provideinstructions on cleaning the Lotus Quickr repository. Because Lotus Quickr is builton WebSphere Portal technology, refer to the WebSphere Portal Information Centerfor instructions on using the XML configuration interface at: http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/admin/admxmlai.html1. Log in to the server where you have Lotus Quickr installed.2. Navigate to the following directory: <portal_server_root>\PortalServer\doc\xml-

samples.3. Locate the following file: Task.xml. Task.xml schedules the cleanup, or final

deletion, of resources that you mark for deletion.4. Open Task.xml with any text editor. Task.xml contains several scheduler tasks

for cleaning deleted resources. You can edit the file to uncomment the taskdefinition that you want to run. The Runs once, starts immediately taskdefinition is enabled by default.

5. Uncomment the Runs once, starts immediately task definition if it is notenabled. The following tag performs the cleanup task:<task action="create" bean="ejb/wpsSchedulerTask"/>

Where the bean attribute specifies the class name of the program that runs inthis task. The default is ejb/wpsSchedulerTask.

6. Open a command line prompt.


http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/admin/admxmlai.html



7. Customize the following command to comply with your system:<portal_server_root>\PortalServer\bin\xmlaccess.bat -in Task.xml -outoutput.xml -user <user_ID> -password <password> -url http://<server_name>:<port_number>/lotus/config

8. Run the command.

Disabling Lotus Quickr indexingBy default, Lotus Quickr has a maintenance task to index the content repositoryevery 60 minutes. When Lotus Quickr indexes the content repository, thedocuments and other files become available to display in the search results. If yourmigration is likely to take several hours, disable this maintenance task so thatindexing of the Lotus Quickr repository does not occur during a migration.Otherwise, the indexing task increases the time that it takes to complete amigration. As an alternative to completely disabling the indexing task, you canschedule the indexing task to run after your migration is finished. However, toschedule this task you must calculate the time necessary for your migration tocomplete.

About this task

The following steps provide instructions to disable or schedule Lotus Quickrindexing before you begin a migration. For information on calculating the time fora migration, refer to the Performance considerations topic in this document.1. Navigate to the following directory on the Lotus Quickr server:

<portal_server_root>/PortalServer/jcr/lib/com/ibm/icm.2. Open the following properties file with any text editor: icm.properties.3. To disable indexing, locate the following property: jcr.textsearch.enabled and

set the value of this property to false. For example,jcr.textsearch.enabled=false.

4. To schedule the indexing task to run after your migration, locate the followingproperty: jcr.textsearch.indexmaintenance.interval and set the value of thisproperty to the total number of minutes necessary to complete the migration.To ensure that the migration completes before the indexing task runs, addseveral minutes to the total number of minutes that you calculate. For example,if you calculate that 10 hours is necessary to complete the migration, specify610 as the value of this property so that the indexing task does not run for 10hours and 10 minutes.

5. Save and close icm.properties.6. Restart the Lotus Quickr server. After you complete the migration, enable Lotus

Quickr indexing by setting the values of the property to true.

Note: It may take some time to rebuild the indexes when you enable indexingafter the migration completes.

Configuring the WebSphere Portal V5.1 JCR resourcesThis topic provides instructions for an optional task to configure the WebSpherePortal V5.1 Java Content Repository (JCR) resources. If you are migrating fromWebSphere Portal V5.1, configuring the JCR resources may prevent errors.Configuring the JCR resources involves running a command that re-indexes therepository and restarts WebSphere Portal V5.1. You might configure the JCRresources if you have recently reinstalled WebSphere Portal V5.1 or have clonedyour WebSphere Portal V5.1 for the migration. Additionally, if you encounter an

62 Migration Guide

error during a migration that indicates no libraries exist in WebSphere PortalDocument Manager V5.1, configuring the JCR might resolve this error.

About this task

The following steps provide instructions to guide you through the task ofconfiguring the WebSphere Portal V5.1 JCR resources:1. Open a command line prompt to the following directory: <portal_server_root>\

PortalServer\config2. Enter the following command: WPSConfig cfg-jcr-resources.

Note: Because the WPSConfig script must authenticate with WebSphere Portalserver, you might need to specify the admininstrator user ID passwordas a value in the following file: wpconfig.properties.

3. Run the command.

Editing the parameter filesEditing the parameter files involves using Java regular expressions to specify pathsto content in WebSphere Portal Document Manager. The paths that you specify tellthe migration tool where to look for content to migrate. By default, the parameterfiles are blank so that the migration tool migrates all libraries and content thatreside in WebSphere Portal Document Manager.

The start parameter fileThe start parameter file is a text file in which you can specify a particular pathwithin a library to start a migration. Using the start parameter file is optional. Youdo not have to specify any paths in this file to successfully migrate library content.The purpose of the start parameter file is to make migrations more efficient. Forexample, if you want to restart a migration, and a large amount of data hasalready been migrated, you can specify a library path in the start parameter file torestart the migration at a point other than the root of the library.

Using the start parameter file

Review the following points before you use the start parameter file to help youavoid errors:v The start parameter file must exist. If the start parameter file does not exist, an

error occurs.v By default, you can locate the start parameter file in the param folder in the

Tivoli Directory Integrator solutions directory. For example,C:\TDI\solutions\param

v The path to the start parameter file on your system must correspond to the pathto the start parameter file that you specify in pdmmigration.properties. Thedefault value in the properties file is param\start.txt, which is relative to thesolutions directory. If you change the location of the start parameter file on yoursystem, you must edit the properties file and specify the new path to the startparameter file.

v You can specify more than one path at a time in the start parameter file.v If you want to start a migration from a subfolder within a library, you must

specify all parent folders in the path to the subfolder.v When you specify paths in the start parameter file, you must use Java regular

expressions. This topic provides examples of Java regular expressions. However


it is beyond the scope of this document to provide an exhaustive list of allpossible Java regular expressions. For more information, refer to the followingsite: http://java.sun.com/

Important: You must save the parameter file with Unicode encoding.

Editing the parameters file

To edit the start parameter file:1. Navigate to the param folder in the Tivoli Directory Integrator solutions

directory. For example, C:\TDI\solutions\param2. Locate the start parameter file. For example, start.txt3. Open the file with any text editor.4. Set the appropriate parameters for WebSphere Portal Document Manager

Tip: You can generate a list of libraries and the paths to each library with themigration tool dashboard. Using the dashboard to generate the list of librarieshelps save you time and ensures the library paths you enter in the parameterfile are correct. Refer to the following topic in this document for moreinformation: The migration tool dashboard.

Setting parameters for WebSphere Portal V5.1

To set parameters for WebSphere Portal V5.1, use paths that conform to thefollowing: /DM/<library ID>/<folder name>

If you want to start a migration from a subfolder within a library, you mustinclude all parent folders in the path to the subfolder. For example, to start amigration from Folder C and migrate all the content in that path you must specifythe following:

/DM/<library ID>/DM/<library ID>//DM/<library ID>/Folder A/DM/<library ID>/Folder A/Folder B/DM/<library ID>/Folder A/Folder B/Folder C/DM/<library ID>/Folder A/Folder B/Folder C/.*


To set parameters for WebSphere Portal V6.0, use paths that conform to thefollowing: /contentRoot/<library ID>/<folder name>

If you want to start a migration from a subfolder within a library, you mustinclude all parent folders in the path to the subfolder. For example, to start amigration from Folder C and migrate all the content in that path you must specifythe following:

/contentRoot/<library ID>/contentRoot/<library ID>//contentRoot/<library ID>/Folder A/contentRoot/<library ID>/Folder A/Folder B/contentRoot/<library ID>/Folder A/Folder B/Folder C/contentRoot/<library ID>/Folder A/Folder B/Folder C/.*

64 Migration Guide

http://java.sun.com/

Using Java regular expressions

You must use Java regular expressions (RegEx) when you specify parameters for amigration. Examples of Java regular expressions are as follows:

[^/].* Matches all entities that do not start with a forward slash (/), such asviews.

/<library ID>/[^A]Matches all entities except those that contain an uppercase A in the name.

/<library ID>/.*my_folder.*Matches all folders that contain my_folder in the name.

/<library ID>/Folder A/.*Starts the migration at Folder A.

/contentRoot/icm:libraries\[7]Starts the migration at library 7.

Tips:

1. Use a forward slash (/) to specify a file path.2. Use a backslash (\) to specify a character that you want to escape.3. Bracket characters ([ ]) denote a group as Java regular expressions. For

this reason you must use a backslash (\) to escape the Java regularexpression when you want to specify a path that would normally appearas follows: \contentRoot\icm:libraries[7].

4. It is beyond the scope of this document to provide an exhaustive list ofall possible Java regular expressions. For more information, refer to thefollowing site: http://java.sun.com/

The exclude parameter fileThe exclude parameter file is a text file in which you can specify library paths tocontent that you want to exclude from a migration. Using the exclude parameterfile is optional. You do not have to specify any paths in this file to successfullymigrate library content. You should use the exclude parameter file if there is anyspecific content in the library that you do not want to migrate. You can specify thepaths to the content that you do not want to migrate and the migration tooltransforms and transfers all other library content.

Using the exclude parameter file

Review the following points before you use the exclude parameter file to help youavoid errors:v The exclude parameter file must exist. If the exclude parameter file does not

exist, an error occurs.v By default, you can locate the exclude parameter file in the param folder in the

Tivoli Directory Integrator solutions directory. For example,C:\TDI\solutions\param

v The path to the exclude parameter file on your system must correspond to thepath to the exclude parameter file that you specify in pdmmigration.properties.The default value in the properties file is param\exclude.txt, which is relative tothe solutions directory. If you change the location of the exclude parameter fileon your system, you must edit the properties file and specify the new path tothe exclude parameter file.

v You can specify more than one path at a time in the exclude parameter file.



v When you specify paths in the exclude parameter file, you must use Java regularexpressions. This topic provides examples of Java regular expressions. Howeverit is beyond the scope of this document to provide an exhaustive list of allpossible Java regular expressions. For more information, refer to the followingsite: http://java.sun.com/

Important: You must save the parameter file with Unicode encoding.

Editing the parameters file

To edit the exclude parameter file:1. Navigate to the param folder in the Tivoli Directory Integrator solutions

directory. For example, C:\TDI\solutions\param2. Locate the exclude parameter file. For example, exclude.txt3. Open the file with any text editor.4. Set the appropriate parameters for WebSphere Portal Document Manager

Tip: You can generate a list of libraries and the paths to each library with themigration tool dashboard. Using the dashboard to generate the list of librarieshelps save you time and ensures the library paths you enter in the parameterfile are correct. Refer to the following topic in this document for moreinformation: The migration tool dashboard.


To set parameters for WebSphere Portal V5.1, use paths that conform to thefollowing: /DM/<library ID>/<folder name>

Important: The migration tool reads every parameter as a Java regular expression.For example, if you enter /DM/<library ID>/Folder A, the migrationtool reads this path as a string and excludes only the library contentthat matches /DM/<library ID>/Folder A. In this case the migrationtool does not exclude any subfolders of this path.

If you want to exclude content within a subfolder, you must specify a full path tothat subfolder. For example, to exclude all content Folder C and all content belowFolder C, specify the following:

/DM/<library ID>/Folder A/Folder B/Folder C/.*


To set parameters for WebSphere Portal V6.0, use paths that conform to thefollowing: /contentRoot/<library ID>/<folder name>

Important: The migration tool reads every parameter as a Java regular expression.For example, if you enter /contentRoot/<library ID>/Folder A, themigration tool reads this path as a string and excludes only the librarycontent that matches /contentRoot/<library ID>/Folder A. In this casethe migration tool does not exclude any subfolders of this path.

If you want to exclude content within a subfolder, you must specify a full path tothat subfolder. For example, to exclude all content Folder C and all content belowFolder C, specify the following:

66 Migration Guide


/contentRoot/<library ID>/Folder A/Folder B/Folder C/.*

Using Java regular expressions

You must use Java regular expressions (RegEx) when you specify parameters for amigration. Examples of Java regular expressions are as follows:

[^/].* Matches all entities that do not start with a forward slash (/), such asviews.

/<library ID>/[^A]Matches all entities except those that contain an uppercase A in the name.

/<library ID>/.*my_folder.*Matches all folders that contain my_folder in the name.

/<library ID>/Folder A/.*Excludes Folder A and all subfolders.

/contentRoot/icm:libraries\[7]Excludes library 7 and all content in that library.

Tips:

1. Use a forward slash (/) to specify a file path.2. Use a backslash (\) to specify a character that you want to escape.3. Bracket characters ([ ]) denote a group as Java regular expressions. For

this reason you must use a backslash (\) to escape the Java regularexpression when you want to specify a path that would normally appearas follows: \contentRoot\icm:libraries[7].

4. It is beyond the scope of this document to provide an exhaustive list ofall possible Java regular expressions. For more information, refer to thefollowing site: http://java.sun.com/

Using the migration tool dashboardUsing the migration tool dashboard lets you perform administrative tasks such asmonitoring the status of a migration and generating a list of library paths to use inthe parameter files. The migration tool dashboard also lets you suspend andresume a migration.

The migration tool dashboardThe migration tool dashboard lets you perform administrative tasks. You can usethe dashboard to suspend and resume a migration and monitor the status of amigration. You can also use the dashboard to generate a list of all the libraries thatexist in Document Manager. When you generate a list of libraries, the dashboardprovides a path to each library. You can specify these library paths in the start andexclude parameter files.

Accessing the migration tool dashboard

The dashboard starts automatically when you start the Tivoli Directory Integratoradministration and monitoring console server. You can access the dashboard withany Web browser at the following URL: http://<tdi_server_name>:<port_number>/home. For example, http://example_server.ibm.com:80/home



The dashboard uses port number 80 by default. You can change the port byspecifying a new port number in the pdmmigration.properties file. Refer to thefollowing topic in this document for more information: The properties file. If youchange the port for the dashboard, you must edit the URL to the dashboard toinclude the new port.

You can stop and restart the dashboard, and view log files, through the TivoliDirectory Integrator administration and monitoring console. However, you mustselect the WebServer AssemblyLine if you create a Config View manually. Refer tothe Creating a Config View manually topic in this document for more information.

Using the migration tool dashboard

When you open the dashboard in a Web browser, you must first select one of thefollowing AssemblyLines from the menu on the left:v WebSphere Portal Document Manager V6.0 to Lotus Quickr

Select this AssemblyLine if you are migrating content from WebSphere PortalDocument Manager V5.1 to Lotus Quickr.

v WebSphere Portal Document Manager V5.1 to Lotus Quickr

Select this AssemblyLine if you are migrating content from WebSphere PortalDocument Manager V6.0 to Lotus Quickr.

After you select the appropriate AssemblyLine, the dashboard displays in the Webbrowser. The dashboard displays the following information to enable you to easilymonitor the status of your migration:v Current path

Displays the current path in the library where the migration tool is transformingand transferring content.

v Library count

Displays the number of libraries that have migrated successfully.v Folder count

Displays the number of folders that have migrated successfully.v Document count

Displays the number of documents that have migrated successfully.v Draft count

Displays the number of drafts that have migrated successfully.v Version count

Displays the number of document versions that have migrated successfully.v View count

Displays the number of views that have migrated successfully.v Status

Displays the status of the migration.

The migration tool dashboard lets you perform specific administrative functions byclicking any of the following buttons:v Refresh

Updates the information that the dashboard displays about the migration.v Suspend

Suspends a migration that is in progress. For more information, refer to theSuspending a migration topic in this document.

68 Migration Guide

v Resume

Resumes a migration that is suspended. For more information, refer to theResuming a migration topic in this document.

Note: If the migrations stops, you cannot restart the migration by clickingResume. You must restart the migration through the administration andmonitoring console. Refer to the following topics for more information:Starting a migration and Restarting a migration.

v Generate a list of libraries

Creates a list of all the libraries in WebSphere Portal Document Manager and thepaths that correspond to each library.

v Reset

Clears the list of libraries from the dashboard.

Suspending a migrationSuspending a migration involves opening the migration dashboard in a Webbrowser to pause a migration. When a migration suspends, the migration toolcompletes any file transformations or transfers that are in progress. The migrationtool then pauses and waits to resume the migration. During suspension, themigration tool keeps contents of the migration queue in the system memory. Whenthe migration resumes after a suspension, the migration tool starts with whateveris next in the migration queue.

About this task

The steps in this task guide you through the process of suspending a migration.1. Log in to the migration dashboard.

a. Open any Web browser.b. Enter the URL to the migration dashboard. For example,

http://<servername>:80/home

Note: When you run ibmdisrv.bat to start Tivoli Directory Integrator the Webserver automatically starts. When the Web server starts, the migrationdashboard is available.

2. Ensure the migration status displays as Running.3. Click Suspend to suspend the migration.

Results

The migration status in the migration dashboard displays as Suspended.

What to do next

After you suspend a migration you can either stop the migration or resume themigration.

Resuming a migrationResuming a migration involves opening the migration dashboard in a Web browserto resume a migration after it suspends. If you resume a migration after it hassuspended, the migration tool starts transforming and transferring files beginning


with the next file in the queue before the migration paused. You cannot resume amigration after it stops. You must restart a migration using the administration andmonitoring console if a migration stops.

About this task

The steps in this task guide you through the process of resuming a migration.1. Log in to the migration dashboard.

a. Open any Web browser.b. Enter the URL to the migration dashboard. For example,

http://<servername>:80/home

Note: When you run ibmdisrv.bat to start Tivoli Directory Integrator the Webserver automatically starts. When the Web server starts, the migrationtool dashboard is available.

2. Ensure the migration status displays as Suspended.3. Click Resume to resume the migration.

Results

The migration status in the migration dashboard displays as Running.

Using the administration and monitoring consoleUsing the Tivoli Directory Integrator administration and monitoring console letsyou perform tasks such as starting, stopping, and restarting migrations. To use theTivoli Directory Integrator administration and monitoring console, you must log in,open a Config View, and select the AssemblyLine that you want to work with.

Starting a migrationStarting a migration involves logging in to the Tivoli Directory Integratoradministration and monitoring console, opening a Config View, and starting anAssemblyLine.

Before you begin1. Review the Migration best practices topic in this document.2. Customize and run the following command to start the administration and

monitoring console if it is not running: <tdi installationdirectory>/bin/amc/start_tdiamc.bat

3. Specify paths to the source content in the parameter files.

About this task

The steps in this task guide you through the process of starting a migration.1. Log in to the administration and monitoring console.


Tip: When you first start the administration and monitoring console theURL where you open the console displays.

b. Enter the user ID and password.2. Navigate to the Monitor Status window.

70 Migration Guide

a. Select Operation Status And AM.b. Select Monitor Status. The Monitor Status window displays.

3. From the Config View column, select the appropriate Config View. The ConfigView Details window displays.

4. Select the appropriate AssemblyLine for the migration. For example, if youwant to migrate content from WebSphere Portal V5.1, select PDM_51_Migrator.

5. From the Select Action menu, select Start AL.6. Click Go to start the migration.

Results

The Status column displays Running when the migration starts.

What to do next

Now you can suspend, resume, or stop the migration as necessary. Refer to theVerifying a migration topic in this document for instructions on confirming asuccessful migration.

Stopping a migrationStopping a migration involves logging in to the Tivoli Directory Integratoradministration and monitoring console, opening a Config View, and stopping anAssemblyLine. Before you stop migrating content from WebSphere PortalDocument Manager, you must suspend the migration to ensure that the migrationtool completes any file transformations or transfers that are in progress. Otherwise,the file transformations or transfers stop while in progress and an unrecoverableerror occurs. If you plan to restart a migration after stopping, use the parameterfiles to restart the migration at the path where it stopped.

Before you begin

Suspend the migration before you stop it. Refer to the Suspending a migration topicin this document for detailed instructions.

About this task

The steps in this task guide you through the process of starting a migration.1. Log in to the administration and monitoring console.


b. Enter your user ID and password.2. Navigate to the Monitor Status window.

a. Select Operation Status And AM.b. Select Monitor Status. The Monitor Status window displays.

3. From the Config View column, select the appropriate Config View. The ConfigView Details window displays.

4. Select the appropriate AssemblyLine for the migration. For example, if youwant to migrate content from WebSphere Portal V5.1, select PDM_51_Migrator.

5. From the Select Action menu, select Stop AL.6. Click Go to stop the migration.


Results

The Status column displays Stopped when the migration stops.

What to do next

After you stop a migration you must restart the AssemblyLine in theadministration and monitoring console to migrate content from WebSphere PortalDocument Manager.

Restarting a migrationRestarting a migration is necessary when the migration tool encounters an errorand stops. The steps involved in restarting a migration are the same as when youstart a migration. Starting a migration involves logging in to the Tivoli DirectoryIntegrator administration and monitoring console, opening a Config View, andstarting an AssemblyLine. This topic provides information on how the migrationtool restarts after a migration stops and contains information that you shouldconsider before restarting a migration.

When you restart a migration because the migration tool encounters an error, orwhen you perform a subsequent migration, the migration tool starts migrating allcontent from the root of the WebSphere Portal Document Manager repository. Themigration tool does not compare the versions of documents in WebSphere PortalDocument Manager and Lotus Quickr for changes. If you have made any changesor edits to migrated documents in Lotus Quickr, the migration tool overwrites thechanges with the version of the document as it exists in WebSphere PortalDocument Manager.

To prevent the migration tool from overwriting content or from migrating theentire source repository, you can use the start or exclude parameter files. The startparameter file lets you specify a particular path within a library to start amigration. The exclude parameter file lets you specify library paths to content thatyou want to exclude from a migration. Refer to the following topics in thisdocument for more information: The start parameter file and The exclude parameterfile.

Verifying a migrationVerifying a migration lets you confirm a successful migration. It is best practice toverify migrations each time you migrate content from WebSphere Portal DocumentManager to prevent data loss.

Before you begin

Ensure that the migration has stopped before you verify it.1. Log in to administration and monitoring console.2. Select the appropriate Config View to view the AssemblyLine status.

The AssemblyLine status should be Stopped.

About this task

The steps in this task help guide you through the process of verifying a successfulmigration.1. Check the migration log files.

72 Migration Guide

a. Navigate to the log file in the Tivoli Directory Integrator installationdirectory. For example, C:\TDI\solutions\system_logs\PDMMigration

b. Select the appropriate log file.

Note: A log file is created every time a migration is started. Select the logfile with the appropriate date and time stamp to access the mostrecent log file.

c. Open the log file with any text editor.d. Scroll to the end of the log file.e. If the migration was successful, Terminated successfully (0 errors) displays

on the last line of the log file.2. Confirm the content in Lotus Quickr

a. Log in to Lotus Quickr 8.1 as a user with sufficient rights to view allmigrated content.

b. Navigate to the appropriate Lotus Quickr place where you migratedcontent.

c. Confirm that the content exists in the appropriate Lotus Quickr place.

Content metadataDuring a migration, the migration tool either transfers existing content metadata orcreates new metadata to conform to the target server. For example, WebSpherePortal Document Manager V5.1 does not assign a Creator metadata attribute to alibrary. However, Lotus Quickr 8.1 requires a Creator metadata attribute for eachLotus Quickr place. When you migrate a library from WebSphere Portal DocumentManager V5.1 to Lotus Quickr 8.1, the migration tool adds a Creator metadataattribute so that the migrated content conforms to the Lotus Quickr environment.

In most cases, there is no change in metadata attributes between WebSphere PortalDocument Manager V5.1 or V6.0 and Lotus Quickr 8.1. However, some metadataattributes in Lotus Quickr do not exist in WebSphere Portal Document Managerand must be created to conform with the Lotus Quickr environment.

The following descriptions provide information on how the migration tooltransforms metadata attributes:

1:1 Indicates that the metadata attributes are the same between WebSpherePortal Document Manager V5.1 or V6.0 and Lotus Quickr 8.1. Wheremetadata attributes are the same, the migration tool transfers whatevervalue the attribute has in WebSphere Portal Document Manager.

Default user IDIndicates the migration tool specifies the user ID of the person whoperforms the migration. The default user ID corresponds to the LotusQuickr user ID and password that you specify in pdmmigration.properties.The migration tool specifies this user ID because either this attribute doesnot exist in WebSphere Portal Document Manager or this attribute has anull value. The migration tool also specifies the default user ID when theexisting user ID belongs to a dormant user. A dormant user is a user IDthat is specified as an attribute, but does not exist in the LDAP directory.

Date of migrationThe migration tool specifies the date when you perform the migration.


WebSphere Portal Document Manager library to Quickr placeThe following table provides information to help you understand what metadataattributes the migration tool supports for Lotus Quickr places. The table shows thesupported metadata attributes and provides a description of how the attribute istransformed during a migration.

Table 8. Lotus Quickr place metadata

WebSphere PortalDocument Manager V5.1


Lotus Quickr metadataattribute

Default user ID 1:1 Author

Date and Time of migration 1:1 Created

Default user ID 1:1 Creator

1:1 1:1 Description

1:1 1:1 Draft Approvers Group

1:1 1:1 Label

1:1 1:1 Languages

Date and Time of migration 1:1 Last Modified

Default user ID 1:1 Last Modifier

Default user ID 1:1 Owners

1:1 1:1 Path

1:1 1:1 Permissions

The migration tool sets thisattribute to TRUE by default.


Searchable

1:1 1:1 Title

WebSphere Portal Document Manager folder to Lotus Quickrfolder

The following table provides information to help you understand what metadataattributes the migration tool supports for folders in Lotus Quickr 8.1. The tableshows the supported metadata attributes and provides a description of how theattribute is transformed during a migration.

Table 9. Folder metadata attributes in Lotus Quickr





Default user ID 1:1 Owner



1:1 1:1 Description

1:1 1:1 Hidden

1:1 1:1 Label

1:1 1:1 Language

74 Migration Guide

Table 9. Folder metadata attributes in Lotus Quickr (continued)




Default user ID v 1:1

v Default user ID, if adormant user ID isspecified for this attribute.

Last modifier

Date and Time of migration 1:1 Last modified

1:1 1:1 Permissions



Searchable

1:1 1:1 Title

WebSphere Portal Document Manager document to LotusQuickr document

The following table provides information to help you understand what metadataattributes the migration tool supports for documents in Lotus Quickr 8.1. The tableshows the supported metadata attributes and provides a description of how theattribute is transformed during a migration.

Table 10. Document metadata attributes in Lotus Quickr





1:1 1:1 Owner

1:1 1:1 Creator

1:1 1:1 Created

1:1 1:1 Description

1:1 1:1 Data last modified

1:1 1:1 Effective date

1:1 1:1 Hidden

1:1 1:1 Label

1:1 1:1 Language

v 1:1


v 1:1


Last modifier

1:1 1:1 Last modified

1:1 1:1 Permissions



Searchable

1:1 1:1 Title

1:1 1:1 Version name

1:1 1:1 Version description

1:1 1:1 Locked


Table 10. Document metadata attributes in Lotus Quickr (continued)




v 1:1


v 1:1


Locked owner

1:1 1:1 Data Length

Does not exist 1:1 Revision

This attribute does not exist.During a migration, themigration tool uses the fileextension of the document tocreate the appropriatemimeType attribute.

Refer to the Extending theMIME types for WebSpherePortal V5.1 in this documentfor instructions on manuallyspecifying MIME types.

1:1 mimeType

WebSphere Portal Document Manager draft to Lotus Quickrdraft

The following table provides information to help you understand what metadataattributes the migration tool supports for drafts in Lotus Quickr 8.1. The tableshows the supported metadata attributes and provides a description of how theattribute is transformed during a migration.

Table 11. Draft metadata attributes in Lotus Quickr





1:1 1:1 Owner

v 1:1


v 1:1


Creator

1:1 1:1 Created

1:1 1:1 Description

1:1 1:1 Data last modified

1:1 1:1 Effective date

1:1 1:1 Hidden

1:1 1:1 Label

1:1 1:1 Language

v 1:1


v 1:1


Last modifier

76 Migration Guide

Table 11. Draft metadata attributes in Lotus Quickr (continued)




1:1 1:1 Last modified

1:1 1:1 Permissions



Searchable

1:1 1:1 Title

1:1 1:1 Version name

1:1 1:1 Version description

1:1 1:1 Locked

1:1 1:1 Locked owner

1:1 1:1 Data Length

1:1 1:1 Submitted

Does not exist 1:1 Revision

This attribute does not exist.During a migration, themigration tool uses the fileextension of the draft tocreate the appropriatemimeType attribute.

Refer to the Extending theMIME types for WebSpherePortal V5.1 in this documentfor instructions on manuallyspecifying MIME types.

1:1 mimeType

WebSphere Portal Document Manager view to Lotus Quickrview

The following table provides information to help you understand what metadataattributes the migration tool supports for views in Lotus Quickr 8.1. The tableshows the supported metadata attributes and provides a description of how theattribute is transformed during a migration.

Table 12. View metadata attributes in Lotus Quickr





Default user ID 1:1 Owner





Deep

1:1 1:1 Description

1:1 1:1 Hidden

1:1 1:1 Label

1:1 1:1 Language


Table 12. View metadata attributes in Lotus Quickr (continued)




Default user ID 1:1 Last modifier

Date and Time of migration 1:1 Last modified

1:1 1:1 Permissions

1:1 1:1 Query



Searchable



Shared

1:1 1:1 Title

78 Migration Guide

Chapter 6. Troubleshooting the migration tool

The topics in this section provide detailed information to help you troubleshootproblems with the migration tool.

System logsThis topic provides a detailed overview of the system log files for the migrationtool. System logs contain messages and information about the migration tool andhow it is operating. The first step in troubleshooting any problems with themigration tool is referring to the system logs.

The system log files for the migration tool are located in all three of the followingplaces:v The server where you have Tivoli Directory Integrator installed.v The server where you have WebSphere Portal installed.v The server where you have Lotus Quickr installed.

Depending on the problem that you are troubleshooting, you might need to accessany or all of the log files in the above locations. Refer to the appropriate topics inthis document to find detailed information on accessing and configuring the logfiles for the different components.

Tivoli Directory Integrator logsThe Tivoli Directory Integrator log files provide detailed information about thetransformation and transferring of library content and tell you whether a migrationis successful. The Tivoli Directory Integrator log files also provide information suchas the status of the various components involved in the migration. Refer to TivoliDirectory Integrator log files first when troubleshooting any problems about amigration.

Default logging

By default, the main Tivoli Directory Integrator log file for the migration process ispdmmigration.log in the solutions directory. For example, C:\TDI\solutions\pdmmigration.log

The migration tool uses the Apache log4j logging framework to increase speed andreduce the size of the log files on your system. The default logging uses a log4jconfiguration to create a set of rolling log files. The default logging configurationcreates a maximum of three log files restricted to a maximum file size of 20 MBper file. The result of this configuration is that no more than 60 MB of your systemmemory is used for logging.

The default logging configuration works by rolling over pdmmigration.log everytime the file size reaches 20 MB. When you start a migration, the migration toolcreates pdmmigration.log. When pdmmigration.log reaches the maximum file sizeof 20 MB, the migration tool backs up the old log file and creates a new log file. Itrenames the log file by adding a .1, .2, or .3 to the file name. For example, the first


time the log files roll over, pdmmigration.log becomes pdmmigration.log.1 and themigration tool creates a new log file named pdmmigration.log. In this case, logfiles appear on your system as follows:v pdmmigration.logv pdmmigration.log.1

Where pdmmigration.log contains the most recent logging information.

The migration tool continues renaming and overwriting the logs each time thecurrent file reaches the maximum size.

Note: pdmmigration.log always contains the most recent logging information.

Configuring default logging

You can configure pdmmigration.log if you want to change the logging level, themaximum file size of 20 MB, or the number of backup log files that the migrationtool creates.

To configure pdmmigration.log:1. Navigate to the etc folder in the solutions directory. For example,

C:\TDI\solutions\etc2. Locate the following file: log4j.properties3. Open log4j.properties with any text editor.4. Locate the following properties in log4j.properties:

v log4j.rootCategory=INFO, Default

The value in this property determines the logging level.By default, thelogging level is set to INFO for normal logging. If you encounter a problemand need to debug the system, specify DEBUG as the logging level.

v log4j.appender.Default.MaxFileSize=20MB

The value in this property determines the maximum file size for each log file.v log4j.appender.Default.MaxBackupIndex=3

The value in this property sets the maximum number of rolling log files.5. Specify the desired properties for the default logging.6. Save and close the properties file.7. Restart Tivoli Directory Integrator for the changes to take effect.

System logging

The Tivoli Directory Integrator system logging is disabled by default to prevent themigration tool from creating large system log files. If you want to enable TivoliDirectory Integrator system logging, you must edit the properties file,pdmmigration.properties. Refer to the Editing the properties file topic in thisdocument for more information.

Locate the log files in the systemLogs folder of the solutions directory. Forexample, C:\TDI Solutions\systemLogs

Note: If you do not enable system logging in pdmmigration.properties, thesystemLogs folder might not exist.

80 Migration Guide

WebSphere Portal logsWebSphere Portal log files provide detailed information about the status of theWebSphere Portal environment during a migration. You should refer to theWebSphere Portal log files to troubleshoot any problems with the proxyconnectors, authentication, or any of the calls to the migration tool.

The log files for WebSphere Portal are:v SystemErr.log

WebSphere Portal V5.1This log file contains error messages and logging information forWebSphere Portal V5.1 and the migration tool. Configure the log settingsin the WebSphere Portal server user interface to change the log leveldetails.

WebSphere Portal V6.0This log file contains error messages.

v SystemOut.logThis log file contains process information about the proxy connectors, such aswhether the Web services have started successfully and user log in details.

v trace.log

WebSphere Portal V5.1This log file does not exist for WebSphere Portal V5.1. If you want toenable trace logging for WebSphere Portal V5.1, configure the logsettings in the WebSphere Portal sever user interface.

WebSphere Portal V6.0This log file contains all the logging information for WebSphere PortalV6.0 and the migration tool.

Important: You must enable trace.log file for WebSphere Portal V6.0.

You can locate these log files in the log folder in the Portal Server directory. Forexample, C:\<portal_server_root>\PortalServer\log

Configuring log settings for WebSphere Portal V5.1

Follow these steps to configure logging for WebSphere Portal V5.1:1. Log in to WebSphere Portal as an administrator.2. Select Administration → Portal Analysis → Enable Tracing

The Enable Tracing window displays.3. In the Append these trace settings field, enter one of the following:

v com.ibm.pdmquickr.*=low=enabled

This setting enables logging of all the logging for WebSphere Portal V5.1 andthe migration tool.

v com.ibm.pdmquickr.*medium=enabled

This setting enables logging of warnings and errors.4. Restart the WebSphere Portal V5.1 server.

Configuring log settings for WebSphere Portal V6.0

Follow these steps to configure log settings for WebSphere Portal V6.0:

Chapter 6. Troubleshooting the migration tool 81

1. Log in to the WebSphere Application Server administration console on theserver where you have WebSphere Portal V6.0 installed.

2. Select Troubleshooting → Logs and Trace

The Logging and Tracing window displays.3. Select WebSphere Portal → Change Log Detail Levels.4. Select the Runtime tab.5. Ensure the following field is selected: Save runtime changes to configuration

as well.This option lets you apply the configuration changes without having to restartthe server.

6. Select the following component from the list: com.ibm.pdm2quickr

A list of log levels display.7. Select the logging level from the list.

For normal logging, specify info as the logging level. If you encounter aproblem and need to debug the system, specify fine as the logging level.

8. Click OK.9. Click Save to apply the changes.

Lotus Quickr logsThe Lotus Quickr logs provide detailed information about the status of the LotusQuickr environment during a migration. You should refer to the Lotus Quickr logfiles to troubleshoot any problems with the proxy connectors, authentication, orany of the calls to the migration tool.

For Lotus Quickr there are three log files:v SystemErr.log

This log file contains error messages.v SystemOut.log

This log file contains process information about the proxy connectors, such aswhether the Web services have started successfully and user login details.

v trace.logThis log file contains the all the logging information for Lotus Quickr and themigration tool.

Important: You must enable this log file for Lotus Quickr.

You can locate these log files in the log folder in the Portal Server directory. Forexample, C:\<portal_server_root>\PortalServer\log

Configuring log settings for Lotus Quickr 8.1

Follow these steps to configure log settings for Lotus Quickr:1. Log in to the WebSphere Application Server administration console on the

server where you have Lotus Quickr 8.1 installed.2. Select Troubleshooting → Logs and Trace

The Logging and Tracing window displays.3. Select WebSphere Portal → Change Log Detail Levels.4. Select the Runtime tab.

82 Migration Guide

5. Ensure the following field is selected: Save runtime changes to configurationas well.This option lets you apply the configuration changes without having to restartthe server.

6. Select the following component from the list: com.ibm.pdm2quickr

A list of log levels display.7. Select the logging level from the list.

For normal logging, specify info as the logging level. If you encounter aproblem and need to debug the system, specify fine as the logging level.

8. Click OK.9. Click Save to apply the changes.

Proxy connector logsThe migration tool installation program uses several Ant tasks to deploy the proxyconnectors. The Ant tasks automate the installation of the proxy connectors onWebSphere Portal V5.1 or V6.0 and Lotus Quickr 8.1. The migration tool createslogging information about these Ant tasks to help you troubleshoot problems withthe installation of the proxy connectors.

To access the proxy connector log file:1. Navigate to the migration tool installation directory. For example, C:\Program

Files\PDM2QuickrMigrationTool 1.2.2. Locate the following file: migrationtool_ant.log.

The migrationtool_ant.log file contains logging information about the followingAnt tasks: InstallApplication, StartApplication, and UninstallApplication. Refer toyour product documentation for more information about these Ant tasks.

Checking the version numbersThe versions of the migration tool, the WebSphere Portal proxy connector, and theLotus Quickr proxy connector must match to perform a successful migration. Theversion numbers correspond to the date the component was released. If theversions do not match, errors might be more likely to occur. Check for updates andreinstall as necessary if the version numbers of the migration tool components donot match.

About this task

The following steps provide instructions to help you check the version numbers ofthe migration tool, the WebSphere Portal proxy connector, and the Lotus Quickrproxy connector:1. Navigate to the solutions directory. For example, C:\TDI\solutions.2. Locate the following file: PDM_<version_number>_Migrator-version.log.3. Open the file with any text editor. The version numbers in the file display as

follows:

pdm60Ver=Corresponds to the WebSphere Portal V6.0 proxy connector.

Note: This property only displays in the file if you are usingWebSphere Portal V6.0.


pdm51Ver=Corresponds to the WebSphere Portal V5.1 proxy connector.

Note: This property only displays in the file if you are usingWebSphere Portal V5.1.

qkrVer=Corresponds to the Lotus Quickr 8.1 proxy connector.

tdiVer=Corresponds to the migration tool.

Changing the Tivoli Directory Integrator portYou might need to change the port that IBM Tivoli Directory Integrator uses if youhave a conflict with another software product that uses the same port. You mightalso need to change the port that Tivoli Directory Integrator uses if you havefirewall restrictions on that port.

About this task

Changing the Tivoli Directory Integrator port involves updating it in two places.You must navigate to the Tivoli Directory Integrator solutions directory and updatethe port in solution.properties. You must also log in to the Tivoli DirectoryIntegrator administration and monitoring console and update the port through theuser interface.1. Navigate to the Tivoli Directory Integrator solutions directory. For example,

C:\TDI\solutions2. Locate the following file: solution.properties3. Open solution.properties with any text editor.4. Locate the following property in solution.properties:

api.remote.naming.port=1099

5. Replace 1099 with the new port.6. Save and close solution.properties.7. Restart the Tivoli Directory Integrator server for the changes to take effect.

Refer to the Starting the servers topic in this document for more information.8. Log in to the Tivoli Directory Integrator administration and monitoring

console as an administrative user.9. Select Console Administration → Manage TDI Servers

10. Select Local TDI Server.11. Select Edit. Alternatively, you can select Add to create a new server. The Edit

TDI server window displays.12. In the Port field, replace 1099 with the new port number.13. Select Test Connection to ensure the connection is valid. A message displays

to tell you if the connection was successfully established.14. Select OK to save the changes.

Contacting IBM supportBefore you contact an IBM technical support representative, collect specificinformation to help you efficiently resolve any difficulties. This topic providesinformation on what you should provide to IBM support should you encounterany errors while using the migration tool.

84 Migration Guide

Before contacting IBM support

Before you contact an IBM technical support representative, do the following:1. Configure the logging for the migration tool. Set the logging levels to DEBUG

and reproduce the error that you encountered.Refer to the following topics in this document for information and instructionson configuring the log files: Tivoli Directory Integrator logs, WebSphere Portal logs,and Lotus Quickr logs.

2. Ensure the version numbers for the migration tool and both proxy connectorsmatch.Refer to the Checking the version numbers topic in this document for instructions.

3. If the version numbers for the migration tool and both proxy connectors do notmatch, download any updates and reinstall as necessary.

Providing information to IBM support

When you contact an IBM technical support representative, include all of thefollowing:1. A detailed description of the task that you were performing when you

encountered the error.2. All the log files for Tivoli Directory Integrator, WebSphere Portal, and Lotus

Quickr.Refer to the following topics in this document for information and instructionson configuring the log files: Tivoli Directory Integrator logs, WebSphere Portal logs,and Lotus Quickr logs.

3. The file that contains the version numbers, PDM_<version_number>_Migrator-version.logRefer to the Checking the version numbers topic in this document for instructions.

4. The report files that the migration tool creates after a migration.There are two report files for the migration tool: report.csv and summary.csv.report.csv contains a list of entities that the migration tool has migrated.summary.csv contains information about a migration, such as the total numberof documents that have migrated, the target and source servers, the date andtime of the migration, and so on. Locate the report files in the Reports folder inthe solutions directory. For example, C:\TDI\solutions\Reports.

5. If an error occurs during installation, include the following file:migrationtool_ant.log.Locate this file in the migration tool installation directory. Refer to the Proxyconnector log file topic in this document for instructions on accessing this logfile.


IBMWebSphere Portal Document Manager migration tool · IBMWebSphere Portal Document Manager...

Documents

Transcript of IBMWebSphere Portal Document Manager migration tool · IBMWebSphere Portal Document Manager...