Verify and test the IBM Connections installation
Once IBM Connections 4.5 has been installed and completely configured, spend some time to test all the components before migrating any Quickr place. This is especially important if there are customizations in the environment. Pay particular attention to the federated repository configurations around the group definitions. If custom ID attributes are defined, ensure that the custom attributes are properly configured. Since the migration tool uses the unique ID to perform the migration of the membership information, it becomes especially critical that the unique IDs are properly defined.
Prioritize custom forms
According to the current design and implementation of the document class in Filenet, all property templates contained in document class are maintained in the DocVersion table. Each time a new document class is created, the DocVersion table is altered to add the columns corresponding to the property template contained in the new document class.
The underlying database has a row length limitation, which restricts the maximum byte length of each row in table. Since each column created for the property template uses some byte space to store data, eventually the row length limitation of the DocVersion table is exceeded, resulting in failure of the document class creation operation.
Therefore, it is strongly recommended that customized forms be prioritized from most significant to least significant, so as to avoid or minimize the need for performing manual cleanup, which is necessary for restoring the DocVersion table to its initial status for preparing to re-migrate customized forms. The prioritized list of custom forms is across all places in the environment, not just within a single place.
Generate the restricted resource list
In the current implementation of the migration tool, the room/folder/document reader ACL setting is not preserved after the Quick Domino migration. All community members are granted reader access to the content contained in the community, regardless of the original Quickr Domino ACL setting. Generating the restricted resource provides an opportunity to identify such restrictions and consider the implications should the place be migrated.
Migrate places and forms to a test environment
Migrating places and forms to a test environment first helps minimize issues for when they are migrated in production. This is especially important for custom forms. Generate a list of prioritized custom forms and migrate them until the message "The row length limitation of the underlying database has been exceeded, incapable of creating document class any further" is returned. This helps determine at which point the custom forms can no longer be migrated if there are enough forms to reach the row limit. Adding QuickPlaceJavaLogging=3
to the server's notes.ini
increases the logging levels.
User and group mapping
The tool refers to the list of user & group mapping files at the time the migration is performed. These mapping files should be re-created just prior to the place migrations. This helps ensure that the complete list of users and groups are available to the tool. If IBM Connections is using a different LDAP directory than Quickr Domino,then groups should be synchronized from Quickr Domino native or LDAP to the LDAP directory used by IBM Connections. All groups that are used for Quickr Domino must be in the IBM Connections LDAP directory (and mapping files) before places can be migrated.