IBM FileNet P8 Content Platform Engine 5.5.4.0-P8CPE-IF007 Interim Fix Readme
© Copyright IBM Corporation 2021.

Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.5.4.0-P8CPE
Fix ID: 5.5.4.0-P8CPE-IF007
Publication date: 14 January 2022
Last modified date: 14 January 2022

Contents

About this interim fix
Download location
Prerequisites
New in this Interim Fix
Known problems, restrictions and solutions
Installation
Preparing the server for installation
Installing this Interim Fix
Server
Server Install
Configuration Manager Installation
Configuring the server after installation
Installing the Content Search Services (CSS) Microsoft Redistributable files
Client
Installing the client updates
Tools
Installing the tools Java updates
Installing the tools FileNet Deployment Manager updates
Installing the Process Designer and Process Engine Tools updates
Installing .Net API updates
Fix list (APARs)
Notices
Trademarks
Document change history

About this interim fix

This interim fix updates the Content Platform Engine, FileNet Deployment Manager, Process Designer, Content Engine Bulk Import (CEBI), and Content Platform Engine client files.

Important: If you are using this interim fix as a part of a new installation of the Content Platform Engine, install the interim fix files as directed here but stop before "Configuring the server after installation". Instead follow the instructions in the Knowledge Center topic "Installing and configuring Content Platform Engine" Installing Content Platform Engine to complete your new installation.

Important: If you are using this interim fix to upgrade from a release prior to 5.5.4, install the interim fix files as directed here but stop before "Configuring the server after installation". Instead continue with the upgrade process as described in the Knowledge Center topic "Upgrading and configuring Content Platform Engine" Upgrading Content Platform Engine.

Download location

Click the following link to access the files for this interim fix server update: Fix Central for Interim Fix 5.5.4.0-P8CPE-IF007. You need an IBM login and password to access this download location.

Prerequisites

This interim fix requires:

New in Interim Fix 5.5.4.0-P8CPE-IF007

The following changes are introduced in this 5.5.4.0-P8CPE-IF007 Interim Fix:

New in Interim Fix 5.5.4.0-P8CPE-IF006

The following changes are introduced in this 5.5.4.0-P8CPE-IF006 Interim Fix:

New in Interim Fix 5.5.4.0-P8CPE-IF005

The following changes are introduced in this 5.5.4.0-P8CPE-IF005 Interim Fix:

New in Interim Fix 5.5.4.0-P8CPE-IF004

The following changes are introduced in this 5.5.4.0-P8CPE-IF004 Interim Fix:

New in Interim Fix 5.5.4.0-P8CPE-IF003

The following changes are introduced in this 5.5.4.0-P8CPE-IF003 Interim Fix:

New in Interim Fix 5.5.4.0-P8CPE-IF002

The following changes are introduced in this 5.5.4.0-P8CPE-IF002 Interim Fix:

New in Interim Fix 5.5.4.0-P8CPE-IF001

The following changes are introduced in this 5.5.4.0-P8CPE-IF001 Interim Fix:


Known problems, restrictions and solutions

Following are some known problems and restrictions that are related to this interim fix:


Installation

Tip When copying files from Windows to Linux, make sure the copy program used does not modify CR/LF

Installation of this interim fix consists of the following tasks:

Preparing the server for installation

In environments where there is more than one Content Platform Engine server running in the P8 domain, the Content Platform Engine nodes can be set up in either a managed or non-managed configuration.

When you deploy Content Platform Engine in a "managed" application server environment, this Content Platform Engine interim fix is installed and configured on the administration server. The Configuration Manager uses the administration tools of the application server to deploy the Content Platform Engine EAR file to the managed servers. This is known as a "managed" deployment.

When you deploy Content Platform Engine in a "non-managed" application server environment, install and configure this Content Platform Engine interim fix on any Content Platform Engine server in the environment. After configuring the Content Platform Engine EAR file on this first server, you will be directed to copy the EAR file to each of the other servers and deploy the EAR file on all of the servers.

Complete the following tasks to prepare the Content Platform Engine server for this interim fix.

  1. Log on to the Content Platform Engine server as the user who is designated as the "cpe_install_user" user.
  2. Download this interim fix and extract its contents to a temporary location. For information, see Download location.
  3. Optionally stop the FileNetEngine and any client applications.

    As updating to this interim fix from an existing 5.5.4.0-P8CPE deployment is a minor version update, it is not required for the Content Platform Engine to be stopped prior to deploying the interim fix.


Installing this Interim Fix

Complete the following tasks to install this interim fix.

Important: The Content Platform Engine (CPE) EAR file naming convention is "Engine-xx.ear" where "xx" represents the Content Platform Engine application server type (ws, wl, wl122).
For WebLogic customers, the Engine-wl.ear is for users of WebLogic 12.1 and earlier while Engine-wl122.ear is for users of WebLogic 12.2 and later.

