Center Stage 1.0.2.102 Installation Guide

EMC ® Documentum ®
CenterStage
Version 1.0 SP1
Installation Guide
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748‑9103
1‑508‑435‑1000
www.EMC.com
Copyright © 2009 EMC Corporation. All rights reserved.
Published December 2009
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.
Table of Contents
Preface ................................................................................................................................. 5
Chapter 1 Preparation ................................................................................................... 7

Installation requirements ................................................................................... 7
Install Microsoft .NET Framework 2.0 or higher .................................................. 8
Pre‑installation requirements for Thumbnail Generator........................................ 8
Installing Microsoft Message Queuing ................................................................ 8
Enable ASP.Net on the server ............................................................................. 9
Using an external SQL 2005 database .................................................................. 9
Secure Sockets Layer (SSL) ................................................................................. 9
Gather information required for installation ....................................................... 10
Schedule time for the install (single‑host installer) .............................................. 11
Review troubleshooting notes ........................................................................... 11
Chapter 2 Singlehost Deployment .............................................................................. 13

Limitations of the embedded database ............................................................... 13
Repository limitations ................................................................................... 13
Full‑text indexing limitations......................................................................... 13
Using language packs with single‑host installation ......................................... 13
Installing CenterStage Essentials........................................................................ 14
Installing CenterStage Pro ................................................................................. 14
Verifying the installation ................................................................................... 16
Chapter 3 Multiplehost Deployment ........................................................................... 17

Deploying CenterStage DAR files using the Windows silent installer ................... 18
Deploying CenterStage DARs using an Ant Task ................................................ 19
Chapter 4 Upgrading from CenterStage 1.0 GA to CenterStage 1.0 SP1 ...................... 21

Chapter 5 Configuration .............................................................................................. 23
Update paths for log4j appender (multiple‑host install) ....................................... 23
Access Documentum Administrator .................................................................. 24
Set up CenterStage Indexes (multiple‑host install) .............................................. 24
Create a user in the repository ........................................................................... 25
Enable email notification for subscribed content ................................................. 26
Assign members to the dce_room_creator role .................................................... 26
Assign members to the dmc_kw_manage_space_templates role .......................... 27
Configure the administrator email address ......................................................... 27
Configure the embedded Content Server for SMTP ............................................. 28
EMC Documentum CenterStage 1.0 SP1 Installation Guide 3

Table of Contents
Configure Retention Policy Services (optional) ................................................... 28

Access CenterStage ........................................................................................... 29
Create a space .................................................................................................. 29
Configure the content policy for each space ........................................................ 30
Installing DARs with a localized data dictionary................................................. 30
Configuring high‑availability ............................................................................ 31
Chapter 6 Troubleshooting .......................................................................................... 33

Installation verification ..................................................................................... 33
Verify the CenterStage server has started............................................................ 33
Verify the Content Server installer completed successfully (single‑host) ............... 34
Verify the CenterStage OEM services started successfully (single‑host) ................ 35
Verify that thumbnail generator services started successfully............................... 35
Potential infinite loop scenario during installation .............................................. 36
Potential conflict with McAfee VirusScan ........................................................... 36
Services and logs .............................................................................................. 36
If logs are not being generated ....................................................................... 37
Version information .......................................................................................... 38
If filters are not populating in the Search tab....................................................... 38
If thumbnails are not appearing ......................................................................... 39
Disable the Windows 2008 firewall on user machines .......................................... 39
Troubleshooting CIS ......................................................................................... 40
Validate the installation of cis_artifacts.dar ..................................................... 40
Verify the required table has been created .................................................. 40
Test the entity extraction ............................................................................... 40
Entities are not extracted (CIS: Luxid) ............................................................ 41
Configuring WebLogic security ......................................................................... 42
Optimizing performance ................................................................................... 42
Performance settings for Oracle repository ..................................................... 42
Performance settings for MS SQL repository....................................................... 43
Chapter 7 Uninstalling CenterStage (Singlehost Install) ............................................. 45

Stop CenterStage services .................................................................................. 45
Uninstall CenterStage ....................................................................................... 46
Uninstalling the CenterStage plug‑in ................................................................. 46
Appendix A Test file for CIS entity extraction: EuropeanUnion.doc ............................... 49
4 EMC Documentum CenterStage 1.0 SP1 Installation Guide

Preface
This manual describes how to install CenterStage Essentials and CenterStage Pro.
• 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 the
CenterStage application.
Intended use of CenterStage singlehost

installer
The CenterStage single‑host installer is intended for departmental deployments, as well as
development and evaluation purposes.
CenterStage multiplehost installations

For multiple‑host installations, this guide covers the specific task of deploying the necessary
Documentum Archive files for the CenterStage application. For additional information on installing
the entire CenterStage system, see the CenterStage 1.0 SP1 System Deployment Guide.

Preface
Revision history
The following changes have been made to this document.
Revision Date Description

December 2009 Initial publication

Chapter 1
Preparation
CenterStage Pro and Essentials provide the primary user interfaces for interacting with the
CenterStage system. CenterStage Essentials provides a subset of functionality provided by
CenterStage Pro. Both CenterStage Pro and Essentials provide functionality for cross‑department
and/or company collaboration and data sharing through communities, spaces, wikis, blogs, and
RSS feeds.
CenterStage Pro and CenterStage Essentials are both deployed into an application server instance and
are accessed by end users through a browser.
There are two basic installation scenarios available for CenterStage. CenterStage Essentials and
CenterStage Pro can be deployed using a single‑host installer. CenterStage can be run on a single‑host
for evaluation, development, or departmental use.
For the enterprise, CenterStage should run 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). For a
description of the deployment process for the entire CenterStage system, see the CenterStage 1.0
SP1 System Deployment Guide.
This chapter gives pre‑installation information and describes pre‑installation tasks. These instructions
apply to both the CenterStage Essentials and the CenterStage Pro applications.
For an overview of the CenterStage system and in‑depth discussion of how to plan your deployment,
see the CenterStage System Planning Guide.
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. This will ensure sufficient performance for evaluation purposes.
• 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.

Preparation
Install Microsoft .NET Framework 2.0 or higher

