Restoring FileNet components after migrating to IBM Connections 5.5

After you migrate to Connections 5.5, restore your FileNet® components.

About this task

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

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 the steps detailed in this section Migrating to IBM Connections 5.5. This implicit migration happens the first time the FileNet Content Engine application is started after it is 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

If you connected to the Connections 4.5 or 5.0 databases during IBM Connections 5.5 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.
Migrate the encryption keys for the FileNet Content Engine EAR file from Connections 4.5 or 5.0 that you backed up before the Connections 5.5 installation:
1. Create two working directories, examples:
```
D:\CCM_WORK\OLD_EAR
```
```
D:\CCM_WORK\NEW_EAR
```
2. Copy Engine-ws.ear from the IBM Connections 4.5 or 5.0 environment to D:\CCM_WORK\OLD_EAR.
  Note: Engine-ws.ear is usually in: <connections_root>\addons\ccm\ContentEngine\tools\configure\profiles\ccm\ear
3. Copy Engine-ws.ear of the IBM Connections 5.5 environment to D:\CCM_WORK\NEW_EAR
  Note: Engine-ws.ear is usually in: <connections_root>\FileNet\ContentEngine\tools\configure\profiles\ccm\ear
4. Run the following command:
```
java -jar BootstrapConfig.jar -e D:\CCM_WORK\OLD_EAR\Engine-ws.ear -j 
D:\CCM_WORK\NEW_EAR\Engine-ws.ear
```
  Where:
  1. BootstrapConfig.jar is under <connections_root>\FileNet\ContentEngine\lib on Windows™ or /FileNet/ContentEngine/lib on Linux™/AIX®.
  2. -e introduces the source (old) EAR file.
  3. -j introduces the target (new) EAR file.
  4. Java can be the executable from WebSphere®, for example: D:\IBM\Websphere\AppServer\java\bin\java.exe
  Example:
```
D:\IBM\WebSphere\AppServer\java\bin\java.exe -jar 
D:\IBM\Connections\FileNet\ContentEngine\lib\BootstrapConfig.jar -e 
D:\CCM_WORK\OLD_EAR\Engine-ws.ear -j 
D:\CCM_WORK\NEW_EAR\Engine-ws.ear
```
  d. Copy the modified target EAR file (D:\CCM_WORK\NEW_EAR) (the file that is referenced by the -j switch in the command) to <connections_root>\FileNet\ContentEngine\tools\configure\profiles\CCM\ear, replacing the backed-up Engine-ws.ear.
5. Log in to 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.
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 or 5.0 server. This action ensures that the WebSphere Application Server running 5.5 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, see Optional: Changing the location on disk used to store library content for more information.