Saving your customizations
Before migrating or updating IBM® Connections, back up and make notes of your customizations.
Only some of the customizations that you made to IBM Connections 4.5 or 5.0 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. Custom CSS files are preserved in the customization directory, but you must update them to match the new One UI version implemented in this release. For more information about the One UI standard used in IBM Connections 5.5, refer to the ICS UI Developer Guide: http://infolib.lotus.com/resources/oneui/3.0/docPublic/index.htm
| 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 IBM Connections 5.5. Custom CSS files are preserved in the customization directory but you must update them to match the new One UI version in IBM Connections. For more information, refer to the ICS UI Developer Guide: http://infolib.lotus.com/resources/oneui/3.0/docPublic/index.htm |
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 IBM Connections 5.5. |
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 4.5 or 5.0 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 4.5 or 5.0 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 5.5 service-location.xsd file. |
Partially. | Yes. |
| profiles-policy.xml Copy the 4.5 or 5.0 version of the profiles-policy.xml file to the 5.5 deployment, overwriting the 5.5 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 4.5 JavaScript customizations. For more information, see the Extending JavaScript in IBM Connections topic. |
No. | Yes |