IBM FileNet P8 Content Engine 5.1.0.4-P8CE-FP004 fix pack readme
© Copyright IBM Corporation 2011, 2013.

Readme file for: IBM® FileNet® P8 Content Engine
Update name: 5.1.0.4
Fix ID: 5.1.0.4-P8CE-FP004
Publication date: 01 November 2013
Last modified date: 01 November 2013

Contents

About this fix pack

Server update

Client update

Content Search update

Prerequisites

Known problems, restrictions, and solutions

Downloading this fix pack

Installing and configuring this fix pack

Installing and configuring the server updates

Installing the client updates

Removing this fix pack

Fix pack contents (APARs)

Notices

Trademarks

Document change history

About this fix pack

This fix pack consists of two parts: a server update for Content Engine and a client update for Content Engine-related applications. The Content Engine server update includes a Content Search update.

Server update

The server update automatically completes the following tasks:

• Installs modified Content Engine files for any of the following Content Engine scenarios:
  • An existing installation of Content Engine 5.1.0.0, 5.1.0.0 IF1, 5.1.0.0 IF2, 5.1.0.0 IF3, 5.1.0.0 IF4, 5.1.0.1 FP1, 5.1.0.2 FP2, or 5.1.0.3 FP3
  • A new installation of Content Engine 5.1.0.0
  • An upgrade to Content Engine 5.1.0.0 from the prior Content Engine releases (3.5.2, 4.0.1, 4.5.0, 4.5.1, or 5.0.0)
• Installs the necessary new or modified files for Configuration Manager.

In Windows environments, the server update also provides selectable options that install new or modified files for FileNet Enterprise Manager and FileNet Deployment Manager.

In AIX environments, the server update also provides Centera SDK 3.3.721 libraries for supporting Content Engine on AIX 7.1 with Centera Storage.

Client update

The client update installs modified Content Engine client files for Content Engine-related Java EE applications, such as FileNet Application Engine, IBM FileNet Workplace XT, IBM FileNet Process Engine, IBM FileNet Process Analyzer, and IBM Enterprise Records.

Content Search update

Content Engine 5.1.0.4-P8CE-FP004 supports both Legacy Content Search Engine and Content Search Services.

The Legacy Content Search Engine client is built into the Content Engine 5.1.0.4-P8CE-FP004 Engine-xx.ear and does not need to be updated as part of this fix pack installation. Therefore, do not run the Legacy Content Search Engine client updater tool. Running the updater tool erases the Content Search Services client and INSO updates.

Beginning with 5.1.0.4-P8CE-FP004, you are not required to run the CSSClientTool.bat (Windows) or CSSClientTool.sh (Linux/Unix) to update the Engine-xx.ear with the CSS client and INSO (OIT) files. The "Bootstrap and Text Extraction" step in the Configuration Manager updates the Engine-xx.ear with the Content Search Services client and INSO (OIT) files.

Prerequisites

This fix pack must be installed on top of either 5.1.0.0-P8CE, 5.1.0.0-P8CE-IF00x (where x represents Interim Fixes 1, 2, 3, or 4), 5.1.0.1-P8CE-FP001, 5.1.0.2-P8CE-FP002 or 5.1.0.3-P8CE-FP003

• See the FileNet P8 5.1 Fix Pack Compatibility Matrix for the compatibility of other IBM FileNet P8 products with this fix pack.

Known problems, restrictions, and solutions

Following are some known problems and restrictions that are related to this fix pack:

• A Fixed Content Device migration issue that occurs in fix pack 5.1.0.1-P8CE-FP001 and that can create problems in low disk space conditions is fixed in 5.1.0.2-P8CE-FP002 and later fix packs. All customers who are now using a Fixed Content Device configuration with 5.1.0.1-P8CE-FP001 should install fix pack 5.1.0.2-P8CE-FP002, 5.1.0.3-P8CE-FP003 or 5.1.0.4-P8CE-FP004. For more information, see Flash Alert 1613523 at: http://www.ibm.com/support/docview.wss?uid=swg21613523.
• This fix pack resolves a security issue on Content Engine. For more information, see the security vulnerability technote 1608749 at: http://www.ibm.com/support/docview.wss?uid=swg21608749.
• This fix pack does not have an uninstall option; be sure to back up Content Engine before installing this fix pack, in the event you need to roll back to your existing release level. For more information, see the Backing up and restoring IBM FileNet P8 components section in the IBM FileNet P8 Platform 5.1 Information Center.
• You can safely install this fix pack even if you have virus protection software that is running in the background.
• You cannot run the Graphical User Interface (GUI) version of the Configuration Manager 5.1 tool for this fix pack on the HP-UX PA-RISC or HP Integrity servers. Use the command line version of the Configuration Manager instead.
• For Linux, Content Search Services 5.1 supports 64-bit INSO only. The 32-bit INSO for Linux (Redhat or SUSE) is not supported.
• Customers using Process Engine (PE) should apply 5.0.0.6-P8PE-IF002 or higher before upgrading to 5.1.0.4-P8CE-FP004. See techdoc 1671531

