c1927197 PDF

IBM FileNet P8
Version 4.5
Release Notes
SC19-2719-07
IBM FileNet P8
Version 4.5
Release Notes
SC19-2719-07
Note Before using this information and the product it supports, read the information in Notices on page 111.
Copyright IBM Corporation 2002, 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM FileNet P8 Release Notes Software Release 4.5 Contents
Contents
Revision Log ................................................................................................................................................. 9 Introduction ................................................................................................................................................. 13 Access IBM FileNet documentation, compatibility matrices, and fix packs............................................. 13 Customer support .................................................................................................................................... 13 Feedback................................................................................................................................................. 13 Whats New ................................................................................................................................................. 14 FileNet P8 Platform ................................................................................................................................. 14 Staged upgrades.................................................................................................................................. 14 Simplified application data deployment ............................................................................................... 14 IBM Support Assistant ......................................................................................................................... 15 FileNet Services for Lotus Quickr 1.0...................................................................................................... 15 Available languages............................................................................................................................. 15 Application Engine................................................................................................................................... 16 Improved installation and configuration process ................................................................................. 16 New access role................................................................................................................................... 16 Removed root user restriction.............................................................................................................. 16 Expanded single sign-on support ........................................................................................................ 16 Improved language support ................................................................................................................. 16 Business Activity Monitor......................................................................................................................... 17 New location for installation instructions.............................................................................................. 17 Application name changes................................................................................................................... 17 Changes to the "Import Out-of-the-box configuration project" topic .................................................... 17 New upgrade procedure ...................................................................................................................... 18 Improved language support ................................................................................................................. 18 Terminal Release of BAM .................................................................................................................... 18 Content Engine........................................................................................................................................ 18 Support for IBM System Storage DR550............................................................................................. 18 Improved configuration and deployment during installation ................................................................ 18 Improved Enterprise Manager functionality ......................................................................................... 18 Removed root user restriction.............................................................................................................. 19 Support for DITA Rendition Engine ..................................................................................................... 19 Improved language support ................................................................................................................. 19 FileNet Content Federation Services ...................................................................................................... 19 Support for Content Manager OnDemand........................................................................................... 19 Integration with Content Engine........................................................................................................... 20 FileNet P8 Documentation ...................................................................................................................... 20 Improved planning, preparation, and installation instructions.............................................................. 20 New location for the upgrade instructions for custom applications ..................................................... 21 IBM FileNet Connector for SharePoint Web Parts 2.2.1 ......................................................................... 21 New Features....................................................................................................................................... 21 Installation Improvements .................................................................................................................... 21 Usability and Accessibility.................................................................................................................... 21 Available languages............................................................................................................................. 21 Process Analyzer..................................................................................................................................... 22 Improved language support ................................................................................................................. 22 Support for separate database servers ............................................................................................... 22 Improved event log processing............................................................................................................ 22 Process Engine ....................................................................................................................................... 22 Process Engine Export and Import Utilities ......................................................................................... 22 New features for Process Designer ..................................................................................................... 22 New features for Process Configuration Console................................................................................ 23 Improved accessibility.......................................................................................................................... 23 New Content Extended Operations ..................................................................................................... 23 Process Simulator ................................................................................................................................... 23 Improved language support ................................................................................................................. 23 Copyright IBM Corp. 2002, 2010 5
IBM FileNet P8 Release Notes Software Release 4.5 Contents Records Manager .................................................................................................................................... 24 New auto-destroy feature..................................................................................................................... 24 Container-managed authentication and single sign-on ....................................................................... 24 New Declassification Sweep utility ...................................................................................................... 24 New report for entities due for an interim transfer ............................................................................... 24 Improved language support ................................................................................................................. 24 Customizable report templates ............................................................................................................ 25 Improved multi-threading process control............................................................................................ 25 Improved object store configuration wizard ......................................................................................... 25 New system-to-system transfers utility ................................................................................................ 25 New workflows with mapping............................................................................................................... 25 Rendition Engine ..................................................................................................................................... 25 Updated rendering engine ................................................................................................................... 25 Expanded application support ............................................................................................................. 25 Expanded platform support.................................................................................................................. 25 Automated Vista Domain handling ...................................................................................................... 26 New default installation location .......................................................................................................... 26 Workplace XT 1.1.3 ................................................................................................................................. 26 Improved user interfaces ..................................................................................................................... 26 Folder customizations .......................................................................................................................... 26 Expanded support for other repositories.............................................................................................. 26 Improved integration with Office applications ...................................................................................... 26 Improved search capabilities ............................................................................................................... 27 Improved installation and configuration process ................................................................................. 27 Removed root user restriction.............................................................................................................. 27 New access role................................................................................................................................... 27 Improved language support ................................................................................................................. 27 Other improvements ............................................................................................................................ 27 Workplace XT 1.1.4 ................................................................................................................................. 28 Improved document management support .......................................................................................... 28 Improved user interfaces ..................................................................................................................... 28 File Tracker .......................................................................................................................................... 28 Improved support for Content Manager OnDemand (CMOD) server.................................................. 28 Application Integration BCS................................................................................................................. 29 Improved installation and configuration process ................................................................................. 29 Improved language support ................................................................................................................. 29 Development Tools.................................................................................................................................. 30 Content Java API Compatibility Layer.............................................................................................. 30 Content Engine Object Model Changes .............................................................................................. 30 Content Engine Java and .NET APIs................................................................................................... 43 Content Engine Web Service............................................................................................................... 46 IBM Enterprise Content Management Widgets ................................................................................... 47 Process Engine Java API .................................................................................................................... 48 Workplace Application Toolkit.............................................................................................................. 49 Fixed APARs............................................................................................................................................... 50 Known limitations ........................................................................................................................................ 52 Content Engine........................................................................................................................................ 52 Limitation on deployment of event action handlers in code modules. ................................................. 52 CFS-CMOD ............................................................................................................................................. 52 Known Issues.............................................................................................................................................. 53 Independent software vendor issues....................................................................................................... 53 Application servers............................................................................................................................... 53 Crystal Reports .................................................................................................................................... 54 Java Virtual Machine............................................................................................................................ 54 Workplace ............................................................................................................................................ 54 Workplace XT ...................................................................................................................................... 55 Content Federation Services (CFS-CS and CFS-IICE)....................................................................... 55 Copyright IBM Corp. 2002, 2010 6
IBM FileNet P8 Release Notes Software Release 4.5 Contents Content Engine Web Service............................................................................................................... 55 Content Engine Java and .NET API .................................................................................................... 56 FileNet P8 Platform Installation, Uninstallation, and Upgrades............................................................... 56 Content Engine .................................................................................................................................... 56 Content Search Engine........................................................................................................................ 58 Process Engine.................................................................................................................................... 59 Application Engine ............................................................................................................................... 59 Workplace XT ...................................................................................................................................... 61 Image Services Resource Adapter (ISRA) .......................................................................................... 61 Content Engine........................................................................................................................................ 61 Content Federation Services (CFS-IS and CFS-CMOD) ........................................................................ 64 Content Search Engine ........................................................................................................................... 64 FileNet Services for Lotus Quickr............................................................................................................ 66 IBM Enterprise Content Management Widgets....................................................................................... 67 Process Engine ....................................................................................................................................... 69 Process Analyzer..................................................................................................................................... 72 Application Engine................................................................................................................................... 72 Workplace ............................................................................................................................................ 72 Workplace XT .......................................................................................................................................... 75 Application Integration BCS................................................................................................................. 77 Records Manager .................................................................................................................................... 79 Disposition sweep ................................................................................................................................ 79 DoD Classified ..................................................................................................................................... 79 File Plan Import and Export Tool ......................................................................................................... 80 Globalization ........................................................................................................................................ 80 High Availability environments............................................................................................................. 80 Installing on Process Engine 4.5 disables CE_Operations component queue ................................... 80 Record operations................................................................................................................................ 80 Reports ................................................................................................................................................ 82 Search template................................................................................................................................... 83 Single sign-on ...................................................................................................................................... 83 Time Zone Settings.............................................................................................................................. 83 User interface....................................................................................................................................... 84 Client tools ........................................................................................................................................... 84 FileNet P8 Platform.............................................................................................................................. 85 eForms for P8.......................................................................................................................................... 86 Rendition Engine ..................................................................................................................................... 87 Desktop eForms 6.0.1 ............................................................................................................................. 88 WebDAV.................................................................................................................................................. 89 Internationalization .................................................................................................................................. 89 IBM FileNet Connector for SharePoint Document Libraries 2.2.0 .......................................................... 89 IBM FileNet Connector for SharePoint Web Parts 2.2.1 ......................................................................... 91 Development Tools.................................................................................................................................. 92 Content Engine Java and .NET APIs................................................................................................... 92 Documentation ........................................................................................................................................ 92 FileNet P8 Documentation ...................................................................................................................... 92 Help system and Search functionality.................................................................................................. 92 Plan and Prepare Guide ...................................................................................................................... 93 Application Engine ............................................................................................................................... 93 Content Engine .................................................................................................................................... 94 Content Federation Services ............................................................................................................... 95 Workplace XT ...................................................................................................................................... 95 Content Search Engine........................................................................................................................ 95 BAM ..................................................................................................................................................... 96 Process Engine.................................................................................................................................... 97 Process Analyzer ................................................................................................................................. 97 Process Task Manager ........................................................................................................................ 99 Copyright IBM Corp. 2002, 2010 7
IBM FileNet P8 Release Notes Software Release 4.5 Contents FileNet Deployment Manager ............................................................................................................ 100 P8 eForms ......................................................................................................................................... 100 Desktop eForms 6.0.1........................................................................................................................ 101 Rendition Engine................................................................................................................................ 101 Records Manager .............................................................................................................................. 102 IBM Enterprise Content Management Widgets ................................................................................. 103 IBM SharePoint Connectors Document Libraries 2.2.0.1.................................................................. 103 Content Java API Compatibility Layer ............................................................................................... 104 Security Concepts > Encryption Schemes ........................................................................................ 104 Working with Security ........................................................................................................................ 104 Content Engine Java and .NET API Developer's Guide.................................................................... 108 Resolved Known Issues............................................................................................................................ 109 Resolved in Workplace XT 1.1.4 ........................................................................................................... 109 Notices ...................................................................................................................................................... 111 Trademarks ........................................................................................................................................... 112 U.S. Patents Disclosure......................................................................................................................... 113
Copyright IBM Corp. 2002, 2010
IBM FileNet P8 4.5 Release Notes Revision Log
Revision Log
Date 17 December 2010 Revision Adds a Whats New in 4.5.0 Content Engine Java and .NET APIs entry regarding the PStore Tool. Adds or updates Known Issue Defects for the following: o o o o o Application Engine: 905170 Content Engine: 777160, 848698 Records Manager: 910896 Workplace XT: 905170 FileNet P8 Documentation: 07/09/10 Content Engine: 908991 Content Search Engine: 919039
Adds updated links for IBM FileNet Services for Lotus Quickr Adds or updates Known Issue Defects for the following: o FileNet P8 Platform Installation, Uninstallation, and Upgrades: o Content Engine: 862430, 893302 Application Engine: 850314 Rendition Engine: 910345
FileNet P8 Documentation: Help system and Search functionality: 859185, 906895 Content Engine: 906636 Rendition Engine: 907727 Records Manager: 904255
03/05/10
Adds or updates Known Issue Defects for the following: o FileNet P8 Platform Installation, Uninstallation, and Upgrades: o o o Content Engine: 780674, 842164, 846316 (update), 850363 Workplace XT: 833280, 859308 Image Services Resource Adapter (ISRA): 853075
Content Engine: 846316, 853401 Content Search Engine: 845707, 856024 Workplace XT: 835374 Application Integration BCS: 819351 (update)
FileNet P8 Documentation: FileNet P8 Plan and Prepare Guide: 842378 9
IBM FileNet P8 4.5 Release Notes Revision Log 10/27/09 Application Engine: 849682 Content Engine: 841060, 843139 Content Federation Services: 787304, 787307 Workplace XT: 852145 Content Search Engine: 841274 Process Task Manager: 802464 Rendition Engine: 840790 Content Engine Java and .NET API Developer's Guide: 866148
Adds or updates Known Issue Defects for the following products: o Installation: o Content Search Engine:785816 (update)
Independent Software Vendors: Workplace XT: 840048
o o o
IBM Enterprise Content Management Widgets: 799097 Process Engine: 799097 (update) Application Engine: Workplace: 785290
Workplace XT: 780538, 759915 (ISV), 785290, 804306, 804309, 825425, 844804 Application Integration BCS: 845953
o o
Records Manager: 836350, 846730 FileNet P8 Documentation: Content Engine: 794829
08/10/09
Adds Whats New section for Workplace XT 1.1.4 Adds or updates Known Issue Defects for the following: o Independent Software Vendors: o o o o o Workplace XT: 825425
Content Federation Services (CFS-IS and CFS-CMOD): 786183 Content Engine Web Service: 835019 Process Engine: 799097 Workplace: 836189 Workplace XT: 786696, 832101, 831263, 837367 Application Integration BCS: 799481, 799757, 812513, 819351, 819664, 829845, 829887,830471, 831234, 835206
Content Engine Java and .NET APIs: 379982, 381685
10
IBM FileNet P8 4.5 Release Notes Revision Log o o Internationalization: 789084 FileNet P8 Documentation: 06/08/09 Content Engine: 752140, 768277 FileNet Deployment Manager: 838187
Adds a Whats New in Content Engine entry regarding support for IBM System Storage DR550. Adds Whats New section for IBM FileNet Connector for SharePoint Web Parts 2.2.1 Adds or updates Known Issue Defects for the following: o o ISV: 798158 FileNet P8 Platform Installation, Uninstallation, and Upgrades o o o o o o Process Engine: 801253
Content Engine: 798158 Process Analyzer: 802805 Process Engine: 785947, 786515, 789096, 789704, 800406, 802481 WebDAV: 779184 Records Manager 779610, 800183 IBM FileNet Connector for SharePoint Document Libraries 2.2.0: 740757, 742757, 756744, 756745, 757601, 758748, 759107, 759111, 759120, 759224, 759405, 780096 IBM FileNet Connector for SharePoint Web Parts 2.2.0: 660127, 743774, 790893, 801999 FileNet P8 Documentation: Content Engine: 792280 BAM: 811205 IBM FileNet for SharePoint Document Libraries 2.2.0: 795624, 795640
o o
01/29/09
Adds Whats New in FileNet Services for Lotus Quickr 1.0 Adds or updates Known Issue Defects for the following: o FileNet P8 Platform Installation, Uninstallation, and Upgrades o o o o o Content Engine: 788041 Content Search Engine:785816 (update)
Records Manager 777137 Content Search Engine: 782390 FileNet Services for Lotus Quickr: 787390, 787114, 767882, 775463, 779920, 780139, 783889, 784386, 785114, 785318, 786243, 787126, 791334 eForms for P8: 323303, 381905, 387365,783825, 784618, 785293, 785409, Desktop eForms: 784364 11
IBM FileNet P8 4.5 Release Notes Revision Log o FileNet P8 Documentation: 11/14/08 Process Engine: 786175 P8 eForms: 386173
Initial release of P8 4.5
12
IBM FileNet P8 4.5 Release Notes Introduction
Introduction
This document provides release information about IBM FileNet P8 4.5 and has the following major topics: Whats new Describes new features. Known issues Lists and describes known product and documentation issues.
This document includes information about the following FileNet P8 components: Application Engine 4.0.2 Business Activity Monitor 4.5 Content Engine 4.5 FileNet Content Federation Services 4.5 FileNet P8 Documentation 4.5 IBM FileNet Connector for SharePoint Document Libraries 2.2.0 IBM FileNet Connector for SharePoint Web Parts 2.2.1 Process Analyzer 4.5 Process Engine 4.5 Process Simulator 4.5 Records Manager 4.5 Rendition Engine 4.5 Workplace XT 1.1.3
Access IBM FileNet documentation, compatibility matrices, and fix packs