Before installing CenterStage, the server host must have Microsoft .NET Framework 2.0 or later
installed. You can check to see if it already exists on the server by navigating to its directory on
your Windows Server 2003 system (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727). If the
directory does not exist, download and install Microsoft .NET Framework 2.0. You can download
the software from the URL http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77‑
E02C‑4AD3‑AACF‑A7633F706BA5&displaylang=en .
Preinstallation requirements for Thumbnail

Generator
Thumbnail Generator has the following requirements:
• Microsoft Windows as the operating system (2003 SP2). If you install CenterStage on Windows
2008, Thumbnail Generator is disabled.
• Microsoft Office (required) and any additional rendering applications listed in .NET Framework
2.0 (latest service pack)
http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77‑E02C‑4AD3‑AACF‑
A7633F706BA5&displaylang=en
• Internet Information Services (IIS)
http://www.microsoft.com/windowsserver2003/iis/default.mspx
• ASP.Net
http://www.asp.net/
• Internet Explorer 6.0 (or later)
http://www.microsoft.com/windows/products/winfamily/ie/default.mspx
• Microsoft Message Queue (MSMQ)
http://www.microsoft.com/windowsserver2003/technologies/msmq/default.mspx
For installation instructions, see Installing Microsoft Message Queuing, page 8.
Note: There are six optional components under Message Queuing (Active Directory Integration,
Common, Downlevel Client Support, MSMQ HTTP Support, Routing Support, and Triggers). The only
component required by Thumbnail Generator is Common.
Installing Microsoft Message Queuing

Microsoft Message Queue is a required third‑party product.
To install Microsoft Message Queuing

1. Select Start>Control Panel>Add or Remove Programs.

Preparation
2. Select Add/Remove Windows Components.

3. In the Components box, click Application Server.
4. Click Details.
5. Select the Message Queuing checkbox.
6. Verify that Application Server Console, Enable Network COM+ Access, Internet Information
Services (IIS), and Message Queuing are all selected.
7. Click OK.
Enable ASP.Net on the server

The Adlib services used by the Thumbnail Generator to create thumbnails for Office and PDF
documents require ASP.Net to be Allowed in IIS.
To enable ASP.NET on the server:

1. Select Start > All Programs > Administrative Tools > IIS Manager.
2. In IIS Manager, expand the server name in the left navigation panel.
3. Double‑click to open Web Service Extensions.
4. In the right panel, select the ASP.NET entry and select Allow.
5. Restart the server to implement the change.
Using an external SQL 2005 database

You have the option of using an external SQL 2005 SP2 database with the single‑host installer rather
than the embedded SQL Express database. If you choose to do so, you must install SQL 2005 SP2
client and connectivity tools on the host server to connect to the external database. The external
database must also use SQL 2005 SP2.
For more information, visit the Microsoft web site, http://www.microsoft.com/sqlserver/2005/en/
us/default.aspx.
Note: If you want to install language packs with single‑host installation, you will need to install using
an external database. The embedded SQL Express database cannot be used due to settings in the
pre‑configured repository.
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.

Preparation
For more information, see the EMC Documentum Content Server Administration Guide, Managing
User Authentication.
Gather information required for installation

The following information is required during installation:
Required information Description

Installation folder Location on the server where CenterStage will
be installed. Requires at least 16 GB of free
disk space. The default location is C:\Program
Files\EMC Documentum\CenterStage or
C:\Program Files\EMC Documentum\CenterStage
Pro, depending on the application you install.
Windows Administrative Account password Password that will be used for installed
components that require an administrative
account.
CenterStage Repository Name Repository name that is appropriate for
your user community. The default name is
documentum. This name cannot be changed in
the single‑host install.
SMTP Server Name 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 will use the
name or IP address of the computer hosting the
SMTP server to configure the Content Server
embedded with CenterStage.
SQL 2005 SA password (Single‑host install) (Optional) If you are planning to use an existing
SQL 2005 database for your repository, rather
than the embedded SQL Express database, you
will need the System Administrator password
for the SQL 2005 database.
ODBC Name (Single‑host install) (Optional) If you are planning to use an existing
SQL 2005 database for your repository, rather
than the embedded SQL Express database,
you will need the Open Database Connectivity
(ODBC) name for the datasource.

Preparation
Schedule time for the install (singlehost

installer)
In planning the best time to install CenterStage, consider that it might take up to three hours for the
installation to complete using the single‑host installer. This is because of system configuration
operations that the installer performs once the software components are installed. Schedule your
installation accordingly.
Review troubleshooting notes

Before you install, review Chapter 6, Troubleshooting. In particular, review the sections Potential
infinite loop scenario during installation, page 36 and Potential conflict with McAfee VirusScan, page
36 before beginning your installation.

Preparation

Chapter 2
Singlehost Deployment
This chapter describes how to install CenterStage using the single‑host installer, and how to optimize
post‑installation performance.
Limitations of the embedded database

The following are some important considerations when using the database embedded by the
single‑host installer.
Repository limitations
The database embedded with the single‑host installer has the SQL 2005 limitation of a maximum size
of 4GB for the repository database.
Fulltext indexing limitations

Full‑text indexing has the following limitations when using the embedded database:
• Only Latin1 languages can be indexed
• XML zone searching is not supported
• Indexing and query support is for exact matches only
• The content of ZIP files is not indexed
Using language packs with singlehost installation

If you want to install language packs with a single‑host installation, you will need to install using

Installing CenterStage Essentials

These are the instructions for installing CenterStage Essentials.
To install CenterStage Essentials:

1. On the server on which you plan to install CenterStage Essentials, log in as a server administrator
(the default administrator username typically is Administrator).
2. Extract the files from the CenterStage Essentials 1.0 Single Server Zip file.
3. Double‑click the CenterStage Essentials install icon.
4. Provide the information requested on each screen in the installation program, as described in
the following table:
Screen Action/Description
License Agreement Read and accept the license agreement.
Choose Install Folder Specify the local folder where CenterStage Essentials will be
installed. The default location is C:\Program Files\EMC
Documentum\CenterStage.
Required Information Enter the administrator’s password and the name of your
CenterStage Essentials repository. The default repository name
is documentum, and cannot be changed.
Database Options Choose whether the repository will reside in the embedded
SQL Express database, or in an existing SQL 2005 database.
Database Information If you choose to use an existing SQL 2005 database for the
repository, enter the SA (System Administrator) password and
the ODBC Datasource name.
Pre‑Installation Summary Review the install information and start the installation.
Installing CenterStage As the software installs, an animated status icon indicates that
the program is running.
Important: The installation might take up to three hours to

