IBM FileNet P8 Version 4.0. Release Notes GC

(1)

Version 4.0

Release Notes

(2)

(3)

Version 4.0

Release Notes

(4)

© Copyright IBM Corporation 2002, 2010.

(5)

Revision Log

Date Revision

03/23/10 • Adds or updates Known Issue Defects for the following:

o FileNet P8 Platform Installation, Uninstallation, and Upgrades: Content Engine: 839314

 Content Search Engine: 812561, 859049

 Content Federation Services- Image Services: 839934 Application Engine: 850322

o Content Engine: 790967, 811489, 848698, 853401, 862860 o Rendition Engine and Publishing: NA, regarding port numbers

o Process Engine: 756934 (update), 759926 (resolved), 776873, 800337, 891669 o Application Engine:

 Workplace: 859920

o Workplace XT: 754410 (update), 851710, 859920 o Content Federation Services- Image Services: o FileNet P8 Documentation:

 Help system and Search functionality: 859185

 FileNet P8 Platform Installation and Upgrade Guide: 796924, 847008, 853363 Content Engine: 795833

 Content Engine Java and .NET API Developer's Guide: 866148

10/29/09 • Adds a ‘What’s New in 4.0.1 Content Engine Java and .NET API’s entry regarding the PStore Tool.

• Adds or updates Known Issue Defects for the following:

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Content Engine: 796308  Process Engine: 796308 o Content Engine: 777300 o Application Engine:  Workplace:836178, 836180, 840306 o Workplace XT: 786696, 803128, 821302, 831263, 842255 o Content Engine Web Service: 835019

o FileNet P8 Documentation:

 FileNet P8 Platform Installation and Upgrade Guide: 830352  Process Engine Developer’s Guide: 824087

(10)

 Content Search Engine: 821891

06/30/09 • Adds a ‘What’s New in 4.0.1 Content Engine Java and .NET API’s entry regarding the PStore Tool.

• Adds ‘What’s New’ section for IBM FileNet Connector for SharePoint Web Parts 2.2.1 • Adds or updates Known Issue Defects for the following:

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Content Engine: 786223

o FileNet Services for Lotus Quickr: 791334 o Application Engine: 797169

o Workplace XT: 787160

o CFS: 786061 (update), 784526

o IBM FileNet Connector for SharePoint Document Libraries: 780096 795624, 795640

o IBM FileNet Connector for SharePoint Web Parts: 660127, 743774, 790893, 801999

o P8 eForms: 554176

o Content Engine Java and .NET APIs: 379982, 381685 (updates) o FileNet P8 Documentation:

 FileNet P8 Platform Installation and Upgrade Guide: 823017  SharePoint Document Libraries installation guide: 796846  Content Engine: 752140, 767829, 789095, 792974, 79482  Process Engine: 786585

 eForms Designer: 661829  P8 eForms: 662579

 Content Engine Java and .NET APIs: 777140, 781001, 792974, 802560 • Add’s updates to Resolved Known Issues sections per P8 Component fix pack 12/19/08 • Adds ‘What’s New in Application Engine 4.0.2’

• Adds ‘What’s New in FileNet Services for Lotus Quickr 1.0’

• Adds ‘What’s New in BPM 4.0.3’ entry for Process Engine available languages • Adds or updates Known Issue Defects for the following:

o FileNet Services for Lotus Quickr: 767882, 775463, 779920, 780139, 783889, 784386, 785114, 785318, 786243, 787126

o Workplace XT: 776213

o CFS: 757042, 760182 (updates)

o IBM FileNet Connector for SharePoint Web Parts: 776736 o Content Engine Java and .NET API: 557429

(11)

 FileNet Services for Lotus Quickr: 786086, 786249, 786377, 786729 09/12/08 • Adds ‘What’s New in Fix Pack P8CE-4.0.1-005’

• Replaces the term ‘3rd

Party’ with ISV (Integrated Software Vendor) throughout document

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Content Engine: 753074

 Application Engine: 759003

 Process Engine: 392213 (update), 771691 o Process Engine: 759926

o Workplace: 743673

o Workplace XT: 759915, 768303

o CFS: 757042, 757730, 758806, 759273, 760164, 760180, 760182, 760185, 760251

o Content Java API Compatibility Layer: 761869 o FileNet P8 Documentation:

 Content Engine Java and .NET API Developer’s Guide: 773292, 773603  Process Analyzer: 553395

 Process Designer: 773707

06/20/08 • Adds ‘What's New for IBM FileNet BPM 4.0.3’

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Process Engine: 749146

 Application Engine: 746340, 755598 o Process Engine: 756934

o IBM FileNet Connector for SharePoint Document Libraries: 759113, 759224, 759405

o Process Engine API: 216885 (update) o FileNet P8 Documentation:

 IBM FileNet Connector for SharePoint Document Libraries: 759390 06/06/08 • Adds ‘What’s New in Workplace XT 1.1.2.0’

• Adds ‘What's New for IBM FileNet Connectors for SharePoint 2.2’

• Adds ‘What’s New in 4.0.1 and PE 4.0.2’ Development Tools and documentation entries

(12)

• Adds Known Limitation for Content Engine

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Content Engine: 748176, 754869  Process Engine: 557305 o Content Engine: 753123 o Enterprise Manager: 743553 o Process Engine  eProcess to BPM Transition: 740259 o Application Engine: 753575 o Workplace XT: 556738, 754410, 757394 o CFS-CS and CFS-IICE: 554634, 758345 o WEBDAV: 748410 o Internationalization:

IBM FileNet Connector for SharePoint Document Libraries: 759234, 759257 IBM FileNet Connector for SharePoint Web Parts: 759224

o P8 eForms: 686524

o IBM FileNet Connector for SharePoint Document Libraries: 742751, 756744, 756745, 757291, 757601, 759107, 759111, 759120, 759171

o IBM FileNet Connector for SharePoint Web Parts: 759095, 759117, 759161, 759288,759558

