General
Q: What is the IBM Connections Migration Tool for lotus Quickr for WebSphere Portal?
A: The IBM® Connections Migration Tool for Lotus® Quickr® for WebSphere® Portal can help customers to migrate their resources from Lotus Quickr for Portal 8.5 to IBM Connections 4.5 CR1.
Q: If a user leaves a place in Quickr where she uploaded documents but still remains in the company, what does the migration tool do with documents from this user in the new community?
A: User is still the author of the document but she would not have access to the Community.
Q: Libraries become folders in the new community but these folders have a name-extension (library1_cc2edb804fafaee5950d9feb8d43bb02). Is there any way to create these folders without this extension?
A: The migration.properties file controls whether multiple Libraries in the Team Place get transferred to single Library in Community. If it is set to false, then migration tool adds an id to the Library name to make it unique. Change the property isMigrateLibraryToOneLibraryWidget=true in the migration.properties file. Set to "true" to migrate each library in a place as a library widget in a community. Set to "false" to migrate all libraries in a place as one library widget in a community.
Q: Is there any impact on disable the three properties (User Identity Document Change Preprocessor Action/User Identity Folder Change Preprocessor Action/User Identity Task Change Preprocessor Action)?
A: Filenet added preprocessors to handle situations where the IDs of users who left the company were given unintentionally to new users. For example User1 uid is uid123. User1 uploaded documents to Library in Filenet and left the company. Now new user User2 is given the same uid assigned uid123. This causes FileNet to display User2 as the owner of the documents uploaded by User1. This is only a display problem and not a permissions issue. User2 still can't access User1 documents. Turning off these for extended period of time should not cause a problem unless customer runs into this scenario (If new users are assigned unique uids then this is not an issue).
Q: What version of Java is supported by the tool?
A: IBM JDK/JRE 1.6 or above.
Q: If a user no longer existing in LDAP as a creator/modifier of document or folder during migration?
A: Migration tool will use Connections admin user which set by migration.properties instead of no longer existing user.
Q: About the tool's ability to recover from a severe error such as a server crash or lost network connectivity. How does the person running the tool resume working once the error is solved? If the error occurs while the tool is actively migrating a library, do you have to restart that migration or will the tool pick up where it left off?
A:Migration tool supports batch migration, so you can refer to info.log to check where you are, and just input place ids into the not_integrated_place_IDs.properties file for the remaining places to restart migration.
Q: How do I remove Orphaned Users from Quickr for Portal?
A: Please run Quickr Portal Cleanup Users task following instructions from http://www-10.lotus.com/ldd/portalwiki.nsf/dx/cleanup-of-deleted-user-artefacts-from-websphere-portal-and-reestablish-unique-id-binding-on-ldap-change
Make DB backup before running Portal Cleanup Users task.
Q: How do I change names of Document owners who left the company and no longer exist?
A: Before migration run Quickr Portal Cleanup Users task to remove Orphaned Users and then run User Transformation Tool to map these Users to valid Users following instructions in http://www-10.lotus.com/ldd/lqwiki.nsf/dx/change-end-user-dN-and-other-ldap-attributes
Make DB backup before running User Transformation Tool task.
Q: How do I restrict access on documents/folders?
A: Community Members have Read access on Library documents and folders. Create Sub Communities with restricted members and add the Library to Sub Community so that access is restricted to only Sub Community members.
Q: How do I migrate resources if display name in DN?
A: Before you do migration please add property "isDisplayNameInDN=true" in migration.properties file first.
Q: How do I find number of Documents in a Quickr Teamplace?
To get number of Documents in a Team Place on QuickrJ you need to install WCM Support Tools Portlet on a Portal Page(https://greenhouse.lotus.com/plugins/plugincatalog.nsf/assetDetails.xsp?action=editDocument&documentId=AE2BB2412F20AA318525772E006F7014 )
Go to Run XPath Query
enter xpath
element(*, clb:clbLibrary)[@icm:label='1F_18M131M410DI60IVPRI9UL0000' or @icm:label='1F_18M131M410DI60IVPRI9UL0021']element(*, clb:clbDocument)
1F_18M131M410DI60IVPRI9UL0000 and 1F_18M131M410DI60IVPRI9UL0021 are Team Place IDs on Quickr in the above example.
Increase Page Size from 100 to higher number
Following is the Screen shot that shows results
![xpath results](/ldd/lcwiki.nsf/xsp/.ibmmodres/persistence/DominoDoc-1363A-content/qjquery.jpeg)
Q: How do I find number of migrated Documents on CCM?
Following is the Query you can run on ACCE to get list of Documents & size on CCM
SELECT This, ContentSize, Creator, CurrentState, DateCheckedIn, DateContentLastAccessed, DateCreated, DateLastModified, DocumentTitle, Id, LastModifier, Name, Owner, VersionStatus FROM Document WHERE Document.This INSUBFOLDER '/ClbTeamspaces/montani2_1423258090423'
In the above query /ClbTeamspaces/montani2_1423258090423 is the path of the Library, so you need to replace it with PATH of migrated Library.
Login to ACCE
Go to Object Store ICObjectStore
Go to Search->Click New
Go to SQL View Tab and enter the query and click Run
Troubleshooting
Add
isDebug=true
in migration.properties file.
Add following to log4j.properties file
log4j.rootLogger=INFO, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p [%c] %m%n
log4j.logger.httpclient.wire.header=DEBUG
log4j.logger.org.apache.commons.httpclient=DEBUG
Redirect output of command line to file and send IBM redirected output from command line, migration.properties, debug.log,info.log & error.log files.
Resources