complete.
Confirmation Page This displays when the installation finishes. This indicates
a successful install, any warnings or errors encountered, and
the location of the installation logs. If warnings are displayed,
CenterStage Essentials has still installed successfully.
If the installation fails to complete, see Troubleshooting and Getting Help.
5. To avoid possible conflict with stale information, we recommend that you clear your Documentum
cache after installation. To do so, delete everything in the directory c:\Documentum\cache.
Installing CenterStage Pro

These are the instructions for installing CenterStage Pro.

To install CenterStage Pro:

1. On the server on which you plan to install CenterStage Pro, log in as a server administrator (the
default administrator username typically is Administrator).
2. Extract the files from the CenterStage Pro 1.0 Single Server Zip file.
3. Double‑click the CenterStage Pro install icon.
4. Provide the information requested on each screen in the installation program, as described in
the following table:
Screen Action/Description
License Agreement Read and accept the license agreement.
Choose Install Folder Specify the local folder where CenterStage Pro will be
installed. The default location is C:\Program Files\EMC
Documentum\CenterStage Pro.
Required Information Enter the administrator’s password and the name of your
CenterStage Pro repository. The default repository name is
documentum and cannot be changed.
Database Options Choose whether the repository will reside in the embedded
SQL Express database, or in an existing SQL 2005 database.
Database Information If you choose to use an existing SQL 2005 database for the
repository, enter the SA (System Administrator) password and
the ODBC Datasource name.
Pre‑Installation Summary Review the install information and start the installation.
Installing CenterStage As the software installs, an animated status icon indicates that
the program is running.
Important: The installation might take up to three hours to

complete.
Confirmation Page This displays when the installation finishes. This indicates
a successful install, any warnings or errors encountered, and
the location of the installation logs. If warnings are displayed,
CenterStage Pro has still installed successfully.
If the installation fails to complete, see Troubleshooting and Getting Help.
5. To avoid possible conflict with stale information, we recommend that you clear your Documentum
cache after installation. To do so, delete everything in the directory c:\Documentum\cache.
Note: When the confirmation page appears, wait approximately 5–10 minutes for the
installation process to complete. The installer issues the JBoss start command, and then exits.
JBoss will continue to start up in the background for a few minutes after the installation
completes. You can check the JBoss log to see when the server is running: <Documentum
Directory>\jboss4.2.0\server\DctmServer_MethodServer\log\server.log will have a message similar
to ʺStarted in 7m:37s:47msʺ when the server is fully started.

Verifying the installation

To verify the installation, see Chapter 6, Troubleshooting, which contains these verification
procedures:
• Installation verification, page 33
• Verify the CenterStage server has started, page 33
• Verify the Content Server installer completed successfully (single‑host), page 34

Chapter 3
Multiplehost Deployment
When deploying CenterStage in a multiple‑host environment, you deploy discrete elements of the
application on two or more servers. For a description of the deployment process for the entire
CenterStage system, see the CenterStage 1.0 SP1 System Deployment Guide. This chapter covers the
specific steps for deploying Documentum Archive (DAR) files required for CenterStage.
For CenterStage Essentials, the following DARs need to be installed in the order listed:
• Collaboration Services.dar
• DCS Attachments.dar
• CenterStage.dar
• CenterStageTemplates.dar
• Extended_Search‑Clustering.dar
• Rich_Media_Services.dar
• Transformation.dar
• cis_artifacts.dar
For CenterStage Pro, the following DARs need to be installed in the order listed:
• Collaboration Services.dar
• DCS Attachments.dar
• CenterStage.dar
• CenterStagePro.dar
• CenterStageTemplates.dar
• Extended_Search‑Clustering.dar
• Rich_Media_Services.dar
• Transformation.dar
• cis_artifacts.dar
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.

Deploying CenterStage DAR files using the

Windows silent installer
CenterStage server DAR files can be deployed from a Windows server using the program
darinstaller.exe. darinstaller.exe is installed with Composer and with Headless Composer.
To install a DAR file using darinstaller.exe

1. Navigate to the directory: Composer\plugins\com.emc.ide.external.dfc_1.0.0\documentum.
config, and back up the dfc.properties file.
2. On the Content Server, copy the dfc.properties file from the \Documentum\Config
directory. On the Composer host computer, paste that file into the directory
Composer\plugins\com.emc.ide.external.dfc_1.0.0\documentum.config.
3. Copy the DAR files that you need to deploy to the Composer machine.
4. In a CMD shell, go to the directory where Composer is installed: (example:
e:\Documentum\product\6.5\install\composer).
5. Type the command:
set JAVA_HOME={javaInstalldir}
For example:
set JAVA_HOME=E:\Program Files\java\1.5.0_12
6. Type the command

set PATH=%PATH%;{javaInstalldir}\bin
For example:
set PATH=%PATH%;E:\Program Files\java\1.5.0_12\bin
7. Type the command:

darinstaller.exe
The Composer splash screen appears.
8. When the DAR installer dialog appears, specify the appropriate configuration values for the
required fields (marked with an asterisk).
• DAR — browse to the location of the DAR you want to deploy.
• Docbroker Host — prepopulated with the connection broker name for your Content Server.
If this value is not correct, then the value in dfc.properties is not correct (see step 2). Press
the Connect button.
• Repository — after the connection is established, choose the correct Repository from the
drop‑down list.
• User Name — Type the user name for the account (Windows account) that was used to install
the Content Server.
• Password — Type the password for the account (Windows account) that was used to install
the Content Server.
9. Click Install. The DAR file is installed.

10. When the install is complete, review the log and verify that the install was successful. If the DAR
fails to deploy, save the log and contact Support for assistance.
11. Repeat these steps to deploy the remaining DAR files.
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.
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>


