IBM FileNet P8 Content Platform Engine 5.2.1.7-P8CPE-IF007 Interim Fix Readme
© Copyright IBM Corporation 2019.

Readme file for: IBM® FileNet® P8 Content Platform Engine
Update name: 5.2.1.7-P8CPE
Fix ID: 5.2.1.7-P8CPE-IF007
Publication date: 28 June 2019
Last modified date: 28 June 2019

Contents

About this interim fix
New in this Interim Fix
Prerequisites
Download location
Known problems, restrictions, and solutions
Installation
Preparing the server for installation
Installing this Interim Fix
Installing the Content Search Services (CSS) Client
Installing the Microsoft Redistributable files
Configuring the server after installation
Installing the client updates
Installing the Content Engine Bulk Importer (CEBI) updates
Installing the Deployment Manager updates
Removing the Interim Fix
Fix list (APARs)
Notices
Trademarks
Document change history

About this Interim Fix

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.

New in Interim Fix 5.2.1.7-P8CPE-IF007

The following items are included in interim fix 5.2.1.7-P8CPE-IF007:

New in Interim Fix 5.2.1.7-P8CPE-IF006

The following items are included in interim fix 5.2.1.7-P8CPE-IF006:

New in Interim Fix 5.2.1.7-P8CPE-IF005

The following items are included in interim fix 5.2.1.7-P8CPE-IF005:

New in Interim Fix 5.2.1.7-P8CPE-IF004

The following items are included in interim fix 5.2.1.7-P8CPE-IF004:

New in Interim Fix 5.2.1.7-P8CPE-IF003

The following items are included in interim fix 5.2.1.7-P8CPE-IF003:

New in Interim Fix 5.2.1.7-P8CPE-IF002

The following items are included in interim fix 5.2.1.7-P8CPE-IF002:

New in Interim Fix 5.2.1.7-P8CPE-IF001

The following items are included in interim fix 5.2.1.7-P8CPE-IF001:

Prerequisites

Note: There is no 5.2.1.1-P8CPE-FP001 release, just a 5.2.1.1-P8CaseFoundation-FP001 release for new licenses

This Fix Pack requires:


Download location

Click the following link to access the files for this interim fix update: Fix Central for Interim Fix 5.2.1.7-P8CPE-IF007. You need an IBM login and password to access this download location.

Known problems, restrictions, and solutions

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

Installation of this interim fix consists of the following tasks:


Preparing the server for installation

In environments where there is more than one Content Platform Engine server running in the P8 domain, the Content Platform Engine nodes can be set up in either a managed or non-managed configuration.

When you deploy Content Platform Engine in a "managed" application server environment, this Content Platform Engine interim fix is installed and configured on the administration server. The Configuration Manager uses the administration tools of the application server to deploy the Content Platform Engine EAR file to the managed servers. This is known as a "managed" deployment.

When you deploy Content Platform Engine in a "non-managed" application server environment, install and configure this Content Platform Engine interim fix on any Content Platform Engine server in the environment. After configuring the 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.

  1. Log on to the Content Platform Engine server as the user who is designated as the "cpe_install_user" user.
  2. Download this interim fix and extract its contents to a temporary location. For information, see Download location.
  3. Stop Content Platform Engine and all client applications, including, but not limited to:
  4. (Existing 5.2.1.x installations only) Back up all existing bootstrapped Engine-xx.ear files (where xx is the application server abbreviation), on the Content Platform Engine server.

    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.

Installing this interim Fix

Complete the following tasks to install this interim fix.

  1. Navigate to the temporary directory where you extracted the contents of this interim fix.

  2. Copy the updated version of the Engine-xx.ear file into the following directory. This directory is a staging location. You will not delete or overwrite the currently deployed Engine-xx.ear file.

    UNIX
    installation_location/FileNet/ContentEngine/lib

    Windows
    installation_location\ContentEngine\lib

  3. Copy the updated version of listener.jar to all locations Content Platform Engine uses it
  4. Copy the updated Java certificate files: Jace.jar, Jace_t.jar, javaapi.jar, javaapi_t.jar, pe3pt.jar, pe3pt_t.jar, peResources.jar, peResources_t.jar, pe.jar, pe_t..jar, eeapi.jar into the following directory

    UNIX
    installation_location/FileNet/ContentEngine/lib

    Windows
    installation_location\ContentEngine\lib


Installing the Process Engine (PE) Region Move tool

This interim fix includes the Process Engine Region Move tool file regmove.jar.
The regmove.jar is located in the root directory of the interim fix zip file.
For information about how to use the Region Move tool, see Tech Note 7036552


