IBM Content Platform Engine 5.2.0.3-P8CPE-FP003 fix pack readme
© Copyright IBM Corporation 2014.

Readme file for: Content Platform Engine
Update name: 5.2.0.3
Fix ID: 5.2.0.3-P8CPE-FP003
Publication date: 07 March 2014
Last modified date: 09 September 2014

Contents

About this fix pack

Server update

Client update

Content Search update

Prerequisites

New in this fix pack

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

Notices

Trademarks

Document change history

About this fix pack

This fix pack provides Content Platform Engine software updates for the FileNet Content Manager, and IBM Content Foundation products. The fix pack consists of two parts: a Content Platform Engine server update and a Content Platform Engine client update. Both the server and the client update must be installed at the same time. Content Platform Engine does not support a server and client at different fix pack levels. The client update is installed where applications that interact with the Content Platform Engine server run.

The Content Platform Engine server update includes a Content Search Services update. This update is the client part of Content Search Services that runs on the Content Platform Engine server.

Server update

The server update automatically completes the following tasks:

• Installs updated Content Platform Engine files for any of the following Content Platform Engine scenarios:
  • An existing installation of Content Platform Engine (5.2.0 or 5.2.0 with fix pack 5.2.0.1-P8CPE-FP001 or fix pack 5.2.0.2-P8CPE-FP002)
  • A new installation of Content Platform Engine 5.2.0
  • An upgrade to Content Platform Engine 5.2.0 from prior Content Engine and Process Engine releases
• Installs updated Configuration Manager files.

The server update also modifies other tools and selectable components.

Client update

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

Content Search Services update

The Content Search Services client software for Content Platform Engine 5.2.0.3-P8CPE-FP003 is packaged with and installed by the fix pack installation program. In the 5.2 GA version, the Content Search Services client software is configured and deployed through the Configuration Manager.

Prerequisites

This fix pack requires that the following software is previously installed:

• 5.2.0.0-P8CPE
• Or any of the following:
  5.2.0.0-P8CPE-IF001, 5.2.0.0-P8CPE-IF002, 5.2.0.1-P8CPE-FP001, 5.2.0.2-P8CPE-FP002, 5.2.0.2-P8CPE-IF001, 5.2.0.2-P8CPE-IF002, or 5.2.0.2-P8CPE-IF003

See the System requirements: Hardware and software requirements for IBM FileNet P8 Versions 3.5, 4.0, 4.5, 4.5.1, 5.0, 5.1, and 5.2 for compatibility of other IBM FileNet P8 products with this fix pack.

New in this fix pack

The following new features are introduced in this fix pack:

• Content Platform Engine
• Introduce support for file based VMM repositories and custom VMM repositories, See techdoc 7041341
• Service Level Agreement and Work Schedule based Deadline and Reminder, See techdoc 7041333
• Process Engine Java API Enhancements for Content Platform Engine 5.2, See techdoc 1640827
• Added Content Based Retrieval low disk-space safeguard, See techdoc 7041382
• Linux x86 64-bit only: When thumbnail generation is enabled, default to generating thumbnail without X Windows server dependency, See technote 1651351
• Administration Console for Content Platform Engine (ACCE), See techdoc 7041321
• Process Administration and Process Configuration Console accessibility support has been added for out-of-the-box Workflows in Content Foundation.
• Administration Console for Content Platform Engine (ACCE) default Content Search Services (CSS) Index Area Maximum Size has changed. See techdoc 1667154
• Content Engine Bulk Importer (CEBI), See techdoc 7041323
• Added Bulk Import feature to enable/disable logging without restarting. See fix list PJ41817 CEBI Enable/Disable logging
• To enable DEBUG logging, create a file named .CEBI.Debug in CE_home/tools/CEBI/
• To disable DEBUG logging, delete the file named .CEBI.Debug from CE_home/tools/CEBI/
• To enable SPY logging, create a file named .CEBI.Spy in CE_home/tools/CEBI/
• To disable SPY logging, delete the file named .CEBI.Spy from CE_home/tools/CEBI/

NOTE: The location to add or delete .CEBI.Debug and .CEBI.Spy depends on where the BulkImport.jar command is run from to start up CEBI.

• Added the full directory path in the .confirm file. Currently the .confirm file only contains the relative path, to help with problem determination the full directory path has been added
• Added the '-r' option flag to signal the Bulk Import tool to ignore .lck files under the config/EOB folder. This was added to support launching multiple Bulk Import tools that use a common config/EOB folder structure in a clustered environment.

