Saving your customizations
Before upgrading HCL Connections, back up and make notes of your customizations.
Only some of the customizations that you made to Connections 6.5 CR1 application files and custom fields are preserved during an upgrade, and only if you are performing an in-place or hybrid upgrade using the Installation Manager's Update function. You'll still need to reapply some customizations after upgrading.
Customized files and themes
The update process changes 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.
| Customization | Automatically preserved by Update function | 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.5 CR1 |
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, Footer, and other JSPs copied from the
Common app Any customized artifacts are preserved in the customization directory, which is not migrated. You must update your customized artifacts to match the new layout and functionality of Connections 7.0. |
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.5 CR1 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.5 CR1 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 |
| service-location.xsd Customized extended service names are not migrated. Copy any customized XSD elements to the 6.5 CR1 service-location.xsd file. |
Partially | Yes |
| profiles-policy.xml Copy the 6.5 CR1 version of the profiles-policy.xml file to the 7.0 deployment, overwriting the 7.0 version of the file. For more information, see the Post-migration steps for profile types and profile policies topic. |
No | Yes |
| validation.xml Redefine customized Profile field validation settings. |
No | Yes |
| JavaScript™
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.5 CR1 JavaScript™ customizations. For more information, see the Extending JavaScript™ in Connections topic. |
No | Yes |
| Touchpoint If you modified parts of the
Touchpoint application within the
installedApps path in 6.5 CR1 (like
JSPs or language-related properties), make sure you back up
these modifications. After upgrading to Connections 7,
modify the default product again based on your
requirements. Note: This kind of customization is not
recommended. |
No | Yes |
| Invite If the Invite feature is configured, transfer the settings from the configuration file (selfregistration-config.xml) to the new environment. |
No | Yes |
| Proxy configuration If modified, LC-config\opensocial-proxy-rules, which affects things like URL or protocol whitelisting in blogs and wikis, needs to be migrated and modifications reapplied. |
No | Yes |
| *In a side-by-side upgrade, you need to reapply customizations to ALL migrated files. | ||