Upgrading FileNet® Collaboration Services only for CR1

The CR1 instructions for updating FileNet® Collaboration Services are provided in this section as a convenience if you are still in the process of applying CR1 and are not planning to apply CR2 right away. After applying IBM® Connections 5.0 CR1, you must upgrade FileNet® Collaboration Services (FNCS) manually since FNCS is now a component of IBM® Content Navigator 2.0.3. Skip these procedures if you have already applied CR2 or have an existing FileNet deployment that was installed independently of IBM Connections.

Before you begin

This task is required only if you have installed Connections Content Manager (CCM) in IBM® Connections 5.0. Your Content Engine (CE) server must be running during this upgrade.
Note: Make sure there is 5 GB of free space before you upgrade.

About this task

The backup and update FNCS scripts only work for the new Connections Content Manager deployment; that is, a Connections Content Manager deployment (including CE, FNCS, CE client) that was installed and configured by IBM® Connections.
Note: Even if you had installed Connections Content Manager as a New Deployment in the 4.5 release, your deployment of CCM is still considered New if you intend to reuse the FileNet® domain and object store that were created in 4.5 and only want to install the new server infrastructure from the 5.0 release.

If you installed Connections Content Manager into an existing FNCS deployment (where CE, FNCS, and CE Client were installed and configured prior to installing IBM® Connections), then the backup and update scripts will not work. Instead, you will have to install FNCS 2.0.3 manually using the Content Navigator installer and configure required tasks.

Note: IBM® Connections Content Manager is supported on IBM® i starting with IBM® Connections 5.0.

Procedure

  1. Navigate to the folder where IBM® Content Navigator has been downloaded:
    • Windows™: IBM_CONTENT_NAVIGATOR-2.0.3-WIN.exe
    • AIX®: IBM_CONTENT_NAVIGATOR-2.0.3-AIX.bin
    • Linux™: IBM_CONTENT_NAVIGATOR-2.0.3-LINUX.bin
    • zLinux: IBM_CONTENT_NAVIGATOR-2.0.3-zLINUX.bin
  2. For Linux™ and AIX® only, assign permission to /opt/IBM/Connections/ccm/ccm/ccm as follows:
    run chmod -R 777 * under the folder  /opt/IBM/Connections/ccm/ccm/ccm
  3. Back up your current Connections Content Manager deployment as follows:
    1. Make sure that the Deployment Manager is running.
    2. Navigate to the connections_root/opt/IBM/Connections/ccm/ccm/ccm/scripts folder to run the backup script appropriate to your operating system:
      • For Windows™ use the backup.bat [-param value] ... [-paramN valueN] script with the following parameters:
        • was.dm.path is the path of WebSphere® Application Server Deployment Manager.
        • was.admin.user is the username of WebSphere® Application Server administrator. was.admin.user is the user id defined by the setting WasUserid in the <DMgr-profile>\ConfigEngine\properties\wkplc.properties file.
        • was.admin.password is the WebSphere® Application Server administrator password.
        For example:
        backup.bat -was.dm.path "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user wasadmin -was.admin.password passw0rd
      • For AIX® or Linux™ use the ./backup.sh [-param=value] ... [-paramN=valueN] script with the following parameters:
        • was.dm.path is the path of WebSphere® Application Server Deployment Manager.
        • was.admin.user is the username of WebSphere® Application Server administrator. was.admin.user is the user id defined by the setting WasUserid in the <DMgr-profile>/ConfigEngine/properties/wkplc.properties file.
        • was.admin.password is the WebSphere® Application Server administrator password.
        For example:
        ./backup.sh -was.dm.path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -was.admin.user=wasadmin -was.admin.password=passw0rd
      Note: If you don't append these parameters, you will be prompted for them while the backup script runs.
  4. Run the upgrade script as follows:
    1. Make sure that the FileNetEngine server's status is enabled (Status shows green checkmark) via the WebSphere® Application Server administrative console: Servers > Server Types > WebSphere application servers.
    2. Navigate to the connections_root/opt/IBM/Connections/ccm/ccm/ccm/scripts folder to run the update scrips for FNCS:
      • For Windows™, use the update-fncs-ceclient.bat script with the following parameters:
        • was.dm.path is the path of WebSphere® Application Server Deployment Manager.
        • was.admin.user is the username of the WebSphere® Application Server administrator. was.admin.user is the user id defined by the setting WasUserid in <DMgr-profile>\ConfigEngine\properties\wkplc.properties.
        • was.admin.password is the WebSphere® Application Server administrator password.
        • fncs.fp.installer.location is the location of FileNet® FNCS Fix pack installer.
        • doInstallFNCS Set to y if installing FNCS or n if not installing FNCS.
        • doInstallCEClient Set to y if install CE Client or n if not installing the CE Client.
        For example:
        update-fncs-ceclient.bat -was.dm.path "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user wasadmin -was.admin.password passw0rd -doInstallFNCS y -fncs.fp.installer.location C:\fncs-fp\installer\IBM_CONTENT_NAVIGATOR-2.0.3-WIN.exe -doInstallCEClient n
        Note: If your DM path contains space, add quotation marks to the path.
      • For AIX® or Linux™, use the ./update-fncs-ceclient.sh script with the following parameters:
        • was.dm.path is the path of WebSphere® Application Server Deployment Manager.
        • was.admin.user is the username of the WebSphere® Application Server administrator. was.admin.user is the user id defined by the setting WasUserid in the <DMgr-profile>/ConfigEngine/properties/wkplc.properties file.
        • was.admin.password is the WebSphere® Application Server administrator password.
        • fncs.fp.installer.location is the location of FileNet® FNCS Fix pack installer.
        • doInstallFNCS Set to y if installing FNCS or n if not installing FNCS.
        • doInstallCEClient Set to y if install CE Client or n if not installing the CE Client.
        For example:
        ./update-fncs-ceclient.sh -was.dm.path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -was.admin.user=wasadmin -was.admin.password=passw0rd -doInstallFNCS=y -fncs.fp.installer.location=/opt/build/IBM_CONTENT_NAVIGATOR-2.0.3-LINUX.bin -doInstallCEClient=n
      Note: If you don't append these parameters, you will be prompted for them while the update script runs.
  5. After the update process completes successfully, start the application named "navigator" in WebSphere® Application Server in order to use it.
    Note: The application name "fncs" in the previous version of FNCS has been changed to "navigator" in FNCS 2.0.3 and later.
  6. Map the new "navigator" application to the web server.

