EMC Documentum CenterStage

Transcription

1 EMC Documentum CenterStage Version 1.2 Installation Guide EMC Corporation Corporate Headquarters: Hopkinton, MA

2 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. Copyright 2012 EMC Corporation. All rights reserved.

3 Table of Contents Preface... 9 Chapter 1 Overview CenterStage system components Content Server Composer Documentum Administrator Transformation Services Federated Search Services Content Intelligence Services Full-text Indexing Application server CenterStage CenterStage DARs CenterStage WAR CenterStage EAR Planning the deployment Chapter 2 Preparation Installation requirements Use fully qualified domain names Secure Sockets Layer (SSL) Review troubleshooting notes Chapter 3 Deploying the CenterStage System Deploying Content Server Deploying Content Transformation Services Deploying Federated Search Services Configuring the connection to the search server Configuring the connection to the backup search server Installing Federated Search Services (FS2) Indexer for shared drives Deploying Full-text Indexing Services Deploying Content Intelligence Services (CIS) Deploying Composer Deploying the application server WebSphere Replace missing class in WebSphere Modify the web.xml file Configure Java options for WebSphere Enable webcontainer filter compatibility JBoss Tomcat Oracle Servers (WebLogic) Deploying CenterStage EMC Documentum CenterStage 1.2 Installation Guide 3

4 Table of Contents Deploying CenterStage DAR files Installing a DAR file with the DAR Installer Deploying CenterStage DARs using an Ant Task Customizing the product name in the application URL Deploying CenterStage WAR files Deploying CenterStage EAR files Deploying the EAR file to Oracle WebLogic Preparing the EAR file Updating the server JDK Installing the EAR file Deploying the EAR file to IBM WebSphere x Installing xplore Security and external access Installing CenterStage with a proxy server Branch office Central office Chapter 4 Upgrading CenterStage Backing up app.xml Backing up custom configuration files Reinstalling custom DARs Upgrading from CenterStage 1.x to CenterStage Running UpgradeCenterStage1_ Upgrading folder permissions from 1.1 to Chapter 5 Configuration Update paths for log4j appender Access Documentum Administrator Set up CenterStage indexes Create a user in the repository Enable notification for subscribed content Assign members to the dce_room_creator role Assign members to the dmc_kw_manage_space_templates role Configure the administrator address Configure the embedded Content Server for SMTP Configure Retention Policy Services (optional) Access CenterStage Create a space Configure the content policy for each space Installing DARs with a localized data dictionary Populating a localized CenterStage data dictionary Configuring high-availability Linux random number daemon configuration Configuring CenterStage to enable Kerberos authentication Configuring CenterStage for RSA authentication Configuring RSA Access Manager Web Agent to use an authorization dialog Configuring CenterStage for Netegrity authentication Configuring single sign-on with a reverse proxy server EMC Documentum CenterStage 1.2 Installation Guide

5 Table of Contents Chapter 6 Troubleshooting Disable the Windows 2008 firewall on user machines Troubleshooting CIS Validate the installation of cis_artifacts.dar Verify the required table has been created Test the entity extraction Configuring WebLogic security Optimizing performance Performance settings for Oracle repository Performance settings for MS SQL repository Delay when installing with existing DCS data tables Appendix A Test file for CIS entity extraction: EuropeanUnion.doc Appendix B Configuring HTTP compression Configuring HTTP compression on the web server Enabling HTTP compression on the Apache web server Enabling HTTP compression on the Apache Tomcat server Enabling HTTP compression on the RedHat JBoss server Enabling compression on the Oracle WebLogic server Enabling compression on the IBM WebSphere 7 application server EMC Documentum CenterStage 1.2 Installation Guide 5

6 Table of Contents List of Figures Figure 1. Branch Office configuration Figure 2. LAN settings Figure 3. BOCS configuration Figure 4. Documentum Administrator BOCS configuration settings Figure 5. HTTP Post method with BOCS read operation Figure 6. Central Office Figure 7. Proxy directives Figure 8. DMS proxy directives Figure 9. BOCS acs.properties definition Figure 10. Proxy URL setting in dms.properties Figure 11. ACS write operation Figure 12. Reverse proxy access log Figure 13. Example code snippet from the authentication element in app.xml Figure 14. sso_config element in app.xml for RSA authentication Figure 15. sso_config element in app.xml for Netegrity authentication EMC Documentum CenterStage 1.2 Installation Guide

7 Table of Contents List of Tables Table 1. DAR installer fields Table 2. Directories containing shared object files EMC Documentum CenterStage 1.2 Installation Guide 7

8 Table of Contents 8 EMC Documentum CenterStage 1.2 Installation Guide

9 Preface This manual describes how to install CenterStage. For information about known issues and limitations, refer to CenterStage Release Notes. For information about using CenterStage, refer to the online help. Intended audience This manual is for system administrators, developers, and evaluators who are installing or upgrading the CenterStage application. Revision history The following changes have been made to this document. Revision Date March 2011 September 2012 Description Initial publication Added a new Appendix chapter called "Configuring HTTP compression. EMC Documentum CenterStage 1.2 Installation Guide 9

10 Preface 10 EMC Documentum CenterStage 1.2 Installation Guide

11 Overview Chapter 1 This guide provides instructions for installing CenterStage application files. It is also an umbrella document that provides references to the specific documentation for the applications that comprise the CenterStage system. The goal is to gather much of the information required to install and configure the system in a convenient format. CenterStage system components This section provides brief descriptions of the applications that comprise the CenterStage system. Content Server Content Server provides basic content management functionality, including check out, check in, and version control capabilities. For more information on Content Server, see the Content Server Installation Guide, Chapter 1, Planning for Content Server Installation. Composer Documentum Composer is used to deploy the Documentum Archives (DARs) that provide supporting services and the CenterStage application files. For more information on Documentum Composer, see Documentum Composer Release Notes, Chapter 1, Product Description. Documentum Administrator Documentum Administrator can be used to create users and assign them permissions necessary to create CenterStage spaces and perform other privileged activities. For more information on Documentum Administrator, see the Documentum Administrator User Guide. EMC Documentum CenterStage 1.2 Installation Guide 11

12 Overview Transformation Services Thumbnail Generator creates single page thumbnails (300x300 pixels in size) for images, PDF, and Office documents. The generated thumbnails are used in various parts of the application to provide previews of content. CenterStage provides inline viewers that display the first page of a document with thumbnail generator. CenterStage can provide full document viewing capabilities after an upgrade to MTS (Media Transformation Services)/ADTS (Advanced Document Transformation Services). For more information, see Content Transformation Services for CenterStage Installation and Configuration Guide, About Content Transformation Services Products. Federated Search Services Federated Search Services (FS2) lets users search across multiple sources and aggregate the results of those searches. CenterStage also provides search adapters for Documentum ECM; eroom; ApplicationXtender; Xtender; ODBC/JDBC; Google.com; Google Desktop Enterprise; OpenDirectory; Yahoo Directory; OpenSearch; Wikipedia; Windows Search; and FS2 Indexer. Additional add-on adapters can be purchased separately. For more information on Federated Search Services, see Federated Search Services Installation Guide, Chapter 1, Preinstallation Tasks. Content Intelligence Services Content Intelligence Services (CIS) uses data mining for extraction of company names, locations, and people. Cartridges provide definitions for particular extraction domains (for example, locations). When users search for a particular location, the cartridge enables the search to infer the country, state, county, city, etc. This provides more reliable search results, even if the criteria entered are not precise matches. For more information on Content Intelligence Services, see Content Intelligence Services Installation Guide, Introduction. Full-text Indexing Full-text indexing enables rapid search on all text in the CenterStage repository. Full-text indexing options are described in the Documentum Content Server Full-Text Indexing Deployment Guide. 12 EMC Documentum CenterStage 1.2 Installation Guide

13 Overview Application server The application server is part of the operating environment for CenterStage. It is a third-party web server such as Apache Tomcat or Red Hat JBoss that enables access to the CenterStage application through a web browser. CenterStage The CenterStage application itself is deployed as Documentum Archives (DARs) to the repository, and Web Archives (WARs) or Enterprise Archives (EARs) to the application server. CenterStage DARs CenterStage DARs are deployed on the Content Server repository and contain the business logic for CenterStage. Certain DARs must also be installed on the Global repository. For DAR file instructions, see Deploying CenterStage DAR files, page 22. CenterStage WAR The CenterStage WAR file is deployed on the application server and provides the UI elements for the web application. Deploy the WAR on the following application servers: Apache Tomcat Oracle Application Server Oracle WebLogic Server 10g R3( ) Red Hat JBoss For WAR file instructions, see Deploying CenterStage WAR files, page 26. CenterStage EAR The CenterStage EAR file is deployed on the application server and provides the UI elements for the web application. Deploy the EAR file on the following application servers: IBM WebSphere x Oracle WebLogic Server (11g R1) For EAR file instructions, see Deploying CenterStage EAR files, page 26. EMC Documentum CenterStage 1.2 Installation Guide 13

14 Overview Planning the deployment CenterStage runs on a standard Documentum Content Server system. The performance and sizing considerations for CenterStage are described in the CenterStage System Planning Guide. 14 EMC Documentum CenterStage 1.2 Installation Guide

15 Preparation Chapter 2 CenterStage provides the primary user interfaces for cross-department and/or company collaboration, and data sharing through communities, spaces, wikis, blogs, data tables, and RSS feeds. CenterStage is deployed into an application server instance and accessed by end users through a browser. CenterStage runs in a multiple-host environment to ensure optimal performance. In this scenario, CenterStage is deployed by installing Documentum Archive (DAR) files on an existing Content Server instance (or one created specifically to host CenterStage). This chapter gives pre-installation information and describes pre-installation tasks. For an overview of the CenterStage system and in-depth discussion of how to plan your deployment, see the CenterStage System Planning Guide. For complete system requirements, see the chapter Environment and System Requirements in CenterStage Release Notes. Installation requirements Your installation must follow these requirements: The name of the machine on which to install the software must begin with an alphabetic character. If the NetBIOS name of the machine begins with a numeric instead of an alphabetic character, the installation will fail. The physical or virtual server used for the installation must be dedicated to the CenterStage application. An SMTP server must be installed and available before you install CenterStage. The SMTP server can be on the CenterStage host or a remote host. After the installation procedure, you must use Documentum Administrator to configure CenterStage to use the name or IP address of the computer hosting the SMTP server so that CenterStage can connect to it. Use fully qualified domain names DNS lookups can be quite costly in terms of performance. To avoid lengthy lookups, use fully qualified path names when configuring the CenterStage server. EMC Documentum CenterStage 1.2 Installation Guide 15

