EMC Documentum TaskSpace

Transcription

1 EMC Documentum TaskSpace Version 6 Deployment Guide P/N A01 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright 2007 EMC Corporation. All rights reserved. Published October 2007 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.

3 Table of Contents Preface... 9 Chapter 1 TaskSpace Deployment Overview Chapter 2 Planning for Deployment Planning TaskSpace deployment Required and optional supporting software Typical configuration Preparing the Content Server Application server host requirements Directory name restriction Content transfer directory permissions DNS resolution Deploying multiple applications Deploying language packs Chapter 3 Preparing Requirements Speci c to TaskSpace Documentum prerequisites for TaskSpace Installing the TaskSpace DocApp Installing the Tutorial Sample DocApp Chapter 4 Preparing the Client Hosts Ensuring a certified JVM on browser clients Enabling HTTP content transfer in Internet Explorer Enabling UCF content transfer in Internet Explorer 7 on Windows Vista Enabling content transfer in Firefox Clearing the browser cache Supporting Outlook mail message archives Using Citrix Presentation Server Client Turning off the pop-up blocker in Internet Explorer Chapter 5 Preparing the Application Server Host Setting the Java memory allocation Preparing environment variables for non-default DFC locations Preparing Apache Tomcat Preparing BEA WebLogic Supporting large content transfer operations in a managed server environment Preparing IBM WebSphere EMC Documentum TaskSpace Version 6 Deployment Guide 3

4 Table of Contents Applying policies for WebSphere security Supporting non-default content transfer locations Preparing Oracle Application Server Preparing Sun Java System Application Server Turning off tag pooling Modifying the Sun policy file Preparing to use an external web server Chapter 6 Deploying TaskSpace Preparing the WAR file for deployment Enabling DFC connections to repositories Enabling DFC memory optimization Enabling presets and preferences repositories Deploying multiple applications Chapter 7 Completing the Deployment Configuring image viewers for TaskSpace Configuring UCF Configuring IBM WebSphere after deployment Changing the classloader and compiler settings Accessing the TaskSpace user interface Chapter 8 Troubleshooting Deployment Wrong JRE used for application server No global registry or connection broker No connection to repository DM_VEL_INSTANTIATION_ERROR Page not found error in browser Login page incorrectly displayed Slow performance Out of memory errors in console or log Slow display first time DFC using the wrong directories on the application server Application startup errors Tag pooling problem UCF client problems Citrix client problems Chapter 9 Troubleshooting TaskSpace Deployment Troubleshooting DocApp deployment Troubleshooting application servers Troubleshooting TaskSpace deployment on Weblogic Troubleshooting TaskSpace deployment on WebSphere Resolving the java.lang.verifyerror Resolving the java.lang.nosuchmethoderror Resolving the JSPG0049E error Implementing configuration changes across multiple application servers EMC Documentum TaskSpace Version 6 Deployment Guide

5 Table of Contents Troubleshooting TaskSpace image viewer deployment Troubleshooting the Brava! image viewer Verifying that the Brava! Server is working Configuring the Brava! license server Specifying the version of the Brava! cab file Enabling client logs for Brava! viewer View other users annotations in Brava! Checking the Brava! viewer version Removing the Brava! viewer from a client computer Troubleshooting the Daeja image viewer Enabling client logs for the Daeja viewer Checking the Daeja viewer version Removing the Daeja viewer from a client computer Troubleshooting the Adobe Reader image viewer Configuring Adobe Reader byte serving on Firefox Troubleshooting when image does not display using Adobe Reader Specifying the deployment location for the image viewer Clearing the browser cache Allowing display of documents without using ACS/BOCS Changing the threshold for page serving Troubleshooting TaskSpace configuration Maintaining configurations while reinstalling the TaskSpace DocApp Troubleshooting a preset error Localizing labels of newly-created tabs Making custom object types available for role configuration Enabling hot keys in Firefox Appendix A Pre-Installation Checklist EMC Documentum TaskSpace Version 6 Deployment Guide 5

6 Table of Contents List of Figures Figure 1. Basic WDK host configuration EMC Documentum TaskSpace Version 6 Deployment Guide

7 Table of Contents List of Tables Table 1. Deployment scenarios Table 2. Image viewer scenarios Table 3. Selecting viewers Table 4. Output directories and JVM custom properties Table 5. Preferences configuration elements Table 6. Preinstallation tasks EMC Documentum TaskSpace Version 6 Deployment Guide 7

8 Table of Contents 8 EMC Documentum TaskSpace Version 6 Deployment Guide

9 Preface This guide describes how to deploy EMC Documentum TaskSpace software. Intended audience The information in this guide is intended for administrators who need to deploy TaskSpace software. It assumes familiarity with basic Documentum functionality, such as repository configuration and maintenance. You should also be familiar with the Windows, UNIX, or Linux operating system and be able to install and configure a J2EE application server. Most of the chapters of this guide provide general information that applies to any WDK-based application. For information specific to TaskSpace, refer to Chapter 1, TaskSpace Deployment Overview and the Documentum TaskSpace Release Notes. For instructions on configuring and using TaskSpace after deployment, refer to the following guides: Documentum TaskSpace Configuration Guide Documentum TaskSpace User Guide Documentum TaskSpace Sample Application Tutorial For instructions on deploying Document Image Services, refer to the Documentum Document Image Services Deployment Guide. Revision history The following changes have been made to this document. EMC Documentum TaskSpace Version 6 Deployment Guide 9

10 Preface Revision History Revision Date October 2007 Description Initial publication 10 EMC Documentum TaskSpace Version 6 Deployment Guide

11 TaskSpace Deployment Overview Chapter 1 This chapter provides an overview of TaskSpace deployment. TaskSpace software, in combination with the rest of the Documentum Process Suite and the Documentum repository, delivers an end-to-end solution for managing high-volume Transactional Content Management (TCM) applications. Note: Repositories from releases older than 6.0 are not supported with the TaskSpace software. To deploy TaskSpace: 1. Before you begin deployment, consider whether you want to deploy TaskSpace alone or with Document Image Services. Other planning decisions are required, as for any WDK-based product. For information, refer to Chapter 2, Planning for Deployment. 2. Prepare the requirements that are specific to TaskSpace, such as the TaskSpace DocApp. For instructions, refer to Chapter 3, Preparing Requirements Specific to TaskSpace. 3. Prepare the client hosts. For instructions, refer to Chapter 4, Preparing the Client Hosts. 4. On the computer that you intend to use as the application server host, perform the following steps: a. Make sure your operating system is supported. For a list of supported operating systems, refer to the Documentum TaskSpace Release Notes. b. Install a supported application server. For a list of supported application servers, refer to the Documentum TaskSpace Release Notes. For more details, refer to Chapter 5, Preparing the Application Server Host. c. Log in to the operating system using a user account with administrative rights on the operating system, such as the Administrator user. d. Use the application server to deploy TaskSpace (TaskSpace.WAR) as described in Chapter 6, Deploying TaskSpace. EMC Documentum TaskSpace Version 6 Deployment Guide 11

12 TaskSpace Deployment Overview 5. Complete the TaskSpace deployment. For instructions, refer to Chapter 7, Completing the Deployment. 6. (Optional) If you have deployed both TaskSpace and Document Image Services, configure one or more image viewers, such as Adobe Acrobat Reader, Daeja ViewOne Pro, or IGC Brava!. For information, refer to Configuring image viewers for TaskSpace, page Using the prepared user account, test the deployment. For instructions, refer to Accessing the TaskSpace user interface, page If any problems occur, refer to Chapter 8, Troubleshooting Deployment and Chapter 9, Troubleshooting TaskSpace Deployment. 12 EMC Documentum TaskSpace Version 6 Deployment Guide

13 Chapter 2 Planning for Deployment This chapter addresses software and hardware decisions you must make before you deploy a WDK-based application. This chapter contains instructions that are shared by all WDK-based products. Check your release notes for information on the application servers, browsers and other software in the environment that are certified for your product. This chapter discusses the following topics: Planning TaskSpace deployment, page 13 Required and optional supporting software, page 15 Typical configuration, page 16 Preparing the Content Server, page 17 Application server host requirements, page 17 Deploying multiple applications, page 18 Deploying language packs, page 18 Planning TaskSpace deployment Before you begin deployment, consider whether you want to deploy TaskSpace alone or with Document Image Services. Table 1. Deployment scenarios Deployment scenario TaskSpace Description The TaskSpace module simplifies tasks through a streamlined user interface with built-in image operations. TaskSpace is specifically designed for users who have to perform a large number of tasks, and who have to find documents and folders in very large repositories. EMC Documentum TaskSpace Version 6 Deployment Guide 13

14 Planning for Deployment Deployment scenario Document Image Services Both Description The Document Image Services module provides support for image-oriented documents and is designed to support a wide range of third-party viewers. The Document Image Services module can be deployed with TaskSpace or with another application that uses the WDK Image viewer control. For instructions on deploying Document Image Services, refer to the Documentum Document Image Services Deployment Guide. For instructions on using the Document Image Services module with another application that uses the WDK Image Viewer Control, refer to the Documentum Document Image Services Developer Guide. If you deploy both TaskSpace and Document Image Services, TaskSpace features include an image viewer, annotation support for Daeja ViewOne Pro and IGC Brava!, and page serving for PDF and TIFF files. (Page serving does not apply to secure PDF files.) The image viewers are installed separately. Also consider image viewer setup. Table 2. Image viewer scenarios Image viewer scenario UCF Image viewers Description If you deploy TaskSpace without Document Image Services, documents are displayed using UCF technology. This means that TaskSpace opens each document using an association of file types to programs. For example, if a TaskSpace user displays an image, the document might open in Microsoft Paint. When UCF opens a file, it uses the file-program association from the client operating system. For more information on UCF, refer to the Web Development Kit and Client Applications Development Guide. If you deploy both TaskSpace and Document Image Services and you want to include image viewers in your deployment, you can install Adobe Acrobat Reader, Daeja ViewOne Pro, or IGC Brava!. The following table compares the available image viewers: 14 EMC Documentum TaskSpace Version 6 Deployment Guide

15 Planning for Deployment Table 3. Selecting viewers Adobe Acrobat Reader IGC Brava! Daeja ViewOne Pro Runtime ActiveX control ActiveX control Java applet Localization Annotations All TaskSpacesupported languages Not currently supported Currently French, German, and Japanese Supported File Formats PDF only Currently TIFF, PDF, and JPEG Page Access Browsers Deployment Byte streaming (PDF) All TaskSpacesupported browsers Client side deployment Page Serving (TIFF/PDF) Internet Explorer 6 only Server side deployment License Server No Yes No Website com Note: Page serving does not apply to secure PDF files. All TaskSpacesupported languages Supported TIFF, PDF, GIF, JPEG, and other common imaging formats Page Serving (TIFF/PDF) All TaskSpacesupported browsers Server side deployment Required and optional supporting software Additional software products are required for WDK and WDK applications including the following: Content Server and its associated database Content Server global repository Connection broker You must specify one or more connection brokers in the dfc.properties file. Refer to To configure connections in dfc.properties before deployment, page 47 for information on configuring the docbroker before deployment. J2EE application server or servlet container EMC Documentum TaskSpace Version 6 Deployment Guide 15

16 Planning for Deployment All WDK-based applications require DocApps that must be installed in the repository. The Webtop DocApps are provided in Content Server version 6. Typical con guration When deployed on a single application server, a typical WDK-based application requires the following network components: Application server host on which the WDK-based application will be deployed Separate Content Server host, where a repository is installed and where one or more Content Servers run Global registry repository Client hosts that run a supported web browser Figure 1, page 16 shows the network components. Figure 1. Basic WDK host con guration 16 EMC Documentum TaskSpace Version 6 Deployment Guide

17 Planning for Deployment Caution: For security and performance reasons, do not install the Content Server and a WDK-based application on the same host. In addition, the Content Server installs an internal WebLogic server that for licensing reasons cannot be used to deploy web applications. Clustered environments WDK-based applications can be deployed in supported clustered environments. Refer to the release notes for each WDK-based application to learn which managed server configurations are supported. Preparing the Content Server The following topics describe Content Server requirements. Content Server 6 installs certain DocApps that are required for a WDK-based application. You do not need to perform a separate installation of these. Products built on WDK or Webtop may require additional DocApps, which are available on the product download site. The global registry requirement A global registry of Content Server version 6 must be installed in your environment in order to run a WDK-based application. A global registry is a Content Server that has been designated as a global registry. For information on designating your application s global registry before deployment, refer to Enabling DFC connections to repositories, page 46. Application server host requirements The application server host used for WDK-based applications has the requirements described in the following sections. Directory name restriction Java does not allow directories containing the following characters, which must not appear in the directory names or paths of Documentum applications:! \ / : *? " < > EMC Documentum TaskSpace Version 6 Deployment Guide 17

18 Planning for Deployment Content transfer directory permissions The content transfer directory on the application server host is used to store files temporarily when they are transferred between the repository and the client machine. The default content transfer directory is specified in the app.xml file as the value of <server>.<contentlocation>. The application server instance owner must have write permissions on this temporary content transfer location. You can change the default value to a location on your application server host for which the application server instance owner has write permission. For information on specifying locations in the Unified Client Facilities (UCF) client and server configuration files, refer to Web Development Kit Development Guide. Some application servers require policies that grant permissions to write to these directories. Refer to deployment information for your application server to see Documentum policy settings. DNS resolution The Domain Name Server must be configured to properly resolve IP addresses based on the URL used to access the server. Deploying multiple applications You can deploy multiple WDK-based applications of version 6 on a single host. Each instance of an application must be deployed to a different virtual directory. If the applications share the same application server instance, the applications must be the same version--version 6 or higher. You can deploy applications to separate instances of the application server. If the applications use different versions of DFC, you must deploy them in separate application server instances. Deploying language packs Language packs are available to localize (translate) WDK-based applications. A language pack is a language-specific archive file that contains a graphical user interface (GUI) and user documentation that have been localized into a language other than the default application language, U.S. English. To deploy language packs, unpack your product 18 EMC Documentum TaskSpace Version 6 Deployment Guide

19 Planning for Deployment WAR file and add the language packs according to the instructions in Web Development Kit Applications Language Pack Installation and Release Notes. EMC Documentum TaskSpace Version 6 Deployment Guide 19

20 Planning for Deployment 20 EMC Documentum TaskSpace Version 6 Deployment Guide

21 Chapter 3 Preparing Requirements Speci c to TaskSpace This chapter describes steps that are required to prepare your environment for TaskSpace. To prepare the Documentum environment: 1. Install Documentum prerequisites. For instructions, refer to Documentum prerequisites for TaskSpace, page In Documentum Administrator, create a user and give it the EMC Documentum administrator or superuser privilege level. This is required for DocApp installations. For instructions, refer to the Documentum Administrator User Guide. 3. Install required DocApps to the repository or repositories that will be used with TaskSpace: a. Install the Forms DocApp (the DocApp for Forms Builder). For instructions, refer to the Forms Builder Installation Guide. b. Install the Process Builder DocApp. For instructions, refer to the Process Builder Installation Guide. c. Install the TaskSpace DocApp. For instructions, refer to Installing the TaskSpace DocApp, page 22. d. (Optional) Install the Document Image Services DocApp. For instructions, refer to the Documentum Document Image Services Deployment Guide. e. (Optional) Install the TaskSpace Tutorial Sample DocApp. For instructions, refer to Installing the Tutorial Sample DocApp, page 24. EMC Documentum TaskSpace Version 6 Deployment Guide 21

22 Preparing Requirements Speci c to TaskSpace Documentum prerequisites for TaskSpace This section briefly describes how to prepare the Documentum environment required by TaskSpace. Note: For each installation, log in to the operating system using a user account with administrative rights on the operating system, such as the Administrator user. To prepare the Documentum environment: 1. Install Content Server and create one or more repositories for TaskSpace users. For instructions, refer to the Content Server Installation Guide. 2. Install the following products in any order: Documentum Administrator. For instructions, refer to the Documentum Administrator Deployment Guide. Application Builder. By default, this also installs Application Installer, which is also required. For instructions, refer to the Application Builder Installation Guide and Release Notes. Process Builder. By default, this also installs Forms Builder, which is also required. Also, installing the Process Builder DocApp enables the Process Engine, which is also required. For instructions, refer to the Documentum Process Builder Installation Guide. When the Documentum environment has been prepared, you can install the TaskSpace DocApp. For instructions, refer to Installing the TaskSpace DocApp, page 22. Installing the TaskSpace DocApp To work properly, TaskSpace requires certain files and objects in any EMC Documentum repository to which it connects. You install these files and objects using a Documentum DocApp, which is an archived collection of Documentum Content Server objects. The files and objects required by Documentum TaskSpace are located in the TaskSpace DocApp. Install the DocApp in the global repository, and once in each EMC Documentum repository in which any user will run TaskSpace. Install the DocApp from any computer with the latest version of Documentum Application Installer on the local computer. (Documentum TaskSpace Release Notes contains specific version requirements.) If Documentum Application Installer is not installed on the local computer, download and install it before running the procedure below. You must have the EMC Documentum administrator or superuser privilege level to install a DocApp using Documentum Application Installer (DAI). 22 EMC Documentum TaskSpace Version 6 Deployment Guide

23 Preparing Requirements Speci c to TaskSpace To install the TaskSpace DocApp: 1. Download the TaskSpace DocApp from the following location: Note: The Powerlink website provides access to subscribenet.com/ control/dctm/index where a complete listing of products is available for download. 2. Unzip the downloaded file TaskSpace_DocApp_6.0.zip. The files comprising the DocApp are extracted into a subdirectory named TaskSpace. 3. From the Start menu, select Programs > Documentum > Application Installer. The login screen for Documentum Application Installer appears. 4. Select the EMC Documentum repository into which you want to install the DocApp and log in as a user with the EMC Documentum superuser or administrator privilege level. Documentum Application Installer starts. 5. Click Browse from the DocApp folder selection section and navigate to the TaskSpace directory containing the DocApp files (from step 2). 6. (Optional) In the Installer Log section, type a log filename in the File name box. The default log filename is TaskSpace_InstallerLog.html. Click Browse to select a directory other than the default to save the log file. You can refer to the log file for any errors that occur during the installation of DocApp. 7. Click OK. A dialog box appears detailing the DocApp name, target repository, and the installation status. EMC Documentum TaskSpace Version 6 Deployment Guide 23

24 Preparing Requirements Speci c to TaskSpace 8. Click Start Installation. A message appears indicating the installation process takes a few minutes to complete. 9. Click OK. If users are currently connected to the EMC Documentum repository into which you are installing the DocApp, a message appears asking whether you want to continue with the installation. Click Yes. Users are not affected by the installation, but they will not see the changes made by the DocApp until they reconnect. 10. Repeat steps 3 through 9 for each EMC Documentum repository in which you plan to use TaskSpace. 11. Click Quit Installer. After you have installed the TaskSpace DocApp, a script automatically runs. This script adds the current user (the user who installed the DocApp) as a member of the ts_designer, form_designer, queue_admin, and queue_advance_processor roles. This user account is required for your initial TaskSpace login. (After your initial TaskSpace login, you can create additional users, groups, and roles in the TaskSpace Administration tab to meet your needs.) Installing the Tutorial Sample DocApp A sample TaskSpace application is provided to help you become familiar with TaskSpace functionality. You install this application using a Documentum DocApp, which is an archived collection of Documentum Content Server objects. Install the Tutorial Sample DocApp in the global repository, and once in each EMC Documentum repository in which any user needs to explore the sample application. 24 EMC Documentum TaskSpace Version 6 Deployment Guide