Installing the Content Search Services (CSS) Client

Only on systems where Content Search Services (CSS) indexing and searching is configured.

  1. Navigate to the temporary directory where you extracted the contents of this test fix.
  2. Copy the updated version of the CSSClientConfig.jar file into the following directories. These directories are staging locations which will be picked up by the bootstrap and redeploy of Engine-xx.ear.

    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\

  3. Change permission for CSSClientConfig.jar

    UNIX
    e.g.: chmod 777 CSSClientConfig.jar


Installing the Microsoft 2013 Redistributable files

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.

Note: If the Microsoft 2013 Redistributable files are currently installed, you do not need to re-install them.

    Windows

  1. Download Microsoft Visual C++ Redistributable 2013 Package for Visual Studio 2013 package vcredist_x64.exe.
  2. Install following Microsoft installation instructions.

Configuring the server after installation

Complete the following post-installation tasks to configure the affected servers after the installation of this interim fix.

Configuring the server after installation: Gathering Content Platform Engine information

Before you can deploy Content Platform Engine, you must gather information that is needed for the application server configuration profile and for start up and deployment of the Content Platform Engine EAR file.

  1. Navigate to the IBM FileNet P8 Knowledge Center at http://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ibm.p8toc.doc/welcome_p8.htm.
  2. Locate the Get Started section on the IBM FileNet P8 Platform Information Center Home page and select Using the installation and upgrade worksheet for instructions on using the worksheet.
  3. Open the Installation and Upgrade Worksheet by selecting Installation and Upgrade worksheet at the bottom of the page.
  4. Customize the worksheet by clicking Customize Worksheet on line 18 of the Instructions tab.

Configuring the server after installation: Removing a deployed Content Platform Engine

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.

IBM WebSphere Application Server

Use the administrative console to uninstall the "FileNetEngine" application. This action deletes the Engine-ws.ear file from IBM WebSphere Application Server.

Oracle WebLogic 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.

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

Configuring the server after installation: Removing the application server cache directories

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.

IBM WebSphere Application Server

  1. Stop all WebSphere application server nodes, including the Deployment Manager node if one exists.
  2. Remove the FileNetEngine directory where the application server cache data is stored. For example, the default Windows path for this directory is:

    C:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name\temp\node_name\server_name\FileNetEngine\

    profile_name
    Specifies the profile for Content Platform Engine
    node_name
    Specifies the name of the Content Platform Engine application server instance node
    server_name
    Specifies the name of the Content Platform Engine application server instance
  3. Restart all WebSphere nodes, including the Deployment Manager node if one exists.

Oracle WebLogic Server

  1. Stop the Oracle WebLogic Server.
  2. Remove the FileNetEngine and EJBCompilerCache directories, where the application server cache data is stored. For example, the default Windows paths for these WebLogic directories are:

    C:\bea\user_projects\domains\mydomain\servers\AdminServer\tmp\_WL_user\FileNetEngine

    C:\bea\user_projects\domains\mydomain\servers\AdminServer\cache\EJBCompilerCache

    mydomain
    Specifies the name of the Content Platform Engine application server instance.
  3. Restart Oracle WebLogic Server.

JBoss application server

  1. Stop the JBoss application server.
  2. Remove the following subfolders and files:
    jboss_install_directory
    Specifies the JBoss installation directory.
    custom_name
    Specifies the name of a user-defined directory.
  3. 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

  4. Do not restart JBoss until prompted to later in this readme. JBoss must not be running during the update process.

Configuring the server after installation: Clearing the Internet browser cache on ACCE clients

Clear the internet browser cache on all client computers that use Administration Console for Content Platform Engine (ACCE) for administering Content Platform Engine.

Firefox
Tools > Clear Recent History > Time range to clear: Everything. Make sure all items are checked under Details.
Internet Explorer
Internet Options > Browsing history > Delete... > Check all boxes. Delete.
Safari
History > Clear History... > Clear

Configuring the server after installation: Granting permissions to the Configuration Manager user

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.

  1. Log on to the Content Platform Engine server as the user who is designated as the cpe_install_user user.
  2. Grant all of the following permissions to the user who is designated as the config_mgr_user user.
  3. Grant Execute permission on the Configuration Manager executable so that the user who is designated as the config_mgr_user user can run the Configuration Manager.

    The executable name depends upon the interface that will be used to run the Configuration Manager:

    1. Grant Write permission on the directory where Configuration Manager stores the configuration XML files that are needed to deploy Content Platform Engine.
    2. Grant Write permission on the ce_install_path/tools/configure directory and all its files and subdirectories.

      Configuration Manager executable name by interface
      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
    3. 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.

  4. Log off of the Content Platform Engine server and log back in as the person who was designated as the config_mgr_user user.

