Before migrating your Quickr Domino servers to Connection CCM learn the tips and tricks from real world examples on how to make the move easier. Get your house in order by stripping out unnecessary baggage. Use TDI and Domino Agents to build a better picture of the condition of your environment and give you the information you need to make the migration as smooth as possible. I will live demo how the IBM's tools migrate docs and files to a CCM Community Library.
The Nuts and Bolts of Migrating Quickr Domino to CCM
1. The Nuts and Bolts of Migrating
Quickr Domino to CCM
Fergal McKenna, Social Software SEAL, IBM Ireland
email: fmckenna@ie.ibm.com
twitter: @fergalmck
3. 3
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole
discretion.
Information regarding potential future products is intended to outline our general product direction and it should not be
relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver
any material, code or functionality. Information about potential future products may not be incorporated into any contract.
The development, release, and timing of any future features or functionality described for our products remains at our sole
discretion
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment.
The actual throughput or performance that any user will experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve
results similar to those stated here.
Please Note
4. Agenda
●
Before we get Started!!!Before we get Started!!!
●
Preparing for the migration
●
Domino Agents
●
Configuration
●
Mapping files
●
Demo
●
Tips and tricks
●
Troubleshooting
5. Before we get started!!
●
Plan, Plan, Plan
●
Phase 1
●
Understand Requirements
●
Phase 2
●
Setup Config
●
Phase 3
●
Test and Migrate
6. Agenda
●
Before we get Started!!!
●
Preparing for the migrationPreparing for the migration
●
Domino Agents
●
Configuration
●
Mapping files
●
Demo
●
Tips and tricks
●
Troubleshooting
7. Preparing for the migration!!
●
Why Migrate? What is CCM???
●
File repository.
●
Blogs, Wikis,Tasks, Business Process, Intranet, Extranet, Template
applications, HTML forms
●
Simple Forms,
8. Preparing for the migration!!
What's covered by the migration tool.
A Place will be migrated as a community in Connections.
Place membership will be migrated to community.
Room will be migrated to CCM as folder, hierarchy will be preserved.
Folder will be migrated to CCM as folder, hierarchy will be preserved.
Documents created from uploads, imports, pages, simple custom forms,
and Microsoft office forms will be migrated to CCM.
9. Preparing for the migration!!
What's covered by the migration tool.
The information of creator, last editor, created timestamp, last updated
timestamp will be migrated with the documents and folders.
Versions and comments will be migrated together with the documents.
Simple custom forms will be migrated to CCM as document classes.
ACLs (Access Control Lists) will be migrated to CCM along with associated
documents, folders, and rooms.
10. Preparing for the migration!!
What's NOT covered by the migration tool.
Wiki and Blog places.
Task, Calendar, forum, list, link, or Templates.
Html forms and the documents based on the html forms
Draft. All drafts need to be completed before migration.
Workflows. All workflows need to be completed before migration.
Content in Trash.
Local members.
Restricted Access: DocsFoldersRooms
11. Preparing for the migration!!
●
Know what you are migrating to.
●
Rooms, Folders, Homes pages
18. Preparing for the migration!!
Access Models - ( current )
Restricted Access – * CCM Members can read all content
load qptool getrestrictedresourcelist -p nameofplace
●
<name>demoairlinetickets</name>
●
<room name="Demo Airline Tickets" nsf="Main.nsf"/>
●
<restricted_room name="Europe"
nsf="PageLibrary882574B2007234C1.nsf" room_owners="[Amy
Jones, Mary Joyce]"/>
●
<restricted_document document_authors="[Amy Jones]"
location="/Library/Administration./" name="Facility"
unid="21D9C782FA5A350B88257BA9006497D5"/>
19. Preparing for the migration!!
Access Models - Users
●
Quickr Domino Place => Connections Library Access
User roles in Quickr Domino. Mapped User Roles in Connections
Owner - Place creator, Owner has access to
all rooms, folders, and pages in the place.
Owner - •Move files to a different location.
•Remove files from the source location when moving
them to another location.
•Delete any library file or folder.
•Change share settings.
•Empty the trash.
Manager - Can create and edit content,
manage membership, and customize the place
Editor - Can create content, and edit other
people’s content
Member - •Add files to folders to which you have access
•Edit files using personal drafts
•Edit folder names and descriptions
•Download, replace, copy, move, and use social features
for files to which you have access
•Delete and use social features for folders to which you
have access
Author - Can create content, and edit his own
content.
Reader - Can read content
20. Preparing for the migration!!
Access Models - Users
●
Rooms & Folders => Folders
User roles in Quickr Domino. Mapped User Roles in Connections
Owner - Room creator gets this role
Owner has access to all folders, and
pages in the room+ Manager
capabilities
Owner - •Change how members access files and folders
Configure the display of folders and files
•Change default document type for all files uploaded to the library
•Enable members to change the document type when uploading
files
•Enable draft review and modify related options
Manager - Can create and edit content,
manage membership, customize rooms
Editor - •Edit and upload new versions of any library file.
Note: Editors can edit the content, the document properties, and
the description of any file.
•Edit folders that they added.
Editor - Can create content, and edit
other people’s content
Author - Can create content, and edit
his own content.
Contributor – Reader tasks plus..... •Upload new files.
•Create folders.
Reader - Can read content Reader - •Access and read files. Like, follow, and comment files.
21. Preparing for the migration!!
Access Models - Users
●
Documents => Documents
User roles in Quickr Domino. Mapped User Roles in Connections
Owner - Can edit all documents Owner - Can edit all documents
Author - Can edit the document Author – Can edit the document
Reader - Can read the document Reader - Can read the document
22. Preparing for the migration!!
Access Models - Groups
Quickr Domino Place => Connections Library Access
- If a group is an owner or manager in a Place, it is expanded to individual members
and migrated to a community as person owners.
Note: Groups cannot be owners in Connections Communities
- If a group is reader, author, or editor in a place, it is migrated as a group as a
community member.
User roles in Quickr Domino. Mapped User Roles in Connections
Owner Owner – ***Expanded to users
Manager
Editor Member
Author
Reader
23. Preparing for the migration!!
●
FileNet Administrator *Important
●
Must be an LDAP user
●
Must not be local wasadminwpsadmin
●
Must be significant..
●
e.g “Migration Admin”
24. Preparing for the migration!!
Custom forms
Problem: There is a limit to the amount of custom forms that can be migrated
Symptom: When running the qptool migratecustomized forms command, if you notice a
runtime exception reporting, “The row length limitation of the underlying database has
been exceeded, incapable of creating document class any further,” it means you are not
able to migrate customized forms any further.
Cause: Underlying database which stores the field info has a row length limitation of 32K,
Resolving the problem: It is recommended that customized forms be migrated by
prioritizing from most significant to least significant,
Reference: http://www-10.lotus.com/ldd/lcwiki.nsf/xpDocViewer.xsp?lookupName=Early+Release+-
+Quickr+for+Domino+Migration+Guide#action=openDocument&res_title=Installing_and_configuring&c
ontent=pdcontent
25. Agenda
●
Before we get Started!!!
●
Preparing for the migration
●
Domino AgentsDomino Agents
●
Configuration
●
Mapping files
●
Demo
●
Tips and tricks
●
Troubleshooting
26. Domino Agents – Sample Agents are not supported
●
Cleanup & Gathering information
●
These examples are shared on Greenhouse under my name
27. Domino Agents – Sample Agents are not supported
●
Cleanup & Gathering information
●
All result files are configured to c:temp
●
Change config settings to suit environment
●
These examples are shared on Greenhouse under my name
Sample Place1 Sample Place2 Sample Place3 Sample Place4
12 Multiple Page Doc
21 Single Page Doc
33 Empty Page doc
105 Single Upload Doc
2 Single Import Doc
11 Multiple Page Doc
21 Single Page Doc
41 Empty Page Doc
22 Single Upload Doc
12 Single Import Doc
18 Multiple Page Doc
72 Single Page Doc
14 Empty Page Doc
410 Single Upload Doc
4 Single Import Doc
113 Multiple Page Doc
402 Single Page Doc
179 Empty Page Doc
6404 Single Upload Doc
152 Single Import Doc
28. Agenda
●
Before we get Started!!!
●
Preparing for the migration
●
Domino Agents
●
ConfigurationConfiguration
●
Mapping files
●
Demo
●
Tips and tricks
●
Troubleshooting
29. Configuration
●
Notes.ini
●
Add the following parameters for communicating with FileNet® and Connections.
●
The setting for the Connections url should be ConnectionsServerURL and must
utilize https.
●
ConnectionsServerURL=https://icserver.example.com:9444
●
FilenetURL=http://fnserver.example.com:9081
30. Configuration
●
Qpconfig.xml
●
Add the following items as the child element of <server_setting> item as follows:.
<migration>
<person_ldap_dump_file>c:ccmcollect_user.dns</person_ldap_dump_file>
<group_ldap_dump_file>c:ccmcollect_groups.dns</group_ldap_dump_file>
<person_mapping_file>c:ccmuser_mapping.txt</person_mapping_file>
<group_mapping_file>c:ccmgroup_mapping.txt</group_mapping_file>
<expand_external_groups enabled="true" max_depth="3" number_limit="10"/>
<special_char_encoding_mode>underline</special_char_encoding_mode>
<single_member_import>true</single_member_import>
</migration>
31. Configuration
●
ACCE
●
Change the Apply to setting to This object and all
children, set the permission group to Custom, and
check all the options. Press OK.
●
Add the group #Authenticated_users along with the
properties associated with View Properties
32. Agenda
●
Before we get Started!!!
●
Preparing for the migration
●
Domino Agents
●
Configuration
●
Mapping filesMapping files
●
Demo
●
Tips and tricks
●
Troubleshooting
34. Mapping Files - Person LDAP dump - collect_groups.dns
●
DN;UniqueID
●
CN=Admin group1/O=Demo;51548bfd-ce3c-4af5-aca4-1e4b8c273eac
●
CN=Admin group2/O=Demo;3c2d1cd0-f737-47de-8dff-972d691d6b6b
●
Note: If the previous collect_user.dns was added then
collect_groups.dns must also be added.
36. Mapping Files – Group Mapping File - group_mapping.txt
●
DN1;DN2
●
CN=Admin group1/O=Demo;CN=Admin group1/O=CCM,DC=IBM,DC=COM
●
CN=Admin group2/O=Demo;CN=Admin group2/O=CCM,DC=IBM,DC=COM
●
Note: If the previous user_mapping.txt was added then
group_mapping.txt must also be added.
37. Mapping Files – Creating the mapping files using TDI
●
Creating Mapping Files
●
Active directory Redbook
●
TDS Wiki
●
Domino Attached with Slidedeck.
38. Agenda
●
Before we get Started!!!
●
Preparing for the migration
●
Domino Agents
●
Configuration
●
Mapping files
●
DemoDemo
●
Tips and tricks
●
Troubleshooting
39. Demo of Migration
1. Getcustomizedforms
2. Migratecustomizedforms
3. Migrate Place
40. Agenda
●
Before we get Started!!!
●
Preparing for the migration
●
Domino Agents
●
Configuration
●
Mapping files
●
Demo
●
Tips and tricksTips and tricks
●
Troubleshooting
41. Tips and Tricks - Custom Form first
Check your config by first migrating a custom form
42. Tips and Tricks – library name
Rename the CCM Library from Library
so it doesn't have the same name twice!!
43. Tips and Tricks – unwanted alerts
●
Turn of Notifications during the migration
Notifications-config.xml – memberAdded, memberRemoved
●
Use ACCE to add the Migration Admin to the black list
http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Configuring_Filenet_to_be_an_Activity_Stream_producer_with_a_new_deployment_ic45
Activity Stream Ignored Users Ids – Add Migration Admin's SID
44. Tips and Tricks
●
For Restricted content (Currently)
●
Migrate the content to a private Place using the Connectors.
●
Migrate this data with the restricted member access into CCM.
●
Leave as separate Community or move as SubCommunity
●
Be Close
45. Agenda
●
Before we get Started!!!
●
Preparing for the migration
●
Domino Agents
●
Configuration
●
Mapping files
●
Demo
●
Tips and tricks
●
TroubleshootingTroubleshooting
46. TroubleshootingE_READ_ONLY
Problem: com.filenet.api.exception.EngineRuntimeException exception when executing qptool
migration command
Symptom: com.filenet.api.exception.EngineRuntimeException: FNRCE0057E: E_READ_ONLY:
Method failed because an object or property is read-only.
Cause: The user specified on the command line does not have certain access right on the object
store.
Resolving the problem: Grant all permission access right on the object store to the user as
described on the "Filenet Object Store properties modification" section of below link:
Reference: https://w3-connections.ibm.com/wikis/home?lang=en-
us#!/wiki/W9fb341241248_4236_bee2_25555962eefd/page/Setup%20test%20environment%20for
%20QD%20migration
47. Troubleshooting
DB_ERROR
●
Problem: com.filenet.api.exception.EngineRuntimeException exception when saving document or
creating folder during place migration
Symptom: com.filenet.api.exception.EngineRuntimeException: FNRCD0009E: DB_ERROR: The
database access failed with the following error: ErrorCode -101, Message 'DB2 SQL Error: SQLCODE=-
101, SQLSTATE=54001, SQLERRMC=null, DRIVER=4.13.127' ObjectStore: "ICObjectStore",
Cause: This message can be returned when an attempt is made to prepare or execute an SQL
statement that exceeds a limit such as a memory limit, an SQL limit, or a database limit.
Resolving the problem: Enable the amount of memory that is allocated for application requests to
grow automatically by setting the APPL_MEMORY database configuration parameter to AUTOMATIC on
FileNet database FNOS & FNGCD.
Reference:http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.messages.sql.doc/do
c/msql00101n.html
48. TroubleshootingOOM Exception
Problem: java.lang.OutOfMemoryError exception when executing qptool migration command
Symptom: 08/05/2013 08:24:57 Agent error: JVMDUMP006I Processing dump event "systhrow",
detail "java/lang/OutOfMemoryError" - please wait.
08/05/2013 08:24:58 Agent error: JVMDUMP013I Processed dump event "systhrow", detail
"java/lang/OutOfMemoryError".
Cause: The java heap size can not satisfy the memory requirement of qptool process when running
migration command.
Resolving the problem: Increase the java maximum heap size setting in notes.ini file. You can adjust
the JavaMaxHeapSize parameter in notes.ini: JavaMaxHeapSize=256M.:
In this example, 256M memory is specified as the java maximum heap size for all domino process,
which is sufficient in most cases. If it still does not solve the OOM exception, you can increase the java
maximum heap size to 512M, 1024M.. and so on
49. TroubleshootingJavaUserClassesExt
Problem: java.lang.ExceptionInInitializerError exception when executing qptool migration command
Symptom:
04/15/2014 04:45:02 1333 ERROR [main] com.lotus.quickplace.api.QPAPIInterface -
com.lotus.quickplace.qom.QPException: 0xffffffff : 0xffffffff : java.lang.ExceptionInInitializerError
04/15/2014 04:45:02 1335 INFO [main] com.lotus.quickplace.api.QPAPIInterface -
com.lotus.quickplace.qom.QPException: 0xffffffff : 0xffffffff : java.lang.ExceptionInInitializerError
Cause: The user specified on the command line does not have certain access right on the object
store.
Resolving the problem: Check that all 25 JavaUserClassesExt are loaded in the notes.ini
50. TroubleshootingAPI_UNABLE_TO_USE_CONNECTION
●
Problem: EngineRuntimeException exception when executing qptool migration command
●
Symptom: Enter password:com.filenet.api.exception.EngineRuntimeException: FNRCA0031E:
API_UNABLE_TO_USE_CONNECTION: The URI for server communication cannot be determined
from the connection object http://myserver.com/wsi/FNCEWS40MTOM. Message was: Connection
refused: connect
●
Cause: There is no connection to the FileNet server
●
Resolving the problem: Open a browser and see if you can connect to the url
http://myserver.com/wsi/FNCEWS40MTOM, you should check that the server is running and that there
is no firewalls between your QD server and CCM server blocking your access.
51. Troubleshooting
Logging info
To enable java logging, add the following line to the notes.ini file. There is no need to restart the
Domino server.
QuickPlaceJavaLogging=3
Detailed migration log information is recorded in the Domino console log.