o Content Java API Compatibility Layer 746321 o FileNet P8 Documentation:

 Help system and Search functionality: 390320, 661675, 758115  BAM: 748573

 Workplace XT: 757435, 758767  Process Designer: 758565 Process Engine: 757845

 IBM FileNet Connector for SharePoint Document Libraries: 758558 03/31/08 • Adds or updates Known Issue Defects for the following:

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Content Engine: 671263, 747785

 eForms: 743768, 747744 o Content Engine: 686537, 686538 o Process Engine: 741185, 742689

(13)

o BAM: 742262

o Workplace XT: 744427 o P8 eForms: 381897

 Workplace XT Installation and Upgrade Guide: 743624  SharePoint Web Parts installation guide: 741754  eForms: 661786, 661835

 P8 eForms: 662579

o FileNet P8 Platform Installation, Uninstallation, and Upgrades:  Application Engine: 557355, 746135

 Process Engine: 392213 o Process Engine: 556375

 eProcess to P8 Migration: 741198 o CFS-CS and CFS-IICE: 743417

o Content Engine Web Service: 660066

o Content Java API (Compatibility Layer): 746201 o FileNet P8 Documentation:

 P8 Platform Installation and Upgrade Guide: 744430, 746054  Content Engine/CFS: 745717

o FileNet P8 Platform Installation, Uninstallation, and Upgrades: Content Engine: 686320, 742074

o Application Engine:  Workplace: 741802

o Workplace XT: 741786, 741802, 743239

o CFS-CS and CFS-IICE: 664842, 686306, 742467, 742469

o IBM FileNet Connector for SharePoint Document Libraries: 740613 o IBM FileNet Connector for SharePoint Web Parts: 743774

o ISRA Integration: 744160 o FileNet P8 Documentation:

 P8 Help System and Search Functionality: 741752

(14)

• A number of Known Issues have been fixed and moved to the ‘Resolved’ section of their respective IBM FileNet P8 component

12/14/07 • Adds new WebSphere® 6.1 support items to the What’s New in 4.0.1 section under Content Engine 4.0.1 > WebSphere Application Server Version 6.1.x Support and under Process Engine 4.0.2 > WebSphere Business Modeler.

• Adds a What's New in 4.0.1 IBM FileNet Workplace XT 1.1.1.0 section

• Adds What’s New section for Content Federation Services for Content Services (CFS-CS) and Content Federation Services for IICE (CFS-IICE) 4.0

• Adds or updates Known Issue Defects for the following: o Application Engine:  Workplace: 742693 o Workplace XT: 661100, 740365, 740616, 741821, 742675 o CFS-CS and CFS-IICE: 174707, 358794, 364563, 379711, 382437, 386675, 389260, 555959, 555982, 686318, 686321, 740583, 740632, 740634, 740962,741355, 741481, 741926, 742312, 742348 o Process Engine: 686222, 686225

o IBM FileNet Connector for SharePoint Document Libraries: 740605, 740757, 741066, 742757

o IBM FileNet Connector for SharePoint Web Parts: 660127 o FileNet P8 Documentation:

 FileNet P8 Platform Installation and Upgrade Guide: ◊ Content Engine: 743864

11/26/07 • Adds new sections for: “Accessing IBM FileNet Documentation” and “Compatibility matrices and fix packs”.

• Adds Known Limitation for Application Engine • Adds Known Limitation for Documentation

• Adds or updates Known Issue Defects for the following: o Application Engine:

 Workplace XT: 740909, 686299  Workplace: 554707, 686299, o Process Engine: 379235

o Content Java and .NET APIs: 740397, 741057

o Content Engine COM API (Compatibility Layer): 144984 o FileNet P8 Documentation:

 FileNet P8 Platform Installation and Upgrade Guide: 217146, 554136 10/12/07 Adds What’s New in 4.0.1 section

(15)

o FileNet P8 Platform Installation, Uninstallation and Upgrades:  Content Engine: 210186, 213904, 214492, 215489, 215686, 216066, 216740, 217826  Application Engine: 209088, 214341, 215048, 215178, 217372, 217556  eForms: 211426 o Content Engine: 209327, 214114, 215442, 214504, 215645, 215658, 217124 o Rendition Engine and Publishing: 190525, 202015, 209390

o Enterprise Manager: 210547, 216315 o Process Engine: 155754, 194956, 205740, 213280, 214056, 214155, 214920, 215172, 215679, 215784, 215956, 216174, 217046 o Application Engine: Workplace: 205337, 209484, 210033, 211929, 212851, 213258, 217595 o WebDAV: 206640 o Internationalization: 215654 o P8 eForms: 202136, 204774, 210264, 211297, 212107 o Content Java and .NET APIs: 215423, 215491, 217018 o Content Java API Compatibility Layer 209179 (update) o Process Engine API: 216885

 P8 Help System and Search Functionality: 205176, 207806, 209918, 212107, 212383, 214483, 216821, 216968, 218310

 FileNet P8 Platform Installation and Upgrade Guide: 212488, 218623  Content Engine: 209994, 213266, 217364

 eForms: 217938

 eForms for Desktop: 202232, 210806, 212107, 215558, 217949, 217951, 217956

 Process Engine API: 214051

06/29/07 Adds entries for the Content Engine (Java API Compatibility Layer) to the What’s New in 4.0.0 Fix Pack-001 section

Adds a Known Limitations section

Adds or updates Known Issue DTS for the following:

o FileNet P8 Platform Installation, Uninstallation and Upgrades:

Content Engine: 188458, 192224, 192796, 197205, 197969, 199007, 200504, 201759, 202596, 205094, 207406, 207227, 207752, 210004

Rendition Engine: 185395 Process Engine: 202092, 203074 Miscellaneous: 198630

(16)

o Content Engine: 208347

o Content Search Engine: 201429, 204109 o Process Engine: 210104 o Application Engine: 211155 Workplace XT:, 200529, 206440, 207634, 207892, 207923, 207968, 207981, 208438, 209122, 209152, 209295, 209531, 209638, 209714, 210990, 211037, 211039, 211135 o WebDAV: 202370 o Internationalization: 206336

o Content Java and .NET APIs: 200666

o Content Java API Compatibility Layer: 209179 o FileNet P8 Documentation:

P8 Help System and Search Functionality: 209177, 208827

FileNet P8 Platform Installation and Upgrade Guide: 210954, 211371 Content Engine: 193433

Application Engine: 211470

Workplace XT: 211149, 211489, 211494, 211543 Content Java and .NET API: 209335, 210243 03/2907 Adds a What’s New in 4.0.1 section

Adds entries for the Content Engine to the What’s New in 4.0.0 Fix Pack-001 section Adds or updates Known Issue DTS for the following:

o FileNet P8 Platform Installation, Uninstallation and Upgrades:

Content Engine: 181785, 199481, 197989, 200504, 201759, 201295, 202094 Rendition Engine: 199022 Process Engine: 199696, 202092 o Content Engine: 199801, 199007 o Rendition Engine: 149295, 188161 o Enterprise Manager: 200489 o Application Engine: Workplace: 198093, 200665, 201430 o WebDAV: 170737, 177522

o Internationalization – new section o P8 eForms: 198738, 202716, 202849 o Desktop eForms: 200985

o Content Engine Java and .NET API: 173759 (expansion), 200011, 202142 o FileNet P8 Documentation:

(17)

201945, 203070, 201582, 203177

Content Engine: 197969, 201726, 201847, 202148, 202249 Process Engine: 200848

(18)

(19)

Introduction

This document contains release notes for IBM® FileNet® P8 4.0.0 and contains the following major topics:

• What’s New in IBM FileNet Connector for SharePoint Web Parts 2.2.1 - Describes the new features in this release.

• What’s New in Application Engine 4.0.2 - Describes the new features in this release.

• What’s New in FileNet Services for Lotus® Quickr™ 1.0 - Describes the new features in this release.

• What’s New in Fix Pack P8CE-4.0.1-005 – Describes the new features in this release. • What’s New in BPM 4.0.3 – Describes the new features in this release.

• What’s New in Workplace XT 1.1.2.0 – Describes the new features in this release.

• What's New for IBM FileNet Connectors for SharePoint 2.2 – Describes the new features in this release.

• What’s New in 4.0.1 and Process Engine 4.0.2 Describes the new features in this release. • What’s New in 4.0.0 – Describes the new features in this release.

• Known Issues – Describes known product and documentation issues.

• Resolved Known Issues – The Known Issues table describes defects that have been fixed.

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 [email protected]. 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). 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).

(20)

Documentation Updates

Release of FileNet Content Manager 4.0.1, FileNet Business Process Manager 4.0.2, and FileNet P8 eForms 4.0.1 Service Packs required updates of the associated documentation. These updates included important changes to the installation and upgrade instructions for FileNet P8 Platform. To download and install this updated documentation, see the following locations:

FileNet P8 Platform Documentation or FileNet P8 Platform Documentation.war for WebSphere at

www.ibm.com/software/data/support > FileNet Business Process Manager or FileNet Content Manager > Product documentation > FileNet P8 Platform.

FileNet P8 eForms Documentation at www.ibm.com/software/data/support > Support & downloads > Documentation > Information Management > FileNet Business Process Manager or FileNet Content Manager > Product documentation > FileNet eForms.

(21)

What’s New in Application Engine 4.0.2

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

Arabic AR Japanese JA

Bulgarian BG Korean KO

Catalan CA Polish PL

Chinese

(Simplified) zh-CN Portuguese (Iberian) PT

Chinese (Traditional) zh-TW Portuguese (Brazilian) pt-BR Croatian HR Romanian RO Czech CS Russian RU Dutch NL Swedish SV Finnish FI Slovak SK

(22)

French FR Spanish ES

German DE Thai TH

Italian IT

Note Separate media are available for each language’s Application Integration and File Tracker installation programs.

FileNet Services for Lotus Quickr 1.0

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 non-English languages:

Language Locale Language Locale

Chinese (Simplified) zh-CN Japanese JA

Chinese (Traditional) zh-TW Korean KO

French FR Portuguese (Brazilian) pt-BR

German DE Spanish ES

Italian IT

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

Arabic AR Korean KO

Catalan CA Norwegian NO

Chinese (Simplified) zh-CN Polish PO

Chinese (Traditional) zh-TW Portuguese PT

Czech CS Portuguese (Brazilian) pt-BR

Danish DA Romanian RO Dutch NL Russian RU Finnish FI Slovak SK French FR Slovenian SL German DE Spanish ES Greek EL Swedish SV Hungarian HU Thai TH Italian IT Turkish TR Japanese JA Ukrainian UK

(23)

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.

What’s New in Fix Pack P8CE-4.0.1-005

Content Engine Java and .NET APIs

Security and authentication

• When using the Microsoft Windows Active Directory service, either the Content Engine Directory Service User account or the #AUTHENTICATED-USERS group must be added as a member of the Pre-Windows 2000 Compatible Access group in each domain configured in FileNet Enterprise Manager. Failure to do so can result in functional errors in security.

Note In releases prior to fix pack P8CE-4.0.1-005, adding the Content Engine Directory Service User account to the group was technically optional, although it is stated as required in the documentation. It is imperative to perform this task prior to upgrading to fix pack level P8CE-4.0.1-005. Failure to do so before an upgrade can lead to missing security functionality, such as users’ loss of security permissions that were configured prior to the upgrade.

(24)

What’s New in BPM 4.0.3

Enable Region for Recovery

To enable recovery of all the data for one isolated region independent of other isolated regions in the system, you can use the Enable Region for Recovery feature in Process Task Manager. The feature separates the global Process Engine data for the region into the region-specific database tablespaces, makingit possible to back up all the data for one isolated region, to roll back only this region, and to roll forward without stopping Process Engine or rolling back all of the isolated regions.

2038 time/date feature

The documentation for Process Configuration Console includes instructions for using dates beyond January 2038.

Improved language support

BPM now installs translated resource files to provide a localized UI without the need for installation of Language Packs.

Process Engine Client Updater

The Process Engine Client Updater now runs on the Process Analyzer and Process Engine and is the mechanism for installing updated Process Engine client files on those components.

Process Engine 4.0.3

Available languages

