IBM FileNet P8 Content Platform Engine 5.5.3.0-P8CPE-IF003 Interim Fix Readme
© Copyright IBM Corporation 2020.

Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.5.3.0-P8CPE
Fix ID: 5.5.3.0-P8CPE-IF003
Publication date: 14 July 2020
Last modified date: 14 July 2020

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
Client
Installing the client updates
Tools
Installing the tools Java updates
Installing the tools FileNet Deployment Manager 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.3, 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.3.0-P8CPE-IF003. You need an IBM login and password to access this download location.

Prerequisites

This interim fix requires:

New in Interim Fix 5.5.3.0-P8CPE-IF003

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

New in Interim Fix 5.5.3.0-P8CPE-IF002

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

New in Interim Fix 5.5.3.0-P8CPE-IF001

The following changes are introduced in this 5.5.3.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

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.3.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/listener.jar

    Windows

    installation_location\ContentEngine\lib\Engine-xx.ear
    installation_location\ContentEngine\lib\listener.jar

  3. Configuration Manager installation

    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/tools/configure/plugins/com.filenet.gcd_5.2.0.cm523/BootstrapConfig.jar
    installation_location/ContentEngine/tools/configure/scripts/deployWSApplication.tcl
    installation_location/ContentEngine/tools/configure/scripts/deployWSUpdate.tcl

    Windows

    installation_location\ContentEngine\tools\configure\plugins\com.filenet.gcd_5.2.0.cm523\BootstrapConfig.jar
    installation_location\ContentEngine\tools\configure\scripts\deployWSApplication.tcl
    installation_location\ContentEngine\tools\configure\scripts\deployWSUpdate.tcl


  4. 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.

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.3 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.3.0-P8CPE version or your upgrade from a pre-5.5.3 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.

Deploy Update

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

Important: Do NOT select "Deploy Update" for new installs or upgrades from a version previous to 5.5.3.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.3.0 Configuration Manager profile or create a new 5.5.3.0 Configuration Manager profile.
  2. If the ear folder is present in the Configuration Manager profile, make a backup of the files in the myprofile/ear folder. If the myprofile/ear folder does not exist, create one.
    Copy the ear that supports your application server type and version from the installation_location to the ear folder in the Configuration Manager profile.

    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. The installation_location is where you previously copied the new ear:

    UNIX:
    installation_location/ContentEngine/lib/Engine-xx.ear

    Windows:
    installation_location\ContentEngine\lib\Engine-xx.ear

    If your application server version is WebLogic 12.2 or higher, rename the file Engine-wl122.ear to Engine-wl.ear in the installation location
    Verify the permissions on the ear file allow the account running the Configuration Manager read/write access.
  3. Choose Add New Task > Deploy Update task.
  4. Provide the property values for your deployment. For details on the fields, hover your mouse over the "?" icon to view the property description.
  5. 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.

  6. 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.
  7. 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

Important: Do NOT use deployupdate for new installs or for upgrades from a version previous to 5.5.3.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. If the ear folder is present in the Configuration Manager profile, make a backup of the files in the myprofile/ear folder. If the myprofile/ear folder does not exist, create one.
    Copy the ear that supports your application server type and version from the installation_location to the ear folder in the Configuration Manager profile.

    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. The installation_location is where you previously copied the new ear:

    UNIX:
    installation_location/ContentEngine/lib/Engine-xx.ear

    Windows:
    installation_location\ContentEngine\lib\Engine-xx.ear

    If your application server version is WebLogic 12.2 or higher, rename the file Engine-wl122.ear to Engine-wl.ear in the installation location.
    Verify the permissions on the ear file allow the account running the Configuration Manager read/write access.
  4. Generate the deployupdate.xml task file for an existing CPE 5.5.3 configuration manager profile or as part of a new CPE 5.5.3 configuration manager profile using this command

    5. 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-dlownload.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 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.3.0-P8CPE-CLIENT-AIX.tar.gz
    Linux
    5.5.3.0-P8CPE-CLIENT-LINUX.tar.gz
    Windows
    5.5.3.0-P8CPE-CLIENT-WIN.zip
    zLinux
    5.5.3.0-P8CPE-CLIENT-ZLINUX.tar.gz
  3. Complete the following instructions as appropriate for the client installation:

    4. 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.

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

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

  5. 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.3.0-P8CPE-CLIENT-AIX.tar.gz
    Linux
    5.5.3.0-P8CPE-CLIENT-LINUX.tar.gz
    Windows
    5.5.3.0-P8CPE-CLIENT-WIN.zip
    zLinux
    5.5.3.0-P8CPE-CLIENT-ZLINUX.tar.gz
  5. 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.

  6. 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.3.0-P8CPE-CLIENT-AIX.BIN -i silent -f ceclient_silent_install.txt
    Linux
    5.5.3.0-P8CPE-CLIENT-LINUX.BIN -i silent -f ceclient_silent_install.txt
    Windows
    5.5.3.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.3.0-P8CPE-CLIENT-ZLINUX.BIN -i silent -f ceclient_silent_install.txt

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

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

  8. 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.5.40 July 2019.

  1. Exit all FileNet tools including FileNet Deployment Manager (FDM), Process Engine Process Designer (PD), Content Engine Bulk Importer (CEBI).
  2. Backup existing files as listed below.
    Then unzip the correct zip file for your operating system that was 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/_cejvm/jre

    Windows
    installation_location\ContentEngine\_cejvm\jre
    Example: C:\Program Files\IBM\FileNet\ContentEngine\_cejvm\jre

    Tools Java update files
    Operating system
    Java update file
    AIX
    ibm-java-jre-8.0-5.40-aix-pcc64.tar.gz
    Linux
    ibm-java-jre-8.0-5.40-linux-x86_64.tgz
    Windows
    ibm-java-jre-8.0-5.40-win-x86_64.zip
    zLinux
    ibm-java-jre-8.0-5.40-linux-s390x.tgz

Installing the tools FileNet Deployment Manager updates

This interim fix updates the FileNet Deployment Manager imex.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, 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
    installation_location/ContentEngine/tools/deploy/plugins/com.filenet.imex_5.5.3/imex.jar
    installation_location/ContentEngine/tools/deploy/plugins/com.filenet.deployment.common_6.0.0.jar
    installation_location/ContentEngine/tools/deploy/plugins/com.filenet.deployment.engine_6.0.0.jar
    installation_location/ContentEngine/tools/deploy/plugins/com.filenet.deployment.modules_6.0.0.jar
    installation_location/ContentEngine/tools/deploy/plugins/com.filenet.deployment.rcp_6.0.0.jar
    installation_location/ContentEngine/tools/deploy/plugins/com.filenet.pch_5.5.3/listener.jar

    Windows
    installation_location\ContentEngine\tools\deploy\plugins\com.filenet.imex_5.5.3\imex.jar
    installation_location\ContentEngine\tools\deploy\plugins\com.filenet.deployment.common_6.0.0.jar
    installation_location\ContentEngine\tools\deploy\plugins\com.filenet.deployment.engine_6.0.0.jar
    installation_location\ContentEngine\tools\deploy\plugins\com.filenet.deployment.modules_6.0.0.jar
    installation_location\ContentEngine\tools\deploy\plugins\com.filenet.deployment.rcp_6.0.0.jar
    installation_location\ContentEngine\tools\deploy\plugins\com.filenet.pch_5.5.3\listener.jar

  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


Fix list (APARs)

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

5.5.3.0-P8CPE-IF003 (Includes 5.5.3.0-P8CPE-IF001 and 5.5.3.0-P8CPE-IF002)
APAR
Description
PJ46044
Administration Console for Content Platform Engine (ACCE) Opening subclass Annotation does not display the annotation in a new tab.
PJ46049
External Share REST: Allow user to enable share even if we cannot resolve email template resource bundle for a locale.
PJ46050
PSIRT ADV0020631 (CVE-2019-4679): Administration Console for Content Platform Engine (ACCE) security vulnerability in logon response. See security bulletin 1283950.
PJ46053, PJ45998
On some CPE (Content Platform Engine) client applications intermittent FIPSRuntimeExceptions may occur.
PJ46054
FNRAM9018 Error returned when you try create a Case History store.
PJ46059
Administration Console for Content Platform Engine (ACCE) document properties page - right pane 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 (CE) Audit disposition has a check against the bookmark which has the reverse of the desired effect.
PJ46075
BACSoC NullPointer exception from Process Engine (PE) when any PE RPC's are performed.
PJ46086
"SymbolicName is a read-only property" error occurs on import with FileNet Deployment Manager (FDM).
PJ46120
Administration Console for Content Platform Engine (ACCE) set default class for new Object Store search.
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.
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.
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.
PJ46194
CONTENT_CA_SKIP_FAILED error occurs when retrieving files greater than 1 MB from an ICOS device using WSI.
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.
PJ46199
Administration Console for Content Platform Engine (ACCE) Property Template Misalignment of buttons/Filterbox/ObjectCount.
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 with out 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.
PJ46207
Opening Process Engine (PE) Process Designer (PD) from IBM Content Navigator (ICN) causes login prompt.
PJ46224
Administration Console for Content Platform Engine (ACCE) on WebSphere fails adding Property Template of type Object or integer into Document Class after upgrade.