Chapter 4
Upgrading from CenterStage 1.0 GA to
CenterStage 1.0 SP1
This chapter provides specific instructions for upgrading an existing CenterStage 1.0 GA instance
CenterStage 1.0 SP1. These steps are essential to ensure optimal performance of the Recent Activity
widget and the space Filter view.
To upgrade from 1.0 GA to 1.0 SP1

1. 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 Deploying
CenterStage DAR files using the Windows silent installer, page 18.
a. Collaboration Services
b. DCS Attachments
c. CenterStage.dar
d. CenterStage_Pro.dar
e. CenterStageDatatable.dar (CenterStage ver. 1.1 and above)
f. CIS_Artifacts.dar
g. Extended_Search‑Clustering.dar
h. All other .dar files (optional/test .dars)
• Rich_Media_Services.dar (optional)
• Transformation.dar (optional)
• CenterStageTemplates.dar (optional)
• MEB_ObjectTypes.dar (test environment)
• SOATest_search.dar (test environment)
3. Again, use the Windows Services window to verify that the Documentum Java Method Server
is running.

Upgrading from CenterStage 1.0 GA to CenterStage 1.0 SP1
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.
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.

Chapter 5
Configuration
After installation, you must set up users and configure the system. Some of these tasks are performed
using Documentum Administrator. Unless otherwise noted, all of these configuration tasks apply to
both single‑ and multiple‑host deployments.
Perform the following tasks in the following order:
• Update paths for log4j appender (multiple‑host install), page 23
• Access Documentum Administrator, page 24
• Set up CenterStage Indexes (multiple‑host install), page 24
• Create a user in the repository, page 25
• Assign members to the dce_room_creator role, page 26
• Assign members to the dmc_kw_manage_space_templates role, page 27
• Configure the administrator email address, page 27
• Configure the embedded Content Server for SMTP, page 28
• Access CenterStage, page 29
• Create a space, page 29
• Configure the content policy for each space, page 30
Update paths for log4j appender (multiplehost

install)
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/centerstagelog.xml
log4j.appender.file.File=/temp/logs/centerstage.log
...

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

If you have installed the single‑host installer, to access Documentum Administrator, click the
Windows Start menu and select Programs > EMC Documentum > CenterStage Pro > Documentum
Administrator Login.
For both single‑ and multiple‑host deployments, you can start Documentum Administrator by going
to http://[machinename]:[port number]/da, where [machinename] is the fully qualified server name and
port number is the port on which Documentum Administrator is listening (port 9060 is used by the
single‑host installer). Log in with the install owner credentials. This is the Windows account that
was used to install CenterStage 1.0.
For information on using Documentum Administrator and on administering CenterStage Pro 1.0,
refer to the following documents, available on http://powerlink.emc.com:
• EMC Documentum CenterStage Administration Guide
• EMC Documentum Administrator Deployment Guide
• EMC Documentum Administrator User Guide
• EMC Documentum Administrator Release Notes
• EMC Documentum Content Server Administration Guide
• EMC Documentum Content Server Installation Guide
• EMC Documentum Media Transformation Services Administration Guide
Set up CenterStage Indexes (multiplehost

install)
After completing a multiple‑host install, it is important that you run the method
SetupCenterStageIndexes from Documentum Administrator. This method greatly improves the
performance of several common CenterStage queries, and is run automatically with the single‑host
installer. For a multiple‑host installation, the database administrator should run the method during a
time when the repository is not heavily being used, 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.
2. Navigate to Administration>Job Management>Methods

Configuration
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 email notifications when subscribed content changes,
enter the Email Address.
Note: For users to receive email notifications, you must also specify the SMTP server on the
Documentum platform, as described in Enable email notification for subscribed content, page 26.
5. Click OK.

Configuration
For more information on configuring users, refer to the following:

• The chapter on ʺUsers and Groupsʺ in the Documentum Content Server Administration Guide
• The chapter on ʺUser Managementʺ in the Documentum Administrator User Guide
Enable email notification for subscribed

content
For users to receive email 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 Email Address option in the user’s profile, as described in Create a user
in the repository, page 25 .
To specify the SMTP server that sends email 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.
If you are using the single‑host install, a command file allows you to assign the CenterStage
Installation Owner to the dce_room_creator role.
To assign the CenterStage Installation Owner to the dce_room_creator role:

1. Open a command prompt window.
2. Enter the command C:\OEMTEMP\addUsertoDceRoomCreatorRole.cmd.
For multiple‑host deployments, or to assign additional users to the role, follow these steps.
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.

Configuration
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.
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 email address

Configure the administrator email address for CenterStage in order to enable email notification of
events. There are two locations where you must update the email address using Documentum
Administrator.
To change the administrator email address using Documentum Administrator

1. Open Documentum Administrator
• Single‑host deployments can choose Start>All Programs>EMC
Documentum>CenterStage>Documentum Administrator login
• Single‑ or multiple‑host deployments can enter the URL [DA Host]:[DA Port]/da
in an Internet browser.
2. Navigate to Adminstration>User Management>Users.
3. Search for the user named Administrator
4. Right‑click the user and choose Properties....
5. In the field E‑mail address, replace “somebody@somebody.com” with the email address of
your system administrator.

Configuration
6. Click OK to save your changes.

7. Navigate to Cabinets>System>Applications>CenterStage.
8. Select the item app.xml and choose File>Edit.
9. Replace all instances of the email address cs_admin@yourcompany.com with the email address
of your system administrator. This email address appears in more than one place in the file
for localization purposes.
10. Save and check in the app.xml file.
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.5 Installation Guide, 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 SP1 DAR or later: 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.

Configuration
Access CenterStage
These are the instructions for accessing CenterStage Essentials or CenterStage Pro, either using the
Start menu shortcut or by entering the URL in a web browser.
To run CenterStage Essentials:

1. In a single‑host install, on the server on which it was installed, click the Windows Start menu and
select Programs > EMC Documentum > CenterStage Essentials> CenterStage Essentials Login.
2. At the login screen, type your Administrator username and the password specified during
installation.
3. Click OK.
Alternatively, you can access CenterStage Essentials through a web browser at:
http://[machinename]:[port]/CenterStage/#[repositoryname]
Where [machinename] is the fully qualified server name on which CenterStage Essentials has
been installed, [port] is the port on which CenterStage Essentials is listening for connections, and
[repositoryname] is the name of the repository. In a single‑host install, the default URL is:
http://[machinename]:9060/CenterStage/#documentum
To run CenterStage Pro 1.0:

1. In a single‑host install, on the server on which it was installed, click the Windows Start menu and
select Programs > EMC Documentum > CenterStage Pro > CenterStage Pro Login.
2. At the login screen, type your Administrator username and the password specified during
installation.
3. Click OK.
Alternatively, you can access CenterStage Pro through a web browser at:
http://[machinename]:[port]/CenterStagePro/#[repositoryname]
Where [machinename] is the fully qualified server name on which CenterStage Pro 1.0 has been
installed, [port] is the port on which CenterStage Essentials is listening for connections, and
[repositoryname] is the name of the repository. For a single‑host install, the default URL is:
http://[machinename]:9060/CenterStagePro/#documentum
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. Click the Spaces action to the right of the text search field in the top header.
2. Click the Create Space button.
3. Complete the Create Space dialog box and click OK.
CenterStage creates the new space and opens the space in a new tab.

Configuration
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 V1.0 and CenterStage Pro V 1.0 release. 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.
Core DAR file name Localized DAR Data Dictionary Language Pack
Collaboration Services.dar Collaboration_Dar_Language_Pack_6.5.0.221.
zip
CenterStage.dar CenterStage_Dar_Language_Pack_1.0.0.563.zip
CenterStage_Pro.dar CenterStage_Pro_Dar_Language_Pack_1.0.0.
563.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 Content Server Administration Guide version 6.

Configuration
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.
Note: For Single server installation, the DAR files are in C:\OEMTEMP\OEMTEMP.
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. Refer to the Documentum Composer User Guide, Version 6.5 SP1 for the steps to 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 51. 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 the ʺDocumentum Composer User Guide, Version 6.5 SP1
(pdf)ʺ for the steps to install the DAR files (Refer to the section ʺInstalling a DAR file with the DAR
Installer Plugin”). As per the instructions given in the section ʺInstalling a DAR file with the DAR
Installer Plugin” in the Composer User Guide, set the “Local Folder” parameter to the temp location
<temp>\<DAR name>\locales where you have unzipped the DAR Language Pack.
Note: For single‑host installation, Headless Composer and the DAR installer plug‑in are installed
in %DM_HOME%\install\composer\ComposerHeadless. Be sure to set JAVA_HOME path before
launching darinstaller.exe.
Note: If you want to install language packs with single‑host installation, you will need to install using
Configuring highavailability
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
[administration configuration] 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

Configuration
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 Load Balancing Recommended

Failover? Options Deployment Types
Yes No By IP Intranet deployments
No Yes (if session affinity By IP or by session Extranet deployments
is by session)

Chapter 6
Troubleshooting
This chapter identifies common installation issues and possible solutions.
Installation verification
Follow these steps to ensure that CenterStage has successfully completed installation.
To verify that a singlehost CenterStage Essentials installation completed

successfully:
1. Navigate to the installation directory. By default, the directory path is:
installation path \EMC Documentum\CenterStage
2. In a text editor, open install.log. This log records the success of the installation steps.
3. If you see any warning or errors, locate the error in the Install Log Detail section of the
log file.
To verify that a singlehost CenterStage Pro installation completed successfully:

1. Navigate to the installation directory. By default, the directory path is:
installation path \EMC Documentum\CenterStage Pro
2. In a text editor, open install.log. This log records the success of the installation steps.
3. If you see any warning or errors, locate the error in the Install Log Detail section of the
log file.
Verify the CenterStage server has started

To verify that the CenterStage server started up successfully, go the \Documentum\oem directory and
review DmServerOemService.log. The following message indicates that the server started successfully:
INFO | jvm 1 | date and time | All service components started successfully

Troubleshooting
Verify the Content Server installer completed

successfully (singlehost)
This procedure verifies that Content Server installed successfully and that all CenterStage components
installed successfully.
To verify CenterStage components installed successfully:

1. Navigate to C:\OEMTEMP.
2. In a text editor, open the install.log file, and verify that there are no errors reported.
3. For CenterStage Essentials, verify that the CenterStage.DAR file deployed successfully by
checking these log files in the install drive\Documentum\dba\config\repository name directory,
verifying that there are no errors reported:
• Collaboration Services_dar.log
• DCS Attachments_dar.log
• CenterStage_dar.log
• Extended_Search‑Clustering_dar.log
• Rich_Media_Services_dar.log
• Transformation_dar.log
• cis_artifacts_dar.log
For CenterStage Pro, verify that all of the required DAR files deployed successfully by checking
these log files in the C:\Documentum\dba\config\CenterStagePro directory, verifying that
there are no errors reported:
• Collaboration Services_dar.log
• DCS Attachments_dar.log
• CenterStage_dar.log
• CenterStage_Pro_dar.log
• CenterStageInstaller_dar.log
• Extended_Search‑Clustering_dar.log
• Rich_Media_Services_dar.log
• Transformation_dar.log
• cis_artifacts_dar.log
For both CenterStage Essentials and CenterStage Pro, if you chose to use an external SQL 2005
SP2 database, you should see these additional log files, and verify that no errors are reported:
• AdminAcess_dar.log
• DmsClient_dar.log
• LDAP_dar.log
• Lifecycle_dar.log

Troubleshooting
• MessaginApp_dar.log
• Presets_dar.log
• ResourceAgentsRegistry_dar.log
• RPS_dar.log
• Webtop_dar.log
• WebtopExpress_dar.log
• Workflow_dar.log
4. Ensure the OEM master services starts properly by verifying that the following completed
successfully:
• Creating master OEM service
• Starting OEM service
For more information, see Verify the CenterStage OEM services started successfully (single‑host),
page 35.
Verify the CenterStage OEM services started

successfully (singlehost)
If you are running a single‑host CenterStage instance, verify that the OEM services stated successfully.
To verify CenterStage 1.0 OEM services started successfully:

1. Navigate to:
C:\Documentum\oem
2. In a text editor, open the DmServerOemService.log.