To access documentation, compatibility matrices, and fix packs for IBM FileNet products: 1. Navigate to the Product Documentation for FileNet P8 Platform support page. (http://www-1.ibm.com/support/docview.wss?rs=3247&uid=swg27010422). 2. Select a PDF or a Doc Link, whichever is appropriate.
Customer support
For information about contacting customer support: 1. Navigate to the FileNet Product Family support page: (http://www-01.ibm.com/software/data/content-management/filenet-product-family/support.html). 2. Click IBM FileNet Support Communications, or search for a particular support topic under Enter search terms.
Feedback
Your feedback helps us to provide quality information. Send your comments about this publication or any other IBM FileNet documentation by e-mail to comments@us.ibm.com. Be sure to include the name of the product, the version number of the product, and the name and part number of the book (if applicable). Copyright IBM Corp. 2002, 2010 - 13 -
IBM FileNet P8 4.5 Release Notes Whats New If you are commenting on specific text, include the location of the text (for example, a chapter and section title, a table number, a page number, or a help topic title).
Whats New
This section lists the new and improved features contained in this release.
FileNet P8 Platform
Staged upgrades
If you are upgrading from IBM FileNet P8 Platform V4.0 components, including supported expansion products, you can choose to upgrade the components independently. This means that you can upgrade one component and still have a working configuration without upgrading all components during the same upgrade session. For more information, see Upgrade Overview in Plan and Prepare Your Environment for IBM FileNet P8.
Simplified application data deployment

The following features simplify the deployment of application data from one FileNet P8 environment to another. FileNet Deployment Manager You use FileNet Deployment Manager to replace environment-specific data, such as user names and object store IDs, in application data that is extracted from a Content Engine object store. You can use this tool for Content Engine core objects, Process Engine workflow definitions, Workplace and Workplace XT objects, and eForms objects. You can run Deployment Manager from a command line or from a graphical user interface. For more information about FileNet Deployment Manager, see FileNet P8 Documentation > Application Deployment > Get started with FileNet Deployment Manager. For information about the command-line interface, see FileNet P8 Documentation > Application Deployment > Use the command line utilities > Deployment command-line reference. Process Engine Export and Import Utilities Process Engine includes the following new command-line utilities to assist in exporting and importing application data from one Process Engine instance to another: o The object utilities consist of two scripts, peObject_export and peObject_import, which assist you with exporting and importing queues, rosters, logs, user preferences, and system properties. The server utilities consist of two scripts, peServerConfig_export and peServerConfig_import, which assist you with exporting and importing server configuration information.
For more information about these utilities, see FileNet P8 Documentation > Application Deployment > Use the command line utilities > Process Engine Export/Import Utilities command-line reference. Application deployment help Application deployment is documented in the FileNet P8 Help. Along with detailed procedures for deploying custom applications, the help includes deployment maps that identify the classes, objects, and other assets that you need to consider when deploying an application. For each asset, these deployment maps describe the deployment mechanism, any dependencies on other assets, and environment-specific data.
- 14 -
IBM FileNet P8 4.5 Release Notes Whats New
IBM Support Assistant

IBM Support Assistant (ISA) is a no-charge support tool that you can download and install on your local system. ISA helps you find information and resolve problems with IBM software products. ISA add-ons are available for a variety of IBM FileNet products, including the IBM FileNet P8 Business Process Manager, Content Manager, and Application Engine products. An add-on enables ISA to display productspecific information (such as APARs and technotes). Instructions for downloading and installing the ISA are on the ISA Web site: www.ibm.com/software/support/ISA/. After you have installed the ISA, you can download product addons. For instructions, see "Find new product add-ons" in the ISA online help.
FileNet Services for Lotus Quickr 1.0

For additional Known Issues and Release Notes associated with FileNet Services for Lotus Quickr see: Known issues for IBM FileNet Services for Lotus Quickr Version 1.0 Fix Pack 1.0: http://www01.ibm.com/support/docview.wss?rs=3278&uid=swg27017650 IBM FileNet Services for Lotus Quickr Version 1.1 Release Notes: http://www.ibm.com/support/docview.wss?rs=3273&uid=swg27018249
IBM FileNet Services for Lotus Quickr 1.0 provides support for integration with Lotus Quickr products. By installing and configuring this service, you can allow end users to view and manage content in a FileNet P8 object store using Lotus Quickr applications.
Available languages
IBM FileNet Services for Lotus Quickr can be installed on an operating system in the following nonEnglish languages: Language Chinese (Simplified) Chinese (Traditional) French German Italian Locale zh-CN zh-TW FR DE IT Language Japanese Korean Portuguese (Brazilian) Spanish Locale JA KO pt-BR ES
Lotus Quickr supports a different set of languages. Some messages produced by IBM FileNet Services for Lotus Quickr are displayed by Lotus Quickr. These messages are available, by default, in the following non-English languages: Language Arabic Catalan Chinese (Simplified) Chinese (Traditional) Czech Danish Dutch Finnish Locale AR CA zh-CN zh-TW CS DA NL FI Language Korean Norwegian Polish Portuguese Portuguese (Brazilian) Romanian Russian Slovak Locale KO NO PO PT pt-BR RO RU SK - 15 -
IBM FileNet P8 4.5 Release Notes Whats New French German Greek Hungarian Italian Japanese FR DE EL HU IT JA Slovenian Spanish Swedish Thai Turkish Ukrainian SL ES SV TH TR UK
See Lotus Quickr at: http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/index.jsp?topic=/com.ibm.lotus.quickr.admin.wpv81 .doc/ecm/ic_ecm_c_configure.html for more information.
Application Engine
Improved installation and configuration process
Starting with fix pack AE-4.0.2-001, all Application Engine fix packs contain all of the software necessary to install Application Engine. You no longer need to install a base Application Engine release prior to installing a fix pack. Installation program panels have been updated to make choices clearer and to simplify the installation process. The Install and Upgrade Worksheet, new in the FileNet P8 Platform documentation release for 4.5, includes rows for Application Engine installation program values. You can use the worksheet when planning and preparing for your Application Engine installation as part of a FileNet P8 environment. The Application Engine installation program and the client installation programs for Process Engine and Content Engine allow you to defer creating a deployment file. By deferring this step, you can bypass creating the deployment file for each installation program. Instead, the last installation program can create the file, or you create the file manually before you deploy.
New access role

The new PWDiagram access role controls access to Diagram mode in Process Designer. Diagram mode provides an easy-to-use tool for business users to create layouts of workflow definitions, including documentation to describe business processes.
Removed root user restriction

Previous releases required that the user installing Application Engine have root permission. This requirement no longer exists.
Expanded single sign-on support

Application Engine supports Kerberos/SPNEGO Single Sign On (SSO) using BEA WebLogic Server 10 and IBM WebSphere V 7.
Improved language support

Application Engine no longer requires language packs to provide a translated Workplace user interface. In addition to English, this release provides the Workplace user interface in the following languages.
Language
Locale
Language
Locale - 16 -
IBM FileNet P8 4.5 Release Notes Whats New Arabic Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Dutch Finnish French German Italian AR BG CA zh-CN zh-TW HR CS NL FI FR DE IT Japanese Korean Polish Portuguese (Iberian) Portuguese (Brazilian) Romanian Russian Swedish Slovak Spanish Thai JA KO PL PT pt-BR RO RU SV SK ES TH
NOTE Separate media are available for each languages Application Integration and File Tracker installation programs.
Business Activity Monitor

New location for installation instructions
The installation guide was removed from the IBM FileNet Business Activity Monitor (BAM) Projects. The new installation instructions are available in the BAM Quick Start Guide.
Application name changes

The following product names have been changed, and the product documentation is updated accordingly. FileNet Application Workbench is changed to IBM Cognos Now! Workbench. FileNet Business Activity Monitor is changed to IBM FileNet Business Activity Monitor. FileNet BAM software is changed to IBM FileNet BAM Projects. FileNet BAM Dashboard is changed to IBM Cognos Now! Dashboard. FileNet Operational Dashboard is changed to IBM Cognos Now! Dashboard. FileNet BAM Workbench is changed to IBM Cognos Now! Workbench. FileNet Application Workbench is changed to IBM Cognos Now! Workbench. FileNet BAM Server Reference is changed to IBM Cognos Now! Streaming Server Reference. FileNet BAM Web application is changed to IBM Cognos Now! Web application. FileNet Activity Suite is changed to IBM Cognos Now! FileNet Business Activity Monitor (BAM) Documentation CD is changed to IBM FileNet BAM Projects Documentation CD.
Changes to the "Import Out-of-the-box configuration project" topic

The "Import the pre-configured Business Activity Monitor objects" topic is changed to "Import Outof-the-box configuration project." - 17 -
IBM FileNet P8 4.5 Release Notes Whats New The "Configure a context data source to access data from Process Analyzer section is changed to "Configure a JDBC agent." "Configure a JDBC agent" includes SQL Server 2005 examples. The "Other application servers" and "Advanced IBM FileNet BAM functionality" sections have been added.
New upgrade procedure

A procedure for upgrading an existing IBM FileNet BAM Project installation has been added. For more information, see FileNet P8 Documentation > Expansion Products > Business Activity Monitor > Upgrade an existing IBM FileNet BAM Projects installation.

In addition to English, BAM provides the user interface in the following languages: Language French German Locale FR DE
The French and German sample project files are located on the media in the following directories:
\Projects\DE \Projects\FR
Terminal Release of BAM

Business Activity Monitor 4.5.0 is the terminal release of this product. P8 4.5.1 provides direct CognosNow! integration.
Content Engine
Support for IBM System Storage DR550
As of fix pack P8CE-4.5.0-002, Content Engine supports the IBM DR550 as a fixed content system in support of a FileNet fixed storage area. This release supports DR550 devices that use magnetic disk storage only. The DR550 device is controlled through the use of IBM Tivoli Storage Manager (TSM). See FileNet P8 Platform Help for additional information: FileNet P8 Documentation > System Administration >
Content Engine Administration > Content storage > Fixed storage areas > About IBM Tivoli Storage Manager (DR550).
Improved configuration and deployment during installation

The new Configuration Manager tool is used to configure and deploy Content Engine on an application server. Configuration Manager can be run either from a command line or from a graphical user interface. It takes the place of manual configuration and deployment steps previously performed using the application server administrative interface.
Improved Enterprise Manager functionality

Content Consistency Checker performance improved. Previously you created Index Areas using a dialog in Content Based Retrieval (CBR). The dialog has been replaced with the Create an Index Area wizard for greater consistency with other creation tasks. - 18 -
IBM FileNet P8 4.5 Release Notes Whats New You can now use the Create Object Store wizard to revise the object store creation schema script. The AddOns installation process is more visible, giving you more flexibility in choosing which AddOns to install when the object store is created. Throughout Enterprise Manager, AddOns are now consistently listed by their new display names. You can now apply non-versioning security templates to documents, folders, and custom objects. You now can control whether to save the Original and Current snapshots (or none at all) when auditing events. You can restrict membership to configured realms. In the Directory Configuration properties, you now can restrict group lookups to configured realms only.

Previous releases required that the user installing Content Engine have root permission. This requirement no longer exists.
Support for DITA Rendition Engine

The Darwin Information Typing Architecture (DITA) Rendition Engine, based on the DITA specification 1.1, uses the DITA Open Toolkit for rendering. The DITA Rendition Engine publishes DITA content (topics and maps) into PDF.

In addition to English, Content Engine provides the user interface for the Content Engine properties for Workplace and Workplace XT in the following languages. Language * Arabic * Bulgarian * Catalan Chinese (Simplified) Chinese (Traditional) * Croatian * Czech Dutch Finnish French German Italian Locale AR BG CA zh-CN zh-TW HR CS NL FI FR DE IT Language Japanese Korean * Polish * Portuguese (Iberian) Portuguese (Brazilian) * Romanian Russian * Swedish * Slovak Spanish * Thai Locale JA KO PL PT pt-BR RO RU SV SK ES TH
* These languages are available only for Workplace.
FileNet Content Federation Services

Support for Content Manager OnDemand
Content Federation Services now supports Content Manager OnDemand as an external repository. Copyright IBM Corp. 2002, 2010 - 19 -
Integration with Content Engine

Content Federation Services supports Image Services and Content Manager OnDemand as part of the FileNet P8 Platform installation. Note that CFS support for Content Services, IBM Content Integrator, and other supported external repositories requires a separate installation. Content Federation Services supports IBM Content Integrator V8.5 (formerly Information Integrator Content Edition IICE).
FileNet P8 Documentation
Improved planning, preparation, and installation instructions
The IBM FileNet P8 documentation set provides a separate customer-oriented environment preparation guide, Plan and Prepare your Environment for IBM FileNet P8, which presents information that was previously included in the planning and preparation section of the IBM FileNet P8 Platform Installation and Upgrade Guide. The topics in this new guide are divided by administrator roles, including Application Server Administrator, Database Administrator, IT Administrator, Security Administrator, and P8 Administrator. The guide provides tasks for these roles to perform in the customer environment to prepare for the installation or upgrade of IBM FileNet P8 components. The documentation set also includes the Installation and Upgrade Worksheet (p8_worksheet.xls). The content of this file can be customized to match the customer's installation parameters, and further customized by role, so that each administrator at a customer site can configure and collect the data needed to complete the installation programs. Each row in the worksheet provides an entry for an installation, upgrade, or configuration field or parameter. Using the worksheet in conjunction with the Plan and Prepare Your Environment for IBM FileNet P8 guide can simplify the installation and upgrade process. The "Glossary" appendix at the end of the Plan and Prepare Your Environment for IBM FileNet P8 guide provides definitions for each of the non-obvious properties or parameters listed in the worksheet. The Plan and Prepare Your Environment for IBM FileNet P8 guide provides a section called "Upgrade Overview." This section presents staged upgrade scenarios in the form of flowcharts to help customers understand the ramifications of choosing a staged upgrade for their existing IBM FileNet P8 environment. The appendix "IBM FileNet P8 ports," in the Plan and Prepare Your Environment for IBM FileNet P8 guide, has been improved with descriptions and explanations of the required or default ports. The IBM FileNet P8 Installation and Upgrade Guide has been re-architected to clarify the sequence of tasks necessary to install a specific core component. In addition, all necessary tasks are inline for both new installations and upgrades, to prevent the need to flip to different sections of the book to complete a task. The procedures in the IBM FileNet P8 Installation and Upgrade Guide have been streamlined to provide required independent software vendor settings, but not the detailed instructions for how to configure vendor software such as application servers and databases. This will result in fewer instances of confusing or outdated instructions specific to these applications. Procedures for installing the Content Engine Client files on the Process Engine and Application Engine servers have been added to the IBM FileNet P8 Installation and Upgrade Guide. This information was formerly available in the Content Engine fix pack readme file. To support the new Content Engine Configuration Management tool, the "Configuration Manager reference" appendix has been added to the IBM FileNet P8 Installation and Upgrade Guide to provide reference information for the graphical-user-interface and command-line versions of the tool. To augment this documentation, rollover context-sensitive help has been added to the tool's graphical user interface to explain screen elements. - 20 -
New location for the upgrade instructions for custom applications

The "Upgrade Custom Applications" section of the IBM FileNet P8 Platform Installation and Upgrade Guide has been moved to the FileNet P8 Platform Help. See FileNet P8 Documentation > Developer Help > Upgrade Custom Applications.
IBM FileNet Connector for SharePoint Web Parts 2.2.1

IBM FileNet Connector for SharePoint Web Parts integrates with the Microsoft SharePoint basic content services offering, providing customers with an alternative user interface for enterprise managed content. SharePoint Web Parts 2.2.1 increases the capabilities and familiarity of the user interface for the SharePoint user.
New Features
Search templates, created in Workplace XT, are now opened within the SharePoint Web Parts environment. This allows users to leverage existing templates. Users can configure and save custom views in the Browse Web Part. Full-page display is available for the Browse Web Part (MOSS only). Users can view and manage their checked-out documents in a new Web Part. Users can perform additional actions on documents and folders, including deleting document versions, showing document hyperlinks, and showing the folders in which a document is filed. Document and folder security can be modified within SharePoint Web Parts.
Installation Improvements
Installer panels provide simplified installation steps and improved embedded assistance. Upgrades now allow the authentication method to be changed. For example, a FileNet credential store deployment can be changed to Windows Integrated Authentication (SSO). Installation and deployment across a SharePoint farm have been improved.
Usability and Accessibility

The user interface and online help are certified to meet IBM accessibility standards. Error messages have been entirely rewritten to provide users with additional information.
Available languages
The SharePoint Web Parts user interface and online help are now available in the nine non-English languages listed in the table. All translated documentation is included on the same media as the English documentation. Language Chinese (Simplified) Chinese (Traditional) French German Italian Locale zh-CN zh-TW FR DE IT Language Japanese Korean Portuguese (Brazilian) Spanish Locale JA KO pt-BR ES
- 21 -
Process Analyzer
Process Analyzer no longer requires language packs to provide a translated user interface. In addition to English, this release provides the user interface in the following language: Language Japanese Locale JA
Support for separate database servers

The Analysis Services server and the Process Analyzer Database server can now reside on different database servers.
Improved event log processing

Process Analyzer server can be configured to process events from specific isolated regions or specific event logs.
Process Engine
Process Engine Export and Import Utilities
Process Engine includes the following new command-line utilities to assist in exporting and importing application data from one Process Engine instance to another: The object utilities consist of two scripts, peObject_export and peObject_import, which assist you with exporting and importing queues, rosters, logs, user preferences, and system properties. The server utilities consist of two scripts, peServerConfig_export and peServerConfig_import, which assist you with exporting and importing server configuration information.
For more information about these utilities, see FileNet P8 Documentation > Application Deployment > Use the command line utilities > Process Engine Export/Import Utilities command-line reference.
New features for Process Designer

Membership in the appropriate access role enables specific functionality in Process Designer, including access to Diagram mode, to configuration and administration features, and to simulation features. Diagram mode in Process Designer provides an easy-to-use tool for business users to create layouts of workflow definitions, including document to describe business processes. These diagrams provide the starting point for collaboration between the business user and the IT developer to create the fully functional workflow definition in Design mode. Configuration and administration tools are integrated into Process Designer to minimize steps and tools required to create solutions. You can make configuration changes, such as adding queues and rosters. After you launch a workflow, you can access work items using Personal Work Manager, and you can use Process Administrator to administer the running workflow. You can insert new or existing scenarios into the workflow collection. A scenario can include one or more of the workflow definitions in the collection. In Process Designer, you can launch the scenario to create the simulation, and you can use Simulation Console to manage the simulation. Process Designer has a tabbed interface to support multiple workflow definitions, scenario definitions, configuration, roles, and in-basket panels. You can switch between the workflow - 22 -
IBM FileNet P8 4.5 Release Notes Whats New definitions, configuration settings, scenario definitions, and other options by clicking the appropriate tab. Support for Web 2.0 components (widgets) enables rapid development of BPM applications without coding. You can combine IBM ECM Widgets with industry and custom widgets to create process application interfaces. Use Process Designer and Process Configuration Console to define application spaces that specify security and roles, and in-baskets that provide a filtered view of tasks for users who fill a specific role in the process. This functionality is available as an optional expansion product. You can register step processors in Process Designer, as well as in Process Configuration Console. Menu items and locations have changed. o o o o o The File menu options apply to the workflow collection. Additionally, the Import Workflow option is no longer available; use the Insert command instead. The Edit menu now contains the Change Step Type and Create Map options, which were previously in the Tools menu. The View menu now supports the tabbed interface to enable you to select workflows, scenarios, the Configuration Console, Roles, and In-baskets. The Action menu items apply to the individual workflow definition or scenario on the selected tab. It also contains Workflow Properties, and print options. The Tools menu now provides access to Personal Work Manager, Process Administrator, and Simulation Console, if you are a member of the appropriate access roles. The tools that were previously on the Tools menu have been moved to the Edit, Action or Settings menus. The Help menu provides access to the online help and the tutorials. Options that were available in the Workflow Collection dialog box are now available on the View, File, and Actions menus or on the Workflow Properties > Advanced tab.
o o
New features for Process Configuration Console

You can export all Process Engine settings or select specific isolated regions, queues, rosters, and event logs to XML. Support for Web 2.0 components (widgets) enables rapid development of BPM applications without coding. You can specify application spaces, roles, and in-baskets in Process Configuration Console.
Improved accessibility
Process Administrator and Process Configuration Console options can now be accessed using the keyboard or assistive software, such as screen readers.
New Content Extended Operations

New Content Extended (CE) Operations methods are available to manipulate documents and folders in a repository.
Process Simulator
Process Simulator no longer requires language packs to provide a translated user interface. In addition to English, this release provides the user interface in the following languages: Copyright IBM Corp. 2002, 2010 - 23 -
IBM FileNet P8 4.5 Release Notes Whats New Language Czech French German Locale CS FR DE Language Italian Japanese Spanish Locale IT JA ES
Records Manager
New auto-destroy feature
Records Manager introduces the auto-destroy feature that, when configured, automatically deletes records at the end of their retention schedule without involving workflow functionality.
Container-managed authentication and single sign-on

Records Manager can now be deployed in a container-managed authentication environment and in a single sign-on (SSO) environment. For more information about supported SSO software, see IBM FileNet P8 Hardware and Software Requirements.
New Declassification Sweep utility

Declassification Sweep is a new Records Manager utility that alters the date on which a classified record will be declassified based on a pre-defined declassification timeframe.
New report for entities due for an interim transfer

Records Manager Disposition Sweep has a new parameter that generates a text file of entities that are due for an interim transfer by a specified date.

The Records Manager user interface is multilingual, and users can select a language based on the browser locale, which is now consistent with FileNet P8 Workplace and Workplace XT. The language pack content is now included in the English installation program. This eliminates the need to download and run a separate language pack. The installation and configuration instructions for non-English environments are now integrated into the IBM FileNet Records Manager Installation and Upgrade Guide. The following table lists the available languages for the user interface. Language Arabic Catalan Chinese (simplified) Chinese (traditional) Czech Dutch Finnish French Locale AR CA ZH_CN ZH-TW CS NL FI FR Language German Italian Japanese Korean Portuguese (Iberian) Portuguese (Brazilian) Spanish Locale DE IT JA KO PT PT-BR ES
- 24 -
Customizable report templates

Records Manager reports can be customized and translated. This can be accomplished in multilingual environments by customizing and translating the report templates so that the reports can be created in any of the available languages.
Improved multi-threading process control

You can now specify the number of simultaneous processing threads that Records Manager can use when running: Hold Sweep Disposition Sweep Auto-destroy
Improved object store configuration wizard

The Records Manager Configure tab now provides the capability to configure new object stores for Records Manager use, and make upgrades to existing Records Manager object stores.
New system-to-system transfers utility

The Records Manager Transfer Tool is a new Records Manager stand-alone utility that transfers active records and folders to an external system for permanent archiving.
New workflows with mapping

Records Manager has three new workflows that you can associate with a disposition action: Export transfer with mapping Interim transfer with mapping Two-step transfer with mapping
These new workflows allow you to select a transfer mapping that Records Manager uses during the disposition action.
Rendition Engine
Updated rendering engine
Rendition Engine is now based on Liquent Enterprise Services (LES) 3.0.
Expanded application support

Rendition Engine now supports Microsoft Office 2007.
Expanded platform support

Rendition Engine now supports installations on the following components: 64-bit Windows 2003 Oracle 11
- 25 -
Automated Vista Domain handling

The server on which the Rendition Engine is installed will automatically be added as a COM Repository to a new Vista domain if none exists in the database location specified, or else added to the existing Vista domain.
New default installation location

The default installation location is: C:\Program Files\FileNet\RenditionEngine\Liquent
Workplace XT 1.1.3
Improved user interfaces
Entry templates and the Add Folder wizard have been updated with the same easy-to-use steps and controls as the Add Document wizard. Adding documents using drag-and-drop opens an entry template where appropriate. The folder Properties page has been updated with the same easy-to-use features as the document Properties page. The Advanced Search page uses improved folder and class selection interfaces. The Move, File, and Unfile actions have been updated to use the new Workplace XT look-andfeel. The current folders contents can be easily refreshed directly from the toolbar. Bookmarked folders, stored searches, and search templates open using the standard Workplace XT interface.
Folder customizations
An administrator can customize the displayed columns and default sort order for each folder. An administrator can associate entry templates with specific folders and specific document types.
Expanded support for other repositories

Documents stored on a Content Manager OnDemand (CMOD) server can be viewed using CMOD viewers. Documents stored on a CM8 server can be viewed.
Improved integration with Office applications

Application Integration BCS integrates Microsoft Office 2007 applications and Outlook with Workplace XT. Integrated Office applications and Outlook provide access to object stores and some of the Workplace XT features, allowing you to perform and complete your document management tasks without leaving the applications. New features include: o o o o o o Add documents and e-mails using entry templates. Browse and search for documents. Add documents and folders to the Favorites folder. View and modify document properties. Open documents recently accessed from an object store. Check documents in and out of an object store. - 26 -
IBM FileNet P8 4.5 Release Notes Whats New o o o E-mail a link or copy of a document. Access document management actions and tools from the familiar Microsoft Office 2007 Ribbon. Control Application Integration BCS behavior using site preferences.
Single sign-on (SSO) using Kerberos is supported with integrated Office applications.
Improved search capabilities

The Advanced Search page has been improved to allow keyword searches in addition to property searches. Keyword search results can, in many cases, be resorted by columns in the search results.

Installation program panels have been updated to make choices clearer and to simplify the installation process. The Installation and Upgrade Worksheet (p8_worksheet.xls) includes rows for Workplace XT installation program values. You can use the worksheet when planning and preparing for your Workplace XT installation as part of a FileNet P8 environment. The Workplace XT installation program and the client installation programs for Process Engine and Content Engine allow you to defer creating a deployment file. Deferring this step allows you to bypass creating the deployment file for each installation program. Instead, the last installation program can create the file, or you create the file manually before you deploy.

Previous releases required that the user installing Workplace XT have root permission. This requirement no longer exists.
New access role

The new PWDiagram access role controls access to Diagram mode in Process Designer. Diagram mode provides an easy-to-use tool for business users to create layouts of workflow definitions, including document to describe business processes.

In addition to the 11 languages already supported, Workplace XT provides a translated user interface for the following new languages:
Language Finnish Russian
Locale FI RU
NOTE Separate media are available for each languages Application Integration and File Tracker installation programs.
Other improvements
The Send Mail action is integrated with the users Lotus Notes or Microsoft Outlook e-mail client. The values of multi-valued properties are displayed in the list view. - 27 -
IBM FileNet P8 4.5 Release Notes Whats New Improved error messages when configuring site preferences help administrators to resolve configuration errors more easily. Improved error messages in Application Integration BCS provide more assistance to the user when resolving errors.
Workplace XT 1.1.4
Improved document management support
The following actions can now be performed on multiple documents: o o o o o Add Checkin Checkout and download Checkout Download.
Modify properties for multiple documents in a single step.

Design entry templates that restrict adding documents with the same file name. Use the new Check out and download action on multiple documents. View the hierarchical relationship of each document in a compound document and perform actions on the documents. View system properties from the standard Workplace XT property page. WebDAV is integrated with Workplace XT. Sort documents by MIME type in the Browse view. Configure the confirmation page to be dismissed automatically after completing a process. Add folders with documents by using drag-and-drop.
File Tracker
File Tracker is now downloaded automatically and tracks documents on a local workstation after they are checked out from an object store. File Tracker supports Internet Explorer and Firefox. Use the environment variable and qualified path site preference settings to indicate the location where the local file is checked out and downloaded. Documents can now be downloaded into the same hierarchical folder structure in which the documents were stored in an object store. File Tracker supports documents that are added using drag-and-drop. Those documents can also be deleted from your local system as part of the add process.
Improved support for Content Manager OnDemand (CMOD) server

An administrator can use the OnDemand Web Enablement Kit to customize MIME types, allowing users to view various documents with different viewers. - 28 -
IBM FileNet P8 4.5 Release Notes Whats New An administrator can configure the trace logging settings that are used by the Content Manager OnDemand Java API.
Application Integration BCS

Improved search capabilities
Perform full-text and property-based searches. Search on properties, content, or properties and content together. The search page now provides smart controls to improve the user experience. Save and delete multiple searches. Define a saved search as the default search. Sort search results.

Access the Add and Check in actions from menus. Use drag-and-drop to move and file both folders and documents. Use drag-and-drop or Send file as link or Send file as copy actions to add documents as attachments or links to an e-mail message. Use drag-and-drop to add one or more e-mails to an object store. Cut, copy, and paste both documents and folders. View security settings for both folders and documents. Adding documents opens an entry template where appropriate.
Folder customizations
Users can now use entry templates that are associated with specific folders and specific document types. An administrator must use Workplace XT to associate the entry templates with folders and document types.

During an upgrade process, Workplace XT migrates folder preferences defined in a previous version. During and installation or upgrade process, Workplace XT detects prerequisite AddOns and lists the AddOns that need to be installed.

The Workplace XT and Application Integration BCS user interfaces and online help are now available in the non-English languages listed in the table. All translated documentation is included on the same media as the English documentation. Language Chinese (Simplified) (Group 1) Chinese (Traditional) Locale zh-CN zh-TW Language Japanese (Group 1) Korean (Group 1) Locale JA KO
- 29 -
IBM FileNet P8 4.5 Release Notes Whats New (Group 1) Dutch Finnish French (Group 1) German (Group 1) Italian (Group 1) NL FI FR DE IT Portuguese (Brazilian) (Group 1) Russian Spanish (Group 1) Swedish Turkish pt-BR RU ES SV TR
Development Tools
Content Java API Compatibility Layer
Encryption Algorithm Change
The use of the Blowfish encryption algorithm for encrypting session tokens is replaced by the FIPS 140compliant Advanced Encryption Standard (AES) algorithm. When testing encryption of credentials tokens during application development, you can run the MakeCryptoKeys utility from a command line to manually generate one or more encryption keys. Under the Blowfish algorithm, the range of allowed key sizes was 8 to 448 in increments of 8 bits. Allowed key sizes for AES are 128 (the default), 192, or 256 bits. If you specify a size greater than 256 bits, the MakeCryptoKeys utility generates a warning and reduces the value to 256 bits. Values that are not exactly 128, 192, or 256 are rounded down. See the Known Issues section of this Release Notes document for additional information, including updates to the MakeCryptoKeys class documentation (ecmdb00755693).
Content Engine Object Model Changes

This section lists the Content Engine classes, interfaces, and properties that have been added in this release as well as the properties that have been deprecated. Note that there are a number of new exposed interfaces and propertiesprimarily those that are replication-relatedthat currently are not supported. The replication-related interfaces and properties that are supported are those used for Content Federation Services (CFS) functionality.
New classes and interfaces

The following classes and interfaces have been added to the Content Engine object model.
Class/interface CMODApplicationGroup
Summary description Represents an IBM Content Manager OnDemand (CMOD) application group that can be configured for content federation. An application group is a collection of one or more OnDemand applications with common indexing and storage management attributes. A collection interface that represents a collection of CMODApplicationGroup objects. - 30 -
CMODApplicationGroupSet
IBM FileNet P8 4.5 Release Notes Whats New CMODFixedContentDevice Represents the description of an IBM Content Manager OnDemand (CMOD) external fixed content storage device. A collection interface that represents a collection of CMODFixedContentDevice objects. A replication interface that represents an IBM Content Manager OnDemand (CMOD) external repository that is capable of federating content. A collection interface that represents a collection of CMODRepository objects. A constants class that provides a set of constants that specifies illegal containment name characters. A replication interface that represents repositories that are external to the Content Engine server and are capable of federating content. This interface is the base for subinterfaces representing external repositories that are capable of federating content. A collection interface that represents a collection of ContentFederatingRepository objects. Not supported. Not supported. Represents site-specific connection data for a DITA Rendition Engine that is referenced by a publishing configuration. (A DITA Rendition Engine is one that uses a DITA Open Toolkit deployment for publishing documents.) A collection interface that represents a collection of DITARenditionEngineConnection objects. A replication interface that represents the mechanism for mapping an external class or property to a corresponding Content Engine class or property. This interface is the base for subinterfaces representing external class and property aliases. A collection interface that represents a collection of ExternalAlias objects. A replication interface that represents the mechanism for mapping an external class to a corresponding Content Engine class. A collection interface that represents a collection of ExternalClassAlias objects. A replication interface that represents the description of a class in an external repository of which an object
CMODFixedContentDeviceSet
CMODRepository
CMODRepositorySet
ContainmentName ContentFederatingRepository
ContentFederatingRepositorySet
DirectoryConfigurationCA DirectoryConfigurationCAList DITARenditionEngineConnection
DITARenditionEngineConnectionSet
ExternalAlias
ExternalAliasList
ExternalClassAlias
ExternalClassAliasList
ExternalClassDescription
- 31 -
IBM FileNet P8 4.5 Release Notes Whats New instance can be replicated. ExternalClassDescriptionSet A collection interface that represents a collection of ExternalClassDescription objects. A replication interface that represents the identity of a replicated object in an external repository. A collection interface that represents a collection of ExternalIdentity objects. Not supported. Not supported. A replication interface that represents the mechanism for mapping an external class property to a corresponding Content Engine class property. A collection interface that represents a collection of ExternalPropertyAlias objects. A replication interface that represents the description of a class property in an external repository. A collection interface that represents a collection of ExternalPropertyDescription objects. A replication interface that represents repositories that are external to the Content Engine server. This interface is the base for subinterfaces representing external repositories. A collection interface that represents a collection of ExternalRepository objects. A replication interface that represents an IBM FileNet Image Services external repository that is capable of federating content. A collection interface that represents a collection of ImageServicesRepository objects. A constants class that provides a set of constants that specifies the audit recording level of the source object for an event of type ObjectChangeEvent. A replication interface that represents an object store participant of a replication group. A collection interface that represents a collection of ObjectStoreParticipant objects. A replication interface that is the base for subinterfaces representing classes of which an object instance can be replicated. Represents the class definition (mutable class - 32 -
ExternalIdentity ExternalIdentityList
ExternalParticipant ExternalParticipantList ExternalPropertyAlias
ExternalPropertyAliasList
ExternalPropertyDescription ExternalPropertyDescriptionList
ExternalRepository
ExternalRepositorySet
ImageServicesRepository
ImageServicesRepositorySet
ObjectStateRecordingLevel
ObjectStoreParticipant ObjectStoreParticipantList
Replicable
ReplicableClassDefinition Copyright IBM Corp. 2002, 2010
IBM FileNet P8 4.5 Release Notes Whats New metadata) of classes of which an object instance can be replicated. ReplicableClassDefinitionSet A collection interface that represents a collection of ReplicableClassDefinition objects. A collection interface that represents a collection of Replicable objects. Represents configuration settings for the replication components of a server. A collection interface that represents a collection of ReplicationConfiguration objects. A constants class that provides a set of constants that specify the direction in which instances of an external class, which is represented by an ExternalClassDescription object, can be replicated between a Content Engine object store and an external repository. Not supported. Not supported. A replication interface that represents the journal record of an operation on a replicated object for outbound replication. A collection interface that represents a collection of ReplicationJournalEntry objects. Not supported. Not supported. A replication interface that is the base for subinterfaces representing external repository or object store participants in a replication group. A collection interface that represents a collection of ReplicationParticipant objects. A replication interface that is the base for subinterfaces representing object stores and external repositories. A collection interface that represents a collection of Repository objects. A constants class that provides a set of GUID constants that identify the AddOns provided by the system.
ReplicableSet
ReplicationConfiguration ReplicationConfigurationList
ReplicationDirection
ReplicationGroup ReplicationGroupSet ReplicationJournalEntry
ReplicationJournalEntrySet
ReplicationJournalStatus ReplicationMode ReplicationParticipant
ReplicationParticipantList
Repository
RepositorySet
SystemAddOnId
- 33 -
New properties
The following properties have been added to the Content Engine object model. Property AliasDirection Applies to ExternalAlias ExternalClassAlias ExternalPropertyAlias ApplicationGroupNumber CMODApplicationGroup Summary description A ReplicationDirection constant that indicates the direction in which the mapping applies for this class or property alias. The unique number identifying this IBM Content Manager OnDemand (CMOD) application group. A CMODApplicationGroupSet object containing the set collection of application groups defined in the IBM Content Manager OnDemand (CMOD) external repository associated with this CMOD fixed content device. A value for the IBM Content Manager OnDemand (CMOD) external repository associated with this CMOD fixed content device that indicates the language in which messages will be output. The password for the security principal identified by the CMODUserName property. The port number on which the IBM Content Manager OnDemand (CMOD) server associated with this CMOD fixed content device is listening. The name of the IBM Content Manager OnDemand (CMOD) server with which this CMOD fixed content device is associated. The amount of trace information that will be gathered by the IBM Content Manager OnDemand (CMOD) external repository associated with this CMOD fixed content device. The name of the security principal for accessing the IBM Content Manager OnDemand (CMOD) server associated with this CMOD fixed content device.
CMODApplicationGroups
CMODFixedContentDevice
CMODLanguage
CMODPassword
CMODPort
CMODServerName
CMODTraceLevel
CMODUserName
- 34 -
IBM FileNet P8 4.5 Release Notes Whats New ClassFamily ExternalClassDescription The symbolic name of the Content Engine root class (for example, "Document") to which the class described by this external class description corresponds. The identity of the external class described by this external class description, external class alias, or external property alias. The database transaction timeout in seconds for DITA-specific publishing requests. The fully qualified path to the directory where the DITA Open Toolkit is installed. The optional Java Virtual Machine (JVM) arguments that will be used to invoke the DITA Open Toolkit when publishing DITA content. The DITARenditionEngineConnection object used by this publishing configuration. The DITARenditionEngineConnection Set object that lists the DITA Rendition Engine connections for this domain. The fully qualified path to the working directory where DITA component documents will be downloaded from the Content Engine server for publishing via the DITA Open Toolkit. The location within the database in which index information is to be created and referenced. The location within the database in which Large Object (LOB) data is to be created and referenced. The location within the database in which new tables are to be created and referenced. The date and time that this document was checked in.
ClassIdentity
ExternalClassAlias ExternalClassDescription ExternalPropertyAlias
DITADatabaseTimeout
DITARenditionEngineConnection
DITAHome
DITAJVMArguments
PublishingConfiguration
DITARenditionEngineConnections
Domain
DITAWorkingDirectory
DatabaseIndexStorageLocation
ObjectStore
DatabaseLOBStorageLocation
ObjectStore
DatabaseTableStorageLocation
ObjectStore
DateCheckedIn
CodeModule Document PublishTemplate
- 35 -
IBM FileNet P8 4.5 Release Notes Whats New Versionable WorkflowDefinition XMLPropertyMappingScript DestinationRepository DuplicateSuppressionEnabled ReplicationJournalEntry DatabaseStorageArea FileStorageArea DynamicGroupMemberAttribute DynamicGroupObjectClass DynamicGroupQueryAttribute ExternalAliases DirectoryConfigurationCA DirectoryConfigurationCA DirectoryConfigurationCA DocumentClassDefinition PropertyDefinition PropertyDefinitionBinary PropertyDefinitionBoolean PropertyDefinitionDateTime PropertyDefinitionFloat64 PropertyDefinitionId PropertyDefinitionInteger32 PropertyDefinitionObject PropertyDefinitionString ReplicableClassDefinition VersionableClassDefinition ExternalClassDescriptions CMODRepository ContentFederatingRepository ExternalRepository ImageServicesRepository ExternalObjectIdentity ExternalIdentity An ExternalClassDescriptionSet object containing the set collection of ExternalClassDescription objects associated with this external repository. The unique identity of this external replica object, relative to the external repository in which it belongs. An ExternalPropertyDescriptionSet object containing the set collection of ExternalPropertyDescription objects associated with this external class description. An ExternalIdentityList collection of the ExternalIdentity objects representing the identities of replicas of this object in external - 36 Not supported. Not supported. Not supported. An ExternalPropertyAliasList collection of the external aliases defined for this property definition or replicable class definition. Not supported. Not supported.
ExternalPropertyDescriptions
ExternalClassDescription
ExternalReplicaIdentities
Action ActionConsumer Annotation
IBM FileNet P8 4.5 Release Notes Whats New ChoiceList ClassDefinition ClassSubscription ClassWorkflowSubscription CodeModule ComponentRelationship Containable ContainmentRelationship CustomObject Document DocumentClassDefinition DocumentClassificationAction DocumentLifecycleAction DocumentLifecyclePolicy DynamicReferentialContainmentRelat ionship EventAction EventClassDefinition Folder InstanceSubscription InstanceWorkflowSubscription Link PropertyTemplate PropertyTemplateBinary PropertyTemplateBoolean PropertyTemplateDateTime PropertyTemplateFloat64 PropertyTemplateId PropertyTemplateInteger32 PropertyTemplateObject PropertyTemplateString PublishStyleTemplate PublishTemplate ReferentialContainmentRelationship Relationship Replicable Copyright IBM Corp. 2002, 2010 - 37 repositories.
IBM FileNet P8 4.5 Release Notes Whats New ReplicableClassDefinition SecurityPolicy StoragePolicy SubscribableClassDefinition Subscription Versionable VersionableClassDefinition WorkflowDefinition WorkflowEventAction XMLPropertyMappingScript ExternalRepositories Domain An ExternalRepositorySet object containing the set collection of ExternalRepository objects associated with this domain. The external repository associated with this replicated object, class or property alias, or external repository participant of a replication group.
ExternalRepository
ExternalAlias ExternalClassAlias ExternalIdentity ExternalParticipant ExternalPropertyAlias
FcpPoolIdleTimeoutSeconds
CMODFixedContentDevice CenteraFixedContentDevice FixedContentDevice GenericFixedContentDevice IICEFixedContentDevice IMFixedContentDevice SnapLockFixedContentDevice TivoliFixedContentDevice (as of fix pack P8CE-4.5.0-002)
The number of seconds an idle connection can remain in the pool before being eligible to be closed and removed from the pool.
FcpPoolMaxInUse
CMODFixedContentDevice CenteraFixedContentDevice FixedContentDevice GenericFixedContentDevice IICEFixedContentDevice IMFixedContentDevice SnapLockFixedContentDevice TivoliFixedContentDevice (as of fix
The maximum number of concurrent connections to the fixed content device.
- 38 -
IBM FileNet P8 4.5 Release Notes Whats New pack P8CE-4.5.0-002) FcpPoolMaxWaitSeconds CMODFixedContentDevice CenteraFixedContentDevice FixedContentDevice GenericFixedContentDevice IICEFixedContentDevice IMFixedContentDevice SnapLockFixedContentDevice TivoliFixedContentDevice (as of fix pack P8CE-4.5.0-002) FcpPoolPreferredSize CMODFixedContentDevice CenteraFixedContentDevice FixedContentDevice GenericFixedContentDevice IICEFixedContentDevice IMFixedContentDevice SnapLockFixedContentDevice TivoliFixedContentDevice (as of fix pack P8CE-4.5.0-002) GroupUniqueIDAttribute GroupUniqueIDAttributeIsBinary HeldUntilDate IICEConfigurationServerURL DirectoryConfigurationCA DirectoryConfigurationCA ReplicationJournalEntry IICEFixedContentDevice Not supported. Not supported. Not supported. The URL that needs to be provided to the IBM Content Integrator API in order for it to locate the Configuration Server. Not supported. Not supported. Not supported. Not supported. Not supported. The direction in which the external property described by this external property description can be mapped for replication with respect to a Content Engine property. Not supported. The preferred size of the fixed provider pool. The maximum number of seconds to wait for a connection once the FcpPoolMaxInUse limit has been reached.
InboundBatchSize InboundBusyWaitInterval InboundDispatcherEnabled InboundIdleWaitInterval LastFailureReason MappableDirection
ReplicationConfiguration ReplicationConfiguration ReplicationConfiguration ReplicationConfiguration ReplicationConfiguration ExternalPropertyDescription
MaxInboundWorkers
ReplicationConfiguration
- 39 -
IBM FileNet P8 4.5 Release Notes Whats New MaxOutboundWorkers ObjectStateRecordingLevel ReplicationConfiguration AuditDefinition Not supported. The audit recording level of the source object for an event of type ObjectChangeEvent. (The source object is the object on which the event is fired.) An object representing the object store in which the object resides. The default SQL script to use when creating object stores within a DB2 database. The default SQL script to use when creating object stores within a Microsoft SQL Server database. The default SQL script to use when creating object stores within an Oracle database. Not supported. Not supported. Not supported. Not supported. Not supported. The identity of the external property described by this external property description or external property alias. The encryption key for this isolated region. The direction in which instances of the external class described by this external class description can be replicated. Provider-specific data for this external replica object. A ReplicationGroup object representing the replication group to which this replicable object belongs.
ObjectStore ObjectStoreSchemaDB2
ObjectStoreParticipant Domain
ObjectStoreSchemaMSSQL
Domain
ObjectStoreSchemaOracle
Domain
OutboundBatchSize OutboundBusyWaitInterval OutboundDispatcherEnabled OutboundIdleWaitInterval PartnerObjectStore PropertyIdentity
ReplicationConfiguration ReplicationConfiguration ReplicationConfiguration ReplicationConfiguration ExternalParticipant ExternalPropertyAlias ExternalPropertyDescription
RegionKey ReplicableDirection
IsolatedRegion ExternalClassDescription
ReplicationData ReplicationGroup
ExternalIdentity Action ActionConsumer Annotation ChoiceList ClassDefinition ClassSubscription ClassWorkflowSubscription CodeModule
- 40 -
IBM FileNet P8 4.5 Release Notes Whats New ComponentRelationship Containable ContainmentRelationship CustomObject Document DocumentClassDefinition DocumentClassificationAction DocumentLifecycleAction DocumentLifecyclePolicy DynamicReferentialContainmentRelat ionship EventAction EventClassDefinition Folder InstanceSubscription InstanceWorkflowSubscription Link PropertyTemplate PropertyTemplateBinary PropertyTemplateBoolean PropertyTemplateDateTime PropertyTemplateFloat64 PropertyTemplateId PropertyTemplateInteger32 PropertyTemplateObject PropertyTemplateString PublishStyleTemplate PublishTemplate ReferentialContainmentRelationship Relationship Replicable ReplicableClassDefinition SecurityPolicy StoragePolicy SubscribableClassDefinition Subscription Copyright IBM Corp. 2002, 2010 - 41 -
IBM FileNet P8 4.5 Release Notes Whats New Versionable VersionableClassDefinition WorkflowDefinition WorkflowEventAction XMLPropertyMappingScript ReplicationGroups ReplicationMode Domain ExternalParticipant ObjectStoreParticipant ReplicationParticipant ReplicationOperation ReplicationParticipants ReplicationStatus ReplicationTraceFlags RestrictMembershipToConfiguredRealms ReplicationJournalEntry ReplicationGroup ReplicationJournalEntry TraceLoggingConfiguration DirectoryConfiguration DirectoryConfigurationAD DirectoryConfigurationAdam DirectoryConfigurationCA DirectoryConfigurationIBM DirectoryConfigurationNovell DirectoryConfigurationSunOne SearchDynamicGroup SuperclassIdentity DirectoryConfigurationCA ExternalClassDescription Not supported. The identity of the immediate superclass of the class described by this external class description. The IDs of AddOn objects superseded by this AddOn. The name of the object store that will participate in content federation in this IBM Content Manager OnDemand (CMOD) application group or to which this external class description belongs. Not supported. Not supported. Not supported. Not supported. Not supported. Not supported. Restricts a group membership search to within the realms configured in FileNet Enterprise Manager. Not supported. Not supported.
SupersededAddOnIds
AddOn UpgradeAddOn
TargetObjectStore
CMODApplicationGroup ExternalClassDescription
UserUniqueIDAttribute UserUniqueIDAttributeIsBinary
DirectoryConfigurationCA DirectoryConfigurationCA
Deprecated properties
The following properties on the IICEFixedContentDevice interface have been deprecated in this release: Copyright IBM Corp. 2002, 2010 - 42 -
IBM FileNet P8 4.5 Release Notes Whats New CFSNamingFactoryInitial CFSNamingProviderURL LockDownExceptionList LockDownPrincipal LockDownPrincipalType
In the Content Engine Java API, the accessor methods (that is, the get_property and set_property methods) for these properties have been deprecated.
Content Engine Java and .NET APIs

PStore tool
The PStore Tool has been added to this version of the Content Engine. For a client application using the Content Engine Web Service transport to open a TSL or SSL connection (HTTPS) with a server, the client must posses the server's public key, which is distributed in the form of a PKI certificate. PKI certificates are normally stored in a key store, from which a client application can retrieve them for use in establishing an SSL connection. However, because the Content Engine Java API uses Systinet libraries to open HTTPS connections, its PKI certificates must be located in a Systinet protected key store. Therefore, to configure a remote Content Engine Java API client to run over SSL, you must add the server's certificate to a Systinet protected key store by using the PStore Tool. The PStore Tool allows you to manipulate data in a Systinet protected store, which contains the user store and the key store. Using the PStore Tool, you can add, edit, and remove any user properties in the user store; or add, edit, and remove certificates and identities in the key store. The following steps describe how to use the PStore Tool to add the server's SSL connection PKI certificate to a Systinet protected key store: 1. Verify that the JAVA_HOME environment variable is set in your operating system. 2. In Windows, open a Command Prompt window or, in Unix, open a Terminal window. 3. In the Command Prompt or Terminal window, change the directory to %WASP_HOME%\bin (for example, C:\Program Files\FileNet\ContentEngine\wsi). 4. Enter the following command: PStoreTool --gui. 5. From the PStore menu, select Open From File, navigate to %WASP_HOME%\conf, then select the key store file: clientconf.xml. 6. From the Key Store menu, select Import Alias. From the dialog, select Type and specify TRUSTED_CERTIFICATE_ENTRY. 7. Click Load Certificate Chain, then select the certificate file. Click OK. 8. Close the PStore Tool.
Support for DITA Publishing

Support has been added for publishing Darwin Information Typing Architecture (DITA) documents using the DITA Open Toolkit as a rendition engine. To support this functionality, the following Content Engine API changes are introduced: A new class, DITARenditionEngineConnection, provides site-specific connection data used by the DITA Rendition Engine and includes the following DITA-specific properties: DITADatabaseTimeout, DITAHome, DITAJVMArguments, and DITAWorkingDirectory. For more information, see FileNet P8 Documentation > Developer Help > Content Engine Development > Java API - 43 -

Reference > DITARenditionEngineConnection or FileNet P8 Documentation > Developer Help > Content Engine Development >.NET API Reference > IDITARenditionEngineConnection.
A new property, DitaRenditionEngineConnection, has been added to the PublishingConfiguration class. For more information, see FileNet P8 Documentation >
Developer Help > Content Engine Development > Java and .NET Developer's Guide > Reference > Properties by Class > PublishingConfiguration Properties.
In addition, this release includes the new DITA Publishing Extension add-on, which does the following: Extends the Document class to represent DITA topics (DitaTask, DitaConcept, and so on), maps (DitaMap and DitaBookMap), and processing profiles (DitaVal). Extends the ComponentRelationship class to represent the relationships between files that make up a DITA project. Adds a document classifier (DITA classifier) that assigns the appropriate Document and ComponentRelationship subclasses when a DITA document is checked in. After all of the documents that make up a DITA project have been checked in and classified, the DITA project is represented as a FileNet P8 compound document.
Finally, the following items have been added to support DITA Publishing: DITA-specific publish style template transformation options that specify the output format, DITAVAL file and title (optional), and whether to do a "copy-only" operation (so that you can process the files outside of the FileNet P8 system). A DITA publish request handler that communicates with the DITA Open Toolkit to publish DITA documents.
For more information, see FileNet P8 Documentation > Developer Help > Content Engine Development > Java and .NET Developer's Guide > DITA Publishing > Publishing Concepts or FileNet P8 Documentation >
Developer Help > Content Engine Development > Java and .NET Developer's Guide > DITA Publishing > Publishing Concepts.
Support for separate database tablespaces during object store creation

Support has been added for creating separate tablespaces using a customized schema script when creating an object store. (ecmdb00669763) A new factory method, Factory.ObjectStore.createInstance(domain, admins, users, schemaScript) is introduced. Using this method, you can submit a custom schema script that the server will use during object store creation. Use of a custom schema script overrides the values of the new ObjectStore properties that specify storage location of tables, indexes, and LOB columns within the database: DatabaseTableStorageLocation, DatabaseIndexStorageLocation, and DatabaseLOBStorageLocation. The custom script is derived from a factory-generated default script, which can be retrieved from a property on the Domain object. The property name corresponds to the database type: ObjectStoreSchemaDB2, ObjectStoreSchemaMSSQL, and ObjectStoreSchemaOracle. Typical modifications that a database administrator (DBA) might make to the script include the distribution of the various tables, indexes, and Large Object (LOB) columns across different tablespaces. For more information, refer to "Working with ObjectStore Objects" in the Content Engine Java and .NET Developer's Guide (IBM FileNet P8 Documentation > Developer Help > Content Engine Development > Java and .NET Developer's Guide), and the Content Engine API reference help for Java or .NET (IBM FileNet P8 Documentation > Developer Help > Content Engine Development > Java [or .NET] API Reference).
Security and authentication

Enhanced flexibility in user/group lookup The capability to restrict user and group lookups to only those in configured realms has been added. (ecmdb00750099) Copyright IBM Corp. 2002, 2010 - 44 -
IBM FileNet P8 4.5 Release Notes Whats New The RestrictMembershipToConfiguredRealms property has been added to the DirectoryConfiguration class and its subclasses to specify whether or not to chase all group memberships during user and group lookup operations. For more information, see the Content Engine Java and .NET API reference help and FileNet P8
Documentation > Developer Help > Content Engine Development > Java and .NET Developer's Guide > Security Concepts > Role-Based Security.
Support for CMOD fixed content devices

This release provides support for IBM Content Manager OnDemand (CMOD) fixed content devices. As part of this support, the following new classes and collection classes are introduced: CMODApplicationGroup CMODApplicationGroupSet CMODFixedContentDevice CMODFixedContentDeviceSet CMODRepository CMODRepositorySet
The following properties are introduced:
CMODApplicationGroup.ApplicationGroupNumber CMODApplicationGroup.TargetObjectStore CMODFixedContentDevice.CMODApplicationGroups CMODFixedContentDevice.CMODLanguage CMODFixedContentDevice.CMODPassword CMODFixedContentDevice.CMODPort CMODFixedContentDevice.CMODServerName CMODFixedContentDevice.CMODTraceLevel CMODFixedContentDevice.CMODUserName
For more information, see FileNet P8 Documentation > Developer Help > Content Engine Development > Java API Reference or FileNet P8 Documentation > Developer Help > Content Engine Development >.NET API Reference.
New DateCheckedIn property

This release introduces a new property, DateCheckedIn, which has been added to the Versionable class. This property specifies the date and time that a document was last checked in. Settability of this property is read-only for most users. Users who have been granted privileged write access can set this property on a document while it is being checked in. Otherwise, the server sets this property automatically on a document when it is checked in. For more information, see FileNet P8 Documentation > Developer Help > Content Engine Development > Java API Reference or FileNet P8 Documentation > Developer Help > Content Engine Development > .NET API Reference.
- 45 -
New field for PersistenceType class

This release introduces a new field, OWN_TABLE, which has been added to the PropertyPersistence constant class. The PropertyPersistence class provides a set of constants that specify whether a property can be made persistent (that is, have its state stored in a database). The new OWN_TABLE field specifies that a property has a dedicated table in the database and therefore can be made persistent. This setting applies only to multi-valued scalar (non-object) properties and causes the server to store a property's values into a custom table, which is generated by the server when its property template is first assigned to a class definition as a property definition. For more information, refer to the Content Engine Java or .NET API reference help (IBM FileNet P8 Documentation > Developer Help > Content Engine Development > Java [or .NET] API Reference).
New auditing option

A new option is available to be able to audit with or without including object state snapshots. You can choose to record these snapshots so that you can review an object before and after an event occurs on that object. Snapshots are recorded in the audit log and written to the database. Storing the serialized object being audited consumes large object (LOB) storage in the database, so you might want to reduce or eliminate snapshot recording, depending on your requirements. You can set the new ObjectStateRecordingLevel property on the AuditDefinition object to specify which objects are recorded when an event fires for a source object change. You can specify that combinations of the original, pre-event object and the modified, post-event object be recorded, or you can suppress all source object recording. (ecmdb00554270)
New constant class for illegal characters in containment and folder names
A new constant, ContainmentName, is exposed in the APIs that provides a list of illegal characters for containment names and folder names. You can use the INVALID_CHARACTERS string to validate explicit containment and folder names before calling methods such as file (to file an object into a folder) or set_ContainmentName (to set an object's containment name) or set_FolderName (to name a new folder). (ecmdb00760311)
Content Engine Web Service

In Content Engine 4.0.x, Content Engine Web Service applications were limited to using the 3.5 WSDL, which supported Microsoft Visual Studio .NET 2003 with Web Services Enhancements (WSE) 2.0 SP2 and IBM Rational Application Developer 6.0. The 3.5 WSDL also supported DIME attachments and SOAP with inline, Base64 encoding for uploading and retrieving content data. In Content Engine 4.5, Content Engine Web Service applications can also use the 4.0 WSDL, which supports Microsoft Visual Studio 2005 with WSE 3.0. The 4.0 WSDL also supports Message Transmission Optimization Mechanism (MTOM) and SOAP with inline, Base64 encoding for uploading and retrieving content data. The 4.0 WSDL does not support IBM Rational Application Developer Java clients. In this release, the use of the Direct Internet Message Encapsulation (DIME) standard to upload and retrieve content is deprecated. Support for DIME attachments will be dropped in a future P8 release. Because DIME support is deprecated in this release, the DIMEAttachmentReference and DIMEContent elements in the 4.0 and 3.5 DIME endpoints are also deprecated. Therefore, any existing .NET client applications that use DIME should be ported to work with the 4.0 endpoints and use either MTOM or SOAP with inline, Base64 encoding for content upload and retrieval. The 4.0 WSDL contains all of the elements, operations, enumerations, subelements, and attributes that are included in the 3.5 WSDL and introduces the following new elements: ContentElementResponse ContentErrorResponse
- 46 -
IBM FileNet P8 4.5 Release Notes Whats New ContentRequestType ContentResponseType ElementSpecificationType GetContentRequest GetContentResponse TakeFederatedOwnershipAction UnevaluatedCollection
The 4.0 WSDL introduces a new operation, GetContent. The 4.0 WSDL introduces the following new enumerations: CollectionType ListOfObjectListMode StringEncodingType
In addition, new attributes and subelements have been added to existing elements in the 4.0 WSDL, as follows: CheckoutAction: ReservationProperties element and reservationClass attribute. CreateAction: objectId and versionSeriesId attributes. EnumOfObject: ParentReference attribute. FilterElementType: levelDependents attribute. ListOfObject: listMode attribute. ListOfString: StringEncodingType attribute. PropertyFilterType: levelDependents attribute. ObjectSetResponse: collectionType attribute. SingletonString: StringEncodingType attribute. WithObjectIdentityType: serializationDuplicate attribute.
For more information, see FileNet P8 Documentation > Developer Help > Content Engine Development > Web Service Developer's Guide. The documentation for the 4.0 WSDL is part of the P8 Platform Help. Documentation for the 3.5 WSDL is available on the IBM documentation Web site. Also available on the IBM documentation Web site are two new stand-alone Visual Studio 2005 sample applications, written in C# and Visual Basic, which use the new features of the 4.0 WSDL (including the GetContent operation). For more information about upgrading a 4.0.x application that uses the 3.5 WSDL to a 4.5 application that uses the 4.0 WSDL, see FileNet P8 Documentation > Developer Help > Upgrade Custom Applications.
IBM Enterprise Content Management Widgets

IBM Enterprise Content Management Widgets is a collection of widgets for use in rapid development of user interfaces for IBM FileNet P8 applications, which can lower the cost of building solutions. Using a graphical, browser-based tool, a designer drags and drops Enterprise Content Management (ECM) widgets and third-party widgets onto a Web page, sets the widgets' attributes, and wires the widgets together, defining inter-widget communications through the widgets' published and handled events. Wiring is automatic between most ECM widgets: the designer simply drops the ECM widgets onto the Copyright IBM Corp. 2002, 2010 - 47 -
IBM FileNet P8 4.5 Release Notes Whats New page to connect them. To connect ECM widgets to third-party widgets, the designer relies on an easy-touse wiring wizard. For this release, IBM Enterprise Content Management Widgets brings Business Process Management (BPM) functionality to Web pages mashed up (assembled) from diverse Internet and enterprise data sources. For example, a UI designer can easily combine ECM widgets with third-party widgets, such as stock tickers, location finders, and revenue trackers, to enhance the information value of a workflow. IBM Enterprise Content Management Widgets is tightly integrated with the IBM FileNet P8 platform, requiring the back end services of the Process Engine and Content Engine servers, and the middleware services of the Process Engine REST Service and Workplace XT. The Process Engine REST Service enables communications between Web clients and Process Engine, and Workplace XT provides access to documents and other content that can be incorporated into workflows.
Process Engine REST Service

The REST Service is implemented as a servlet in the IBM FileNet Workplace XT application. This is a general-purpose RESTful service, and is used by IBM Enterprise Content Management Widgets. For more information, see FileNet P8 Documentation > Developer Help > Process Engine Development > Developers Guide > Process Engine REST Service.
Content-Extended Operations for Component Integrator

The new ContentOperations class supports content-extended operations (CEOperations) for IBM Content Manager, as well as the IBM FileNet Content Engine. For more information, see FileNet P8 Documentation > Developer Help > Process Engine Development > Component Integrator Reference.
Process Engine Java API

New classes
The ContentOperations class has been added to support content-extended operations for the Component Integrator: The following classes have been added to support IBM Enterprise Content Management Widgets and the REST Service: VWApplicationSpaceDefinition VWRoleDefinition VWRole VWRole.WorkBasketReference VWWorkBasketDefinition VWWorkBasketFilterDefinition VWWorkBasketColumnDefinition VWWorkBasketCollectionDefinition VWWorkBasket VWWorkBasket.Column VWWorkBasket.Filter VWWorkBasket.QueryResults
- 48 -
New methods
The following methods have been added to existing classes to support IBM Enterprise Content Management Widgets and the REST Service: VWRole.fetchMyRole VWRole.fetchMyRoles VWQueueDefinition.addWorkbasketDefinition VWQueueDefinition.createWorkbasketDefinition VWQueueDefinition.createWorkbasketDefinitions VWQueueDefinition.createCopyOfWorkbasketDefinition VWQueueDefinition.deleteWorkbasketDefinition VWQueueDefinition.getWorkbasketDefinition VWQueueDefinition.getWorkbasketDefinitions VWQueueDefinition.getDeletedWorkbasketDefinition VWSystemConfiguration.createApplicationSpaceDefinition VWSystemConfiguration.getApplicationSpaceDefinition VWSystemConfiguration.getApplicationSpaceDefinitions VWSystemConfiguration.updateApplicationSpaceDefinition
Workplace Application Toolkit

The Workplace source code is no longer provided with the Application Engine software. However, it is available upon request. For information on how to obtain the Workplace source code, see FileNet P8
Documentation > Developer Help > Workplace Development > Workplace Application Toolkit Developer's Guide.
- 49 -
IBM FileNet P8 4.5 Release Notes Fixed APARs
Fixed APARs
IBM FileNet P8 4.5 incorporates the APAR fixes that were originally distributed in the following fix packs and interim fixes. For details, see the associated fix pack and interim fix readmes. 4023-P8AE-FP003 P8CE-4.0.1-009 P8CE-4.0.1-005.001 P8PA-4.0.1-002 P8PA-4.0.1-000.001 P8PE-4.0.2-002 P8PE-4.0.2-001.005 P8PS-4.0.0-006 P8RM-3.5.0-002 P8RM-3.5.0-002.001 P8RM-3.5.1-008 P8RM-3.7.0-004 P8RM-3.7.0-004.001 P8RM-4.0.0-002 P8RM-4.0.0-002.001 SPDL 2.2.0.1-FP001 SPWP 2.2.0.1-FP001 WPXT 1.1.3 FP005
Fixes for the following APARs are also included in the 4.5 release. These reflect fixed defects that are not included in one of the fix packs or interim fixes listed above. Content Engine APAR Name Defect ID PJ32587 743435 PJ34127 745504 PJ34276 753081 PJ34317 749262
PJ34333
Description Searches in Enterprise Manager Query Builder continue the query after the Maximum Results have already been reached. An Install Shield limitation requiring a root user for installation has been removed.
The count for how many sub-folders and objects are in a folder is no longer available from the General tab of the Folder. Unable to log into Enterprise Manager if password contains Unicode characters.
759316
The P8 4.0 upgrade tool fails because it does not locate FNUPGRADE_40_TeamCollaborationManagerAddOn.xml. The Content Engine 4.0 installer does not find WebSphere Profiles if they are not located in the default location. The context root of a Content Engine cannot be changed on an application server.
742961
743670 The 4.0.0b installer does not update the login-config.xml with FileNet security info when a DOCTYPE tag exists. Asynchronous Event Action Triggers can be slow on Content Creation Events. Copyright IBM Corp. 2002, 2010 - 50 -
746307
IBM FileNet P8 4.5 Release Notes Fixed APARs APAR Name Defect ID 748802 The BootstrapConfig JNDI change is not reflected in the GCD. 771564 Content Engine 4.0 Installer does not recognize the WAS profile if it is located other than default location. Description
687032
Records Manager APAR Name Defect ID PJ33216 PJ33306 Description A runtime exception occurs when navigating record categories
PJ33422
An error occurs when declaring a document as a record with Workplace XT 1.1.2
- 51 -
IBM FileNet P8 4.5 Release Notes Known limitations
Known limitations
Content Engine
Limitation on deployment of event action handlers in code modules.
As documented in the IBM FileNet P8 Content Engine Java and .NET API Developers Guide > Deploying Action Handlers, you can store an action handler as a CodeModule object in a Content Engine object store, or alternatively, you can specify the action handler in the Java Virtual Machine (JVM) classpath of the application server on which Content Engine is running. The referenced documentation provides guidelines for deploying event action handlers. In Release 4.5.0, the following additional guidelines and limitations are added for deploying event action handlers: For event handler code on the JVM classpath: the logic of Java classes that are referenced by the event action handler, and that are found in the classpath, can call into the Content Engine Java API. For event handler code in code modules: an event action handler in a code module can invoke Java classes that are on the JVM classpath as long as the logic of those classes in the classpath does not in turn call into the Content Engine Java API. Attempts to do so will fail. If you have designed such a deployment scenario, instead add the .class file that is making the API calls to the code module. The calls into the Content Engine Java API will then be supported. (ecmdb00761403)
CFS-CMOD
Federated OnDemand extended mime type documents are not displayed in the Workplace XT CMOD Viewer. A Save dialog box is displayed instead. For viewing all issues through XT, please refer to the XT release notes and XT documentation.
- 52 -
IBM FileNet P8 4.5 Release Notes Known Issues
Known Issues
This section describes: Independent software vendor issues related to P8 P8-specific known issues
Where applicable, each issue includes an associated APAR name and defect ID for reference and tracking purposes. For some entries, known issues might be cited in multiple sections. For instance, an installation problem involving Content Engine might appear in both the Installation and the Content Engine sections. As these known issues are fixed, they will be moved to a corresponding section under Resolved Known Issues. For an overview of the 4.5.0 known issues that have been fixed by a service pack, fix pack, or interim fix, see the associated readme.
Independent software vendor issues

Application servers
WebLogic
Description A custom client application is subject to a repeatable query failure under the following conditions: Content Engine is hosted by WebLogic 9.2 The client application depends upon the Content Engine EJB Transport You are using the WebLogic wlclient.jar file
If you encounter problems, restart the WebLogic server. This problem does not occur when using the weblogic.jar file. With WebLogic 9x, the Bulk Declare Service (BDS) can use either wlclient.jar or weblogic.jar. However, weblogic.jar is not compatible with Java Runtime Environment (JRE) 1.4. JRE 1.5.x is recommended. 789084 (WebLogic 9.x only) To fix the BEA CR298435 character corruption problem in FileNet P8, apply, WebLogic 9.2 MP1 on the WebLogic 9.x application server. See the Oracle BEA website here for details: http://e-cs.bea.com/wls/docs92/issues/known_resolved.html
WebSphere
Description When you start WebSphere 5.x with Records Manager, you might see errors similar to the following:
[10/11/07 16:55:27:720 EDT] c42b5 WebGroup E SRVE0020E: [Servlet Error]-[AdminServlet]: Failed to load servlet: java.lang.ExceptionInInitializerError at org.apache.axis.transport.http.AxisServlet.<clinit>(AxisServlet.java:103)
- 53 -
IBM FileNet P8 4.5 Release Notes Known Issues Description

at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at org.apache.axis.transport.http.AxisServletBase.class$(AxisServletBase.java:9 5) at org.apache.axis.transport.http.AxisServletBase.<clinit>(AxisServletBase.java :94) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance
These errors are internal to WebSphere and do not impact Records Manager or WebSphere functionality. They occur because a Records Manager setting causes incompatible JAR files due to the order in which the application files are loaded. A FileNet P8 Content Engine Web Service Extensible Authentication Framework (WS-EAF) failure occurs when authenticating with a custom Java Authentication and Authorization Service (JAAS) login module under WebSphere 7.0. When using WS-EAF in a WebSphere Application Server 7.0 environment, JAAS login authentication fails when stacking a custom login module. The failure can occur even if one of the login modules in the chain is configured as SUFFICIENT and the module successfully authenticates the user. The authentication failure can occur with the WebSphere Application Server Express, BASE, or Network Deployment editions. Resolution: From the Support and Downloads section of the IBM Support web site, install the iFix for APAR PK82390 (http://www01.ibm.com/support/docview.wss?rs=0&q1=PK82390&uid=swg1PK82390&loc=en _US&cs=utf-8&cc=us&lang=en). You can also install WebSphere Application Server 7.0 Fix Pack 5, which incorporates PK82390.
798158
Crystal Reports
Description When a report needs to query a large number of (for example, 12,000) folders or records, paginating the report, as well as exporting the report can take a long time (several minutes). This is due to the load on the Crystal Reports server.
Java Virtual Machine

Description RecordsManagerSweep.sh requires the DISPLAY environment variable to be set in UNIX environments. If RecordsManagerSweep.sh is executed in a UNIX environment without the DISPLAY environment variable set to a valid X Window display value, the Java Virtual Machine (JVM) throws java.lang.InternalError: Cannot connect to X11 window server. This error is harmless and does not prevent the sweep from running.
Workplace
Description When a file is saved to a mapped network drive, the file might not show as tracked when it is checked back in depending on the user's permissions to the share. Copyright IBM Corp. 2002, 2010 - 54 -
Workplace XT
Description 780538 When using Mozilla Firefox 2, the CM8 Viewer locks up when trying to open a document for viewing. This problem does not occur when using Firefox 3 or when using Firefox 2 with JRE 1.6.0_10. To work around this problem, upgrade to the latest Firefox version or the most current supported version of JRE 1.6. 840048 The following issues occur when file tracking is enabled and JRE 1.6.0_14 is used: Browsing for files after doing a Download action or Check out and download action results in a Java script error if the specified qualified path in the site preference is invalid. The workaround is to confirm the qualified path site preference setting is a valid path and the user has the valid path set up on their local system. Browsing for files to add after doing an Add action results in freezing the selected file. The workaround is to refocus the Select File dialog box by clicking the Start menu.
825425
When using Mozilla Firefox 3 on a Microsoft Vista operating system, the following occurs when checking in a document: Browse for a document to check in, the Select File dialog box is displayed in the background instead of in front of existing windows. Cancel the Select File dialog box. The Checkin wizard will no longer be displayed in front of existing windows. It is displayed in the background. Work around: Install Microsoft Service Pack 1.
Content Federation Services (CFS-CS and CFS-IICE)

Description 779602 During installation on Linux, when prompted for the JAVA HOME path, you must type in the path information; you cannot browse to the location This is an InstallAnywhere limitation.
Content Engine Web Service

Description When running a Content Engine Web Service client application created in Visual Studio 2005 with Web Service Enhancements (WSE) 3.0 that uses the 4.0 Message Transmission Optimization Mechanism (MTOM) endpoint, you might experience high memory usage or an OutOfMemoryException exception when you stream large MTOM attachments. This problem occurs because WSE 3.0 buffers attachments before they are sent, potentially creating very large buffers. When using WSE 3.0, you cannot stream MTOM attachments without buffering. Microsoft has a WSE hotfix available that allows proper, non-buffered streaming of content uploaded over MTOM, which does not require the entire source content to be loaded into memory at once. For more information, see article 943508 on the Microsoft support site: http://support.microsoft.com/?id=943508. This hotfix is not available for general download; to obtain it, you must call 1-800-MICROSOFT. Copyright IBM Corp. 2002, 2010 - 55 -
IBM FileNet P8 4.5 Release Notes Known Issues Description To stream MTOM attachments as they are sent from the client application to the Web server, you must modify the definition of the generated InlineContent class, applying techniques similar to those described in the following MSDN article: How to Stream Large Amounts of Data from a Web Service (http://msdn.microsoft.com/enus/library/aa528818.aspx). 835019 When using the SOAP endpoint to upload large content, an out-of-memory exception on the server during the decoding of the content attachment can be incorrectly interpreted as the end of the stream. The result is an empty content element for the document with no indication of an error having occurred. 836721
Content Engine Java and .NET API

Description When running a .NET client application created in Visual Studio 2005 with Web Service Enhancements (WSE) 3.0, you might experience high memory usage or an OutOfMemoryException exception when you stream large Message Transmission Optimization Mechanism (MTOM) attachments. This problem occurs because WSE 3.0 buffers attachments before they are sent, potentially creating very large buffers. When using WSE 3.0, you cannot stream MTOM attachments without buffering. Microsoft has a WSE hotfix available that allows proper, non-buffered streaming of content uploaded over MTOM, which does not require the entire source content to be loaded into memory at once. For more information, see article 943508 on the Microsoft support site: http://support.microsoft.com/?id=943508. This hotfix is not available for general download; to obtain it, you must call 1-800-MICROSOFT.
FileNet P8 Platform Installation, Uninstallation, and Upgrades

Content Engine
APAR Name Defect ID 777894 Description The Content Engine and Content Engine Client installers do not generate silent response files for uninstalling, and the silent uninstall will remove all program components regardless of attempts to only uninstall a specific feature. This is a known issue with Install Anywhere, Issue# IOA-000034429. Before starting the Content Engine Client installation program on a machine that runs HP-UX, make sure that the PATH environment variable on the machine includes /usr/contrib/bin. Otherwise, the program will not find gzip and gunzip (located in /usr/contrib/bin) and will fail. Configuration Manager fails to create a port XML attribute for the XA data source for Microsoft SQL Server when deploying Content Engine on JBoss. As a workaround, after running Configuration Manager, add the following line to the XA data source XML file (inserting your Microsoft SQL Server instance port number in place of 1096): <xa-datasource-property name="PortNumber">1096</xa-datasource-property> The Configuration Manager tool cannot create JDBC data sources in a WebLogic cluster. To work around this problem, complete the following steps when you are Copyright IBM Corp. 2002, 2010 - 56 -
785417
788041
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID 780674
Description configuring Content Engine in a WebLogic cluster: 1. In the Configuration Manager tool, select the "standard" deployment type. 2. In the Application Server Properties page, specify the Administration server name to create a JDBDC data source on the WebLogic Administration Server. 3. Using WebLogic Administration Server, navigate to and click the newly created data source, click the Targets tab. 4. Clear the check box next to the admin server, and select the check box next to the name of the WebLogic cluster. In the topic 'Task 3: (optional) Install additional locales," step 4 of the Windows procedure specifies the location for creating a directory only for 32-bit machines. The location for the directory on a 64-bit machine is the following: C:\Program Files (x86)\Common Files\InstallShield\Universal\WinVersion\x86\host_name\Gen1\_vpddb The maximum row size of the underlying DB2 database tables is 32 KB. Therefore, choose a minimal set of addons before creating an object store. After the object store exists, be aware that each user property reduces the row size from what already is reserved by the current system and addon properties. You should initially allocate string properties to be as small as possible; you can increase the sizes later in FileNet Enterprise Manager. A string property with a large allocation size is more space efficient if you create it as a long string data type; however, long strings have some functionality limitations. The maximum row size of DB2 tables is 32KB. Due to the way in which DB2 allocates space in a row, when using DB2 with the Content Engine be very precise when selecting the add ongs to use and defining custom properties. Add ons can be added to, but not removed from, an object store, therefore during object store creation, select the minimum set of add ons required for your applications. When defining string properties, make the string as small as possible, you can increase the size later if needed. Also consider using the long string data type for large strings. Refer to the following topic for more information on long strings: http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic= /com.ibm.p8.doc/ce_help/properties/pr_concepts_properties.htm FileNet Configuration Manager does not save the configuration values correctly when you select WebLogic Cluster for the application deployment type with Oracle RAC for the database type. You must manually edit the configuration XML files the were created in the graphical user interface to correct the settings before you deploy Content Engine. To set the deployment type and the database information, complete these steps: 1. Open the ce_install_path\tools\configuration\profile\my_profile\applicationserver.xml file in a text editor. The default value for ce_install_path is C:\Program Files\FileNet\ContentEngine or opt\FileNet\ContentEngine.
842164
850363
862430
- 57 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID
Description 2. Locate the entry for the ApplicationServerName, and enter your cluster server name for the value attribute: <property name="ApplicationServerName"> <value>my_production_cluster_name</value> 3. Save the file. 4. Open the ce_install_path\tools\configuration\profile\my_profile\configurejdbc.xml file in a text editor. Use the profile that contains your GCD database information. 5. Locate the entry for the DeploymentType, and enter Cluster for the value attribute. <property name="DeploymentType"> <value>Cluster</value> 6. Save the file. 7. Open the ce_install_path\tools\configuration\profile\my_profile\configurejdbc.xml file in a text editor. Use the profile that contains your object store database information. 8. Locate the entry for the DeploymentType, and enter Cluster for the value attribute. <property name="DeploymentType"> <value>Cluster</value> 9. Repeat steps 7 and 8 for each object store that you use in this cluster. 10. Deploy the Content Engine instance according to the directions in the IBM FileNet P8 Platform Installation Guide. In the FileNet P8 Installation and Upgrade Guide topic Installing the latest Content Engine client files on other IBM FileNet P8 servers (for staged upgrades), which you work through when upgrading Content Engine from 3.5.2, 4.0.1, or 4.5.0, note that you need to obtain the Content Engine Client files from the latest Content Engine fix pack.
893302
Content Search Engine

APAR Name Defect ID 785816 Description In UNIX environments only, installing a Local Admin Server (other than the Master) creates k2adminstart/stop scripts with incorrect paths. Workaround: 1. Login to the Dashboard. 2. Detach the broker for the Ticket Server on the Master Admin Server. 3. Restart the Ticket Server. 4. Re-login to Dashboard and verify you are not prompted for credentials (for example: username/password). 5. On the Local Admin Server, uninstall and re-install the Content Search Engine.
- 58 -
Description 6. After installation and startup of the Admin Server, log in to Dashboard, and verify you see the Local Admin Server, then re-attach the broker to the Ticket Server.
Process Engine
APAR Name Defect ID PJ35139 782145 Description During Process Engine installation with a DB2 database, if an invalid BLOB tablespace name is entered, no error is returned. However, when saving security settings in Process Engine Task Manager, an error [Err=7900004c] is returned to the screen and is not written to any error log. Workaround: Assure that the BLOB tablespace name entered during Process Engine installation matches the actual BLOB tablespace name pre-defined by the database administrator. The Process Engine installer on AIX 6.1 TL2 or AIX5.3 ML9 aborts after the "Verifying JVM" step. No GUI opens and the installer returns to the command line. Running the installer with the -is:log option shows the following message in the log file: "JavaHome is not resolved correctly in the jvm file /tmp/istemp569384354231000/_bundledJRE_/jvm. Failed to launch the application." The problem is caused by a newer version of the sed program (version 5.3.9.0 of bos.rte.edit) which appears to fix a bug that the installer was dependent upon. -r-xr-xr-x 1 bin bin 30106 Aug 01 09:45 /usr/bin/sed Workaround: Use an older version of sed from either AIX 6.1 base or AIX5.3 ML6. A version of sed with the following stamp does not cause the problem: -r-xr-xr-x 1 bin bin 28338 May 10 2005 /usr/bin/sed To place the older version of sed in the Process Engine installer directory, change the PATH to add the Process Engine installer directory to the front of the PATH, and then run the installer.
PJ35505 801253
Application Engine
APAR Name Defect ID 383070 Description When Application Engine is configured to use 1-box SSL redirect and Internet Explorer as the browser, the browser fails to load the graphics of the login page and it also fails to login. A workaround is to use different machine names in the http and https URLs. For example, use the machine name in one and use the IP address in the other. PJ35070 661128 Switching from WAR file to EAR file deployment. If you choose to deploy Application Engine as a WAR file and later decide to redeploy it as an EAR file, you must uninstall Application Engine and then reinstall the application, selecting EAR file deployment in order to add the required files to your setup. If this change of deployment type seems likely for your setup we suggest - 59 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description that you install Application Engine as if you would deploy an EAR file, which will create both WAR and EAR files, and then use the WAR file to deploy your web application. PJ35071 664389 During Application Engine 4.0.1 uninstallation, the uninstaller prompts the user to select whether or not to preserve custom-modified files. On upgraded systems the response is not registered correctly and custom-modified files are always deleted. During uninstallation of freshly installed Application Engines the uninstaller works correctly and preserves the files if requested. Application Engine shared directories must be mapped drives, not Windows shares. The Application Engine installer prompts for locations for the following directories: Configuration Directory Upload Location Download Location Logfile Location
On Windows, if these are shared directories you must map these locations to drives on the Application Engine server and enter the mapped drive information during installation. PJ35110 759003 When installing Application Engine on HP Itanium, finishing or cancelling the Application Engine installer program can result in a syntax error in the console. The error is harmless and can be ignored Silent upgrades from any version of Application Engine Application Integration and File Tracker to version 4.0.2.5 are not successful. The workaround is to uninstall the previous versions and silently install version 4.0.2.5 as a new installation. Workaround for running a silent upgrade of any previous Application Integration version to Application Integration 4.0.2.5: 1. Silently start the uninstaller using the following statement in the command line: MsiExec.exe /X{35907B7D-02E2-490C-8F3B-54C4E3729D90} /qn LICENSE_ACCEPTED="true" 2. Start the Application Integration version 4.0.2.5 silent upgrade as a new installation: ApplicationIntegration.exe /s /v"/qn ADDLOCAL=ALL HOST=cm-xtdev01 PORT=8080 APPLICATION=Workplace /L*v %Temp%\FnAppIntSetup.txt LICENSE_ACCEPTED=true" Workaround for running a silent upgrade of any previous File Tracker version to File Tracker 4.0.2.5: 1. Silently start the uninstaller using the following statement in the command line: Msiexec.exe /X{4291FBBC-C585-43ED-9416-5F22D8C6FEE9} /qn LICENSE_ACCEPTED="true" Copyright IBM Corp. 2002, 2010 - 60 -
NA 850314
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description
2. At the command line, start the File Tracker version 4.0.2.5 silent upgrade as a new installation: FileTracker.exe /s /v"/qn /L*v %Temp%\FnFileTrackerSetup.txt LICENSE_ACCEPTED=true"
Workplace XT
Defect 833280 Description The IBM FileNet Workplace XT Installation and Upgrade Guide v. 1.1.3 task "Install IBM FileNet Workplace XT" includes a step "(Optional) (UNIX only) Set the P8TASKMAN_HOME system environment variable." In the case of collocated instances of Workplace XT and Application Engine (Workplace), the value of the variable that is set as part of the first installation, that is, whichever application you install first, will apply for both installations. 859308 If you are running WebSphere as a Windows service, and you are planning to install Application Engine or Workplace XT using a UNC path for the configuration, upload, and download directories, you must set the "Log On As" value of the WebSphere service to a specific user with write permissions to the share of the UNC path.
Image Services Resource Adapter (ISRA)

Defect 853075 Description Instructions for upgrading the ISRA Servlet are missing from the Installation and Upgrade Guide. To upgrade the ISRA Servlet: 1. From your application server, undeploy the ISRA Servlet. 2. From the install_location\_uninstISRA folder, run uninstall.exe. 3. Delete the AE_ISRA_Servlet_install_log-xxx.txt file and the entire ApplicationEngineISRAServlet folder. 4. From the installation media or your local copy, start the Application Engine ISRA Servlet installation program: UNIX: AE-ISRA-Servlet-4.0.2.0-operating_system.bin Windows: AE-ISRA-Servlet-4.0.2.0-WIN.exe
Content Engine
APAR Name Defect ID 747777 Description Importing lifecycle actions with a code module requires an automatic retry. If a lifecycle event action references a code module, and both are exported together, the lifecycle event action can fail to import. This is because the lifecycle event action appears before the code module in the exported data. To correct this problem, check - 61 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description the Retry Failed Imports option on the Import Helper (Import Options Tab). When the code module successfully imports, the lifecycle event action import is retried and will complete successfully. PJ34144 780949 PJ34999 749735 777160 Files containing Portuguese characters cannot be indexed to a File Storage Area.
A null pointer exception occurs when checking in a document using a security template. Oracle 11g R1 does not use the I_RELATIONSHIP27(TAIL_ID,NAME) index on the RELATIONSHIP table, which is created during object store creation, properly. As a result, slow folder population rates have been observed. Workaround: Recreate the I_RELATIONSHIP27(TAIL_ID,NAME) index on the RELATIONSHIP table by dropping the existing index and then recreating it manually. Ensure that the TAIL_ID column is the first column and the NAME column is the second column.
PJ35002 784915 PJ35003 753551
Enterprise Manager displays incorrect IS Data Type for F_DOCNUMBER.
The stop word list does not function correctly for the uni/en (Universal English) locale.
BEA reports the following problem with WebLogic 10 MP1. 782194 When a request with invalid credentials is rejected, the request immediately following it is also rejected with an authentication error (E_NOT_AUTHENTICATED), even if the second request contains valid credentials, and even if it comes from a different user. Valid requests after the second request are fine, and the workaround is therefore to resend the valid request. This problem occurs regardless of which host operating system or directory server is being used. This problem does not exist in earlier releases (including the base WebLogic 10 release), nor in WebLogic 10 MP2 or later. You can request a patch for WebLogic 10 MP1 from BEA support by referencing Change Request number CR356815. If you use the command line version of Configuration Manager to generate a single task, you cannot open that task as a profile in the Configuration Manager graphical user interface. You must manually edit the configuration XML file and use the command line version to execute the task. A FileNet P8 Content Engine Web Service Extensible Authentication Framework (WS-EAF) failure occurs when authenticating with a custom Java Authentication and Authorization Service login module under WebSphere 7.0. When using WS-EAF in a WebSphere Application Server 7.0 environment, JAAS login authentication fails when stacking a custom login module. The failure can occur even if one of the login modules in the chain is configured as SUFFICIENT and the module successfully authenticates the user. The authentication failure can occur with the WebSphere Application Server Express, BASE, or Network Deployment editions. Copyright IBM Corp. 2002, 2010 - 62 -
785703
798158
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description Resolution: From the Support and Downloads section of the IBM Support web site, install the fix for APAR PK82390 (http://www01.ibm.com/support/docview.wss?rs=0&q1=PK82390&uid=swg1PK82390&loc=en_U S&cs=utf-8&cc=us&lang=en). You can also install WebSphere Application Server 7.0 Fix Pack 5, which incorporates PK82390. If Content Federation Services for Image Services (CFS-IS) is in the environment in which you are upgrading Content Engine from version 3.5 to 4.5.0, complete the following steps after you have completed your configuration of Content Engine (using the graphical user interface or the command-line interface): 1. Remove the "IS Class to object store/domain" default map using the IS RAC utility for the IS document class used for federation for object stores that participates in CFS-IS federation. 2. Modify the "f_ce_domain_guid" and "f_ce_domain_name" columns in the ce_id_map table on the IS database to correspond to the new, Content Engine 4x domain guid/name. For example: UPDATE ce_id_map SET f_ce_domain_guid = 'new_domain_guid' and f_ce_domain_name = 'new_domain_name' where f_ce_os_name='object_store_name'; 3. Repeat steps 1 and 2 for every object store being upgraded that participates in CFS-IS federation. 4. From a command line, restart Image Services: initfnsw -y stop; then "killfnsw -ADy" (UNIX) DyS (Win); "initfnsw start" 5. Re-add the IS Class to object store/domain map by using the Remote Admin Console. 6. Stop and start Content Engine. 848698 A CONTENT_FCA_FILE_DOES_NOT_EXIST error message intermittently occurs on cluster or multiple Content Engine configurations when attempting to retrieve a document from a file store shortly after the file has been added. This issue occurs due to NFS directory attribute caching on NFS clients (Content Engine server host machines). When multiple NFS clients are accessing the same directory, directory updates made by one server might not be immediately visible to other servers. Renames of files from one directory to another do not force directory attribute caches to be refreshed on other NFS clients. A file rename occurs when adding a document to the file store. By default, Linux systems have a 60 second attribute cache. Other UNIX operating systems have a similar default. Disabling attribute caching with the noac option on the Linux NFS mount command will avoid this issue. Disabling attribute caching can effect document retrieval performance from NFS file shares (specifically, Content Engine file stores). To identify this issue, enable IBM FileNet P8 Content Engine tracing with Content Storage enabled on all Content Engine machines. The following should be apparent in the logs: 1. A file rename occurs on CENode1. Note: {11111111-1111-1111-1111111111111111} is an example GUID. Copyright IBM Corp. 2002, 2010 - 63 -
846316
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description CENode1.p8_server_trace.log: 2009-10-07T04:54:10.514Z 1D2A1D2A CSTG rename [/apps/p8/FileStore/inbound/FN{11111111-1111-1111-1111111111111111}{11111111-1111-1111-1111-111111111111}] to [/apps/p8/FileStore/content/FN9/FN5/FN8/FN{11111111-1111-1111-1111111111111111}{11111111-1111-1111-1111-111111111111}-0] 2. After the file rename, attempts to retrieve the file occur on CENode2. The file retrieval attempts occur within 60 seconds of the file rename. CENode2.p8_server_trace.log: 2009-10-07T04:54:10.642Z 7FC27FC2 CSTG file doesn't exist in the content directory, will search inbound /apps/p8/FileStore/content/FN9/FN5/FN8/FN{11111111-1111-1111-1111111111111111}{11111111-1111-1111-1111-111111111111}-0 3. CENode2 fails with a CONTENT_FCA_FILE_DOES_NOT_EXIST error. CENode2.p8_server_trace.log: 2009-10-07T04:54:38.212Z 44A544A5 ENG ERROR method name: retrieve principal name: xxxxx Global Transaction: false User Transaction: false Exception Info: com.filenet.api.exception.EngineRuntimeException: CONTENT_FCA_FILE_DOES_NOT_EXIST: The file does not exist /apps/p8/FileStore/content/FN9/FN5/FN8/FN{11111111-1111-1111-1111111111111111}{11111111-1111-1111-1111-111111111111}-0. 853401 The base version of WebSphere Application Server that is bundled with Content Engine does not include cluster support. To configure clusters, you must have Content Engine installed on servers that are running the IBM WebSphere Application Server Network Deployment version.
Content Federation Services (CFS-IS and CFS-CMOD)

APAR Name Defect ID PJ34875 782467 Description A document federation update fails when a user re-maps an existing external repository field to a new Content Engine property. Selecting a non-instantiable class as a target document class will cause an importer error when federating documents. To determine whether a document class is noninstantiable, use Enterprise Manager and navigate to the class definition. Right-click on the document class in question and select 'Properties' from the context menu, then select the 'Properties' tab on the class properties dialog box. The 'Allows Instances' property appears near the top of the list of class properties. If the 'Allows Instances' property value is false, the document class is not instantiable.
786183

APAR Name Defect ID PJ33358 752390 Description Content Search Engine hangs during high volume indexing. New indexing requests are queued, but do not complete. If the Index Server and Search Server are running on the same machine search ceases to function.
- 64 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description Resolution: Reduce the number of Indexing threads in the Verity Server tab of the P8 Domain Properties in FileNet Enterprise Manager to 1. Indexing throughput will be slower, but the risk of encountering a hang condition is significantly reduced. If the Content Search Engine server is in a hung state, recycle the K2 Administration Server service (For Windows Platforms) or the K2Admin process (For UNIX platforms). If these services do not terminate gracefully, reboot the Content Search Engine server. Indexing will resume and Content Engine will re-submit failed index jobs. All content will be re-submitted and indexed and no data will be lost. PJ34997 771529 PJ34998 747682 PJ35000 777182 PJ35001 781008 PJ35004 773204 NA 845707 NA 856024 Multiple version numbers for Verity might be seen in CSE.
Performance problems occur when running CBR queries for exact matches.
Verity 6.2.2 K2 online documentation for supported platforms and file types is not current. Performing the k2adminstop operation does not function with Verity 6.2.1 on AIX 6.3. Verity sends index requests to the wrong index server.
Install the Autonomy K2 services on local mounts. Autonomy K2 Ticket Server services do not start on an NFS mounted location. The path to the Verity bulk insert file bif.txt associated with an object store must not exceed 256 characters. Otherwise, any indexing job on the object store will fail to complete. To prevent this failure, minimize the number of characters in the file path. You can do this by limiting the number of characters in the following components of the path: Verity installation path K2 indexer process alias Host name or cluster name
If you encounter this failure, there are two ways you can recover: Manually remove the index area and collections that you created for the object store, and recreate them with shorter names. Drop and recreate the object store database, and then recreate the object store.
- 65 -
FileNet Services for Lotus Quickr

Description PJ35298 PJ35362 787390 787114 The Content Engine client installer can detect the installation path of FileNet Services for Lotus Quickr. However, even if FileNet Services for Lotus Quickr is installed on a non-default location on Windows, such as: C:\Program Files\IBM\FN Services for Lotus Quickr036, Content Engine client installer detects and displays the default install path C:\Program Files\IBM\FN Services for Lotus Quickr. If FileNet Services for Lotus Quickr is installed on a non-default location on AIX, Content Engine client installer detects and displays an incorrect location of: /opt/IBM/FFN Services for Quickr. Workaround for Windows or AIX: Browse to the correct path and proceed with the installation. When adding a document to a FileNet P8 library, then checking it out, modifying it, and checking it back into the library, the First created on information for the file changes to the last modified date and time. The First created on information should display the date and time the file was first added. When searching a FileNet P8 system in Lotus Quickr Search Center and the search criteria includes only invalid characters, such as {, },and ., the following message appears: "A problem occurred during the search. If the problem persists, contact your System Administrator." Instead of displaying this message, the search should execute, but no documents should be returned. If you use the Microsoft Windows installer, you might see the following error message: No entry found: MakeExecutableAction_zg_ia_sf.jar. It is a non-fatal error and you can ignore this error. This error is caused by InstallAnywhere. If you want to use the Configuration Manager tool to deploy FileNet Services for Lotus Quickr product, you must manually modify the configuration files generated by Configuration Manager. In the deployapplication.xml file, change the following parameters from the default values to the required FileNet Services for Lotus Quickr product values. 1. <property name="Ear"> <value>C:\Program Files\IBM\lib\<insert product name here>\Enginews.ear</value> Replace Engine-ws.ear with the FileNet Services for Lotus Quickr product ear file name. For example: C:\Program Files\IBM\FN Services for Quickr\fnqs.ear. 2. <property name="ApplicationName"> <value>FileNetEngine</value> FileNet Engine is the Content Engine application name. Change the value to the application name for FileNet Services for Lotus Quickr product. For example: FNQuickrServices. A search with a query string containing at least one hyphen (-) character might return Copyright IBM Corp. 2002, 2010 - 66 -
775463
779920
780139 ISV
783889
IBM FileNet P8 4.5 Release Notes Known Issues Description 784386 785318 unexpected results. This is due to a hyphen being treated as punctuation by the P8 search engine. Examples: A search for 010-68967707 returns documents containing either 01068967707, or 010 68967707 A search for 9EA8249E-095A-4AFC-8244-64D9159309BE will not return documents containing that exact string.
To resolve this issue, append a wildcard character to the end of the search string. For example: a search for 9EA8249E-095A-4AFC-8244-64D9159309BE* returns documents containing 9EA8249E-095A-4AFC-8244-64D9159309BE. Users with a double-byte character in their user name cannot log on to a FileNet P8 system using the Quickr Web UI. An "Invalid credentials for remote server" error occurs. On HPUX, HPUX-Itanium, and AIX platforms, the FileNet Services for Lotus Quickr uninstaller fails if the Java Virtual Machine (JVM) is not included in the system path. The following error message is displayed: No Java virtual machine could be found from your PATH environment variable. You must install a VM prior to running this program. This issue is caused by InstallAnywhere. Work around: Add JVM to your path. For example: export PATH=$PATH:/user/bin/jave.exe If a folder contains only subfolders (no documents), and the number of subfolders displayed is a multiple of the page size, then the ATOM feed for the folder contains an unnecessary "next" link on the last page. The Lotus Quickr library viewer and the publish dialogs use ATOM feeds. Using Quickr Connectors, if your rename a document, the document content is lost. 791334 Workaround: To save the content, right click the document and select Versions. Highlight the previous version with content, and then click Restore. This creates a new version with content and old name.
785114 767882
786243
787126

APAR Name Defect ID PJ35116 781723 PJ35107 785473 Description The names of ECM widgets that are intended to be hidden, ECM Create Work Item and ECM Create Action, are distorted when viewed in the hidden widgets corral. The distortion varies depending on the language for which the browser is configured. In the Step page with an ECM Step Complete widget, closing a work item with the close icon in the upper-right corner of the window might result in a lock-out condition if you later attempt to reopen the same work item. To avoid this issue, close the Step page window with the ECM Step Complete widget's Close button. This lock-out condition is accompanied by a "LockedByOthers" message, which is erroneous. The condition is, in fact, caused by a discrepancy between the way a user Copyright IBM Corp. 2002, 2010 - 67 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description name is stored in LDAP and on the Process Engine server. Should you encounter this issue, you can unlock the work item using Process Administrator. LO33481 779752 There is a known issue with how Lotus Mashups 1.0 displays widgets in a multilingual environment. When editing a mashup page with Lotus Mashups, use the same browser language preference that is used to view the page. Otherwise, the page is likely to display incorrectly When using Internet Explorer 7.x, you cannot use the mouse to select text within some input fields of the ECM Work Data widget. However, you can click within a field and then use the keyboard to edit data. In the ECM In-basket widget, when the last page is reached, the next-page button is erroneously enabled, and clicking this button navigates to a blank list in the inbasket. To return to the list of work items in the in-basket, click either the previouspage button or the first-page button. If you launch Workplace XT from an IBM Enterprise Content Management Widgets mashup page, and if you later encounter an error message dialog box as the result of a Workplace XT operation, the dialog box's "Close Window" link will not work. To close the dialog box, click the "X" button on the top-right corner of the dialog box. In the ECM Work Data widget, the edit window for adding or removing array data disappears if you click the window's vertical scroll bar. To avoid the problem, use the mouse's scroll wheel. Or, if your page permissions allow you to move widgets, move the ECM Work Data widget to the top or the bottom of the page so that the edit window displays completely, and then save the page setting. IBM Enterprise Content Management Widgets supports only the 6.1.0.13 version of WebSphere Application Server (WAS), which is the version bundled with IBM Mashup Center 1.0. If you upgrade to WAS 6.1.0.17, you will be unable to log on to IBM Enterprise Content Management Widgets. IBM FileNet fix pack P8PE-4.5.0-001 adds Web application for Business Space and a new set of email templates. Following are existing issues with the templates: Get and open email for New Work item: Opens Business Space, but the data is not displayed on the step processor. Get and open email for Reminders: Opens Business Space step processor, but the data is not displayed on the step processor. Get and open email for New Tracker item: Opens Business Space step processor, should open the Tracker. Get and open email for Workflow deadline reminders: Opens Business Space step processor, should open the Tracker. Get and open email for Workflow deadline expired: Opens Business Space step processor, should open the Tracker. Get and open email for Workflow expired step deadline: Opens Business Space step processor, but the data is not displayed on the step processor. Get and open email for Workflow milestone reached: Should open Milestone - 68 -
PJ35125 779110 PJ35088 781661
PJ35089 781664
PJ35090 783278
PJ35092 786044
NA 799097
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description page, opens Business Space step processor.
Process Engine
APAR Name Defect ID PJ35137 756934 PJ35065 782220 PJ35138 783418 783515 Description The 4.5.0 release does not support Point-in-Time Recovery on Oracle, IBM DB2 or Microsoft SQL Server File menu items are not aligned correctly when using Sun JRE 1.5.
The -L parameter purges event log records. If the Process Analyzer option has been enabled on the Process Engine server, the -L parameter only purges records that have been processed by Process Analyzer. All records will be purged regardless of the PA option if a PA server has not been configured for the event log (PA can be configured to process records from only a subset of the event logs).
PJ35064 771691
Running the Process Engine client installer on HPUX Itanium returns an error No java runtime ENV (JRE). Workaround: Run the HPUXi client installer with the following command: ./P8PE-CLIENT-4.5.0-HPUXI.BIN -is:jvmtimer 10 This gives the installer more time to complete JVM verification. The default value is 5.
PJ35109 786497
If special characters are used in the step name of a workflow, the event transformation information written in XML for the associated work class is invalid since the special characters are not escaped. When using Process Engine with DB2 for z/OS, you might experience intermittent transaction failures which correspond to a SQL -906 error on the DB2 server (SQLCODE -906 and MSGDSNT501I RESOURCE UNAVAILABLE). Workaround: Apply the fix for APAR PK75567 for DB2 for z/OS.
786515
PJ36128 789704
The Process Engine 4.5 Solaris installer fails when using an alias for the fnsw user. Workaround: 1. Before running the Process Engine installation program on Solaris, create an fnsw user and an fnusr group, as documented in the Plan and Prepare Your Environment for IBM FileNet P8 guide. This user and group are in addition to the alias user and group. 2. Specify the alias user and group names during the installation. 3. After the installation completes, change the owner:group from fnsw:fnusr to fnswalias:fnusr-alias for the following files in /fnsw/bin:
- 69 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description VWJs VWKs VWRs VWSs vwaemsg vwapitst vwcimsg vwclean vwdb2util vwdone vwintpgm vwisi vwldap vwlog vwmsg vwnotify vwperut vwsectldf vwspy vwstats vwsvrtst vwtfer vwtime vwtool vwtran vwverify vwior vwcemp vworbbroker vwsvrtime During installation of Process Engine 4.5.0 on AIX, the following error might be logged even though there is no error: fn_pso_convert: not found
798096
- 70 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description Workaround: Add /fnsw/bin to the PATH in the .profile for root and fnsw (or alias) users before installing Process Engine. IBM FileNet fix pack P8PE-4.5.0-001 adds Web application for Business Space and a new set of email templates. Following are existing issues with the templates: Get and open email for New Work item: Opens Business Space, but the data is not displayed on the step processor. Get and open email for Reminders: Opens Business Space step processor, but the data is not displayed on the step processor. Get and open email for New Tracker item: Opens Business Space step processor, should open the Tracker. Get and open email for Workflow deadline reminders: Opens Business Space step processor, should open the Tracker. Get and open email for Workflow deadline expired: Opens Business Space step processor, should open the Tracker. Get and open email for Workflow expired step deadline: Opens Business Space step processor, but the data is not displayed on the step processor. Get and open email for Workflow milestone reached: Should open Milestone page, opens Business Space step processor.
799097
802481
In the procedure for converting an existing Process Engine region to a backup enabled region, vwtool->rdbConvertReg does not list or verify the new (added in BPM450) VWRole<reg> table as one of the tables that is required to be moved to the new tablespace. Workaround: If converting an existing Process Engine region to a backup enabled region, the VWRole<region> table must also be backed up and moved to the new tablespace assigned for the backup enabled region from the generic tablespace. The utility that is provided: vwtool->rdbConvertReg, does not list this as one of the tables to be moved. It also does not verify that this table has been moved successfully to the new tablespace. If this step is not performed, the role information for the region will be lost, and the role related features will not function correctly. When using IBM JRE 1.6 only, an exception occurs and users are unable to display the WSRR tab in Region Properties/Web Services in the Configuration Console when there is a WSRR registry entry. If no WSRR registry is configured, the WSRR tab displays with no error. However, if you add a WSRR registry to the tab, then click OK, the error appears and the dialog box hangs. This occurs with Microsoft Internet Explorer 6, Microsoft Internet Explorer 6, Mozilla and IBM JRE 1.6. This does not occur with IBM JRE 1.5, Sun JRE 1.5 or 1.6.
785947
- 71 -
Process Analyzer
APAR Name Defect ID 802805 Description The P8PA-4.5.0 installer on Windows 2003 with SQL Server 2005 fails on an IPv6 only network as the installer is unable to determine the version of the database. The installer does not proceed after checking for the database, causing the user to cancel the installation. The P8PA-4.5.0-001 fix pack installer was changed to use the SQL server native client to obtain this information. This problem is not seen on Windows 2008. Workaround: For Windows 2003 32-bit server 1] Run the installer and complete the installation with the following arguments on the command prompt: P8PA-4.5.0-Engine.exe -W PADetectSQLServerVersion.active=false -W PADetectSQLServerVersion.SQLServerVersion=9.00 -W PADetectSQLServerVersion.SQLServerType=SQLServer2005 For Windows 2003 64-bit server 1] Run the installer and complete the installation with the following arguments on the command prompt: P8PA-4.5.0-Engine.exe -W PADetectSQLServerVersion.active=false -W PADetectSQLServerVersion.SQLServerVersion=9.00 -W PADetectSQLServerVersion.SQLServerType=SQLServer2005 2] Run the script to create the OLAPDB and PADB using the 32-bit cscript utility as mentioned below: C:\Program Files (x86)\FileNet\Process Analyzer Engine\jpa\scripts\sqlserver>C:\WINDOWS\SysWOW64\cscript setupsqlserver.wsf
Application Engine
Workplace
APAR Name Defect ID 383681 Description The Component Manager does not start on HP-UX systems running WebLogic. Workaround: Modify the routercmd.sh file to use the BEA-supplied JRE. Use a text editor to change <ae_install_path>/Router/JRE/bin/java to /opt/bea/jdk150_03/jre/bin/java The default value for <ae_install_path> is /opt/FileNet/AE PJ35050 553411 When running Workplace File Tracker in Windows Vista, an error message appears and you cannot use the Delete local file option. To work around this issue, it is recommended you add the Application Engine(s) on which Workplace is running to the Trusted Sites list in Internet Explorer. You can access this list in Internet Explorer - 72 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description by doing the following: 1. In Internet Explorer, go to Tools > Internet Options. 2. Click the Security tab. 3. Click Trusted Sites and add the Application Engine(s) to the list of trusted sites. PJ35051 554888 When using Advanced Search via the Quick Search portlet running on WebSphere Portal 6.0, selecting any search template results in a "404 file not found" error. You can avoid this error by setting the postThreshold parameter to -1 in the web.xml file, which is located in <install location>/Workplace/WEB-INF/web.xml. After making this change, re-pack the war file and re-deploy Workplace for the changes to take effect. Refer to Task 28a-c in the IBM FileNet P8 Installation and Upgrade Guide for more information on deploying Workplace and packaging the war file. Following is an example of the postThreshold setting in the web.xml file:
<context-param> <param-name>postThreshold</param-name> <param-value>-1</param-value> </context-param>
PJ35052 555596
When you access Workplace from the Mozilla Firefox browser version 2.0.x, multiselect various documents that contain spaces in their document title, and then use the Download action, the Open with WinZip option is not available. The workaround is to use Internet Explorer. Errors can occur when saving a search template in the Search Designer. Work around this memory problem with the Java environment by using the following parameter for the JRE: -Xms 1024m -Xmx 1024m. McAfee Virus Scanner 8 has a default setting to block port 25 in order to stop Mass Mailing worms. This also blocks access to the exchange server and must be disabled or removed before the connection can be restored. (This issue also affects Process Engine DTS 183503 for information.) The Max number of search results is incorrect for simple search in Workplace and the Portlet Quick searches. Firefox has a new feature in which you are prompted for the latest available JRE if no JRE is installed and not prompted for a JRE if any JRE is installed (even an older version). This is contrary to Internet Explorer behavior as well as legacy Firefox behavior (1.x), This is a designed function. Firefox might prompt you to get a JRE that is not supported by Workplace XT or might not prompt you to update your JRE at all. If this occurs, you need to manually pick up the supported JRE provided by Workplace XT. This affects both Workplace and Workplace XT. If the client has a JRE that is older than the supported JRE version (for example, 1.4.2_0), when the Workplace XT user launches an applet (such as Search Designer or Viewer) from within a Firefox browser, the user is not prompted to install the supported JRE that ships with Workplace XT. Instead, the applets are launched using the clients current JRE. The "Use Java Applets" topic needs to be updated to include the following instructions to download the JRE provided with Workplace XT before launching
PJ35053 381961 PJ35054 374956
PJ35055 383192 PJ35056 741802
- 73 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description applets. 1. Log in to Workplace XT. 2. Go to http://<servername:port>/WorkplaceXT/download/jre-1_5_0_11-windowsi586-p.exe, where <servername:port> is the name and port number of your server. 3. At the Firefox prompt, download and save the installer file for JRE 1.5.0_11 on your local hard drive. 4. Run the downloaded installer file to install JRE 1.5.0_11 on the client. 5. Restart Firefox and proceed as usual to launch the applets. Note that these instructions are specific for JRE 1.5. PJ35057 742693 In Workplace, if you are using Internet Explorer 7.0, you may get a dialog box "The webpage you are viewing is trying to close the window? Do you want to close this window?" when you are attempting to close an Internet Explorer window. This is a new security feature for Internet Explorer 7.0 and cannot be disabled. Click OK to continue working. When using P8 WebDAV integration with SSL, MS Office documents do not open.
PJ35058 779184 779188 NA 785290
Running the Application Engine installer on HPUX Itanium returns an error: No Java Runtime Environment (JRE) was found on this system. Workaround: Run the HPUXi Application Engine installer with the following command: ./P8AE-4.0.2.0-HPUX64.bin -is:jvmtimer 100 This gives the installer more time to complete JVM verification. The default value is 5.
NA 836189
Two new My Active Workflows site preference settings were added. The Show step name column setting determines when the step name of a workflow is displayed in the list view. The Maximum number of rows to return setting determines the number of workflows that are displayed. The maximum number is 1000. If you attempt to install Application Engine or Workplace XT as a non-root user on Windows 2008, the system will require an administrator password during the installation. Workaround: You can turn off User Access Control on Windows 2008 before you run the installation program. Navigate to Control Panel> User Accounts > Turn User Access Control on or off. Click OK to turn off.
NA 905170
- 74 -
Workplace XT
APAR Name Defect ID 755620 Description When you open an Excel workbook in Excel 2007 by using a hyperlink that contains a query string as part of the URL, you are incorrectly prompted that the workbook that you are trying to open is in a different format than the file name extension specifies. If you plan to use the migration tool to upgrade your WebLogic environment from 9.x to 10, and you have Workplace XT installed with user token configuration, you must remove the Workplace user token configuration before you attempt to upgrade WebLogic. Use the following steps to prepare for the upgrade: 1. Log in to the WebLogic administrative console. 2. Navigate to Security Realms > myrealm > Providers > Authentication. 3. Click on Lock & Edit. 4. In the list, select the name of the custom provider you specified when you configured user token support. 5. Click Delete, and click Yes to confirm the deletion. 6. Click Activate Change. 7. Shut down the WebLogic server. 8. Remove the authentication-weblogic-9.jar file and the log4j-1.2.13.jar file from the following directory: <WL_home>/server/lib/mbeantypes 9. Perform your WebLogic upgrade. 10.Configure WebLogic per the instructions in the Workplace XT 1.1.2 Installation and Upgrade Guide, including the optional procedure to configure WebLogic to support user tokens for Workplace XT (including Application Integration, eForms, Records Manager, and others). Defect ID PJ34149 760924 Description Microsoft PowerPoint documents do not display correctly if opened in PowerPoint 2007 from Workplace or Workplace XT. Resolution: Install Service Pack 1 for Microsoft 2007. When using Mozilla Firefox 2, the CM8 Viewer locks up when attempting to open a document for viewing. Workaround: Upgrade to the latest supported Firefox version or the most current supported version of JRE 1.6.
759915
ISV
780538
Running the Workplace XT installer on HPUX Itanium returns an error: 785290 No Java Runtime Environment (JRE) was found on this system. The installer also requires a JAVA home patch to be set. Workaround: Run the HPUXi Workplace XT installer with the following command:
- 75 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description ./WorkplaceXT-1.1.3.2-HPUXi.bin -is:javahome <java location> -is:jvmtimer 100 This gives the installer more time to complete JVM verification. The default value is 5. If the user enables WebSphere integrated security through the Administrative console, the Workplace XT log out link fails to function and returns the user to a blank page, instead of re-directing the user back to the Workplace XT sign in page. When a child document is filed in multiple locations and is then moved or unfiled using the View Compound Document action, an error occurs. Work around: Perform the move or unfile action from the Browse view. On Turkish Solaris 10 and HP-UX 11iv3, the Workplace XT installation program will not run and will return an error: "The wizard cannot continue because of the following error: could not load wizard specified in /wizard.inf (104) WARNING: could not delete temporary file /tmp/ismp001/5145393 WARNING: could not delete temporary file /tmp/ismp001/8409926" Workaround: Change the locale to en_US.utf8 before running the Workplace XT installation program. Most translated key FileNet terminology used in the Workplace XT user interface (UI) in this release has been aligned with IBM standard terminology. Terminology alignment has not been applied to translated key FileNet terminology used in the Online user help in this release. Terminological inconsistencies therefore exist between the product UI and the Online user help. Issues exist when attempting to check out multiple documents in a Japanese locale. You might see an error message such as "String index out of range: -26". Workaround: In a Japanese locale, check out documents one at a time. When multiple documents are assigned file names containing double-byte characters, the file names appear garbled after the documents are downloaded. The file name assigned to the zip file appears garbled after downloading multiple documents. When the zip file is opened, the file names assigned to the documents also appear garbled. When using Mozilla Firefox 3 on a Microsoft Vista operating system, the following occurs when checking in a document: Browse for a document to check in, the Select File dialog box is displayed in the background instead of in front of existing windows. Cancel the Select File dialog box. The Checkin wizard will no longer be displayed in front of existing windows. It is displayed in the background. Work around: Install Microsoft Service Pack 1. When attempting to deploy Workplace XT 1.1.4.1 on JBoss 4.3.0, a stack trace displays with the following error: java.lang.NullPointerException
786696
804306 804309
831263
832101
835374
837367
825425
844804
- 76 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description javax.faces.webapp.FacesServlet.init(FacesServlet.java:165) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAsso ciationValve.java:182) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBa se.java:433) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.ja va:84) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:1 04) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedCo nnectionValve.java:157) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2 41) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:84 4) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process (Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) Workaround: Add the following to the web.xml. <listener> <listener-class>com.sun.faces.config.ConfigureListener</listener-class> </listener> NA 905170 If you attempt to install Application Engine or Workplace XT as a non-root user on Windows 2008, the system will require an administrator password during the installation. Workaround: You can turn off User Access Control on Windows 2008 before you run the installation program. Navigate to Control Panel> User Accounts > Turn User Access Control on or off. Click OK to turn off.
Application Integration BCS