Introduced in fix pack 5.2.0.2-P8CE-FP002

• DB2 for z/OS is supported by FileNet Content Manager beginning with fix pack 5.2.0.2-P8CPE-FP002. Support for DB2 for z/OS is limited to Content Platform Engine GCD and object store databases, and Process Engine isolated region databases. For more information, see techdoc 7038918
• Content Platform Engine activity stream enhancements for IBM Connections.
  An integration between IBM FileNet Content Manager and IBM Connections was first available in the 5.2.0 GA release. The integration of these two products forms the IBM Connections Content Manager (CCM) release. One of the features in this release is support for activity streams. An activity stream allows events, such as creation, deletion, and update events (including the tagging, commenting, or liking of documents) for enterprise content to appear interactively in each user stream. This activity stream ensures that changes to important documents in the social community are current.
  For more information, see techdoc 7039091
• Asynchronous event queue processing in Content Platform Engine. For more information, see techdoc 7039089
• Wizard and other new enhancements to the Administration Console for the Content Platform Engine.
• Security Wizards and Bulk Update
• Search wizards for creating and saving SQL queries, simple search queries, search templates, and applying bulk action to search results
• Content upload and download of documents, annotations, code modules, and workflow definitions
• Wizards for localizing class definitions, property templates, and choice lists
• Move Site Components Wizard

  For more information, see techdoc 7039066

• Choose Licenses task in Configuration Manager, where you choose one of the following license types for your installed products:
  • User Value Unit (UVU)
  • Processor Value Unit (PVU) for Production Environments
  • Processor Value Unit (PVU) for Non-Production Environments

  For more information, see techdoc 7039138

• Process Engine Java API Enhancements for Content Platform Engine 5.2. For more information, see technote 1640827.
• FileNet Deployment Manager enhancements, including the following:
• IBM Form Support
• Marking Sets
• Import option to transfer workflows after an import
• New create options
• Support for the Content Navigator form template
• Support for Case Manager page document
• Follow AuditAs property reference from Property Template
• The Add Assets dialog supports browsing for Event and Task class definitions. You can then add the definitions to an export manifest, which can then be used to deploy the definitions to destination systems
• A user preference is supported that specifies whether or not metadata assets that were created by an add-on should be included when you export assets

  For more information, see techdoc 7039065

• Full text index resync capabilities. For more information, see techdoc 7039153
• CSS index thread control. Administrators can now control the indexing work load for each Content Platform Engine process and Content Search Services process. For more information, see techdoc 7039156
• Content Migration Policy. Introduces the ability to manage the lifecycle of document and annotation content through a content migration policy. For more information, see techdoc 7039129
• Reservation storage evaluation, by using the storage policy. The storage area that is selected for a reservation of a checked-out document is determined by re-evaluating the storage policy of the parent document. For more information, see techdoc 7039127
• Sweep performance improvement, using the new FilteredQueryTimeout-integer property. For more information, see techdoc 7039125

Introduced in fix pack 5.2.0.1-P8CE-FP001

• Administration Console enhancements for the Content Platform Engine

  The Administration Console for the Content Platform Engine includes the features that are described in the following bullets. For more information, see techdoc 7038646, "What's new in the Administration Console for the Content Platform Engine," on the IBM support site for details about these features. These tools were integrated into Administration Console for the Content Platform Engine from Workplace and Workplace XT.

  • Process Administrator
    You can now launch the Process Administrator from the Administration Console.

    Process Administrator can search for workflows, work items, and workflow events that are based on criteria that you choose. Process Administrator provides a wide variety of options so you can focus your search precisely. For example, you can search for all the workflows that your manager sent only to you.

    The Process Administrator lets administrators view and manage work in progress. With Process Administrator, you can:

    • Manage workflows
    • Edit workflow data and properties
    • Search for and view workflows
  • Process Configuration Console
    You can now launch the Process Configuration Console from the Administration Console for the Content Platform Engine.

    Process Configuration Console provides the tools to manage the workflow database configuration, including isolated regions, queues, rosters, event logs, and application spaces. Process Configuration Console also includes management tools to configure event logging and to set performance parameters.

    With Process Configuration Console, you can:

    • Create and modify Content Platform Engine database structures (for example, isolated regions, queues, rosters, and event logs)
    • Configure Content Platform Engine event logging
  • Transferring Workflows
    You can now transfer workflow definitions using the Administration Console for the Content Platform Engine.

    Before you can launch a work item from a workflow definition, the workflow definition must be transferred, or saved, to the Content Platform Engine server.