3. Verify that there are no errors when starting the services.
Verify that thumbnail generator services

started successfully
Thumbnail generator requires Adlib services in order to display thumbnails of PDF and Microsoft
Office files.
To verify Adlib services started successfully

1. Open the Start>Control Panel>Administrative Tools>Services.
2. Verify that the following four services have started:
• Adlib Exponent Connector
• Adlib Exponent Manager

Troubleshooting
• Adlib Express Server

• Adlib FMR
3. If any of the services is not in the started state, start the service manually.
If you experience any problems starting these services, you can go to [Installation
Drive:]\Documentum\product\6.5\CTS\logs\DocumentTG_log.txt to review any errors.
Potential infinite loop scenario during

installation
If the single‑host installer download is corrupt or incomplete, there is a potential for the installer to go
into an infinite loop. If the install does not complete after a reasonable period of time (1–3 hours), we
recommend that the administrator cancel the install, delete the installation files, download a fresh
copy of the installer, and try the installation again.
Potential conflict with McAfee VirusScan

With McAfee VirusScan, there is an option that disallows the creation of autorun.inf files. When you
install CenterStage, and particularly during the install of SQLExpress, it is not possible to launch the
SQLExpress install process because it is not possible to extract the autorun.inf to the install folder. If
you are running McAfee VirusScan software, ensure that your McAfee Virus instance is configured to
allow the creation of autorun.inf files before you install CenterStage.
Services and logs

After installing and configuring CenterStage, the following services should appear as Started in
Administration Tools > Services:
• Documentum Content Transformation Monitor Services (Manual)
• Documentum Content Transformation Services (Manual)
• Documentum Docbase Service [RepositoryName] (Manual)
• Documentum Docbroker Service DocBroker (Manual)
• Documentum Java Method Server (Started)
• Documentum Master Service (Automatic)
• Documentum Content Intelligence Services (Automatic)
• aOAdminCenter — for Federated Search administration
• aOServer — for the Federated Search server

Troubleshooting
• For Content Intelligence Services entity extraction:

— Temis IDC Server v2
— Temis IDE Server v2
— Temis IDK Server v2
® Admin Server
— Temis Luxid®
® Annotation Node
— Temis Luxid®
® Annotation Server
— Temis Luxid®
® Default. TM360 Annotation Service
— Temis Luxid®
® SVN Service
— Temis Luxid®
® Vinci Naming Service
— Temis Luxid®
® Xelda Server
— Temis Luxid®
• For Thumbnail Generator:
— Adlib Exponent Connector
— Adlib Exponent Manager
— Adlib Express Server
— Adlib FMR
For debugging and troubleshooting purposes, collect all logs from these locations:
• C:\Documentum\jboss4.2.0\server\DctmServer_MethodServer\logs
• C:\Documentum\oem
• C:\Documentum\product\6.5\CTS\logs
• C:\Documentum\product\6.5\install\install.log
• C:\OEMTEMP\SetupErrors.log
• C:\Documentum\jboss4.2.0\server\serviceConfig\CIS\CmCISService.log
• <CIS installation directory>\log\server.log
• <CIS installation directory>\data\CIS\Logs\
• <FS2 installation directory>\www\logs
• <FS2 installation directory>\admin\logs
If logs are not being generated

If the log files search‑log.xml, centerstage.log, and acs.log are not being generated, the relative
path for the specified files is not being resolved. In this case, edit the <application server
directory>/CenterStagePro/WEB‑INF/classes/log4j.properties file, and uncomment and replace the
relative path, ${java.io.tempdir}, with the absolute path, /apps/appadmin/bea10/logs, in the following
lines (changes in bold):

Troubleshooting
log4j.appender.SEARCHXML.File=<application server directory>/CenterStage/

logs/searchlog.xml
log4j.appender.FILE.File=<application server directory>/CenterStage/logs/centerstage.log
log4j.appender.XMLFILE.File=<application server directory>/CenterStage/logs/centerstagelog.xml
log4j.appender.ACSFILE.File=<application server directory>/CenterStage/logs/acs.log
log4j.appender.ACSXMLFILE.File=<application server
directory>/CenterStage/logs/acslog.xml
Version information
The Read me.txt file contains version information for all CenterStage components. The file can be
found at: <install directory>/ OEMTEMP/OEMTEMP”
If filters are not populating in the Search tab

If filters in the Search tab are not populating with counts or values, there may be a problem with the
IndexAgent’s lock status. Look for the following error in the DmServerOemService.log (located
under \Documentum\oem):
java.lang.Exception: Application Server test failed.
INFO | jvm 1 | 2008/08/13 12:56:40 | at com.documentum.install
.servicewrapper.impl.Service.startComponent(Service.java:175)
.servicewrapper.impl.Service.startAll(Service.java:240)
.servicewrapper.impl.JavaServiceWrapperType3$StartupApplication
.run(JavaServiceWrapperType3.java:183)
INFO | jvm 1 | 2008/08/13 12:56:41 | Stopping all service components.
This error indicates that the Java Method Server failed to start. This might be due to a problem
releasing the IndexAgent lock.
To verify that the IndexAgent is locked, open the logfile IndexAgent1.log file, which is located under:
\Documentum\jboss4.2.0\server\DctmServer_MethodServer\logs. Search for a line that looks like this:
FATAL LIndexer [main][DM_INDEX_AGENT_PLUGIN] ERROR: Opening of index at
D:\Documentum\data\fulltext\lucene\IndexAgent1\index failed.
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out:
SimpleFSLock@D:\Documentum\data\fulltext\lucene\IndexAgent1
\index\write.lock
If you see this error in the IndexAgent1.log file, do the following to correct the problem:
1. Stop the CenterStage services, as described in Stop CenterStage services, page 45.
2. Go to \Documentum\data\fulltext\lucene\IndexAgent1\index.
3. Delete the file write.lock.
4. Go to \Documentum\jboss4.2.0\server\DctmServer_MethodServer\deploy\IndexAgent1.war\WEB‑
INF\classes.
5. Open the indexagent.xml file for editing and set the ʺforceUnlockʺ parameter to true, as shown here:
<parameter>
<parameter_name>forceUnlock</parameter_name>
<parameter_value>true</parameter_value>
</parameter>