16 Preparation Secure Sockets Layer (SSL) By default, SSL is not enabled in CenterStage. Over HTTP, passwords are sent in clear text when SSL is not enabled. EMC recommends that customers enable SSL to provide secure transmission of sensitive data such as authentication credentials. For more information, see the EMC Documentum Documentum Administrator User Guide, Managing User Authentication. Review troubleshooting notes Before you install, review Chapter 6, Troubleshooting. 16 EMC Documentum CenterStage 1.2 Installation Guide

17 Chapter 3 Deploying the CenterStage System This section of the manual provides references to the specific manuals for installing each element in the CenterStage system, with commentary on any special considerations when you are installing the product to work well with CenterStage. Deploying Content Server To install Content Server, follow the instructions in Content Server Installation Guide, Chapter 1, Planning for Content Server Installation. Deploying Content Transformation Services Thumbnail Generator is used to create thumbnail views of documents in CenterStage. CenterStage is also compatible with Media Transformation Services and Advanced Document Transformation Services for enhanced capabilities. To install Content Transformation Services, see the Content Transformation Services for CenterStage Installation and Configuration Guide. Deploying Federated Search Services To deploy Federated Search Services (FS2), follow the instructions starting with Federated Search Services Installation Guide, Chapter 1, Preinstallation Tasks. To allow users to search external sources, an administrator must configure a connection to a Federated Search server. EMC Documentum CenterStage 1.2 Installation Guide 17

18 Deploying the CenterStage System Configuring the connection to the search server The following procedure describes how to enable the Federated Search server to query external sources. The Federated Search documentation provides more information about how to configure the Federated Search server itself. To configure the connection to a Federated Search server: 1. Unpack the client application WAR file. 2. Open the file dfc.properties in WEB-INF/classes. 3. Enable the Federated Search server by setting the following: dfc.search.ecis.enable=true 4. Specify the RMI Registry host for the Federated Search server by setting the following: dfc.search.ecis.host=host_ip dfc.search.ecis.port=port Where host_ip is IP address or machine name of the Federated Search server port is the port number that accesses the Federated Search server. The default port is Configuring the connection to the backup search server You can set a backup server in case the primary Federated Search server is unreachable. If a DFC application cannot connect to the primary Federated Search server to query external sources, the backup server is used. You can define the time period after which the application will try to connect again to the primary server. To define the backup server, specify the RMI host and port in the dfc.properties file: dfc.search.external_sources.backup.host : host of the backup Federated Search server. Default value is localhost dfc.search.external_sources.backup.port : port of the backup Federated Search server. Default value is dfc.search.external_sources.retry.period : waiting period before retrying to connect to the primary Federated Search server. This time is in milliseconds. Default value is Installing Federated Search Services (FS2) Indexer for shared drives To index and search shared (network) drives as part of the federated search experience in CenterStage, you must install FS2 Indexer. The installation files for this option are available in the Download Center under the FS2 product line, as part of the archive file for Windows operating systems. The installation procedure is described in the Federated Search Services Installation Guide. 18 EMC Documentum CenterStage 1.2 Installation Guide

19 Deploying the CenterStage System Deploying Full-text Indexing Services EMC Documentum recommends that you use xplore full-text indexing services for improved performance. If you choose to do so, you need to install xplore after you deploy CenterStage. See Installing xplore, page 27 for more information. If you choose to deploy Documentum Content Server Full-text Indexing Services (FAST), the installation should take place at this point in the stack. Follow the instructions in the Full-Text Indexing System Installation and Administration Guide, Chapter 2, Prepare for Installation. Deploying Content Intelligence Services (CIS) To deploy Content Intelligence Services, follow the instructions in the Content Intelligence Services Installation Guide. Deploying Composer To deploy Documentum Composer, follow the instructions in the Documentum Composer Release Notes, Chapter 9, Installation. Deploying the application server Follow the instructions provided by the vendor of your supported application server of choice. After deploying the application server, you need to update the dfc.properties file to access the repository. To update the dfc.properties file for your application server: 1. Unpack the client application WAR (or EAR) file. 2. Open the file dfc.properties in WEB-INF/classes. 3. Enter the correct values for the following properties: dfc.docbroker.host[0] dfc.docbroker.port[0] dfc.globalregistry.repository dfc.globalregistry.username dfc.globalregistry.password 4. Save the dfc.properties file. 5. Restart the application server. EMC Documentum CenterStage 1.2 Installation Guide 19

20 Deploying the CenterStage System The sections that follow provide specific installation and configuration information for supported application servers. WebSphere IBM WebSphere is a third-party product. For installation information, visit the IBM web site. At the time this guide is being written, the correct link to product documentation is For information on load balancing for IBM WebSphere, see docview.wss?rs=180&uid=swg After installing WebSphere, you deploy CenterStage as follows: 1. Replace missing class in WebSphere, page Modify the web.xml file, page Configure Java options for WebSphere, page Enable webcontainer filter compatibility, page Deploy the EAR file Replace missing class in WebSphere Due to an incompatibility in the bundled JAR files in WebSphere version , users may encounter parsing errors when saving page objects. To prevent these errors, perform the following workaround before deploying the CenterStage application: 1. Obtain a copy of xalan.jar, as follows: 2. Go to the JAXP website: &expandfolder=4584&folderID= From the JAXP 1.3.x directory, download JAXP Stand-alone. 4. After downloading, run java -cp JAXP_RI_ , which unpacks JAXP into./jaxp_ri_ Locate the xalan.jar file in the JAXP_RI_ directory after extraction. 6. Copy xalan.jar to <CenterstagePro.ear>\APP-INF\libif. 7. Clear the application server cache. 8. Restart the server. Modify the web.xml file The web.xml file as shipped: 20 EMC Documentum CenterStage 1.2 Installation Guide

21 Deploying the CenterStage System <web-app xmlns:j2ee=" xmlns:xsi=" xsi:schemalocation=" The web.xml file updated for WebSphere application server (changes in bold text): <web-app xmlns:j2ee=" xmlns:xsi=" xsi:schemalocation=" metadata-complete="true"> Configure Java options for WebSphere IBM WebSphere does not recognize the JAVA_OPTS variable used by CenterStage for application server configuration. Three variables need to be set using the WebSphere Administration Console. To configure Java options for WebSphere: 1. Open the WebSphere Administration Console. 2. Navigate to Java Virtual Machine Custom Properties panel. For example, Application servers > server_name > Process definition > Java Virtual Machine > Custom Properties 3. Click New. 4. Set the name of the new property to javax.xml.stream.xmlinputfactory. 5. Set the value of the new property to com.sun.xml.stream.zephyrparserfactory 6. Click OK. Enable webcontainer filter compatibility This is a workaround for a known bug in the WebSphere server. To specify the Web container custom property: 1. In the administrative console choose Servers > Application Servers > server_name > Web Container settings > Web Container 2. Under Additional Properties select Custom Properties. 3. On the Custom Properties page, click New. 4. On the settings page, enter the name of the custom property: "com.ibm.ws.webcontainer. invokefilterscompatibility" 5. Set the value of the property to true. 6. Click Apply or OK. 7. Click Save on the console task bar to save your configuration changes. 8. Restart the server. EMC Documentum CenterStage 1.2 Installation Guide 21

22 Deploying the CenterStage System JBoss Red Hat JBoss is a third-party product. For installation information, visit the Red Hat web site. At the time this guide is being written, the link to the installation guide is For an example of load balancing for Red Hat JBoss, see Tomcat Apache Tomcat is an open source product. For installation information, visit the Apache Software Foundation web site. At the time this guide is being written, the link to the setup instructions is For a discussion of load balancing for Apache Tomcat, see generic_howto/loadbalancers.html. Oracle Servers (WebLogic) CenterStage supports third-party application servers from Oracle. You can find documentation for all Oracle products on the Oracle Technology Network website at Deploying CenterStage After completing the tasks outlined in Deploying the application server, page 19, continue with your CenterStage deployment by following these instructions: Deploying CenterStage DAR files, page 22 Deploying CenterStage WAR files, page 26 Deploying CenterStage EAR files, page 26 Deploying CenterStage DAR files When deploying CenterStage, you deploy discrete elements of the application on two or more servers. This chapter covers the specific steps for deploying Documentum Archive (DAR) files to the repositories required for CenterStage. The following DARs need to be installed in the order listed: Collaboration Services.dar DCS Attachments.dar CenterStage.dar 22 EMC Documentum CenterStage 1.2 Installation Guide

23 Deploying the CenterStage System CenterStagePro.dar CenterStageDatatable.dar CenterStageTemplates.dar Extended_Search-Clustering.dar Rich_Media_Services.dar Transformation.dar cis_artifacts.dar Install all DAR files on the global repository and any working CenterStage repository. DARs can be deployed using any of the methods described in the Documentum Composer User Guide. For convenience, the following are specific examples for deploying the necessary DARs for CenterStage. Two options are available for deploying DAR files: Installing a DAR file with the DAR Installer, page 23 (recommended) Deploying CenterStage DARs using an Ant Task, page 25 Installing a DAR file with the DAR Installer You can use the DAR Installer to install the CenterStage DAR files to a repository if you do not want to use the interface within Composer. The DAR Installer requires Composer to be installed, but does not launch the full Composer IDE. When you open the DAR Installer, it creates three folders in your Composer installation directory: darinstallerconfig contains configuration files for the DAR Installer Plugin darinstallerlogs the default location of the log files darinstallerworkspaces workspaces that are created and used by the DAR Installer Plugin. The DAR Installer Plugin does not delete these workspaces automatically after installation of the DAR file. The workspace directories are named in the following form: darinstaller_workspace_yyyy-mm-dd-hh-mm-ss. Moving, deleting, or adding projects manually to the workspace might have adverse effects on DAR installations. The DAR Installer requires you to fill in certain values that are marked with an asterisk (*). All other fields are optional. For a description of the fields for the DAR Installer plug-in, see Table 1, page 24. To install a DAR file: 1. Run dardeployer.exe, which is located in the Composer root directory, to start the DAR Installer. 2. In the DAR Details section, specify values for the fields. 3. In the Connection Broker Details section, specify values for Connection Broker Host and Connection Broker Port and click Connect. 4. In the Repository Details section, specify values for the fields and click Install to install the DAR file to the repository. EMC Documentum CenterStage 1.2 Installation Guide 23