25 Preparing Requirements Speci c to TaskSpace Install the DocApp from any computer with the latest version of Documentum Application Installer on the local computer. (Documentum TaskSpace Release Notes contains specific version requirements.) If Documentum Application Installer is not installed on the local computer, download and install it before running the procedure below. You must have the EMC Documentum administrator or superuser privilege level to install a DocApp using Documentum Application Installer (DAI). To install the Tutorial Sample DocApp: 1. In Documentum Administrator, create a user named dmadmin. Documentum Administrator creates a directory for this user. This directory is required for a successful DocApp installation. Also add this user as a member of the ts_designer, form_designer, queue_admin, and queue_advance_processor roles, so that you can log in to the sample application later. For instructions, refer to the Documentum Administrator User Guide. 2. Download the Tutorial Sample DocApp from the following location, under the product name TaskSpace: Note: The Powerlink website provides access to subscribenet.com/ control/dctm/index where a complete listing of products is available for download. 3. Unzip the downloaded file TaskSpace_Sample_DocApp_6.0.zip. The files comprising the DocApp are extracted into a subdirectory named mailmanager_samp. 4. From the Start menu, select Programs > Documentum > Application Installer. The login screen for Documentum Application Installer appears. 5. Select the EMC Documentum repository into which you want to install the DocApp and log in as a user with the EMC Documentum superuser or administrator privilege level. Documentum Application Installer starts. EMC Documentum TaskSpace Version 6 Deployment Guide 25

26 Preparing Requirements Speci c to TaskSpace 6. Click Browse from the DocApp folder selection section and navigate to the TaskSpace directory containing the DocApp files (from step 2). 7. (Optional) In the Installer Log section, type a log filename in the File name box. The default log filename is mailmanager_samp_installerlog.html. Click Browse to select a directory other than the default to save the log file. You can refer to the log file for any errors that occur during the installation of DocApp. 8. Click OK. A dialog box appears detailing the DocApp name, target repository, and the installation status. 9. Click Start Installation. A message appears indicating the installation process takes a few minutes to complete. 10. Click OK. If users are currently connected to the EMC Documentum repository into which you are installing the DocApp, a message appears asking whether you want to continue with the installation. Click Yes. Users are not affected by the installation, but they will not see the changes made by the DocApp until they reconnect. 26 EMC Documentum TaskSpace Version 6 Deployment Guide

27 Preparing Requirements Speci c to TaskSpace 11. Repeat steps 3 through 9 for each EMC Documentum repository in which you plan to use TaskSpace. 12. Click Quit Installer. After you have used this application to explore TaskSpace functionality, consider recreating this sample application for practice before you start creating your own applications. For instructions, refer to the Documentum TaskSpace Sample Application Tutorial. EMC Documentum TaskSpace Version 6 Deployment Guide 27

28 Preparing Requirements Speci c to TaskSpace 28 EMC Documentum TaskSpace Version 6 Deployment Guide

29 Chapter 4 Preparing the Client Hosts This chapter contains instructions that are shared by all WDK-based products. Check your release notes for information on the browsers that are certified for your product. This chapter contains information on the following predeployment tasks: Ensuring a certified JVM on browser clients, page 29 Enabling HTTP content transfer in Internet Explorer 7, page 30 Enabling UCF content transfer in Internet Explorer 7 on Windows Vista, page 30 Enabling content transfer in Firefox 2, page 31 Clearing the browser cache, page 32 Supporting Outlook mail message archives, page 32 Using Citrix Presentation Server Client, page 32 Ensuring a certi ed JVM on browser clients Browser client hosts require a certified version of the Sun Java virtual machine (JVM) to initiate content transfer in a WDK application. New machines may not have a VM installed in the browser. Check the release notes for your product version for the JVMs that are supported. If the WDK-based application is configured to use UCF content transfer, a lightweight applet is downloaded to the browser when the client makes the first content transfer or preferences request. If the JVM required for UCF is not present on the client machine, UCF uploads to the client a private JVM. This VM does not replace the JVM that is used by the browser. Since the UCF VM file (Sun JRE) is over 10 MB in size, the installation can cause a delay. You can avoid this delay by installing a compatible local JVM prior to using UCF transfer. EMC Documentum TaskSpace Version 6 Deployment Guide 29