APAR Name Defect ID PJ35094 777762 Description When you open a .pps or .ppt file in a Microsoft Office application integrated with Workplace XT using Application Integration BCS, the file opens up directly into a slide show mode without any editing capabilities. As a result, you cannot see the commands available under the IBM ECM tab on the Microsoft Office 2007 Ribbon. To work around this issue and edit the file, open the document from your local file system after downloading it. The JAWS screen reader announces the incorrect number of items in a list view. - 77 -
PJ35095
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID 781999 PJ35103 783112 The JAWS screen reader only the node name in an expanded tree view. It does not announce the additional levels and groups under a specific node. There is an InstallShield Wizard issue that occurs during the Application Integration BCS installation. The issue occurs on operating systems that use the Japanese language pack. The InstallShield window that lists the installation requirements contains Japanese text that incorrectly includes the word OK. The word OK should be replaced with the word Install. There is an InstallShield Wizard issue that occurs during the Application Integration BCS installation. The issue occurs on operating systems that use the Japanese language pack. The InstallShield window that lists the installation requirements contains Japanese text that is truncated. When you change system's display settings to a high contrast white and select an item from a context menu, you cannot read the selected menu item. The default high contrast color theme does not work with context menus. The work around is to modify your display's appearance and adjust the color scheme for your background. When you drag multiple documents and attach them as links to a rich-text format email, only the link for the first document is added to the e-mail. To resolve this issue, refer to Microsoft's Knowledge Base article 976176. It includes the update and hot fix package for resolving this issue: http://support.microsoft.com/kb/976176.., or, 976730 Office 2007 Cumulative Update for October 2009 http://support.microsoft.com/default.aspx?scid=kb;EN-US;976730 When you drag multiple documents and attach them as links to a rich-text format email, the link for only the first document is added to the e-mail. To work around this issue, drag the documents to e-mails using the text or HTML formats. The following note in the Application Integration BCS site preferences topic needs to be replaced with the following note: NOTE The local file is deleted only when the Office application you are using is the same application that was used to create the file. The file must also be open when you cancel the checkout. If it is closed, the local file is not deleted. When you send mail from an integrated application using Application Integration BCS, you cannot drag documents to applications other than Microsoft applications. To use the Send Mail action, you must set your web browser default e-mail client to Microsoft Outlook. Microsoft Office 2007 applications with Application Integration BCS installed are very slow to start when the client machine does not have internet access. The Office applications automatically try to connect to a Microsoft Windows update site to download the most current root certificates regardless of any internet access. There are two workarounds for this issue. You can turn off the automatic root certificate update or manually download the root certificates. To turn off the automatic root certificate update, refer to Microsoft's Knowledge Base article 909561. It includes the procedure for accessing the Group Policy and turning off the update: http://support.microsoft.com/kb/909561. Copyright IBM Corp. 2002, 2010 - 78 Description
799481
799757
812513
819351
819664
829845
829887
830471
To manually download the root certificate, refer to Microsoft's Knowledge Base article 931125. It includes the procedure for downloading the certificate: http://support.microsoft.com/kb/931125. The title for the Properties pane is not announced when The JAWS screen reader is used for keyboard navigation. An error occurs when a user tries to drag e-mails from Outlook to an object store from two different systems at the same time. When a user checks in a document that was exclusively checked out by another user, no error appears to notify the user the checkin was not successful.
831234
835206
845953
Records Manager
Disposition sweep
APAR Name Defect ID NA 910896 Description There is a new Multi-Filed Records Cache Size option in the Disposition Sweep Configuration user interface to help address performance issues when the Disposition Sweep tool is run on a container with multi-filed records. This new option allows you to configure your own cache size for these multi-filed records. The default value for this new option is 10,000. By default, sweep saves up to 10,000 multi-filed records' ids in cache. To achieve optimal performance, make the number you put in the Multi-Filed Records Cache Size field greater than the total number of multi-filed records in the system to avoid having to check the Content Engine server for ids not found in the cache. However, setting sweep to cache a huge number of multi-filed records may exhaust the memory on the server.
DoD Classified
APAR Name Defect ID PJ34538 368935 Description Exceeding the string property maximum causes an error. Long string properties are limited to 256 characters. However, Records Manager does not monitor text input on every string property field for performance reasons. If you enter more than 256 characters, you can receive an error when sending the string. For example, in the DoD Classified data model, entering more than 256 characters in the Downgrade instructions field (Security Classification page) causes an error when you click Apply. To recover, click Return on the error message and modify the field to have no more than 256 characters.
- 79 -
File Plan Import and Export Tool