24 Deploying the CenterStage System You can view the log for the DAR installation by selecting the log file from the Log File drop down menu and clicking Open. Table 1. DAR installer fields Parameter Required Description DAR Yes The absolute file path to the.dar file that you want to install. The file path cannot contain any international characters or the installation will fail. Input File No The absolute file path to the install-based parameter file. Local Folder No The absolute file path to localized.properties files. If you want to make your application available in other languages, localize the project data such as labels, tabs, and descriptions. Log File No The file to save the log to. If this is not specified, the file defaults to <DAR>.log. Connection Broker Host Yes The address of the Connection Broker. Connection Broker Port Yes The port of the Connection Broker Repository. Repository Yes The name of the repository that you want to install the DAR file to. Click the Connect button after entering the Docbroker host and port to retrieve the available repositories. User Name Yes The login name for the repository. Password Yes The password for logging in to the repository. Domain No The domain of the user. Locale Folder No The absolute file path to localized.properties files. 24 EMC Documentum CenterStage 1.2 Installation Guide

25 Deploying the CenterStage System Deploying CenterStage DARs using an Ant Task You can deploy CenterStage DARs using the Ant task emc.install. Create an XML file that sets the following parameters. Parameter Required Description dar Yes The absolute file path to the.dar file being installed inputfile No The absolute file path to the install-based parameter file docbase Yes The name of the repository into which the.dar file is installed username Yes The login name for the repository password Yes The password for logging in to the repository domain No The domain in which the repository resides. localesfolder No The absolute file path to localized.properties files The following example XML file installs the DAR file CenterStage.dar in the testrepo repository. <?xml version="1.0"?> <project name="testtarget" default="installdar"> <description> This is ant script code used to install a DAR in a repository. </description> <!================================= target: installdar ================================= > <target name="installdar"> <emc.install dar="c:\builds\tools\headless\centerstage.dar" docbase="testrepo" username="user1" password="xxyyzz" domain=""/> </target> Customizing the product name in the application URL You can change the product name that appears in the product URL by renaming the WAR or EAR file before you deploy it. By default, CenterStagePro appears in the URL, but you can customize this name. Prior to deploying the CenterStage WAR or EAR file on the application server, change the name of the file from CenterStagePro to your preferred product name. The new name can contain only upper and lower case letters from A to Z and numbers from 0 to 9. Deploy the WAR or EAR file as described in Deploying CenterStage WAR files, page 26 or Deploying CenterStage EAR files, page 26 For more information about customizing and branding CenterStage, see the chapter Branding CenterStage in the EMC Documentum CenterStage Version 1.2 Best Practices Guide. EMC Documentum CenterStage 1.2 Installation Guide 25

26 Deploying the CenterStage System Deploying CenterStage WAR files Deploy the CenterStage WAR files according to the instructions provided with your chosen application server. Deploy the WAR on the following application servers: Apache Tomcat Oracle Application Server Oracle WebLogic Server 10g R3( ) Red Hat JBoss If your application server is not listed here, then it requires the CenterStage EAR file. See Deploying CenterStage EAR files, page 26 for instructions. Deploying CenterStage EAR files While some application servers require the CenterStage WAR file, the following application servers use the EAR file instead: Oracle WebLogic Server (11g R1) IBM WebSphere x If your application server is not listed here, then it requires the CenterStage WAR file. See Deploying CenterStage WAR files, page 26 for instructions. Deploying the EAR file to Oracle WebLogic Oracle WebLogic Server (11g R1) deployments use the CenterStage EAR file. Follow these tasks to deploy the EAR file to Oracle WebLogic Server (11g R1): 1. Preparing the EAR file, page Updating the server JDK, page Installing the EAR file, page 27 Preparing the EAR file To prepare the CenterStage EAR file for Oracle WebLogic: 1. Update the weblogic-application.xml file: <?xml version="1.0" encoding="utf-8"?> <weblogic-application xmlns=" <prefer-application-packages> <package-name>javax.namespace.xml.* </package-name> <package-name>org.apache.xerces.*</package-name> <package-name>org.apache.commons.*</package-name> </prefer-application-packages> <prefer-application-resources> <resource-name>meta-inf/services/*</resource-name> 26 EMC Documentum CenterStage 1.2 Installation Guide

27 Deploying the CenterStage System </prefer-application-resources> </weblogic-application> 2. Update weblogic.xml to set <cookie-http-only> to false: <?xml version="1.0" encoding="utf-8"?> <weblogic-web-app xmlns=" <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> <session-descriptor> <cookie-http-only>false</cookie-http-only> </session-descriptor> </weblogic-web-app> Updating the server JDK If the Oracle WebLogic server uses JDK 1.6, it can cause failures in CenterStage, including problems transferring files, and changing space settings. If these problems arise, use the following workaround. To update the WebLogic server for JDK 1.6: 1. Copy jaxb-api.jar, jaxb-impl.jar, jaxb1-impl.jar and jaxws-api.jar from %CenterStage%/APP-INF/lib 2. Paste the files into the application server directory %JAVA_HOME%/jre/lib/endorsed. If the endorsed directory does not exist, create it. 3. Delete jaxb-api.jar, jaxb-impl.jar, jaxb1-impl.jar, jaxws-api.jar, jsr173_api.jar, and saaj-api.jar from %CenterStage%/APP-INF/lib. Installing the EAR file Install the CenterStage EAR file per the instructions provided with Oracle WebLogic Server (11g R1). Deploying the EAR file to IBM WebSphere x Install the CenterStage EAR file per the instructions provided with IBM WebSphere x. Installing xplore To use xplore, you need to set up index agent filters after you configure the index agent, but before you start reindexing. Otherwise, the filters cannot be applied to objects that already have been indexed. You can install index agent filters that exclude cabinets, folders, or object types from being indexed. The CenterStage index filter is installed along with the CenterStage DARs. CenterStage needs to be installed before xplore starts to index. For information on installing xplore, see the EMC Documentum xplore Installation Guide. EMC Documentum CenterStage 1.2 Installation Guide 27

28 Deploying the CenterStage System Security and external access In some cases, CenterStage customers want to provide CenterStage access to employees, suppliers, clients, or partners who are not part of their internal network. They require a deployment solution that enables secure access to the CenterStage application. This section discusses the basic configuration required to deploy CenterStage with a proxy server. For additional information on external access scenarios, see the CenterStage System Planning Guide. Installing CenterStage with a proxy server Proxy servers can be integrated into the distributed content architecture to provide additional security to customer deployments. They can also provide caching benefits and traffic monitoring. There are two types of proxy servers. A forward proxy server acts as an intermediary between browsers in a client subnet and the outside world. HTTP requests from the client are redirected through the forward proxy so that outside of the client subnet, all requests are seen as coming from the proxy. Reverse proxy servers provide protection to the back end environments. They work in parallel with firewall configurations so that only the reverse proxy host has access to the back end environment. HTTP requests from the outside world are intercepted by the reverse proxy server and passed to the back end servers. This section walks through the configuration steps required to implement a topology in which proxy servers are implemented with ACS, Branch Office Caching Services (BOCS), and DMS. The Apache 6.0 Web Server is shown as an example, acting as the forward and reverse proxy server. Please note that the following are sample configurations. Refer to the appropriate third party vendors for additional information. Branch office This configuration uses one client and a BOCS server in the branch office using a forward proxy. The BOCS and the client need to be configured to send requests to the backend servers via the forward proxy. The configuration settings are shown in Figure 1, page EMC Documentum CenterStage 1.2 Installation Guide

29 Deploying the CenterStage System Figure 1. Branch Office configuration To implement a Branch Office configuration: 1. To configure Apache 6.0 web server as a forward proxymodify Apache s httpd.conf file to specify the clients allowed to use this proxy. ProxyRequest On ProxyVia On <Proxy *> Order deny.allow Deny from all Allow from </Proxy> 2. Restart the Apache web server. 3. Configure the client to access the proxy. In Internet Explorer, select Tools > Internet Options > Connections tab > LAN Settings. Enter the address and port of the Apache forward proxy. In Figure 2, page 30, Apache running on plesys107 vm2 port 80 is set to be the forward proxy to be used by this client. EMC Documentum CenterStage 1.2 Installation Guide 29

30 Deploying the CenterStage System Figure 2. LAN settings 4. IF DMS can directly access BOCS, push or pull mode can be used. Otherwise, BOCS must be configured to work in pull mode. In this case (BOCS behind a forward proxy), BOCS must be configured in pull mode to poll the DMS server periodically for any messages. 5. If BOCS is using a forward proxy, the forward proxy server host and port should be specified. The values are stored in the BOCS acs.properties as shown in Figure 3, page 30. Figure 3. BOCS configuration The BOCS installer presents options to install in pull mode and also specify the proxy host and port. The corresponding BOCS configuration object is defined in Documentum Administrator as shown in Figure 4, page EMC Documentum CenterStage 1.2 Installation Guide

31 Deploying the CenterStage System Figure 4. Documentum Administrator BOCS configuration settings 6. View the Apache access logs to see if the proxy is being used properly. A snippet of the HTTP Post method with BOCS URL for a BOCS read operation is shown in Figure 5, page 31. Figure 5. HTTP Post method with BOCS read operation Central office The central office example uses Content Server/Accelerated Content Server (CS/ACS), Documentum Messaging Server (DMS), CenterStage, and Documentum Administrator (DA). DMS should always be installed in a location with direct access to the primary CS/ACS. In this scenario, ACS, DMS, and CenterStage are configured with supported reverse proxy servers so that client requests will be redirected through the proxy server to the ACS, DMS, or CenterStage servers. This involves 1) configuring the reverse proxy for redirection and 2) modifying the base URLs of the ACS Server configuration object to use the proxy URL, as shown in Figure 6, page 32. EMC Documentum CenterStage 1.2 Installation Guide 31

