Restoring FileNet® components after migrating to IBM® 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 IBM® 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 IBM® Connections 6.0.
Procedure
- Update Connections Content Manager as explained in the IBM technote, IBM Connections 6.0 CR requirements for IBM 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:
- Start IBM® Connections and Connections Content Manager.
- Access ACCE.
- Navigate to .
- 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:
- Create two working directories, examples:
D:\CCM_WORK\OLD_EAR
D:\CCM_WORK\NEW_EAR
- 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
- Copy Engine-ws.ear of the IBM®
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
- Run the following
command:
Where:java -jar BootstrapConfig.jar -e D:\CCM_WORK\OLD_EAR\Engine-ws.ear -j D:\CCM_WORK\NEW_EAR\Engine-ws.ear
- BootstrapConfig.jar is under <connections_root>\FileNet\ContentEngine\lib on Windows™ or /FileNet/ContentEngine/lib on Linux™/AIX®.
- -e introduces the source (old) EAR file.
- -j introduces the target (new) EAR file.
- Java can be the executable from WebSphere®, for example: D:\IBM\Websphere\AppServer\java\bin\java.exe
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.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
- Log in to the WebSphere® Application Server
administrative console, then navigate to .
- Choose FileNetEngine for update.
- Replace the entire application, specify the file path to the target (new) Engine-ws.ear, and then click Next.
- Accept the default setting on the next page, and then click Next.
- Accept the default installation options, and then click Next.
- Accept the Map modules setting, and then click Next.
- Review the summary, and then click Finish.
- Create two working directories, examples:
-
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.