After you apply CR2, you must run scripts to update FileNet® Content Engine Server (5.2.1.0 FP4), FileNet
Content Engine client (5.2.1.0 FP4), and FileNet
Collaboration Services in a new FileNet deployment. The
new deployment is the one that was installed as part of IBM®
Connections 5.5. FileNet Collaboration Services is part of
IBM Content Navigator (2.0.3 FP7).
Before you begin
- Back up the FileNet Global Configuration Database
(FNGCD) and FileNet Object Store (FNOS) as part of
Backing up IBM Connections.
- Install IBM Connections 5.5 CR2 and migrate database
schemas for CR2.
- Download and extract the FileNet updates package. For
more information, see Downloading the latest Cumulative Refresh (CR) and related
updates.
- Make sure that you have at least 6 GB in %TEMP% (Windows™) or /tmp (AIX® or Linux™) disk.
About this task
First, run the script to update the FileNet
Content Engine server. Then, run the script to update the FileNet Content Engine client, and FileNet
Collaboration Services.
Procedure
-
Download the FileNet update packages for your
operating system to a temporary folder. For example, in Windows:
C:\Install\CONNECTIONS-CR2\FILENETCR2.
- 2.0.3-ICN-FP007-WIN.zip
- 5.2.1.4-P8CPE-CLIENT-WIN-FP004.zip
- 5.2.1.4-P8CPE-WIN-FP004.zip
-
Extract the packages and make a note of the location. You specify the location of the
.exe and .bin files when you run the scripts.
-
Make sure that the Deployment Manager, node agents, and Connections nodes are all
running.
-
Open a command line window.
-
For Linux and AIX
only, assign permission to
connections_root/FileNet.update/scripts as follows:
run chmod -R 777 * under the folder /opt/IBM/Connections/FileNet.update/scripts
-
Go to the following folder.
AIX or Linux
/opt/IBM/Connections/FileNet.update/scriptsWindows
C:\opt\IBM\Connections\FileNet.update\scripts
-
Run the script with the following parameters to back up the Deployment Manager profile.
AIX or Linux
./backup.sh -conn_home_path=/opt/IBM/Connections
Windows
backup.bat -conn.home.location=C:\IBM\Connections
-
Run the script with the following parameters to update the FileNet Content Engine server.
If you don't append these parameters, you are prompted for them while the update script runs.
Linux
./update-ce.sh -was_dm_path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -was_admin_user=admin
-was_admin_password=password -conn_home_path=/opt/IBM/Connections -ce_fp_installer_location=
/software/FileNet/5.2.1.4-P8CPE-LINUX-FP004/5.2.1.4-P8CPE-LINUX-FP004.BIN
Windows
update-ce.bat -was.dm.path=C:\IBM\WebSphere\AppServer\profiles\Dmgr01 -was.admin.user=admin
-was.admin.password=password -conn.home.location=C:\IBM\Connections -ce.fp.installer.location=
C:\filenetFixpack\5.2.1.4-P8CPE-WIN-FP004.EXE
This process can take up to 60 minutes. The fn-ce-update.log in the
scripts folder provides information as the script runs.
-
Verify that the Content Engine is updated to the latest version.
Open ce_version.txt in the following folder:
Windows
C:\IBM\Connections\FileNet\ContentEngine
Linux/AIX:
/opt/IBM/Connections/FileNet/ContentEngine
Note: Use this URL to verify the Content Engine: <your
server><port>(if required)/FileNet/Engine.
-
Test that the FileNet application is started.
Open a browser and go to the hostname:port/FileNet/Engine
URL. If the page does not open, the Content Engine is not working or the FileNet application was not started. Try restarting Connections to ensure
that the update took effect and that the FileNet
application is started.
-
With the Deployment Manager, node agents, and Connections nodes all running, return to a
command line.
-
Go to the connections_root/FileNet.update/scripts
folder.
AIX or Linux
/opt/IBM/Connections/FileNet.update/scriptsWindows
C:\opt\IBM\Connections\FileNet.update\scripts
-
Run the script with the following parameters to update the FileNet Content Engine Client and FileNet
Collaboration Services.
If you do not append these parameters, you are prompted for them while the update script
runs.
AIX
./update-fncs-ceclient.sh -was.dm.path=websphere_root/profiles/Dmgr01
-was.admin.user=admin -was.admin.password=password
-fncs.fp.installer.location=download_location/IBM_CONTENT_NAVIGATOR-2.0.3.2-FP002-AIX.BIN
-doInstallFNCS=y -ceclient.fp.installer.location=download_location/5.2.1-P8CPE-CLIENT-AIX.BIN
-doInstallCEClient=y -supportIBMDocs=y
Linux
./update-fncs-ceclient.sh -was_dm_path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01
-was_admin_user=admin -was_admin_password=password -conn_home_path=
/opt/IBM/Connections -doSetAnonymous=n -fncs_fp_installer_location=
/software/FileNet/2.0.3-ICN-FP007-LINUX/IBM_CONTENT_NAVIGATOR-2.0.3.7-FP007-LINUX.bin
-ceclient_fp_installer_location=/software/FileNet/5.2.1.4-P8CPE-CLIENT-LINUX-FP004/
5.2.1.4-P8CPE-CLIENT-LINUX-FP004.BIN
Windows
update-fncs-ceclient.bat -was.dm.path=C:\IBM\WebSphere\AppServer\profiles\Dmgr01
-was.admin.user=admin -was.admin.password=password -conn.home.location=C:\IBM\Connections
-doSetAnonymous=n -fncs.fp.installer.location=C:\filenetFixpack\IBM_CONTENT_NAVIGATOR-2.0.3.7-FP007-WIN.exe
-ceclient.fp.installer.location=C:\filenetFixpack\5.2.1.4-P8CPE-CLIENT-WIN-FP004.EXE
Note: If you set doSetAnonymous to 'y' or 'Y', you must also specify
anonymous_user and -anonymous_password. If you set
doSetAnonymous to 'n' or 'N', you do not need to specify
anonymous_user and -anonymous_password.
-
Verify that the Content Engine client and FileNet
Collaboration Services (Content Navigator) are updated to the latest version.
Open ce_version.txt in the following folder:
Windows
C:\IBM\Connections\FileNet\CEClient
Linux/AIX:
/opt/IBM/Connections/FileNet/CEClient
Note: To verify the Content Navigator, use the following URL:
<yourserver>/dm.
-
Check the FileNet Collaboration Services (Content Navigator) log file
(version.txt) for errors.
Open version.txt in the following folder:
Windows
C:\IBM\Connections\FNCS
Linux/AIX:
/opt/IBM/Connections/FNCS