Releases prior to P8 Process Engine 4.0.3 required language packs to provide a translated user

interface. IBM FileNet Process Engine 4.0.3 does not require language packs and in addition to English, provides the Workplace user interface in the following languages:

Language Locale Language Locale

Arabic AR Japanese JA

Bulgarian BG Korean KO

Catalan CA Polish PL

Chinese (Simplified) zh-CN Portuguese (Iberian) PT

Chinese (Traditional) zh-TW Portuguese (Brazilian) pt-BR

Croatian HR Romanian RO Czech CS Russian RU Dutch NL Swedish SV Finnish FI Slovak SK French FR Spanish ES German DE Thai TH Italian IT

Note The Process Engine 4.0.3 Client files also provides translated user interface for the above list of languages.

(25)

What’s New in Workplace XT 1.1.2.0

New Features

Customizable user interface

You can now customize the appearance of Workplace XT, by changing the images and colors of the application's banner and menu bar. Workplace XT provides a properties file where you can modify the appearance properties and a script file that generates a new style sheet with your changes.

Microsoft® Outlook mapping

You can now map Outlook message properties to corresponding Email class properties using the OutlookPropertyMappings.xml file. Once Outlook properties are mapped to the Email class properties, you can assign those properties to each Outlook message that is added to an object store.

Lotus Forms Support

You can now use Lotus Forms 3.0.1, in addition to FileNet P8 eForms, for workflows. Export list

You can now export items from a list view to a comma-separated delimited file, which can be imported into another application, such as Microsoft® Excel.

Improved Workflow Policy wizard page settings

You can control the visibility, accessibility, and printability of form template pages by using settings available in the Workflow Policy Wizard. A selected page can also be designated as the form's start page. Improved user interfaces

The Add Document and Check In wizards are now redesigned to make the processes easier and faster. The properties page and folder and class selection have been improved. Site preferences control whether the older wizards and pages remain accessible for sites that require specialized processing.

Improved language support

Workplace XT now installs translated resource files to provide localized UI without the need for Language Packs to be installed. Chinese (Simplified) zh-CN Chinese (Traditional) zh-TW Dutch nl French fr German de Italian it Japanese ja Korean ko Portuguese (Brazilian) pt-BR Spanish es

Saved advanced searches

Users can now save frequently used search criteria as saved searches in the new 'My searches' folder on the search page.

(26)

Default starting class for an object store

The administrator can now set the default class for an object store. With this default set, users can add new documents without having to navigate the full tree to find the class they need.

Continued accessibility improvements

All new user interfaces and installers pass the accessibility checklist requirements. Increased performance and scalability

Application performance and scalability have improved.

Documentation

Installation and Upgrade Guide

The IBM FileNet P8 Platform Installation and Upgrade Guide includes the following new information: • A topic for installing Process Engine Client files on the Workplace XT server

• Upgrade information for Workplace XT installations on JBoss • An "Accessibility Considerations" topic for the install process • An "Available Languages" topic

Workplace XT administrative help

Workplace XT administrative help is now located in the FileNet P8 Administration section of the online documentation. Topics unique to Workplace XT have been consolidated in a Workplace XT

(27)

What's New for IBM FileNet Connectors for SharePoint

2.2

ITLM enablement

IBM FileNet SharePoint Connectors support IBM Tivoli License Management (ITLM). FDCC compliance

IBM FileNet SharePoint Connectors meet the requirements set forth in the Federal Desktop Core Configuration mandate.

IBM FileNet Connector for SharePoint Web Parts

Stored searches

Users can now display the results of a stored search using the Browse web part. Public inboxes

Users can process work in public work queues using the Public Inbox web part. Column sorting and filtering

Users can sort and filter columns in the IBM FileNet web parts in the same way they can sort and filter with out-of-the-box SharePoint web parts.

Workflow launching

Users can launch a workflow from the list of subscriptions associated with a document or folder class. Single sign-on support

Using Kerberos, users can log on to the SharePoint server using their Windows username and have access to the FileNet P8 system without logging on again.

Improved language support

Releases prior to IBM FileNet Connector for SharePoint Web Parts 2.2 required Language Packs to provide translated user interface. The IBM FileNet Connector for SharePoint Web Parts 2.2 release does not require Language Packs and, in addition to English, provides the user interface in the following languages: Chinese (Simplified) zh-CN Chinese (Traditional) zh-TW Dutch nl French fr German de Italian it Japanese ja Korean ko Portuguese (Brazilian) pt-BR Spanish es

(28)

IBM FileNet Connector for SharePoint Document Libraries

Remote deployments

You can install and run the Document Library application and processing on a server separate from the SharePoint server.

Server configuration migration

You can export the Configuration Manager Data Store configurations from a staging environment into a production environment. This eliminates the need to manually re-create data store configurations during an export.

Centralized management for multiple SharePoint servers

You can use a single or remote Document Library server to process multiple SharePoint server implementations.

Oracle and DB2 support for configuration database

The Configuration Manager data store database can reside on Oracle and DB2 in addition to the existing support for Microsoft SQL.

Document version support

Users can now specify SharePoint document versions that need to be processed using the Get Versions task in a task route.

Post-Processing task option

The new move and link Post-Processing option in a task route moves SharePoint documents to an IBM FileNet P8 object store, and then deletes them from the SharePoint server. Documents can still be accessed from a SharePoint site through links to each document.

Configuration file customization to fine-tune performance settings

The Connector Services allows customization of your configuration using the web.config file. This file is used for optimizing the tasks that need to be performed. It is also used to create the links that appear on a SharePoint server after selecting the new move and link Post-Processing option in a task route. Records Management support

SharePoint documents moved to an IBM FileNet P8 object store can now be processed by Records Manager.

IBM FileNet Connectors for SharePoint Documentation

Improved documentation

The documentation for the IBM FileNet Connectors for SharePoint has been rewritten using a task-based approach.

(29)

What’s New in 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

• IBM FileNet Connector for SharePoint Web Parts 2 2.1 supports IPv6.

• 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. • Users can configure and save custom and filtered views in the Inbox web parts.

• 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 Locale Language Locale

