Post-migration tasks

After you migrate to IBM® Connections 5.5, perform post-migration tasks to ensure that your new deployment is complete.

1. Reapply the customizations that you used in IBM Connections 4.5 or 5.0. 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 5.5. 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 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.
   5. Copy the customized XSD elements of the 4.5 or 5.0 service-location.xsd file to the 5.5 version of the file.
   6. Redefine customized Profiles fields in the validation.xml file.
   7. Migrate your 4.5 or 5.0 JavaScript customizations. For more information, see Customizing strings sourced in JavaScript and Extending JavaScript in IBM 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 4.5 or 5.0 premigration content search indexes. For more information, see Migrating the search index from the Connections 4.5 or 5.0 deployment to Connections 5.5.
4. Synchronize the member database tables for each IBM 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 IBM Connections before you synchronize Profiles and the LDAP directory.
5. If you changed the root URL of any IBM 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 ibm_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://blog45.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 5.5. 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://blog40.example.com/newblogs/$1 [R,L]

      ServerName blog40.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 IBM HTTP Server before you install IBM Connections 5.5, map the host name of your deployment in the LotusConnections-config.xml file. For more information, see the Updating IBM Connections to use 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 Preparing IBM Connections for maintenance topic.