Downloading this fix pack

Click the following link to access the files for this fix pack server update: Fix Central for fix pack 5.1.0.4-P8CE-FP004.

Server update files

The following table lists the names of the compressed fix pack server update files by operating system type:

Client update files

The following table lists the names of the compressed fix pack client update files by operating system type:

Installing and configuring this fix pack

Installing and configuring the server updates

This section consists of two parts: installing the Content Engine 5.1.0.4-P8CE-FP004 files, followed by configuring the Content Engine.

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

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

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

Preparing the Content Engine server for installation

Complete the following tasks to prepare the Content Engine server for this fix pack.

Downloading this fix pack server update

Complete the following tasks to install this fix pack.

1. Log on as the "ce_install_user" user.
2. Stop Content Engine and all client applications, including, but not limited to:
   • Enterprise Manager
   • Configuration Manager
   • Deployment Manager
   • .NET client applications
3. Download the fix pack server update file that is appropriate for your operating system and extract its contents to a temporary location. For information, see Downloading this fix pack.
4. If you are installing only the .NET client or Tools components in the server update part of this fix pack, then skip step 5 and continue with Installing this fix pack on the Content Engine server.
5. (Existing 5.1.0.x installations only) Back up all existing bootstrapped Engine-xx.ear files (where xx is the application server abbreviation), on the Content Engine server.

   Important Failure to make a backup of the existing bootstrapped Content Engine EAR file can have serious repercussions on the operation of Content Engine if you accidentally delete or overwrite the existing bootstrapped Content Engine EAR file during the installation of this fix pack. A common symptom of a deleted or an overwritten bootstrapped EAR file is that system users cannot log on to Content 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 Engine by viewing the contents of the Servers.xml file, which is in the ce_install_path directory.

Installing this fix pack on the Content Engine server

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

• Installing the Content Engine server updates interactively
• Installing the Content Engine server updates silently
• Completing the Content Engine server installation

Installing the Content Engine server updates interactively

Complete the following procedure to install the Content Engine server updates interactively.

1. Navigate to the temporary directory that you selected in Preparing the Content Engine server for installation, and install the server updates on Content Engine by running the installation program file that is appropriate for your operating system:

   Content Engine server update executable file name by operating system

   Operating system	Executable file name for the Content Engine server update
   AIX	5.1.0.4-P8CE-AIX-FP004.BIN
   HP-UX	5.1.0.4-P8CE-HPUX-FP004.BIN
   HP-UX Itanium	5.1.0.4-P8CE-HPUXI-FP004.BIN
   Linux	5.1.0.4-P8CE-LINUX-FP004.BIN
   Solaris	5.1.0.4-P8CE-SOL-FP004.BIN
   Windows	5.1.0.4-P8CE-WIN-FP004.EXE
   zLinux	5.1.0.4-P8CE-ZLINUX-FP004.BIN

   
   
2. From the Choose Components dialog box, select the components that you want to install.
   1. Select Content Engine Server to install the server updates, Configuration Manager and Content Engine Web Upgrade Tool.
   2. Windows only: Select .NET Client to update the Content Engine COM Compatibility Layer for Content Engine-related .NET applications. You must enter a valid URL in the Specify CE URL for COM Compatibility Layer dialog box, in the following form: http://CEserver:http_port/wsi/FNCEWS40MTOM/. Leaving the URL blank prevents the required .DLLs from being copied.
   3. Windows only: Select FileNet Enterprise Manager to install updates to the FileNet Enterprise Manager.
   4. Select Tools to install updates to the Configuration Manager. On Windows systems, this also includes the Deployment Manager and the command line based Content Engine Web Upgrade Tool.