Configuring the server after installation: Completing Configuration Manager tasks

Complete the tasks in this section to configure the server set-up information and to deploy Content Platform Engine.

Completing Configuration Manager tasks interactively

Completing Configuration Manager tasks using the command line

Configuring the server after installation: Completing Configuration Manager tasks interactively

Complete the following tasks in the order that is shown to set up and deploy the Content Platform Engine.

Configuring the server after installation:

Completing Configuration Manager tasks interactively: Starting the Configuration Manager

  1. Log on to the Content Platform Engine server as the "config_mgr_user" user.
  2. Start Configuration Manager by completing the procedure that is appropriate for the operating system.

    Windows

    Select Start > All Programs > IBM FileNet P8 Platform > FileNet Configuration Manager or run the following command: ce_install_path\tools\configure\configmgr.exe.

    UNIX

    Run the following command from the command line: ce_install_path/tools/configure/configmgr.

Completing Configuration Manager tasks interactively

Completing Configuration Manager tasks interactively: Choosing Licenses

Complete the following procedure to choose which licenses apply for your system.

  1. Choose File > Upgrade Profile (or click Create a profile from the upgrade installation icon).
  2. Enter your application server credentials.
  3. When the profile opens, ensure that, in the Configure Bootstrap and Text Extraction task in the Content Platform Engine Task View pane the Bootstrap operation property shows Upgrade.
  4. Right-click on the profile tree and choose Add New Task > Choose Licenses.
  5. Choose one of the following license types for your installed products:
  6. Click on the Save button.
  7. Click on the Run Task button

    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:

    1. Uninstall the FileNetEngine application from your application server.
    2. Run the "Configure Bootstrap and Text Extraction" task.
    3. Run the "Deploy Application" task.

Configuring the server after installation:

Completing Configuration Manager tasks interactively: Bootstrapping the Content Platform Engine

Complete the following procedure to enter, update, or verify the Content Platform Engine bootstrap information.

  1. Open the configuration profile if it is not already open. Right-click Configure Bootstrap and Text Extraction task in the Content Platform Engine Task View pane and select Edit Selected Task.
  2. In the Bootstrap operation field, select Upgrade.

    IMPORTANT The default value is Configure New, but you must change it to Upgrade.

  3. In the Bootstrapped EAR file location field, enter the fully qualified path to the currently bootstrapped Content Platform Engine EAR file.
  4. Select File > Save to save your changes.
  5. Right-click Configure Bootstrap and Text Extraction task in the Content Platform Engine Task View pane and select Run Task. This operation applies the bootstrap information to the updated Content Platform Engine EAR file that is provided by the interim fix. This operation can take a few minutes. Task execution status messages display in the Console pane below the bootstrap properties.

Configuring the server after installation:

Completing Configuration Manager tasks interactively: Copying the bootstrapped Content Platform Engine EAR file to the remaining application servers

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

Configuring the server after installation:

Completing Configuration Manager tasks interactively: Modifying deployment information

Complete the following procedure to enter, update, or verify deployment information.

  1. Open the configuration profile if it is not already open.

    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.

  2. Right-click Deploy Application in the Content Platform Engine Task View pane and select Edit Selected Task.
  3. Enter, update, or verify the following information according to the application server:

    Content Platform Engine deployment parameters for WebSphere Application Server
    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.

    Content Platform Engine deployment parameters for JBoss Application Server
    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.

    Content Platform Engine deployment parameters for Oracle WebLogic Server
    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.

  4. If you made any changes, select File > Save.

Configuring the server after installation:

Completing Configuration Manager tasks interactively: Deploying Content Platform Engine

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.

Configuring the server after installation:

Completing Configuration Manager tasks interactively: Restarting the application server

Stop and start the application server, as follows:

WebSphere and WebLogic

Stop and restart all servers and clusters where the Content Platform Engine EAR file has been deployed.

JBoss

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.

Configuring the server after installation:

Entering setup information, bootstrapping, and deploying Content Platform Engine from the command line