32 Deploying the CenterStage System Figure 6. Central Office Configure the Apache web server as a reverse proxy to ACS, DMS, and CenterStage. The UCF client needs to send requests to the back-end servers via the proxy. Modify the Apache configuration file (httpd.conf) on the proxy server to specify the redirect rules. 1. Add the directives shown in Figure 7, page 32 to map proxy host>/acs1 to server host>:9080/acs. Figure 7. Proxy directives 2. Add the directives shown in Figure 8, page 32 to map proxy host>/dms to server host>:8489. Figure 8. DMS proxy directives Next you will configure the ACS and DMS servers. To the UCF client, the ACS is hidden behind a proxy. The ACS base URL must be modified since DFC will use this information to construct the URL that the UCF client uses to perform content transfer. The constructed URL must be accessible from the UCF client and should be accessed via the proxy. Use Documentum Administrator to modify the base URL (acs_base_url) of the ACS server configuration object. To modify the base URL of the ACS server configuration object 1. Log in to each repository associated with the ACS server using Documentum Administrator. 2. Navigate to Administration>Distributed Content Configuration>ACS Servers. 32 EMC Documentum CenterStage 1.2 Installation Guide

33 Deploying the CenterStage System 3. Go to the Properties page of the ACS server. 4. Select the ACS Server Connect URL and click Edit. 5. Modify the ACS Base URL to specify the proxy URL. For example: Original ACS URL server host>:9080/acs/servlet/acs Proxy ACS URL proxy host>/acs1/servlet/acs 6. Restart the repository and the ACS server (Java Method Server). Configure DMS messaging and verify the proxy is working properly. To configure DMS and verify the proxy configuration 1. Define a URL for DMS to use when polling BOCS for messages. This is defined in the BOCS acs.properties as shown in Figure 9, page 33. Figure 9. BOCS acs.properties definition Note that the dms.pulling.url is set to http\://<reverse proxy host>/dms, which was mapped to server host>:8489 in the httpd.conf. 2. On the DMS host, the dms.service.return.url defined in the DMS dms.properties must contain the proxy URL, as shown in Figure 10, page 33 Figure 10. Proxy URL setting in dms.properties 3. To verify that proxy is being properly used, check the ACS log on the application server. The URL built by DFC that is passed to the UCF client to use for the content transfer contains the proxy host. The URL from an ACS write operation is shown in Figure 11, page 33. Figure 11. ACS write operation The access logs on the reverse proxy host will also show a POST method, as shown in Figure 12, page 34. EMC Documentum CenterStage 1.2 Installation Guide 33

34 Deploying the CenterStage System Figure 12. Reverse proxy access log 34 EMC Documentum CenterStage 1.2 Installation Guide

35 Chapter 4 Upgrading CenterStage This chapter provides both general and specific information regarding upgrading from earlier versions of CenterStage to CenterStage 1.2. Backing up app.xml If you have customized one or both of your CenterStage app.xml files, back them up before upgrading to a new version to avoid having the file overwritten by the generic app.xml files that ship with CenterStage. These files are located in Documentum Administrator at the following locations: Cabinets > System > Applications > CenterStage Cabinets > System > Applications > CenterStage Pro After Upgrading from 1.0 or 1.1 to CenterStage 1.2, you must apply your configuration changes to /CenterStage Pro/app.xml. Note that /CenterStage/app.xml should NOT be modified. This contains the base configuration for CenterStage. Edit /CenterStage Pro/app.xml to configure CenterStage. See the instructions in app.xml for details. Backing up custom configuration files If you have added any custom configuration files to the /CenterStage Pro/config/ directory, back up those files and restore them after upgrade. Reinstalling custom DARs If you have deployed any custom DARs in your current CenterStage system, reinstall them after installing the CenterStage DAR. EMC Documentum CenterStage 1.2 Installation Guide 35

36 Upgrading CenterStage Upgrading from CenterStage 1.x to CenterStage 1.2 This chapter provides specific instructions for upgrading an existing CenterStage 1.x instance to CenterStage 1.2. To upgrade from 1.x to Clear the DFC BOF cache on the Content Server machine a. Go to the Windows Services panel and stop the Documentum Java Method Server service. b. Delete the contents of <documentum_home>/cache (for example C:\Documentum\cache). c. In the Windows Services panel, start the Documentum Java Method Server service. Verify that the service is running before you continue. 2. Install.dar files in the following order. For installation instructions, please see Installing a DAR file with the DAR Installer, page 23. a. Collaboration Services b. DCS Attachments c. CenterStage.dar d. CenterStage_Pro.dar e. CenterStageDatatable.dar f. CIS_Artifacts.dar g. Extended_Search-Clustering.dar h. All other.dar files (optional.dars) Rich_Media_Services.dar (optional) Transformation.dar (optional, supports Thumbnail Generator) CenterStageTemplates.dar (optional) 3. Again, use the Windows Services window to verify that the Documentum Java Method Server is running. 4. Using Documentum Administrator (DA), verify that UpdateRoomAspect Attributes has run successfully. a. Open the DA application and log in as the repository owner. b. Navigate to Cabinets>Temp. c. Double-click Result.UpdateRoomAspectAttributes to open the item. If there are multiple items with the same name, open the one with the most current date and time. The file will open in a text editor, such as Notepad. d. Verify the following text in the result file: Result: T Update: Updating RoomAspect attribute a_modify_date successful. 36 EMC Documentum CenterStage 1.2 Installation Guide

37 Upgrading CenterStage If it has not run successfully, run the method manually using DA. 5. Using DA, run the SetupCenterStageIndexes method. a. Navigate to Administration>Job Management>Methods. b. Type setup in the search box to find the method. c. Right-click the SetupCenterStageIndexes method and choose Run. d. Select the Save Results and Run As Server options and click OK. 6. Verify the ServerApps.log file does not contain any current errors. a. On the Content Server, navigate to the Method Server logs directory. For example, C\Documentum\jboss4.2.0\server\DctmServer_MethodServer\logs. b. Notice the Date Modified for the ServerApps.log file. Verify that this file has not been modified since you began the upgrade process. c. Open the log file and verify that no new/current errors have occurred. Running UpgradeCenterStage1_2 The method UpgradeCenterStage1_2 should run automatically after you deploy the version 1.2 DAR files. In Composer, check the log for the DAR installation by selecting the centerstagedar.log file from the Log File drop down menu and clicking Open. The log files are stored in [composer installation directory]/darinstallerlogs/. If UpgradeCenterStage1_2 did not run, you should run the UpgradeCenterStage1_2 method manually using Documentum Administrator. When running the method, choose the option Save Results and Run as Server, then click OK. Running this method ensures that: changes to the discussion/topic object model are visible in the user interface custom space icons and template icons are retained customized ACLs on folders are upgraded to the ContainerSecurityAspect for consistency with the new ContainerSecurityModel.. EMC Documentum CenterStage 1.2 Installation Guide 37

38 Upgrading CenterStage Upgrading folder permissions from 1.1 to 1.2 During upgrade from 1.1 to 1.2, a method is invoked at the end of the DAR installation that will do the following: Assign the kw_acl permission to all folders with dm_permissions that are governed by a space. Convert subfolders with custom permissions to the container security aspect. Folders having custom ACLs are not converted. ACLs on children of folders will not change. 38 EMC Documentum CenterStage 1.2 Installation Guide

39 Chapter 5 Configuration After installation, you must set up users and configure the system. Some of these tasks are performed using Documentum Administrator. Perform the following tasks in the following order: Update paths for log4j appender, page 40 Access Documentum Administrator, page 40 Set up CenterStage indexes, page 40 Create a user in the repository, page 41 Enable notification for subscribed content, page 42 Assign members to the dce_room_creator role, page 42 Assign members to the dmc_kw_manage_space_templates role, page 43 Configure the administrator address, page 43 Configure the embedded Content Server for SMTP, page 44 Configure Retention Policy Services (optional), page 44 Access CenterStage, page 44 Create a space, page 45 The following are additional and optional configuration options: Configure the content policy for each space, page 45 Installing DARs with a localized data dictionary, page 45 Populating a localized CenterStage data dictionary, page 46 Configuring high-availability, page 47 Linux random number daemon configuration, page 47 Configuring CenterStage to enable Kerberos authentication, page 48 Appendix B, Configuring HTTP compression (Optional) EMC Documentum CenterStage 1.2 Installation Guide 39

40 Configuration Update paths for log4j appender After installing the CenterStage WAR file (or before, if you prefer), you need to update two placeholder path values in the log4j.properties file. The log4j.properties file is located at <Web Application Home Folder>/CenterStagePro/WEB-INF/classes/log4j.properties. In that file are two values identifying the locations for log4j files. log4j.appender.xmlfile.file=/temp/logs/centerstage-log.xml log4j.appender.file.file=/temp/logs/centerstage.log Change the path values for these two variables to valid paths on the web application system where log4j log files can be created and updated by the web application server. This should be done for all lines in the log4j.properties file that contain the string ${java.io.tmpdir}. Note: Starting the CenterStage web application without changing these values to valid paths on the host machine will result in an error message about log4j.appender configuration that varies depending on the application server in use. Access Documentum Administrator You can start Documentum Administrator by going to number]/da, where [machinename] is the fully qualified server name and port number is the port on which Documentum Administrator is listening. Log in with the install owner credentials. This is the account that was used to install the Content Server. For information on using Documentum Administrator and on administering CenterStage, refer to the following documents, available on EMC Documentum CenterStage Administration Guide EMC Documentum Documentum Administrator Deployment Guide EMC Documentum Documentum Administrator User Guide EMC Documentum Documentum Administrator Release Notes EMC Documentum Content Server Installation Guide EMC Documentum Content Transformation Services Administration Guide Set up CenterStage indexes After completing an install, it is important that you run the method SetupCenterStageIndexes from Documentum Administrator. This method greatly improves the performance of several common CenterStage queries. The database administrator should run the method during a time when the repository is not being used heavily, as the method can take a long time to run when the repository has millions of objects. To run the SetupCenterStageIndexes method: 1. Open Documentum Administrator. 40 EMC Documentum CenterStage 1.2 Installation Guide

41 Configuration 2. Navigate to Administration>Job Management>Methods 3. Locate the method SetupCenterStageIndexes. For example, search for methods that begin with Set. 4. Right-click the method name and choose Run. 5. Accept the default parameters and click OK. Create a user in the repository To use CenterStage, a person must have a user account in at least one EMC Documentum repository. This section describes how to create a user account in a repository. Before you create a user, determine the type of authentication used by the Documentum Content Server. Content Server can use any of the following: LDAP authentication, Windows domain authentication, or an inline password managed by the server. To create a user: 1. In Documentum Administrator, connect to the repository in which to create the user and navigate to Administration>User Management>Users. 2. Select File>New>User. 3. Enter the following minimum information required to create a CenterStage user: Name: Type the name that appears to other users. User Login Name: Type the name for signing into a repository. User Source: Select one of the following options: None: User is authenticated in a Windows domain. LDAP: User is authenticated by an LDAP server. Inline Password: User is authenticated by a password stored in the repository. Unix only: User is authenticated by UNIX. Domain only: In a repository with Windows domain authentication enabled, user is authenticated against a Windows domain. Unix first: In a repository with Windows domain authentication enabled, user is authenticated first by UNIX and then against a domain. Domain first: In a repository with Windows domain authentication enabled, user is authenticated first against a domain and then by UNIX. Note: For instructions on entering additional user information, see the Documentum Administrator User Guide. 4. Users have the ability to subscribe to content of interest and to be notified when the content changes. To allow the user to receive notifications when subscribed content changes, enter the Address. Note: For users to receive notifications, you must also specify the SMTP server on the Documentum platform, as described in Enable notification for subscribed content, page 42. EMC Documentum CenterStage 1.2 Installation Guide 41

42 Configuration 5. Click OK. For more information on configuring users, refer to the chapter "User Management" in the Documentum Administrator User Guide. Enable notification for subscribed content For users to receive notifications when subscribed content changes, do the following: Specify the SMTP server that provides mail services to the Content Server, as described in this section. For each user, set the Address option in the user s profile, as described in Create a user in the repository, page 41. To specify the SMTP server that sends notifications to CenterStage users: 1. In Documentum Administrator, navigate to Administration>Basic Configuration>Content Servers. 2. Select the Content Server and select View>Properties>Info. 3. In the SMTP Server field in the Info tab, type the name or IP address of the SMTP server that provides mail services to the Content Server. 4. Click OK. Assign members to the dce_room_creator role Space coordinators who create spaces must have the dce_room_creator role. To assign members to the dce_room_creator role: 1. In Documentum Administrator, open the User Management node. 2. Select the Roles node. 3. Navigate to and double-click the dce_room_creator role. If the role does not appear on the first page of the list, navigate to the next page. 4. Select File > Add Member(s). 5. Add users to the role by selecting the users in the left pane and using the arrow button to move the users to the right pane. 6. Click OK. 42 EMC Documentum CenterStage 1.2 Installation Guide

43 Configuration Assign members to the dmc_kw_manage_ space_templates role Space coordinators who have been assigned the dce_room_creator role can also be given permission to create space templates, if necessary. To assign members to the dmc_kw_manage_space_templates role: 1. In Documentum Administrator, open the User Management node. 2. Select the Roles node. 3. Navigate to and double-click the dmc_kw_manage_space_templates role. If the role does not appear on the first page of the list, navigate to the next page. 4. Select File > Add Member(s). 5. Add users to the role by selecting the users in the left pane and using the arrow button to move the users to the right pane. 6. Click OK. Configure the administrator address In certain locations on the CenterStage user interface provides a contact your administrator link. For example, this link is available on the Advanced tab of My Preferences if members need additional information about the CenterStage server URL for notifications. Configure an appropriate address in app.xml so that CenterStage members can contact an administrator for assistance when needed. Note: This procedure is mandatory. To configure CenterStage with an administrator address: 1. In Documentum Administrator, navigate to Cabinets > System > Applications > CenterStage Pro. 2. Check out the app.xml file. 3. Open app.xml for editing in a text or XML editor. 4. Locate the <administrator> element. 5. Replace the following placeholder address with the appropriate address: < >[email protected]</ > 6. Save your changes. You can continue with any further configuration tasks from this chapter, but remember to check in the file when you are finished. EMC Documentum CenterStage 1.2 Installation Guide 43

44 Configuration Configure the embedded Content Server for SMTP An SMTP server must be installed and available before you install CenterStage. The SMTP server can be on the CenterStage host or a remote host. After installing CenterStage, you need to configure the name or IP address of the computer hosting the SMTP server in the embedded Content Server so that CenterStage can connect to it. To configure the embedded Content Server for SMTP 1. In Documentum Administrator, navigate to Administration > Basic Configuration > Content Server 2. Select the CenterStage Server line item. 3. Choose View > Properties > Info. 4. Scroll down to the field SMTP Server: 5. Enter the name or IP address of the computer hosting the SMTP server. For more information, see the EMC Documentum Content Server 6.6 Installation Guide, Chapter 2, Preparing the Host for Content Server Installation. Configure Retention Policy Services (optional) To configure CenterStage to utilize Retention Policy Services (RPS), ensure that you have installed the RPS 6.5 SP3 DAR: there is an incompatibility with earlier versions of the RPS BOF modules. After a space has a retention policy applied, participants (or anyone that can create objects) need to be added to the "dmc_rps_contributor" role. CenterStage provides the method SetupCenterStageForRPS, which can be run from Documentum Administrator. This method makes the necessary changes to privileged roles and the member groups for all existing spaces to the RPS Contributor role. For a space or folder under retention, users who can create content must be able to apply retention that is, they need to be members of this role. This method can be set up to run nightly, via a job. It needs to be run any time new users need to be given the extended privileges required to execute RPS operations. Access CenterStage These are the instructions for accessing CenterStage, either using the Start menu shortcut or by entering the URL in a web browser. You can access CenterStage through a web browser at: Where [machinename] is the fully qualified server name on which CenterStage has been installed, [port] is the port on which CenterStage is listening for connections, and [repositoryname] is the name of the repository. 44 EMC Documentum CenterStage 1.2 Installation Guide

45 Configuration Create a space A space is the primary environment in which users work with content and collaborate with team members. To create a space: 1. Log in to CenterStage as a member with sufficient access rights to create a space (see Assign members to the dce_room_creator role, page 42). 2. Click the Spaces action to the right of the text search field in the top header. 3. Click the Create Space button. 4. Complete the Create Space dialog box and click OK. CenterStage creates the new space and opens the space in a new tab. Configure the content policy for each space A space coordinator must modify each space s content policy to specify the types of documents that users can add to the space. For CenterStage, EMC recommends specifying that any type of document can be added. To configure content policy, a user must have space coordinator privileges. To configure a space s content policy: 1. Open the space by clicking the space s tab. If the space s tab does not appear, click Spaces at the top of the page and then select the space. 2. Click the Settings button. If the Settings button is not visible, you are not assigned to the appropriate role for performing this procedure. 3. Select the Content Policy tab. 4. In the column labelled when they import a file in this format, double-click the Document row. 5. If necessary, select the option (any file format) [default]. 6. Click Save. Installing DARs with a localized data dictionary In order to populate locale-specific type and attribute labels, DARs have to be installed with localized DAR Data Dictionary Language Pack files. The following is a list of DARs that have localized Data Dictionary DAR files for CenterStage. These localized DAR Data Dictionary files are located inside each CenterStage Language Pack. To proceed with DAR Language pack installation you need to download the core DAR file. EMC Documentum CenterStage 1.2 Installation Guide 45

46 Configuration Core DAR file name Collaboration Services.dar CenterStage.dar CenterStage_Pro.dar Localized DAR Data Dictionary Language Pack Collaboration_Dar_Language_Pack_ zip CenterStage_Dar_Language_Pack_ zip CenterStage_Pro_Dar_Language_Pack_ zip Before installing the DAR with localized data dictionary, the required locale should be enabled in the repository. During repository creation, a set of data dictionary information is loaded. based on the Content Server host locale. Content Server currently supports English, Japanese and Korean as host locales. If the host locale is English, Japanese or Korean, the data dictionary information for that locale is loaded. To add a new locale, use the population script provided by Documentum. You can populate and publish the data dictionary file by following the procedures located in Appendix E, "Populating and Publishing the Data Dictionary, in the Documentum Content Server Administration Guide. To install DAR files with DAR Data Dictionary Language Pack: 1. From the Download Center, download the core DAR file included in each target deployment zip in the War and Dar folder. 2. Download the corresponding DAR Language Pack included in each CenterStage Language Pack. 3. Unzip the DAR Language Pack zip to a temp directory which will contain localized Data Dictionary files for the DAR. 4. Install the DAR files. Per the instructions given in the section "Installing a DAR file, create a build file, add the "localesfolder" parameter to the build file, and give the absolute file path to the localized properties files. Example 5-1. Example <emc.install dar="c:\builds\headless\<core DAR name>" docbase="<repository name>" username="<login name>" domain="" localesfolder="<temp>\<core DAR name>\locales"/> For another installation method, refer to Installing a DAR file with the DAR Installer, page 23. Per the instructions, set the Local Folder parameter to the temp location <temp>\<dar name>\locales where you have unzipped the DAR Language Pack. Populating a localized CenterStage data dictionary Follow instructions below to populate additional CenterStage Pro locale-specific type and attribute labels. 46 EMC Documentum CenterStage 1.2 Installation Guide

