Home

 

Post-migration tasks

After migration, you need to perform further tasks to ensure that your new deployment is complete.

Ensure that you have successfully migrated to Lotus Connections 2.5 and that you have completed any required post-installation tasks.

To finalize the migration process...

1. Re-apply any proxy configurations, if necessary. For more information, see the Configuring the AJAX proxy and Configuring a reverse caching proxy topics.

2. If you have changed the root URL of any feature, and if the old and new URLs point to the same webserver, redirect requests to the new URL:

   1. Open the httpd.conf file in a text editor. The file is located in the ibm_http_server_root/conf directory.

   2. Comment out the following line:

      LoadModule rewrite_module modules/mod_rewrite.so

   3. Add the following statements:

      This example redirects all requests to the pre-migration URL of https://blog201.example.com/weblogs/* to the post-migration URL of https://blog25.example.com/newblogs/*. Substitute your own URLs as appropriate.

      RewriteEngine on

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

      Listen 0.0.0.0:443

      <VirtualHost *:443>

      RewriteEngine on

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

      ServerName blog25.example.com

      SSLEnable

      </VirtualHost>

      SSLDisable

3. Optional: Delete your pre-migration search indexes. For more information, see the Managing the Index topic in the Lotus Connections 2.0.1 information center.

   The Search feature in 2.5 stores its indexing tasks in a database, whereas these tasks were stored in the homepage-config.xml file in 2.0.1. To edit the indexing tasks, do not edit the search-config.xml file; instead, follow the relevant instructions in the Managing the search index topic.

4. Update the favicon.directory attribute in the 2.5 dogear-config-cell.xml file:

   1. Open the 2.0.1 dogear-config-node.xml file, usually located in the app_server_root/profiles/<profile>/config/cells/<cell>/nodes/<node>/LotusConnections-config directory, and locate the favicon.directory attribute.

   2. If the value of the favicon.directory attribute is ${DOGEAR_FAVICON_DIR}, then your configuration is correct and you can skip the remainder of this step.

   3. Copy the value of the favicon.directory attribute from the 2.0.1 file into the same attribute in the 2.5 dogear-config-cell.xml file, usually located in the app_server_root/profiles/<profile>/config/cells/<cell>/LotusConnections-config The attribute should have the following format: <stringProperty name="favicon.directory">${DOGEAR_FAVICON_DIR}</stringProperty>

   4. Save the dogear-config-cell.xml file.

   5. From the WAS admin console, restart the Dogear feature.

   For more information about configuring favicons, see the Configuring favicons topic.

5. Optional: Remove the Location and ErrorDocument stanzas if you added them to the httpd.conf file before migrating. For more information, see the Preparing Lotus Connections for maintenance topic.

6. Optional: If you used Lotus Connections Connectors in release 2.01, such as Lotus Quickr™ and Confluence, re-install them.

7. Optional: If you defined a server whitelist in release 2.0.1 for publishing file attachments from Activities to Lotus Quickr, re-define it after migration.

8. Update any configuration settings that you customized in 2.0.1. For more information, see the Saving your customizations topic.

Migrating to Lotus Connections 2.5

Saving your customizations

Manage the index

 

Related tasks

Prepare Lotus Connections for maintenance

Configure favicons

Migrating a stand-alone deployment

Migrating a network deployment

---

+

Search Tips   |   Advanced Search