Troubleshooting
6. Restart the CenterStage services.
If thumbnails are not appearing

If users upload files and the files are not being displayed as thumbnails within CenterStage, you
might need to restart the Documentum services. You must be a Windows administrator to perform
this procedure.
To enable viewing of thumbnails:

1. In the Windows Start menu, select Control Panel > Administrative Tools > Services.
2. Stop the following services in the order listed below. To stop each service, select the service
and select Action > Stop:
• Documentum Content Transformation Monitor Services
• Documentum Content Transformation Services
• Documentum Master Service
Note: Stopping the Documentum Master Service automatically stops other remaining services.
3. Wait for the services to stop before proceeding to the next step. This might take several minutes.
4. Once the services have stopped, restart the Documentum Master Service service.
5. Restarting the Documentum Master Service automatically restarts other services. Wait for the
following two services to be listed as started before proceeding to the next step. This might
take several minutes:
• Documentum Docbase Service repository name
• Documentum Docbroker Service DocBroker
6. Once the services have started, restart the Documentum Content Transformation Monitor
Services service.
Starting this service automatically starts the Documentum Content Transformation Services
service.
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.

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

Troubleshooting
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.
Entities are not extracted (CIS: Luxid)

After deploying CenterStage Pro using the single‑host installer, it might happen that entities are not
extracted because of a port conflict. The port conflict occurs between the Documentum service
DmServerDocumentum and one of the services of the entity extraction engine used by CIS: Luxid. If
this should happen, you need to modify the port used by the DmServerDocumentum service.
To modify the port used by the DmServerDocumentum service

1. Stop CenterStage services using the Documentum Master Service.
2. Stop Luxid services: in the notification area, right‑click the Temis Luxid Started icon and select
Stop Luxid.
3. Locate and open with the text editor the Services file:
C:\WINDOWS\system32\drivers\etc\Services
(The file has no format extension.)
4. Find the two lines:
dm_documentum 10000/tcp #Documentum Docbase Service documentum
dm_documentum_s 10001/tcp #Documentum Docbase Service documentum (secure service)
5. Modify the port numbers with port numbers that are not used, for example:
dm_documentum 10440/tcp #Documentum Docbase Service documentum
dm_documentum_s 10441/tcp #Documentum Docbase Service documentum (secure service)
6. Restart the Documentum Master Service.

7. Restart Luxid services.
If the ports listed in the Services file are not 10000 and 10001, then the issue is not due to a port
conflict, and you should look at the CIS logs to find out why the entities are not extracted.

Troubleshooting
After performing these steps, verify that CIS is working.
To verify that CIS is operational:

1. Check the CIS log file (C:\Documentum\jboss4.2.0\server\DctmServer_
CIS\data\CIS\Logs\cis.log). At the end of the file, look for something similar to the following:
INFO 20090729 10:11:07,472 com.documentum.cis.service.internal.
server.CISServerImpl [main] Credentials ok, repository available.
CIS server connecting...
2. If you do not see the line specified in the preceding item, restart the CIS service and check the
CIS log file again.
3. Verify that entity extraction is working by following the instructions described in Test the entity
extraction, page 40.
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.
====================================================================
<securityconfiguration>
.
.
.
<enforcevalidbasicauthcredentials>
false
</enforcevalidbasicauthcredentials>
</securityconfiguration>
====================================================================
Information about the WebLogic setting can be found at http://edocs.bea.com/wls/docs100/security/

thin_client.html in the section titled Understanding BASIC Authentication with Unsecured Resources.
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

The following are suggested settings to improve performance when using an Oracle repository.

Troubleshooting
The RETURN_TOP 350 DQL hint for recent activity causes performance issues on the Oracle
repository. In the server.ini file, update the value for return_top_results_row_based to false using
the following syntax to improve performance:
return_top_results_row_based=F
Another setting that will improve performance is to set Oracle 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.
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.
To set MS SQL ServerParameterization:

1. Open MS SQL Server Managemetn 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.

Troubleshooting

Chapter 7
Uninstalling CenterStage (Singlehost
Install)
To uninstall CenterStage on a single‑host install, perform these procedures in the following order:
1. Stop CenterStage services, page 45
2. Uninstall CenterStage, page 46
Stop CenterStage services

Begin by stopping all CenterStage services.
To stop CenterStage Essentials services:

• Documentum Docbase Server [RepositoryName]
• Documentum Java Method Server
To stop CenterStage Pro services:

• Documentum Docbase Server [RepositoryName]

Uninstalling CenterStage (Singlehost Install)

• Documentum Java Method Server
• EMC Documentum Content Intelligence Services
• aOAdminCenter
• aOServer
• Temis IDC Server v2
• Temis IDE Server v2
• Temis IDK Server v2
® Admin Server
• Temis Luxid®
® Annotation Node
• Temis Luxid®
® Annotation Server
• Temis Luxid®
® Default. TM360 Annotation Service
• Temis Luxid®
® SVN Service
• Temis Luxid®
® Vinci Naming Service
• Temis Luxid®
® Xelda Server
• Temis Luxid®
Uninstall CenterStage
To uninstall CenterStage, you must first stop all CenterStage Pro services as described in Stop
CenterStage services, page 45.
To uninstall CenterStage Essentials:

1. In the Windows Start menu, select Control Panel > Add or Remove Programs.
2. Select CenterStage.
3. Click Remove.
To uninstall CenterStage Pro:

1. In the Windows Start menu, select Control Panel > Add or Remove Programs.
2. Select CenterStage Pro.
3. Click Remove.
Uninstalling the CenterStage plugin

Individual users can remove the CenterStage plug‑in from their local browser.

To remove the CenterStage plugin

1. Close all browsers.
2. Remove persistent files on disk.
• If you are not using Webtop on the client machine, delete the Documentum folder on the client
machine (for example, ʺC:\Documents and Settings\[client log in name]\Documentumʺ).
• If you are using Webtop on the client machine, delete only the cta folder from the Documentum
folder on the client machine (for example, “C:\Documents and Settings\[client log in
name]\Documentum\cta).
3. In a Windows environment, remove the registry key \\HKCU\Software\Documentum
4. Delete the cookie kwclientinstall from the browser(s) that were used to access CenterStage.
Performing all four steps will return the client machine to a ʺcleanʺ state. In practice, step 3 can be
skipped. Step 4 is necessary in order to trigger the install mechanism from the browser when you
use it to visit a CenterStage location.


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

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

