Post-migration tasks

After you migrate to HCL Connections™ 6.0, perform post-migration tasks to ensure that your new deployment is complete.

Before you begin

Ensure that you complete any required post-installation tasks.

Ensure that you backed up customized files from your Connections 5.0 or 5.5. For more information, see the Saving your customizations topic.

About this task

After you update or migrate Connections, you must update any custom fields and customized files that might not be automatically updated or migrated.

To finalize the migration process, complete the following steps:

Procedure

  1. Reapply the customizations that you used in 5.0 or 5.5. For more information about migrating customizations, see the Saving your customizations topic.
    1. Migrate any JSP, CSS, and string customizations.
    2. Verify that your Blogs themes are present in 6.0. If they are not, manually update them. For more information, see the Customizing a blog theme topic.
    3. Update your customized Community themes.
    4. Copy the 5.0 or 5.5 version of the profiles-policy.xml file to the 5.0 deployment, overwriting the 6.0 version. For more information, see the Post-migration steps for profile types and profile policies topic.
    5. Copy the customized XSD elements of the 5.0 or 5.5 service-location.xsd file to the 6.0 version of the file.
    6. Redefine customized Profiles fields in the validation.xml file.
    7. Migrate your 5.0 or 5.5 JavaScript™ customizations. For more information, see Customizing strings sourced in JavaScript and Extending JavaScript in Connections.
  2. Reapply any proxy configurations, if necessary. For more information, see Configuring the Ajax proxy and Configuring a reverse caching proxy.
  3. Required: Migrate your 5.0 or 5.5 premigration content search indexes.
    For more information, see Migrating the search index from the Connections 5.0 or 5.5 deployment to Connections 6.0.
  4. Synchronize the member database tables for each Connections application with the data in the user directory. For more information, see Synchronizing user data using administrative commands.
    Note: You must have a web server that is configured for Connections before you synchronize Profiles and the LDAP directory.
  5. If you changed the root URL of any Connections application, and if the old and new URLs point to the same web server, redirect requests to the new URL.
    1. Open the httpd.conf file in a text editor. The file is in the http_server_root/conf directory.
    2. Uncomment the following line:

      LoadModule rewrite_module modules/mod_rewrite.so

    3. Add the following statements:
      Note:
      • The lines that refer to weblogs redirect all requests for the pre-migration URL of https://blog50.example.com/weblogs/* to the post-migration URL of https://blog50.example.com/newblogs/*. Substitute your own URLs.
      • The lines that refer to bookmarklet redirect the path of the bookmarklet feature to make it work in 6.0. Use the exact URLs shown.

      RewriteEngine on

      RewriteRule /weblogs/(.*) https://blog50.example.com/newblogs/$1 [R,L]

      RewriteCond %{REQUEST_URI} /(.*)/bookmarklet/(.*)

      RewriteCond %{REQUEST_URI} !^/connections/bookmarklet/(.*)

      RewriteRule ^/(.*)/bookmarklet/(.*) /connections/bookmarklet/$2 [noescape,L,R]

      Listen 0.0.0.0:443

      <VirtualHost *:443>

      RewriteEngine on

      RewriteRule /weblogs/(.*) https://blog50.example.com/newblogs/$1 [R,L]

      ServerName blog50.example.com

      SSLEnable

      RewriteCond %{REQUEST_URI} /(.*)/bookmarklet/(.*)

      RewriteCond %{REQUEST_URI} !^/connections/bookmarklet/(.*)

      RewriteRule ^/(.*)/bookmarklet/(.*) /connections/bookmarklet/$2 [noescape,L,R]

      </VirtualHost>

      SSLDisable

  6. If you installed and configured HTTP Server before you install 6.0, map the host name of your deployment in the LotusConnections-config.xml file. For more information, see the Updating Connections to the HTTP server topic.
  7. Optional: Remove the Location and ErrorDocument stanzas if you added them to the httpd.conf file before migrating. For more information, see the Informing users of a migration or update topic.

What to do next

Important: After you complete the mandatory post-installation tasks, update the deployment with the latest fixes. For more information, see Updating Connections 6.0 .