IBM FileNet Workplace XT 1.1.5.2-WPXT-IF002 Interim Fix Readme
© Copyright IBM Corporation 2013.
All Rights Reserved.

About this fix

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Compatibility

Known issues

Localization

Installing a non-English version of Application Integration

New in this fix pack

Installation, migration, upgrade, and configuration

Requirements

Install this fix pack

Uninstall this fix pack

Product fix history

Contact customer support

Notices

Trademarks

About this fix

This document provides information about the IBM® FileNet® Workplace XT 1.1.5.2-WPXT-IF002 interim fix. 

The Workplace XT 1.1.5.2-WPXT-IF002 interim fix installs a new, complete Workplace XT 1.1.5.2 system, or upgrades an existing Workplace XT system. Workplace XT fixes are cumulative; each fix pack contains the base release and content from all previously released fix packs.

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Documentation and compatibility matrices

To access documentation and compatibility matrices for IBM FileNet products:

1.     Navigate to the Product Documentation for FileNet P8 Platform support page (www.ibm.com/support/docview.wss?rs=3247&uid=swg27010422).

2.     Select a PDF or a Doc Link, whichever is appropriate.

Fix packs

To access fix packs:

1.     You can navigate directly to the Workplace XT 1.1.5.x fixs or manually locate the fixes by doing one of the following:

·         Navigate to the Fix Central page for the Workplace XT 1.1.5.x fixes
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=FileNet+Product+Family&product=ibm/Information+Management/FileNet+Workplace+XT&release=1.1.5.*&platform=All&function=all

·         Manually locate the fix packs by specifying the product group, product, installed version, and platform with the following options:

o    Product Group: Enterprise Content Management

o    Select from Enterprise Content Management: FileNet Product Family

o    Select from FileNet Product Family: FileNet Workplace XT

o    Installed Version: 1.1.5.*

o    Platform: All

Click Continue and identify the fixes you want to locate or select Browse for fixes.

2.     View the list of available fixes.

Compatibility

NOTE: Recent updates were made to the Java trust and signing requirements. IBM recommends a minimum of JRE 1.7.0_45. Please see the Java JRE Compatibility Flash.

For compatibility information, see the:

·       IBM FileNet P8 Hardware and Software Requirements Guide

·       IBM FileNet P8 Fix Pack Dependency/Compatibility Matrix

·       Java JRE Compatibility Flash

Known Issues

The log4j.properties file

There is a behavior change between the 1.1.4 and 1.1.5 installer. The log4j.properties file is not being customized with a path for the log file write location. So, to enable logging, an additional step is required:

·       After renaming _log4j.properties to log4j.properties, edit the file to add the path where you want the log files to be written. Change each occurrence of {LOG_FILE_DIR} to a suitable path.

For example, change "log4j.appender.CommonLogCBEFormat.File={LOG_FILE_DIR}WorkplaceXT_IBMcommon_CBE.log" to "log4j.appender.CommonLogCBEFormat.File=/opt/IBM/FileNet/WebClient/LogFiles/WorkplaceXT_IBMcommon_CBE.log". Then, restart the application.

For information about this known issue, see the section about enabling and disabling logging at http://publib.boulder.ibm.com/infocenter/p8docs/v5r1m0/index.jsp?topic=/com.ibm.p8.xt.user.doc/ae_help/ae_admin/wpxt_logging.htm.

For more information on all other known issues, go to http://www-01.ibm.com/support/search.wss?&tc=SSNVNV&atrn1=SWVersion&atrv1=5.1.0&rankprofile=8&dc=DA440&dtm and select Workplace XT as the Product Category.

Localization

Available languages

In addition to English, the following languages are available:

Language

Code

Arabic

ar

Chinese (Simplified)

zh-CN

Chinese (Traditional)

zh-TW

Dutch

nl

Finnish

fi

French

fr

German

de

Hebrew

he

Italian

it

Japanese

ja

Korean

ko

Polish

pl

Portuguese (Brazilian)

pt-BR

Russian

ru

Spanish

es

Swedish

sv

Turkish

tr

Installing a non-English version of Application Integration