30 Preparing the Client Hosts Enabling HTTP content transfer in Internet Explorer 7 Internet Explorer (IE) version 7 has a default security setting that prevents the display of the file download dialog. You must add the WDK-based application URL to the list of trusted sites in the browser in order to perform checkout, view, or edit in HTTP mode. Nothing happens when user exports as CSV if the browser security settings is disabled for prompt for file downloads and file download. These are disabled by default in IE7. The user must enable them. To enable HTTP le download in IE 7 1. In the IE 7 browser menu, choose Tools Internet Options and click the Security tab. 2. Choose Trusted sites and then click Custom level. 3. Scroll to the Downloads section and enable Automatic prompting for file downloads. 4. Click OK twice to save settings. 5. Close all browser windows and restart the browser. Enabling UCF content transfer in Internet Explorer 7 on Windows Vista Internet Explorer 7 on Windows Vista OS does not display a file download dialog to permit UCF content transfer unless it is enabled by adding the application server host to the trusted sites list and doing one of the following: Turn off User Account Control (UAC) security for each client. Configure the application to use file registry mode. To add the application server host to the list 1. In IE7, go to Tools Internet Options Security tab. 2. Select Trusted sites. Click Custom level in the section Security level for this zone. 3. Scroll to Downloads and check Automatic prompting for file downloads. 4. Click OK to accept changes, and close the browser. To turn off UAC on each client 1. Log in as a user who has administrator privileges on the Windows Vista machine. 30 EMC Documentum TaskSpace Version 6 Deployment Guide

31 Preparing the Client Hosts 2. Open the Control panel and choose Administrative Tools. 3. In the left pane, choose User Accounts. 4. Choose Turn User Account Control on or off. 5. Uncheck Use User Account Control (UAC) to help protect your computer. 6. Click OK and restart the system. To con gure UCF to use le registry mode 1. Ensure the clients have checked in all checked out files. 2. Open the file ucf.installer.config.xml located in WDK-based applications directory /wdk/contentxfer. 3. Locate the element <platform os="windows" arch="x86">, which configures Windows clients. 4. Locate the child element <defaults>.<configuration name="com.documentum.ucf">. <option name="registry.mode">. 5. Change the value element to the following: <value>file</value> 6. Save and restart the application. Enabling content transfer in Firefox 2 Firefox 2 requires a setting to enable content transfer. To enable le download in Firefox 1. Open the Options menu in Firefox. 2. In the Main dialog Downloads section, enable Show the Downloads window when downloading a file and Close it when all downloads are finished. 3. Check Always ask me where to save files. 4. On the Tabs dialog, check New pages should be opened in: a new window. 5. On the Content dialog, check Load images automatically, Enable JavaSript, and Enable Java. 6. Install the Firefox add-on FireBug, which is available from mozilla.org. EMC Documentum TaskSpace Version 6 Deployment Guide 31

32 Preparing the Client Hosts Clearing the browser cache Browsers cache JavaScript. Cached JavaScript in the browser from a 5.x WDK-based application may cause errors when the user connects to a version 6 application. Clear the browser JavaScript cache to avoid these errors. Supporting Outlook mail message archives WDK supports viewing and exporting dm_message_archive objects. If your WDK-based product displays Outlook mail messages, read these instructions. The objects can be viewed as HTML or as.msg files in Outlook. To view or export dm_message_archive objects as.msg files, the client must download and install a converter. This converter can be automatically installed as part of the UCF download. To enable automatic download, uncomment the ExMRE.exe section in the app\wdk\contentxfer\ucf.installer.config.xml file on the application server. The converter can take a long time to download and install. You can avoid the delay by deploying the ExMRE.exe installer using standard mechanisms such as Microsoft Systems Management Server (SMS). Using Citrix Presentation Server Client Citrix Presentation Server Client can be used as a web browser. Check the release notes for your WDK-based product to determine whether Citrix clients are supported for your product. In the Citrix environment, content files are exported or checked out to the Presentation Server host, not to individual client hosts. Each individual user works on a client host with an image of a web browser that is running on the Presentation Server host. For detailed information on enabling applications on Presentation Server, refer to documentation provided by Citrix. Note: If you have previously attempted to content transfer to the client, it will use the client s location machine, and you must delete the ucf directory that was installed on the local client machine under the user s OS home directory, for example, C:\Documents and Settings\pradeep\Documentum\ucf. 32 EMC Documentum TaskSpace Version 6 Deployment Guide

33 Preparing the Client Hosts Turning off the pop-up blocker in Internet Explorer Windows XP SP2 installs a pop-up blocker in Internet Explorer that is enabled by default. HTTP content transfer operations in WDK applications are prevented by the pop-up blocker. You must turn off the pop-up blocker for HTTP transfer. EMC Documentum TaskSpace Version 6 Deployment Guide 33

34 Preparing the Client Hosts 34 EMC Documentum TaskSpace Version 6 Deployment Guide

35 Chapter 5 Preparing the Application Server Host This chapter contains instructions that are shared by all WDK-based products. Check your release notes for information on the application servers that are certified for your product. This chapter describes the tasks you must complete to prepare the application server host before deploying your WDK-based application. Before you deploy a WDK-based application, ensure that your J2EE application server or servlet container is a supported version and that it can successfully serve sample JSP pages. Tip: EMC recommends but does not require that you uninstall DFC 5.x and any application that uses DFC 5.x and then reboot before deploying an application based on WDK 6. For uninstall procedures, refer to the 5.x product documentation. This chapter contains the following sections. Your selected application server and optional external web server must be certified for your product. Setting the Java memory allocation, page 36 Required information for all application servers Preparing environment variables for non-default DFC locations, page 36 Information for enterprise environments that do not use the default (recommended) DFC environment locations. Preparing Apache Tomcat, page 37 Preparing BEA WebLogic, page 37 Preparing IBM WebSphere, page 38 Preparing Oracle Application Server, page 40 Preparing Sun Java System Application Server, page 41 Preparing to use an external web server, page 42 EMC does not provide support for installing or running application servers. Refer to the documentation for each application server for instructions on installing, stopping, starting, and running the application server. Contact the application server vendor for technical support. EMC Documentum TaskSpace Version 6 Deployment Guide 35