APAR Name Defect ID PJ34539 747704 Description When exporting categories with identical partial paths, the tool concatenates the paths in the exported XML file. When a user employs the -o option to export categories with identical partial paths, the tool concatenates the paths in the resulting exported XML file. To correct the problem, manually edit the ParentPath attribute value of the RecordFolder entity.
Globalization
APAR Name Defect ID PJ34541 664158 Description When changing the encoding to Right to Left view, some popup windows do not display correctly.
High Availability environments

APAR Name Defect ID PJ34536 766617 766619 Description In High Availability environments, Records Manager does not recognize the virtual server name so users must specify an active server name from the Configuration page of the Records Manager Transfer Tool, Records Manager Access Role Tool, Records Manager Creation Tool, and the Records Manager File Plan Import Export Tool.
Installing on Process Engine 4.5 disables CE_Operations component queue

APAR Name Defect ID 800183 Description After installing Records Manager 4.5 in an environment using Process Engine 4.5, the CE_Operations component queue stops working. The RMWorkflowConfiguration.xml file imported during Records Manager workflow configuration incorrectly references the p8ciops.jar file from the previous release of Process Engine instead of the correct ContentExtendedOps.jar file. To correct this problem, update the isolated regions on the Process Engine server by transferring classes from the upgrade.cdl file. Follow the instructions in "To update all isolated regions" sub-task of the "Complete post-upgrade Process Engine configuration" task in the IBM FileNet P8 Platform Installation and Upgrade Guide.
Record operations
APAR Name Defect ID PJ34542 Description When using container-managed authentication (CMA), and a user logs on using one of the following methods, and then logs off the application they first logged in to, the - 80 -
Description original connection remains valid. Logs on to Records Manager from Workplace or Workplace XT using the Records Manager link Logs on to Workplace or Workplace XT, from Records Manager using the Workplace link
Consequently, if the user logs in again to the first browser session using a different user account, Records Manager adopts the user information of the first connection. This causes a credential conflict, and can cause a security violation when the user tries to declare physical records or perform some other similar action. Workaround: When logging off Workplace, Workplace XT, or RM, the user should close the browser window before logging back in. PJ34325 757291 PJ34564 775910 The Records Manager SendEmailOnSupercede event does not work properly when Records Manager uses JBoss as the application server. When E-mail Manager is configured to declare an email as a record, the DocURL field is populated with references to the attachments of the e-mail that have been separated and declared as records. The attachment references ensure end users can retrieve any associated attachments for that e-mail. However, for each reference, fewer than 100 characters are used. If emails have more than 15 attachments, E-mail Manager produces the following error due to the DocURL field exceeding 1333 characters:
10/02/2007 15:35:16 Error An error occurred while attempting to populate the Record properties for the target file 'C:\eMgr_temp\TA Numbers Requested for Fourth Quarter 07.1F29632C2329D4E085257362005E1AED.0000.20071002153501.dxl'. Reason: The value specified for property Document Location exceeds the maximum permitted length. (error 0x80040229)
PJ34557 663975
The Records Manager user interface has no mechanism to declare all parts of a compound document as a single record. However, users can declare individual child or parent documents as records. Documents that have already been declared as records can also become part of a compound document later. Certain compound document settings (such as Prevent delete, or Delete child when parent is deleted) can affect the normal disposition of a record. For this reason, Records Manager cannot support the disposition of records that are part of a compound document. The Confirmation page does not display the copy name. When copying a record, the confirmation page displays only the name of the original record. It should display both the original name and the name of the copy. Changing the display name of the record object store disables access to the content of records from RM. Do not change the ROS display name. A search for "is null" or "is not null" incorrectly displays a drop-down choice list. In a Records Manager search for records where the user adds the Current Classification property and specifies a value of is null or is not null, Records Manager displays a choice list of values, which should only be seen with other kinds of operators.
PJ34543 393090 PJ34544 388575 PJ34545 376949
- 81 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID PJ34546 376702
Description Supersede property values are not visible. When you view the properties of a record as a user with read-only privileges, you will not be able to see the value for the Superseded Records field. Only users with Modify Properties access can see this information. The export and import of some internal events fail when imported to a different object store. An internal events export contains two parts: A list of all properties/operators/values (for example, Location = MyLocation) A SQL statement for the query When exporting an internal event with a condition such as Location = MyLocation, the first part of the trigger contains the name of the location (for example, MyLocation), and the second part (SQL statement) contains the GUID of the location from the exported object store. When reimporting the XML file into a new object store, the import tool recreates the location with a new GUID, but does not recalculate the SQL statement. (This is by design to enable the user to create more complex SQL statements than produced by the Records Manager UI). Therefore, the UI shows the appropriate value for the location (for example, MyLocation), but the sweep utility uses the SQL statement directly, and is unable to find any entity for this location (since sweep still uses the old GUID).
PJ34547 376031
PJ34565 366283
Records Manager and Workplace have different functionality during record declaration. When completing the Supersede and ReceiptOf properties during record declaration, Workplace users will need to select the file plan when navigating to the record. For Records Manager users, the default file plan is already selected. An unnecessary blank window appears when viewing an Outlook record. After adding an email document to Workplace via Outlook Integration and declaring it as a record, an unnecessary blank window appears when you view the record in Records Manager. Workaround: Close the extra blank window. Receipt Of info button causes error. With Retain Metadata enabled, destroying the record associated with a receipt leaves the link between the receipt and its associated record unchanged. The name of the associated record appears in the ReceiptOf property of the receipt along with an info button. Clicking the info button should display the associated record's properties in read-only mode. Instead, an error message informs you that the associated record was logically deleted.
PJ34548 365758
PJ34549 365068
Reports
APAR Name Defect ID PJ34550 394513 PJ34551 Description Printable view results are incomplete. The Printable View feature that is available in Search lists only the selected class. Even if you select "Include subclasses, the additional classes are not listed. The report titled Electronic Records Viewed by a User within a specific period report includes extra view events. - 82 -
Description This report lists all of the Get Content events captured by Content Engine, including view events that occurred on the document before it was declared as a record.
Search template
APAR Name Defect ID 779610 Description Records Manager supports only the VQL option for a search or search template that includes a content-based retrieval (CBR) element. Other CBR options, such as, ALL and NONE, are not supported. VQL is the query language that is supported by the Autonomy K2 software, which underlies the Content Search Engine. For more information on VQL syntax, refer to the Autonomy documentation installed on the K2 Master Administration Server: http://<Master_Administration_Server_hostname>:9990/verity_docs/
Single sign-on
APAR Name Defect ID PJ34552 768478 Description In an SSL-redirect environment, Records Manager 4.5 does not redirect users from the HTTPS URL to the HTTP URL. Because users are not sent to the HTTP URL, user sessions run in HTTPS mode and remain on the HTTPS server. As a result, the server hosting the HTTPS sessions has to handle more traffic than expected. Important This problem applies to any container-managed authentication (CMA) configuration that has SSL-redirect configured. Records Manager 4.5 supports WebSEAL from IBM Tivoli Access Manager (TAM) for single sign on (SSO) configurations; in this environment, Records Manager is supported with both Workplace and Workplace XT. Records Manager 4.5 is also supported with Netegrity SiteMinder Web Agent; in this environment, Records Manager is supported with Workplace only. Records Manager 4.5 currently does not support other SSO providers or configurations, including Kerberos. If IBM Records Manager is deployed with Workplace in Container-Managed Authentication mode, or if it is deployed in a Single Sign On (SSO) environment, you are prompted to login (only once during the user session) after clicking Next on the Manage Reporting page in order to launch InfoSphere Enterprise Records reports.
PJ34553 775499
NA 846730
Time Zone Settings