The Application Integration installed on the Workplace XT server is English by default. If you require a non-English version of Application Integration on the Workplace XT server, two methods are available to apply the alternative language version:

1.     Download/copy the latest available 1.1.5.x version of multilingual files from the same IBM FTP site to the following location, overwriting the English version:  

·         UNIX …/Filenet/Workplace/download

·         Windows ...\FileNet\Workplace\download

2.     End users can download ApplicationIntegration.exe in the required language directly to the end-user system.

New in this fix pack

The changes for this fixpack are listed in the Product fix history table for 1.1.5.2-WPXT-IF001. We recommend all customers using Java applets (file tracking, drag and drop add, search designer and the process applets) to install 1.1.5.2-WPXT-IF001 or greater to remove the security warnings displayed when applets are started on client workstations with Oracle JRE 1.7.0-45 or greater. For more information see the Java JRE Compatibility Flash

Current Daeja version

The current Daeja ViewOne Viewer version is 4.0.48.

Installation, migration, upgrade, and configuration

This section contains the following topics:

Support documentation

Requirements

 

Install this fix pack

Install a Workplace XT 1.1.5.2 system

Upgrade an existing version of Workplace XT to fix pack level 1.1.5.2-WPXT-IF002

Install this fix pack on a server with multiple Workplace XT instances

Notes

·       Workplace XT does not support migration from Application Engine.

·       The following installation procedures contain path names for both UNIX® and Windows®. If there is no difference in directory structure, a forward slash (/) is used to separate the elements of a path name for both UNIX and Windows.

·       When one of the following installation procedures includes an application path for WebSphere®, WebLogic, or JBoss, the default location is provided. The paths for your installation or deployment location might be different.

·       "<WPXT_install_path>" is a variable that indicates the location of the installed Workplace XT source files. Following are the default values for this variable, when using 1.1.3.x:

UNIX /opt/FileNet/WebClient/
Windows C:\Program Files\FileNet\WebClient\

Following are the default values for this variable, if Workplace XT was first installed with 1.1.4.0 or above:

UNIX /opt/IBM/FileNet/WebClient/
Windows C:\Program Files\IBM\FileNet\WebClient\

·       Installation of this fix pack is not affected by any virus protection software that might be running in the background.

Support documentation

·       Before installing this fix pack, consult the IBM FileNet P8 Platform Documentation and the IBM FileNet Workplace XT 1.1.5 documentation in the IBM FileNet P8 version 5.1 information center. The documentation in the P8 5.1 information center is the only current documentation for Workplace XT 1.1.5. This documentation contains additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and Workplace XT-related applications.

Note Search is enabled in the help system only if you have installed it as a Web site on a Web server that supports Java™ applications.

·       When installing this fix pack as a new system, or when installing this fix pack on a server with multiple instances of Workplace XT, you will need to use the IBM FileNet Workplace XT Installation Guide in conjunction with this readme.

·       When installing this fix pack in a high-availability environment, such as Veritas or Microsoft Cluster, or a load-balanced server farm, see the latest edition of the IBM FileNet P8 High Availability Technical Notice.

Requirements

This fix pack requires the following minimum versions of the supporting FileNet P8 Platform software:

·       For new installations:

o P8CE-4.5.1-007

o P8PE-4.5.1-002 (requires the PE client installation program version P8PE-4.5.1-002)

·       For upgrades:

o P8CE-4.5.1-007

o P8PE-4.5.1-002

If the optional IBM FileNet P8 eForms components are installed, the following minimum versions are required:

·       P8eF-4.0.2.-011

For more information, see the FileNet P8 Hardware and Software Requirements Guide and the FileNet P8 Fix Pack Dependency/Compatibility Matrix.

Install this fix pack

Download and extract the Workplace XT 1.1.5.2-WPXT-IF002 fix pack for your operating system.

Depending upon whether Workplace XT is already installed on your system, you can:

·       Install a Workplace XT 1.1.5.2 system

·       Upgrade an existing Workplace XT system to fix pack level 1.1.5.2

This fix pack should be installed on all machines where Workplace XT is (or will be) installed.

Install a Workplace XT 1.1.5.2 system