• Enhancements for IBM Connections environments

  The enhancements for IBM Connections environments include the features that are described in the following bullets. For more information, see technote 1636386, "Enhancements in the Content Platform Engine 5.2.0 FP1 release for IBM Connections environments," on the IBM support site for details about these features.

  • Identity Mapping for Creator and Last Modifier Properties
    This enhancement allows the creator and last modifier of a document to be identified by their SID (which is a permanent, unique value) rather than by their short name, which can change over time. It is available through an optionally installed AddOn, adds two new integer properties (ClbLastModifierIndex and ClbCreatorIndex) to the Document, Folder, and Task classes. When the AddOn is installed, these properties hold indexes that are used to look up the user's Security ID (SID) in a new User Identity Mapping table. The values of these indexes are maintained by new ChangePreprocessors.
  • Expire User Access Tokens on Demand
    This enhancement adds a capability for a caller of the Content Platform Engine Java API to force the Content Platform Engine server to flush their entries in the User Access Token cache prior to executing a request. This action forces the Content Platform Engine server to query the Directory Server again to retrieve the set of groups that the user belongs to. This feature can be useful in cases where the user was recently added or removed from a group, and the application wants to ensure that the user immediately picks up the permission changes that the group membership changes imply, rather than waiting for the users entry in the User Access Token cache to expire.
  • New Connections Directory
    This enhancement defines a new directory service type: CmDirectoryConfigurationConnections. This directory type is used exclusively in environments where an IBM Connections integration is present.

Known problems, restrictions, and solutions

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

• This fix pack does not have an uninstall option; be sure to back up Content Platform Engine before you install this fix pack, in the event you need to roll back to your existing release level. For more information, see the FileNet P8 domain backup and recovery section in the IBM FileNet P8 Platform 5.2 Knowledge Center.
• You cannot run the interactive version of the Configuration Manager 5.2 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.
• The Dynamic Summary / Hit Highlighting feature is provided only for technical preview. In a future release, the dynamic summary content might need to be reindexed, so use this feature at your own risk. To use this feature as a technical preview, contact IBM Support for information about enabling it.
• When you use the Administration Console for the Content Platform Engine with Internet Explorer 9, content upload and download to the Content Platform Engine is not supported.
• Due to a Floating Point Exception, thumbnails are not generated on SUSE 10 Content Platform Engine deployments.
• The Administration Console for Content Platform Engine (ACCE) incorrectly removes the display of newline characters (displays text on a single line) in TextBox controls when information is persisted to the Content Platform Engine (CPE) server. This is strictly a cosmetic display issue with no impact to functionality.
• Administration Console for Content Platform Engine (ACCE) default Content Search Services (CSS) Index Area Maximum Size has changed. See techdoc 1667154
• IBM Case Manager 5.1.1.2 users should wait until 5.2.0.3-P8CPE-IF001 is available before upgrading to 5.2.0.3-P8CPE-FP003.
  Process Engine (PE) REST throws No logged-on session exists even if a session is still active after 30 minutes. See techdoc 1668534
• Process Engine (PE) applet exceptions with 5.2.0.3-P8CPE-FP003
• Workplace (AE) will encounter Process Engine (PE) applet exceptions with 5.2.0.3-P8CPE-FP003. See techdoc 1671521
• WorkplaceXT versions prior to XT 1.1.5.2-IF001 will encounter Process Engine (PE) applet exceptions with 5.2.0.3-P8CPE-FP003. See techdoc 1669964

Downloading this fix pack

Click the following link to access the files for this fix pack server update: Fix Central for fix pack 5.2.0.3-P8CPE-FP003. You need an IBM login and password to access this download location.

The files that you download depend on your IBM software license and the GA product that you have installed.

• If you are licensed for, and have previously installed, the FileNet Content Manager or the IBM Content Foundation product, download the Content Platform Engine server update and the Content Platform Engine client update that apply to your operating system.
• Download the notices.txt file and replace the notices file that exists in your FileNet Content Manager or IBM Content Foundation system.

Content Platform Engine 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 Platform Engine 5.2.0.3 files, followed by configuring the Content Platform Engine. If you are licensed for FileNet Content Manager or IBM Content Foundation, complete the following sections.

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

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