APAR Name Defect ID PJ36573 836350 Description Records Manager does not support using the time zone settings set in the Site Preferences in Workplace or Workplace XT. The application always displays the date
- 83 -
Description and time settings using the browser locale.
User interface
APAR Name Defect ID PJ34554 384406 Description The GUID displays instead of the name in Alternate Retentions. When you select either Location or Record Type for an alternate retention, the GUID displays instead of the name. This problem occurs both in the detail of the alternate retention and in the list of alternate retentions on the Phase Properties page.
Client tools
APAR Name Defect ID NA 777137 Description In WebLogic environments use the wlfullclient.jar, complete the following procedures for each of the IBM InfoSphere Enterprise Records client tools: For WebLogic 9 environments, copy the weblogic.jar file from the BEA_HOME/server/lib WebLogic Server directory on the Application Engine or the Workplace XT machine to the following installed lib directory of the tool machine: IER_install_path/FileNet/IER/FilePlanImportExportTool/lib IER_install_path/FileNet/IER/RMTransfer/lib IER_install_path/FileNet/IER/RecordsManagerSweep/lib For WebLogic 10 environments and later, client applications should use the wlfullclient.jar file. To use the wlfullclient.jar, complete the following procedures for each of the IBM InfoSphere Enterprise Records client tools: 1. Change directories to the WebLogic server/lib directory. For example, use the following command on UNIX systems: cd WL_HOME/server/lib 2. Create the wlfullclient.jar in the WebLogic server/lib directory: java -jar ../../../modules/com.bea.core.jarbuilder_X.X.X.X.jar, where X.X.X.X is the version number of the jarbuilder module in the WL_HOME/server/lib directory. For example: java -jar ../../../modules/com.bea.core.jarbuilder_1.2.0.0.jar 3. Copy the newly-created wlfullclient.jar file from the BEA_HOME/server/lib WebLogic Server directory on the Application Engine or the Workplace XT machine to the following installed lib directory of the tool machine: IER_install_path/FileNet/IER/FilePlanImportExportTool/lib IER_install_path/FileNet/IER/RMTransfer/lib IER_install_path/FileNet/IER/RecordsManagerSweep/lib 4. Edit the batch file for the IBM InfoSphere Enterprise Records tool to include wlfullclient.jar in the CLASS_PATH. For example, for the Transfer tool, edit RMTransfer.bat file to include the following: set CLASS_PATH=%CLASS_PATH%;lib/wlfullclient.jar For more information on creating the wlfullclient.jar, please refer to Oracle site and Copyright IBM Corp. 2002, 2010 - 84 -
Description search for references to wlfullclient.jar.
FileNet P8 Platform
Workplace
APAR Name Defect ID PJ34565 366283 Description Records Manager and Workplace have different functionality during record declaration. When completing the Supersede and ReceiptOf properties during record declaration, Workplace users are required to select the file plan when navigating to the record. For Records Manager users, the default file plan is already selected. The Records Manager base URL stored in Workplace site preferences is not updated if the Records Manager application URL changes. The Records Manager base URL is stored in the Workplace site preferences and is set automatically when Workplace receives the first log in. If you change the Application Engine URL, the Records Manager base URL is not updated automatically. To continue linking Records Manager with Workplace, you must manually refresh the Records Manager base URL information in the site preferences whenever you do the following: Configure Workplace to share an existing preferences file with another Workplace application. Configure the entire Workplace application to run (or not to run) under SSL. Change the hostname or port number used to access Workplace.
PJ34556 362429
To update the Records Manager base URL 1. Determine the site preference name and the object store where the site preferences are located. a. Log in to Workplace. b. Select the Admin tab. c. Click the Site Preferences link. d. On the site preferences page, click the bootstrap link. e. On the bootstrap page, note the Object Store Location for the object store that holds the preference file and Preference (the name of the preference file) under the "Preference Settings". 2. Log in to Enterprise Manager. 3. Locate the object store that holds the preference file and expand it. 4. Navigate to the Root Folder > Preferences folder. 5. In the Preferences folder, locate the file called "Site Preferences for <preference name>," where <preference name> is the name of the preference file. 6. Check out the "Site Preference for <preference name>" file.
- 85 -
Description 7. In the checked out file, search for the following string: <setting key="RMBaseURL"> 8. Replace the value of this <setting> tag to reflect the new base URL of the Records Manager application.
eForms for P8
APAR Name Defect ID PJ34868 323303 PJ34870 686524 Description The JAWS screen reader does not recognize fields with the title on the side.
When opening an eForm directly by entering its URL in the Firefox 2.0 address field, the eForm will not close after clicking the Launch Workflow button or the Close button on the eForm. This behavior can be corrected by adjusting Firefox-2.0 settings in the following manner: 1. Open a Firefox browser window. 2. Type in "about:config" in the address bar. 3. Scroll down to the " dom.allow_scripts_to_close_windows" entry and double click on the entry to switch the boolean condition to true. 4. Close the browser window.
PJ34871 381897
For versions of P8 eForms 4.0 and later, any data returned to a date or time cell from a lookup must be entered in canonical format. Dates must be in YYYY-MM-DD format regardless of the format configured for the cell. Times must be in HH:MM:SS format (including the seconds) regardless of the format of the cell. Note Non-canonical data will work with P8eForms 3.5, Desktop eForms and Forms Manager.
PJ34872 381905
On-form buttons cannot be activated from the keyboard. You must use the mouse to click the button. Resolution: Assign the action to the cell's onchange event to achieve the same result without using on-form buttons. You cannot tab to a form button.
PJ34872 381905 PJ34874 387365
Clicking the small signature icon brings up two Signature Verification dialogs with Mac/Safari 2.0.3
PJ34876 387996 PJ34877
In the eForms Designer help, the method described for changing the text style for a button label causes an "Object Required" error when the form is loaded in IBM FileNet P8 eForms and the button is disabled. For forms containing hundreds of cells, speed is considerably reduced when tabbing through cells that are locked by a signature. - 86 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID 391743 PJ34878 392320 An error occurs when attempting to create a dynamic choice list in a table that provides the choices as values from other columns in the same row of the table. Two methods of creating this dynamic choice list are available: by referring to the column without reference to the row (<<Column1>>), and by referring to the column with the row specified using the Row function (<<Column1[Row]>>). Neither of these methods is currently working. The API method of setting a page as not printable does not work. If you set a page using the API method Page.setPrintable(false), the page is still rendered when the form is rendered to PDF. The sample SQL code in the "Assessment" sample template that comes with eForms Designer 5.0.2 is incorrect. Some data in the expandable rows of a table doesn't print on the overflow pages. If you enter more data than fits in the table's expandable rows visible area and click PDF, some data will not print on the overflow page. Iterating through the Built-in commands collection using the getCommand(number index) produces an "index out of bounds" exception. Description
PJ34879 394352 PJ34886 386173 PJ34954 783825
PJ34992 785409
PJ34993 785293
When a form is taken offline, incorrect results are produced for some functions. The Today and Now functions will show the time and date that the form was taken offline instead of the time and date that the data document was created. Every instance will show the same time and date. The Random function will display a constant value instead of a random number. In Desktop eForms, when you sign a pictures cell using CSP, the signature is invalid when bringing the form online.
PJ34995 784618
Rendition Engine
APAR Name Defect ID NA 910345 Description When publishing Microsoft Project documents, the Gantt chart might not be included in the published document if the splitter bar between the resource descriptions and the Gantt chart is not automatically displayed in Microsoft Project during the publishing process. This occurs if the resolution of the client where the Project document was created is higher than the native resolution of the Rendition Engine server, or if the Project application is not resized properly on the Rendition Engine server desktop. Work around: Log in as the FNRE_Admin user: 1. Increase the resolution of the Rendition Engine server display so that it is higher than most clients where Project files are created. This shifts the splitter bar to the Copyright IBM Corp. 2002, 2010 - 87 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description left on the Rendition Engine display in relation to when it was viewed on the Project client machine, and therefore allows the project to display the Gantt chart. This might not solve the problem if a Project file is created on a client that has a higher screen resolution than the highest resolution of the Rendition Engine server, and the splitter bar was placed near the right edge by the user. 2. Resize the Microsoft Project window on the Rendition Engine server so that the entire Project application fits into the current screen size without maximizing the Project application. This forces Project into the current resolution on the server, and also allows Project to reset the splitter bar between the resource descriptions and the Gantt chart onto the current display. This should fix the exceptions where the Project client resolution is higher than the resolution on the Rendition Engine server. Perform these actions when logged directly into the Rendition Engine server desktop or with a remote access solution that does not change the resolution of the display. Be aware that Remote Desktop may change the display resolution and cause this fix to fail if it is set to a different resolution than the native server desktop.
Desktop eForms 6.0.1

