Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.2.0.3-P8CPE
Fix ID: 5.2.0.3-P8CPE-IF003
Publication date: 28 August 2014
Last modified date: 28 August 2014
This interim fix updates the Content Platform Engine "Engine-xx.ear" file, where "xx" represents the Content Platform Engine application server type (ws, wl, jb or jbc). See the Interim fix contents (APARs) section of this Readme for a list of fixes in this interim fix.
This interim fix requires:
The following new features are introduced in this interim fix:
Following are some known problems and restrictions that are related to this interim fix:
Click the following link to access the files for this interim fix server update: Fix Central for interim fix 5.2.0.3-P8CPE-IF003. You need an IBM login and password to access this download location.
The files that you download depend on your IBM software license and the GA product that you have installed.
The following table lists the names of the compressed feature pack server update files by operating system type:
Operating system type |
Name of compressed Content Platform Engine feature pack server update file |
|---|---|
AIX® |
5.2.0.3-P8CPE-AIX-IF003.tar.gz |
HP-UX |
5.2.0.3-P8CPE-HPUX-IF003.tar.gz |
HP-UX Itanium® |
5.2.0.3-P8CPE-HPUXI-IF003.tar.gz |
Linux® |
5.2.0.3-P8CPE-LINUX-IF003.tar.gz |
Solaris |
5.2.0.3-P8CPE-SOL-IF003.tar.gz |
Windows® |
5.2.0.3-P8CPE-WIN-IF003.zip |
zLinux |
5.2.0.3-P8CPE-ZLINUX-IF003.tar.gz |
The following table lists the names of the compressed interim fix client update files by operating system type:
Operating system type |
Name of compressed Content Platform Engine interim fix client update file |
|---|---|
| AIX |
5.2.0.3-P8CPE-CLIENT-AIX-IF003.tar.gz |
| HP-UX |
5.2.0.3-P8CPE-CLIENT-HPUX-IF003.tar.gz |
HP-UX Itanium |
5.2.0.3-P8CPE-CLIENT-HPUXI-IF003.tar.gz |
| Linux |
5.2.0.3-P8CPE-CLIENT-LINUX-IF003.tar.gz |
| Solaris |
5.2.0.3-P8CPE-CLIENT-SOL-IF003.tar.gz |
| Windows |
5.2.0.3-P8CPE-CLIENT-WIN-IF003.zip |
| zLinux |
5.2.0.3-P8CPE-CLIENT-ZLINUX-IF003.tar.gz |
The server update automatically completes the following tasks:
The server update also modifies other tools and selectable components. If any client tools such as FileNet Deployment Manager (FDM), Consistency Checker, or the Bulk Import Tool (CEBI), are affected by changes in this interim fix, the installer can be run with the Tools option on those machines to update them.
The client update installs updated Content Platform Engine client files for Content Platform Engine-related Java EE applications, such as FileNet Application Engine, IBM FileNet Workplace XT, and IBM Enterprise Records.
The Content Search Services client software for Content Platform Engine 5.2.0.3-P8CPE-IF003 is packaged with and installed by the interim fix installation program. In the 5.2 GA version, the Content Search Services client software is configured and deployed through the Configuration Manager.
This section consists of two parts: installing the Content Platform Engine 5.2.0.3 files, followed by configuring the Content Platform Engine. If you are licensed for FileNet Content Manager or IBM Content Foundation, complete the following sections.
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, install and configure the Content Platform Engine interim fix 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 the Content Platform Engine interim fix on one of the Content Platform Engine servers in the environment. After you configure the bootstrapped Content Platform Engine EAR file on this first server, copy and deploy the bootstrapped EAR file to each of the other servers.
Complete the following tasks to prepare the Content Platform Engine server for this interim fix.
Important Failure to make a backup of the existing bootstrapped Content Platform Engine EAR file can have serious repercussions on the operation of Content Platform Engine if you accidentally delete or overwrite the existing bootstrapped Content Platform Engine EAR file during the installation of this interim fix. A common symptom of a deleted or an overwritten bootstrapped EAR file is that system users cannot log on to Content Platform Engine and are not able to log on until that file is restored. If this situation occurs, you need a backup to recover.
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.
You can install the server updates either interactively or silently. This section consists of the following steps:
Complete the following procedure to install the Content Platform Engine server updates interactively.
Navigate to the temporary directory that you selected in Preparing the Content Platform Engine server for installation, and install the server updates on Content Platform Engine by running the installation program file that is appropriate for your operating system:
Operating system |
Executable file name for the Content Platform Engine server update |
|---|---|
| AIX |
5.2.0.3-P8CPE-AIX-IF003.BIN |
| HP-UX |
5.2.0.3-P8CPE-HPUX-IF003.BIN |
| HP-UX Itanium |
5.2.0.3-P8CPE-HPUXI-IF003.BIN |
| Linux |
5.2.0.3-P8CPE-LINUX-IF003.BIN |
| Solaris |
5.2.0.3-P8CPE-SOL-IF003.BIN |
| Windows |
5.2.0.3-P8CPE-WIN-IF003.EXE |
| zLinux |
5.2.0.3-P8CPE-ZLINUX-IF003.BIN |
Complete the following procedure to install the Content Platform Engine server updates silently.
Operating system |
Command to install the Content Platform Engine server update |
|---|---|
| AIX |
5.2.0.3-P8CPE-AIX-IF003.BIN -f ce_silent_install.txt -i silent |
| HP-UX |
5.2.0.3-P8CPE-HPUX-IF003.BIN -f ce_silent_install.txt -i silent |
| HP-UX Itanium |
5.2.0.3-P8CPE-HPUXI-IF003.BIN -f ce_silent_install.txt -i silent |
| Linux |
5.2.0.3-P8CPE-LINUX-IF003.BIN -f ce_silent_install.txt -i silent
|
| Solaris |
5.2.0.3-P8CPE-SOL-IF003.BIN -f ce_silent_install.txt -i silent |
| Windows |
5.2.0.3-P8CPE-WIN-IF003.EXE -f ce_silent_install.txt -i silent
TIP You can use the Windows Task Manager to monitor completion of this interim fix server update installation on Windows based systems. |
| zLinux |
5.2.0.3-P8CE-ZLINUX-IF003.BIN -f ce_silent_install.txt -i silent |
Installation errors are recorded in the ce_install_log_5_2_0_3.txt file, which is in the ce_install_path directory (normally under ../IBM/FileNet/ContentEngine).
Record the Content Platform Engine build number from the ce_version.txt file, which is in the ce_install_path directory.
You use this build number later in the installation process to confirm the deployment of the updated Content Platform Engine.
The Content Platform Engine installation program places the updated file (FileNet.API.dll) into the "installation_location\ContentEngine" directory.
The remainder of this server update section applies only if you selected to install the Content Platform Engine server. Otherwise, you can skip to the section, Installing the client updates.
After you install the Content Platform Engine server software, configure it by using the steps in this section:
Determining the documentation to use for the remaining post-installation tasks
Removing a deployed Content Platform Engine
Removing the application server cache directories
Clearing the Internet browser cache on ACCE clients
Completing Configuration Manager tasks
The documentation that you use to configure and deploy Content Platform Engine depends upon the installation scenario
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.
jboss_install_directory\server\default\deploy
jboss_install_directory\server\custom_name\deploy
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
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
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.
You can bootstrap and deploy Content Platform Engine either interactively or by using the command line. Choose one of the following links to complete the Configuration Manager tasks in this section.
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 update or verify the Content Platform Engine bootstrap information.
(Multiple non-managed stand-alone application servers only) Copy the bootstrapped Content Platform Engine EAR file into the profiles directory (where 5.2.0.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.
Deployment of the Content Platform Engine server update is now complete. Continue with Restarting the application server.
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 | 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 | Indicates the server for which the upgrade profile is being created. Run the configmgr_cl listServers command to display 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\ce_was_tiv_db2\ce_was_tiv_db2.cfg". |
| -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. Requires -silent. |
| -help | When -help is specified, a brief message describing the command syntax displays; the command does not run. |
<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 on the node. </description>
<displayName>Application server profile directory</displayName>
</property>
configmgr_cl storepasswords -profile myprofile
Repeat steps 5 and 6 as needed to edit the application server properties for each Content Platform Engine instance directory that was created.
configmgr_cl generateconfig -appserver app_server_type -task task_type -license license_type -profile upgrade_profile_name
Where the following parameters apply:
Restriction: If the license type value contains embedded blanks, you must delimit the value by adding double quotes (").
The upgrade_profile_name is your upgrade profile name.
Specify the fully qualified path to the profile directory if it is not in the default directory: \ContentEngine\tools\configure\profiles.
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 will be 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 running application always has the correct licensing information:
configmgr_cl execute [-task task_type | -taskfile task_file_name ] -profile upgrade_profile_name [-silent] [-force] [-help]
Where the following parameters apply:
configmgr_cl generateConfig -task configurebootstrap -profile myprofile -bootstrap upgrade -appserver appserver_type
The bootstrap information is stored in the configurebootstrap.xml and the deployapplication.xml files. Each time the bootstrap information is generated, the system saves a unique version of the file. The initial file name is configurebootstrap.xml; subsequent file names are configurebootstrap.n.xml where "n" starts with 1 and represents the version number of each file.
configmgr_cl execute -task configurebootstrap -profile myprofile
Status messages display in the console.
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
ce_install_path\tools\configure\profiles\myprofile\ear
The location you select 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.
configmgr_cl execute -task deployapplication -profile myprofile
configmgr_cl checkstatus -task deployapplication -profile myprofile
Deployment of the Content Platform Engine server update is now complete. Continue with the next section, Restarting the application server.
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.
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:
When you deploy the upgraded Content Platform Engine application on the web application server and start the application, the existing Content Platform Engine data upgrade begins. You can check the progress on the upgrade to confirm that the upgrade was successful. Complete the following steps to check the status of the automatic data upgrade:
For more information on upgrades, see the IBM FileNet P8 Version 5.2 documentation for: Working with Configuration Manager.
If your configuration uses Rendition Engine with Oracle RAC, complete the steps in this section, otherwise the interim fix installation is complete.
Publishing.OracleJDBCServiceFormat=true
The following table lists the possible location of the FileNet.properties file:
Application server |
Sample location of the FileNet.properties file |
|---|---|
| IBM WebSphere® application server |
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\FileNet.properties |
| Oracle WebLogic Server |
C:\bea\user_projects\domains\mydomain\FileNet.properties |
| JBoss Application Server |
C:\jboss\jboss-5.2.0_EAP\bin\FileNet.properties |
Important Because the publishing database connection is cached, you must restart the application server that is running Content Platform Engine after you update the parameter value of Publishing.OracleJDBCServiceFormat.
This completes the installation and configuration of the server upgrade part of this interim fix.
The following files are included in this interim fix:
Note: By following the client installation instructions below, these files will be installed on all clients that are supported by the client installer. These files are provided for clients not supported by the client installer.
You can install the client updates either interactively or silently. This section consists of the following steps:
After you have updated the Content Platform Engine servers and the Content Platform Engine-related .NET clients, 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).
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 your application depends on the legacy 3.5.x Content Java API, then follow the below instructions:
Installation errors are recorded in the ceclient_install_log_5_2_0_3.txt file, which is in the ceclient_install_path directory.
The installation and configuration of the client upgrade for this fix pack is complete.
Complete the following procedure to install the Content Platform Engine client updates silently.
Install this interim 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.0.3-P8CPE-CLIENT-AIX-IF003.BIN -i silent -f ceclient_silent_install.txt |
| HP-UX |
5.2.0.3-P8CPE-CLIENT-HPUX-IF003.BIN -i silent -f ceclient_silent_install.txt |
| HP-UX Itanium |
5.2.0.3-P8CPE-CLIENT-HPUXI-IF003.BIN -i silent -f ceclient_silent_install.txt |
| Linux |
5.2.0.3-P8CPE-CLIENT-LINUX-IF003.BIN -i silent -f ceclient_silent_install.txt |
| Solaris |
5.2.0.3-P8CPE-CLIENT-SOL-IF003.BIN -i silent -f ceclient_silent_install.txt |
| Windows |
5.2.0.3-P8CPE-CLIENT-WIN-IF003.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.0.3-P8CPE-CLIENT-ZLINUX-IF003.BIN -i silent -f ceclient_silent_install.txt |
Installation errors are recorded in the ceclient_install_log_5_2_0_3.txt file, which is in the ceclient_install_path directory.
The installation and configuration of the client upgrade for this fix pack is complete.
This interim fix does not have an uninstall option. To remove this interim fix, you must redeploy the backed up copy of your previously bootstrapped Content Platform Engine EAR file.
The following table lists the product fix for this interim fix.
APAR |
Description |
|---|---|
PJ41638 |
ACCE cannot change the Workflow properties on the advanced tab in non-English environments. The "all servers" link is missing. |
PJ41982 |
PSIRT 1422: Oracle OIT 8.4.1 Security Patch p17733168. See techdoc 1672337 |
PJ42059 |
Running a Workflow as a service, and waiting on it at another workflow, using Condition Identifier, gives assertion failure. |
PJ42089 |
|
PJ42093 |
Pinging is not working if the event logging for the Process Engine region is completely disabled. |
PJ42099 |
"This Fixed Content Device is not implemented" message when attempting to add FCD. |
PJ42128 |
IBM FileNet Process Engine parameter replacement in sendMailTemplate function of CE-Operations works only until $9 parameter. |
PJ42135 |
The contributor (submitter name) of a comment is not displayed correctly in the "Recent Updates" view on Connections 4.5.x |
PJ42136 |
Workplace XT throws exception while trying to display audit event info. |
PJ42154 |
No logged on session exists at FILENET.VW.API.VWSESSION.CHECKSESSION |
PJ42158 |
In some cases, creating a sub-folder can result in two File events being fired, when there should only be one. |
PJ42159 |
Content Engine Bulk Importer (CEBI) -CE switch is not working, always runs with default of 3 threads. |
PJ42161 |
Process Engine (PE) Exception: java.lang.ClassNotFoundException: filenet.pa.sql.DBInt in pesvr_trace.log |
PJ42163 |
Process Engine (PE) CE_Operations copy operation fails when source document is a case related document. |
PJ42180 |
Process Engine CE_Operations::setMultipleStringProperty throws Work Performer Exception: null error when the value of the property is empty. |
PJ42184 |
Attachment sent through a workflow using Process Engine CE_Operations sendMailAttachment or sendMailTemplateAttachment are either blank or result in "file appears to be damaged, corrupted, or is too large". |
PJ42191 |
Processing of Content Engine (CE) Events stopped due to unique key violation error. |
PJ42193 |
Content Search Services (CSS) indexing plain text document binary recognizer incorrectly setting document type causing the document to not be indexed. |
PJ42237 |
IBM Enterprise Records foreign object reference declaration error. See techdoc 1669418 |
PJ42239 |
Unable to create content when number of subscribed events exceeds the number of subscription cache entries. |
PJ42240 |
Content Engine enable database tracing causes failure to add a new case with an automatic start of task that simply assign a date of creation (F_CaseFolder.DateCreated) into a custom property of the case folder Process Engine error. |
PJ42241 |
Content Search Services (CSS) incorrectly indexing email attachments with Oracle OIT. |
PJ42248 |
Case Analyzer 5.2 is not able to process user without a display name. |
PJ42249 |
PSIRT 1486: Apache and Tomcat security. See techdoc 1672717 |
PJ42252 |
Reassign Object Store operation not prevented when associated with Workflow system isolated region. |
PJ42271 |
IBM Case Manager (ICM) Timeline visualizer should expose at least one Document Update event when filing a document into Case Folder. |
PJ42274 |
Content Search Services (CSS) text search error for an Object Store in a larger cluster of Content Platform Engine (CPE) servers. |
PJ42289 |
Persister processing non-persistent OVPs in security proxy propagation code causes FNRCD0003E: DB_BAD_DATATYPE: Bad data type: (null). |
PJ42324 |
MIME type values are truncated to 64 characters for Content Federation Services Image Services (CFS-IS) migrated documents. |
PJ42328 |
Activity Stream does not encode Chinese characters correctly in file names. |
PJ42331 |
Create wizard unable to display existing object names in Internet Explorer (IE) 10. |
PJ42339 |
Process Engine (PE) class loading constraint violated issue with axis.jar (org.apache.axis.MessageContext) due to missing jaxrpc.jar in ICM All-In-One Configurations - Process Orchestration and Simulation functionality impacted. |
PJ42358 |
PSIRT 1732: IBM SDK Java Technology Edition Quarterly April 2014 update. See techdoc, 1674132 |
PJ42359 |
PSIRT 1696: Apache Xalan-Java security. See techdoc 1674134 |
PJ42364 |
Intermittently unable to access ObjectStore. |
PJ42372 |
Case Analyzer (CA) store creation fails when using the Oracle 11.2.0.3 JDBC driver embedded with WebLogic 12.1.2. |
PJ42375 |
INSUBFOLDER search query is mistranslated by the Content Engine (CE) server. |
PJ42384 |
Process Engine (PE) WSRequest performance for version agnostic workflows. |
PJ42408 |
Process Engine (PE) Case History shows information on additional case properties instead of only the modified case properties. |
PJ42412 |
DB2 for zOS downgrades "SELECT for update with RS" lock on Queueitem table causing duplicate workflows to be launched |
PJ42425 |
Class path problem causes Content Search Services (CSS) Outside In Technology (OIT) filters to be installed in the wrong location with JBoss EAP 4.3. |
PJ42426 |
When a Content Engine (CE) object property is changed from any non-NULL to NULL value on the Case details page, the change is not saved/reflected on the Work Item list in-basket. |
PJ42436 |
PSIRT 1907 : ACCE Potential Cross Site Scripting (XSS) vulnerability. See techdoc 1679930 |
PJ42444 |
Process Engine (PE) CE_Operations Copy operation fails when document is inheriting permissions. |
PJ42450 |
Process Engine (PE) CE_Operations will only get the current or released version of a document passed as a VWAttachment; it ignores any specific version GUID. |
PJ42453 |
When a Process Engine (PE) workflow is added to a solution's global workflow collection, the roster name and required class values are not updated. |
PJ42478 |
Process Engine (PE) CE_Operations.searchForOne retrieving too many CE objects. |
PJ42505 |
Content Engine (CE) sweep framework policy handler objects are leaked at the end of a complete sweep pass. |
APAR |
Description |
|---|---|
PJ42268 |
PSIRT 1719: Apache Struts security. See techdoc 1674128 |
PJ42328 |
Activity stream does not encode file name non-English (UTF-8) characters correctly. |
APAR |
Description |
|---|---|
PJ42154 |
Process Engine (PE) REST throws No logged-on session exists even if a session is still active after 30 minutes IBM Case Manager 5.1.1.2 users must install 5.2.0.3-P8CPE-IF001. See techdoc 1668534 |
PJ42158 |
Content Engine (CE) sub-folder event subscriptions when creating a sub-folder can result in two File events being fired, when there should only be one. |
PJ42161 |
Process Engine (PE) Exception: java.lang.ClassNotFoundException: filenet.pa.sql.DBInt in pesvr_trace.log. |
PJ42179 |
Case Analyzer (CA) fails with error FNRCS0001E: SECURITY_ANONYMOUS_DISALLOWED: Access to Content Engine was not allowed because the request was made anonymously instead of by an authenticated user. The application server reported that the user was anonymous. |
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, FileNet, 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 |
|---|---|
| 28 August 2014 |
Initial release of this interim fix. |