Copying content stores

Copy data from your HCL Connections 50. or 5.5 content stores to your 6.0 deployment.

Before you begin

Ensure that you create new content stores when you install HCL Connections 6.0.

About this task

You can reuse content stores from your 5.0 or 5.5 deployment by copying the data to the new content stores in your 6.0 deployment. You do not need to copy local content stores because those directories are re-created by the 6.0 deployment.
Note: Do not copy the network path shared_content_store/provision directory. This folder contains program binary files only. It does not contain user content.
Note: IBM® Connections 5.0 GA, 5.0 (with CRs), 5.5 GA and 5.5 (with CRs) can be migrated directly to Connections 6.0.

To copy data from your 5.0 or 5.5 content stores, complete the following steps:

Procedure

  1. Locate the content stores in your 5.0 or 5.5 deployment.
  2. Copy the 5.0 or 5.5 data to the corresponding content store in your 6.0 deployment.
    Notes:
    • Once copied to the 6.0 deployment, rename the statistics subdirectories under activities, communities, and profiles to statistic.
    • If you are doing a side-by-side migration, you might need to rename the profiles statistic subdirectories after you copy to reflect the node and cluster names on the target system.
  3. Use the following table as a guide to organizing the content stores:
    Notes:
    • The table excludes content that is generated by the Search application, such as indexes and statistics.
    • If you created extra content stores, copy these content stores and the default content stores in the table. For Activities, for example, the content stores that you must copy are defined in the objectStore element of the oa-config.xml file.
    Table 1. Content stores that must be copied
    Content Store Location
    shared_content_store/audit
    shared_content_store/activities/content
    shared_content_store/activities/statistics
    shared_content_store/blogs/upload
    shared_content_store/ccm
    shared_content_store/communities/statistics
    shared_content_store/dogear/favorite
    shared_content_store/files/upload
    shared_content_store/forums/content
    shared_content_store/profiles/statistics
    shared_content_store/wikis/upload
    shared_content_store/customization
    Note: For shared_content_store/customization, if you updated Connections JSPs, CSS, or other files from the prior version of Connections, you must remerge your changes into the /customization directory by using new Connections source files. In this case
    1. Back up the /customization directory before migrating Connections.
    2. Rename the /customization directory to a temporary name so that the old customizations are not picked up when the new applications are started.
    3. Continue to step d after you finish installing the new version of Connections.
    4. Verify that the base product works without your customizations before you proceed with the remaining steps.
    5. For each file in the renamed customization directory, determine:
      1. Whether it is a Connections file that was customized.
      2. If so, locate the new version of the file and determine whether the file must still be customized.
      3. If so, use the new file from Connections as the base and apply your necessary customizations.
    6. Restore the /customization directory to its original name and then test the customization.