Complete the following procedure to specify setup information and deploy Content Platform Engine.

  1. Log on to the Content Platform Engine server as the user who is designated as the config_mgr_user user.
  2. Change the current directory to ce_install_path/tools/configure, where ce_install_path is the path where you installed Content Platform Engine. For example, ce_install_path might be /opt/FileNet/ContentEngine.
  3. Run the configmgr_cl listServers command to display a list of valid server name values before you run the generateupgrade command.

    configmgr_cl listServers

  4. Run the generateupgrade command to generate the configuration profile. Enter the command on one line without line breaks.

    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:

    Command line configuration profile 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.

    1. Select one of the following values: Standard, Cluster, or Netdeploy (network deployment).
    2. Specify Standard if you are deploying Content Platform Engine to a standalone WebSphere Application Server, Oracle WebLogic Server, or JBoss Application Server.
    3. Specify Cluster if you are deploying Content Platform Engine to a WebSphere Application Server, Oracle WebLogic Server, or JBoss Application Server cluster.
    4. Specify Netdeploy if you are deploying Content Platform Engine to a managed WebSphere Application Server instance. That is, you are using Network Deployment to manage individual servers that are not necessarily in a cluster.
    -profile myprofile
    The myprofile value can be one of the following items:
    • The name of the profile, such as cpe_was_tiv_db2. The profile must be located in the ce_install_path/tools/configure/profiles directory, where ce_install_path is the location where the Content Platform Engine software is installed.
    • The absolute path to the profile directory, such as "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\cpe_was_tiv_db2" or opt/IBM/FileNet/ContentEngine/tools/configure/profiles/cpe_was_tiv_db2.
    • The absolute path to the profile input file, such as "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\cpe_was_tiv_db2\cpe_was_tiv_db2.cfgp" or opt/IBM/FileNet/ContentEngine/tools/configure/profiles/cpe_was_tiv_db2/cpe_was_tiv_db2.cfgp.

    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.
  5. (IBM WebSphere Application Server and Oracle WebLogic Server only) Set the application server administrator properties:
    1. Navigate to the myprofile/mycontent_engine_instance directory.
    2. Open the applicationserver.xml file in a text editor.
    3. Set the value for the ApplicationServerAdminUsername property:

      <propertyname="ApplicationServerAdminUsername">

      <value>administrator_user_name</value>

      </property>

    4. (IBM WebSphere Application Server only) Verify the values for the following properties. If these properties do not exist, add them and set the values according to your environment.

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

    5. Save your changes and close the file.
  6. (Optional) Run the storepasswords command, which prompts you (respond with yes or no) to encrypt and store the web application server administrator password to the applicationserver.xml file. If you do not need to encrypt the application server administrator password, edit the applicationserver.xml file and enter the clear text of the password for the ApplicationServerAdminPassword 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.

  7. If a bootstrap task does not already exist, generate the bootstrap information by entering the following information at the command line prompt.

    configmgr_cl generateConfig -task configurebootstrap -profile myprofile -bootstrap upgrade -appserver appserver_type

    -appserver appserver_type
    Specifies the application server type. Valid values are: WebSphere, WebLogic, or JBoss.
    -profile myprofile
    Specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.

    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.

  8. Confirm that the bootstrap configuration file was properly generated for an upgrade.

    If this is the first time that the bootstrap information has been generated:

    1. Open the configurebootstrap.xml file and verify that you see the following XML tag and that it has the word "upgrade" in it.

      JBoss example: <configuration class="com.ibm.ecm.configmgr.product.ce.task.UpgradeJBBootstrap">

    2. If the XML tag value is correct, enter the following information at a command line prompt to update the EAR file with bootstrap information:

      configmgr_cl execute -task configurebootstrap -profile myprofile

      Status messages display in the console.

    3. If the XML tag value does not include the word "upgrade", return to step 7 and generate the bootstrap information again so that the next configurebootstrap.n.xml file indicates that it is for an upgrade.

    If the bootstrap information has been previously generated:

    1. Open the most current configurebootstrap.n.xml file and verify that you see the following XML tag and that it has the word "upgrade" in it.

      JBoss example: <configuration class="com.ibm.ecm.configmgr.product.ce.task.UpgradeJBBootstrap">

    2. If the XML tag value is correct, enter this command:

      configmgr_cl execute -task configurebootstrap -profile myprofile -taskfile configurebootstrap.2.xml

      Status messages display in the console.

    3. If the XML tag value does not include the word "upgrade", return to step 7 and generate the bootstrap information again so that the next configurebootstrap.n.xml file is properly configured with "upgrade."
    4. Check the completion status of the bootstrap task by running the checkStatus command that matches the bootstrap execute command that you just ran by entering the following command:

      configmgr_cl checkStatus -task configurebootstrap -profile myprofile -taskfile configurebootstrap.n.xml

    5. If only one task file exists, enter this command instead:

      configmgr_cl checkStatus -task configurebootstrap -profile myprofile

  9. (Multiple non-managed stand-alone application servers only) After you have configured the first application server up to this point, copy the newly updated Content Platform Engine EAR file into the Profiles directory on each of the remaining application servers. For example:
  10. ContentEngine\tools\configure\profiles\myprofile\ear

  11. 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.
  12. Edit the deployapplication.xml file and verify that the value of the BootstrappedContentEngineEar property is the same as the location of the Content Platform Engine bootstrapped EAR file.
  13. Run the following command to deploy Content Platform Engine:

    configmgr_cl execute -task deployapplication -profile myprofile

  14. Run the following command to check the completion status of Content Platform Engine deployment:

    configmgr_cl checkstatus -task deployapplication -profile myprofile

  15. Restart the application server, including any managed servers.

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.

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:

  1. Navigate to the following page:

    http://server:port/FileNet/Engine

    server
    Specifies the host name of the machine where Content Platform Engine is deployed.
    port
    Specifies the HTTP port used by the Web application server on the machine where Content Platform Engine is deployed.

    The defaults for the application server HTTP port number are as listed:

    • 9080 for WebSphere
    • 7001 for WebLogic
    • 8080 for JBoss
  2. Verify that the value in the Startup Message key for Content Platform Engine is the same as the Content Platform Engine build number from the version.txt file, which is located in the temporary directory where you extracted the contents of this interim fix.
  3. Verify the INSO Version in the Startup Message key is 8.5.3.p28760615