3. If you installed the Content Engine Server component, a dialog box prompts you to launch the Configuration Manager. Uncheck the Launch Configuration Manager check box and click Done.
4. Continue with Completing the Content Engine server installation.

Installing the Content Engine server updates silently

Complete the following procedure to install the Content Engine server updates silently.

1. Navigate to the temporary directory that you selected in Preparing the Content Engine server for installation.
2. Open the ce_silent_install.txt file and edit the CHOSEN_INSTALL_FEATURE_LIST as appropriate for your configuration.
• ContentEngineServer - Installs the server updates, Configuration Manager and Content Engine Web Upgrade Tool.
• DotNetClients - Updates the Content Engine COM Compatibility Layer for Content Engine-related .NET applications.
• FileNetEnterpriseManager - Updates FileNet Enterprise Manager.
• Tools - Updates the Configuration Manager. On Windows systems, this also updates the Deployment Manager, and the command line based Content Engine Web Upgrade Tool.
3. Set LAUNCH_CM to 0 (zero). This setting prevents Configuration Manager from launching after the silent installation is complete.
4. Read the license, and set LICENSE_ACCEPTED = true. This setting automatically accepts the end user license agreement. If LICENSE_ACCEPTED is not set to true, the installation program cannot continue.
5. Install this fix pack by running the following command that is appropriate for your operating system.

Completing the Content Engine server installation

1. Review the Content Engine log files for installation errors

   Installation errors are recorded in the ce_install_log_5_1_0_4.txt file, which is in the ce_install_path directory

2. Review the Content Engine version log file (ce_version.txt)

   Record the Content Engine build number from the ce_version.txt file, which is in the ce_install_path directory.

   You will use this build number later in the installation process to confirm the deployment of the updated Content Engine.

3. (Custom .NET applications only) This step applies if you installed only the .NET client component on a machine that is not the Content Engine server.
1. Stop the .NET application.
2. Activate the updated file (FileNet.API.dll) by placing it in the .NET application directory

   The Content Engine installation program places the updated file (FileNet.API.dll) into the "installation_location\ContentEngine" directory.

   TIP installation_location\ContentEngine is the Enterprise Manager application directory.

3. Restart the .NET application.

The remainder of this server update section applies if you selected to install only the Content Engine Server. Otherwise, you can skip to the section, Installing the client updates.

Configuring the Content Engine server after installation

After you install the Content Engine server software, configure it using the steps in this section:

Determining the documentation to use for the remaining post-installation tasks

Removing a deployed Content Engine

Removing the application server cache directories

Completing Configuration Manager tasks

Determining the documentation to use for the remaining post-installation tasks

The documentation that you use to configure and deploy Content Engine depends upon the installation scenario:

• If the FileNet P8 installation documentation prompted you to install this fix pack server update as part of a new installation of Content Engine 5.1.0 or as part of an upgrade to Content Engine 5.1.0 from either a 3.5.2, 4.0.1, 4.5.0, 4.5.1, or 5.0.0 system, return to the FileNet P8 5.1.0 installation documentation to continue with the instructions to configure and deploy Content Engine.
• If you are updating an existing Content Engine 5.1.0 system with the contents from this fix pack server update, continue with the remaining tasks.

Removing a deployed Content Engine

To help prevent errors when redeploying the updated version of Content Engine, remove the previously deployed copy of Content Engine from the application server before deploying the updated Content Engine. See the following topics for more information on specific application servers.

IBM WebSphere application server

Use the administrative console to uninstall the "FileNetEngine" enterprise 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

Removing the application server cache directories

To help prevent errors when redeploying the updated version of Content Engine, remove the application server cache as described in the following topics.

NETWORK NOTE If the Content Engine server uses a central Java EE application server (which might manage other application servers), remove the application server cache directories from only the central "managing" application server and not on any managed application servers. If Content Engine uses multiple non-managed, stand-alone application servers, remove the application server cache directories from all the application servers.

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\

   Where:

   • profile_name is the profile for Content Engine
   • node_name is the name of the Content Engine application server instance node
   • server_name is the name of the Content 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

   Where:

   • mydomain is the name of the Content Engine application server instance.
3. Restart Oracle WebLogic Server.

JBoss application server

1. Stop JBoss application server.
2. Remove the following sub-folders and files, where:
   • jboss_install_directory is the JBoss installation directory.
   • custom_name is the name of a user-defined directory.

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

3. Do not restart JBoss until specified later in this readme. JBoss must not be running during the update process.

Completing Configuration Manager tasks

You can bootstrap and deploy Content 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

Completing Configuration Manager tasks interactively

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

• Starting the Configuration Manager
• Bootstrapping the Content Engine
• Updating EMC Centera SDK library files in an AIX environment
• Configuring the Rendition Engine client
• Configuring the Process Engine client
• Copying the bootstrapped Content Engine EAR file to the remaining application servers
• Deploying Content Engine
• Restarting the application server

Starting the Configuration Manager

1. Log on to the Content 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.

Bootstrapping the Content Engine

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

1. Open your existing configuration profile (created when 5.1.0.0-P8CE was originally installed).
2. Right-click Configure Bootstrap Properties in the Content Engine Task View pane, and select Edit Selected Task.
3. In the Bootstrap operation field, select Upgrade.

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

4. In the Bootstrapped EAR file location field, verify the fully qualified path to the currently bootstrapped Content Engine EAR file.
5. Select File > Save.
6. Right-click Configure Bootstrap Properties in the Content Engine Task View pane, and select Run Task. This operation applies the bootstrap information to the updated Content Engine EAR file that is provided by this fix pack. This operation can take a few minutes. Task execution status messages display in the window below the bootstrap properties.

Updating EMC Centera SDK library files in an AIX environment

If your configuration uses Centera Storage, and your Content Engine runs in an AIX environment, complete the steps in this section; otherwise, continue with the Configuring the Rendition Engine client section.

1. Review the Centera Support and Protected Storage section in the Hardware and software requirements for IBM FileNet P8 Versions 5.1 for compatibility information.
2. On each Content Engine server that is running in an AIX environment, update EMC Centera SDK library files and reconfigure the environment variable. See the Installing or updating EMC Centera SDK library files section in the IBM FileNet P8 Platform 5.1 Information Center.

Configuring the Rendition Engine client

If your configuration uses Rendition Engine, complete the steps in this section, otherwise continue with the Configuring the Process Engine client section.

To complete this step, see the IBM FileNet 5.1.0.1-P8RE-FP001 fix pack readme, "Install Rendition Engine clients on Content Engine servers."

Configuring the Process Engine client

If your configuration uses Process Engine, complete the steps in this section, otherwise continue with the Configuring the Content Search Services client section.

This step updates the recently bootstrapped Engine-xx.ear file with the Process Engine client.

Locate the Process Engine client installation program that correlates with the version of your Process Engine server and follow the directions that are associated with that version of the Process Engine client.

Tip Run the Process Engine installation program only once on the Content Engine server because the Process Engine client installation program detects all EAR files and updates them all at one time.

Copying the bootstrapped Content Engine EAR file to the remaining application servers

(Multiple non-managed stand-alone application servers only) Copy the bootstrapped Content Engine EAR file into the profiles directory (where 5.1.0.0-P8CE was originally bootstrapped) on each of the remaining Content 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 Engine EAR file is referred to as the "bootstrapped EAR path." You must enter this path when you deploy the Content Engine EAR file on the remaining application servers.

Deploying Content Engine

1. Right-click Deploy Application in the Content Engine Task View pane, and select Edit Selected Task.
2. In the Bootstrapped EAR file location field, verify the fully qualified path to the currently bootstrapped Content Engine EAR file.
3. Right-click Deploy Application in the Content Engine Task View pane, and select Run Task to deploy Content Engine. This task can take a few minutes. Task execution status messages display in the Console pane.
4. Repeat steps 1 - 3 on all non-managed Content Engine application servers in your P8 domain.

Restarting the application server

WebSphere and WebLogic

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

JBoss

Start all servers and clusters where the Content Engine EAR file has been deployed.

Installation of the Content Engine fix pack is now complete. Continue with Verifying the deployment of the updated Content Engine EAR file.

Completing Configuration Manager tasks using the command line

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

