Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.5.9.0-P8CPE
Fix ID: 5.5.9.0-P8CPE-IF001
Publication date: 26 October 2022
Last modified date: 26 October 2022
This interim fix updates the Content Platform Engine and FileNet Deployment Manager, Process Designer 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.9, 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.9.0-P8CPE-IF001. You need an IBM login and password to access this download location.
To verify that FileNet Content Manager files were not altered, see the signature verification technical note 6416109.
This interim fix requires:
The following changes are introduced in this 5.5.9.0-P8CPE-IF001 Interim Fix:
Following are some known problems and restrictions that are related to this interim fix:
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:
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.
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.
UNIX
<WebSphere_install_location>/<AppServer>/profiles/<profile_name>/FileNet/<server_name>/INSO/bin/sx-8-x-x-linux-x86-64/sx.cfg <WebSphere_install_location>/<AppServer>/profiles/<profile_name>/FileNet/<server_name>/INSO/bin/sx-8-x-x-linux-x86-64/ix.cfg <WebSphere_install_location>/<AppServer>/profiles/<profile_name>/FileNet/<server_name>/INSO/bin/sx-8-x-x-linux-x86-64/sxhtml.cfg <WebSphere_install_location>/<AppServer>/profiles/<profile_name>/FileNet/<server_name>/INSO/bin/sx-8-x-x-linux-x86-64/CSEStellentConfig.properties <WebSphere_install_location>/<AppServer>/profiles/<profile_name>/FileNet/<server_name>/INSO/bin/sx-8-x-x-linux-x86-64/css_mime_actions_config.xml
Windows
<WebSphere_install_location>\<AppServer>\profiles\<profile_name>\FileNet\<server_name>\INSO\bin\sx-8-x-x-win-x86-64\sx.cfg <WebSphere_install_location>\<AppServer>\profiles\<profile_name>\FileNet\<server_name>\INSO\bin\sx-8-x-x-win-x86-64\ix.cfg <WebSphere_install_location>\<AppServer>\profiles\<profile_name>\FileNet\<server_name>\INSO\bin\sx-8-x-x-win-x86-64\sxhtml.cfg <WebSphere_install_location>\<AppServer>\profiles\<profile_name>\FileNet\<server_name>\INSO\bin\sx-8-x-x-win-x86-64\CSEStellentConfig.properties <WebSphere_install_location>\<AppServer>\profiles\<profile_name>\FileNet\<server_name>\INSO\bin\sx-8-x-x-win-x86-64\css_mime_actions_config.xml
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-authn.jar
installation_location/ContentEngine/lib/Engine-xx.ear installation_location/ContentEngine/lib/pe.jar (from inside Engine-*.ear\APP-INF\lib\pe.jar)
Windows
installation_location\ContentEngine\lib\Engine-authn.jar
installation_location\ContentEngine\lib\Engine-xx.ear installation_location\ContentEngine\lib\pe.jar (from inside Engine-*.ear\APP-INF\lib\pe.jar)
Delete the below files and directories (if they are present)
UNIX
installation_location/ContentEngine/lib/httpClient-4.5.12.jar installation_location/ContentEngine/lib/log4j-1.2.17.jar installation_location/ContentEngine/lib/Jace_t.jar installation_location/ContentEngine/lib/pe_t.jar installation_location/ContentEngine/lib/pe3pt_t.jar
Windows
installation_location\ContentEngine\lib\httpClient-4.5.12.jar installation_location\ContentEngine\lib\log4j-1.2.17.jar installation_location\ContentEngine\lib\Jace_t.jar installation_location\ContentEngine\lib\pe_t.jar installation_location\ContentEngine\lib\pe3pt_t.jar
UNIX
user_home_directory/configmgr_workspaceWindows
user_home_directory\configmgr_workspaceUNIX
user_home_directory/configmgr_workspace_5.5.9Windows
user_home_directory\configmgr_workspace_5.5.9Only on Windows systems where Content Search Services (CSS) indexing and searching or Thumbnails are configured for Oracle Outside In Technology (OIT) v8.5.3 and higher.
Note: If the Microsoft 2013 & 2015-2019 Redistributable files are currently installed, you do not need to re-install them. Both 2013 & 2015-2019 versions are required.
Windows
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.9 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.9.0-P8CPE version or your upgrade from a pre-5.5.9 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 uninstall, see Knowledge Center topic Removing Content Platform Engine and to deploy see Knowledge Center topic Deploying Content Platform Engine instances.
To redeploy/update an existing 5.5.9.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.9.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
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.8.0-P8CPE.
To uninstall, see Knowledge Center topic Removing Content Platform Engine and to deploy see Knowledge Center topic Deploying Content Platform Engine instances.
To redeploy/update an existing 5.5.9.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.9.0-P8CPE.
See Knowledge Center topic Planning and preparing for FileNet P8 updates for deploy update WebSphere Application Edition Management (AEM) details.
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.
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.
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.
Delete the below files (if they are present)
UNIX
Windows
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.9.0-P8CPE-CLIENT-AIX.tar.gz |
| Linux |
5.5.9.0-P8CPE-CLIENT-LINUX.tar.gz |
| Windows |
5.5.9.0-P8CPE-CLIENT-WIN.zip |
| zLinux |
5.5.9.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.9.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.9.0-P8CPE-CLIENT-AIX.tar.gz |
| Linux |
5.5.9.0-P8CPE-CLIENT-LINUX.tar.gz |
| Windows |
5.5.9.0-P8CPE-CLIENT-WIN.zip |
| zLinux |
5.5.9.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.9.0-P8CPE-CLIENT-AIX.BIN -i silent -f ceclient_silent_install.txt |
| Linux |
5.5.9.0-P8CPE-CLIENT-LINUX.BIN -i silent -f ceclient_silent_install.txt |
| Windows |
5.5.9.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.9.0-P8CPE-CLIENT-ZLINUX.BIN -i silent -f ceclient_silent_install.txt |
Installation errors are recorded in the ceclient_install_log_5.5.9.0.txt file, which is in the ceclient_install_path directory.
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.
The installation and configuration of the client upgrade for this interim fix is complete.
This interim fix updates the server tools private Java files used by Configuration Manager User Interface (CMUI), the Content Engine (CE) and Process Engine (PE) tools, and the un-installer.
Complete the following procedure to update server tools IBM Java to v8.0.7.15 August 2022.
If the JRE version is older (lower number) than IBM Java JRE 8.0 SR7 FP15, then continue on to the next step. If Java 8.0 SR7 FP15 is already installed, then no further action is required, since 8.0 SR7 FP15 should only be installed once.
$ java -version
For customers that have installed the FileNet Deployment Manager (FDM) tool, this interim fix updates the FileNet Deployment Manager files.
Complete the following procedure to update Deployment Manager.
Linux Unzip fdm-linux.zip
Windows Unzip fdm-windows.zip
Linux Copy the fdm-linux.zip extracted files in the deploy directory to installation_location/deploy/
Run the following command: chmod +x DeploymentManager
Windows Copy the fdm-linux.zip extracted files in the deploy directory to installation_location\deploy\
Linux
FDM_installation_directory/deploy
Run the following command: DeploymentManager -clean
Windows
FDM_installation_directory\deploy
Run the following command: DeploymentManager.exe -clean
Note: With 5.5.9.0-P8CPE (GA) and higher versions, the Process Engine (PE) Process Designer (PD) tools are installed separately from Passport Advantage.
For customers that have installed the Process Engine (PE) Process Designer (PD) Tools, this interim fix updates the Process Designer and Process Engine Tools pe.jar file.
Complete the following procedure to update Process Designer and Process Engine Tools.
Linux client_library_installation_location/pe.jar
Windows client_library_installation_location\pe.jar
The following table lists the product fixes for this interim fix.
Deployment type: T=Traditional application server, C=Containerized, A=All deployment types
APAR |
Deployment |
Description |
|---|---|---|
PJ46815 |
A |
PSIRT ADV0053879 (CVE-2022-21496): IBM Java (JRE) LDAP security vulnerabilities (April 2022 Oracle Critical Update Patch). See security bulletin 6591917. |
PJ46824 |
A |
SCIM: "The repository is not available" error occurs on first attempt to logon to IBM Content Navigator (ICN). |
PJ46840 |
A |
Process Engine (PE) Process Designer (PD) may start either off-screen or minimized. See technote 6590513. |
PJ46841 |
A |
Multiple failed logins lock user when standalone Process Engine (PE) Process Designer (PD) tries a bad password. |
PJ46843 |
A |
Administration Console for Content Platform Engine (ACCE) not able to access the Search option when SavedSearches folder is renamed. |
PJ46844 |
A |
Administration Console for Content Platform Engine (ACCE) bad error messages from Security Templates. |
PJ46845 |
A |
SCIM directory configuration does not support user with Domain Name (DN) length greater than 508 characters. |
PJ46870 |
A |
Replication continues even after a file system storage device is removed from an advanced storage area. |
PJ46871 |
A |
Process Engine (PE) CE_Operations.sendMailTemplate() failed after Axis2 v1.8.0 upgraded. |
PJ46874 |
A |
Add Kerberos support for the Process Engine (PE) system user on tWAS. |
PJ46882 |
A |
Content Engine (CE) Storage: Move content job sweep fails when updating storage policy for version 0.1 reserved documents. |
PJ46884 |
A |
Send MSSQL date/time columns as literals fails in locale other than en-us. |
PJ46885 |
A |
Add support for mapping members of a Static Role to FileNet Deployment Manager (FDM). |
PJ46886 |
A |
Administration Console for Content Platform Engine (ACCE) LocalizedString table is adding rows for choice list value display names for en-us, then en, then en-us locales. |
PJ46887 |
A |
Content Engine (CE) configured with SunOneProvider/Oracle Unified Directory (OUD) on Server Side Sort (SSS) results in error when searching without a filter. |
PJ46888 |
A |
Case Analyzer: Update Case Analyzer query to get full view definition from MSSQL. |
PJ46906 |
A |
Administration Console for Content Platform Engine (ACCE) unable to add item to choice list when an existing choice item has a null value. |
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 |
|---|---|
| 26 October 2022 |
Initial interim fix release. |
| 18 January 2023 |
Corrected server install of engine-authn & pe.jar. |