If you do not have Workplace XT already installed, use the downloaded 1.1.5.2 installation program to complete a full Workplace XT installation. See the latest edition of the IBM FileNet Workplace XT Installation Guide for instructions. Use the steps from the IBM FileNet Workplace XT Installation Guide and substitute 1.1.5.2 for any 1.1.5.0 entries as is currently documented.

·       If you are upgrading from Workplace XT 1.1.4.x to 1.1.5.2, follow the upgrade instructions in the IBM FileNet P8 version 5.1 information center.

·       If you are upgrading from Workplace XT 1.1.5.0 to 1.1.5.2, use the steps below.

Note: Refer to the IBM FileNet P8 Hardware and Software Requirements Guide to validate that your application server versions are supported with Workplace XT 1.1.5. Upgrade the server versions as necessary prior to upgrading Workplace XT.

Upgrade an existing Workplace XT 1.1.5 system to fix pack level 1.1.5.2

Use the following instructions to upgrade an existing version of Workplace XT to fix pack level 1.1.5.2:

1.     Log on to the application server:

UNIX Log on as a user with write access to the /bin directory and read, write, and execute access to the directory where you plan to install Workplace XT.

   Tip Although the installing user must have write access to the /bin directory, the Workplace XT installation program does not write to that directory.

Windows Log on as a member of the local Administrators group or a user with equivalent permissions.

2.     From Process Task Manager, stop Component Manager (if running), then exit the Process Task Manager application.

3.     (Windows only) From the Windows Services console, stop the Process Services Manager service.

4.     (Windows only) Using the Windows Task Manager, verify that no javaw.exe processes are running.

If the applications in the preceding steps stopped correctly, no Workplace XT-related javaw.exe processes should be running. If needed, use Windows Task Manager or some other process management tool to stop all javaw.exe processes that are in the directory path <WPXT_install_path>\_WCjvm\bin.

5.     Back up, undeploy, and remove the Workplace XT (web_client) web application from the J2EE application server.

WebSphere 6.1.x or 7.0.x

a.     Back up the deployed Workplace XT directory:

·         <WAS_HOME>/profiles/<profile_name>/installedApps/<node_name>/WorkplaceXT.ear/web_client.war

b.    Stop the Workplace XT application from the WebSphere administration console.

c.     Uninstall the Workplace XT application from Enterprise Applications.

d.    Save the changes and stop the WebSphere server.

e.     Delete the temporary Workplace XT directory (default: WorkplaceXT) from:

·         <WAS_HOME>/profiles/<profile_name>/temp/<node_name>/<instance>/

f.     Delete all folders from the wstemp in the following location:

·         <WAS_HOME>/profiles/><profile_name>/wstemp

WebLogic 10.3.0+

g.    From the WebLogic administration console stop the Workplace XT Web Application Module.

h.     Make a backup copy of the Workplace XT folder or of the deployed Workplace XT directory:

·         <WPXT_install_path>/WorkplaceXT

·         <WPXT_install_path>/deploy/<application_name>.war

·         <WPXT_install_path>/deploy/web_client.ear

i.      Delete the Workplace XT Web Application Module.

j.      Stop the WebLogic server.

k.     Delete the temporary Workplace XT directory (default: WorkplaceXT or web_client) from:
<WL_HOME>/<domain>/servers/<instance>/tmp/_WL_user

JBoss 4.3 EE and 5.0.1 AS

l.      Stop the JBoss server.

m.   Back up the deployed Workplace XT application:

·         <JBOSS_HOME>/server/<server_name>/deploy/<application_name>.war or .ear

n.     Delete the Workplace XT application from the deployed location.

o.    Clear out all files and folders within the following temp directories:

·         <JBOSS_HOME>/server/<server_name>/tmp/deploy

·         <JBOSS_HOME>/server/<server_name>/work/jboss.web/localhost

6.     For systems with the IBM Content Manager OnDemand (CMOD) site preference configured: Move the CMOD key store and change the keyStorePath context parameter in the web.xml file.

a.     Copy the CMOD key store file, cmodKeyStore. The default location is in the following path:

install_path/WorkplaceXT/WEB-INF