Installing the client updates

You can install the client update either interactively or silently. This section consists of the following steps:


Installing the Content Platform Engine client update on Content Platform Engine-related Java EE applications interactively

After you have updated the Content Platform Engine servers complete the following tasks for all of the Content Platform Engine-related Java EE applications, 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).

  1. Back up the existing Content Platform Engine client directories.
  2. Download the appropriate client update file from the latest generally available fix pack and extract its contents to a temporary location.
  3. The following table lists the names of the compressed fix client update files by operating system type:

    Name of compressed Content Platform Engine client update file by operating system type
    Operating system type
    Name of compressed Content Platform Engine client update file
    AIX
    5.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
  4. Complete the following instructions as appropriate for the client installation:
  5. 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.

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

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

  7. Restart the applications that use the Content Platform Engine client.

The installation and configuration of the client upgrade for this interim fix is complete.


Installing the Content Platform Engine client updates silently

Complete the following procedure to install the Content Platform Engine client updates silently.

  1. Log on as a user with permissions to install software.
  2. Stop all custom applications that use the Content Platform Engine client.
  3. Back up the existing Content Platform Engine client directories.
  4. Download the appropriate client update file from the latest generally available fix pack and extract its contents to a temporary location.
  5. The following table lists the names of the compressed fix client update files by operating system type:

    Name of compressed Content Platform Engine client update file by operating system type
    Operating system type
    Name of compressed Content Platform Engine client update file
    AIX
    5.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
  6. Open the ceclient_silent_install.txt file and edit the file as appropriate for your configuration, including the following fields and other fields that apply to your system.
  7. Install this fix by running the following command that is appropriate for your operating system.

    Silent installation start commands by operating system for the Content Platform Engine client update
    Operating system
    Command to install the Content Platform Engine server update
    AIX
    5.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

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

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

  9. Restart the custom applications that use the Content Platform Engine client.

The installation and configuration of the client upgrade for this interim fix is complete.


Installing the Content Engine Bulk Importer (CEBI) updates

This interim fix updates the bulkimport.jar file.

Complete the following procedure to update Content Engine Bulk Importer.

  1. After downloading the interim fix and extracting its contents to a temporary location (in step 2 under Preparing the server for installation ), the updated bulkimport.jar should be in the temporary location.
  2. Log on to Content Platform Engine with a user account that has the appropriate permissions to create folders and install files.
  3. If running, stop Content Engine Bulk Import (CEBI).
  4. Make a backup of the existing bulkimport.jar file.

    CE_home/tools/CEBI/bulkimport.jar

  5. Copy the new bulkimport.jar file from the temporary location to the default directory.

    CE_home/tools/CEBI/

  6. Restart Content Engine Bulk Import (CEBI) if needed.

Installing the Deployment Manager updates

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, and replaces the org.apache.log4j_1.2.13 folder with an org.apache.log4j_1.2.17.jar file.