APAR Name Defect ID PJ34880 359276 Description Page tabs are not correctly read by JAWS in Desktop eForms. If the first or last page tab is active, JAWS repeats the page up or page down message. Without sight, the user does not have a reference as to which page they are on or how many pages there are in the form. The JAWS screen reader disabled menu items are read as enabled.
PJ34881 365107 PJ34882 367046 PJ34883 380330
You cannot add documents with non-Latin1 characters in file names.
A lookup that returns a large amount of data into a table can cause the program to crash. Desktop eForms 6.0.1 can open ITXs and IFXs that are compatible with previous versions of Desktop eForms. This feature is not documented in the help. For Desktop eForms, documents with non-Latin 1 characters in the file name cannot be added as an attachment.
661805
784364
- 88 -
WebDAV
APAR Name Defect ID PJ35058 779184 Description When you are using WebDAV, an error message appears after you try to open or download Microsoft Office documents from a server that is using Secure Sockets Layer (SSL). You cannot access these documents because of a limitation described in the Microsoft Knowledge Base article KB 316431 (http://support.microsoft.com/kb/316431).
Internationalization
APAR Name Defect ID 769201 Description You cannot open an object store using Microsoft WebDAV if the folder you are opening contains non-English characters.
IBM FileNet Connector for SharePoint Document Libraries 2.2.0

Defect ID 740757 Description If you delete a collector in IBM FileNet Collector for SharePoint Document Libraries, the associated event log must be manually deleted. To remove an event log, follow the Microsoft Help and Support site instructions for removing event viewer log files. If a UFI Configuration Manager Data Store database has been restored from a backup, an unhandled exception occurs if any modifications are made to the database. This is because the collection source configurations don't get saved during a backup and are missing from the Windows Registry (HKEY_LOCAL_MACHINE\SOFTWARE\IBM\EMRC\4.0\Factories) Workaround: Either use the Windows registry program to backup and restore the factory registry entry or to manually recreate the registry entries. To manually create the required registry entry (repeat on each collection source within the collector): 1. Open the collection source and make any modification (i.e. select or unselect a configuration). 2. Undo the modification by setting it back to the original state. 3. Save. The Last Modified User and Date Last Modified FileNet P8 system properties are overwritten when the Modify document security task is used. This occurs when the Last Modified User and Date Last Modified system properties are mapped to comparable SharePoint system properties and the Modify document security task is applied to documents that are being archived. The results are the initially set SharePoint data are overwritten, where Last Modified User property is set to the P8 Connection configured user, and the Date Last Modified property is set to the date and time the document's security is was modified.
742757
756744
- 89 -
IBM FileNet P8 4.5 Release Notes Known Issues Defect ID 756745 Description When the File in Folder task is configured to inherit folder security with the option to add folder security to document security, the folder permission inheritance is not processed completely. The folder's inherited security from a parent folder is not added to the document security. Only the explicit security configured for the folder class is added. The version series documents are not added as minor versions when the Contentless option is applied. This occurs when the Capture task in a task route is configured to process documents as minor versions as well as contentless documents, but the documents are incorrectly added as major versions. When using the post-processing task, if the option of 'Copy & Lock Down' is implemented, the crawling time of the SharePoint site increases for each query page." When performing an import/export process, there are issues on Microsoft Windows 64-bit operating systems. UFI Services Components must be run in 32-bit compatibility mode by using the CorFlags Conversion Tool (CorFlags.exe) included with Microsoft Visual Studio 2005/.NET Framework 2.0. Use the following syntax to run the tool: corflags /win32+<service_ executable_name> An example is: c:\> CorFlags /32bit+ c:\Program Files\IBM\UFI\Mercure.Host.exe) Information for the SharePoint system site column is supplied by the SharePoint metadata type, such as Title. When an empty SharePoint metadata type site column is mapped to an IBM FileNet P8 CE string data type property that is configured to have a required value, this site column is successfully processed and the IBM FileNet P8 CE document is created, but the required property is assigned an empty string value. When multiple collectors are configured to process the same site collection and the site collection was not previously processed, only one collector is successfully processed because only one collector can create the post-processing site columns and content type. The failed collectors do not execute and the following error is logged: Server was unable to process request. The object has been updated by another user since it was last fetched. To avoid this error, do one of the following: Execute a single collector against the site collection initially. Instead of creating multiple collectors to process a site collection, create one collector with multiple collection sources to process the site collection.
757601
758748
759107
759111
759120
759224
An error message appears when using Japanese characters in a site name after completing a workflow step. The step is completed successfully. To view the completed step, refresh the screen by, for example, pressing Back on your browser window, and then refreshing the page. For IBM FileNet Connectors for SharePoint, if both WebParts and Document Library connectors are installed to the same server, uninstalling the Web Parts solution causes the remaining User Administration web part to become unusable. For example: Existing web parts on pages will show an error indicating that they cannot be - 90 -
759405
IBM FileNet P8 4.5 Release Notes Known Issues Defect ID Description loaded. If attempting to add a new User Administration web part, it is still listed as an option, but attempts to add it will cause an error message to be displayed.
To fix this problem, use either the Central Administration web client or the command line Stsadm.exe and: 1) Retract the Administration web part solution file 2) Re-deploy the Administration web part solution file Note: If both products are installed and you uninstall the Document Library connector, there are no issues. IBM FileNet Connector for SharePoint Document Libraries versions 2.1.0.0 and 2.2.0.0 releases cannot be collocated with Records Crawler or Email Manager.
780096
IBM FileNet Connector for SharePoint Web Parts 2.2.1