b.    Place the copy of the cmodKeyStore file into the Config/WebClient directory, in the following path:

install_home/FileNet/Config/WebClient

The default path for the variable install_home depends on the Workplace XT version that you are upgrading and on your operating system:

Version 1.1.3.x and earlier releases

UNIX: /opt

Windows: C:\Program Files

 

Version 1.1.4.0 and later releases

UNIX: /opt/IBM

Windows: C:\Program Files\IBM

Change the value for the keyStorePath parameter in the web.xml file to match the new location of the key store file:
<context-param>
<param-name>keyStorePath</param-name>
<param-value>install_home/FileNet/Config/WebClient/cmodKeyStore </param-value> </context-param>

7.     Optional: Copy existing configuration files.

If you have made custom changes to your configuration files in the deployed location, copy the following configuration files from the backup copy of your deployed Workplace XT application to the /WEB-INF folder in the installed directory on your application server, overwriting the existing installed files. You must do this before you apply the fix pack to the existing Workplace XT installation.

Copy the following files:

o    WcmApiConfig.properties

o    web.xml

from the /WEB-INF folder in the backed-up Workplace XT directory created in the previous step to the following directory:

<WPXT_install_path>/WorkplaceXT/WEB-INF/

1.     (Upgrade JBoss 4.x.x to JBoss 5.x.x only) When Workplace XT is upgraded on a system that has been upgraded from JBoss 4.x.x to JBoss 5.x.x, the Workplace XT upgrade will need the following code snippet added to the web.xml file before attempting to deploy Workplace XT using JBoss 5.x.x. Type the following lines at the end of the corresponding listener section of the web.xml file.

<listener>
   <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>

The jboss-classloading.xml file must also be manually copied into the /WorkplaceXT/WEB-INF/ directory:

From the FileNet/WebClient/jboss5 folder, copy the jboss-classloading.xml file to the<WPXT_install_path>/WorkplaceXT/WEB-INF/ directory.

2.     Optional: Install IBM Production Imaging Edition Viewer Pro. If you have purchased IBM Production Imaging Edition, the Viewer Pro software can be installed when you run the Workplace XT installation. To activate the Viewer Pro installation, you must run the license installer before you install Workplace XT.

Attention: For sites with IBM® Production Imaging Edition Viewer Pro installations: If you want to upgrade a Workplace XT version 1.1.4 configuration to version 1.1.5 including the Viewer Pro software, you must uninstall the software as documented in its Installation Guide before running the Workplace XT installer.

3.     Upgrade Workplace XT.

a.     Access the Workplace XT 1.1.5.2 fix pack software package.

b.    Start the installation process in one of the following ways:

·         To upgrade interactively, launch the appropriate setup program (WorkplaceXT-1.1.5.2-<operating_system>.bin or .exe) and follow the steps in the installation screens. The installation program detects and copies settings from the previous Workplace XT installation.

·         If you are upgrading to this fix pack silently, navigate to and execute the installation program from the command line prompt.

UNIX ./WorkplaceXT-1.1.5.2-<operating_system>.bin -options <path_to_edited_input_file>/XT_silent_upgrade.txt -silent

Windows WorkplaceXT-1.1.5.2-WIN.exe -options “<path_to_edited_input_file>\XT_silent_upgrade.txt” -silent

c.     Verify that no errors or failures were logged in the web_client_install_log_1_1_5_2.txt file, located in <WPXT_install_path>. Correct any errors before proceeding.

If user tokens are enabled on the system prior to the upgrade and if you are using version 4.5.1, 5.0, or 5.1 of Content Engine, the authentication-websphere.jar and log4j-1.2.13.jar files must be copied again. Refer to the appropriate section below for configuring user tokens and the location from which these files are copied.

To configure WebSphere to support user tokens and WebDAV connections for Workplace XT (for Application Integration, eForms, Records Manager, and others)

·         Copy the authentication-websphere.jar file from here:
install_path/IBM/FileNet/WebClient/WorkplaceXT/authenticationFiles

to here:
WAS_home/AppServer/lib/ext

·         Copy the log4j-1.2.13.jar file from here:
install_path/FileNet/WebClient/WorkplaceXT/WEB-INF/lib

to here:
WAS_home/AppServer/lib/ext

To configure WebLogic to support user tokens and WebDAV connections for Workplace XT (including Application Integration, eForms, Records Manager, and others)

·         Copy the authentication-weblogic.jar file from here:
install_path/IBM/FileNet/WebClient/WorkplaceXT/authenticationFiles

to here:
WL_home/server/lib/mbeantypes

·         Copy the log4j-1.2.13.jar file from here:
install_path/FileNet/WebClient/WorkplaceXT/WEB-INF/lib

to here:
WL_home/server/lib/mbeantypes

To configure JBoss to support user tokens and WebDAV connections for Workplace XT (for Application Integration, eForms, Records Manager, and others)

·         Copy the authentication-utils.jar file from here:
install_path/IBM/FileNet/WebClient/WorkplaceXT/authenticationFiles

to here:
JBOSS_home/server/server_name/lib

1.     Configure the WebLogic session cookie settings. (This step is only required for newer WebLogic versions.)

a.     Go to the {WORKPLACEXT_INSTALLED_DIR}/FileNet/WebClient/WorkplaceXT/WEB-INF directory.

b.    Back up the weblogic.xml to weblogic.xml.bak.

(Upgrade of WebLogic 10.x to 11g only) When Workplace XT is upgraded on a system that has been upgraded from WebLogic 10.x to WebLogic 11g, the Workplace XT upgrade will need the following weblogic.xml file added to the WEB-INF directory before attempting to deploy Workplace XT using WebLogic 11g.

·         Copy the weblogic-11g.xml from <install location>\WebClient\weblogicFiles. to the WEB-INF directory

·         Rename the weblogic-11g.xml file to weblogic.xml.

1.     Go to the {WORKPLACEXT_INSTALLED_DIR}/FileNet/WebClient/deploy directory

2.     Delete the existing web_client.war and web_client.ear.

3.     Re-create the WAR and/or EAR file.

a.     To create a UNIX WAR file, run the shell script "./create_web_client_war.sh."

b.    To create a UNIX EAR file, run the shell scripts "./create_web_client_war.sh." then "./create_web_client_ear.sh."

c.     To create a Windows WAR file, run the batch script "create_web_client_war.bat."

d.    To create a Windows EAR file, run the batch scripts "create_web_client_war.bat" then "create_web_client_ear.bat."

4.     Deploy the new web_client.ear or web_client.war file.

5.     Restart the application server and redeploy Workplace XT.

6.     (Windows only) From the Windows Services console, restart the Process WP XT Services Manager service.

7.     If needed, restart Component Manager from Process Task Manager, then exit the Process Task Manager application. For details, see the IBM FileNet Workplace XT Installation Guide.

Note - Content Engine and Process Engine client installers

·       After you install a Content Engine fix, you must run the Content Engine Java Client Files using the Workplace XT option. For instructions, see the Content Engine fix readme or this article in the Info Center

·       After you install a Business Process Management (BPM) Process Engine fix, you must run the Process Engine Client. For instructions, see the Process Engine fix readme or this article in the Info Center

Install this fix pack on a server with multiple Workplace XT instances

If you are installing this service pack in an environment where you have multiple instances of Workplace XT on a single application server, use the "Upgrade an existing Workplace XT system to fix pack level 1.1.5.2" procedure with the following modifications:

·       When you complete the steps under "Back up, undeploy, and remove the Workplace XT web application from the J2EE application server," you must:

o Make backup copies of all deployed instances or Workplace XT.

o Uninstall all deployed instances of Workplace XT.

o Delete the temporary directory for all instances of Workplace XT.

·       When you "Copy existing configuration files," you must copy the web.xml files for each deployed instance of Workplace XT, and give them a descriptive name (such as web.xml.2)

·       After you "Upgrade Workplace XT," you must back up the existing configuration files in ..FileNet/Config/WebClient2 and so on, and then copy the updated configuration files in ..FileNet/Config/WebClient to ..FileNet/Config/WebClient2 and manually edit in any custom changes from the old configuration files to the new updated files.

·       When you "Redeploy Workplace XT," you must repackage the .war or .ear files for the additional instances of Workplace XT using the modified web.xml files mentioned above. For information, see the IBM FileNet Workplace XT Installation Guide.

Uninstall this fix pack

To remove this fix pack, you must completely uninstall Workplace XT. Removal of the fix pack alone is not supported. For more information, see the IBM FileNet Workplace XT Installation Guide.

Product fix history

The following table lists the product fixes in interim fix 1.1.5.2-WPXT-IF002

APAR

Description

Undisclosed security issue

PJ39056

When rendering to pdf using the integratedWebbasedCommand, the url will open the data form in an active window rather than pdf.

PJ39737

The setparameterValue parameter value cannot be null else an error message is received when completing the workflow form.

PJ40978

When file tracker is enabled, using the add document wizard in conjunction with the viewer can cause the add wizard to hang.

PJ41770 

Some date values, when entered in a search, or document properties are incorrectly being reported as invalid, with the following error: "The specified value for this data type is not valid. Enter a valid date using the format dd/MM/yy"

PJ42065

The eForms table cell sends a null value separated with a semicolon to the workflow field that mapped to it.

PJ42102

On the All Properties info page under system properties, the document size is inaccurately listed as 1KB.

PJ42112

Opening an eForms form data (.ifx) from Workplace XT returns a blank screen.

PJ42211

From Internet Explorer, the add user dialog may fail to load on the security page due to a malformed windowID.

PJ42263

Dates on the audited event page are displayed in the time zone of the application server regardless of the date/time settings defined in preferences.
A new setting is supported in web.xml, showDatePropertyHistoryInPreferredFormat, that can be used to display dates according to the date/time preference settings. If it's set to false (default), the time format will include the time zone to indicate that the time is in the server time zone.

PJ42334

The eForms step processor used in work items sent to multiple users switches edit control from first user to second user

PJ42466

User, with locale set to zh-CN locale, cannot transfer a workflow from in the Process Designer from Workplace XT in the CPE 5.2 environment.

 

The following table lists the product fixes in interim fix 1.1.5.2-WPXT-IF001

APAR

Description

PJ39285

When using a multi-object store search template, if classes defined in one object store are not present in another object store that is part of the search criteria, the search template will fail to open.

PJ39899

With P8eF-4.0.2 and WPXT-1.1.5 when a mapping relationship between form cells and workflow properties is configured (using the eformsMapNullforTableDateString parameter in bootstrap.properties), if there is a space without a value for a number field, then any value below it in the same column will move up to fill it, instead of remaining in the table cell (row) where it was placed.

PJ40142

After upgrading to Workplace XT 1.1.5, users cannot open a document by clicking on the document name from the properties page.

PJ41215

From My Workplace, My inbox refresh shows as empty after clicking the close button on a work item eForm.

PJ41297

Cannot run an Advanced Search on a subclass against Content Engine 4.5.1 after upgrading to Workplace XT 1.1.5.2.

PJ41337

eForms: If a user has a form open in a browser and closes the browser without using the close button on the form toolbar, the form data file is left in a checked-out state.

PJ41380

With Workplace XT configured for Tivoli Access Manager SSO, the maximize option fails from My Workplace.

PJ41395

The csv file created using the Export List action contains extra characters in date and size values. 

PJ41411

Multi select Set Properties or Checkin action does not refresh the content listview after the properties are updated.

PJ41478

Can not download files with Chinese characters in the file name if using IBM HTTP server.

PJ41790

If an Object Store in the Content Engine domain does not include the publishing extension add on, a failure will occur when attempting to add a workflow definition using Process Designer.

PJ41690

SSL redirection fails after upgrade to Workplace XT 1.1.5.2

PJ41838

JBOSS users cannot log back into Workplace XT 1.1.5.2 after logging out unless they open a new browser.

Undisclosed security APAR

The following table lists the product fixes in fix pack 1.1.5.2-WPXT-FP002

APAR

Description

PJ41000

After saving site preferences, running simulations from the simulation designer will fail with a malformed url exception.

PJ40956