Complete the following procedure to update Deployment Manager.

  1. After downloading the interim fix and extracting its contents to a temporary location (in step 2 under Preparing the server for installation ), the updated 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, listener.jar and org.apache.log4j_1.2.17.jar files should be in the temporary location.
  2. Back up the existing copy of 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, and the org.apache.log4j_1.2.13 folder which are located in the following directories:

    Linux

    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/

    Windows

    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\

  3. Copy the updated versions of 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 that were extracted from the fix (see step 1) into the same directory as the existing copy that you just backed up. (This action overwrites the existing copy.) Remove the org.apache.log4j_1.2.13 folder and its contents, then copy the org.apache.log4j_1.2.17.jar file into the location where that folder was (within the plugins folder).
  4. If you have previously executed Deployment Manager from this installation directory, the old files have been cached. To remove the old cache from your system, go to:

    Linux

    cpe_installation_directory/IBM/FileNet/ContentEngine/tools/deploy

    Windows

    cpe_installation_directory\IBM\FileNet\ContentEngine\tools\deploy

    and run the following command:

    Linux

    DeploymentManager -clean

    Windows

    DeploymentManager.exe -clean

Removing the interim fix

This interim fix does not have an uninstall option.

Fix list (APARs)

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

5.2.1.7-P8CPE-IF007 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, 5.2.1.7-P8CPE-ALL-LA008, 5.2.1.7-P8CPE-IF001, 5.2.1.7-P8CPE-IF002, 5.2.1.7-P8CPE-IF003, 5.2.1.7-P8CPE-IF004, 5.2.1.7-P8CPE-ALL-LA015 and 5.2.1.7-P8CPE-IF005)
APAR
Description
PJ45477
Oracle Outside In Technology (OIT) v8.5.3 indexing errors with some older 1997-2003 Microsoft Word documents. See technote 2015948.
PJ45748
PSIRT 16012: (CVE-2019-2705, CVE-2019-2608, CVE-2019-2609, CVE-2019-2610, CVE-2019-2611, CVE-2019-2612, CVE-2019-2613): Open Source Oracle Outside In Technology Vulnerabilities - April 2019. See security bulletin 0883190
PJ45752
Administrative Console for Content Platform Engine (ACCE) Error when trying to view Update Event information if the associated document has been deleted.
PJ45767
Disabling an auditing policy does not halt the audit disposition deletion sweep from occurring.
PJ45771
eDM CBR query continuation issue with Content Search Services (CSS) first queries resulting in odd results.
PJ45757
Policy based sweep with multiple policies throws E_BAD_CLASSID exception.

5.2.1.7-P8CPE-IF006 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, 5.2.1.7-P8CPE-ALL-LA008, 5.2.1.7-P8CPE-IF001, 5.2.1.7-P8CPE-IF002, 5.2.1.7-P8CPE-IF003, 5.2.1.7-P8CPE-IF004, 5.2.1.7-P8CPE-ALL-LA015 and 5.2.1.7-P8CPE-IF005)
APAR
Description
PJ45561
peverify does not (re-)create sequence/identity table "VWUniqueIdX" correctly in MSSQL.
PJ45584
Administrative Console for Content Platform Engine (ACCE) Login takes too long, trying to make redundant Server calls.
PJ45599
Administrative Console for Content Platform Engine (ACCE) AllowRetentionReduction property is not updated correctly.
PJ45661
FileNet Deployment Manager (FDM) ObjectStore halfmap retrieval from workflow definition retrieves two entries instead of one.
PJ45662
Content Platform Engine (CPE) potential XML External Entity (XXE) vulnerability. See security bulletin 2015943
PJ45668
Unable to process work objects using a Sweep due to "Subtransactions not supported" error.
PJ45682
FileNet Process Engine won't start - potential deadlock condition on startup.
PJ45689
Content Platform Engine (CPE) HealthCheck servlet shows all red when accessed through a load balancer.

5.2.1.7-P8CPE-IF005 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, 5.2.1.7-P8CPE-ALL-LA008, 5.2.1.7-P8CPE-IF001, 5.2.1.7-P8CPE-IF002, 5.2.1.7-P8CPE-IF003, 5.2.1.7-P8CPE-IF004 and 5.2.1.7-P8CPE-ALL-LA015)
APAR
Description
PJ43434
The event action that launches workflows fails when the event that triggered it was raised by a background service.
PJ45025
Administrative Console for Content Platform Engine (ACCE) cannot assign two Inbaskets with the same name from two different Queues for Application Space.
PJ45339
Unnecessary ibm-entryuuid=null LDAP queries are issued.
PJ45423
Remove JavaMail mailapi.jar from Process Engine (PE).
PJ45425
LDAP Directory configuration clash of user email addresses in one directory with UPN (short name) of users in the other causes our caching to go astray.
PJ45438
NullPointerException occurs when running a sweep where some of the resulting string values are null and the "Allow string truncation" option is checked.
PJ45503
Administrative Console for Content Platform Engine (ACCE) does not allow properties to be set to null.
PJ45508
Cannot take ownership of documents in Administrative Console for Content Platform Engine (ACCE).
PJ45523
Enhancement: Failed expansion of group members in ADAM where a group has more than 1500 direct members.
PJ45524
Saved Searches in Administrative Console for Content Platform Engine (ACCE) when run with Bulk Actions script do not work in specific case.
PJ45534
PSIRT 13565 (CVE-2018-11797): Apache PDFBox vulnerabilities. See security bulletin 0734711
PJ45557
Add JVM argument to skip the sidHistory lookup when there is a miss on "objectSID" (for customers with many child domains).
PJ45576
Administrative Console for Content Platform Engine (ACCE) provide Spinny for localize choice lists/Class Definitions.
PJ45600
Adding a choice item to a choice list in Administrative Console for Content Platform Engine (ACCE) that has more than 100 entries fails.
PJ45603
Receiving WCMApiConfig.properties file not found / logon prompt when attempting to access Process Designer through Content Navigator.
PJ45614
Enhancement: Process Engine (PE) REST: Simplify algorithm to figure out CEURI for PE REST Servlet.
PJ45620
Unable to associate an Integer choicelist to an Integer property in Administrative Console for Content Platform Engine (ACCE).
PJ45624
FileNet Deployment Manager (FDM) Date Last Modified is updated for existing classes when using "Use original create/update timestamps and users" option.
PJ45627
Workflow error with generated large user SID.

5.2.1.7-P8CPE-ALL-LA015
APAR
Description
PJ45551
PSIRT 13727 (CVE-2018-3217, -3218, -3219, -3220, -3221, -3302, -3222, -3223, -3224, -3225, -3226, -3227, -3228, -3229, -3230, -3231, -3232, -3233, -3234, -18223, -18224, -3147): Open Source Oracle Outside In Technology Vulnerabilities - October 2018. See security bulletin 0736035

5.2.1.7-P8CPE-IF004 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, 5.2.1.7-P8CPE-ALL-LA008, 5.2.1.7-P8CPE-IF001, 5.2.1.7-P8CPE-IF002, and 5.2.1.7-P8CPE-IF003)
APAR
Description
PJ43927
In Administrative Console for Content Platform Engine (ACCE) the past audit history is displaying the latest change that was made instead of the change made on that audit event.
PJ44970
Process Engine (PE) enhancement: NoClassDefFoundError errors when creating component queue through Administrative Console for Content Platform Engine (ACCE).
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).
PJ45146
PSIRT 12005 (CVE-2018-1844): External DTD vulnerability with FileNet Deployment Manager. See security bulletin 0732755
PJ45326
Administrative Console for Content Platform Engine (ACCE) does not save Property definitions on properties tab.
PJ45376
Process Engine (PE) Region Move tool cannot handle special columns in indexes in Oracle, Message = ORA-00904: "SYS_NC00062$": invalid identifier.
PJ45380
When importing methods for Component Manager in Administrative Console for Content Platform Engine (ACCE), the method list and classname areas are not scrollable.
PJ45406
Administrative Console for Content Platform Engine (ACCE) displays multiple status pop-ups for one bulk script.
PJ45429
PSIRT 11709 (CVE-2012-5783): HttpClient security vulnerability. See security bulletin 0731533
PJ45440
PSIRT 12599 (CVE-2018-8036): Apache PDFBox vulnerabilities. See security bulletin 0716315
PJ45444
Process Engine (PE) Null pointer exception during expression evaluation using xmlstringexpr function.
PJ45445
Process Engine (PE) WSRequest invoke timeout causing by 60 seconds hard-coded.
PJ45447
Content Engine Bulk Import (CEBI) CEBI_Maint does not delete transact.dat files and files referenced in transact.dat.
PJ45453
Administrative Console for Content Platform Engine (ACCE) hangs while assigning a large number of storage areas to a storage policy.
PJ45460
PPSIRT 12766 (CVE-2018-2992, CVE-2018-3093, CVE-2018-3094, CVE-2018-3095, CVE-2018-3096, CVE-2018-3097, CVE-2018-3009, CVE-2018-3010, CVE-2018-3092, CVE-2018-3098, CVE-2018-3099, CVE-2018-3102, CVE-2018-3103, CVE-2018-3104): Open Source Oracle Outside In Technology Vulnerabilities - July 2018. See security bulletin 0718295
PJ45462
Invalid date does not error out of bulk content move job.
PJ45472
Enhancement: Object Search Save is not working when Administrative Console for Content Platform Engine (ACCE) Plugin is disabled on default desktop and enabled on non-default desktop.
PJ45481
Component queues are not imported via FileNet Deployment Manager (FDM) on Linux.

5.2.1.7-P8CPE-IF003 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, 5.2.1.7-P8CPE-ALL-LA008, 5.2.1.7-P8CPE-IF001, and 5.2.1.7-P8CPE-IF002)
APAR
Description
PJ44047
Choice lists in Administrative Console for Content Platform Engine (ACCE) take a long time to load if they have a large number of choices.
PJ44754
Cannot create index jobs for documents with titles longer than 64 characters.
PJ44881
Administrative Console for Content Platform Engine (ACCE) errors in script not reported when running Saved Searches.
PJ44884
Administrative Console for Content Platform Engine (ACCE) Workflow search cannot override Workflow lock.
PJ44899
Install add-on wizard in Administrative Console for Content Platform Engine (ACCE) should only allow current version add-ons to be installed.
PJ44923
Encrypted database password visible in response in Administrative Console for Content Platform Engine (ACCE).
PJ44928
Administrative Console for Content Platform Engine (ACCE) Client API download node is missing via load balanced URL.
PJ44975
Enhancement: Add Process Engine (PE) WSRequest queue's polling interval and batch size.
PJ45024
Administrative Console for Content Platform Engine (ACCE) default instance security FULL_CONTROL on Sweep Action doesn't include Link permission.
PJ45026
Administrative Console for Content Platform Engine (ACCE) wrongly says that Audit Definition -> Filter Expression applies to GetContentEvent.
PJ45033
Enhancement: Administrative Console for Content Platform Engine (ACCE) not able to insert a choice item into the middle of the choice item list.
PJ45036
Administrative Console for Content Platform Engine (ACCE) unexpected error message: 'FNRCE0002E: E_BAD_CLASSID: Class "CmHadoopStorageDevice" not found.'.
PJ45039
Administrative Console for Content Platform Engine (ACCE) Security Script Wizard updates the security on subfolders.
PJ45127
Administrative Console for Content Platform Engine (ACCE) does not save marking set on first try.
PJ45207
Administrative Console for Content Platform Engine (ACCE) setting DefaultInstanceOwner of Sub class of root document class to null gives Error.
PJ45208
Administrative Console for Content Platform Engine (ACCE) cannot save workflows to a file.
PJ45225
Administrative Console for Content Platform Engine (ACCE) not setting correct containment name when re-filing a document.
PJ45237
Administrative Console for Content Platform Engine (ACCE) search for custom properties on all Document classes.
PJ45339
Content Engine (CE) server Unnecessary ibm-entryuuid=null LDAP queries are issued.

5.2.1.7-P8CPE-IF002 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, 5.2.1.7-P8CPE-ALL-LA008, and 5.2.1.7-P8CPE-IF001)
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

5.2.1.7-P8CPE-IF001 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, 5.2.1.7-P8CPE-ALL-LA007, and 5.2.1.7-P8CPE-ALL-LA008)
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 add-on 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.

5.2.1.7-P8CPE-ALL-LA008 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, 5.2.1.7-P8CPE-ALL-LA006, and 5.2.1.7-P8CPE-ALL-LA007, and replaces 5.2.1.7-P8CPE-ALL-LA007)
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.

5.2.1.7-P8CPE-ALL-LA007 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, and 5.2.1.7-P8CPE-ALL-LA006, and replaces 5.2.1.7-P8CPE-ALL-LA005)
APAR
Description
PJ45011
FileNet Deployment Manager (FDM) resets a source required class back to the default class during export.

5.2.1.7-P8CPE-ALL-LA006 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003, 5.2.1.7-P8CPE-ALL-LA004, and replaces 5.2.1.7-P8CPE-ALL-LA005)
APAR
Description
PJ44544
Content Federated Services - Image Services (CFS-IS) Connection Timed Out exception corrupts SSI handle.
5.2.1.7-P8CPE-ALL-LA004 (which includes 5.2.1.7-P8CPE-ALL-LA002, 5.2.1.7-P8CPE-ALL-LA003)
APAR
Description
PJ44856
Dashboard PCH process prevents WebSphere JVM from shutting down.

5.2.1.7-P8CPE-ALL-LA003 (which includes 5.2.1.7-P8CPE-ALL-LA002)
APAR
Description
PJ44912
Content Federated Services - Image Services (CFS-IS) cannot federate documents that contain Daeja 5.0 annotations.

5.2.1.7-P8CPE-ALL-LA002
APAR
Description
PJ44901
Intermittent Isilon device session absolute timeout.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
J74/G4
555 Bailey Avenue
San Jose, CA 95141
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.

Document change history


Date
Description
28 June 2019
Initial release of this interim fix.