Restoring FileNet components after migrating to IBM Connections 5.0

After migrating to Connections 5.0, complete the migration of IBM® Connections Content Manager from 4.5 to 5.0.

About this task

Complete the migration of IBM Connections Content Manager from 4.5 to 5.0 by restoring FileNet® components that you backed up before installing IBM Connections 5.0.

Note: During migration the IBM Connections Content Manager databases (FNGCD and FNOS) are migrated automatically by the FileNet upgrade scripts. No additional actions are required other than those detailed in this section Migrating to IBM Connections 5.0. This implicit migration happens the first time the FileNet Content Engine application is started after being updated. Progress of the migration can be viewed on the FileNet status page as described in Checking the automatic upgrade status for Content Engine data .

Procedure

  1. If you connected to the Connections 4.5 databases during IBM Connections 5.0 installation, you must update the configuration of the FileNet storage area:
    1. Start IBM Connections and Connections Content Manager.
    2. Access ACCE.
    3. Navigate to IC Domain > Object Stores > ICObjectStore > Administrative > Storage Areas > ICObjectStore > Properties.
    4. Change the value in Root Directory path as needed.
  2. Migrate the encryption keys for the FileNet Content Engine EAR file from Connections 4.5 that you backed up before the Connections 5.0 installation:
    1. Back up the Engine-ws.ear file of the IBM Connections 5.0 environment under the temp2 directory.
    2. Run the following command:
      java -jar BootstrapConfig.jar -e \temp1_device/Engine-ws.ear -j \temp2_device/Engine-ws.ear
      Where:
      • BootstrapConfig.jar is under <connections_root>\addons\ccm\ContentEngine\lib on Windows or /addons/ccm/ContentEngine/lib on Linux/AIX.
      • -e introduces the source (old) EAR file.
      • -j introduces the target (new) EAR file.
    3. Copy the new target EAR file (the file referenced by the -j switch in the command) to <connections_root>\addons\ccm\ContentEngine\tools\configure\profiles\CCM\ear, replacing the Engine-ws.ear in the directory.
    4. Log into the WebSphere® Application Server administrative console, then navigate to Applications > WebSphere Enterprise Applications.
      1. Choose FileNetEngine for update.
      2. Replace the entire application, specify the file path to the target (new) Engine-ws.ear, and then click Next.
      3. Accept the default setting on the next page, and then click Next.
      4. Accept the default installation options, and then click Next.
      5. Accept the Map modules setting, and then click Next.
      6. Review the summary, and then click Finish.
  3. If you determined that the filenetAdmin user (usually the same as the ConnectionsAdmin user) is a local WIM user, restore the backup of fileRegistry.xml file from the 4.5 server to ensure that the WebSphere Application Server running 5.0 has the same file-based user registry to guarantee that user's ID is the same. If the location does not match exactly, as when changing operating systems, refer to Optional: Changing the location on disk used to store library content for more information.