APAR Name Defect ID 660127 Description Using IBM FileNet Connector for SharePoint Web Parts with Workplace XT requires tokens to be enabled for the Application Engine. If they are not enabled, after logging into SharePoint, when a user selects to open a document or launch a workflow from a FileNet web part that is configured for Workplace XT, the user will be prompted to log on to Workplace XT. To enable tokens see IBM FileNet P8 help topic: FileNet P8 Administration > Application Engine security. To integrate IBM FileNet Connector for SharePoint Web Parts with Application Engine/Workplace, Workplace must be installed with application-managed authentication. If you want to integrate IBM FileNet Connector for SharePoint Web Parts with an existing instance of Application Engine/Workplace that uses containermanaged authentication, you need to make one of the following changes: Uninstall Application Engine/Workplace and reinstall it to use applicationmanaged authentication. Install a separate application-managed instance of Application Engine/Workplace to integrate with IBM FileNet Connector for SharePoint Web Parts.
743774
Note that any Workplace installation integrates successfully with IBM FileNet Connector for SharePoint Web Parts. When a deployed Admin Web Part for 2.2.0 is upgraded to 2.2.1, the deployed admin Web Part returns the following error: "Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type could not be found or it is not registered as safe." Workaround: After upgrading to 2.2.1, delete existing User Administration web parts from any pages where deployed and re-add the User Administration web part to those pages. In a new browser session, if the first document you attempt to open is a Microsoft Copyright IBM Corp. 2002, 2010 - 91 -
790783
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID 801999 Description Office document (Word or Excel), the document does not open. Instead, the default time zone location displays as the name. If you press OK it will fail. If you fail, or cancel, then reopen the document, the document opens correctly. Does not occur for non-MSOffice files.
Development Tools
Content Engine Java and .NET APIs
APAR Name Defect ID 379982 Description Querying for metadata If your query is intentionally written to retrieve zero result rows, for the purpose of getting the metadata without incurring the performance overhead of fetching the rows, no metadata will be returned. The JDBC provider implements ResultSet.getMetaData() by checking the first column returned in the first row of results. If there are no result rows, the metadata is empty. The JDBC provider does not currently expose any way to get the metadata in such cases. Instead of querying for zero result rows, include "TOP 1" in the query. This will return a single result row, and the metadata will be available. No exception is thrown when setting containment names of DynamicReferentialContainmentRelationship objects that have a name that exceeds 255 characters. A containment name that is longer than this limitation is automatically truncated to 255 characters. The BatchItemHandle methods getException and hasException do not currently work as designed. These methods do not indicate the items that failed in the UpdatingBatch operation. A failed UpdatingBatch returns only a single exception, which applies to the batch as a whole.
381685
740397
Documentation FileNet P8 Documentation

Help system and Search functionality
APAR Name Defect ID NA 859185 Description The following information should have been included in the Support Matrix section of the directory server topics in ECM help: The LDAP attributes that P8 reads, when resolving member users and member groups in a group entry, are: LDAP Provider AD LDAP Attribute member
- 92 -
ADAM eDirectory SunONE Tivoli NA 906895
member member uniqueMember, member uniqueMember, member
In the topic "Required minimum access rights by operation" (found in the ecm_help at System Administration > FileNet P8 Security > Authorization > Required minimum access rights by operation) the tables for Checkout minor version and Checkout major version should have stated that the required minimum access rights for a Document are Major Versioning or Minor Versioning. In other words, as of 4.x, a user with either the Minor Versioning or the Major Versioning rights can check out a document.
Plan and Prepare Guide

APAR Name Defect ID NA 842378 Description In the Preparing DB2 for Linux, UNIX and Windows servers section, the following information should be added: User-defined index fields include property templates. In addition, you must choose a minimal set of add-ons before creating an object store. Each add-on reserves space in a row whether the add-on is used or not.
Application Engine
APAR Name Defect ID NA 849682 Description The installation instructions for Configuring Application Engine on JBoss are missing a step. The task "Configure Application Engine (JBoss)" should contain the following changes: The configuration edits must be made to the run.conf file instead of the application server startup script run.sh or run.bat. The step "Configure LDAP settings on Application Engine need to exactly match the Content Engine settings." The section should contain the following three additional substeps after step c: d. Copy the new <application-policy name="FileNetP8Engine"> entry, and paste the copied entry directly before the entry you copied (<application-policy name="FileNetP8Engine">). e. Change the first instance of the <application-policy name="FileNetP8Engine"> to <application-policy name="FileNetP8">. f. Move all the FileNet-related <application-policy name=> elements before the <application-policy name="other"> element. After the three new steps, continue with the remaining substeps to save the file and restart JBoss.
- 93 -
Content Engine
APAR Name Defect ID 752140 Description The topic entitled "View storage area states" describes the disabled storage area icon as follows: "Storage area has been disabled (unavailable to service requests: users cannot add, view, or modify documents in the storage area)." This statement is partially incorrect, because users can view documents in a disabled storage area. A limited user cannot update the P8 online help URL from the FileNet Enterprise Manager root properties page. The Content Engine Administration Guide includes an obsolete topic, "Export document class schema." In the P8 online help, this topic is located under "System Administration > Content Engine Administration > Exporting and Importing > How to". Ignore this topic. The topic entitled "Fixed Content Devices properties (General tab)" does not contain information about the following supported fixed content device providers: IBM Content Manager OnDemand IBM Content Integrator
768277
792280
NA 794829
The missing information is available in the documentation for the 4.5.1 Release. NA 841060 Active Directory is the only directory server type for which you can select Kerberos support when configuring Content Engine. The following topics erroneously contain references to selecting Kerberos support for directory server types other than Active Directory: Install and configure Content Engine > Configure Content Engine instances > Configure instances using the graphical user interface. Upgrade Content Engine software from version 3.5.x > Configure Content Engine instances > Configure instances using the graphical user interface.
NA 843139
In the topic To create Content Engine operating system accounts, the description of the Content Engine database user for DB2 LUW databases should read: Operating system user account on the database server. This user is granted database permissions for Content Engine access to the DB2 database. The user needs access to each database created for an object store and the GCD database. Separate accounts can be used for each object store, but are not required. A user can be configured to access multiple object store databases, depending on your installation requirements. Permissions granted by the database administrator determine which object store databases any user can access.
NA 906636
In step 1 of the procedure "To configure permissions for a FileNet P8 domain" in the topic "Establish the FileNet P8 domain and Global Configuration Data (GCD)," delete the (optional) action in the "Perform this action..." entry for the Specify Domain Administrators" row to remove the Content Engine system user (ce_bootstrap_admin). That is, the Content Engine system user ce_bootstrap_admin must not be removed. The topic "Component trace logging properties (General tab)" is incorrectly included in the documentation. These properties are not applicable to this version of Content - 94 -
NA
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID 908991 Description Engine.
Content Federation Services

APAR Name Defect ID NA 787304 Description The Content Federation Services Installation and Upgrade Guide should have included the following information about the disk requirements for installing and upgrading CFS components: CFS 4.5 requires 136MB for both a new installation and for upgrades from 4.x. NA 787307 The CFS Installation and Upgrade Guide should have included the following information about the logs to review during CFS installs and upgrades: There is one file generated at the end of an installation or upgrade. This file is located under CFS_HOME. The naming convention is: federator_install_log_<CFS version>-<patch level>.txt for example, federator_install_log_4.5.0.txt or federator_install_log_4.5.0-001.txt
Workplace XT
APAR Name Defect ID NA 852145 Description In the IBM FileNet Workplace XT 1.1.4 Installation and Upgrade Guide task called "Deploy IBM FileNet Workplace XT (WebSphere)," there are several instances of "Workplace" that should be "Workplace XT."

APAR Name Defect ID NA 841274 Description Add the following step between steps 7 and 8 in the Windows procedure in the topic (optional) Install additional locales: If prompted, select the Install all platform binaries option if you want licensed language locales not only for the Windows operating system on the machine where you are installing CSE Locales, but also for all other supported operating system types, such as AIX, HP-UX, Linux, and Solaris. Add the following step between steps 5 and 6 in the UNIX procedure in the topic (optional) Install additional locales: If prompted, select the Install all platform binaries option if you want licensed language locales not only for the UNIX operating system on the machine where you Copyright IBM Corp. 2002, 2010 - 95 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description are installing CSE Locales, but also for Windows and the other supported UNIX operating systems (AIX, HP-UX, Linux, and Solaris). NA 919039 In the P8 4.5.1 Information Center topic "Install or upgrade IBM FileNet P8 Platform > Upgrading and configuring IBM FileNet P8 Platform > Upgrading and configuring Content Engine and Content Search Engine > Upgrading from version 3.5.2 > Completing pre-upgrade Content Engine configuration > Determining the CBRenabled properties in an object store," the SQL query in step 2 does not determine which properties are enabled for content-based retrieval. To determine these properties, replace step 2 with steps 1 through 5 of the document "Best practice: Unconfigure content-based retrieval (CBR) prior to upgrading Content Engine (CE) 3.5.x object stores" at http://www01.ibm.com/support/docview.wss?uid=swg21405324.
BAM
APAR Name Defect ID PJ35032 785853 Description In the Cognos LAVA installation documentation, the links for Creating Application Servers for WebSphere 6.0 and 6.1 do not find the correct topics. Workaround: Use the following link to access the documentation for WebSphere 6.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0//index.jsp Search for "Creating application servers". Use the following link to access the documentation for WebSphere 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1//index.jsp Search for "Creating application servers". The BAM online help topic "Import the IBM FileNet BAM Projects for a new installation" is incorrect. The topic discusses using a URL-based connection when configuring the JDBC agent on WebSphere; however, you should use a datasource-based connection for all of the application servers. The updated Configure a JDBC Agent section should read: Configure a JDBC agent The VMAEDM_JDBC_AGENT is created after importing the OOTBConfiguration project, and is used to access data from the Process Analyzer database. The VMAE_JDBC_AGENT uses a datasource-based connection. By default, the JNDI name is com.celequest.context. Follow the IBM Cognos Now! documentation to configure a datasource for your particular application server type. The datasource created in this process should have a JNDI name that matches what is configured in the VMAE_JDBC_AGENT. The Quick Start Guide for the Business Activity Monitor (BAM) 4.5.0 does not explicitly name the installation guide for the Cognos Now! software. Users are instructed to use the Cognos Now! software installation instructions. The set of instructions is titled "Installing and configuring Cognos LAVA." This set of instructions, is intended and correct. - 96 -
785930
811205
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description The first step of "Step 4: Install and configure FileNet Business Activity Monitor" should be the following text: 1. Install the Cognos Now! software following the Installing and configuring Cognos LAVA document (install.pdf) available in the IBM FileNet Business Activity Monitor software package.
Process Engine
APAR Name Defect ID 786175 Description An incomplete sentence exists in the topic \ecm_help\pe_help\designer\vwworkflowpropertiesdialog.htm The incomplete sentence will be replaced with the following sentence: "For the workflow collection, specify the properties such as the name of the workflow collection."
Process Analyzer
APAR Name Defect ID 780258 Description Scenarios that were created with Simulation Designer v3.5.2 might experience the following error when the simulation is run: "Java.lang.illegalArgumentException: Not participant field type F_Originator: int" Workaround: 1. Make a copy of the scenario definition as backup. 2. Open the scenario definition in Simulation Designer and remove the workflow that has F_Originator assigned as a participant for a step. 3. Re-import the workflow and re-create any simulation properties that were previously set for the workflow. Microsoft SQL Server 2000 784730 Although it is mentioned in the online help, Microsoft SQL Server 2000 is not supported in this release. Instead, Microsoft SQL Server 2005 is required for all new installations or upgrades. Because Microsoft SQL Server 2000 is no longer supported, the "Work around the Microsoft Analysis Services 2000 64K limitation" topic is no longer relevant. Disregard this topic and any other mentions of Microsoft SQL Server 2000. Move the Process Analyzer database files topic The "Move the Process Analyzer database files" steps should be amended as follows: 1. Use the Process Task Manager to stop PA. Stop the Process Analyzer Services Manager. Copyright IBM Corp. 2002, 2010 - 97 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description 2. In Microsoft SQL Server Management Studio (SQL Server 2005), detach the PA database. 3. Move the PA data files <PADBname>mdf and <PADBname>.ldf from the default SQL Server data file location to your preferred location. The default SQL Server location is the Data folder in the SQL Server instance folder. 4. In Microsoft SQL Server Management Studio (SQL Server 2005), attach the database and reference the new file location. 5. Start the Process Analyzer Services Manager and use Process Task Manager to start PA. Note that the .mdf and .ldf file names will be different in your configuration, as these names correspond to whatever you named your database. Previously, these files were called VMAEDM.mdf and VMAEDM.ldf. Compress the Process Analyzer database The Compress the Process Analyzer database topic should include the following information for Step 3 and its sub steps: 3. If the PA database is installed locally, select Compress Database from the Action menu to start the Compression Wizard. If the database is not installed locally, you must run the compression wizard on the remote database server. To do so, perform the following steps on the remote database server. a. The first time: i. Install the appropriate Microsoft SQL Server JDBC driver for SQL Server 2005. You can download it from http://www.microsoft.com. ii. Create an installation folder (for example, C:\Process Analyzer). iii. Copy the _java folder from the PA Engine to the installation folder. The java folder is located directly under the installation folder. iv. Copy the following files from PA Engine to the installation folder. The files are located in the java folder directly under the installation folder: pa.jar paResources.jar pe.jar pe3pt.jar peResources.jar analyzer.properties b. Run the following command from the command line to start the compression wizard. For SQL Server 2005: <installDir>\java\bin\jre\bin\java.exe -Xms128m -Xmx300m cp <installDir>\pa.jar;<installDir>\paResources.jar; <installDir>\pe.jar; <installDir>\peResources.jar; <installDir>\pe3pt.jar;<MSSQL Driver Dir>\sqljdbc_1.2\enu\sqljdbc.jar Copyright IBM Corp. 2002, 2010 - 98 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description "Danalyzer.properties=<installDir>\analyzer.properties" filenet.pa.apps.rollup.RollupApplication -remote PJ35141 785913 After installing the PA Client software using the silent installer, the shortcut to the Process Analyzer User Guide online Help does not work from the Programs list. Workaround: In the Programs list, locate PA documentation and right-click Process Analyzer User Guide. Select Properties and enter the correct URL in the target: <ECM documentation URL>/pa_help/userguide.htm, where <ECM documentation URL> is the base URL you entered during the Process Analyzer Client installation.
Process Task Manager