Index
A L
Adlib, 9, 35 Latin1 languages, 13
ASP.Net, 8 to 9 logs
list of, 36
Luxid
C Troubleshooting, 41
configuration
post‑installation sequence, 23
space policy, 30 M
users, 25 to 26 members
assign, 26
create, 25
D Microsoft Message Queue (MSMQ), 8
dce_room_creator
role, 26
dmc_kw_manage_space_templates O
role, 27 OEM services
documents verify startup, 35
related, 24 open
Documentum Administrator CenterStage Pro, 29
access, 24
P
F Performance optimization, 42
filters
not populating, 38
R
related documents, 24
I repository
IIS, 8 to 9 name, 10, 14 to 15
installation requirements
information required beforehand, 10 installation, 7
install, 13 pre‑install information, 10
location for, 10 role
post‑install sequence, 23 assign users, 26
pre‑install sequence, 7 dce_room_creator, 26
requirements, 7 dmc_kw_manage_space_templates, 27
schedule, 11 run
verify, 33 to 34 CenterStage Pro, 29
Internet Information Services (IIS), 8 to 9

Index
S U
server uninstall, 45
verify startup, 33 users
services assign, 26
list of, 36 create, 25
start and stop, 46 dce_room_creator role, 26
stop, 45
SMTP server, 28
SMTP Server, 10
V
space policy verify
configure, 30 installation, 33 to 34
SQL 2005, 10, 13 to 15 OEM services started, 35
server started, 33
T
Thumbnail generator
X
Troubleshooting, 35 XML zone searching, 13
thumbnails, 39
troubleshooting, 33

Center Stage 1.0.2.102 Installation Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Center Stage 1.0.2.102 Installation Guide

Transféré par

Droits d'auteur :

Formats disponibles

EMC ® Documentum ®

Chapter 1 Preparation ................................................................................................... 7

Chapter 2 Single­host Deployment .............................................................................. 13

Chapter 3 Multiple­host Deployment ........................................................................... 17

Chapter 4 Upgrading from CenterStage 1.0 GA to CenterStage 1.0 SP1 ...................... 21

EMC Documentum CenterStage 1.0 SP1 Installation Guide 3

Conﬁgure Retention Policy Services (optional) ................................................... 28

Chapter 6 Troubleshooting .......................................................................................... 33

Chapter 7 Uninstalling CenterStage (Single­host Install) ............................................. 45

Appendix A Test ﬁle for CIS entity extraction: EuropeanUnion.doc ............................... 49

4 EMC Documentum CenterStage 1.0 SP1 Installation Guide

Intended use of CenterStage single­host

CenterStage multiple­host installations

EMC Documentum CenterStage 1.0 SP1 Installation Guide 5

Revision Date Description

6 EMC Documentum CenterStage 1.0 SP1 Installation Guide

EMC Documentum CenterStage 1.0 SP1 Installation Guide 7

Install Microsoft .NET Framework 2.0 or higher

Pre­installation requirements for Thumbnail

Installing Microsoft Message Queuing

To install Microsoft Message Queuing

8 EMC Documentum CenterStage 1.0 SP1 Installation Guide

2. Select Add/Remove Windows Components.

Enable ASP.Net on the server

To enable ASP.NET on the server:

Using an external SQL 2005 database

Secure Sockets Layer (SSL)

EMC Documentum CenterStage 1.0 SP1 Installation Guide 9

Gather information required for installation

Required information Description

10 EMC Documentum CenterStage 1.0 SP1 Installation Guide

Schedule time for the install (single­host

Review troubleshooting notes

EMC Documentum CenterStage 1.0 SP1 Installation Guide 11

12 EMC Documentum CenterStage 1.0 SP1 Installation Guide

Limitations of the embedded database

Full­text indexing limitations

Using language packs with single­host installation

EMC Documentum CenterStage 1.0 SP1 Installation Guide 13

Installing CenterStage Essentials

To install CenterStage Essentials:

Important: The installation might take up to three hours to

Installing CenterStage Pro

14 EMC Documentum CenterStage 1.0 SP1 Installation Guide

To install CenterStage Pro:

Important: The installation might take up to three hours to

EMC Documentum CenterStage 1.0 SP1 Installation Guide 15

Verifying the installation

16 EMC Documentum CenterStage 1.0 SP1 Installation Guide

EMC Documentum CenterStage 1.0 SP1 Installation Guide 17

Deploying CenterStage DAR ﬁles using the

To install a DAR ﬁle using darinstaller.exe

6. Type the command

7. Type the command:

18 EMC Documentum CenterStage 1.0 SP1 Installation Guide

Deploying CenterStage DARs using an Ant

Parameter Required Description

EMC Documentum CenterStage 1.0 SP1 Installation Guide 19

20 EMC Documentum CenterStage 1.0 SP1 Installation Guide

To upgrade from 1.0 GA to 1.0 SP1

EMC Documentum CenterStage 1.0 SP1 Installation Guide 21

Update: Updating RoomAspect attribute a_modify_date successful.

5. Using DA, run the SetupCenterStageIndexes method.

22 EMC Documentum CenterStage 1.0 SP1 Installation Guide

Chapter 2 Singlehost Deployment .............................................................................. 13

Chapter 3 Multiplehost Deployment ........................................................................... 17

Chapter 7 Uninstalling CenterStage (Singlehost Install) ............................................. 45

Intended use of CenterStage singlehost

CenterStage multiplehost installations

Preinstallation requirements for Thumbnail

Schedule time for the install (singlehost

Fulltext indexing limitations

Using language packs with singlehost installation

Update paths for log4j appender (multiplehost

Set up CenterStage Indexes (multiplehost

Example 51. Example

To verify that a singlehost CenterStage Essentials installation completed

To verify that a singlehost CenterStage Pro installation completed successfully: