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

About this fix pack
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 pack

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

The Workplace XT 1.1.5.2-WPXT-FP002 fix pack installs a new, complete Workplace XT 1.1.5.2 system, or upgrades an existing Workplace XT system. Workplace XT fix packs 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 fix packs or manually locate the fix packs by doing one of the following:
  2. View the list of available fix packs.

Compatibility

For compatibility information, see the:

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:

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.

The ToolbarCollapsed HTML parameters used to control the default display of the viewer toolbars are not picked up in version 4.0.26 of the ViewOne viewer (included in 1.1.5.2-WPXT-FP002.) 

The default behavior is the toolbars are not collapsed so this issue only effects customers who have changed the default behavior by modifying the WcmJavaViewer.jsp file and added one or more of the following HTML parameters:
imageToolbarCollapsed
viewToolbarCollapsed
annotationToolbarCollapsed

Workaround: Once the viewer is opened, manually collapse or expand the toolbar.

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:  
  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-FP002.

Current Daeja version

The current Daeja ViewOne Viewer version is 4.0.26.

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-FP002
Install this fix pack on a server with multiple Workplace XT instances

Notes

Support documentation

Requirements

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

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

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-FP002 fix pack for your operating system.

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

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.

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

    1. Back up the deployed Workplace XT directory:
      • <WAS_HOME>/profiles/<profile_name>/installedApps/<node_name>/WorkplaceXT.ear/web_client.war
    2. Stop the Workplace XT application from the WebSphere administration console.
    3. Uninstall the Workplace XT application from Enterprise Applications.
    4. Save the changes and stop the WebSphere server.
    5. Delete the temporary Workplace XT directory (default: WorkplaceXT) from:
      • <WAS_HOME>/profiles/<profile_name>/temp/<node_name>/<instance>/
    6. Delete all folders from the wstemp in the following location:
      • <WAS_HOME>/profiles/><profile_name>/wstemp

    WebLogic 10.3.0+

    1. From the WebLogic administration console stop the Workplace XT Web Application Module.
    2. 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
    3. Delete the Workplace XT Web Application Module.
    4. Stop the WebLogic server.
    5. 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

    1. Stop the JBoss server.
    2. Back up the deployed Workplace XT application:
      • <JBOSS_HOME>/server/<server_name>/deploy/<application_name>.war or .ear
    3. Delete the Workplace XT application from the deployed location.
    4. 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.
    1. Copy the CMOD key store file, cmodKeyStore. The default location is in the following path:

      install_path/WorkplaceXT/WEB-INF

    2. 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:

  8. 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/

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

  10. 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.
  11. Upgrade Workplace XT.
    1. Access the Workplace XT 1.1.5.2 fix pack software package.
    2. 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

    3. 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.
    4. 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)

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

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

  12. Configure the WebLogic session cookie settings. (This step is only required for newer WebLogic versions.)
    1. Go to the {WORKPLACEXT_INSTALLED_DIR}/FileNet/WebClient/WorkplaceXT/WEB-INF directory.
    2. Back up the weblogic.xml to weblogic.xml.bak.
    3. (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.

  13. Go to the {WORKPLACEXT_INSTALLED_DIR}/FileNet/WebClient/deploy directory
  14. Delete the existing web_client.war and web_client.ear.
  15. Re-create the WAR and/or EAR file.
    1. To create a UNIX WAR file, run the shell script "./create_web_client_war.sh."
    2. To create a UNIX EAR file, run the shell scripts "./create_web_client_war.sh." then "./create_web_client_ear.sh."
    3. To create a Windows WAR file, run the batch script "create_web_client_war.bat."
    4. To create a Windows EAR file, run the batch scripts "create_web_client_war.bat" then "create_web_client_ear.bat."
  16. Deploy the new web_client.ear or web_client.war file.
  17. Restart the application server and redeploy Workplace XT.
  18. (Windows only) From the Windows Services console, restart the Process WP XT Services Manager service.
  19. 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.

Notes

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:

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