Saving your customizations

Before migrating or updating HCL Connections, back up and make notes of your customizations.

Only some of the customizations that you made to HCL Connections 6 CR6 application files and custom fields are preserved by the migration tool (the lc-export and lc-import commands). Ensure that you reapply your customizations after migration.

Customized files and themes

The update and migration processes change several configuration files, including files that you customized. Customized files can include header and footer HTML files, CSS and JSP files, themes, and several other files that are listed in this topic.

You must manually migrate the files that are referenced in the Migrate manually column of the following table:
Table 1. Configuration files to migrate
Customization Automatically migrated Migrate manually
User interface (customized CSS, JSP, and HTML; labels and strings).

Customized string files are preserved in the customization directory but you might need to rename some string files to match new Java and Dojo package names in HCL Connections 6 CR6.

Partially. Yes.
Template configuration

Manual post-migration steps might be required, see the Post-migration steps for profile types and profile policies topic.

Partially. See the post-migration steps.
Header and Footer

The customized header and footer are preserved in the customization directory, which is not migrated. You must update your customized header and footer to match the new layout and functionality of HCL Connections 6 CR6.

No. Yes.

Email notification templates

Email notification templates have been translated from JSP to FreeMarker. For more information, see the Customizing notifications topic.

Merge your existing customizations with the new Notification templates in the profile_root/Dmgr01/config/cells/cell_name/LotusConnections-config/notifications directory. If a global customization exists for all emails, then you only need to customize the shared resources. If JSP templates were customized in the 6 CR6 customization folders, then you can remove them.

No. Yes.
Blog themes Partially. Yes.
Community themes

The default Communities themes are migrated automatically. However, must redefine any custom theme.

Yes Redefine any custom themes.
Business cards

The Links and Actions attributes of business cards are migrated when the LotusConnections-config.xml and profiles-config.xml are migrated. Link definitions defined as attributes to each service in the LotusConnections-config.xml file are migrated to the new LotusConnections-config.xml file.

Manual steps may also be required to migrate profile customizations for business cards from 6 CR6 as described in the Post-migration steps for profile types and profile policies topic.

Yes. Partially.
Security role mappings

Redefine your security role mappings. For more information about security role mapping, see the Security role to user or group mapping topic in the WebSphere® Application Server Information Center.

No. Yes.

Customized extended service names are not migrated. Copy any customized XSD elements to the 6 CR6 service-location.xsd file.

Partially. Yes.

Copy the 6 CR6 version of the profiles-policy.xml file to the 6.5 deployment, overwriting the 6.5 version of the file. For more information, see the Post-migration steps for profile types and profile policies topic.

No. Yes.

Redefine customized Profile field validation settings.

No Yes.

The file path and contents of JavaScript string customizations have changed and require manual migration. For more information about the locations of JavaScript files, see the Customizing strings sourced in JavaScript topic.

The ui-extensions framework is deprecated, so you must manually migrate your 6 CR6 JavaScript customizations. For more information, see the Extending JavaScript in Connections topic.

No. Yes