1. Log on to the Content Engine server as the "config_mgr_user" user.
2. Navigate to ce_install_path/tools/configure.
3. Run the configmgr_cl listServers command to display a list of valid server name values (in preparation for running 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 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	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. Select one of the following values: Standard, Cluster, or Netdeploy (network deployment). Specify Standard if you are deploying Content Engine to a stand-alone WebSphere application server, Oracle WebLogic Server, or JBoss application server. Specify Cluster if you are deploying Content Engine to a WebSphere application server cluster, Oracle WebLogic Server cluster, or JBoss Application Server cluster. Specify Netdeploy if you are deploying Content 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 ce_was_tiv_db2. The profile must be in the ce_install_path/tools/configure/profiles directory. The absolute path to the profile directory, such as "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2" or opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2. The absolute path to the profile input file, such as "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2\ce_was_tiv_db2.cfg" or opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2/ce_was_tiv_db2.cfg. 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.

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 ApplicationServerInstallationFolder 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 Engine is stored. If you are installing Content 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>

   5. Save your changes and close the file.
6. (Optional) To encrypt and store the web application server administrator password to the applicationserver.xml file, run the storepasswords command. 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 steps 5 and 6 as needed to edit the application server properties for each Content Engine instance directory that was created.

7. If a bootstrap upgrade task does not 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

   The -appserver appserver_type parameter specifies the application server type. Valid values are: WebSphere, WebLogic, or JBoss.

   The -profile myprofile parameter specifies the profile name. If a profile exists, use the name that you recorded earlier in this procedure.

   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.

8. Confirm that the bootstrap configuration file was properly generated for an upgrade as follows.
1. If this is the first time that the bootstrap information has been generated:
1. Open the configurebootstrap.xml file and verify that the configuration tag contains the string implementorid="upgrade".
2. If the configuration tag contains the string implementorid="upgrade", update the EAR file with bootstrap information by entering the following information at a command line prompt:

   configmgr_cl execute -task configurebootstrap -profile myprofile

   Status messages display in the console.

3. If the configuration tag does not include the string implementorid="upgrade," return to step 7 and generate the bootstrap information again so that the next configurebootstrap.n.xml file is properly configured with the implementorid="upgrade" string.
2. If the bootstrap information has been previously generated:
   1. Open the most recent configurebootstrap.n.xml file and verify that the configuration tag contains the string implementorid="upgrade".

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

   2. If the configuration tag contains the string implementorid="upgrade", enter this command:

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

      Status messages display in the console.

   3. If the configuration tag does not include the string implementorid="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 as follows:

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

      where:

      -profile myprofile specifies the profile name. If a profile exists, use the name that you recorded earlier in this procedure.

      -taskfile configurebootstrap.n.xml specifies the version of the file to use. Omit this parameter if only one version of the task file exists.

9. If your configuration uses Process Engine, complete the steps in the Configuring the Process Engine client section.
10. If your configuration uses Rendition Engine, complete the steps in the Configuring the Rendition Engine client section.
11. If your configuration uses Centera Storage, and your Content Engine runs in an AIX environment:
    1. Review the Centera Support and Protected Storage section in the Hardware and software requirements for IBM FileNet P8 Versions 5.1 for compatibility information.
    2. On each Content Engine server that is running in an AIX environment, update EMC Centera SDK library files and reconfigure the environment variable. See the Installing or updating EMC Centera SDK library files section in the IBM FileNet P8 Platform 5.1 Information Center.
12. (Multiple non-managed stand-alone application servers only) Copy the newly updated Content Engine EAR file into the Profiles directory on each of the remaining application servers. For example:

    ce_install_path\tools\configure\profiles\myprofile\ear

    The location that you select is referred to as the "bootstrapped EAR path." You must enter this path when you deploy the Content Engine EAR file on the remaining application servers.

13. Edit the deployapplication.xml file and verify that the value of the BootstrappedContentEngineEar property is the same as the location of the Content Engine bootstrapped EAR file.
14. Run the following command to deploy Content Engine:

    configmgr_cl execute -task deployapplication -profile myprofile

    where:

    -profile myprofile specifies the profile name. If a profile exists, use the name that you recorded earlier in this procedure.

15. Check the completion status of the Content Engine deployment by running the following command:

    configmgr_cl checkstatus -task deployapplication -profile myprofile

    where:

    -profile myprofile specifies the profile name. If a profile exists, use the name that you recorded earlier in this procedure.

16. If the Content Engine uses multiple non-managed, stand-alone application servers, repeat steps 13 - 16 on all the application servers.

This completes the installation and configuration of the server upgrade part of this fix pack.

Installing the client updates

The following files are included in this fix pack:

• javaapi.jar and Jace.jar or javaapi_t.jar and Jace_t.jar (to be installed as needed on the Content Engine client, such as WorkplaceXT, Application Engine, and customized application installation locations).

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

• Installing the Content Engine fix pack client update on Content Engine-related Java EE applications interactively
• Installing the Content Engine fix pack client updates silently

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

After you have updated the Content Engine servers and the Content Engine-related .NET clients, complete the following tasks for all of the Content Engine-related Java EE applications, such as Application Engine, Process Analyzer, Process Engine, Workplace XT, IBM FileNet Services for Lotus Quicker, and IBM Enterprise Records servers and any custom Content Engine-related Java EE applications.

1. Back up the existing Content Engine client directories.
2. Download the appropriate fix pack client update file and extract its contents to a temporary location. For information, see Download location.
3. Complete the following instructions as appropriate for the client installation:

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.

• Application Engine: See "Installing the latest Content Engine Client files on Application Engine servers" in the Installing and configuring Application Engine section of the IBM FileNet P8 Version 5.1 Information Center.
• Case Analyzer: See "Installing the latest Content Engine Client files on FileNet Case Analyzer servers" in the Installing and configuring FileNet Case Analyzer section of the IBM FileNet P8 Version 5.1 Information Center.
• Process Analyzer: See "Install the latest Content Engine client files on Process Analyzer servers" in the Install and configure Process Analyzer section of the IBM FileNet P8 Version 5.1 Information Center.
• Process Engine: See "Installing the latest Content Engine client files on Process Engine servers" in the Installing and configuring Process Engine section of the IBM FileNet P8 Version 5.1 Information Center.
• IBM Enterprise Records (formerly IBM FileNet Records Manager and IBM InfoSphere Enterprise Records):
  1. Log on as a user with permissions to install software.
  2. Undeploy the IBM Enterprise Records EAR or WAR file from the application server.
  3. Run the appropriate Content Engine client file installation program for your operating system. The installation program is included in the compressed client update file that you downloaded earlier in this procedure. See the Client update files section of "Downloading this fix pack."
  4. Redeploy the updated IBM Enterprise Records EAR or WAR file on the application server.
     See "Installing the Content Engine clients" in the Installing the latest Content Engine and Process Engine client files on IBM Enterprise Records servers section of the IBM FileNet P8 Version 5.1 Information Center.
• Workplace XT: See "Installing the latest Content Engine client files on Workplace XT servers" in the Installing and configuring IBM FileNet Workplace XT section of the IBM FileNet P8 Version 5.1 Information Center.
• IBM FileNet Services for Lotus Quickr: See "Installing the Content Engine Client" in the Installing FileNet Services for Lotus Quickr section of the IBM FileNet P8 Version 5.1 Information Center.
• DB2 Content Manager: See "Connect to Content Manager EE Version 8 library server (Content Manager EE Version 8 Connector window) for DB2" in the Installing and configuring IBM Information Integrator for Content section of the IBM Content Management Information Center.
• IBM Content Navigator: See the "Updating the Content Engine client connector files (FileNet P8)" section in the IBM Content Navigator 2.0 Information Center.
• IBM CMIS for FileNet Content Manager: See "Installing Content Engine Client files for IBM CMIS for FileNet Content Manager" in the Installing IBM CMIS for FileNet Content Manager section of the IBM FileNet P8 Version 5.1 Information Center.
• IBM Case Manager: See "Installing IBM Case Manager to work with an existing FileNet P8 system" in the Installing IBM Case Manager section in the IBM Case Manager Information Center.
• IBM ECM Widgets: See "IBM ECM Widgets V4.5.2.1 installation" in the Installing additional IBM FileNet P8 products section of the IBM FileNet P8 Version 5.1 Information Center.
• InfoSphere Master Content: See "Installing Content Engine Client files for InfoSphere Master Content" in the InfoSphere Master Content installation section of the IBM InfoSphere Master Data management Servicer v8.0.1 Information Center.
• Other applications:
  1. Log on as a user with permissions to install software.
  2. Stop all custom applications that use the Content Engine client.
  3. Run the Content Engine fix pack client update that is appropriate for your operating system. For information see Preparing the Content Engine server for installation.
  4. Click the "Other Applications" option.
  5. Choose the installation directory. Based on the location you specify, the installation program creates a sub-directory called "lib" and populates it with the following files: Jace.jar, javaapi.jar, and p8cjares.jar.
  6. Replace the existing jar files in your directory structure with these new versions.
  7. The root installation directory contains two files, one of which you will rename depending on the transport type you are using.
     • EJB transport
       Rename WcmApiConfig_ejb.properties to WcmAPIConfig.properties.
     • WSI transport
       Rename WcmApi_Config_wsi.properties to WcmApiConfig.properties.
4. Review the Content Engine client log files for installation errors.

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

5. Restart the custom applications that use the Content Engine client.
6. Continue with the section, Verifying the deployment of the updated Content Engine EAR file.

Installing the Content Engine client updates silently

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

1. Log on as a user with permissions to install software.
2. Stop all custom applications that use the Content Engine client.
3. Back up the existing Content Engine client directories.
4. Download the appropriate fix pack client update file and extract its contents to a temporary location. For information, see Download location.
5. 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.
   • LICENSE_ACCEPTED - Read the license, and select "true" to accept the license agreement and to complete the installation
   • UPDATE_application - Select which client applications to update
   • application_FOLDER - Set the directory path of each application
   • APP_SERVER_servertype - Select which server type to update

6. Install this fix pack by running the following command that is appropriate for your operating system.

   Silent installation start commands by operating system for the Content Engine client update

   Operating system	Command to install the Content Engine server update
   AIX	5.1.0.4-P8CE-CLIENT-AIX-FP004.BIN -i silent -f ceclient_silent_install.txt
   HP-UX	5.1.0.4-P8CE-CLIENT-HPUX-FP004.BIN -i silent -f ceclient_silent_install.txt
   HP-UX Itanium	5.1.0.4-P8CE-CLIENT-HPUXI-FP004.BIN -i silent -f ceclient_silent_install.txt
   Linux	5.1.0.4-P8CE-CLIENT-LINUX-FP004.BIN -i silent -f ceclient_silent_install.txt
   Solaris	5.1.0.4-P8CE-CLIENT-SOL-FP004.BIN -i silent -f ceclient_silent_install.txt
   Windows	5.1.0.4-P8CE-CLIENT-WIN-FP004.EXE -i silent -f ceclient_silent_install.txt Tip You can monitor completion of this fix pack server update installation on Windows-based systems by using the Windows Task Manager.
   zLinux	5.1.0.4-P8CE-CLIENT-ZLINUX-FP004.BIN -i silent -f ceclient_silent_install.txt

   
   
7. Review the Content Engine client log files for installation errors.

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

8. Restart the custom applications that use the Content Engine client.

The installation and configuration of the client upgrade for this fix pack is complete. Continue with the next section, Verifying the deployment of the updated Content Engine EAR file.

Verifying the deployment of the updated Content Engine EAR file

Complete the following procedure to verify that Content Engine deployed successfully:

1. Navigate to the following page:

   http://server:port/FileNet/Engine

   where:

   • server is the host name of the machine where Content Engine is deployed.
   • port is the HTTP port used by the Web application server on the machine where Content 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 Engine is the same as the Content Engine build number that you recorded earlier in this procedure.

Configuring the Rendition Engine connection to connect to an Oracle RAC

If your configuration uses Rendition Engine with Oracle RAC, complete the steps in this section, otherwise the fix pack installation is complete.

1. Add the following parameter to a FileNet.properties file on the Content Engine server.

   Publishing.OracleJDBCServiceFormat=true

   The following table lists the possible location of the FileNet.properties file:

   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.1.0_EAP\bin\FileNet.properties

   Tip Because the publishing database connection is cached, you must restart the application server that is running Content Engine after you update the parameter value of Publishing.OracleJDBCServiceFormat.

2. Start the application server that is running Content Engine.
3. Modify the properties of the Rendition Engine connection. The properties can be set at either the Domain, Site, or Virtual Server level in your configuration.
   
   For example, to set the properties of the connection at the Domain level, complete the following procedure by using FileNet Enterprise Manager:
   1. Right-click the Domain and choose Properties.
   2. Select the Publishing tab.
   3. Click Properties in the Select Rendition Engine Connection, or in the Select DITA Rendition Engine Connection area.
   4. Edit the Database name to be the service name of the Oracle RAC.
   5. Edit the Database Server Name to be the SCAN name of the Oracle RAC.
   6. Click OK to accept the change and close the property sheet.
4. Restart the application server that is running Content Engine.
5. Verify that Rendition Engine is started.
6. Verify the Rendition Engine Connection configuration by publishing a test document.

Removing this fix pack

This fix pack does not have an uninstall option. You can remove this fix pack by restoring a backup.

Fix pack contents (APARs)

The following table lists the product fixes in the Content Engine server fix pack update.

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, ibm.com, and FileNet 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