When you deploy Content Platform Engine in a "non-managed" application server environment, install and configure the Content Platform Engine fix pack on one of the Content Platform Engine servers in the environment. After you configure the bootstrapped Content Platform Engine EAR file on this first server, copy and deploy the bootstrapped EAR file to each of the other servers.

Preparing the Content Platform Engine server for installation

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

Downloading this fix pack server update

1. Log on as the "ce_install_user" user.
2. 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.
3. Stop Content Platform Engine and all client applications, including, but not limited to:
   • Enterprise Manager
   • Configuration Manager
   • Deployment Manager
   • .NET client applications
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 Platform Engine server.
5. (Existing 5.2.0.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.

   Important Failure to make a backup of the existing bootstrapped Content Platform Engine EAR file can have serious repercussions on the operation of Content Platform Engine if you accidentally delete or overwrite the existing bootstrapped Content Platform Engine EAR file during the installation of this fix pack. A common symptom of a deleted or an overwritten bootstrapped EAR file is that system users cannot log on to Content Platform Engine and are not able to log on until that file is restored. If this situation occurs, you need a backup to recover.

You can determine the location of the existing bootstrapped EAR file for Content Platform Engine by viewing the contents of the Servers.xml file, which is in the ce_install_path directory.

Installing this fix pack on the Content Platform Engine server

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

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

Installing the Content Platform Engine server updates interactively

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

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

   Content Platform Engine server update executable file name by operating system

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

   
   
2. From the Choose Components dialog box, select the components that you want to install.
   • Select Content Platform Engine server to install the server updates and Configuration Manager.
   • Windows only: Select .NET Client to update the Content Platform Engine COM Compatibility Layer for Content Platform 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.
   • Windows only: Select FileNet Enterprise Manager to install updates to the FileNet Enterprise Manager.
     Restriction FileNet Enterprise Manager is not available with IBM Content Foundation.
   • Select Tools to install updates to the Configuration Manager. The tools include updates to FileNet Deployment Manager.
3. If you selected the Content Platform 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 Platform Engine server installation.

Installing the Content Platform Engine server updates silently

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

1. Navigate to the temporary directory that you selected in Preparing the Content Platform 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 and Configuration Manager.
• Windows Only: DotNetClients - Updates the Content Platform Engine COM Compatibility Layer for Content Platform Engine-related .NET applications.
• Windows Only: FileNetEnterpriseManager - Updates FileNet Enterprise Manager.
  Restriction FileNet Enterprise Manager is not available with IBM Content Foundation.
• Tools - Updates the Configuration Manager. The tools include updates to FileNet Deployment Manager.
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 run.
5. Install this fix pack by running the following command that is appropriate for your operating system.

Completing the Content Platform Engine server installation

1. Review the Content Platform Engine log files for installation errors

   Installation errors are recorded in the ce_install_log_5_2_0_3.txt file, which is in the ce_install_path directory (normally under ../IBM/FileNet/ContentEngine).

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

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

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

3. (Custom .NET applications only) This step applies if you installed only the .NET client component on a machine that is not the Content Platform 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 Platform Engine installation program places the updated file (FileNet.API.dll) into the "installation_location\ContentEngine" directory.

3. Restart the .NET application.

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

Configuring the Content Platform Engine server after installation

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

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

Removing a deployed Content Platform Engine

Removing the application server cache directories

Clearing the Internet browser cache on ACCE clients

Completing Configuration Manager tasks

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

The documentation that you use to configure and deploy Content Platform 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 Platform Engine 5.2.0 or as part of an upgrade to Content Platform Engine 5.2.0, return to the FileNet P8 5.2.0 installation documentation to continue with the instructions to configure and deploy Content Platform Engine.
• If you are updating an existing Content Platform Engine 5.2.0 system with the contents from this fix pack server update, continue with the remaining tasks.

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

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.

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 prompted to later in this readme. JBoss must not be running during the update process.

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 that all items are checked under Details.

Internet Explorer

Internet Options > Browsing history > Delete... > Check all boxes. Delete.

Safari

History > Clear History... > Clear

Completing Configuration Manager tasks

You can bootstrap and deploy Content Platform Engine either interactively or by using the command line. Choose one of the following links to complete the Configuration Manager tasks in this section.

Completing Configuration Manager tasks interactively

Completing Configuration Manager tasks using the command line

Completing Configuration Manager tasks interactively

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

• Starting the Configuration Manager
• Choosing Licenses
• Bootstrapping the Content Platform Engine
• Copying the bootstrapped Content Platform Engine EAR file to the remaining application servers
• Deploying Content Platform Engine
• Restarting the application server

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.

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:
   • User Value Unit (UVU)
   • Processor Value Unit (PVU) for Production Environments
   • Processor Value Unit (PVU) for Non-Production Environments
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.

Bootstrapping the Content Platform Engine

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

1. In the Bootstrapped EAR file location field, verify the fully qualified path to the currently bootstrapped Content Platform Engine EAR file.
2. Select File > Save.
3. 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 this fix pack. This operation can take a few minutes. Task execution status messages display in the window below the bootstrap properties.

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.0.0-P8CPE was originally bootstrapped) on each of the remaining Content Platform Engine application servers in your P8 domain. For example:

ce_install_path\tools\configure\profiles\myprofile\ear

(JBoss Application server) Based on your "Standard or Cluster" deployment, remove the Engine-jb.ear file or Engine-jbc.ear file from one of the following directories, where jboss_install_directory is the JBoss installation directory and custom_name is the name of a user-defined directory.

Standard deployment

jboss_install_directory\server\default\deploy

jboss_install_directory\server\custom_name\deploy

Cluster deployment

jboss_install_directory\server\all\deploy

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

Deploying Content Platform Engine

1. Right-click Deploy Application in the Content Platform 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 Platform Engine EAR file.
3. 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.
4. Repeat steps 1 - 3 on all non-managed Content Platform Engine application servers in your P8 domain.

Deployment of the Content Platform Engine server update is now complete. Continue with Restarting the application server.

Completing Configuration Manager tasks using 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 "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 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	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 Platform Engine to a standalone WebSphere application server, Oracle WebLogic Server, or JBoss application server. Specify Cluster if you are deploying Content Platform Engine to a WebSphere application server cluster, Oracle WebLogic Server cluster, or JBoss Application Server cluster. 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 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.cfgp" 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 Platform Engine is stored. If you are installing Content Platform Engine on a node in a cluster or on a managed server node and Deployment Manager is remote from Configuration Manager, use the directory for the WebSphere profile that is on the node. </description>

      <displayName>Application server profile directory</displayName>

      </property>

   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 Platform Engine instance directory that was created.