Advanced checkin fails when an entry template uses a choice list and a value in the choice list contains an apostrophe.

PJ40918

Error message unclear when searching for a property string longer than maximum length defined in content engine using DB2.

PJ41002

Viewing a work item with with forms and form policies results in a null pointer exception when using p8 forms 4.0.2.12 or higher

PJ40900

Right-to-left language documents are displayed left-to-right in the Production Imaging Edition viewer.

My Workplace does not honor the maximum number of tasks before filtering in Site Preferences.

PJ41052

When using WebSphere, the session id created before login does not change after a successful login to Workplace XT.

PJ40987

When updating a multi-valued property that was previously filled with an empty string, an update confirmation is not displayed.

PJ40649

Get content using path-based url fails on Workplace XT when using TAM SSO.

PJ40588

Viewer annotation highlight polygons lose translucency upon re-open.

PJ40540

Search templates load slowly on object stores with a large number of classes.

PJ40568

When a date time property federated from IS is displayed it will be modified to midnight in the current user's timezone.

PJ40313

After upgrade from P8 eForms 3.5.1.x to 4.0.2.x users are unable to open form data due to an XML error.

PJ40415

Event data is missing from the history print view when the server is using a locale other than English.

PJ40986

When the WEB.XML disableEnterEscPageClose option is set to true, a return character cannot by typed into multi-line text fields.

PJ40143

Pressing the ENTER or ESC keys while entering a property value using Windows IME also completes or cancels the wizard page.

PJ40963

Running a search template does not return documents when "added on" is used with the "is equal to" clause.

PJ40137

In Workplace Only mode choice lists values longer than 48 characters cannot be displayed as the drop down is too narrow.

PJ40052

Cannot open a folder using path based urls.

PJ40039

Advanced search fails when searching a subclass and the detailed properties contains a property not belonging to the class.

PJ40111

Unable to view any color LZW compressed .TIFF document from the Image Viewer.

PJ40030

Search designer error "eq node must have 2 child nodes" when when searching on properties with choice lists.

PJ39962

An error occurs when sorting on a property designated as a secondary sort column in a search template.

PJ39899

eForm table values for number data type are shifting after saving.

PJ39740

When redacting TIFF images with TIFF tags, the redacted tiff file may be distorted and unviewable.

PJ39729

When more than 150 access roles exist, only the first 150 can be seen in site preferences.

PJ39696

Cannot refresh the user display name cache.

PJ39306

Add document file selection dialog comes up behind the add document wizard window  on Windows 7 with IE 7/8.

PJ39264

Search templates with more than 9 sort levels are not sorted properly in Workplace XT.

The following table lists the product fixes in fix pack 1.1.5.1-WPXT-FP001

APAR

Description

PJ39553

If object store settings under User Preferences contain a column property that has been removed from the system, searches can no longer be executed from the search page.

PJ39514

Potential data corruption during simultaneous batch upload via drag and drop. The content of some documents could be corrupted.
For more information, refer to the flash alert for this issue.

PJ39140

Slow performance when opening the advanced download page for documents with multiple content elements.

PJ39294

The error message when a user does not have permission to open a document received by hyperlink indicated the object was not found.

PJ39265

If the search timed out, you cannot re-run the search immediately.

PJ39129

Images are slow to display when rotateAnnotationsWithView is enabled.

PJ39088

Users that belong to an authorized group have rights to add annotations, but cannnot add the annotation to a document.

PJ39382

PDF files created by the Datacap application and ingested into the P8 CE cannot be viewed.

Contact customer support

For information about contacting customer support:

1.     Navigate to the Information Management support page (www.ibm.com/software/data/support).

2.     On the Information Management Support page, search for: How to get support for IBM FileNet products.

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:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106-0032, Japan

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

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

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

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

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

IBM Corporation

J46A/G4

555 Bailey Avenue

San Jose, CA 95141-1003

U.S.A.

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

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

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

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

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

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

COPYRIGHT LICENSE:

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

Trademarks

·       IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines 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.ibm.com/legal/copytrade.shtml.

·       Sun, Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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

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

·       Other company, product, or service names may be trademarks or service marks of others.