5.5.3.0-P8CPE-IF002 (Includes 5.5.3.0-P8CPE-IF001)
APAR
Description
PJ44132
Content Search Services (CSS) indexed XLS Documents with numbers in German format containing a comma “,” are not searchable using comma but require using a dot ".". Fixed for AIX.
Oracle Outside In Technology patch - October 2019
PJ45822
Sensitive Information in Administration Console for Content Platform Engine (ACCE) URL Parameters.
PJ45873
Process Engine (PE) WSDL breaks down with 401 error (unauthorized).
PJ45887
Administration Console for Content Platform Engine (ACCE) localization issue in string and integer Choicelists.
PJ45888
Administration Console for Content Platform Engine (ACCE): Get error: 'theName is invalid' when importing an operation and changing the parameter name for a Component Queue.
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
PJ45929
PSIRT 17771 (CVE-2019-12402): Administration Console for Content Platform Engine (ACCE) Apache Commons Compress jar security vulnerability. See security bulletin 1077471
PJ45931
FileNet Deployment Manager (FDM) "Retrieve Data for Connection Point Half Map -> From Content Platform Engine" does not retrieve object store or isolated region values.
PJ45932
User information in IBM Content Navigator (ICN) Entry Template not updating when migrating with FileNet Deployment Manager (FDM).
PJ45945
java.lang.ClassNotFoundException occurs while trying to run "Configure the Case Management Object Store".
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.
PJ45969
Modifying a Fixed Content Storage created in pre-5.5.2 version will cause Null Point Exceptionn.
PJ45973
Process Engine (PE) AutomaticUpgrade fails when working with Database connection attribute with "/" in the display name.
PJ46028
Administration Console for Content Platform Engine (ACCE) using greater then ">" or less then "<" in a sweep job filter expression throws syntax error "Bad filter expression".
PJ46033
Snaplock Fixed Content Device (FCD) update retention failure for NFS mount.

5.5.3.0-P8CPE-IF001
APAR
Description
PJ44132
XLS files that use GERMAN FORMAT WITH COMMA ',' are not searchable using comma but require using dot '.'. Fixed for Windows, Linux, zLinux.
PJ44718
Enhancement: Add PDF Adobe Sign Content Search Services indexing (CSS) support with Oracle Outside In Technology (OIT).
PJ45757
Policy based sweep with multiple policies throws E_BAD_CLASSID exception.
PJ45767
Disabling an auditing policy does not halt the audit disposition deletion sweep from occurring.
PJ45790
Administrative Console for Content Platform Engine (ACCE) simple searches with date search condition throws a DB_ERROR with German MS SQL Server.
PJ45800
Administrative Console for Content Platform Engine (ACCE) cannot view update event on Role objectDefect Lists.
PJ45807
FileNet Deployment Manager - Reassign Object Store - Object Store selection control does not have a vertical scroll bar.
PJ45829
"E_BAD_CLASSID: Class "Obsolete class VSC" not found." occurs during upgrade causing issues with Process Engine (PE).
PJ45830
Opening attachments from a work object which was opened by Process Administrator from a User InBox fails with a malformed URL.
PJ45834
Isilon multi content elements document migration command retry is not handled correctly.
PJ45857
Administration Console for Content Platform Engine (ACCE) - Select from Search Result pane was checked even though users didn't do the selection.
PJ45868
PSIRT 17288: (CVE-2019-2769, CVEID: CVE-2019-2762): Java Technology Edition Critical Patch Update - July 2019. See security bulletin 0967409
PJ45873
WSDL breaks down with 401 error (unauthorized). See APAR PJ45873 for details
PJ45878
Remove default user data from Axis.
PJ45882
PSIRT 17737 (CVE-2019-4572): Security vulnerability in Process Orchestration Web Service logging. See security bulletin 1072042

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 July 2020
Initial interim fix release.