Server
  1. Navigate to the temporary directory where you extracted the contents of this interim fix.
  2. Server Install

    Backup existing files as listed below.
    Then copy the updated versions of the files that were extracted from the fix (see prior step) into the same directory as the existing copy that you just backed up. (This action overwrites the existing copy.)

    UNIX

    installation_location/ContentEngine/lib/Engine-xx.ear
    installation_location/ContentEngine/lib/Jace.jar
    installation_location/ContentEngine/lib/pe.jar

    Windows

    installation_location\ContentEngine\lib\Engine-xx.ear
    installation_location\ContentEngine\lib\Jace.jar
    installation_location\ContentEngine\lib\pe.jar

  3. Configuration Manager cleanup

Configuring the server after installation

Complete the tasks in this section to configure the server set-up information and to deploy Content Platform Engine. Following are an overview of the steps.

Important: If you are using this interim fix as a part of a new installation of the Content Platform Engine or upgrade from a pre-5.5.4 version of the Content Platform Engine, stop here. Return to the instructions in the Knowledge Center topic to complete the process for your new installation of a 5.5.4.0-P8CPE version or your upgrade from a pre-5.5.4 CPE version.


Gathering Content Platform Engine information

Before you can deploy Content Platform Engine, you must gather information that is needed for the application server configuration profile and for startup and deployment of the Content Platform Engine EAR file.

Use the Installation and Upgrade Planning Worksheet to help identify all the required information about your Content Platform Engine installation. Refer to the following link for more details:
See Knowledge Center Using the installation and upgrade worksheet.

Completing Configuration Manager tasks

Complete the tasks in this section to configure the server set-up information and to deploy Content Platform Engine.

Completing Configuration Manager update tasks interactively

Completing Configuration Manager tasks Command-line: Add and execute deployupdate


Completing Configuration Manager tasks interactively


Starting the Configuration Manager

  1. Log on to the Content Platform Engine server as the "config_mgr_user" user.
  2. Start Configuration Manager by completing the procedure that is appropriate for the operating system.

    UNIX

    Run the following command from the command line: ce_install_path/tools/configure/configmgr.

    Windows

    Select Start > All Programs > IBM FileNet P8 Platform > FileNet Configuration Manager or run the following command: ce_install_path\tools\configure\configmgr.exe.


Installing the Content Search Services (CSS) Microsoft 2019 Redistributable files

Only on Windows systems where Content Search Services (CSS) indexing and searching or Thumbnails are configured for Oracle Outside In Technology (OIT) v8.5.5 and higher.

Note: If the Microsoft 2019 Redistributable files are currently installed, you do not need to re-install them.

    Windows

  1. Open Windows Control Panel > Programs and look for Microsoft Visual C++ 2015-2019 Redistributable (x64)", and if present, no need to re-install.
  2. Download Microsoft Visual C++ Redistributable 2019 Package for Visual Studio 2019 package vcredist_x64.exe
  3. Install following Microsoft installation instructions.

Deploy Update

To redeploy/update an existing 5.5.4.0-P8CPE FileNetEngine application, add and run the "Deploy Update" task.

Note: If you elected to "Remove the deployed FileNetEngine application" when preparing for the update, you will need to use "Deploy Application" instead of "Deploy Update".

Important: Do NOT select "Deploy Update" for new installs or upgrades from a version previous to 5.5.4.0-P8CPE.