Chinese (Simplified) zh-CN Japanese JA

Chinese (Traditional) zh-TW Korean KO

French FR Portuguese (Brazilian) pt-BR

German DE Spanish ES

(30)

What’s New in P8 4.0.1 and Process Engine 4.0.2

This section describes the new features of the components of the 4.0.1 release: Content Engine 4.0.1, Process Engine 4.0.2, Application Engine 4.0.1, eForms 4.0.1, Rendition Engine 4.0.1, IBM FileNet Workplace XT 1.1.1.0, and Documentation.

Content Engine 4.0.1

Security

Improved security inheritance model

The security inheritance implementation has been significantly improved. Previously, inheritable security settings (access control entries or ACEs) were physically propagated from security parent to child. With this release, the security model has been changed to one in which these settings are dynamically computed.

This dynamic computation occurs whenever an access check is performed on the security child object or when the Permissions collection (Access Control List or ACL) associated with the security child object is retrieved. Instead of persisting inherited ACEs in the child object’s ACL (as was done by the previous security inheritance model), the ACEs to be inherited are now calculated dynamically from the inheritable ACEs on the security parent. Additionally, you can extend the security inheritance model (using custom object-valued properties) to inherit from multiple security parents: access rights are now inheritable from documents, custom objects, and folders in different, customizable combinations. Consequently, and perhaps most importantly, all of this now enables you to assign security relationships that reflect the relationships inherent in your application object model.

It is important to note that this change to the security inheritance model affects the ordering of entries within Permissions collections, and how an Update Security Event is handled. Both of these impacts are described below.

Permissions Ordering

The order of a permissions list (Access Control List, or ACL) is changed. ACEs are now listed in Enterprise Manager in order of precedence:

1. Default/Direct allow 2. Default/Direct deny 3. Template allow 4. Template deny 5. Parent allow 6. Parent deny

ACE's are applied from the bottom up, so that that the most important entries, which are at the top of the list, are processed last. This means that entries lower in the list would be changed by entries higher in the list. Remember that within each type, Default/Direct, Template, and Parent (also called Inherited), deny always trumps allow. For more information about permissions ordering, see the following online help topic: FileNet P8 Administration > Enterprise-wide Administration > FileNet P8 Security > Authorization > Access Rights > Allow/Deny and order of evaluation.

Events

If an object is subscribed to the “Update Security Event” and the security for an object changes, the system generates an UpdateSecurityEvent. Prior to dynamic inheritance, modifying the security of a folder could also modify the security of the documents contained in that folder. The applicable Access

(31)

Control Entry (ACE) would be physically copied from the folder to the document. Because this actually modified the document security, an UpdateSecurityEvent was generated for each document. With dynamic inheritance, physical copying of ACEs no longer occurs. Thus, the system no longer generates the UpdateSecurityEvent for each impacted object. Given the example, only a single

UpdateSecurityEvent is generated for the security modification performed on the folder.

For information about the changes to the security model, see the following online help topic: FileNet P8 Administration > Enterprise-wide Administration > FileNet P8 Security > Authorization > Understanding inheritance. This topic includes a link to information on configuring security inheritance.

Support for ADAM directory service provider

• Content Engine now supports Microsoft® Windows® Active Directory Application Mode (ADAM) for providing directory services. You can find more information about ADAM (and other supported directory service providers) in the following online help topic: FileNet P8 Administration > Enterprise-wide Administration > FileNet P8 Security > Directory service providers > Windows Active Directory Application Mode (ADAM). For configuration information, see the following IBM FileNet P8 Platform Installation and Upgrade Guide topic: Configure Active Directory Application Mode (ADAM).

• A new ADAM Directory Configuration Type has been added to the Enterprise Manager’s Directory Configuration Wizard.

• The Content Engine .NET and Java™ APIs have been updated to include the classes, interfaces, and properties related to ADAM support. For details, see CE Java and .NET APIs.

Content-based Retrieval (CBR) indexing enhancements

A new TempDirectoryPath property has been added to the VerityIndexArea object. In previous releases, the Autonomy indexes could be stored remotely from the Verity server. This was found to reduce indexing performance. Therefore, Autonomy indexes must be stored locally to the Verity server. The previously existing RootDirectoryPath property should always be a local path on the Autonomy server (the path should not be a UNC path). The new TempDirectoryPath property specifies a shared directory used by both Verity and Content Engine 4.0.1. The shared directory is where data is shared between the two engines. This path can be remote to either server application.

WebSphere Application Server Version 6.1.x support

