Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.5.5.0-P8CPE
Fix ID: 5.5.5.0-P8CPE-IF003
Publication date: 5 February 2021
Last modified date: 26 February 2021
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.5, 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.
Click the following link to access the files for this interim fix server update: Fix Central for Interim Fix 5.5.5.0-P8CPE-IF003. You need an IBM login and password to access this download location.
This interim fix requires:
The following changes are introduced in this 5.5.5.0-P8CPE-IF003 Interim Fix:
The following changes are introduced in this 5.5.5.0-P8CPE-IF002 Interim Fix:
Following are some known problems and restrictions that are related to this interim fix:
Installation of this interim fix consists of the following tasks:
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.
As updating to this interim fix from an existing 5.5.5.0-P8CPE deployment is a minor version update, if this is a managed deployment, it is not required for the Content Platform Engine to be stopped prior to deploying the interim fix.
If the deployment is in a "non-managed" application server environment, the recommendation is to first remove the FileNetEngine application from the application server instances and clear any application server caches.
Removing the existing version ensures a clean deployment of the upgraded version of the Content Platform Engine EAR file. This includes the scenario where a single instance of WebSphere Application Server (standard) or WebLogic are running as an all-in-one deployment with their administration console and application server hosted by a single JVM instance.
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, wl122).
For WebLogic customers, Engine-wl122.ear is for users of WebLogic 12.2 and later.
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/petools.jar
Windows
installation_location\ContentEngine\lib\Engine-xx.ear
installation_location\ContentEngine\lib\Jace.jar
installation_location\ContentEngine\lib\petools.jar
UNIX
user_home_directory/configmgr_workspaceWindows
user_home_directory\configmgr_workspaceUNIX
user_home_directory/configmgr_workspace_5.5.5Windows
user_home_directory\configmgr_workspace_5.5.5Complete 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.5 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.5.0-P8CPE version or your upgrade from a pre-5.5.5 CPE version.
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.
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
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.
To redeploy/update an existing 5.5.5.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.5.0-P8CPE.
See Knowledge Center topic Planning and preparing for FileNet P8 updates for deploy update WebSphere Application Edition Management (AEM) details.
Running the deploy task might take several minutes. The task status messages are displayed in the Console pane below the deploy application properties.
Update of the FileNetEngine application is now complete. Continue with the next section, Installing the client updates.
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.5.0-P8CPE.
configmgr_cl generateconfig -appserver WebSphere/WebLogic -deploy standard/cluster/netdeploy -task deployupdate -profile myprofile
configmgr_cl execute -task deployupdate -taskfile deployupdate.xml -profile myprofile
In a non-managed application server environment, repeat the EAR deployment for all servers.
This interim fix updates the Client Download client-download.jar file.
Note: If Client downloader is not installed, this step can be skipped.
Example: installation_location/CEClient/lib
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.
UNIX
installation_location/ContentEngine/lib/Jace.jar
installation_location/ContentEngine/lib/petools.jar
Windows
installation_location\ContentEngine\lib\Jace.jar
installation_location\ContentEngine\lib\petools.jar
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:
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.
The following table lists the names of the compressed fix client update files by operating system type:
Operating system type |
Name of compressed Content Platform Engine client update file |
|---|---|
| AIX |
5.5.5.0-P8CPE-CLIENT-AIX.tar.gz |
| Linux |
5.5.5.0-P8CPE-CLIENT-LINUX.tar.gz |
| Windows |
5.5.5.0-P8CPE-CLIENT-WIN.zip |
| zLinux |
5.5.5.0-P8CPE-CLIENT-ZLINUX.tar.gz |
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.
If you have a custom application which uses the Content Platform Engine client files then follow the below instructions:
Installation errors are recorded in the ceclient_install_log_5.5.5.0.txt file, which is in the ceclient_install_path directory.
The installation and configuration of the client upgrade for this interim fix is complete.
Complete the following procedure to install the Content Platform Engine client updates silently.
The following table lists the names of the compressed fix client update files by operating system type:
Operating system type |
Name of compressed Content Platform Engine client update file |
|---|---|
| AIX |
5.5.5.0-P8CPE-CLIENT-AIX.tar.gz |
| Linux |
5.5.5.0-P8CPE-CLIENT-LINUX.tar.gz |
| Windows |
5.5.5.0-P8CPE-CLIENT-WIN.zip |
| zLinux |
5.5.5.0-P8CPE-CLIENT-ZLINUX.tar.gz |
Install this fix by running the following command that is appropriate for your operating system.
Operating system |
Command to install the Content Platform Engine server update |
|---|---|
| AIX |
5.5.5.0-P8CPE-CLIENT-AIX.BIN -i silent -f ceclient_silent_install.txt |
| Linux |
5.5.5.0-P8CPE-CLIENT-LINUX.BIN -i silent -f ceclient_silent_install.txt |
| Windows |
5.5.5.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.5.0-P8CPE-CLIENT-ZLINUX.BIN -i silent -f ceclient_silent_install.txt |
Installation errors are recorded in the ceclient_install_log_5.5.5.0.txt file, which is in the ceclient_install_path directory.
The installation and configuration of the client upgrade for this interim fix is complete.
This interim fix updates the tools private Java files.
Complete the following procedure to update tools IBM Java to v8.0.6.15 July 2020.
If the JRE version is older (lower number) than IBM Java JRE 8.0 SR6 FP15, then continue on to the next step. If Java 8.0 SR6 FP15 is already installed, then no further action is required, since 8.0 SR6 FP15 should only be installed once.
$ java -version
This interim fix updates the Process Designer and Process Engine Tools Jace.jar file.
Complete the following procedure to update Process Designer and Process Engine Tools.
Linux
installation_location/ContentEngine/lib/Jace.jar
Windows
installation_location\ContentEngine\lib\Jace.jar
The following table lists the product fixes for this interim fix.
APAR |
Description |
|---|---|
PJ46171 |
Case Analyzer loading Process Task Manager user interface is slow when there are lots of user defined fields. |
PJ46297 |
FileNet Deployment Manager (FDM): E_ACCESS_DENIED error occurs when trying to import a document with the "Sharing Controller" property. |
PJ46298 |
Three PDF files create invalid thumbnail images - text displayed in the image is invalid. |
PJ46302 |
Administration Console for Content Platform Engine (ACCE) search results issue when clicking column header to sort. |
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. |
PJ46383 |
Launching a Workflow Subscription with a user who is not the SystemUserName (bootstrap user), the workflows launch with the F_Originator parameter value being the SystemUserName. |
PJ46392 |
Administration Console for Content Platform Engine (ACCE) replaces white space with plus sign "+" when downloading content with accents. |
The following table lists the product fixes for this interim fix.
APAR |
Description |
|---|---|
PJ46165 |
Centra FCP FPPool close cause crash in customer environment. |
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. |
PJ46211 |
Administration Console for Content Platform Engine (ACCE) Legacy Workflow System's Adapter's Configure User Interface (UI) may display incorrect Object Store. |
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. |
PJ46219 |
S3 Storage Configuration parameters are defined as static, might cause issues in certain situations. |
PJ46228 |
E_BAD_PARAMETER exception caused by invalid binary id in Content Search Services (CSS) search result set. |
PJ46232 |
Process Engine (PE) Web Services (PEWS) Client Authentication Issue when using BINARYSECURITYTOKEN instead of username - method does not exist wsiAuthenticator error. |
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. |
APAR |
Description |
|---|---|
PJ46194 |
CONTENT_CA_SKIP_FAILED error occurs when retrieving files greater than 1 MB from an ICOS device using WSI. |
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. |
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. |
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.
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.
| Date |
Description |
|---|---|
| 5 February 2021 |
Initial interim fix release. |
| 26 February 2021 |
Added OIT SUSE known issue. |