APAR Name Defect ID 802464 Description The topic titled Isolated region recovery overview requires clarification. Under the subtopic General procedure for enabling recovery of one isolated region, Step 1 should be amended to the following: 1. In the database, create one or more custom table spaces for the exclusive use of one isolated region. Grant table space privileges to the Process Engine runtime user. Under the subtopic General procedure for restoring or rolling forward an isolated region, the Note should be amended to the following: Note: Point in Time Restore (PITR) is not supported. The topic titled Regions General tab requires clarification. Under the subtopic General tab, the sentence should be amended to the following: Set the custom table space properties for the selected region. From the Regions node on the Process Task Manager, select a region, then click the General tab. The topic titled Enable recovery for a new region, not initialized requires clarification. Step 1 should be amended to the following: 1. In the database, create the new table space. Grant table space privileges to the Process Engine runtime user. The topic titled Convert existing region to recovery enabled requires clarification. The following information should be added after the third paragraph of the topic: If you are upgrading from a prior release, all regions must be upgraded per the upgrade documentation before starting this procedure. In vwtool, use the dbviews command to check the current database view names. Database view names should exist. If they do not exist, it is possible the regions were not completely upgraded when coming from a prior release. Complete the upgrade process before continuing. Under the subtopic Converting existing isolated regions, Steps 2, 3, 4, 5, and 11 should be amended and added with the following: 2. Use the database tools to create one or more new table spaces for the existing Copyright IBM Corp. 2002, 2010 - 99 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description region, according to your database. Grant table space privileges to the Process Engine runtime user (such as, f_sw). For example, for Region 100, create reg100data. 3. In Process Task Manager, specify one or more custom table spaces for the region. See Regions General tab for more information. If Process Analyzer is configured for Process Engine, stop Process Analyzer in Process Task Manager. After you have specified the new region information, make sure you apply your changes. When the changes are applied, close the Process Task Manager. 4. Reopen Process Task Manager and verify that the table space information is correct for the existing region. The table spaces listed should include the original table spaces along with the new table spaces. 5. In Process Task Manager, lock the region. The region should remain locked and unavailable for use until after Step 8. 11. (Optional) After the convert process, existing database views are still usable. Because the tables are moved to another location in the database, the database views are not affected. However, to recreate the database views, use the following step. In vwtool, set the correct region, then use the createDBViews command to recreate the database views. Select either the v or s options. The v option automatically creates the views and the s option creates a script you run manually from the RDBMS database tools Under the subtopic Running the region conversion utility, the examples within this subtopic have been updated and can be found in the IBM FileNet P8 Process Task Manager Region Recovery Technical Notice located on the Product Documentation for FileNet P8 Platform Web site.
FileNet Deployment Manager

APAR Name Defect ID 838187 Description The FileNet Deployment Manager online help topic "Object Store Assets" implies that you can add a new version to an existing document. The "Document" section of this topic states that you can retain the version series ID by selecting the Import Object ID option in Enterprise Manager's Import Helper, thereby adding a new version to an existing document. This is incorrect: you cannot add a new version to an existing document in 4.5.0. (This limitation has been removed in version 4.5.1 of FileNet Deployment Manager.)
P8 eForms
APAR Name Defect ID PJ34886 386173 Description The Tutorial for eForms Designer, which an be found in the default location C:\FileNet\eForms\Designer\Tutorials\Use with P8, contains the following errors: Step 8 of Task 34: Configure an Auto-increment states the following SQL code: Select InvoiceNo from tblInvoiceNo;
- 100 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description Update tblInvoiceNo Set InvoiceNo = "InvoiceNo" + 1; Select InvoiceNo from tblInvoiceNo; <<1@DANumber>> The SQL code should instead state the following: Select InvoiceNo from tblInvoiceNo Update tblInvoiceNo Set InvoiceNo = "InvoiceNo" + 1 Select InvoiceNo from tblInvoiceNo; <<1@DANumber>>
Desktop eForms 6.0.1

APAR Name Defect ID PJ34884 382803 Description In the "Export records" and "Import records" topics, the Help does not say that users can export data in the XML File and eForms XML Data formats. In the "Export records" topic, the help does not say that the data for all cells will be exported even though users can select specific cells for exporting. Forms can be saved in the IFX format. From the File Menu, select Save As and choose IFX as the format.
Rendition Engine
APAR Name Defect ID 840790 Description To clarify the information related to Rendition Engine Oracle client requirements, the following Oracle packages should be installed on the Oracle client (Rendition Engine) server when the Oracle database is remote from the Rendition Engine: Network Utilities (same as oracle net) SQL* Plus JDBC/OCI Interfaces Windows Interfaces
907727
The following information should be appended to the end of the CAUTION in the Inherited Security section of the Object security help topic located in Records Manager > FileNet P8 security: There are several places in the IBM FileNet Records Manager code which require a security parent in order to work correctly with multi-filed records: viewing folders filed in, Disposition Sweep, and Autodestroy. If you are performing one of these tasks, you cannot disable the inherit security function by clearing the "inherit security from folder" checkbox. You will receive a security parent error.
- 101 -
Records Manager
User help
Browser language settings APAR Name Defect ID PJ34392 772439 Description The following information will be included in a future refresh of the Records Manager documentation: When Records Manager has FileNet P8 components deployed in a JBoss environment or a WebLogic environment, and the browser setting is updated, properties might not display according to the new browser language until the cache has been refreshed. Restarting JBoss or WebLogic also corrects this error.
NOTE Other clients that change the language will experience the same behavior before
the cache refresh. PJ34393 772425 The following information will be included in a future refresh of the Records Manager documentation: Records Manager displays a localized interface according to the browser language setting. Tools that do not use a browser set the language according to the Records Manager server locale.
NOTE If you change the browser locale when you are working in Records Manager 4.5,
you must log out of your local Records Manager session, close the browser window, and log back in to Records Manager for the new locale setting to take effect. Hold Sweep and Disposition Sweep APAR Name Defect ID PJ34540 775871 Description The following information will be included in a future refresh of the Records Manager documentation: In the Preview Entities page that is used for reviewing the entities that match the hold criteria for executing Hold Sweep, the filter does not support the % or & characters. Third party report generation tools APAR Name Defect ID NA 904255 Description This topic entitled "Generating reports using third-party report generation tools" in the RM Developer's Guide is out of date and needs be removed. http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.d oc/developer_help/records_manager_api/guide/rm_dev_generating_reports_using_thir d_party_report_generation_tools.htm In place of that topic, use the section inside the product's user Help titled "Report Generation to create a new customized report. http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/topic/com.ibm.p8.doc/rm_help/ report_generation.htm - 102 -

APAR Name Defect ID 784203 Description In the IBM Enterprise Content Management Widgets Reference, the "Payload Types" topic is missing information. In the WorkItemField payload type description, the following information should be included:
NOTE For the "value" attribute, the JavaScript data type must match the type of the
data field, as shown in the table.

Data Field Type "value" JavaScript type String Integer Float Boolean Time string (e.g. "ECM Widgets") number with no decimal places (e.g. 100) number (e.g. 3.14159) boolean (e.g. true or false) JavaScript Date object (e.g. new Date()).
785819
A configuration procedure having to do with FileNet P8 eForms is missing from the IBM Enterprise Content Management Widgets Installation Guide. If you have installed FileNet P8 eForms in Workplace XT, and if you want to use the ECM Create Action widget to launch workflows associated with eForms, then you must enter the Workplace XT base server URL in the Process Configuration Console. This procedure is covered in the FileNet P8 Documentation online help. Using the table of contents in the left pane of the online help, navigate to the topic User Help > Integrating Workflow > Workflow applications > Process Configuration Console > VWServices > View or Modify VWServices properties > Set web application properties.
IBM SharePoint Connectors Document Libraries 2.2.0.1

APAR Name Defect ID 795624 Description The Connector Services web.config file section in the "Fine-tune performance settings" topic incorrectly identifies the location of the web.config file. The section should read as follows: Connector Web Services allows you to customize your configuration using the web.config file. This file allows you to optimize the tasks you need to perform. The web.config file is a configuration file for the Web Services web site and is located at <SharePoint_install_drive>\Inetpub\wwwroot\FnSpWebServices. 823760 Currently, the "Run the archive process' in the import_process.htm topic includes the procedure for starting the archive process: To run the archive process 1. From the server where the Connector for SharePoint Document Libraries is installed, open the Microsoft Windows Control Panel. 2. Select Administrative Tools, and double-click the Services applet. 3. In the Services applet, manually start the Task Routing Engine service This procedure should also include instructions for stopping the archive process:
795640
- 103 -
Description To stop the archive process 1. From the server where the Connector for SharePoint Document Libraries is installed, open the Microsoft Windows Control Panel. 2. Select Administrative Tools, and double-click the Services applet. 3. In the Services applet, manually stop the Task Routing Engine service.
Content Java API Compatibility Layer

APAR Name Defect ID 755691 Description Issue: The use of the Blowfish encryption algorithm for encrypting session tokens is replaced by the FIPS 140-compliant Advanced Encryption Standard (AES) algorithm. The Content Java API Developer's Guide and Content Java API reference help are not updated for the switch from Blowfish to AES. Resolution: The Content Java API Compatibility Layer documentation is no longer being updated. The sections of that documentation affected by the change to AES are provided below with the necessary updates. Note that some sections have been removed, while others are modified with the pertinent information.
Security Concepts > Encryption Schemes

The following topic has been reduced from two paragraphs to one:
Symmetric Encryption Protection Level

For a protection level of Session.SYMMETRIC, credentials are encrypted. Encryption is based on the encryption keys created by running the MakeCryptoKeys utility on the Web Application server. The generated keys are used with the Advanced Encryption Standard (AES) algorithm. For procedural information about setting up your environment for symmetric encryption and for manually generating a cryptographic keys file, refer to Setting up Symmetric Encryption in the Configuration and the Content Java API section. For details on MakeCryptoKeys and its output, refer to Creating Cryptographic Keys for Symmetric Encryption below.
Working with Security

Creating Cryptographic Keys for Symmetric Encryption
During Application Engine installation, the administrator can optionally select sitewide symmetric credentials protection. This option causes the setup program to generate a CryptoKeyFile.properties file containing cryptographic keys. (You can also create cryptographic keys outside of the installation process by running the MakeCryptoKeys utility.) The generated keys will be used with the Advanced Encryption Standard algorithm. If you install multiple Application Engine servers, you can just copy one of these generated files to all of the Application Engine servers. Otherwise, each of the Application Engine server s will have different key files. The setup program also updates the WcmApiConfig.properties file with the selected protection scheme and the path to the CryptoKeyFile.properties file. The setup program places the CryptoKeyFile.properties file in an authentication folder on the Application Engine server. (The installation documentation specifies the Copyright IBM Corp. 2002, 2010 - 104 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description default location, which differs by operating system type. However, the administrator can choose to move the file to another location and can update the WcmApiConfig.properties with the new location.) When configuring Application Engine for symmetric encryption during installation, you can specify that you want to generate limited strength or maximum strength cryptographic keys. If you select "Create maximum strength keys", then 256-bit keys are generated; otherwise, limited strength (128-bit) keys are generated. Java Development Kit (JDK) 1.4 (and later) includes the Java Cryptography Extension (JCE) with jurisdiction policy files shipped with "strong" but limited cryptography, which limit key length. Your application might encounter an "unsupported keysize" EncryptionException. This exception occurs under the following circumstances: If you are using symmetric encryption with keys that are over a certain length. If you are serializing Content Java API objects as parameters or return values of an EJB method and you have a CryptoKeysFile configured, even if you are not using symmetric encryption. (Internally, the serialization encrypts the credentials of the Session object that is contained in each Document, Folder, etc.)
The EncryptionException occurs because the JDK includes the Java Cryptography Extension (JCE) with jurisdiction policy files shipped with "strong" but limited cryptography, which limit key length. To resolve the problem, see the Troubleshooting Encryption Exceptions topic below.
Running MakeCryptoKeys
When testing encryption of credentials tokens during your application development, you can run MakeCryptoKeys from a command line to manually generate one or more encryption keys. (You can display usage information by running the utility with no arguments.) Specify the number of keys and the size (in bits) of the keys to be generated. We recommend that you keep the number of keys to the minimum that will satisfy your security requirements (the default is 3). The default key size is 128 bits. If you do not have the unlimited strength policy files, you should use keys of 128 bits. If you specify a size greater than 256 bits, the utility generates a warning and reduces the value to 256 bits. Due to initialization processing, a delay of several seconds is not unusual when MakeCryptoKeys starts. The utility writes its output to standard output (System.out); redirect the output to a CryptoKeyFile.properties file. Edit the WcmApiConfig.properties file to add an entry specifying the full path to the key file. The following command creates three 256-bit keys, and redirects the output to a file. (This example assumes that your classpath is already set up to include the Content Java API JAR files.)
java com.filenet.wcm.api.util.MakeCryptoKeys -n 3 -s 256 > CryptoKeyFile.properties
To test, instantiate a Session object, specifying symmetric credentials protection for the credTag parameter of the method call, as shown below. (You can specify either the string "Symmetric" or use the Session.SYMMETRIC constant.)
Session sess = ObjectFactory.getSession("com.example.apps.MyTestApp", Session.SYMMETRIC, "tester", "testpswd");
Refer to the online help for the MakeCryptoKeys class for additional information. Copyright IBM Corp. 2002, 2010 - 105 -
Configuring a Security Provider for a J2EE Application Server Environment

This section, including its subtopics Configuring for the Sun JDK and Configuring for the IBM JDK, apply only to JDK 1.3.x and have been removed.
Troubleshooting Encryption Exceptions

This section provides information you can use to determine the cause of some frequently encountered EncryptionException messages. Note that the message text contains the location of the JRE, since a physical server can have multiple JREs installed. In addition, the message text contains additional information, where appropriate, for nested exceptions. The following exception text represents some of the common failures you might encounter that are related to misconfiguration of symmetric encryption or security providers, and pointers you can use to troubleshoot the problem.
com.filenet.wcm.api.EncryptionException: Problem creating JCE Cipher instance for AES/ECB/NoPadding algorithm. java.home=C:\java\jdk1.4.2\jre. Exception was java.lang.NoSuchAlgorithmException: Cannot find any provider supporting AES/ECB/NoPadding
This exception indicates that no provider supplies AES. Since most providers do provide AES, this is probably indicative of a problem in the static configuration of java.security, static configuration of java.security has not been done, or the .jar file for the provider is missing from the classpath.
com.filenet.wcm.api.EncryptionException: Problem creating JCE Cipher instance for AES/ECB/NoPadding algorithm. java.home=C:\j2sdk1.4.2\jre. Cause: java.lang.ExceptionInInitializerError; Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs; Caused by: java.lang.SecurityException: Cannot locate policy or framework files!
This exception, which traverses nested exception levels to get to the underlying failure, can be caused by a number of different problems, but generally means that there is a problem between the compatible levels of the JCE framework and a specific JCE provider. For example: o Either the JCE provider is incompatible with the framework or vice versa. These components conduct mutual authentication checks of each other and will fail if found to be incompatible with each other. JRE certifications (found in jre\lib\security\cacerts) might be expired. Consult your JDK vendor for the procedure to obtain new certifications. Missing or misplaced policy files. Make sure that all policy files are available and in the proper locations.
o o
com.filenet.wcm.api.EncryptionException: Problem initializing encryption/decryption with keyId 8110f2b1, size 256 bits. java.home=C:\java\jdk1.4.2\jre. Exception was java.lang.SecurityException: Unsupported keysize or algorithm parameters
This exception indicates a keysize problem and occurs under the following circumstances: o If you are using symmetric encryption with AES keys that are longer than the - 106 -
IBM FileNet P8 4.5 Release Notes Known Issues APAR Name Defect ID Description keysize supported by your installed policy files. o If you are serializing Content Java API objects as parameters or return values of an EJB method and you have a CryptoKeysFile configured, even if you are not using symmetric encryption. (Internally, the serialization encrypts the credentials of the Session object that is contained in each Document, Folder, etc.)
To resolve the problem, upgrade to an "unlimited strength" version of the policy files. See "Downloading the 'Unlimited Strength' Jurisdiction Policy Files" in the Java Cryptography Extension (JCE) topic at java.sun.com or the equivalent documentation from your JDK vendor.
Content Java API Reference Help Updates

The description of the MakeCryptoKeys class is changed as follows: public class MakeCryptoKeys extends java.lang.Object This class generates cryptographic keys for use with Symmetric encryption of session credentials tokens. The encrypted keys are used by the Advanced Encryption Standard (AES) algorithm. A site administrator is usually responsible for configuring site-wide security. However, when testing encryption of credentials tokens during application development, an application programmer might wish to run this utility to generate keys for the test. After generating the test keys and installing them on the Application Engine server, call getSession on the ObjectFactory class to instantiate a Session object, specifying Session.SYMMETRIC for the credTag parameter. You can display usage information by running MakeCryptoKeys with no arguments from a terminal command window. Input to the utility is the number of keys to generate and the key size. Key size is specified as 128, 192, or 256 bits. The default key size is 128 bits. Specifying 192-bit or 256-bit key sizes requires use of unlimited strength security policy files. If you specify a key size greater than 256 bits, the utility generates a warning and then uses a key size of 256 bits. The utility's output is written to standard output (System.out), which you redirect to a file (for example, CryptoKeyFile.properties). A delay of several seconds is not unusual when the utility starts. The following command creates three keys that are 128 bits in length, and redirects the output to a file:
java com.filenet.wcm.api.util.MakeCryptoKeys -n 3 -s 128 > CryptoKeyFile.properties
The Application Engine installation process creates an entry in the WcmApiConfig.properties file that identifies the default location of the CryptoKeyFile. The location differs depending on the type of installation performed and the platform on which the installation occurs. Refer to your installation documentation for the specific location for your environment. If the location of your CryptoKeyFile is different, use a text editor to create an entry in the WcmApiConfig.properties file that points to the correct location of your CryptoKeyFile.properties file. The following are two examples of such an entry:
CryptoKeyFile = C:\\filenet\\CryptoKeyFile.properties
- 107 -
CryptoKeyFile = CryptoKeyFile
Keywords are case insensitive. In the first example above, note the use of double backslashes (\\) in the path statement of the entry's value portion. WcmApiConfig.properties is read as a Java PropertyResourceBundle. If your operating system uses backslashes as directory separator characters, the syntax requires that you double any literal backslash character that you use in the value portion of a keyword/value entry. If slashes are not used, you can specify the value with or without the ".properties" extension, as shown in the second example. The Content Java API reads the WcmApiConfig.properties file at runtime. It locates the CryptoKeyFile.properties file in the following manner: If the value specified for the CryptoKeyFile keyword contains a forward slash (/) or backslash (\) character, the value is read as the full and complete path name to the file that contains the encryption keys. If no path is specified, the Content Java API attempts to open CryptoKeyFile.properties according to the search scheme described in the Java ResourceBundle class. For more information, refer to Key Configuration Files and Logs in the Application Engine Administrator's help and Creating Cryptographic Keys for Symmetric Encryption in the Content Java API Developers Guide. Batching: Unless otherwise noted, the methods in this class are unaware of batching, and their behavior is undefined when a batch is active. Execution Venue: Unless otherwise noted, the methods in this class are executed locally. They do not make a network round-trip. See Also: Security Concepts in the Content Java API Developers Guide
Content Engine Java and .NET API Developer's Guide

Description NA 866148 An invalid list of restrictions on object locking exists in the Content Engine Java and .NET API Developer's Guide > Cooperative Locking Concepts > Locking an Object. Because there are no restrictions on locking an object, the following statement and associated list items are incorrect and should be disregarded: However, you cannot lock the following: A Document object that is checked out by another user A "frozen" Document object (that is, one whose IsFrozenVersion property is true). An object that is locked by another cooperating application The root folder"
- 108 -
IBM FileNet P8 4.5 Release Notes Resolved Known Issues
Resolved Known Issues

Resolved in Workplace XT 1.1.4
Defect ID 784150 Description You can use an entry template to add and assign a specific document class to documents, and then check out the documents. However, if you modify that same entry template to assign a different document class, you cannot use that entry template to check in documents that were assigned the initial document class. If you are using WebSphere and Workplace XT 1.1.3 is configured to use port 80, the Application Integration BCS download will fail with a 'Page Not Found' error. The workaround is to specify the WebSphere port, "WC_defaulthost," explicitly in the URL. During the installation process, if information is not entered in the Object Store name field or Preference name field, users cannot log into Application Integration BCS. There is no error message indicating information is missing and preventing users from logging in. When you upgrade from Workplace XT 1.1.2 to Workplace XT 1.1.3, the Application Integration BCS view site preference does not contain default values for Columns 13. When you open a new document in a new window in a Microsoft Office application integrated with Workplace XT using Application Integration BCS, the F6 key does not work if you want to move your focus from one window to another. The workaround for this issue is to press Shift + F6. When you cancel a checkout after closing the currently checked out document and the Delete after canceling checkout site preference is set to Yes, the local copy of the document is not deleted from the local file system.
PJ35171 786069
PJ35105 784148
PJ35106 784887 PJ35100 782757
PJ35102 782782
- 109 -
IBM FileNet P8 4.5 Release Notes
- 110 -
IBM FileNet P8 4.5 Release Notes Notices
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 North Castle Drive Armonk, NY 10504-1785 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. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 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.
- 111 -
IBM FileNet P8 4.5 Release Notes Notices Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.com/legal/copytrade.shtml. Adobe is a registered trademark of Adobe Systems Incorporated in the United States, and/or other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. UNIX is a registered trademark of The Open Group in the United States and other countries. - 112 -
IBM FileNet P8 4.5 Release Notes Notices The Oracle Outside In Technology included herein is subject to a restricted use license and can only be used in conjunction with this application. Other company, product, and service names may be trademarks or service marks of others.
U.S. Patents Disclosure

This product incorporates technology covered by one or more of the following patents: U.S. Patent Numbers: 6,094,505; 5,768,416; 5,625,465; 5,369,508; 5,258,855.
- 113 -
Program Number: 5724-R76, 5724-R81, 5724-R74, 5724-R96, 5724-R81, 5724-R85, 5724-S13, 5724-S19, 5724-S17
Printed in USA
SC19-2719-07

c1927197 PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

c1927197 PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

IBM FileNet P8

IBM FileNet P8 Release Notes Software Release 4.5 Contents

Copyright IBM Corp. 2002, 2010

IBM FileNet P8 4.5 Release Notes Revision Log

FileNet P8 Documentation: FileNet P8 Plan and Prepare Guide: 842378 9

Copyright IBM Corp. 2002, 2010

Independent Software Vendors: Workplace XT: 840048

Records Manager: 836350, 846730 FileNet P8 Documentation: Content Engine: 794829

Content Engine Java and .NET APIs: 379982, 381685

Copyright IBM Corp. 2002, 2010

Copyright IBM Corp. 2002, 2010

Initial release of P8 4.5

Copyright IBM Corp. 2002, 2010

IBM FileNet P8 4.5 Release Notes Introduction

Access IBM FileNet documentation, compatibility matrices, and fix packs

Simplified application data deployment

Copyright IBM Corp. 2002, 2010

IBM FileNet P8 4.5 Release Notes Whats New

IBM Support Assistant

FileNet Services for Lotus Quickr 1.0

Copyright IBM Corp. 2002, 2010

See Lotus Quickr at: http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/index.jsp?topic=/com.ibm.lotus.quickr.admin.wpv81 .doc/ecm/ic_ecm_c_configure.html for more information.

New access role

Removed root user restriction

Expanded single sign-on support

Improved language support

Copyright IBM Corp. 2002, 2010

Business Activity Monitor

Application name changes

Changes to the "Import Out-of-the-box configuration project" topic

Copyright IBM Corp. 2002, 2010

New upgrade procedure

Improved language support

Terminal Release of BAM

Improved configuration and deployment during installation

Improved Enterprise Manager functionality

Copyright IBM Corp. 2002, 2010

Removed root user restriction

Support for DITA Rendition Engine

Improved language support

* These languages are available only for Workplace.

FileNet Content Federation Services

IBM FileNet P8 4.5 Release Notes Whats New

Integration with Content Engine

Copyright IBM Corp. 2002, 2010

IBM FileNet P8 4.5 Release Notes Whats New

New location for the upgrade instructions for custom applications

IBM FileNet Connector for SharePoint Web Parts 2.2.1

Usability and Accessibility

Copyright IBM Corp. 2002, 2010

IBM FileNet P8 4.5 Release Notes Whats New

Support for separate database servers

Improved event log processing

New features for Process Designer

Copyright IBM Corp. 2002, 2010

New features for Process Configuration Console

New Content Extended Operations

Container-managed authentication and single sign-on

New Declassification Sweep utility

New report for entities due for an interim transfer

Improved language support

Copyright IBM Corp. 2002, 2010