47 Configuration To populate a localized CenterStage Data Dictionary: 1. Download the CenterStage_Pro_Data_Dictionary_Language_Pack_1.1.zip included in each CenterStage Language Pack to the Content Server. 2. Unzip the file to %DM_HOME%\bin folder You can populate and publish the data dictionary file by following the procedures located in Appendix E, "Populating and Publishing the Data Dictionary, in the Content Server version 6 Administration Guide. Configuring high-availability CenterStage can be load balanced using network load balancers. In order to support the CTA plug-in, session "stickiness" (or affinity) must be used. That is, once a session has been established between a browser and a CenterStage application server, all subsequent traffic from that browser must be routed to that application server (by the load balancer) for the duration of the session. There are two scenarios for session stickiness, based on whether the CTA plug-in is used or not (see "Allowing users to install CenterStage plug-ins" in the CenterStage Administration Guide for details on how to enable or disable the plug-in through configuration). If the use of the plug-in is disabled, then session affinity can be accomplished either by IP or session. If the session affinity is by session, then session failover is supported if the application server is properly configured. If the use of the plug-in is enabled, session affinity must use affinity by IP, and in the instance where one of the application server instances fails, users are re-prompted for login, as session failover does not occur. The table below summarizes the supported configurations: CTA Plug-in Enabled? Support for Session Failover? Load Balancing Options Recommended Deployment Types Yes Yes By IP Intranet deployments No Yes (if session affinity is by session) By IP or by session Extranet deployments Linux random number daemon configuration The Intel-based platform does not have a random generator in its chip set. As a result, Linux cannot generate random numbers. Workflow and other platform features use random number generators. Any feature that uses random numbers from the system (OS level) on Linux will encounter a performance issue. Linux comes with a random generator daemon, but it must be started manually. To start the random generator, enter this command as the root user: /sbin/rngd -b -r /dev/urandom -o /dev/random Somtimes, it is necessary to modify the Java Method Server to use this random generator. Check the number of entropy_avail events to see if it changed to a higher number: cat /proc/sys/kernel/random/entropy_avail If necessary, add this line to startmethodserver.sh: EMC Documentum CenterStage 1.2 Installation Guide 47

48 Configuration Djava.security.egd=file:/dev/urandom For Java 5 or later, use this version of the command: -Djava.security.egd=file:/dev/./urandom Configuring CenterStage to enable Kerberos authentication CenterStage supports Kerberos single sign-on (SSO) authentication. Complete instructions for configuring Kerberos for use with Content Server are provided in the white paper EMC Documentum Kerberos SSO Authentication: A Detailed Review. This section discusses specific extensions that must be made to the CenterStage app.xml to enable Kerberos SSO authentication. An extensible app.xml configuration file can be located and modified using Documentum Administrator. The file path is /Cabinets/system/applications/CenterStage Pro/app. xml. You can copy the <authentication> element from /Cabinets/system/applications/ CenterStage/app.xml paste it into /Cabinets/system/applications/CenterStage Pro/app.xml, then modify the settings, or you can retype the information as shown in Figure 13, page 48. Note: In a distributed system, only the app.xml file on the global repository needs to be updated. The other repositories in the system will inherit these settings from the global repository. Update the authentication/kerberos_sso elements as follows. Set the <enabled> element to true. Set the <domain> element to your Kerberos domain. Set the <docbase_login_fallback> element to true. Should there be a failure in the Kerberos mechanism, the fallback behavior will be to ask the user to log in to the repository. Figure Figure 13, page 48 shows a sample authentication element from an app.xml file. Figure 13. Example code snippet from the authentication element in app.xml <authentication> <!-- Kerberos SSO authentication protocol configuration --> <kerberos_sso> <enabled>true</enabled> <domain>dctmlabs.com</domain> <docbase_login_fallback>true</docbase_login_fallback> </kerberos_sso> </authentication> 48 EMC Documentum CenterStage 1.2 Installation Guide

49 Configuration Configuring CenterStage for RSA authentication You can configure RSA authentication per the instructions in Configuring Single Sign-on for Documentum D6 with RSA Access Manager Products, with one minor configuration change to enable RSA Access Manager to work correctly with CenterStage. Configuring RSA Access Manager Web Agent to use an authorization dialog The appropriate method for user authorization is to use a pop-up dialog rather than a form redirect. You can configure this by changing a value in the webagent.conf. As described in Configuring Single Sign-on for Documentum D6 with RSA Access Manager Products, configuring the RSA Access Manager Web Agent generates the file webagent.conf (for example, under C:\Program Files\RSA\Access Manager Agent 4.7\IIS\conf). In webagent.conf, change the value of cleartrust.agent.form_based_enabled to FALSE so that the server will use the browser authentication dialog instead of a form redirect. Once RSA Access Manager and RSA Policy server are configured, make the following extensions to the CenterStage app.xml to enable RSA authentication. An extensible app.xml configuration file can be located and modified using Documentum Administrator. The file path is /Cabinets/system/applications/CenterStage Pro/app. xml. You can copy the <authentication> element from /Cabinets/system/applications/ CenterStage/app.xml paste it into /Cabinets/system/applications/CenterStage Pro/app.xml, then modify the settings, or you can retype the information as shown in Figure 13, page 48. Note: In a distributed system, only the app.xml file on the global repository needs to be updated. The other repositories in the system will inherit these settings from the global repository. Update the authentication/sso_config elements as follows: Set the <ecs_plug_in> element to dm_rsa. Set the <ticket_cookie> element to CTSESSION or ticket cookie name used by your RSA policy server. Set the <user_header> element to remote_user or user header name used by your RSA policy server. Set the <sso_argument> element to RSA [rsa policy server host name] [rsa policy server port] 1. Figure 14, page 49 provides a sample of sso_config element code from the app.xml configuration file. Figure 14. sso_config element in app.xml for RSA authentication <ecs_plug_in>dm_rsa</ecs_plug_in> <ticket_cookie>ctsession</ticket_cookie> <user_header>remote_user</user_header> <sso_argument>rsa RSA-POLICY </sso_argument> EMC Documentum CenterStage 1.2 Installation Guide 49

50 Configuration Configuring CenterStage for Netegrity authentication Configure Netegrity per the instructions in the Netegrity Configuration for EMC Documentum Webtop Solutions Guide. The only difference in the instructions is the location of the app.xml file you must modify. Once the Netegrity reverse proxy and policy servers are configured, make the following extensions to the CenterStage app.xml file to enable Netegrity authentication. An extensible app.xml configuration file can be located and modified using Documentum Administrator. The file path is /Cabinets/system/applications/CenterStage Pro/app. xml. You can copy the <authentication> element from /Cabinets/system/applications/ CenterStage/app.xml paste it into /Cabinets/system/applications/CenterStage Pro/app.xml, then modify the settings, or you can retype the information as shown in Figure 13, page 48. Note: In a distributed system, only the app.xml file on the global repository needs to be updated. The other repositories in the system will inherit these settings from the global repository. Using Documentum Administrator, locate the file at /Cabinets/system/applications/ CenterStage/app.xml. Copy the <authentication> element and paste it into the file /Cabinets/system/applications/CenterStage Pro/app.xml. Update the authentication/sso_config elements as follows: Set the <ecs_plug_in> element to dm_netegrity. Set the <ticket_cookie> element to SMSESSION or the ticket cookie name used by your Netegrity policy server. Set the <user_header> element to SM_USER or the user header name used by your Netegrity policy server. Figure 15. sso_config element in app.xml for Netegrity authentication <ecs_plug_in>dm_netegrity</ecs_plug_in> <ticket_cookie>smsession</ticket_cookie> <user_header>sm_user</user_header> 50 EMC Documentum CenterStage 1.2 Installation Guide

51 Configuration Configuring single sign-on with a reverse proxy server When you set up a proxy server with single sign-on, the product name used by the proxy server must match the product name on the application server. Specifically, depending on the server you are using, the httpd.conf file contains lines similar to these, where the product name has to be the same on both sides of the connection. This is a valid configuration setting: ProxyPass /CenterStagePro This configuration setting is invalid: ProxyPass /CustomName EMC Documentum CenterStage 1.2 Installation Guide 51

52 Configuration 52 EMC Documentum CenterStage 1.2 Installation Guide

53 Chapter 6 Troubleshooting This chapter identifies common installation issues and possible solutions. Disable the Windows 2008 firewall on user machines Windows 2008 comes with a firewall enabled. Users need to disable it in order to log in to CenterStage. To disable the Windows 2008 firewall: 1. Select Start->Control panel. 2. Open Windows Firewall. 3. Click Change Setting. 4. Choose the Off radio button. 5. Click OK. Troubleshooting CIS This section provides suggested steps for verifying that Content Intelligence Services is installed and running properly. Validate the installation of cis_artifacts.dar Once you have deployed cis_artifacts.dar, check in Documentum Administrator that the following modules are created: sco_annotation: in Cabinets>System>Modules cis_annotation_aspect: in Cabinets>System>Modules>Aspect EMC Documentum CenterStage 1.2 Installation Guide 53

54 Troubleshooting Verify the required table has been created Once cis_artifacts.dar is installed, check that the table dm_annotation has been created. This can be done using a DQL query as described in the following procedure. To check the existence of the dm_annotation table: 1. Log in to DA. 2. Select Tools > DQL Editor. 3. Run the query: Select * from dm_annotation 4. The result must be: ann_id ann_value Test the entity extraction Before testing the entity extraction, make sure the following prerequisites are met: The repository is started and reachable. CenterStage is started. CIS (including Luxid services) is started. You can then test the entity extraction. Before starting the test, create a Word document, EuropeanUnion.doc with the content from the Appendix. To test the entity extraction: 1. Log in to CenterStage. 2. Create a space called The European Union. 3. Open the Content view and create a folder. 4. Import the EuropeanUnion.doc file. 5. Wait for an hour (CIS server looks for new or modified spaces every half hour). 6. Open the Search view of the space. 7. Check that the filters Company, Place and People contain entities of the document EuropeanUnion.doc. If you cannot wait and want to run the test faster, you can modify the default frequency of CIS servers checks. In cis.properties configuration file, located in <CIS installation directory>\deploy\cis.ear\app-inf\classes, edit the property cis.server.centerstage.interval. It is set to 1800 seconds by default, you can set it to 60 seconds for example. 54 EMC Documentum CenterStage 1.2 Installation Guide

55 Troubleshooting Configuring WebLogic security To allow subscriptions in CenterStage to work correctly without an existing repository session in WebLogic, the WebLogic config.xml file needs to be modified so that the <enforce-valid-basic-auth-credentials> element within the <security-configuration> element has a value of false. This will also ensure that RSS feeds work for LDAP users. ==================================================================== <security-configuration>... <enforce-valid-basic-auth-credentials> false </enforce-valid-basic-auth-credentials> </security-configuration> ==================================================================== Optimizing performance This section describes settings that have been tested by our internal deployment engineers and have been shown to enhance performance. For additional information on performance optimization, see the current CenterStage Release Notes. Performance settings for Oracle repository You can improve performance when using an Oracle repository by setting cursor_sharing to FORCE. To set Oracle cursor_sharing: 1. Log in to Oracle Enterprise Manager 2. Navigate to Administration>All Initialization Parameters. 3. Click the SPFile tab. 4. Use the pop-up menu to change the value for cursor_sharing to FORCE. 5. Restart the repository to implement the change. Performance settings for MS SQL repository The following are suggested settings to improve performance when using an MS SQL repository. On the server machine, update or create the System variable DM_LEFT_OUTER_JOIN_FOR_ACL and set the value to T. Another setting that will help performance is to set Forced parameterization in SQL Server. EMC Documentum CenterStage 1.2 Installation Guide 55

56 Troubleshooting To set MS SQL Server Parameterization: 1. Open MS SQL Server Management Studio. 2. Right-click the documentum database. 3. Choose Properties from the context menu. 4. Click the Options tab in the Database Properties screen. 5. Under Miscellaneous, locate the Parameterization variable and set it to Forced. Delay when installing with existing DCS data tables When installing CenterStage in an environment with existing DCS data tables, it can take up to one hour for the DCS dar file to be installed when 200 data tables exist. The installation process updates the dmc_datatable_row type, which is the base type for all data table rows. Even though the type installation does not actually change anything about the type, reinstalling it triggers a data dictionary republish for all of the existing 200 data table types. 56 EMC Documentum CenterStage 1.2 Installation Guide

57 Appendix A Test file for CIS entity extraction: EuropeanUnion.doc The European Union (EU) is an economic and political union of 27 member states, located primarily in Europe. It was established by the Treaty of Maastricht on 1 November 1993[5] upon the foundations of the pre-existing European Economic Community. With almost 500 million citizens, the EU combined generates an estimated 30% share (US$16.8 trillion in 2007) of the nominal gross world product.[6] The EU has developed a single market through a standardised system of laws which apply in all member states, guaranteeing the freedom of movement of people, goods, services and capital.[7] It maintains a common trade policy,[8] agricultural and fisheries policies,[9] and a regional development policy.[10] Sixteen member states have adopted a common currency, the euro. It has developed a role in foreign policy, representing its members in the World Trade Organisation, at G8 summits, and at the United Nations. Twenty-one EU countries are members of NATO. The EU has developed a role in justice and home affairs, including the abolition of passport controls between many member states under the Schengen Agreement, which incorporates also non-eu states.[11] The EU operates through a hybrid system of intergovernmentalism and supranationalism. In certain areas it depends upon agreement between the member states. However, it also has supranational bodies, able to make decisions without unanimity between all national governments. Important institutions and bodies of the EU include the European Commission, the European Parliament, the Council of the European Union, the European Council, the European Court of Justice and the European Central Bank. EU citizens elect the Parliament every five years. The EU traces its origins to the European Coal and Steel Community formed among six countries in 1951 and the Treaty of Rome in Since then the union has grown in size through the accession of new countries, and new policy areas have been added to the remit of the EU institutions. States member of European Union: Austria Belgium Bulgaria Cyprus Czech Republic Denmark Estonia Finland EMC Documentum CenterStage 1.2 Installation Guide 57

58 Test file for CIS entity extraction: EuropeanUnion.doc France Germany Greece Hungary Ireland Italy Latvia Lithuania Luxembourg Malta Netherlands Poland Portugal Romania Slovakia Slovenia Spain Sweden United Kingdom 58 EMC Documentum CenterStage 1.2 Installation Guide

59 Configuring HTTP compression Appendix B You can choose to configure HTTP compression on the application or web server and enable gzip compression in CenterStage. Perform the instructions provided in this chapter after you have installed CenterStage. Configuring HTTP compression on the web server When you request data using the browser from any website, the server compresses the requested content and sends the data to your browser. The browser then decompresses the data and displays it in the browser. Enabling HTTP compression is resource-intensive on the server. Therefore, it is recommended to configure reverse proxies if you have a front-end web server such as an Apache web server on a separate host, and configure the compression on the server. It is recommended that you enable HTTP compression for the following Mime types available in the CenterStage application: compressablemimetype="text/html,text/xml,application/xml,text/javascript,text/css" Enabling HTTP compression on the Apache web server On the Apache web server, using the mod_deflate module is the most popular and efficient option. To enable gzip on an Apache web server, edit the httpd.conf file, and add the following lines: LoadModule deflate_module modules/mod_deflate.so <Location /> SetOutputFilter DEFLATE # Netscape 4.x has some problems... BrowserMatch ^Mozilla/4 gzip-only-text/html # Netscape have some more problems BrowserMatch ^Mozilla/4\.0[678] no-gzip # MSIE masquerades as Netscape, but it is fine BrowserMatch \bmsie!no-gzip!gzip-only-text/html EMC Documentum CenterStage 1.2 Installation Guide 59

60 Configuring HTTP compression # NOTE: Due to a bug in mod_setenvif up to Apache # the above regex won't work. You can use the following # workaround to get the desired effect: #BrowserMatch \bmsi[e]!no-gzip!gzip-only-text/html # Don't use gzip for IE6, as it can cause the browser to hang SetEnvIf User-Agent ".*MSIE.6.*" no-gzip # Don't compress images SetEnvIfNoCase Request_URI \ \.(?:gif jpe?g png)$ no-gzip dont-vary # Make sure proxies don't deliver the wrong content Header append Vary User-Agent env=!dont-vary </Location> For instructions on configuring the mod_deflate module, see the Apache official documentation available here: Enabling HTTP compression on the Apache Tomcat server To enable gzip compression on the Tomcat web server, edit the server.xml file in the conf directory of your Tomcat installation, and insert the lines related to compression as indicated (last 4 lines): <!-- Define a non-ssl HTTP/1.1 Connector on port > <Connector port="8080" maxhttpheadersize="8192" maxthreads="150" minsparethreads="25" maxsparethreads="75" enablelookups="false" redirectport="8443" acceptcount="100" connectiontimeout="20000" disableuploadtimeout="true" compression="on" compressionminsize="1024" nocompressionuseragents="gozilla, traviata" compressablemimetype="text/html,text/xml,application/xml,text/javascript,text/css" /> Enabling compression is resource-intensive on the Tomcat hosting server node. Hence, it is recommended to configure an Apache web server as the front-end server and enable compression on the Apache web server instead of the Tomcat server. You can configure the mod_jk or another relevant module between Apache and Tomcat request routing. For more information, read the documentation available here: Enabling HTTP compression on the RedHat JBoss server You can enable compression in the server.xml file of the application server in the following manner: <Connector port="${bv.jboss.port.http}" address="${jboss.bind.address}" maxthreads="250" maxhttpheadersize="8192" 60 EMC Documentum CenterStage 1.2 Installation Guide

61 Configuring HTTP compression emptysessionpath="true" protocol="http/1.1" enablelookups="false" redirectport="${bv.jboss.port.https}" acceptcount="100" connectiontimeout="20000" disableuploadtimeout="true" compression="on" compressionminsize="2048" nocompressionuseragents="gozilla, traviata" compressablemimetype="text/html,text/xml,text/plain, application/xml,text/javascript, text/css" > Enabling compression is resource-intensive on the JBoss hosting server node. Hence, it is recommended to configure an Apache web server as the front-end server and enable compression on the web server instead of enabling it on the JBoss server. You can configure the Mod_jk module or another suitable module between Apache and JBoss request routing. For more information, read the documentation available here: Enabling compression on the Oracle WebLogic server It is recommended to configure an Apache HTTP server as the front-end server for the WebLogic server. To install an Apache 2.0.X or 2.2.X web server: 1. Download the Apache 2.0.X or 2.2.X web server installer from the following location for Windows: You can download the web server for any operating system and install and configure the web server. For more information see To install an Apache web server plug-in to communicate with the WebLogic server: 1. Download the latest Apache plug-ins for the WebLogic server from the Oracle website. The direct link to download the apache plug-in modules zip file is as follows: Apache.zip 2. After downloading the zip file, extract the zip to a local directory. The following directories are created when you extract the zip file to the specified directory. These directories contain shared object files for various platforms. EMC Documentum CenterStage 1.2 Installation Guide 61

62 Configuring HTTP compression Table 2. Directories containing shared object files Operating System Solaris Shared Object Location solaris/sparc solaris/sparc/largefile1 solaris/x86 Linux solaris/x86/largefile1 linux/i686 linux/i686/largefile1 linux/ia64 Windows (Apache 2.0 and 2.2, 32-bit) linux/x86_64 win\32 3. Copy mod_wl_22.so for the Apache 2.2.X web server file or mod_wl_20 for the Apache 2.0.X web server, to the following location on the web server: %ApcheHome%\Apache2.x.x\modules 4. Open the httpd.conf file available in the following path: %ApcheHome%\Apache2.x.x\conf 5. Change the listen port from 80 to another port that is not a system port in the httpd.conf file. Example: Listen Depending on the version of the Apache web server you have installed, add one of the following lines in the httpd.conf file: For Apache web server 2.2.X: LoadModule weblogic_module modules/mod_wl_22.so For Apache web server 2.0.X: LoadModule weblogic_module modules/mod_wl_20.so 7. Add the following lines in the httpd.conf file: <IfModule mod_weblogic.c> WebLogicHost <Hostname\IPAddress of WebLogicServer> WebLogicPort <WebLogic Port > </IfModule> <Location /> SetHandler weblogic-handler </Location> 8. Start the Apache web server. 9. Access CenterStage URL using the following URL: <protocol>//<apachehost>:<listenport>/ <CenterStagePro>/#<RepositoryName> 10. After successful communication between Apache and WebLogic, add the following lines to the httpd.conf file for compression: LoadModule deflate_module modules/mod_deflate.so 62 EMC Documentum CenterStage 1.2 Installation Guide