7. Enter the following command to run the Choose Licenses task:

   configmgr_cl generateconfig -appserver app_server_type -task task_type -license license_type -profile upgrade_profile_name

   Where the following parameters apply:

   • The app_server_type is WebSphere, WebLogic, or JBoss.
   • The task_type is configurepricingmodel.
   • The license_type is UVU, "PVU Production", or "PVU Non-Production".

     Restriction: If the license type value contains embedded blanks, you must delimit the value by adding double quotes (").

   • The upgrade_profile_name is your upgrade profile name.
     Specify the fully qualified path to the profile directory if it is not in the default directory: \ContentEngine\tools\configure\profiles.

   The licensing choices that are stored in the software tag files are written into the Content Platform Engine EAR file as part of the "Configure Bootstrap and Text Extraction" task execution.

   The IBM System Dashboard for Enterprise Content Management Listener component will be configured with that licensing information so that usage reporting and the IBM License Metric Tool can make the correct product and license association.

   If you rerun the "Choose Licenses" task with a different set of licensing choices, you must complete the following steps in order that the running application always has the correct licensing information:

   1. Uninstall the FileNet Engine application from your application server.
   2. Run the "Configure Bootstrap and Text Extraction" task.
   3. Run the "Deploy Application" task.
8. Enter the following command to run the Choose Licenses task:

   configmgr_cl execute [-task task_type | -taskfile task_file_name ] -profile upgrade_profile_name [-silent] [-force] [-help]

   Where the following parameters apply:

   • The task_type is configurepricingmodel.
   • The task_file_name is configurepricingmodel.xml.
   • The upgrade_profile_name is your profile name.
9. If a bootstrap upgrade task (configurebootstrap.xml) 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 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.

10. 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 9 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 9 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

      -profile myprofile

      Specifies the profile name. If a profile already 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.

3. (Multiple non-managed stand-alone application servers only) Copy the newly updated Content Platform 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 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.

4. 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.
5. Run the following command to deploy Content Platform Engine:

   configmgr_cl execute -task deployapplication -profile myprofile

   -profile myprofile

   Specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.

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

   configmgr_cl checkstatus -task deployapplication -profile myprofile

   -profile myprofile

   Specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.

7. If the Content Platform Engine uses multiple non-managed, stand-alone application servers, repeat steps 10 c-f on all the application servers.

Deployment of the Content Platform Engine server update is now complete. Continue with the next section, Restarting the application server.

Restarting the application server

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.

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 that you recorded earlier in this procedure.

Checking the automatic upgrade status for Content Platform Engine data

When you deploy the upgraded Content Platform Engine application on the web application server and start the application, the existing Content Platform Engine data upgrade begins. You can check the progress on the upgrade to confirm that the upgrade was successful. Complete the following steps to check the status of the automatic data upgrade:

1. Enter the URL for the automatic upgrade status page into your browser:
   http://server_name:port/FileNet/AutomaticUpgradeStatus
2. Review the status for the FileNet P8 domain or object store.
3. Verify that the status of the upgrade is "Completed" for the GCD and object stores. The upgrades are complete when they have a status of "Ready".

For more information on upgrades, see the IBM FileNet P8 Version 5.2 documentation for: Working with Configuration Manager.

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 the FileNet.properties file on the Content Platform 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.2.0_EAP\bin\FileNet.properties

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

2. Start the application server that is running Content Platform 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 Platform Engine.
5. Verify that Rendition Engine is started.
6. Verify the Rendition Engine Connection configuration by publishing a test document.

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 Platform 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 Platform Engine fix pack client update on Content Platform Engine-related Java EE applications interactively
• Installing the Content Platform Engine fix pack client updates silently

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

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

1. Back up the existing Content Platform Engine client directories.
2. Download the appropriate fix pack client update file and extract its contents to a temporary location. For information, see Downloading this fix pack.
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 Platform Engine client files on Application Engine servers" in the Installing and configuring Application Engine section of the IBM FileNet P8 Version 5.2 Knowledge 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 Platform 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 Content Platform Engine 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 Platform Engine clients" in the Installing the latest Content Platform Engine client files on IBM Enterprise Records servers section of the IBM FileNet P8 Version 5.2 Knowledge Center.
• Workplace XT: See "Installing the latest Content Platform Engine client files on Workplace XT servers" in the Installing and configuring IBM FileNet Workplace XT section of the IBM FileNet P8 Version 5.2 Knowledge Center.
• IBM FileNet Services for Lotus Quickr: See "Installing the Content Platform Engine client" in the Installing FileNet Services for Lotus Quickr section of the IBM FileNet P8 Version 5.2 Knowledge 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 Knowledge Center.
• IBM Content Navigator: See the "Updating the Content Platform Engine client connector files (FileNet P8)" section in the IBM Content Navigator 2.0 Knowledge 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 Knowledge Center.
• IBM ECM Widgets: See "IBM ECM Widgets v4.5.2.5 FP3 installation" in the Installing additional IBM FileNet P8 products section of the IBM FileNet P8 Version 5.2 Knowledge Center.
• Other applications:

  If your application depends on the legacy 3.5.x Content Java API, then follow the below instructions:

  1. Log on as a user with permissions to install software.
  2. Stop all custom applications that use the Content Platform Engine client.
  3. Run the Content Platform Engine fix pack client update that is appropriate for your operating system. For information see Preparing the Content Platform 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 Platform Engine client log files for installation errors.

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

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

The installation and configuration of the client upgrade for this fix pack 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 fix pack client update file and extract its contents to a temporary location. For information, see Downloading this fix pack.
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 Platform Engine client update

   Operating system	Command to install the Content Platform Engine server update
   AIX	5.2.0.3-P8CPE-CLIENT-AIX-FP003.BIN -i silent -f ceclient_silent_install.txt
   HP-UX	5.2.0.3-P8CPE-CLIENT-HPUX-FP003.BIN -i silent -f ceclient_silent_install.txt
   HP-UX Itanium	5.2.0.3-P8CPE-CLIENT-HPUXI-FP003.BIN -i silent -f ceclient_silent_install.txt
   Linux	5.2.0.3-P8CPE-CLIENT-LINUX-FP003.BIN -i silent -f ceclient_silent_install.txt
   Solaris	5.2.0.3-P8CPE-CLIENT-SOL-FP003.BIN -i silent -f ceclient_silent_install.txt
   Windows	5.2.0.3-P8CPE-CLIENT-WIN-FP003.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.2.0.3-P8CPE-CLIENT-ZLINUX-FP003.BIN -i silent -f ceclient_silent_install.txt

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

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

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

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

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

The following table lists the contents of this Content Platform 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