Only some of the customizations that you made to IBM
Connections 3.0.1 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 4.0, refer to the ICS UI Developer Guide: http://infolib.lotus.com/resources/oneui/3.0/docPublic/index.htm
You must manually migrate the files that are referenced in the Migrate manually
column of the following table:
Table 1. Configuration files to migrate
Parent topic: Updating and migrating
Updating IBM Connections 4.0
Installing fix packs
Installing interim fixes
Post-migration steps for profile types and profile policies
Customizing a blog theme
User interface customization
Customization best practices
Preparing IBM Connections for maintenance
Backing up IBM Connections
Preparing to migrate the media gallery
Migrating to IBM Connections 4.0
Rolling back a migration
Specifying a custom field as required and declaring maximum field length
Security role to user or group mapping
|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 4.0.
Custom CSS files are preserved in the customization directory but you must update them to match the new One UI version in IBM Connections 4.0. For more information, refer to the ICS UI Developer Guide: http://infolib.lotus.com/resources/oneui/3.0/docPublic/index.htm
Manual post-migration steps may 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 4.0.
|Email notification templates.|
Email notification templates have been translated from JSP to FreeMarker. For more information, see the Customizing standard 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 3.0.1 customization folders - you can remove them.
The default Communities themes are migrated automatically. However, must redefine any custom theme.
|Yes||Redefine any custom themes.|
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 LCC.xml file are migrated to the new LCC.xml file.
The photo and contact information in business cards is migrated from the profiles-config.xml file in 3.0.1 to the new businessCardInfo.ftl FreeMarker Template Language file in 4.0. Other elements in the profiles-config.xml file are migrated to the new profiles-config.xml file.
Manual steps may also be required to migrate profile customizations for business cards from 3.0.1 as described in the Post-migration steps for profile types and profile policies topic.
|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.
Customized extended service names are not migrated. Copy any customized XSD elements to the 4.0 service-location.xsd file.
Copy the 3.0.1 version of the profiles-policy.xml file to the 4.0 deployment, overwriting the 4.0 version of the file. For more information, see the Post-migration steps for profile types and profile policies topic.
Redefine customized Profile field validation settings.
|IBM Connections Connector for Lotus® Quickr®.|
The IBM Connections Connector for Lotus Quickr was updated for IBM Connections 4.0. You must obtain the 4.0 version from the catalog.
|No. ||Reinstall the connector.|
|Server whitelist for publishing file attachments from Activities to Lotus Quickr.||No.||Redefine the whitelist.|