63 Configuring HTTP compression LoadModule headers_module modules/mod_headers.so <Location /> SetOutputFilter DEFLATE # Netscape 4.x has some problems... BrowserMatch ^Mozilla/4 gzip-only-text/html # Netscape has some more problems BrowserMatch ^Mozilla/4\.0[678] no-gzip # MSIE masquerades as Netscape, but it is fine BrowserMatch \bmsie!no-gzip!gzip-only-text/html # NOTE: Due to a bug in mod_setenvif up to Apache # the above regex won't work. You can use the following # workaround to get the desired effect: #BrowserMatch \bmsi[e]!no-gzip!gzip-only-text/html # Don't use gzip for IE6, as it can cause the browser to hang SetEnvIf User-Agent ".*MSIE.6.*" no-gzip # Don't compress images SetEnvIfNoCase Request_URI \ \.(?:gif jpe?g png)$ no-gzip dont-vary # Make sure proxies don't deliver the wrong content Header append Vary User-Agent env=!dont-vary </Location> 11. Restart the ApacheServer and access CenterStage using the following URL: <protocol>://<apachehost>:<listenport>/<centerstagepro>/#<repositoryname> For more information, read the documentation available here: Enabling compression on the IBM WebSphere 7 application server Download the IBM HTTP server zip file (ihs.7000.windows.ia32.zip) from the following location: R&STACT=&S_CMP= To install the IBM HTTP server: 1. Extract the ihs.7000.windows.ia32.zip file and open the IHS folder and locate the Install.exe file. 2. Double-click Install.exe to install the IBM HTTP server. 3. Click Next. 4. Accept the license agreement and click Next. 5. Specify the path where you want to install the product and click Next. 6. Enter the ports or accept the default ports as 80 and 8008 and click Next. 7. Enter the credentials for IBM HTTP server administration and click Next. 8. Select the We do not wish to configure a IBM HTTP Administration server option and click Next and complete the installation. EMC Documentum CenterStage 1.2 Installation Guide 63

64 Configuring HTTP compression 9. Type or in the browser to verify whether the IBM HTTP server is working. If the server is working, the IBM HTTP server Welcome screen is displayed. Refer to the following link for instructions on IBM HTTP server installation: sites/screv_faq.nsf/docs/installing%20ibm%20http%20server To install the WebSphere or web server plug-in: 1. Download the WebSphere or web server plug-in (trial_plugins_7000_windows.ia32.zip) from the following location: &k=all&pid=&q=websphere+plugin&ibm-search=search&pf=&b=&q0= 2. Extract the contents of the zip file. 3. Go to the Plugin folder in the extracted file and double-click install.exe 4. Clear the selection of both check-boxes and click Next. 5. Click Next until you come to the Web Server Configuration page. 6. Select the IBM HTTP server option and click Next. 7. Select WebSphere appliction server machine (local) and click Next. 8. Enter the location where plug-ins must be installed and click Next. 9. Enter the WebSphere server location to enable the plug-in wizard to detect the location of the WebSphere plugin-cfg.xml file and click Next. 10. Select the profile and click Next. 11. Point the plug-in wizard to the location of the IHS conf directory so it can modify the httpd.conf file or leave it as default. Click Next. 12. Select the location of the plugin-cfg.xml file and click Next and Finish to complete the installation. To create a web server using the WebSphere Administration Console: 1. Open the Administration Console for WebSphere 7 application server and go to Servers. 2. Expand Server Types and select Web Servers. 3. Select New and provide the server name. 4. Select Type as IBM HTTP server and click Next. Note: Check for available port numbers by typing command netstat -a at the Command prompt. 5. Provide port number for the web server installation and valid locations for the plug-in. Ensure that the status is set to Started and verify the plug-in configuration by accessing the web server and click Plugin Properties. 6. Verify whether the correct path is created in the Plug-in logging and Plugin Properties attributes of the web server. 7. Verify the port for the IBM HTTP server in virtual hosts by accessing Environments in the Administrative Console. Alternatively, you can create a virtual host (Ex: 80, 81) as the default host. For instructions about installing the plug-ins, see the documentation available here: 64 EMC Documentum CenterStage 1.2 Installation Guide

65 Configuring HTTP compression 8. Restart the computer. 9. Start all servers (Oracle\SQL server, application server, Admin server, and IBM HTTP server). 10. Follow the steps for mapping the CenterStage module to the web server in the Manage Modules user interface and select both clusters to apply. 11. Save the settings. To generate and propagate the plug-in: 1. Select Servers > Server Types > Web Servers in the Administrative Console. 2. Click Generate Plugin button. 3. Click the Propagate Plugin button. The paths where the plug-in is generated and propagated are displayed. Note both paths. To ensure CenterStage works with IBM HTTP server and the plug-ins installed: 1. Open the Httpd.conf file available in the C:\Program Files (x86)\ibm\httpserver\conf\ path and add the following lines at the end of the file: LoadModule was_ap22_module <path of the mod_was_ap22_http.dll> WebSpherePluginConfig <path of the plugin-cfg.xml> Example: LoadModule was_ap22_module "C:/Program Files (x86)/ibm/httpserver/ Plugins/bin/mod_was_ap22_http.dll" WebSpherePluginConfig "C:/Program Files (x86)/ibm/websphere/appserver/ profiles/appsrv04/config/ cells/win2k8r2sp1-001node02cell/nodes/win2k8r2sp1-001node02/servers/ HTTPServer/plugin-cfg.xml" Note: The path of the.dll and.xml files are unique to your machine. Ensure that you copy the correct path of the files. Ensure the file paths have forward slashes. Perform the following steps if the files are not automatically generated at the locations: a. Copy the app_server_root/profiles/profile_name/config/cells/../../ nodes/../servers/web_server_name /plugin-cfg.xml file to to the web server host location which is Plugin_Install_Root/config/web_server_name/. Example: From C:\Program Files (x86)\ibm\websphere\appserver\profiles\appsrv04\config\cells\win2k8r2sp1-001node02cell\nodes\win2k8r2sp1-001node02\servers\httpserver to C:\Program Files (x86)\ibm\httpserver\plugins\config\httpserver b. Add the following line at the beginning of the httpd.conf file: AllowEncodedSlashes On c. Save the file and restart the machine. d. Start the Oracle\SQL server, application server, Admin server, and IBM HTTP server. e. Connect to CenterStage using the IBM HTTP port (80 or as defined in the Httpd.conf file and web server): EMC Documentum CenterStage 1.2 Installation Guide 65

66 Configuring HTTP compression Note: Ensure that both ports in the web server and httpd.conf file match, and the port defined in the admin.conf file is different. 2. Save the file. Note: For more information about configuring the web server, see the documentation available here: doc%2finfo%2fexp%2fae%2fcins_webserver.html To enable gzip on the WebSphere 7 application server: 1. Open the httpd.conf file and add the following lines : LoadModule deflate_module modules/mod_deflate.so DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio # log some info #LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate #CustomLog logs/deflate_log deflate # Insert filter SetOutputFilter DEFLATE # Netscape 4.x has some problems... BrowserMatch ^Mozilla/4 gzip-only-text/html # Netscape have some more problems BrowserMatch ^Mozilla/4\.0[678] no-gzip # MSIE masquerades as Netscape, but it is fine BrowserMatch \bmsie!no-gzip!gzip-only-text/html # Don't compress images SetEnvIfNoCase Request_URI \ \.(?:gifjpe?gpngexe)$ no-gzip dont-vary 2. Stop all servers and restart the computer by starting all the servers. 3. Connect to CenterStage through the IBM HTTP server to apply gzip compression. 66 EMC Documentum CenterStage 1.2 Installation Guide

67 Index A ADTS, 12 Advanced Document Transformation Services (ADTS). See ADTS application servers, 13 requiring EAR file, 26 requiring WAR file, 26 C cartridges, 12 CenterStage installation overview, 13 CenterStage components, 11 Composer, 11 configuration post-installation sequence, 39 space policy, 45 users, 41 to 42 Content Intelligence Services, 12 Content Server, 11 D DAR files and global repository, 22 Ant task deployment, 25 deployment overview, 22 installing using the DAR Installer, 23 list of required, 22 DAR Installer Plug-in, 23 DARs, 13 dce_room_creator role, 42 dfc.properties, 19 dmc_kw_manage_space_templates role, 43 docbroker, 19 documents related, 40 Documentum Administrator, 11 access, 40 Documentum Archive files (DARs). See DARs E EARs, 13, 26 installing, 27 preparing for deployment, 26 Enabling Kerberos authentication, 48 Enterprise Archive files (EARs). See EARs F FAST, 19 Federated Search Services (FS2), 17 FS2, 12, 17 Full-text indexing, 12, 19 G global registry, 19 global repository, 23 I installation post-install sequence, 39 pre-install sequence, 15 requirements, 15 installing DAR file using the DAR Installer, 23 DAR files using Ant task, 25 J JDK, updating, 27 M Media Transformation Services (MTS). See MTS EMC Documentum CenterStage 1.2 Installation Guide 67

68 Index members assign, 42 create, 41 MTS, 12 O open CenterStage, 44 P performance optimization, 55 settings, 55 R related documents, 40 requirements, installation, 15 role assign users, 42 dce_room_creator, 42 dmc_kw_manage_space_templates, 43 run CenterStage, 44 S single sign-on Kerberos, 48 Netegrity, 50 RSA, 49 SMTP server, 44 space policy, configuring, 45 T Thumbnail Generator, 12 transformation services ADTS, 12 MTS, 12 Thumbnail Generator, 12 troubleshooting, 53 U users assign, 42 create, 41 dce_room_creator role, 42 W WARs, 13, 26 Web Archive files (WARs). See WARs 68 EMC Documentum CenterStage 1.2 Installation Guide