Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.2.1.7-P8CPE
Fix ID: 5.2.1.7-P8CPE-IF002
Publication date: 25 May 2018
Last modified date: 31 July 2018
This interim fix updates the Content Platform Engine "engine-xx.ear" file, where "xx" represents the Content Platform Engine application server type (ws, wl, wl122, jb, or jbc). This fix also includes updates to the CSSClientConfig.jar, Content Engine Bulk Importer and the Deployment Manager.
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 following issues are included in interim fix 5.2.1.7-P8CPE-IF002:
The following issues are included in interim fix 5.2.1.7-P8CPE-IF001:
Click the following link to access the files for this interim fix update: Fix Central for Interim Fix 5.2.1.7-P8CPE-IF002. You need an IBM login and password to access this download location.
This interim fix requires:
Following are some known problems and restrictions that are related to this interim fix: See 5.2.1.7-P8CPE-FP007 readme for a list of other known issues.
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 bootstrapped Content Platform Engine EAR file on this first server, you will be directed to copy the bootstrapped EAR file to each of the other servers and deploy the bootstrapped EAR file on all of the servers.
Complete the following tasks to prepare the Content Platform Engine server this interim fix.
You can determine the location of the existing bootstrapped EAR file for Content Platform Engine by viewing the contents of the Servers.xml file, which is in the ce_install_path directory.
Complete the following tasks to install this interim fix.
Navigate to the temporary directory where you extracted the contents of this interim fix.
UNIX
installation_location/FileNet/ContentEngine/lib
Windows
installation_location\ContentEngine\lib
Only on systems where Content Search Services (CSS) indexing and searching is configured.
UNIX
installation_location/FileNet/ContentEngine/lib/
installation_location/FileNet/ContentEngine/tools/configure/plugins/com.filenet.css.client_5.2.0.cm5217/
Windows
installation_location\FileNet\ContentEngine\lib\
installation_location\FileNet\ContentEngine\tools\configure\plugins\com.filenet.css.client_5.2.0.cm5217\
UNIX eg chmod 777 CSSClientConfig.jar
Intermediate Fix 5.2.1.7-P8CPE-IF001 and later includes Oracle Outside In Technology (OIT) v8.5.3. This new OIT version requires a new 64-bit Microsoft Visual C++ DLL. Install the Microsoft Redistributable files only on Windows systems where Content Search Services (CSS) indexing or searching is installed, or Thumbnails are configured.
Windows
Complete the following post-installation tasks to configure the affected servers after the installation of this interim fix.
Before you can deploy Content Platform Engine, you must gather information that is needed for the application server configuration profile and for start up and deployment of the Content Platform Engine EAR file.
To help prevent errors when you are redeploying the updated version of Content Platform Engine, remove the previously deployed copy of Content Platform Engine from the application server before you deploy the updated Content Platform Engine. The following sections provide information on specific application servers.
Use the administrative console to uninstall the "FileNetEngine" application. This action deletes the Engine-ws.ear file from IBM WebSphere Application Server.
Use the Change Center in the administrative console to delete the "FileNetEngine" application. This action deletes the Engine-wl.ear file from Oracle WebLogic Server.
Based on your "Standard" or "Cluster" deployment, remove the Engine-jb.ear file or Engine-jbc.ear file from one of the following directories, where jboss_install_directory is the JBoss installation directory and custom_name is the name of a user-defined directory.
Standard deployment
jboss_install_directory\server\default\deploy
jboss_install_directory\server\custom_name\deploy
Cluster deployment
jboss_install_directory\server\all\deploy
To help prevent errors when you are redeploying the updated version of Content Platform Engine, remove the application server cache as described in the following topics.
MULTI-CPE NODE NOTE If your system has multiple Content Platform Engine nodes that run in a "managed" configuration, remove the application server cache directories from only the central "managing" application server and not from any managed application servers. If your system has multiple Content Platform Engine nodes that run in a "non-managed" configuration (multiple stand-alone application servers), remove the application server cache directories from all the application servers in the configuration.
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name\temp\node_name\server_name\FileNetEngine\
C:\bea\user_projects\domains\mydomain\servers\AdminServer\tmp\_WL_user\FileNetEngine
C:\bea\user_projects\domains\mydomain\servers\AdminServer\cache\EJBCompilerCache
Standard deployment
jboss_install_directory\server\default\tmp\deploy
jboss_install_directory\server\default\work\jboss.web\localhost\FileNet
jboss_install_directory\server\custom_name\tmp\deploy
jboss_install_directory\server\custom_name\work\jboss.web\localhost\FileNet
Cluster deployment
jboss_install_directory\server\all\tmp\deploy
jboss_install_directory\server\all\work\jboss.web\localhost\FileNet
Clear the internet browser cache on all client computers that use Administration Console for Content Platform Engine (ACCE) for administering Content Platform Engine.
Before you can verify setup information and deploy Content Platform Engine, the user who is designated as the cpe_install_user user must grant certain permissions to the user who is designated as the config_mgr_user.
NOTE Complete this procedure only if you need to add or update permissions on the target directories and files.
The executable name depends upon the interface that will be used to run the Configuration Manager:
| Configuration Manager interface |
Executable name |
|---|---|
UNIX graphical user interface |
configmgr |
UNIX command line |
configmgr_cl |
Windows graphical user interface |
configmgr.exe |
Windows command line |
configmgr_cl.exe |
The ce_install_path/tools/configure directory is the default directory that Configuration Manager uses if a directory path is not specified when the configuration profile information for deploying Content Platform Engine is verified.
Complete the tasks in this section to configure the server set-up information and to deploy Content Platform Engine.
Completing Configuration Manager tasks interactively
Completing Configuration Manager tasks using the command line
Complete the following tasks in the order that is shown to set up and deploy the Content Platform Engine.
Select Start > All Programs > IBM FileNet P8 Platform > FileNet Configuration Manager or run the following command: ce_install_path\tools\configure\configmgr.exe.
Run the following command from the command line: ce_install_path/tools/configure/configmgr.
Complete the following procedure to choose which licenses apply for your system.
The licensing choices that are stored in the software tag files are written into the Content Platform Engine EAR file as part of the "Configure Bootstrap and Text Extraction" task execution.
The IBM System Dashboard for Enterprise Content Management Listener component is configured with that licensing information so that usage reporting and the IBM License Metric Tool can make the correct product and license association.
If you rerun the "Choose Licenses" task with a different set of licensing choices, you must complete the following steps in order that the Content Platform Engine component that is running always has the correct licensing information:
Complete the following procedure to enter, update, or verify the Content Platform Engine bootstrap information.
IMPORTANT The default value is Configure New, but you must change it to Upgrade.
(Multiple non-managed stand-alone application servers only) Copy the bootstrapped Content Platform Engine EAR file into the profiles directory (where 5.2.1.0-P8CPE was originally bootstrapped) on each of the remaining Content Platform Engine application servers in your P8 domain. For example:
ce_install_path\tools\configure\profiles\myprofile\ear
(JBoss Application server) Based on your "Standard or Cluster" deployment, remove the Engine-jb.ear file or Engine-jbc.ear file from one of the following directories, where jboss_install_directory is the JBoss installation directory and custom_name is the name of a user-defined directory.
Standard deployment
jboss_install_directory\server\default\deploy
jboss_install_directory\server\custom_name\deploy
Cluster deployment
jboss_install_directory\server\all\deploy
The location where you copy the bootstrapped Content Platform Engine EAR file is referred to as the "bootstrapped EAR path." You must enter this path when you deploy the Content Platform Engine EAR file on the remaining application servers.
Complete the following procedure to enter, update, or verify deployment information.
IMPORTANT If a configuration profile previously existed and the configuration information does not require editing begin with Deploying Content Platform Engine. If you just created a configuration profile for an upgrade, continue with the following steps.
Parameter name |
Description |
|---|---|
| Deployment type |
Enter or verify the deployment type. The valid values are: Standard, Network Deployment, or Cluster.
If you change this setting, you will be required to provide values for the properties required by the selected deployment type. |
| Bootstrapped EAR path |
Enter or verify the fully qualified path to the bootstrapped and updated Content Platform Engine EAR file that was created by the "Configure bootstrap" task. |
| Content Platform Engine Application name |
Enter or verify the Content Platform Engine application name as it will appear in the application server (for example, in an administration console). The application name is subject to application server naming constraints. For WebSphere Application Server, each application in a cell must have unique name. The default is FileNetEngine. |
| Application server node |
Enter or verify the name of the WebSphere Application Server node where Content Platform Engine will be deployed (n/a for Cluster Deployment Type). |
| Application server name |
Enter or verify the name of the WebSphere Application Server where Content Platform Engine will be deployed (n/a for Cluster Deployment Type). |
| Script |
Enter or verify the fully qualified path to the deploy configuration task script. The task script filename depends on the application server type selected. |
| Temporary directory |
Enter or verify the fully qualified path to a temporary directory to be used by the configuration task. |
| Parameter name |
Description |
|---|---|
| Deployment type |
Enter or verify the deployment type. The valid values are: Standard or Cluster.
If you change this setting, you will be required to provide values for the properties required by the selected deployment type. |
| Bootstrapped EAR path |
Enter or verify the fully qualified path to the bootstrapped and updated Content Platform Engine EAR file that was created by the "Configure bootstrap" task. |
| Kerberos support |
Select this check box if you want to use Kerberos authentication. |
| Parameter name |
Description |
|---|---|
| Bootstrapped EAR path |
Enter or verify the fully qualified path to the bootstrapped and updated Content Platform Engine EAR file that was created by the "Configure bootstrap" task. |
| Content Platform Engine Application name |
Enter or verify the Content Platform Engine application name as it will appear in the application server (for example, in an administration console). The application name is subject to application server naming constraints. The default is FileNetEngine. |
| Script |
Enter or verify the fully qualified path to the deploy configuration task script. The task script filename depends on the application server type selected. |
| Temporary directory |
Enter or verify the fully qualified path to a temporary directory for use by the configuration task. |
Right-click Deploy Application in the Content Platform Engine Task View pane, and select Run Task to deploy Content Platform Engine. This task can take a few minutes. Task execution status messages display in the Console pane.
Stop and start the application server, as follows:
Stop and restart all servers and clusters where the Content Platform Engine EAR file has been deployed.
Start all servers and clusters where the Content Platform Engine EAR file has been deployed.
Installation of the interim fix is now complete. Continue with Verifying the deployment of the updated Content Platform Engine EAR file.
Complete the following procedure to specify setup information and deploy Content Platform Engine.
configmgr_cl listServers
configmgr_cl generateupgrade [-appserver app_server_type] -server server_name [-deploy deploy_type] -profile myprofile [-silent] [-force] [-help]
If a message indicates that a profile already exists, record the profile name. Use this profile name in places where this readme references myprofile.
The following table lists the descriptions for the configmgr_cl generateupgrade command parameters:
| Parameter |
Description |
|---|---|
| -appserver appserver_type |
The -appserver appserver_type parameter is required only if the ce_install_path/Servers.xml file does not exist or does not contain any servers. This parameter specifies the type of application server and must be one of the following values: WebSphere, WebLogic, or JBoss. |
| -server server_name |
The -server server_name parameter indicates the server to create the upgrade profile for. Run the configmgr_cl listServers command to displays a list of valid server name values before you run the generateupgrade command. |
| -deploy deploy_type |
Type of deployment.
Required if the Servers.xml file does not exist or does not contain a deployment type for the selected server. If the Servers.xml file already has a deployment type for the selected server, then the value from the Servers.xml file is used instead of the value you specify on the command line.
|
| -profile myprofile |
The myprofile value can be one of the following items:
If the path includes a directory name with spaces, enclose the entire path in quotation marks. For example, enter "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\cpe_was_tiv_db2\cpe_was_tiv_db2.cfgp". |
| -silent |
When -silent is specified, no prompts or informational messages display in the console, but errors are written to the log. Failure messages and validation error messages display as needed, such as messages about missing passwords or invalid port numbers.<
If you run the execute command to run all the tasks in a profile, and you specify the -silent parameter, you must also specify the -force parameter. The -silent parameter is optional. |
| -force |
When -force is specified, the command is forced to continue running while in silent mode. |
| -help |
When -help is specified, a brief message displays on the command syntax instead of running the command. |
<propertyname="ApplicationServerAdminUsername">
<value>administrator_user_name</value>
</property>
<property name="ApplicationServerInstallationFolder">
<value>/opt/IBM/WebSphere/AppServer</value>
<description>Enter the absolute path to the directory where the WebSphere Application Server is installed.</description>
<displayName>Application server installation directory</displayName>
</property>
<property name="ApplicationServerProfileFolder">
<value>/opt/IBM/profiles/AppSrv01</value>
<description>Enter the absolute path to the directory where the WebSphere Application Server profile for Content Platform Engine is stored. If you are installing Content Platform Engine on a node in a cluster or on a managed server node and Deployment Manager is remote from Configuration Manager, use the directory for the WebSphere profile that is located on the node.</description>
<displayName>Application server profile directory</displayName>
</property>
configmgr_cl storepasswords -profile myprofile
Repeat this step as needed to edit the application server properties for each Content Platform Engine instance directory that was created.
configmgr_cl generateConfig -task configurebootstrap -profile myprofile -bootstrap upgrade -appserver appserver_type
The bootstrap information that you define is stored in the configurebootstrap.xml and the deployapplication.xml files. However, the system saves a unique configurebootstrap.xml file each time the bootstrap information is generated. For example, the initial file name is configurebootstrap.xml. The subsequent file names are configurebootstrap.n.xml where "n" represents the number of each of the subsequent files in ascending numerical order.
If this is the first time that the bootstrap information has been generated:
JBoss example: <configuration class="com.ibm.ecm.configmgr.product.ce.task.UpgradeJBBootstrap">
configmgr_cl execute -task configurebootstrap -profile myprofile
Status messages display in the console.
If the bootstrap information has been previously generated:
JBoss example: <configuration class="com.ibm.ecm.configmgr.product.ce.task.UpgradeJBBootstrap">
configmgr_cl execute -task configurebootstrap -profile myprofile -taskfile configurebootstrap.2.xml
Status messages display in the console.
configmgr_cl checkStatus -task configurebootstrap -profile myprofile -taskfile configurebootstrap.n.xml
configmgr_cl checkStatus -task configurebootstrap -profile myprofile
ContentEngine\tools\configure\profiles\myprofile\ear
configmgr_cl execute -task deployapplication -profile myprofile
configmgr_cl checkstatus -task deployapplication -profile myprofile
Installation of this interim fix is now complete. Continue with the next section, Configuring the server after installation: Verifying the deployment of the updated Content Platform Engine EAR file.
Complete the following procedure to verify that Content Platform Engine deployed successfully:
http://server:port/FileNet/Engine
The defaults for the application server HTTP port number are as listed:
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, such as Application Engine, Workplace XT, IBM FileNet Services for Lotus Quicker, and IBM Enterprise Records servers and any custom Content Platform Engine-related Java EE applications (like IBM Content Navigator).
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.2.1.7-P8CPE-CLIENT-AIX.tar.gz |
| HP-UX |
5.2.1.7-P8CPE-CLIENT-HPUX.tar.gz |
HP-UX Itanium |
5.2.1.7-P8CPE-CLIENT-HPUXI.tar.gz |
| Linux |
5.2.1.7-P8CPE-CLIENT-LINUX.tar.gz |
| Solaris |
5.2.1.7-P8CPE-CLIENT-SOL.tar.gz |
| Windows |
5.2.1.7-P8CPE-CLIENT-WIN.zip |
| zLinux |
5.2.1.7-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 are running IBM FileNet P8, Version 5.2 or later, you can update the Content Platform Engine client connector files when you run the IBM Content Navigator Configuration and Deployment Tool.
Synchronize the Content Platform Engine server and client files in your Case Manager V5.2 system by running the "Update the Content Platform Engine Client Connector Files" task in the Case Manager V5.2 configuration tool. If Workplace XT is installed on the same server, running this task also updates the Content Platform Engine client files for Workplace XT.
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.2.1.7.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.2.1.7-P8CPE-CLIENT-AIX.tar.gz |
| HP-UX |
5.2.1.7-P8CPE-CLIENT-HPUX.tar.gz |
HP-UX Itanium |
5.2.1.7-P8CPE-CLIENT-HPUXI.tar.gz |
| Linux |
5.2.1.7-P8CPE-CLIENT-LINUX.tar.gz |
| Solaris |
5.2.1.7-P8CPE-CLIENT-SOL.tar.gz |
| Windows |
5.2.1.7-P8CPE-CLIENT-WIN.zip |
| zLinux |
5.2.1.7-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.2.1.7-P8CPE-CLIENT-AIX.BIN -i silent -f ceclient_silent_install.txt |
| HP-UX |
5.2.1.7-P8CPE-CLIENT-HPUX.BIN -i silent -f ceclient_silent_install.txt |
| HP-UX Itanium |
5.2.1.7-P8CPE-CLIENT-HPUXI.BIN -i silent -f ceclient_silent_install.txt |
| Linux |
5.2.1.7-P8CPE-CLIENT-LINUX.BIN -i silent -f ceclient_silent_install.txt |
| Solaris |
5.2.1.7-P8CPE-CLIENT-SOL.BIN -i silent -f ceclient_silent_install.txt |
| Windows |
5.2.1.7-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.2.1.7-P8CPE-CLIENT-ZLINUX.BIN -i silent -f ceclient_silent_install.txt |
Installation errors are recorded in the ceclient_install_log_5.2.1.7.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 bulkimport.jar file.
Complete the following procedure to update Content Engine Bulk Importer.
CE_home/tools/CEBI/bulkimport.jar
CE_home/tools/CEBI/
This interim fix updates the com.filenet.deployment.common_5.2.1.jar, com.filenet.deployment.engine_5.2.1.jar, com.filenet.deployment.modules_5.2.1.jar, com.filenet.deployment.rcp_5.2.1.jar, imex.jar, and listener.jar files.
Complete the following procedure to update Deployment Manager.
cpe_installation_directory/IBM/FileNet/ContentEngine/tools/deploy/plugins/ cpe_installation_directory/IBM/FileNet/ContentEngine/tools/deploy/plugins/com.filenet.imex_5.2.1/ cpe_installation_directory/IBM/FileNet/ContentEngine/tools/deploy/plugins/com.filenet.pch_5.2.1/
cpe_installation_directory\IBM\FileNet\ContentEngine\tools\deploy\plugins\ cpe_installation_directory\IBM\FileNet\ContentEngine\tools\deploy\plugins\com.filenet.imex_5.2.1\ cpe_installation_directory\IBM\FileNet\ContentEngine\tools\deploy\plugins\com.filenet.pch_5.2.1\
cpe_installation_directory/IBM/FileNet/ContentEngine/tools/deploy
cpe_installation_directory\IBM\FileNet\ContentEngine\tools\deploy
and run the following command:DeploymentManager -clean
DeploymentManager.exe -clean
This interim fix does not have an uninstall option.
The following table lists the product fixes for this interim fix.
APAR |
Description |
|---|---|
PJ44729 |
The behavior of the ContentOperations.delete(VWAttachment) method in 5.0.0 and 5.2.1 is not the same. |
PJ44765 |
E_BAD_VALUE occurs when creating an instance of a document class containing a choice list assigned to a property definition. |
PJ44778 |
Cannot select all ACE's for security update in Bulk Operations within Administration Console for Content Platform Engine (ACCE) with Microsoft Internet Explorer (IE). |
PJ44858 |
Process Engine (PE) peverify: Failed to verify PE repository error. |
PJ44887 |
Process Engine (PE) intermittent ORA-24816 exception during transfer exposing a large field on a queue or roster, and then retry and fail again, repeatedly. |
PJ44946 |
Administration Console for Content Platform Engine (ACCE) security updates creates unneeded Access Control Entries (ACE) entries. |
PJ44952 |
Administration Console for Content Platform Engine (ACCE) Panel Scrolling issue multiple vertical and horizontal scrollbars. |
PJ44963 |
Administration Console for Content Platform Engine (ACCE) security template is not displayed on documents. |
PJ45070 |
Administration Console for Content Platform Engine (ACCE) cannot directly create a file storage area or advanced storage area with 256-bit encryption "Read-only property EncryptionKey cannot be updated" error. |
PJ45088 |
NullPointerException with PEEJBSession executeRPC when ICM EventHandler is updating Process Engine (PE) datafields (peSyncUpWorkObjects) to synchronize data between Content Engine (CE) and Process Engine (PE). |
PJ45142 |
Process Engine (PE) transfer in a farm, server that cannot claim region lock does not stop the transfer and continues to use the old workspace. |
PJ45215 |
Move content for a no-content elements documents to a Fixed Storage Area will leave the referral bob as pending migration. |
PJ45233 |
Out-of-Band XXE through Workflow Parser. |
PJ45234 |
Provide look-ahead Java Serialization in relation to the Process Engine (PE) HTTP input stream readObject method which was exposed with Apache common collection security vulnerability. |
PJ45245 |
Fix Cross Site Scripting Reflected - XSS in some Process Engine (PE) components. |
PJ45248 |
"Unable to find replacement value. type='Principal'" error occurs when trying to convert an IBM Content Navigator (ICN) entry template in FileNet Deployment Manager (FDM). |
PJ45249 |
Need to secure the /admin/api path for Process Engine (PE) ping page. |
PJ45266 |
Workflow collections fail to convert using FileNet Deployment Manager (FDM). |
PJ45275 |
Content on file system storage device is not deleted when the Deletion mode of the advanced Storage area is set to Destroy or Purge. |
PJ45276 |
PERSIST_TS_CANT_CHANGE_INDEXING_LANGUAGE error occurs in FileNet Deployment Manager (FDM) reassign Object Store operation. |
PJ45293 |
Java Virtual Machine (JVM) should exit when METADATA_STATIC_LOAD_FAILED exceptions occur. |
PJ45308 |
Axis SoapMonitorService may make Process Engine (PE) system vulnerable to Deserialization of Untrusted Data. |
PJ45333 |
Content Engine Bulk Importer Tool (CEBIT) does not allow for property values with only a space. |
PJ45334 |
PSIRT 11720: (CVE-2018-1542), PSIRT 11721 (CVE-2018-1555), PSIRT 11722 (CVE-2018-1556): Administration Console for Content Platform Engine (ACCE) Cross-site scripting vulnerability. See security bulletin 2015943 |
PJ45337 |
PSIRT 12022 (CVE-2018-2768, CVE-2018-2806, CVE-2018-2801): Open Source Oracle Outside In Technology Vulnerabilities - April 2018. See security bulletin 2007456 |
APAR |
Description |
|---|---|
PJ44314 |
FileNet Bulk Import tool performance enhancement with large number of classes. |
PJ44648 |
Performance of the update statement for the ContentQueue expired processing is unable to be optimized. |
PJ44720 |
Administration Console for Content Platform Engine (ACCE) cannot add new Property Definition to a class. |
PJ44724 |
Thread race condition causes Null Pointer Exception (NPE) in isAnonymousUser. |
PJ44751 |
FNRCE0023E: E_FAILED error occurs when trying to restore document from the recovery bin. |
PJ44752 |
Content Platform Engine Bulk Import (CEBI) process does not get stopped by CEBI.Shutdown. |
PJ44757 |
Administration Console for Content Platform Engine (ACCE) recycle bin allows duplicate documents and cannot be emptied. |
PJ44766 |
Search template in CE_Operation SearchForMany always returns attachment for specific Doc version not current or released version. |
PJ44821 |
API_PROPERTY_NOT_IN_CACHE error occurs on merge searches with order by clause. |
PJ44830 |
Adding new document as minor version to a task configured with CE_Operations may result in error. |
PJ44857 |
.msg files added to P8 Content Platform Engine have mimetype of application/octet-stream instead of application/vnd.ms-outlook. |
PJ44890 |
Cross Repository search does not return values when a MVP String is included in the search. |
PJ44893 |
Cannot add custom sweep actions in FileNet Deployment Manager (FDM) to export. |
PJ44904 |
Error messages on ContentQueueDirectoryCleanUp missing required information. |
PJ44910 |
java.lang.NumberFormatException occurs when trying to query for a number greater than 2,147,483,648 on a double property.. |
PJ44914 |
Content Engine Bulk Import (CEBIT) does not support usernames with a space. |
PJ44971 |
Content Platform Engine Bulk Import Tool (CEBI) is not pulling back all document classes when running -G. |
PJ44973 |
Orphaned SIDs prevent Permissions updates. |
PJ44991 |
Administration Console for Content Platform Engine (ACCE) hangs on Search - Bulk Actions tab when duplicate recovery bins exist. |
PJ45015 |
A cooperative lock is not released by the lock owner over a checkout. |
PJ45017 |
Administration Console for Content Platform Engine (ACCE) Bulk Action tab gets stuck by duplicate recovery bins created via API. |
PJ45019 |
peREST: support Basic Authentication for SSO. |
PJ45029 |
Unable to upgrade IBM Enterprise Records addon on WebLogic. |
PJ45131 |
LDAP: vwtool/refreshEnv does not detect that an env record has been changed from group to user. |
PJ45153 |
ECS/Centera Retention Handling fixes. |
PJ45188 |
Process Engine (PE) worker thread is looping when the workobject blob is unexpectedly null. |
PJ45167 |
Expand CE_Operation to support setStringProperty() with id as input. |
PJ45179 |
Case History Store stops processing events. |
PJ45235 |
Using a date from a Case folder or task to update a filed in a Process Engine (PE) event log fails. |
APAR |
Description |
|---|---|
PJ45042 |
Isilon session idle timeout handling fix. |
PJ45055 |
PSIRT 10042 (CVE-2016-1000031): Open Source Commons FileUpload Apache Vulnerabilities. See techdoc 2010868 |
PJ45057 |
Snaplock Delete using Java File IO leaves entry in the Content Queue. |
APAR |
Description |
|---|---|
PJ45011 |
FileNet Deployment Manager (FDM) resets a source required class back to the default class during export. |
APAR |
Description |
|---|---|
PJ44544 |
Content Federated Services - Image Services (CFS-IS) Connection Timed Out exception corrupts SSI handle. |
APAR |
Description |
|---|---|
PJ44856 |
Dashboard PCH process prevents WebSphere JVM from shutting down. |
APAR |
Description |
|---|---|
PJ44912 |
Content Federated Services - Image Services (CFS-IS) cannot federate documents that contain Daeja 5.0 annotations. |
APAR |
Description |
|---|---|
PJ44901 |
Intermittent Isilon device session absolute timeout. |
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 |
|---|---|
| 25 May 2018 |
Initial release of this limited availability fix. |
| 29 May 2018 |
Added missing APARs PJ45248 & PJ45266. |
| 31 July 2018 |
Add Microsoft re-distributable instructions for thumbnail Outside In Technology. |