Results

If you do not have an existing P8 domain before you update FNCS, then you must create the P8 domain using the ccmDomain tool in order to use FNCS, as described in Configuring a new FileNet deployment for the first time.
If registering the FNCS add-ons fails, then you will have to register the add-ons manually. For FNCS 2.0.3 (IBM® Content Navigator), open a browser, enter http://hostname:port/dm/jsp/addons.jsp, and then click Install.
Note: The Content Engine Server must be started before running createGCD and createObjectStore.
If your update failed because you didn't start the Content Engine server before upgrading:
  • Start the Content Engine server.
  • Make sure your FNCS 2.0.3 is installed by checking the version number in connections_root/addons/ccm/FNCS/version.txt.
  • Run the update-fncs-ceclient.bat/.sh script without installing FNCS 2.0.3 again, being sure to set doInstallFNCS to be n. For example:
    • On Windows™:
      update-fncs-ceclient.bat -was.dm.path "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user wasadmin -was.admin.password passw0rd -doInstallFNCS n -doInstallCEClient n
    • On AIX/Linux:
      ./update-fncs-ceclient.sh -was.dm.path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -was.admin.user=wasadmin -was.admin.password=passw0rd -doInstallFNCS=n -doInstallCEClient=n
If your update failed because you didn't have enough space to install FNCS 2.0.3:
  1. Clear at least 5 GB of space.
  2. Rerun the update-fncs-ceclient.bat/.sh script as before, being sure to set -doInstallFNCS y -fncs.fp.installer.location C:\fncs-fp\installer\IBM_CONTENT_NAVIGATOR-2.0.3-WIN.exe -doInstallCEClient=n. For example:
    • For Windows™:
      update-fncs-ceclient.bat -was.dm.path "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user wasadmin -was.admin.password passw0rd -doInstallFNCS y -fncs.fp.installer.location C:\fncs-fp\installer\IBM_CONTENT_NAVIGATOR-2.0.3-WIN.exe -doInstallCEClient n
    • For AIX/Linux:
      ./update-fncs-ceclient.sh -was.dm.path=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -was.admin.user=wasadmin -was.admin.password=passw0rd -doInstallFNCS=y -fncs.fp.installer.location=/opt/build/IBM_CONTENT_NAVIGATOR-2.0.3-LINUX.bin -doInstallCEClient=n
Note: The anonymous user won't be recognized if it was configured via the WebSphere® Application Server administrative console before CR1 was applied. In this case, you re-specify the anonymous user again after you upgrade to FNCS 2.0.3. Do so as described in Managing anonymous access for a FileNet® deployment, modifying the Applications > WebSphere Enterprise Applications > navigator application rather than the fncs application in those instructions. If you had configured the anonymous user during Connections Content Manager installation through Installation Manager instead of the administrative console, then the anonymous user will be recognized.
When updating an already installed Connections Content Manager, run the ccmUpdate.bat|sh command in the ccmDomainTool package to update the User Token Cache and Subject Cache values to 3600 as follows:
  1. Make sure the cluster and Connections Content Manager are running before running the ccmUpdate task.
  2. Run the command as follows:
    • For AIX/Linux:
      cd /opt/IBM/Connections/addons/ccm/ccmDomainTool/
 chmod +x ccmUpdate.sh
 ./ccmUpdate.sh
    • For Windows™:
      cd C:\Program Files\IBM\Connections\addons\ccm\ccmDomainTool/
 ccmUpdate.bat