36 Preparing the Application Server Host Setting the Java memory allocation The minimum recommended Sun Java memory allocation values for application servers on a small system are the following: -Xms1024m -Xmx1024m Application servers can slow down, throw exceptions, or crash with an application that has a large number of Java Server Pages. Set the MaxPermSize parameter to 128 or higher to avoid this problem. Document caching can consume at least 80 MB of memory. User session caching can consume approximately 2.5 MB to 3 MB per user. Fifty connected users can consume over 200 MB of VM memory on the application server. Increase the values to meet the demands of the expected user load. For more information on these settings, refer to Java documentation at the Sun web site ( More information on application server performance tuning and benchmarking for Documentum products is available from your EMC Documentum SE or EMC Documentum Consulting. Preparing environment variables for non-default DFC locations The base location for content transfer on the application server host is specified by the DFC environment variable dfc.data.dir. This location is specified as the value of the key dfc.data.dir in dfc.properties located within the application WAR file in WEB-INF/classes. If this variable is not set in the environment for the application server, the default location is the documentum subdirectory of the current working directory. (The current working directory contains the application server executable.) For example, in Tomcat the location is %CATALINA_HOME%/bin. On WebLogic, it is BEA, it is %BEA_HOME%/domains/wl_server/documentum. By default, the checkout and export directories are subdirectories of the dfc.data.dir directory, and the user directory is the same as dfc.data.dir. If you wish to use non-default locations for these, you can create environment variables for dfc.checkout.dir, dfc.export.dir, and dfc.user.dir, respectively. The default value of dfc.registry.mode, which corresponds to the key dfc.registry.mode in dfc.properties, is "file". The full path to this file by default is dfc.user.dir/documentum.ini. For a non-default file name or location, specify it as the value of the environment variable dfc.registry.file. 36 EMC Documentum TaskSpace Version 6 Deployment Guide

37 Preparing the Application Server Host Preparing Apache Tomcat Please refer to your product release notes to determine whether Apache Tomcat is a supported application server for your product. You must disable tag reuse in Apache Tomcat in the web.xml file of the Tomcat /conf directory. Find the JSP servlet entry in web.xml. Add the enablepooling initialization parameter and set it to false: <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.jspservlet</servlet-class> <init-param> <param-name>enablepooling</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>fork</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>xpoweredby</param-name> <param-value>false</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> Preparing BEA WebLogic Please refer to your product release notes to determine whether BEA WebLogic is a supported application server for your product. The following topic describes preparations that may be necessary before you deploy a WDK-based application. Supporting large content transfer operations in a managed server environment If you are deploying in a WebLogic Managed Server environment and you use UCF to perform large content operations, set the WLIOTimeoutSecs parameter for the web server plugin to a very large value. UCF requires a sticky session for a single operation. For additional details, refer to BEA s documentation on Web Serve Plug-ins parameters. EMC Documentum TaskSpace Version 6 Deployment Guide 37

38 Preparing the Application Server Host Preparing IBM WebSphere IBM WebSphere is a supported application server for TaskSpace. The following topics describe how to prepare IBM WebSphere for use with TaskSpace. Applying policies for WebSphere security If WebSphere global security is enabled for the application server, by default it enables Java 2 security. Java 2 security requires security policies. You must apply the policies in the Documentum files app.policy, library.policy and was.policy. These files are provided by EMC Documentum on the download site in the compressed archive PolicyFiles.zip. These files contain the minimum set of policies that are required for the application to run without error. Add these policies to your existing files. You must set up the environment variables that are referenced in these policies, and the application server instance owner must have write permission on these directories. Define the following environment variables: dfc.data.dir By default, the dfc.data.dir directory is the documentum subdirectory of the directory that contains the application server executable. webtop.content.xfer Specifies the temporary content transfer directory on the application server. Must match the value in app.xml of the element <contentxfer>.<server>. <contentlocationwindows> or <contentlocationunix>. The policy files in PolicyFiles.zip contain the minimum required policies for the dfc.data.dir directory. To add additional policies for non-default content transfer locations, add the following lines to library.policy. For each policy that you add, set up an environment variable that specifies the non-default location. Tip: Select only the policies that are needed for your application. Policy for local user directory (non-default location) This policy is required if the user directory for the application server host machine is a non-default location. The default location is the same as the location specified by the dfc.properties key dfc.data.dir. permission java.io.filepermission "${dfc.user}${/}-", "read, write, delete"; permission java.io.filepermission "${dfc.user}", "read, write, delete"; Policy for checkout and export directories (non-default location) These environment variables must specify the same location as the value of the dfc.properties keys dfc.checkout.dir and dfc.export.dir. The default locations for these directories are checkout and export subdirectories of dfc.data.dir. 38 EMC Documentum TaskSpace Version 6 Deployment Guide

39 Preparing the Application Server Host permission java.io.filepermission "${dfc.checkout}${/}-", "read, write, delete"; permission java.io.filepermission "${dfc.checkout}", "read, write, delete"; permission java.io.filepermission "${dfc.export}${/}-", "read, write, delete"; permission java.io.filepermission "${dfc.export}", "read, write, delete"; Policy for DFC registry file (non-default location) The value of the dfc.registry environment variable must match the location specified in dfc.properties for the key dfc.registry.file. permission java.io.filepermission "${dfc.registry}${/}-", "read, write, delete"; permission java.io.filepermission "${dfc.registry}", "read, write, delete"; Policy for Webtop temporary content transfer directory (non-default location) permission java.io.filepermission "${webtop.content.xfer}${/}-", "read, write, delete"; permission java.io.filepermission "${webtop.content.xfer}", "read, write, delete"; Policy for non-webtop WDK-based temporary content transfer (non-default location) You can use this policy for TaskSpace or other application that is not based on Webtop: permission java.io.filepermission "${wdk.content.xfer}${/}-", "read, write, delete"; permission java.io.filepermission "${wdk.content.xfer}", "read, write, delete"; Policy for documentum applications directory (non-default location) The default location is dfc.data.dir. permission java.io.filepermission "${documentum}${/}-", "read, write, delete"; permission java.io.filepermission "${documentum}", "read, write, delete"; Policy for DFC class cache directory (non-default location) The default location is dfc.data.dir/cache. permission java.io.filepermission "${dfc.cache.dir}${/}-", "read, write, delete"; permission java.io.filepermission "${dfc.cache.dir}", "read, write, delete"; Policy for Web Publisher permission java.io.filepermission "${wp.content.xfer}${/}-", "read, write, delete"; permission java.io.filepermission "${wp.content.xfer}", "read, write, delete"; Policy for Documentum Administrator permission java.io.filepermission "${da.content.xfer}${/}-", "read, write, delete"; permission java.io.filepermission "${da.content.xfer}", "read, write, delete"; Policy for Digital Asset Manager permission java.io.filepermission "${dam.content.xfer}${/}-", "read, write, delete"; permission java.io.filepermission "${dam.content.xfer}", "read, write, delete"; EMC Documentum TaskSpace Version 6 Deployment Guide 39

40 Preparing the Application Server Host Policy for Content Intelligence Services permission java.io.filepermission "${cis.content.xfer}${/}-", "read, write, delete"; permission java.io.filepermission "${cis.content.xfer}", "read, write, delete"; Supporting non-default content transfer locations If you want to use non-default locations for content transfer, you must create custom JVM properties using the WebSphere administration console. Create a JVM custom property named dfc.data to reflect the path to the location. The value must match the value of dfc.data.dir in dfc.properties. Table 4, page 40 shows the custom properties you must create each DFC output directory that is not the default location. Table 4. Output directories and JVM custom properties DFC output directory key dfc.data.dir dfc.user.dir dfc.checkout.dir dfc.export.dir dfc.registry.file JVM custom property name dfc.data dfc.user dfc.checkout dfc.export dfc.registry For dfc.registry, type the path to the parent directory of the file. Refer to the documentation for WebSphere for information on modifying JVM custom properties. Preparing Oracle Application Server Please refer to your product release notes to determine whether Oracle Application Server is a supported application server for your product. You must disable tag reuse for the application server. To disable tag pooling for the application 1. Open orion-web.xml. 2. Change the default value of the <init-param> tags_reuse_default from compiletime to the value none as shown in the following example: <servlet> <servlet-name>jsp</servlet-name> <servlet-class>oracle.jsp.runtimev2.jspservlet</servlet-class> <init-param> 40 EMC Documentum TaskSpace Version 6 Deployment Guide

41 Preparing the Application Server Host <param-name>tags_reuse_default</param-name> <param-value>none</param-value> </init-param> </servlet> To disable tag pooling for all applications 1. Open global-web-application.xml in < ORACLE_HOME >\j2ee\home\config 2. Add the following init-param in the <servlet> element: <servlet> <init-param> <param-name>tags_reuse_default</param-name> <param-value>none</param-value> </init-param> </servlet> Preparing Sun Java System Application Server Please refer to your product release notes to determine whether Sun Java System Application Server is a supported application server for your product. The following topics describe preparations to deploy a WDK-based application. Turning off tag pooling You must turn off tag pooling for the domain in which you deploy WDK-based applications. For the domain in which you will deploy the application, open default-web.xml, for example, install path/domains/domain1/config/default-web.xml Add the following <init-param> to the jsp servlet declaration as follows <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.jspservl <init-param> <param-name>xpoweredby</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>enablepooling</param-name> <param-value>false</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> EMC Documentum TaskSpace Version 6 Deployment Guide 41