IBM FileNet P8 Content Engine now supports IBM WebSphere® Application Server Version 6.1. This support requires the installation of the Content Engine Interim Fix P8CE-4.0.1-000.001, as well as the WebSphere APAR PK54565 (

http://www- ibm.com/support/docview.wss?rs=0&q1=PK54565&uid=swg1PK54565&loc=en_US&cs=utf-8&cc=us&lang=all).

For installation and configuration information, see the IBM FileNet P8 Installation and Upgrade Guide on the IBM support site. Refer to the following topics: Configure an Application Server for Content Engine (WebSphere) and Configure Content Engine Application Server Database Connectivity (WebSphere 6.1.x).

Content Engine also supports the federated user repository feature of WebSphere 6.1.x, which provides multiple authentication realms. For information, see the IBM FileNet P8 Installation and Upgrade Guide topic Configure an Application Server for Content Engine (WebSphere) > To use WebSphere 6.1 federated user repository.

Platform support

• Support for JBoss 4.0.5 application server

Installation and configuration of JBoss for Content Engine is documented in the IBM FileNet P8 Platform Installation and Upgrade Guide.

(32)

Backward Compatibility Note: If you want to run a Content Java API 3.5.1 application in the JBoss 4.0.5 environment, and if that application executes batch operations in a transaction, then you must set JBoss JNP-related properties in the Java Virtual Machine. For details, see the description of the startBatch method on the Session interface in the Javadoc™ comments of the Content Java API Compatibility Layer online help. (Note that this online help is available using the FileNet P8 4.0.x Compatibility Layers for Content Engine APIs Help zip file.) The information is also included below.

To execute a batch as a transaction in the JBoss environment, you must set the following Java VM arguments:

-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces -Djava.naming.provider.url=jnp://<host name>:<port>

Do not set the above properties using the TxJndiProperties option in the

WcmApiConfig.properties configuration file. Doing so can result in “Could not begin transaction” or “Could not instantiate class” exceptions.

• Support for DB2® 9.x database platform.

• Support for multiple instances of Content Engine deployed on the same application server.

Installation and configuration information is documented in the following topic in the IBM FileNet P8 Platform Installation and Upgrade Guide: Deploy Multiple Content Engine Instances.

Installation and Upgrade

• Additional Content Engine components can be installed from the baseline installation software package after Content Engine fix packs and interim fixes have been applied. For more information, see the following topics in the IBM FileNet P8 Platform Installation and Upgrade Guide:

o Install Enterprise Manager o Install and Deploy Content Engine

• Upgrades of Content Engine to version 4.0.1 are supported directly from 3.5.2 as well as from 4.0.0. For more information, see the following topic in the IBM FileNet P8 Platform Installation and Upgrade Guide: Upgrade Content Engine Data.

• When using the Microsoft Windows Active Directory service, either the Content Engine Directory Service User account or the #AUTHENTICATED-USERS group must be added as a member of the Pre-Windows 2000 Compatible Access group in each domain configured in FileNet Enterprise Manager. Failure to do so can result in functional errors in security.

Note In releases prior to fix pack P8CE-4.0.1-005, adding the Content Engine Directory Service User account to the group was technically optional, although it is stated as required in the documentation. It is imperative to perform this task prior to upgrading to fix pack level P8CE-4.0.1-005. Failure to do so before an upgrade can lead to missing security functionality, such as users’ loss of security permissions that were configured prior to the upgrade

Enterprise Manager

In addition to the Enterprise Manager enhancements mentioned earlier in this document, Enterprise Manager includes the following improvements:

• The Test Connection button has been removed from the Fixed Content Device Properties General tab. The functionality provided by this button is available through the Apply button.

(33)

• Enterprise Manager’s list of configurable fixed content devices now includes “Federated Device (IBM WebSphere® IICE)”. This new device option has been added to support Content Federation Services for IICE (CFS-IICE).

• The context menu for the Virtual Server and Server Instance nodes now contains a Delete command. From the Sites node, right-click the Virtual Server or Server Instance node and then select Delete from the context menu. You can also delete a node by using the Actions menu or by selecting the node and clicking on the Delete icon in the tool bar.

• When mapping Image Services (IS) dates in the property mapping dialog, Enterprise Manager now displays both Content Engine DateTime and String properties when an IS date is selected, allowing the user to map an IS date to either a Content Engine DateTime or String value. For a String value, the CFS-IS Import Agent formats the date to “yyyy-mm-dd”, which conforms to the Internet date standard and ISO8601. For mapping information, see the following online help topic: FileNet P8 Administration > Content Engine Administration > Content Storage > Fixed storage areas > How To … > Map IS properties > Add/Edit Image Services Property Mapping dialog box.

Development Tools

Workplace Application Integration Toolkit

Deprecations

The Java transport and upload servlets in the Application Integration Toolkit have been deprecated. For new development, use the Content Engine Java API, the Content Engine .NET API, or the Content Engine Web Service (CEWS) instead.

Process Engine Java API

VWSchema class

A new getFileName() method has been added to the VWSchema class. This method returns the name of the file used in the design-time schema. For run-time schemas, the return value is non-null only if the design-time schema contained the name of a schema file instead of a schema. At run-time, the Process Engine server expands the schema to the contents of the file; however, some run-time applications will need to know the name of the file. For more information, see the Process Java API reference help for the VWSchema class (Developer Help > Process Engine Development > Process Java API Reference). VWSystemConfiguration.commit

Depending on your application and the calls you are making, you might need to adjust the client timeout value in your Java initiation statement before calling this method. For example, under Sun Solaris or using the Sun JVM, you might need to adjust the timeout value in the Java initiation statement as follows: -Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=100:15000:300:5

For more information, refer to the description of VWSystemConfiguration.commit in the Process Java API reference help (IBM FileNet P8 Documentation > Developer Help > Process Engine Development > Process Java API Reference).

Date/Time Support

o A new VWFieldType attribute, FIELD_TYPEDEF_TIME64, has been created to support date/time values beyond the year 2038. This attribute is based on a 64-bit representation, and should be used for the creation of all date/time values.

o The VWFieldType date/time attribute, FIELD_TYPE_TIME, continues to be supported, but does not allow for the creation of date/time values beyond the year 2038.

(34)

o The VWFieldType date/time attribute, FIELD_TYPEDEF_TIME32, has been deprecated. This attribute does not allow date/time values beyond the year 2038.

Pay particular attention to the date/time support changes when using the following methods: VWQueue.createQuery, VWRoster.createQuery, and VWLog.startQuery

The date/time columns in the database can be exposed as either 32-bit (can only support dates earlier than 2038) or 64-bit (can support dates beyond 2038). If a user has a filter on a 32-bit time field, the value bound to the bind variable in the query using that filter must be a value that can fit in 32 bits: otherwise the query will not return the expected result.

VWDataField.getStringValue

Returned date/time values are formatted as defined in VWFieldType.TIME_MASK. Prior releases used a long format (for example, “Sun Apr 17 04:00:00 PST 1977”). If you want to continue returning date/time values in a long format, you can use code similar to the following:

if (vwDataField.getType == VWFieldType.FIELD_TYPEDEF_TIME32 || vwDataField.getType == VWFieldType.FIELD_TYPEDEF_TIME64)

{

Object fieldValue = vwDataField.getValue(); //java.util.Date if (fieldValue != null)

{

if (vwDataField.isArray())

stringValue = fieldValue.toString(); //long format else

{

stringValue = "{";

for (int nIndex = 0; nIndex < vwDataField.length; nIndex++) { stringValue += "\"" + fieldValue.toString() + "\""; } stringValue += "}"; } } }

For more information, refer to the relevant class members in the Process Java API reference help (IBM FileNet P8 Documentation > Developer Help > Process Engine Development > Process Java API Reference).

Deprecations

The following class and methods have been deprecated as of this release: • VWStatistics

• VWQueue.fetchStatistics • VWRoster.fetchStatistics

Process Engine Web Services

New operations have been added to Process Engine Web Services. The following operations were added to provide WSI compliancy:

(35)

• getRosterNamesWrapped • getWorkClassNamesWrapped

The following operations were added to support heterogeneous objects (an array of Values) for substitution variables:

• getQueueElementsEx • getRosterElementEx

• getStepElementsFromRosterEx • getStepElementsFromQueueEx

For more information, refer to the Process Engine Web Services Reference documentation (IBM FileNet P8 Documentation > Developer Help > Process Engine Development > Developer’s Guide > Web Services > Reference).

Content Engine Java and .NET APIs

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

• References to the PermissionSource.MARKING and PermissionSource.MARKING_AS_INT constants, which were deprecated in the 4.0.1 release, are now removed from the

PermissionSource property description in the online reference help.

• A new constant, ConfigurationParameter.EJB_CONTEXT_PROPERTIES is added to the Java API. This new constant provides the ability to configure the Java Naming and Directory Interface (JNDI) service environment for InitialContext. The new constant is used for EJB-related lookups

(36)

and application server type detection in a multi-JNDI directory environment. You can use the constant to override the default environment for the java.naming.InitialContext that is used to locate the internal EJB used by the Java API EJB transport. You can supply different properties for every InitialContext instance. For usage information, see the description of

api.constants.ConfigurationParameter.EJB_CONTEXT_PROPERTIES in the Java reference help (IBM FileNet P8 Documentation > Developer Help > Content Engine Development > Java API Reference).

• New code samples illustrating the use of the Content Engine Java™ and .NET APIs are posted to the Product Documentation for FileNet P8 Platform web page (

http://www-1.ibm.com/support/docview.wss?rs=3273&uid=swg27010422). You can download the samples from the “FileNet P8 Platform Developer Samples” table. Both Java and C# versions are available for each of the following samples:

o Demo – demonstrates the following operations: Configuring the server

Creating a document Getting a document Creating a folder

Creating a custom object Getting a custom object

Creating a compound document Getting a compound document Creating an ad-hoc query

o Folder Browser – demonstrates the following operations: Configuring the server

Retrieving the contents of a folder

o Bulk Loader – demonstrates the following operations: Configuring the server

Bulk document ingestion

Documentation

Content Engine API Documentation

The IBM FileNet P8 Content Engine Java and .NET API Developer’s Guide now contains the following new sections: o Object Stores o Choice Lists o Documents o Versioning o Custom Objects

These new sections provide both conceptual information and code examples. For more information, see the guide (IBM FileNet P8 Documentation > Developer Help > Content Engine Development > Java and .NET Developer's Guide).

(37)

New interfaces

• New classes, interfaces, and properties have been added to support Content Federation Services for IICE (CFS-IICE) as a fixed content device. See the reference help for the IICEFixedContentDevice interface (Java) and IIICEFixedContentDevice interface (C#).

Note Although this version of Content Engine provides this support, you cannot use these APIs until the next release of Content Federation Services for IICE (CFS-IICE) becomes available. • New interfaces and properties have been added to support the version series federation model. See

the reference help for the CFSImportAgentConfiguration interface (Java) and ICFSImportAgentConfiguration interface (C#).

Security and authentication

• The Versionable interface has a new SecurityFolder property to identify a folder from which the object inherits security. (Both the Document and CustomObject classes implement Versionable.) This property supports the new dynamic security inheritance model introduced in this release, and is used in conjunction with the new SecurityProxyType.INHERITANCE setting and the

Permission.InheritableDepth property. The effective permissions of a given object will be computed dynamically, based on a combination of the object’s access control entries, the inheritable access control entries of the parent object, and the inheritable depth specified for the parent object.

Backward Compatibility Note: The SecurityParent property on the Document and

CustomObject classes has been deprecated. If the SecurityParent property is set (by an existing application, for example), the SecurityFolder property is assigned the value of the SecurityParent property. When upgrading to this release, note the following:

o Objects with the SecurityParent property set use the tail (Folder) of the SecurityParent ReferentialContainmentRelationship object to set the SecurityFolder property to the SecurityParent value. Any access control entries in the object that were persisted in the object’s ACL with a source type of PARENT are removed.

o Objects having superseded versions that do not have a SecurityParent property set will have a SecurityFolder property set to the SecurityParent property value for the version that had a security parent.

• The SecurityProxyType constant class has a new INHERITANCE setting to indicate that the security is inherited from a parent object.

By assigning SecurityProxyType.INHERITANCE values to more than one object-valued property on a given object, you can specify multiple security parents for an object. The resulting security descriptor for the object is calculated dynamically by merging the inheritable access control entries of the different security parents with the child object’s persisted access control entries. For more information, see Developer Help > Content Engine Development > Java and .NET

Developer’s Guide > Security Concepts > Security Inheritance.

• In support of the new Microsoft Active Directory Application Mode (ADAM) directory service provider, two new classes are available: DirectoryConfigurationAdam and DirectionConfigurationAdamList. In addition, the following properties have been updated for this support: GroupMembershipSearchFilter, GroupSearchFilter, UserSearchFilter. For more information, see class and property descriptions in the Java API reference help and the .NET API reference help.

Properties

• A new attribute, pageSize, has been added to property filters and filter elements. This new attribute allows you to specify the iterator page size for independent object sets returned by

PropertyIndependentObjectSet properties. In connection with this change, the following changes have been made to the PropertyFilter class:

(38)

o A new addIncludeProperty method has been added that requires an additional

parameter, pageSize. The existing addIncludeProperty method that it replaces has been deprecated. The existing addIncludeProperty method that requires a FilterElement object remains unchanged.

o A new addIncludeType method has been added that requires an additional parameter, pageSize. The existing addIncludeType method that it replaces has been deprecated. The existing addIncludeType method that requires a FilterElement object remains unchanged.

• The following changes have been made to the FilterElement class:

o Two new FilterElement constructors have been added that require an additional

parameter, pageSize. The two existing FilterElement constructors that they replace have been deprecated.

o A new method, getPageSize, as been added.

• A new property, TempDirectoryPath, has been added to the AutonomyIndexArea interface in support of content-based-retrieval (CBR) indexing enhancements. This new property specifies a remote path to the directory to be used for storing temporary indexing files. For more information, see the property description in the Java API reference help and the .NET API reference help.

Process Engine 4.0.2

WebSphere Business Monitor Integration

You can use the IBM WebSphere Business Monitor to monitor active IBM FileNet Business Process Manager (BPM) processes and monitor the processes on a WebSphere Process Server. BPM software includes a CBE Adaptor, a basic BPM Monitor Model, and some basic dashboard views that you can configure and deploy to the WebSphere Application server and WebSphere Business Monitor server. For more information, see the following online help topic: FileNet P8 Administration > Process Engine

Administration > Workflow Administration tasks > Analyze workflows > WebSphere Business Monitor integration.

WebSphere Business Modeler Integration

Customers can model a business process using WebSphere Business Modeler (WBI Modeler), export the model to an XPDL 2.0 file, and open the model in Process Designer.

IBM FileNet P8 BPM supports opening XPDL files exported from WBI Modeler:

• Schema files can contain external references—import, include, and redefine. The external references must be relative to the schema file location on the Process Engine server. There is no change in the interface in Process Designer. For details, see the online help in the Workplace > Advanced Author Tools > Process Designer > Workflow Properties > Web Services > XML Schema topic.

• XML data fields can be arrays. In Process Designer, the Workflow Properties > Web Services > XML Data Fields dialog box has a new Array option for each field, and you can specify values for each element in the new Edit Array Fields dialog box. For information, see the online help in the Workplace > Advanced Author Tools > Process Designer > Workflow Properties > Web Services > XML Data fields topic.

• Imported models can reference an “Interface-only” WSDL definition. Although Process Designer can open models that reference a WSDL file that does not define a SOAP binding, the binding information must be complete before the workflow definition can be transferred.

WebSphere Services Registry and Repository (WSRR) Integration

To improve integration between FileNet P8 BPM and WebSphere Process Server technology, Process Configuration Console and Process Designer support interfaces with WSRR.

(39)

• Process Configuration Console supports publishing processes in WSRR and discovering Web Services from these registries. For details, see the following online help topic: Workplace > Admin Tools > Process Configuration Console > Isolated regions > View or modify isolated region properties > Web Services – WSRR registries.

• Process Designer supports browsing WSRR, creating a partner link, and invoking steps based on both design-time WSDL and runtime WSDL. See the following online help topic: Workplace > Advanced Author Tools > Process Designer > Workflow Properties > Web Services > Partner Link.

Platform Support

• Support for JBoss 4.0.5 application server. Installation and configuration of JBoss for Process Engine is documented in the IBM FileNet P8 Platform Installation and Upgrade Guide.

• Support for DB2 9.x database platform.

Process Designer 4.0.2

• Workflow validation now checks Web Services Partner Links for invoke steps to ensure a valid SOAP binding in the WSDL.

Previous versions allowed a workflow to be transferred with an incomplete partner link for an invoke step, even though that workflow could not run successfully. Some workflow authors used this behavior as a shortcut in creating workflows that invoke each other. To continue to use the previous behavior, you can set User Preferences to not validate on Transfer of the workflow. For a procedure that creates workflows that invoke each other, see the following online help topic: Workplace > Advanced Author Tools > Process Designer > Steps > System Steps > Web

Services system functions > Using Web Services in FileNet workflows > Correlation set example. • You can now model a bu

IBM FileNet P8 Version 4.0. Release Notes GC

Version 4.0

© Copyright IBM Corporation 2002, 2010.

Contents

Revision Log

Date Revision

 IBM FileNet Connector for SharePoint Document Libraries: 759234, 759257  IBM FileNet Connector for SharePoint Web Parts: 759224

Introduction

• What’s New in IBM FileNet Connector for SharePoint Web Parts 2.2.1 - Describes the new features in this release.

• What's New for IBM FileNet Connectors for SharePoint 2.2 – Describes the new features in this release.

Access IBM FileNet documentation, compatibility matrices,

Feedback

What’s New in Application Engine 4.0.2

New access role

Improved language support

Language Locale Language Locale

FileNet Services for Lotus Quickr 1.0

Language Locale Language Locale

Language Locale Language Locale

What’s New in Fix Pack P8CE-4.0.1-005

Security and authentication

What’s New in BPM 4.0.3

2038 time/date feature

Process Engine 4.0.3

Language Locale Language Locale

What’s New in Workplace XT 1.1.2.0

Customizable user interface

Improved Workflow Policy wizard page settings

Saved advanced searches

Documentation

Installation and Upgrade Guide

What's New for IBM FileNet Connectors for SharePoint

ITLM enablement

IBM FileNet Connector for SharePoint Web Parts

Stored searches

Improved language support

IBM FileNet Connector for SharePoint Document Libraries

Remote deployments

Oracle and DB2 support for configuration database

Configuration file customization to fine-tune performance settings

IBM FileNet Connectors for SharePoint Documentation

Improved documentation

What’s New in IBM FileNet Connector for SharePoint

Installation Improvements

Available languages

Language Locale Language Locale

What’s New in P8 4.0.1 and Process Engine 4.0.2

Improved security inheritance model

Events

Support for ADAM directory service provider

Content-based Retrieval (CBR) indexing enhancements

Platform support

Installation and Upgrade

Enterprise Manager

Development Tools

Deprecations

Process Engine Java API

VWSchema class

VWDataField.getStringValue

Deprecations

Process Engine Web Services

Content Engine Java and .NET APIs

Documentation

Content Engine API Documentation

Security and authentication

Properties

Process Engine 4.0.2

WebSphere Services Registry and Repository (WSRR) Integration

Process Designer 4.0.2

IBM FileNet Connector for SharePoint Document Libraries: 759234, 759257 IBM FileNet Connector for SharePoint Web Parts: 759224