Restoring FileNet® components after migrating to HCL Connections™ 6.0

After you migrate to HCL Connections™ 6.0 CR1, update Connections Content Manager and then restore your FileNet® components.

About this task

Complete the migration of Connections Content Manager from 5.0 or 5.5 to 6.0 CR1 by updating restoring FileNet® components that you backed up before you installed Connections 6.0.

Procedure

Update Connections Content Manager as explained in the technote, Connections 6.0 CR requirements for FileNet for use with Connections Content Manager (CCM).
If you connected to the Connections 5.0 or 5.5 databases during ® 6.0 installation, you must update the configuration of the FileNet® storage area:
1. Start 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 5.0 or 5.5 that you backed up before the 6.0 installation:
1. Create two working directories, examples:
```
D:\CCM_WORK\OLD_EAR
```
```
D:\CCM_WORK\NEW_EAR
```
2. Copy Engine-ws.ear from the 5.0 or 5.5 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 Connections 6.0 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 5.0 or 5.5 server. This action ensures that the WebSphere® Application Server running 6.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, see Optional: Changing the location on disk used to store library content for more information.