See Knowledge Center topic Planning and preparing for FileNet P8 updates for deploy update WebSphere Application Edition Management (AEM) details.

  1. Open the existing 5.5.4.0 Configuration Manager profile or create a new 5.5.4.0 Configuration Manager profile.
  2. Choose Add New Task > Deploy Update task.
  3. Provide the property values for your deployment. For details on the fields, hover your mouse over the "?" icon to view the property description.
  4. Save your changes then select Run Task.

    Running the deploy task might take several minutes. The task status messages are displayed in the Console pane below the deploy application properties.

  5. If the FileNetEngine application server was shutdown, or the application server does not restart it in a timely fashion, manually restart the FileNetEngine application after confirming the new files were distributed by the application server to all nodes or managed servers.
  6. Open the Content Engine (CE) ping page (http://server:port/FileNet/Engine) and verify that the value in the Startup Message key for Content Platform Engine is the same as the Content Platform Engine build number from the version.txt file, which is located in the temporary directory where you extracted the contents of this interim fix.

Update of the FileNetEngine application is now complete. Continue with the next section, Installing the client updates.


Completing Configuration Manager Tasks Command-line

Add and execute deployupdate

Complete the following procedure to specify setup information and deploy an update to an existing Content Platform Engine

Note: If you elected to "Remove the deployed FileNetEngine application" when preparing for the update, you will need to use "Deploy Application" instead of "Deploy Update". Which for the command line utility means specifying "-task deployapplication" instead of "-task deployupdate" in the steps below.

Important: Do NOT use deployupdate for new installs or for upgrades from a version previous to 5.5.4.0-P8CPE.

  1. Log on to the Content Platform Engine server as the user who is designated as the config_mgr_user user
  2. Change the current directory to ce_install_path/tools/configure, where ce_install_path is the path where you installed Content Platform Engine. For example, ce_install_path might be /opt/FileNet/ContentEngine
  3. Generate the deployupdate.xml task file for an existing CPE 5.5.4 configuration manager profile or as part of a new CPE 5.5.4 configuration manager profile using this command
  4. configmgr_cl generateconfig -appserver WebSphere/WebLogic -deploy standard/cluster/netdeploy -task deployupdate -profile myprofile

  5. Supply the needed values in the deployupdate.xml task file. If this is a new configuration manager profile, also complete the applicationserver.xml file.
  6. Use the command-line to execute the deployupdate task. Enter the command on one line without line breaks

    configmgr_cl execute -task deployupdate -taskfile deployupdate.xml -profile myprofile

  7. If the application server was shutdown, or the application server does not restart in a timely fashion, manually restart the FileNetEngine application after confirming the new files were distributed by the application server to all nodes or managed servers.
  8. Open the Content Engine (CE) ping page (http://server:port/FileNet/Engine) and verify that the value in the Startup Message key for Content Platform Engine is the same as the Content Platform Engine build number from the version.txt file, which is located in the temporary directory where you extracted the contents of this interim fix.

Completing Configuration Manager tasks

In a non-managed application server environment, repeat the EAR deployment for all servers.


Client Installation

Installing the client download updates

This interim fix updates the Client Download client-download.jar file.

Note: If Client downloader is not installed, this step can be skipped.

  1. Navigate to the temporary directory where you extracted the content of this interim fix.
  2. Client Application Install

Installing the client updates

The following Content Platform Engine client API files are included in this interim fix. These files must be installed as needed on the Content Platform Engine clients and customized application installation locations.

Complete the following procedure to update Content Platform Engine with the updated JAR files.

  1. Backup existing files as listed below.
    Then copy the updated versions of the files that were extracted from the fix (see prior step) into the same directory as the existing copy that you just backed up. (This action overwrites the existing copy.)
    The below client files are located in the interim fix cpetools\peclient directory.

    UNIX
    installation_location/ContentEngine/lib/Jace.jar (copy from zip root directory)
    installation_location/ContentEngine/lib/pe.jar (copy from zip root directory)
    installation_location/ContentEngine/lib/petools.jar

    Windows
    installation_location\ContentEngine\lib\Jace.jar
    installation_location\ContentEngine\lib\pe.jar
    installation_location\ContentEngine\lib\petools.jar

  2. On some systems (for example, systems using custom applications), the Jace.jar, Jace_t.jar, pe.jar files might also exist in other directories or be otherwise bundled with the custom application (for example, with the J2EE WAR or EAR file). If you have any custom applications, search for the files and replace other instances with the new version supplied in this interim fix.

Note: You use the Content Platform Engine client installer to install the new jars that will come from the updated Content Platform Engine server via the download service. It's important that the Content Platform Engine server be already updated by this interim fix and be running prior to running the client installer. By following the client installation instructions below, the updated files will be installed on all clients that are supported by the client installer. The files are also provided separately for clients not supported by the client installer.

You can install the client update either interactively or silently. This section consists of the following steps:


Installing the Content Platform Engine client update on Content Platform Engine-related Java EE applications interactively

After you have updated the Content Platform Engine servers complete the following tasks for all of the Content Platform Engine-related Java EE applications, and any custom Content Platform Engine-related Java EE applications.

  1. Back up the existing Content Platform Engine client directories.
  2. Download the appropriate client update file from the latest generally available release and extract its contents to a temporary location.
  3. The following table lists the names of the compressed fix client update files by operating system type:

    Name of compressed Content Platform Engine client update file by operating system type
    Operating system type
    Name of compressed Content Platform Engine client update file
    AIX
    5.5.4.0-P8CPE-CLIENT-AIX.tar.gz
    Linux
    5.5.4.0-P8CPE-CLIENT-LINUX.tar.gz
    Windows
    5.5.4.0-P8CPE-CLIENT-WIN.zip
    zLinux
    5.5.4.0-P8CPE-CLIENT-ZLINUX.tar.gz
  4. Complete the following instructions as appropriate for the client installation:
  5. Tip If the client installation program is unable to detect the existing installation of the FileNet P8 application you are updating, you must manually ensure that the update occurs. Check the item in the "Select FileNet P8 Applications" dialog box and complete the client installation by entering (or browsing to) the location where that application is installed.

  6. Review the Content Platform Engine client log files for installation errors.

    Installation errors are recorded in the ceclient_install_log_5.5.4.0.txt file, which is in the ceclient_install_path directory.

  7. Restart the applications that use the Content Platform Engine client.

The installation and configuration of the client upgrade for this interim fix is complete.


Installing the Content Platform Engine client updates silently

Complete the following procedure to install the Content Platform Engine client updates silently.

  1. Log on as a user with permissions to install software.
  2. Stop all custom applications that use the Content Platform Engine client.
  3. Back up the existing Content Platform Engine client directories.
  4. Download the appropriate client update file from the latest generally available fix pack and extract its contents to a temporary location.
  5. The following table lists the names of the compressed fix client update files by operating system type:

    Name of compressed Content Platform Engine client update file by operating system type
    Operating system type
    Name of compressed Content Platform Engine client update file
    AIX
    5.5.4.0-P8CPE-CLIENT-AIX.tar.gz
    Linux
    5.5.4.0-P8CPE-CLIENT-LINUX.tar.gz
    Windows
    5.5.4.0-P8CPE-CLIENT-WIN.zip
    zLinux
    5.5.4.0-P8CPE-CLIENT-ZLINUX.tar.gz
  6. Open the ceclient_silent_install.txt file and edit the file as appropriate for your configuration, including the following fields and other fields that apply to your system.
  7. Install this fix by running the following command that is appropriate for your operating system.

    Silent installation start commands by operating system for the Content Platform Engine client update
    Operating system
    Command to install the Content Platform Engine server update
    AIX
    5.5.4.0-P8CPE-CLIENT-AIX.BIN -i silent -f ceclient_silent_install.txt
    Linux
    5.5.4.0-P8CPE-CLIENT-LINUX.BIN -i silent -f ceclient_silent_install.txt
    Windows
    5.5.4.0-P8CPE-CLIENT-WIN.EXE -i silent -f ceclient_silent_install.txt
    TIP You can monitor completion of this interim fix server update installation on Windows-based systems by using the Windows Task Manager.
    zLinux
    5.5.4.0-P8CPE-CLIENT-ZLINUX.BIN -i silent -f ceclient_silent_install.txt

  8. Review the Content Platform Engine client log files for installation errors.

    Installation errors are recorded in the ceclient_install_log_5.5.4.0.txt file, which is in the ceclient_install_path directory.

  9. Restart the custom applications that use the Content Platform Engine client.

The installation and configuration of the client upgrade for this interim fix is complete.


Tools Installation

Installing the tools Java updates

This interim fix updates the tools private Java files.

Complete the following procedure to update tools IBM Java to v8.0.6.26 March 2021.

  1. Exit all FileNet tools including FileNet Deployment Manager (FDM), Process Engine Process Designer (PD), Content Engine Bulk Importer (CEBI).
  2. If the JRE version is older (lower number) than IBM Java JRE 8.0 SR6 FP26, then continue on to the next step. If Java 8.0 SR6 FP26 is already installed, then no further action is required, since 8.0 SR6 FP26 should only be installed once.

  3. Rename current Java cpe_installation_location/FileNet/ContentEngine/_cejvm directory to Javaxxx as a backup, where xxx is the old Java version.
  4. Create a new, empty cpe_installation_location/FileNet/ContentEngine/_cejvm Java directory.
  5. Extract the contents of ibm-java-jre-platform.zip (.tgz, .tar.gz) into temporary directory
  6. Move from temporary location the jre directory contents to the _cejvm directory
  7. Move from temporary location the copyright, license, notices, readme files to the _cejvm directory
  8. Verify that cpe_installation_location/FileNet/ContentEngine/_cejvm directory contains both lib & bin directories, and plugin for AIX & Linux.
  9. Verify that the new Java Runtime Environment is Java 8.0 SR6 FP26 :

    $ java -version


Installing the tools FileNet Deployment Manager updates

This interim fix updates the FileNet Deployment Manager imex.jar, Jace.jar, pe.jar, com.filenet.deployment.common_6.0.0.jar, com.filenet.deployment.engine_6.0.0.jar, com.filenet.deployment.modules_6.0.0.jar, com.filenet.deployment.rcp_6.0.0.jar and listener.jar files.

Complete the following procedure to update Deployment Manager.

  1. After downloading the fix and extracting its contents to a temporary location (in step 2 under Preparing the server for installation ), the updated imex.jar, Jace.jar, pe.jar, com.filenet.deployment.common_6.0.0.jar, com.filenet.deployment.engine_6.0.0.jar, com.filenet.deployment.modules_6.0.0.jar, com.filenet.deployment.rcp_6.0.0.jar, and listener.jar files should be in the temporary location.
  2. Backup existing files as listed below.
    Then copy the updated versions of the files that were extracted from the fix (see prior step) into the same directory as the existing copy that you just backed up. (This action overwrites the existing copy.)

    Linux
    Copy the fdm-linux.zip extracted files in the deploy directory to installation_location/deploy/

    Windows
    Copy the fdm-linux.zip extracted files in the deploy directory to installation_location\deploy\

  3. If you have previously executed Deployment Manager from this installation directory, the old files have been cached. To remove the old cache from your system, go to:

    Linux

    installation_location/ContentEngine/tools/deploy

    Run the following command: DeploymentManager -clean

    Windows

    installation_location\ContentEngine\tools\deploy

    Run the following command: DeploymentManager.exe -clean


Installing the Process Designer and Process Engine Tools updates

This interim fix updates the Process Designer and Process Engine Tools Jace.jar, pe.jar, and petools.jar files.

Complete the following procedure to update Process Designer and Process Engine Tools.

  1. After downloading the fix and extracting its contents to a temporary location (in step 2 under Preparing the server for installation ), the updated Jace.jar, pe.jar, and petools.jar files should be in the temporary location.
  2. Backup existing files as listed below.
    Then copy the updated versions of the files that were extracted from the fix (see prior step) into the same directory as the existing copy that you just backed up. (This action overwrites the existing copy.)

    Linux
    installation_location/ContentEngine/lib/Jace.jar
    installation_location/ContentEngine/lib/pe.jar
    installation_location/ContentEngine/lib/petools.jar
    installation_location/ContentEngine/lib/applets.jar

    Windows
    installation_location\ContentEngine\lib\Jace.jar
    installation_location\ContentEngine\lib\pe.jar
    installation_location\ContentEngine\lib\petools.jar
    installation_location\ContentEngine\lib\applets.jar


Installing .Net API updates

This interim fix updates the .Net API FileNet.Api.dll and FileNetApiSetup.msi files.

Complete the following procedure to update .Net API client installed on a Windows machine.

  1. Log on as a user with permissions to install software.
  2. After downloading the fix and extracting its contents to a temporary location (in step 2 under Preparing the server for installation ), the updated FileNetApiSetup.msi file should be in the temporary location.
  3. Launch FileNetApiSetup.msi and complete the IBM FileNet Content Engine .NET API Setup Wizard.

Fix list (APARs)

The following table lists the product fixes for this interim fix.

5.5.4.0-P8CPE-IF007 (includes 5.5.4.0-P8CPE-IF001, 5.5.4.0-P8CPE-IF002, 5.5.4.0-P8CPE-IF003, 5.5.4.0-P8CPE-IF004, 5.5.4.0-P8CPE-IF005, and 5.5.4.0-P8CPE-IF006)
APAR
Description
PJ46021
Oracle OIT PDF files create invalid thumbnail image text. Fixed in Oracle OIT v8.5.5 BP#6 p33394086 (October 2021) to fix hang.
PJ46615
Killing hung Thumbnail generation process should cleanup journal directory. New Oracle OIT v8.5.5 BP#6 p33394086 (October 2021) to fix hang.
PJ46633
Administration Console for Content Platform Engine (ACCE) shows the object as '{0}', instead of displaying the objects symbolic name when trying to save an object with insufficient access.
PJ46637
OIT v8.5.5 Microsoft Project (.mpp) files error "EXRunExport() failed: file is corrupt (0x0009)". OIT regression fixed in Oracle OIT v8.5.5 BP#6 p33394086 (October 2021).
PJ46639
PSIRT ADV0026757 (CVE-2020-4759): Administration Console for Content Platform Engine (ACCE) CSV injection security vulnerability in export Search Results. See security bulletin 6336917.
PJ46641
FileNet Deployment Manager (FDM) does not update modified symbolic name on document classes.
PJ46646
PSIRT ADV0036652 (CVE-2021-23926): Apache XMLBeans XML Entity Expansion security vulnerability. See security bulletin 6497193.
PJ46649
Administration Console for Content Platform Engine (ACCE) displays component operation parameters in alphabetic order.
PJ46654
PSIRT ADV0038035 (CVE-2021-38965): FileNet Content Manager component Administration Console for Content Platform Engine (ACCE) user Operating System command injection security vulnerability. See security bulletin 6509840.
PJ46656
Staging Area files are not deleted after finalization to the Fixed Content Device when "AllowDelete" is unchecked.
PJ46671
S3 ASA upload failure for storageGrid when the file size is the exact multiple of upload part size.
PJ46677
Content Platform Engine (CPE) S3 Storage URL Encoding implementation not fully compatible with Amazon Web Services (AWS) specs.
PJ46692
Administration Console for Content Platform Engine (ACCE) display error in the Audit Definitions configuration.

characters.
5.5.4.0-P8CPE-IF006 (includes 5.5.4.0-P8CPE-IF001, 5.5.4.0-P8CPE-IF002, 5.5.4.0-P8CPE-IF003, 5.5.4.0-P8CPE-IF004, and 5.5.4.0-P8CPE-IF005)
APAR
Description
PJ46304
Unsupported EPS files fail to extract thumbnail images now return an unsupported format error.
PJ46407
Some Customer PDF files generate thumbnail images that are either blank or contain garbage.
PJ46463
PSIRT ADV0030051 (CVE-2021-20448): Administration Console for Content Platform Engine (ACCE) Cross Site Scripting (XSS) security vulnerability when Content Platform Engine (CPE) server responds. See security bulletin 6438907.
PJ46564
Administration Console for Content Platform Engine (ACCE) Cannot create a custom sweep policy using the 'Queue Item' class from the Target Class drop down.
PJ46568
PSIRT ADV0032964 (CVE-2021-31811, CVE-2021-31812): Apache PDFBox security vulnerability. See security bulletin 6467839.
PJ46569
Administration Console for Content Platform Engine (ACCE) Bulk Action Dependent permissions check-boxes are only visually checked when switching between user groups.
PJ46570
Administration Console for Content Platform Engine (ACCE) Default value for Sting property is set to empty string instead of NULL.
PJ46578
Administration Console for Content Platform Engine (ACCE) Updating string property values to blank, or updates to other property values, stores value in DB as blank instead of NULL.
PJ46579
Administration Console for Content Platform Engine (ACCE) Issue in 'get object event' audit entries for case folder object.
PJ46587
Administration Console for Content Platform Engine (ACCE): Unable to download Files with filename having comma only on Chrome browser.
PJ46591
Content Engine (CE) server cmcl-p8-*.jar file handle leak in /tmp folder.
PJ46600
The Consistency Check sweep database (DB) query returns more property values than necessary (performance).
PJ46604
Enhancement: Administration Console for Content Platform Engine (ACCE) not able to apply Security Templates in Documents.
PJ46613
Content Engine (CE) FNRCS0001E: SECURITY_ANONYMOUS_DISALLOWED repeatedly in logs when Component Manager attempting to load the code module.
PJ46615
Killing hung Thumbnail generation process should cleanup journal directory.
PJ46620
Enhancement: FileNet Deployment Manager (FDM) does not update annotations.
PJ46624
Some Customer PDF files generate thumbnail images that are either incomplete or contain garbage characters. Fixed in Oracle OIT v8.5.5 BP#5 p33024357 (July 2021).

5.5.4.0-P8CPE-IF005 (includes 5.5.4.0-P8CPE-IF001, 5.5.4.0-P8CPE-IF002, 5.5.4.0-P8CPE-IF003, and 5.5.4.0-P8CPE-IF004)
APAR
Description
PJ46188
Content Search Services (CSS) Indexing/Search PDF document issues due to added spaces during text extraction.
PJ46395
Administration Console for Content Platform Engine (ACCE) does not allow a domain administrator to delete a read-only object store.
PJ46409
FileNet Deployment Manager (FDM) fails to reassign object store with error FNRCE0058E: E_REQUIRED_VALUE_ABSENT.
PJ46414
Administration Console for Content Platform Engine (ACCE) Custom Property "RetentionPeriod" showing unexpected behavior.
PJ46427
Enhancement: Content Engine (CE) .NET API must support mutual authentication.
PJ46444
Administration Console for Content Platform Engine (ACCE) Search results save as functionally does not work with all browsers.
PJ46463
PSIRT ADV0030051 (CVE-2021-20448): Administration Console for Content Platform Engine (ACCE) Cross Site Scripting (XSS) security vulnerability. See security bulletin 6438907.
PJ46468
Content Engine (CE) client API TRANSPORT_WSI_DESERIALIZATION_ERROR occurs in custom bulk import utility.
PJ46483
Administration Console for Content Platform Engine (ACCE) Localization issue with float property thousand separator when operating system language is not English.
PJ46485
Content Search Services (CSS) Linux x86 Oracle Outside In Technology (OIT) Open SSL dependency starting with the January 2021 OIT Search/Image Export patch. See technote 6439533
PJ46490
Intermittently Content Search Services (CSS) is failing to index documents with large number of content elements.
PJ46491
Content Engine Bulk Importer (CEBI) does not validate date values.
PJ46492
Content Search Services (CSS) Content Based Retrieval (CBR) search "divide by zero" error and failure to truncate Oracle CBR temp table.
PJ46503
Process Engine (PE) TCP connection is reset for each RPC calls with SSL. The connection expected to be reused instead.
PJ46505
Content Platform Engine (CPE) REST API: Create object store sets compression on for database tables and index even if the underlying database server does not support compression, causing object store creation failure.
PJ46522
Web Service GetContent by path call throws E_UNEXPECTED_EXCEPTION error.
PJ46527
Administration Console for Content Platform Engine (ACCE) Search results export to file and multiple values in property.

5.5.4.0-P8CPE-IF004 (includes 5.5.4.0-P8CPE-IF001, 5.5.4.0-P8CPE-IF002, and 5.5.4.0-P8CPE-IF003)
APAR
Description
PJ46298
Three PDF files create invalid thumbnail images - text displayed in the image is invalid.
PJ46320
Administration Console for Content Platform Engine (ACCE) folders not showing the 'Containment Name' value in the 'Containment Name' column.
PJ46324
Content Search Services (CSS) Content Base Retrieval (CBR) and Thumbnail generation: Some PDF documents have some areas inside that are missed by CBR extraction and Thumbnail generation.
PJ46336
Enhancement: Allow sensitive information to (optionally) be removed from Content Platform Engine (CPE) ping page.
PJ46337
Content Search Services (CSS) text extraction failed against Lotus 123 document with Oracle Outside In Technology (OIT) v8.5.5.
PJ46338
S3 Advanced Storage Device authentication issue for some S3 vendors when JDK is not in an English Locale.
PJ46351
Inefficient logic for looking up a GCD object by name.
PJ46359
Administration Console for Content Platform Engine (ACCE) use of Marking Sets and Security Proxies prevent DISTINCT queries from working.
PJ46370
Administration Console for Content Platform Engine (ACCE) issue with user created Component Queues.
PJ46392
Administration Console for Content Platform Engine (ACCE) replaces white space with plus sign "+" when downloading content with accents.
PJ46396
FileNet Deployment Manager (FDM): Object Store reassign fails when reassigning a CPE 5.2.0 Object Store with an isolated region to a CPE 5.5.x p8 domain.
PJ46397
Administration Console for Content Platform Engine (ACCE) unable to edit security template.
PJ46398
Administration Console for Content Platform Engine (ACCE) Object store search returns bad class id when class set to Documents and its Subclasses.
PJ46399
Administration Console for Content Platform Engine (ACCE) issue with Saving Searches with Date/Time included in Search fields.

5.5.4.0-P8CPE-IF003 (includes 5.5.4.0-P8CPE-IF001, and 5.5.4.0-P8CPE-IF002)
APAR
Description
PJ46171
Loading of Case Analyzer process task manager user interface is slow with lots of user defined fields.
PJ46215
PSIRT ADV0026757 (CVE-2020-4759): Administration Console for Content Platform Engine (ACCE) result in csv is incorrectly separated after importing to Excel. See security bulletin 6336917.
PJ46246
Content Engine (CE) Thumbnail ibmfnthb processes can be orphaned (not terminated) during CPE shutdown.
PJ46249
Administration Console for Content Platform Engine (ACCE) Document name with Chinese/Arabic characters gets corrupted when download document name.
PJ46297
FileNet Deployment Manager (FDM): E_ACCESS_DENIED error occurs when trying to import a document with the "Sharing Controller" property.
PJ46302
Administration Console for Content Platform Engine (ACCE) search results issue when clicking column header to sort.

5.5.4.0-P8CPE-IF002 (includes 5.5.4.0-P8CPE-IF001)
APAR
Description
PJ46086
"SymbolicName is a read-only property" error occurs on import with FileNet Deployment Manager (FDM).
PJ46120
Administration Console for Content Platform Engine (ACCE) object store search now sets "Document" as the default class for new searches.
PJ46127
Administration Console for Content Platform Engine (ACCE) error message when trying to import component operations.
PJ46130
NullPointerException occurs when trying to Generate an Audit report with FileNet Deployment Manager (FDM).
PJ46132
Problem with Content Search Services (CSS) Content Based Retrieval (CBR) indexing dispatcher stats logging and locale (German) decimal parsing.
PJ46138
Administration Console for Content Platform Engine (ACCE) annoyance check-in external URL.
PJ46144
PSIRT Advisory ADV0023337 (CVE-2020-4447): Administration Console for Content Platform Engine (ACCE) Cross-site scripting security vulnerabilities. See security bulletin 6208453.
PJ46153
Apache Commons FileUpload Resource Leak WS-2014-0034.
PJ46165
Centera FCP FPPool close causes crash in customer environment.
PJ46166
Administration Console for Content Platform Engine (ACCE) FileNet Rounding float decimals.
PJ46176
Administration Console for Content Platform Engine (ACCE) shows wrong queue sweep items.
PJ46178
User unable to log into Process Engine (PE) vwtool where a Principal anonymous error is returned.
PJ46179
Localization of Property templates in Administration Console for Content Platform Engine (ACCE) not loading.
PJ46194
CONTENT_CA_SKIP_FAILED error occurs when retrieving files greater than 1 MB from an ICOS device using WSI.
PJ46200
Administration Console for Content Platform Engine (ACCE) Not able to create Master domain with option CPEDomainType.
PJ46201
Administration Console for Content Platform Engine (ACCE) enhancement to improve display of choice items for choice lists.
PJ46202
Administration Console for Content Platform Engine (ACCE) Choice list Audit history without editing items, showing in update event Properties.
PJ46203
WebSphere LTPA SSO fails from traditional WebSphere Application Server (tWAS) Content Platform Engine (CPE) client to CPE server on Liberty.
PJ46206
A file handle and memory leak occurs when using Process Engine (PE) custom component queues in Apache Axix2.
PJ46211
Administration Console for Content Platform Engine (ACCE) Legacy Workflow System's Adapter's Configure User Interface (UI) displays incorrect Object Store potentially.
PJ46219
S3 Storage Configuration parameters are defined as static, might cause issues in certain situation.
PJ46224
Administration Console for Content Platform Engine (ACCE) on WebSphere fails adding Property Template of type Object or integer into Document Class after upgrade. See technote 6250299.
PJ46232
Process Engine (PE) Web Services (PEWS) Client Authentication Issue when using BINARYSECURITYTOKEN instead of username - method does not exist wsiAuthenticator error.

5.5.4.0-P8CPE-IF001
APAR
Description
PJ45887
Administration Console for Content Platform Engine (ACCE) localization issue in string and integer Choicelists.
PJ45908
PISRT ADV0018019 (CVE-2019-4642), ADV0020486 (CVE-2019-4646, CVE-2019-4652, CVE-2019-4643, CVE-2019-4645, CVE-2019-4650, CVE-2019-4656, CVE-2019-4651, CVE-2019-4659, CVE-2019-4644, CVE-2019-4655, CVE-2019-4657, CVE-2019-4641, CVE-2019-4654), ADV0020487 (CVE-2019-4661), ADV0020488 (CVE-2019-4662): IBM FileNet Content Manager has multiple security vulnerabilities in Administration Console for Content Platform Engine (ACCE). See security bulletin 1073876
PJ45961
Administration Console for Content Platform Engine (ACCE): Content Platform Engine(CPE) Security Policy does not save configuration of Security Template when using Roles.
PJ45964
Administration Console for Content Platform Engine (ACCE) Choice lists have a null value added.
PJ45992
NullPointerException occurs if a property with null value is included in an arithmetic clause in a filter expression.
PJ46004
Apostrophe in the Process Engine (PE) in-basket filter search causes a syntax failure when configured for case insensitive Search.
PJ46028
Administration Console for Content Platform Engine (ACCE) using greater than ">" or less than "<" in a sweep job filter expression throws syntax error "Bad filter expression".
PJ46033
Snaplock Fixed Content Device (FCD) update retention failure for NFS mount.
PJ46034
Stand-alone Process designer error "java.lang.ClassNotFoundException: com.filenet.wcm.toolkit.client.ui.WcmDlgFactory". See technote 1171240.
PJ46044
Administration Console for Content Platform Engine (ACCE) Opening subclass Annotation doesn't display the annotation in a new tab.
PJ46049
External Share REST API: Allow user to enable share even if we cannot resolve email template resource bundle for a locale.
PJ46050
PISRT ADV0020631 (CVE-2019-4679): IBM FileNet Content Manager security vulnerabilities in Administration Console for Content Platform Engine (ACCE) logon response header. See security bulletin 6251987.
PJ46053, PJ45998
On some Content Platform Engine (CPE) client applications intermittent FIPSRuntimeExceptions may occur.
PJ46054
FNRAM9018 exception returned creating Case History store after upgrading.
PJ46059
On Administration Console for Content Platform Engine (ACCE) document properties page, the right panel is transparent.
PJ46061
Administration Console for Content Platform Engine (ACCE) FNRAC1005E error occurs when trying to add Choice Item to a Choice List with 951 choice items.
PJ46069
Case History - Handle update events on case comments.
PJ46070
Content Engine Audit disposition code has a check against the bookmark which is inverted.
PJ46075
BACSoC NullPointerException from PE when any Process Engine (PE) RPC's are performed after 72 hours from initial logon.
PJ46196
Administration Console for Content Platform Engine (ACCE) Security Policy does not save configuration of Security Template when using Delegate users.
PJ46198
Administration Console for Content Platform Engine (ACCE) Choice List Localization of Choice Items after group in a Choice List showing items of group in localization dialog and Editing of Display Name not working.
PJ46648
PSIRT ADV0036738 (CVE-2021-35516, CVE-2021-35517, CVE-2021-35515, CVE-2021-36090): IBM FileNet Content Manager security vulnerabilities in Administration Console for Content Platform Engine (ACCE) with Apache commons-compress. See security bulletin 6498123.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
J74/G4
555 Bailey Avenue
San Jose, CA 95141
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.

Document change history


Date
Description
14 January 2022
Initial interim fix release.