Académique Documents
Professionnel Documents
Culture Documents
Installation Guide
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.emc.com
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.
Table of Contents
Preface
Chapter 1
Chapter 2
................................................................................................................................ 11
Planning for Content Server Installation
..................................................... 13
13
13
15
15
17
17
18
18
18
19
19
20
20
21
22
23
......................................
Host preparation checklist ................................................................................
Hardware and network environment requirements ............................................
Internationalization settings ..............................................................................
Server host code page ...................................................................................
Firewalls ..........................................................................................................
Setting up user accounts ...................................................................................
Setting up the installation owner account .......................................................
Installation owner account naming requirements ........................................
Required rights for an installation owner account .......................................
Setting up the repository owner account ........................................................
Repository owner account naming requirements ........................................
Setting up repository user accounts ...............................................................
Preparing UNIX and Linux hosts .......................................................................
Shared memory and semaphore requirements ................................................
XWindows requirement ................................................................................
The /tmp directory ........................................................................................
Root user password ......................................................................................
Setting Documentum environment variables ..................................................
Setting up the services file .............................................................................
Preparing Windows hosts .................................................................................
Setting the PATH Environment Variable .........................................................
Running WDK Applications on the Content Server Host .................................
Restricted Characters ....................................................................................
25
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
25
27
28
28
29
29
29
29
30
30
30
31
31
31
31
32
32
32
33
34
34
34
35
Table of Contents
35
35
35
..............................
Database preparation checklists .........................................................................
Requirements for all databases ..........................................................................
Database code page ......................................................................................
Database locales ...........................................................................................
Semantics .....................................................................................................
Database service on Windows .......................................................................
Repository owner account .............................................................................
Database administrator account.....................................................................
Oracle requirements .........................................................................................
Entries in tnsnames.ora file............................................................................
Oracle repository sizes ..................................................................................
SQL Server requirements ..................................................................................
Configuring an ODBC Data Source for SQL Server .........................................
Configuring a 32bit repository on 64-bit SQL server .................................
SQL Server repository sizes ...........................................................................
Sybase requirements .........................................................................................
Sybase repository sizes .................................................................................
DB2 requirements .............................................................................................
Configuring a DB2 database ..........................................................................
Configuring DB2 from the Control Center ..................................................
Configuring a DB2 database from the command line...................................
DB2 performance wizard requirements ..........................................................
Tuning a DB2 database..................................................................................
Running multiple Content Servers on the DB2 host .........................................
DB2 repository sizes .....................................................................................
37
Chapter 4
55
55
Chapter 5
Chapter 6
Chapter 7
Chapter 3
40
40
41
41
41
41
42
42
43
44
44
44
45
45
46
46
47
48
48
49
51
51
52
53
....................... 59
............................... 63
Chapter 8
Chapter 9
37
67
............ 73
......................................................................... 79
79
80
80
81
81
82
82
83
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Table of Contents
Chapter 10
83
84
84
84
84
........................................................................... 87
87
90
91
91
91
92
93
94
94
97
97
98
99
101
101
Chapter 11
Chapter 12
Chapter 13
Chapter 14
..................................................... 105
......................................................................
Order of uninstalling components ...................................................................
Deleting a repository ......................................................................................
Deleting a connection broker ...........................................................................
Uninstalling the Content Server software .........................................................
107
107
108
109
109
111
111
112
114
116
119
119
120
121
121
122
123
124
124
124
125
125
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Table of Contents
Chapter 15
Chapter 16
Chapter 17
125
Preinstallation requirements............................................................................
125
125
126
129
131
132
........................
Overview .......................................................................................................
Choosing a configuration ................................................................................
Preinstallation requirements............................................................................
Configuring an active/passive cluster ...............................................................
Creating the cluster resource group .............................................................
Installing Content Server software on the nodes ...........................................
Configuring Content Server.........................................................................
Configuring the connection brokers .............................................................
133
134
136
137
137
138
138
143
144
145
146
146
147
147
147
147
148
148
148
151
151
153
..........................................
Creating the test environment .........................................................................
Precopying tasks ............................................................................................
Copying a repository ......................................................................................
155
155
156
157
................................ 161
Appendix A
Appendix B
133
163
163
163
164
164
164
164
164
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Table of Contents
share .........................................................................................................
Additional directories .................................................................................
Scripts run during installation or upgrade ....................................................
Configuration objects ..................................................................................
Appendix C
Appendix D
Appendix E
165
165
168
171
.......................................... 173
Identifying the problem and resolution ............................................................ 173
176
176
177
177
178
...............................
Type categories for tablespace specifications .....................................................
Type categories for extent allocation ................................................................
Object types categorized as large .................................................................
Object types categorized as small .................................................................
Object types categorized as default ..............................................................
181
181
182
182
182
183
185
186
186
186
187
188
189
189
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Table of Contents
List of Figures
Figure 1.
Figure 2.
16
Figure 3.
120
Figure 4.
122
Figure 5.
123
Figure 6.
124
Figure 7.
126
Figure 8.
129
Figure 9.
130
Figure 10.
135
Figure 11.
Active/active cluster............................................................................................
136
14
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Table of Contents
List of Tables
Table 1.
25
Table 2.
37
Table 3.
38
Table 4.
............................................
SQL Server database installation and configuration checklist ..................................
Sybase database installation and configuration checklist .........................................
Content Server installation and configuration checklist ...........................................
Content Server upgrade checklist ..........................................................................
Update Statistics arguments ..................................................................................
Parameters required by dm_acs_install.ebs script .................................................
Precopying tasks ................................................................................................
Required environment variables ..........................................................................
Subdirectories created during installation ............................................................
Repository configuration scripts ..........................................................................
Troubleshooting checklist ....................................................................................
39
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
39
40
56
87
98
115
156
161
166
168
173
Table of Contents
10
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Preface
Purpose of the manual
This guide contains information and instructions you need to install or upgrade EMC Documentum
Content Server.
If you are installing full-text indexing, consult the xPlore Installation Guide.
Intended audience
This guide is for system administrators who are responsible for the installation of Content Server.
Revision history
The following revisions have been made to this document:
Revision History
Date
Description
April 2011
Initial publication
June 2012
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
11
Preface
12
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 1
Planning for Content Server Installation
This chapter contains the information you need to plan a Content Server installation or upgrade. This
chapter contains the following topics:
Important changes for 6.7, page 13
Content Server and repository overview, page 13
Content Server installation models , page 15
Basic installation model, page 15
Configuration decisions, page 17
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
13
tables within a relational database, and full-text indexes. A repository can store its content files in
any of the following:
Directories on the Content Server hosts file system
Directories on a remote host to which Content Server has access
A variety of storage devices including retention type stores, such as EMC Centera and Network
Appliance SnapLock
Content Server coordinates the different forms of data to create the object-based repository. Objects
in a repository are composed of content files (the source file in its native format) and attributes (also
known as metadata or properties), such as document owner, version, and creation date. Metadata
describes the content and the relationships between this content and other objects in the repository. A
repository uses the metadata to organize the content, and users can use metadata to search for content.
Metadata is stored in tables in a relational database as sets of attributes. A configurable and extensible
set of attributes is stored for each item. A set of attributes can include attributes with a single value,
such as the documents globally unique identifier. Attributes can also have multiple values, such as
keywords that describe the content.
Figure 1, page 14 shows the basic structure of a repository.
Figure 1. Repository structure
Even though Content Server is composed of several components, details of how content is stored in
the repository is hidden from client applications. Content Server treats the content files and metadata
as part of a single entity and handles updates to the document object as a single transaction: Content
Server updates both elements in concert or updates neither of them. Content Server automatically
updates the index entries as well, ensuring that the three types of data remain synchronized.
14
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
15
You can install and start a connection broker on the Content Server host as part of the installation
process, or the Content Server can project to one or more connection brokers located on a different
host, thereby making itself available to client applications. Chapter 4, Pre-Installation Checklist
provides details on installing and starting a connection broker. When a client application wants to
connect to a repository, the following occurs:
1.
The client contacts the connection broker and requests the information it needs to connect with a
Content Server for the requested repository.
2.
The connection broker sends back the IP address for the host on which the Content Server resides
and the port number that the Content Server is using.
3.
The client application uses that information to open a connection to Content Server.
Client applications communicate with Content Server through its programming interface, DFC.
Content Server also uses an SMTP server to send tasks and notification messages to user mailboxes
when necessary.
The file stores, relational database, SMTP server, and license server must be installed and available
before you install Content Server.Chapter 2, Preparing the Host for Content Server Installation
contains information about the steps to take to prepare to install Content Server. Content Server does
not function properly unless the database is installed correctly. Review the requirements in Chapter
3, Preparing the Database for Content Server Installation, and ensure that the database installation
meets these requirements. The SMTP server can be on the Content Server host or a remote host.
During the installation procedure, you provide the name or IP address of the computer hosting the
SMTP server so that Content Server can connect to it. Like the SMTP server, the license server can
be on the Content Server host or a remote host. During configuration of the global repository, you
16
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
provide the name or IP address of the license server host, and the port on which the license server
listens, so that Content Server and client applications can connect to it.
The installation or deployment guide for the application, such as the Documentum Web Development
Kit and Webtop Deployment Guide, contains information about installing client applications.
Configuration decisions
When you install Content Server, you are asked to make several configuration decisions. The
remainder of this chapter identifies the decisions you should make before beginning the Content
Server installation procedure. Chapter 3, Preparing the Database for Content Server Installation
and Chapter 4, Pre-Installation Checklist provide checklists where you can record your decisions
for reference during the installation procedure.
Location for installing the relational database, page 17
Username Content Server will use to connect to the database, page 18
Size of repository to create, page 18
Location for storing the content files, page 18
Name and ID to assign to the repository, page 19
Connection brokers to which to project Content Server information, page 19
Permit or require secure SSL connections, page 20
Ports to reserve for Content Server use, page 21
Repository to use as the global registry, page 23
Extended service features to license, page 22
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
17
Chapter 3, Preparing the Database for Content Server Installation provides details about installing
the relational database.
18
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
19
Authenticate users
User authentication typically occurs when a user attempts to connect to a repository. Content Server
determines whether the user is a valid, active repository user and, if so, authenticates the user name
and password. You can perform user authentication using one of the following methods:
The default mechanism
20
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
The default mechanism authenticates the user against the operating system.
A custom dm_check_password program
You can create a custom password checking program and set up the servers to call that program
for user authentication. This option is useful if you want to use Windows domain authentication
for UNIX users.
An LDAP directory server
If you use a directory server, you have the following options:
Authenticate against the directory server directly, using a secure or a nonsecure connection.
Authenticate using an LDAP-enabled dm_check_password program.
An authentication plugin
Authentication plugins provide an alternate way to customize user authentication. EMC
Documentum provides one authentication plugin with Content Server. The following plugins
are included with Content Server:
Netegrity SiteMinder Policy Server
RSA
Kerberos
Plugins support Web-based Single Sign-On (SSO) and strong authentication.
An inline password
A user can be authenticated using an encrypted password that is stored in the user_password
attribute of the user object.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
21
22
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
23
Before you configure a repository Determine whether the repository you create will be a global
registry. If you are installing a single production repository, designate it as a global registry. If the site
has multiple production repositories, designate only one repository as a global registry.
To designate a new repository as a global registry, provide a username and password for the global
registry user in the current repository. Client applications and other repositories will use this login
name and password to connect to the global registry. Record the username and password so that
you can provide it when installing other EMC Documentum products that require global registry
access. The global registry user must have read access to objects in the /System/Modules and
/System/NetworkLocations folders. Do not use the repository owners credentials or the installation
owners credentials. The password you assign to the global registry user will also be automatically
assigned to the user named dm_report_user. This user can access the usage tracking information
stored in the global registry. The passwords for these users do not have to remain the same.
If you plan to connect to an existing global registry repository, provide the repository name, the
username, and the password of the global registry user in that repository. The current repository is
configured to access the remote global registry repository.
The Content Server configuration program gives you the option to designate the global registry
repository at a later time. If you select this option, use Documentum Administrator to identify
the global registry and enter the appropriate connection information. The EMC Documentum
Administrator User Guide provides instructions.
24
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 2
Preparing the Host for Content Server
Installation
Use the information in this chapter to prepare the host on which you plan to install Content Server.
Chapter 3, Preparing the Database for Content Server Installation contains additional information for
preparing the relational database for Content Server.
This chapter contains the following information:
Hardware and network environment requirements, page 27
Internationalization settings, page 28
Setting up user accounts, page 29
Preparing UNIX and Linux hosts, page 31
Task
Resource
Value
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
25
Task
Resource
SMTP hostname:
__________
26
Value
root password
__________
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Task
Resource
Value
domain name
__________
port number:
__________
port number:
__________
hostname:
__________
Disabling User Access Control
(UAC), page 35
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
27
Internationalization settings
Content Server runs in the UTF-8 code page. Perform the following tasks before Content Server
installation:
Install the server host code page.
Set the code page in the database.
Set the server host locale.
The server host locale and the server code page do not have to be the same. For example, if
the host code page is set to ISO-8859_1, the host locale would typically be set to a European
language (English, French, German, Italian, Portuguese, or Spanish). If the host locale is set to
French, a client that connects to the Content Server without specifying a client locale is served
French data dictionary labels.
If the host locale is one of the languages supported by EMC Documentum, the data dictionary
information for that locale is loaded. Otherwise, the server defaults to loading the English
data dictionary information. You can load additional sets of data dictionary information by
modifying the data_dictionary.ini file. Installing additional data dictionary information can
affect server performance, and EMC Documentum only supports the languages that are shipped
with Content Server. The EMC Documentum Administrator User Guide provides information on
leading additional data dictionary information.
On Windows hosts, the host locale is set in the Regional Settings dialog box.
On UNIX and Linux hosts, the host locale is set with the LANG environment variable.
Database code page, page 40 contains information about setting the database code page. EMC
Documentum Content Server Fundamentals provides complete information on Content Server
internationalization.
28
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Firewalls
Typically, the server-side components of Content Server, such as index server, index agent, and
Documentum Administrator, must be behind a firewall. Only the client side applications, such as
Webtop and the connection broker are supported outside the firewall.
For clients and a connection broker outside of a firewall, you need to use connection broker IP
translation as described in the EMC Documentum Administrator User Guide, Appendix G.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
29
30
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
The repository owners password must consist of letters, numbers, dashes, underscores, or periods.
XWindows requirement
XWindows must be installed on the UNIX host to run the graphical installation program, and the
xterm program must be in the installation owners path. The xterm program may be installed
in various locations depending on the operating system and software packages installed. Some
typical locations are:
On Solaris, /usr/openwin/bin
On HP-UX and AIX, /usr/bin/X11
Verify that the xterm program is in one of the preceding paths or in an alternate location and add
that location to the PATH variable.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
31
32
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
If NIS is running, the local services file (/etc/services) is ignored. Place the entries in the NIS services
map. Use the ypwhich command to identify the hostname of the NIS master server, if there is one.
The port numbers can be any unused port numbers greater than 1024. UNIX reserves port numbers
up to 1024 for system use. For example, if the repository service were named "lime, the services
file entries might be:
lime
1497/tcp # 6.5 Repository native connection
lime_s 1498/tcp # 6.5 Repository secure connection
If the correct services file entries are not present, the installer stops.
If you have multiple repositories on a single host, create a services file entry for each repository.
Ensure that the repositories have different names and port numbers.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
33
2.
Select Properties
3.
4.
5.
6.
7.
34
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
For more information, refer to the EMC Documentum Web Development Kit and Webtop Deployment
Guide.
Restricted Characters
The name of the directory in which Content Server is installed can only contain ASCII characters.
Additionally, do not use the following characters in path names accessed by EMC Documentum
product installers: ! \ / : * ? " < > |
Do not use spaces in the name of the product installation directory. For example, do not use
c:\Documentum Products\ or /Documentum Products as the name of the installation directory.
Regional Settings
Before you install a repository, the Windows Regional Settings must be set to specify a four-digit date.
3.
4.
Select a date style that includes a four-digit year from the dropdown list.
5.
Click Ok.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
35
2.
3.
Uncheck the option Use User Account Control to help protect your computer.
4.
Click OK.
36
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 3
Preparing the Database for Content
Server Installation
This chapter contains information on configuring the database for Content Server installation. For
details about installing or supporting a database, refer to the database administrator or the database
vendors documentation. This chapter contains the following topics:
Database preparation checklists, page 37
Requirements for all databases, page 40
Oracle requirements, page 42
SQL Server requirements, page 44
Sybase requirements, page 46
DB2 requirements, page 47
Task
Resource
Database documentation
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Value
datafile size:
__________
37
Task
Resource
Value
Database documentation
"Database administrator
account, page 42 and the
database administrator
database administrator
name:
__________
database administrator
password:
__________
Install the database instance with
the UTF-8 code page.
Database documentation
Task
Resource
Oracle documentation
Oracle documentation
Oracle documentation
38
Value
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Task
Resource
DB2 documentation
Value
1208
Task
Resource
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Value
39
Task
Resource
Value
Task
Resource
Sybase documentation
Value
40
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Database locales
Typically, Content Server is installed on the English version a database. However, Content Server
installation is also supported on localized databases if the database fulfills the following criteria:
Database supports internationalization of locales (I18N)
Database and adheres to I18N standards
Content Server installation is done with UTF8 and case sensitive (SQL)
Semantics
Content Server installation requires a database server to use byte-length semantics.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
41
The account must have the appropriate privileges to perform the following tasks:
Connect to the database.
Create tables, views, and indexes in the database.
Insert records (rows) into the tables.
Drop tables, views, and indexes.
The names of the privileges depend on the RDBMS. If you create the account before running the
installer, give the account these privileges:
On Oracle, the repository owner must have Connect and Resource privileges. The Resource
privilege encompasses creating and maintaining database objects. The repository owner also
must have permission to create any view, resource, and unlimited tablespace. The tablespace
created by the repository owner for tables or indexes must be designated the default, while the
standard Oracle temporary tablespace must be the default for any temporary tables that the
repository owner creates. The name of the temporary tablespace needs to be valid for the Oracle
configuration used. The default name is either temporary_data or temp, depending on which
Oracle version is used.
The repository must also have the Select Catalog Role privilege.
On DB2, grant use of tablespaces, list tablespace, and connect to database privileges.
On DB2, the repository owner does not have an account. The repository owner is created when
you grant the required privileges to an existing operating system account.
On all supported SQL Server versions, the repository owner must be able to access tempdb, and if
the account is created before running the installer, the user must own all tables and views. Ensure
that the repository owner has the Create Any Database privilege.
On Sybase, the repository owner must be able to execute procedures and update statistics.
If you allow the Content Server Setup program to create a database account for the repository owner,
the proper privileges are granted to the repository owner automatically.
Oracle requirements
Note: In release 6.7, for UNIX and Linux, we changed the way we link to the Oracle Client library.
Prior to 6.7 we linked statically to the 32bit Oracle Client library. In 6.7 we do not link with the
32bit Oracle Client library at build time, we dynamically link it in to the running process at
runtime. Therefore, you must install a 32bit Oracle Client on the Content Server host, and add the
directory containing the client libraries to the appropriate environment variable (SHLIB_PATH for
HPUX, LIBPATH for AIX or LD_LIBRARY_PATH for Linux and Solaris) of the repository owner
42
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
before configuring or starting Content Server. You must install the 32bit Oracle Client even if you
successfully used the 64bit Client with an earlier release.
For HPUX-IA64, after installing the 32bit Client, you must create a symbolic link from the library file
to libclntsh.o. For example:
ln -s libclntsh.so.11.1 libclntsh.o
The actual version number of the library will depend on the client you have installed.
The Oracle RDBMS must meet these requirements:
On UNIX and Linux, ensure that these environment variables are set in the installation owners
environment:
ORACLE_HOME
TNS_ADMIN
ORACLE_SID
This environment variable points to the location of the tnsnames.ora file. The Content Server
installation program looks first for TNS_ADMIN, then for ORACLE_HOME, in order to locate
the tnsnames.ora file.
For UNIX and Linux hosts, install the 32bit Oracle Client package on the Content Server host and
update the value of the shared library path environment variable (appropriate to your operating
system) to include the library directory. For Windows, install a 32bit client package for a 32bit
Content Server; install a 64bit client package for a 64bit Content Server.
If you see this error, modify the database_conn key in the server.ini file and continue with the
installation or upgrade.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
43
44
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
2.
Use the 32-bit ODBC Data Source Administrator tool, which is available at
C:\Windows\SysWOW64\odbcad32.exe.
After the DSN is set, the data source drop-down list is populated.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
45
Sybase requirements
The Sybase RDBMS installation must meet these requirements:
In the $SYBASE/$SYBASE_ASZserver_name.cfg file, set the following system parameters to the
values shown.
number of
number of
number of
number of
procedure
number of
46
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
In a medium or large repository on Sybase, you can change the device size and the log file size
for the database.
A medium Sybase repository has a datafile size of 180 MB and a log file size of 180 MB.
A large Sybase repository has a datafile size of 800 MB and a log file size of 250 MB.
DB2 requirements
The DB2 configuration requirements apply whether DB2 and Content Server are running on
Windows or AIX or a combination.
On AIX, ensure that the following DB2 environment variables are set in the installation owners
environment:
Update the database configuration for the database to 200 using the following command:
MAXAPPLS 200 AUTOMATIC MAXLOCKS 80 AUTOMATIC
DB2_BASE
This must point to /DB2_installation_dir/home/instance_name/sqllib.
DB2INSTANCE
This must point to the name of the default DB2 instance.
To support audit trail functionality, DB2 requires 8K-page capability. During the installation
of version 6.5, the installer automatically creates 8K pages. To find out whether you have 8K
temporary tablespace before an installation or upgrade, run the following command:
db2 LIST TABLESPACES SHOW DETAIL
If the page size parameter is 4096, you have 4K page size, if it is 8192, you have 8K page size.
To create an 8K temporary tablespace, run the following command:
db2 CREATE TEMPORARY TABLESPACE TEMPSPACE2 PAGESIZE = 8192
Ensure that the DB2 clients are installed on the Content Server host.
If you install DB2 on the same host as the Content Server, the clients are installed automatically.
If you install DB2 on a different host from the Content Server, you need to manually install
the DB2 clients on the Content Server host.
Set the code page to UTF-8.
Set the DB2NTNOCACHE environment variable:
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
47
db2set DB2NTNOCACHE=1
You can create the database and set the parameters from the DB2 command line or from the Control
Center. Use the Control Center to run the performance wizard. You can run the Control Center
on AIX, or you can run performance wizard from a Windows system to tune performance for the
instance on AIX.
Use the following general guidelines to install and configure DB2:
1.
Install DB2.
2.
3.
Configure DB2.
2.
Right-click the database and choose Configure from the context menu.
3.
48
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
If you are configuring DB2 Enterprise Edition, set the lock list size to a minimum of 500.
If you are configuring the DB2 Workgroup Edition, set the lock list size to 300.
4.
Click the Applications tab and set the maximum number of locks to 80.
5.
6.
7.
When the Control Center is displayed, click the database for your repository and right-click
Buffer Pools.
8.
9.
2.
Set the application heap size to 1024 or greater, where <dbname> is the name of the database you
created for use by the repository:
update db cfg for <dbname> using applheapsz 1024
3.
4.
db
db
db
db
cfg
cfg
cfg
cfg
for
for
for
for
<dbname>
<dbname>
<dbname>
<dbname>
using
using
using
using
LOGFILSIZ 1000
LOGPRIMARY 5
logbufsz 128
logsecond 10
5.
db
db
db
db
cfg
cfg
cfg
cfg
for
for
for
for
<dbname>
<dbname>
<dbname>
<dbname>
using
using
using
using
LOGFILSIZ 1000
LOGPRIMARY 5
logbufsz 64
logsecond 15
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
49
6.
7.
Set the sort heap and buffer page sizes. Ensure that the buffer page size (buffpagesize) is set to
a minimum of 6000.
If you are configuring DB2 Workgroup Edition:
update db cfg for <dbname> using sortheap 512
update db cfg for <dbname> using buffpage buffpagesize
If the repository and the DB2 server are on the same machine and you are configuring DB2
Enterprise Edition, set buffpagesize to 40% of the available physical memory divided by the
page size of your tablespace.
If the repository and the DB2 server are on the same machine and you are configuring DB2
Workgroup Edition, set buffpagesize to 20% of the available physical memory divided by the
page size of your tablespace.
If the repository and the DB2 server are on different machines, set buffpagesize to 80% of the
available physical memory divided by the page size of your tablespace.
Note: If you are running more than one repository and database on the same DB2 server, the
percentage recommended for buffer pool is for the sum of all databases. In all cases, ensure that
the buffer page size is a minimum of 6000.
8.
If you see the SQL1482W error message "The BUFFPAGE parameter will only be used if one of
the buffer pools is defined with a size of -1, change the buffer pool size:
ALTER BUFFERPOOL buffpoolname SIZE -1
9.
10. If DB2 is installed remotely, use the DB2 Client Configuration Assistant after database creation to
add the database alias to the list of available databases.
50
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
2.
3.
On the context menu, choose Configure Performance Using Wizard. The name of the production
database dialog box is displayed.
4.
5.
6.
7.
8.
Click Mixed , then click Next . The typical database transaction dialog box is displayed.
9.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
51
If you are installing DB2 Enterprise Edition, click More than 10 SQL statements and 60
transactions per minute, then click .
If you are installing DB2 Workgroup Edition, click Less than 10 SQL statements and 30
transactions per minute, then click Next.
The database administration priority dialog box is displayed.
10. Click Faster transaction performance (slower recovery), then click Next.
The database data population dialog box is displayed.
11. Click No, then click Next.
After the repository is in use and the database contains more data, you can run the Performance
Wizard again and change this parameter. The number of connected applications dialog box is
displayed.
12. Provide the average number of local and remote connections.
If you are installing DB2 Enterprise Edition, type in four average local connections and 20 average
remote applications and click Next.
If you are installing DB2 Workgroup Edition, type in four average local connections and two
average remote connections and click Next.
These numbers can be larger depending on the number of clients connecting to your repository.
A production repository can have many more client applications connecting.
The isolation level dialog box is displayed.
13. Click Cursor stability (many locks of short duration) and click Next. The Performance Wizard
displays values it recommends based on the information you provided and choices you made.
14. Check Apply these recommendations immediately, then click Finish.
15. From the command line, restart the DB2 server:
db2stop force
db2start
52
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
53
54
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 4
Pre-Installation Checklist
Content Server installation has two stages: The first stage copies Content Server software from the
installation media to the proper directories on the Content Server host and, on Microsoft Windows
hosts, modifies the Windows registry and environment variables. The second stage configures at least
one repository and at least one connection broker and starts the repository and connection broker.
Step-by-step instructions for installing Content Server software are found in these chapters:
Chapter 5, Installing Content Server software on a UNIX or Linux host
Chapter 6, Installing Content Server software on a Windows host
Step-by-step instructions for running the configuration program to create a connection broker and
repository are found in these chapters:
Chapter 7, Configuring Content Server and the repository on a UNIX or Linux host
Chapter 8, Configuring Content Server and the repository on a Windows host
After the installation, complete the tasks described in Chapter 9, Completing the Installation. To
upgrade from a previous release of Content Server, complete the preparatory steps described in
Chapter 10, Upgrading Content Server before installing the new version of Content Server.
You can choose to perform an express repository configuration or a custom repository configuration.
Express configuration minimizes the amount of information that you need to provide. It also limits
how much you can customize the configuration of Content Server and repository. The procedure for
installing and configuring Content Server on Windows and Linux and UNIX hosts calls out explicitly
those steps required for custom installation and configuration only and those required for express
installation only. Otherwise, the steps apply to both installation methods.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
55
Pre-Installation Checklist
Task
Resource
Value
installation owner
username:
__________
installation owner
password:
__________
56
repository name:
__________
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Pre-Installation Checklist
Task
Resource
Value
repository ID:
__________
repository owner
name:
__________
repository password:
__________
Database administrator
account, page 42 and the
database administrator
database administrator
name:
__________
database password:
__________
repository size:
__________
Content Server and
the file store need
to be on the same
domain
The installation user
account of Content
Server needs to be
available on the
domain.
The installation user
account needs to
have full access
control for the
filestore.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
57
Pre-Installation Checklist
58
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 5
Installing Content Server software on a
UNIX or Linux host
This first part of the installation process copies files from the installation media to the correct
directories on the hard disk. After installing the software, you will follow the instructions in Chapter
7, Configuring Content Server and the repository on a UNIX or Linux host, to configure one or
more repositories.
Have all checklists from the previous chapters ready before you begin with the installation.
Note: Displaying the installer remotely across platforms is not supported.
Note: When installing Content Server on a Suse11 with Oracle 11.1 platform, the netegrity plugin
does not load. To resolve this issue, install the libstdc++-libc6.2-2.so.3 library on Suse11, then install
Content Server. The netegrity platform will then load properly.
2.
Download the Content Server software for your operating system and database.
You can find the location of the software and instructions for downloading it in the EMC
Documentum Content Server Enterprise Edition Release Notes or in the instructions you received
through email regarding how to download products from the EMC download site.
3.
4.
If you are running from a UNIX environment, ensure that you have execute permission on the
#####.bin file. You can verify this by running the chmod +x ###.bin command.
5.
Run the installation program from the directory into which you expanded the files, which must
be a directory on the local host by typing the following:
% serveroperatingsystemSuiteSetup.bin
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
59
7.
8.
To continue with installation, click I accept the terms of the license agreement and click Next.
If you do not accept the license agreement terms, the Next button becomes unavailable, and you
cannot continue with the installation.
9.
Type the host name and port number for your existing primary connection broker. The default
port number is 1489. If you are using the default port number, ensure that the next port number
(1490) is available for use because the connection broker requires that two ports be reserved.
You can configure additional connection brokers by using the Content Server configuration
wizard.
Note: If you already have EMC Documentum software installed on the host, the installation
program will skip this step because you installed a connection broker with the previous
installation of the EMC Documentum software.
10. To enable Federated Search Services (FS2), select the check box.
If you choose not to enable FS2 services, leave the check box blank, and click Next.
If you choose to enable FS2, type the FS2 services host name and the FS2 services RMI port
number. The default port number is 3005. Click Next.
11. Type the password for the installation owner and click Next.
The dialog box shows the username and domain for the currently logged-in user. This user will
be the installation owner. When you click Next, the installation program validates the password.
12. To enable the High-Volume Server, select the check box, type the High-Volume Server license
key, and click Next.
13. To enable Trusted Content Services, select the check box, type the Trusted Content Services
license key, and click Next.
Note: Archive Services for Reports (ASR) does not work when Trusted Content Services is
enabled.
14. To enable Content Services for EMC Centera, select the check box, type the Content Services
for EMC Centera license key, and click Next.
15. To enable SnapLock, select the check box, type the SnapLock license key, and click Next.
16. To enable XML Store integration, select the check box, type the license key, and click Next.
If you choose not to enable XML Store integration, leave the check box blank and click Next.
17. You can install the DFC developer documentation.
a.
To install the DFC developer documentation, select the Developer Documentation check box.
b. Click Next.
Installing developer documentation requires an additional 18 MB.
18. Enter the connection information for the application server that Content Server installs for its
private use.
a.
60
Type the password for the administration user in the Admin User Password and Re-enter
Password fields. You will use this password and the username admin to access the
administration console for the application server. The password must be at least five
characters long, and it cannot contain double or single quotation marks (" or ).
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
b. Type the port number to use as the primary port for communications between the application
server and Content Server. The default port is 9080. The selected port must not be used by
another application. A total of 20 ports starting at port number 9080 are reserved for this
application server instance, and all of them must be available.
c.
Click Next.
19. Type a password for managing Accelerated Content Services (ACS) configuration and properties
files.
Accelerated Content Services is a Content Server component used for exchanging content with
Web-based client applications. Use the username acsAdmin and the specified password to access
the components that are used for modifying Accelerated Content Services configuration settings.
a.
Type the password for the acsAdmin user in the Password and Confirm password fields.
b. Click Next.
A panel displays the software to be installed.
20. Click Next to begin the software installation.
The dialog box reports the progress of the installation. If any components already exist on the
host, click Yes or Yes to All to replace the older components.
21. Choose whether to run the dm_root task automatically or manually at a later time. For
instructions on how to run the dm_root task manually, see Running dm_root_task manually
on UNIX or Linux hosts, page 80.
22. Click Finish to exit the Content Server installation program.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
61
62
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 6
Installing Content Server software on a
Windows host
The first part of the installation process copies files from the installation media to the correct
directories on the hard disk. After installing the software, you will follow the instructions in Chapter
8, Configuring Content Server and the repository on a Windows host, to configure one or more
repositories.
On Windows, this procedure also sets environment variables needed by Content Server. On
Windows, if you exit the Setup part of the installation program, all Content Server registry entries
are deleted. To install a component that was not previously installed, go through the complete
Setup program.
Have all checklists from the previous chapters ready before you begin with the installation.
Note: Displaying the installer remotely across platforms is not supported.
2.
Download the Content Server software for your operating system and database.
You can find the location of the software and instructions for downloading it in the EMC
Documentum Content Server Enterprise Edition Release Notes or in the instructions you received
through email regarding how to download products from the EMC download site.
3.
4.
Run the installation program from the directory into which you expanded the files, which must
be a directory on the local host. Double-Click the serverWinSuiteSetup.exe file (for the 32bit
Windows version) or serverWin64SuiteSetup.exe (for the 64bit Windows version).
Note: When this document was published, the 64-bit version of Content Server was
not yet available (April, 2011). Check the Powerlink website for the latest information
(http://powerlink.emc.com).
The installation program starts and a Welcome dialog box appears. The Welcome dialog box lists
the products and components that the program makes available for installation.
5.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
63
6.
7.
To continue with installation, click I accept the terms of the license agreement and click Next.
If you do not accept the license agreement terms, the Next button becomes unavailable, and you
cannot continue with the installation.
8.
If you are installing on a Windows host that has no other EMC Documentum software installed
on it, choose the installation directory for Content Server.
If you previously installed EMC Documentum software on the host, the relevant directories
might already be set. Skip to Step 16
Click Next to accept the default directory (C:\Documentum) where Content Server and data
installation or click Browse to select a different installation directory. The name of the directory
in which Content Server is installed must contain only ASCII characters and must not include
spaces. Do not use any of these characters in pathnames: ! \ / : * ? " < > | .
9.
To install the DFC developer documentation, select the Developer Documentation check box.
b. Click Next.
10. If DFC is not already installed on the host, click Next to accept the default installation directory
(C:\Program Files\Documentum,) for shared programs such as DFC or click Browse to select
a different directory.
If DFC is already installed on the host, the Content Server installation program uses the existing
DFC installation directory.
11. Select a user directory. You can either accept the default user directory C:\Documentum and
click Next or click Browse to choose another directory.
EMC Documentum products use the user directory to store working files, program settings,
and log files.
12. Type the host name and port number for your existing primary connection broker. The default
port number is 1489. If you are using the default port number, ensure that the next port number
(1490) is available for use because the connection broker requires that two port numbers be
reserved.
You can configure additional connection brokers by using the Content Server configuration
wizard.
Note: If you already have EMC Documentum software installed on the host, the installation
program will skip this step because you installed a connection broker with the previous
installation of the EMC Documentum software.
13. To enable Federated Search Services (FS2), select the check box.
If you choose not to enable FS2 services, leave the check box blank, and click Next.
If you choose to enable FS2, type the FS2 services host name and the FS2 services RMI port
number. The default port number is 3005. Click Next.
14. Type the password for the installation owner and click Next.
The dialog box shows the username and domain for the currently logged-in user. This user will
be the installation owner. When you click Next, the installation program validates the password.
15. To enable the High-Volume Server, select the check box, type the High-Volume Server license
key, and click Next.
64
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Note: If you opt to enable the High-Volume Server at a later time, you need to rerun the Content
Server installation program.
16. To enable Trusted Content Services, select the check box, type the Trusted Content Services
license key, and click Next.
17. To enable Content Services for EMC Centera, select the check box, type the Content Services
for EMC Centera license key, and click Next.
18. To enable XML Store integration, select the check box, type the license key, and click Next.
If you choose not to enable XML Store integration, leave the check box blank and click Next.
19. To enable SnapLock, select the check box, type the SnapLock license key, and click Next.
20. Enter the connection information for the application server that Content Server installs for its
private use.
a.
Type the password for the administration user in the Admin User Password and Re-enter
Password fields. You will use this password and the username admin to access the
administration console for the application server. The password must be at least five
characters long, and it cannot contain double or single quotation marks (" or ).
b. Type the port number to use as the primary port for communications between the application
server and Content Server. The default port is 9080. The selected port must not be used by
another application. A total of 20 ports starting at port number 9080 are reserved for this
application server instance, and all of them must be available.
c.
Click Next.
21. Type a password for managing Accelerated Content Services (ACS) configuration and properties
files.
Accelerated Content Services is a Content Server component used for exchanging content with
Web-based client applications. Use the username acsAdmin and the specified password to access
the components that are used for modifying Accelerated Content Services configuration settings.
a.
Type the password for the acsAdmin user in the Password and Confirm password fields.
b. Click Next.
A panel displays the software to be installed.
22. Click Next to begin the software installation.
The dialog box reports the progress of the installation. If any components already exist on the
host, click Yes or Yes to All to replace the older components.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
65
66
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 7
Configuring Content Server and the
repository on a UNIX or Linux host
This chapter provides instructions for configuring a Content Server repository on a UNIX or Linux
host. Perform this part of the installation after you install the software as described in Chapter 5,
Installing Content Server software on a UNIX or Linux host.
Click Next.
3.
Choose whether to run the dm_root task automatically or manually later. See Running the
administrative tool script manually, page 80 for details.
4.
Type the password for the installation owner and click Next.
The dialog box shows the username and domain for the currently logged-in user, who must be
the installation owner. When you click Next, the installation program validates the password.
5.
Select whether to perform an Express configuration or a Custom configuration and click Next.
If you select Express, the configuration program creates a new connection broker using a
default name and port number, and uses default values for certain repository configuration
settings. Skip to Step 13
If you select Custom, the configuration program enables you to edit the configuration values
used to create one or more connection brokers, a repository, or both.
6.
On SQL or Oracle databases, when you configure a repository, optionally select the check box to
enable database partitioning. By default, database partitioning is disabled.
If you select this option, the repository that you create is partitioned, but only one partition
exists. To take advantage of data partitioning and create multiple partitions, you must have a
High-Volume Server license.
7.
Choose whether to configure a connection broker, a repository, or both, and click Next.
If you checked connection broker, the connection broker configuration appears.
If you checked repository but not connection broker, the repository configuration appears.
Skip to Step 13 .
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
67
8.
b. Type a connection broker name (default: Docbroker) and the port number on which the
connection broker listens, or accept the defaults. The default port is 1489. If you are using
the default port number, ensure that the next port (1490) is available for use because the
connection broker requires that two ports be reserved.
c.
9.
Click Automatic to have the connection broker automatically start when the host starts, or
click Manual for manual startup.
Select the mode in which the connection broker connects to the repository.
Select Native for nonsecure connections.
Select Secure for secure connections.
Select Native and Secure if clients can use either connection mode.
68
Type the name of the repository. Name and ID to assign to the repository, page 19 contains
information about repository name requirements.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
f.
Click Next.
g. Type the service name. The service name must match the entry in the /etc/services file.
23. Click Next.
24. Select whether to create a new database user account and storage areas or use an existing user
account and storage, and click Next. If you use an existing database user account, be sure that
you have previously created a database user account.
Username Content Server will use to connect to the database, page 18 contains information about
this configuration option. The database user is the repository owner.
25. If you chose to use an existing database account and tablespaces or databases, provide the
database connection information.
a.
Choose the correct database connection for your database instance from the drop-down list:
On Oracle, select the connection string.
On DB2, select the database name.
On Sybase, select the database name.
b. Type the username for an existing database user. This user becomes the repository owner,
and must have the privileges identified in Repository owner account, page 41.
c.
f.
Click Next.
g. For Custom configuration only, choose the correct index tablespace or datafile name. Express
configuration uses default values.
h. Click Next.
Content Server starts.
26. If you chose to create a new database user account, provide database connection information.
a.
Choose the correct database connection for your database instance from the drop-down list:
On Oracle, select the connection string.
On DB2, select the database name.
On Sybase, select the database name.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
69
d. Type the database administrators username and password that was created when setting
up the database.
e.
Click Next.
f.
In a custom installation, you are prompted to either accept or change the default paths and
sizes for database storage. In an express installation the software automatically applies
the default values.
On Oracle, these are the Data Tablespace Data File Path and Index Tablespace Data File
Path.
On SQL Server, these are the Data Device File Path and Log Device File Path.
On Sybase, these are the Data Device File Path and Log Device File Path.
On DB2, these are the Tablespace File Path and Index Data File Path.
The tablespace or database creation dialog box appears.
g. Click Next.
h. For custom configuration only, edit or accept the default database scripts. Express
configuration runs the default scripts.
To edit the tablespace or database creation or deletion script, select the script and click
Edit. When you have saved the file, click Next.
To accept the default scripts and run them, click Next.
The new tablespaces or databases are created.
27. For custom configuration only, accept or modify Content Server initialization values. Express
configuration uses the default initialization file.
The server.ini file contains Content Server initialization information. If you are installing on
DB2 or Oracle and you want to modify the database parameters for the repository tables, edit
the server.ini file during this step. You cannot change these parameters after Content Server
creates the database tables for the repository. Appendix E, Defining Oracle or DB2 Database
Parameters for Repository Tables contains descriptions of the DB2 and Oracle parameters for
repository tables.
To accept the files, click Next.
To edit the server.ini file, select Server Initialization File and click Edit. After you save the
file, click Next.
28. Optionally, you can edit a tablespace script by clicking Edit.
29. Optionally, you can edit an initialization file by clicking Edit.
Caution: Errors in the server.ini file can cause problems with Content Server startup.
30. Click Next.
The configuration program runs the repository configuration scripts based on the settings you
provided.
31. If you dont already have a designated global registry, decide here whether to designate the
current repository as a global registry.
70
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Repository to use as the global registry, page 23 contains details on determining which repository
to designate as the global registry.
To use the current repository as a global registry, select Use this Repository and click Next.
To use a different repository as the global registry repository, select Specify a Different
Repository and click Next
To designate the global registry repository at a different time, select Do Later and click Next.
32. Type the connection information for the global registry.
If you chose the current repository as a global registry, type a username and password for the
global registry user and click Next. The default username is dm_bof_registry. The password
you supply is also used as the initial password for dm_report_user. Record this password to
use later for usage tracking.
Click Next.
If you chose to use a different repository as a global registry, type the repository name and
the global registry users username and password. The repository must be known to the
connection broker.
If you chose Do Later, the global registry connection page does not appear.
A warning message to enable the global registry connection appears. Click CONTINUE.
33. For custom configuration only, accept or modify the repository configuration scripts. Express
configuration runs the scripts without modification.
Appendix B, Content Server Installation Directories and Repository Configuration Scripts
contains information on what each of the scripts does.
To accept the scripts, click Next.
To edit a script, select it and click Edit. After you edit and save all the scripts you are
modifying, click Next.
Caution: Use caution in editing the scripts. Errors in the scripts can cause problems in
the repository.
When you click Next, the repository configuration scripts run, and the bundled DARs are also
installed. A message appears when these tasks are completed.
Note: For more information about DAR files, consult the EMC Documentum Composer User
Guide. If the DAR installation fails, you can still use the repository. Refer to the installation
logs for details.
34. Click Next.
35. Choose whether to restart Content Server to enable SSL client connections.
To enable SSL client connections, click Restart repository now and click Next.
Content Server stops and is restarted.
To restart Content Server at a different time, click Restart repository later and click Next.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
71
36. For custom configuration only, choose whether to configure additional repositories on the host.
Express configuration skips to the next step.
To configure additional repositories, select the check box and click Next. The configuration
program returns to Step 13.
To continue, select Exit from the Content Server configuration, and click Next.
A summary appears with information about the products configured on the host.
37. Click Finish.
38. On AIX, restart Content Server.
This loads required full-text plugins.
The xPlore Installation Guide provides instructions on how to install the full-text indexing software.
72
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 8
Configuring Content Server and the
repository on a Windows host
This chapter provides instructions for configuring Content Server and a repository on a Windows
host. Perform this part of the installation after you install the software as described in Chapter 6,
Installing Content Server software on a Windows host.
2.
Click Next.
3.
Type the password for the installation owner and click Next.
The dialog box shows the username and domain for the currently logged-in user, who must be
the installation owner. When you click Next, the installation program validates the password.
4.
Select whether to perform an Express configuration or a Custom configuration and click Next.
If you select Express, the configuration program creates a new connection broker using a
default name and port number, and uses default values for certain repository configuration
settings. Skip to Step 8.
If you select Custom, the configuration program enables you to edit the configuration values
used to create one or more connection brokers, a repository, or both.
5.
On SQL or Oracle databases, when you configure a repository, optionally select the check box to
enable database partitioning. By default, database partitioning is disabled.
If you select this option, the repository that you create is partitioned, but only one partition
exists. To take advantage of data partitioning and create multiple partitions, you must have a
High-Volume Server license.
6.
Choose whether to configure a connection broker, a repository, or both, and click Next.
If you checked connection broker, the connection broker configuration appears.
If you checked repository but not connection broker, the repository configuration appears.
Skip to Step 13 .
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
73
7.
b. Type a connection broker name (default: Docbroker) and the port number on which the
connection broker listens, or accept the defaults. The default port is 1489. If you are using the
default port number, ensure that the next port number (1490) is available for use because
the connection broker requires that two ports be reserved.
c.
8.
Click Automatic to have the connection broker automatically start when the host starts, or
click Manual for manual startup.
Select the mode in which the connection broker connects to the repository.
Select Native for nonsecure connections.
Select Secure for secure connections.
Select Native and Secure if clients can use either connection mode.
9.
10. To configure additional connection brokers on this host, select Configure an additional
connection broker and click Next. Repeat these steps, making sure to provide each connection
broker with a unique port number that is not used by another application.
To continue with the server configuration, select the Continue with server configuration check
box and click Next.
11. For custom configuration only, select Create a repository and click Next.
12. Choose whether to Create a new repository, Upgrade an existing repository, or Delete an
existing repository. Click Next.
Note: During repository configuration, if the administrative tool script does not run properly
and you see an error message, you can run it manually by using the procedure in Running the
administrative tool script manually, page 80.
13. Configure a repository.
14. To enable Content Storage Services, select the check box, type the license key, and click Next.
15. To enable Retention Policy Services, select the check box, type the license key, and click Next.
16. To enable Federated Records Services, select the check box, type the license key, and click Next.
17. To enable Records Manager, select the check box, type the license, and click Next.
18. To enable Physical Records Manager, select the check box, type the license, and click Next.
19. To enable data partitioning, select the check box and click Next.
20. Click Next to accept the default fully qualified domain name.
21. Provide the repository information.
a.
Type the name of the repository. Name and ID to assign to the repository, page 19 contains
information about repository name requirements.
74
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
e.
f.
g. Click Next.
22. Select the mode in which clients connects to the repository.
Select Native for nonsecure connections.
Select Secure for secure connections.
Select Native and Secure if clients can use either connection mode.
23. Select whether to create a new database user account and storage areas or use an existing
database user account and storage, and click Next. If you choose the option to use an existing
database user account, you must have created a database user account previously.
Username Content Server will use to connect to the database, page 18 contains information about
this configuration option. The database user is the repository owner.
24. If you chose to use an existing database account and tablespaces or databases, provide the
database connection information.
a.
Choose the correct database connection for your database instance from the drop-down list:
On Oracle, select the connection string.
On SQL Server, select an ODBC data source.
On DB2, select the database name.
On Sybase, select the database name.
b. Type the username for an existing database user. This user becomes the repository owner,
and must have the privileges identified in Repository owner account, page 41.
c.
f.
Click Next.
g. For Custom configuration only, choose the correct index tablespace or datafile name. Express
configuration uses default values.
h. Click Next.
Content Server starts.
25. If you chose to create a new database user account, provide database connection information.
a.
Choose the correct database connection for your database instance from the drop-down list:
On Oracle, select the connection string.
On SQL Server, select an ODBC data source.
On DB2, select the database name.
On Sybase, select the database name.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
75
This user becomes the repository owner, and must have the privileges identified in
Repository owner account, page 41.
c.
d. Type the database administrators username and password that was created when setting
up the database.
e.
Click Next.
f.
In a custom installation, you are prompted to either accept or change the default paths and
sizes for database storage. In an express installation the software automatically applies
the default values.
On Oracle, these are the Data Tablespace Data File Path and Index Tablespace Data File
Path.
On SQL Server, these are the Data Device File Path and Log Device File Path.
On Sybase, these are the Data Device File Path and Log Device File Path.
On DB2, these are the Tablespace File Path and Index Data File Path.
The tablespace or database creation dialog box appears.
g. Click Next.
h. For custom configuration only, edit or accept the default database scripts. Express
configuration runs the default scripts.
To edit the tablespace or database creation or deletion script, select the script and click
Edit. When you have saved the file, click Next.
To accept the default scripts and run them, click Next.
The new tablespaces or databases are created.
26. For custom configuration only, accept or modify Content Server initialization values. Express
configuration uses the default initialization file.
The server.ini file contains Content Server initialization information. If you are installing on
DB2 or Oracle and you want to modify the database parameters for the repository tables, edit
the server.ini file during this step. You cannot change these parameters after Content Server
creates the database tables for the repository. Appendix E, Defining Oracle or DB2 Database
Parameters for Repository Tables contains descriptions of the DB2 and Oracle parameters for
repository tables.
To accept the files, click Next.
To edit the server.ini file, select Server Initialization File and click Edit. After you save the
file, click Next.
27. Click Next.
The installation program runs the repository configuration scripts based on the settings you
provided.
28. Configure the data files or data devices
a.
76
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Type the name or IP address of a computer on the network that hosts an SMTP server.
The computer can be a remote host or the computer that hosts Content Server. All UNIX
operating systems and Windows 2000 Server include an SMTP server.
Click Next.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
77
When you click Next, the repository configuration scripts run, and the bundled DARs are also
installed. A message appears when these tasks are completed.
35. Specify the port that the XML Store should use and the directory where the XML
Store should be created. The default port is 1235 and the default directory is
$DOCUMENTUM\data\xhive_storage.
36. Choose whether to restart Content Server to enable SSL client connections.
To enable SSL client connections, click Restart repository now and click Next.
Content Server stops and is restarted.
To restart Content Server at a different time, click Restart repository later and click Next.
37. For custom configuration only, choose whether to configure additional repositories on the host.
Express configuration skips to the next step.
To configure additional repositories, select the check box and click Next. The configuration
program returns to Step 13.
To continue, select Exit from the Content Server configuration, and click Next.
A summary appears with information about the products configured on the host.
38. Click Finish.
The xPlore Installation Guide provides instructions on how to install the full-text indexing software.
78
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 9
Completing the Installation
This chapter describes required and optional tasks to perform after installing Content Server so
that users can begin working with a repository.
This chapter contains the following sections:
Reviewing the Content Server installation logs, page 79
Running dm_root_task manually on UNIX or Linux hosts, page 80
Running the administrative tool script manually, page 80
Changing the default passphrase, page 81
Binding Content Server to a network card, page 81
Configuring JBoss application servers for SSL, page 82
Changing the installation owner account, page 82
Backing up key store files, page 83
Starting Content Server repositories and connection brokers, page 83
Adding users and groups to a repository, page 84
Enabling jobs after installation, page 84
Creating additional repositories or connection brokers, page 84
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
79
2.
3.
2.
On the dialog box, clear the Run Script Again box and click Next.
3.
80
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
4.
For UNIX
dmbasic -f $DM_HOME/install/admin/toolset.ebs -P repository_name
$DM_HOME/install/admin database_connection_string -e ToolSetup
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
81
For more details about binding Content Server to a network card, see the EMC Documentum
Administrator User Guide, Appendix C.
Make the Java key store that was created for the server available on the Content Server host.
2.
Open the JBoss server configuration file. The default location of the configuration file
is \Documentum\jboss4.2.0\server\DctmServer_MethodServer\deploy\jboss-web.
deployer\server.xml.
3.
4.
82
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
To start Content Server repositories and the connection broker on Windows hosts:
1.
From Microsoft Windows, select Start > All Programs > Documentum > Documentum Server
Manager.
The Server Manager tool appears.
2.
Select the tab for starting the connection broker (labeled DocBroker) or repository.
3.
4.
Click Start.
5.
Click Start > All Programs > Administrative Tools > Services.
d. Click Start.
e.
To start Content Server and the connection broker on UNIX or Linux hosts:
1.
2.
3.
Run the script dm_start_serverconfigname script, where serverconfigname is the object name of the
Content Servers server config object.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
83
4.
84
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
1.
2.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
85
86
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 10
Upgrading Content Server
This chapter describes how to upgrade from a previous release and how to upgrade repositories to
Content Server version 6.7. The System Upgrade and Migration Guide contains additional information
on migrating the installation from a previous version to Content Server version 6.7. The System
Upgrade and Migration Guide and the EMC Documentum Content Server Enterprise Edition Release Notes
provide information about supported upgrade paths.
You cannot upgrade to Content Server Version 6.7 from a version earlier than 5.3 SP6. If your
current installation is an earlier version, you will have to upgrade it to 5.3 SP6 or later before you
upgrade to version 6.7.
This chapter contains the following topics:
Upgrade checklist, page 87
Upgrading the Content Server software, page 94
Each step in the upgrade process must be to a platform that is fully supported by EMC Documentum.
Depending on the Content Server release from which you are upgrading, you might need to upgrade
the operating system or database. The documentation provided by the operating system or database
vendor contains information on upgrading those components of the system. After each upgrade step,
test the repository to ensure that all functions are normal.
Note: Windows Server 2003 is not a supported environment for Content Server version 6.7. You must
upgrade your operating system to a supported environment before upgrading Content Server.
Caution: After upgrading, you cannot revert to previous versions of the Content Server.
Upgrade checklist
Use the following checklist for upgrading the Content Server. In the Value column, note any values
you will be prompted for during the upgrade procedure.
Table 8. Content Server upgrade checklist
Task
Resource
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Value
87
Task
Resource
Value
Upgrading sequence
considerations, page 91
EMC Documentum
Administration and Configuration
Guide
88
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Task
Resource
Database documentation
Value
EMC Documentum
Administrator User Guide
and Chapter 10, Upgrading
Content Server
EMC Documentum
Administration and Configuration
Guide
EMC Documentum
Administration and Configuration
Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
89
Task
Resource
Value
repository name:
__________
Content Server version:
__________
90
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Take the repository offline to prevent new workflows from being submitted.
2.
If the query returns a nonzero value, active automatic tasks still need to be processed. If it returns
0, the repository contains no more active automatic tasks, and you can safely stop the repository.
If the query returns 0, run the query a few more times to ensure that no new automatic tasks
are being generated.
Upgrade your current 32bit Content Server to a version 6.7 32bit Content Server.
2.
Upgrade/install a 64bit version of the database client on the Content Server host machine (see
below for updating DSNs or TNSNAMES.ORA).
3.
4.
5.
In step 2, when you install the 64bit client, you must copy the DSNs from the 32bit ODBC
driver to the 64bit driver if used by your database. When you redefine the DSN, you must use
the same level or later level of client library.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
91
If you use Oracle, the entries from the 32bit TNSNAMES.ORA file have to be copied into the
64bit TNSNAMES.ORA file.
During steps 2 and 3, you may see database connection errors in the repository logs, since the
combination of a 32bit Content Server and a 64bit database client is not supported. These
errors may be safely ignored.
During the upgrade from 32bit to 64bit, Content Server cannot upgrade the
authentication plugins that you have installed. You will need to replace the 32bit
authentication plugins with the 64bit plugins. You will find the plugins in the
%DM_HOME%\install\external_apps\authplugins folder.
Upgrade to a 64bit Content Server is not supported if there is no upgrade path from your
current OS to a 64bit OS.
If you are using the data partitioning feature, which is supported as of version 6.5, you need to
upgrade the database first before you upgrade Content Server. If you are not using the data
partitioning feature, it does not matter which one you upgrade first.
Do not probe log files before the entire upgrade is completed. Partial upgrade is not supported.
You need to upgrade the binaries, the connection broker, and the repositories are the same time.
For operating systems that do not support IPv6 in versions prior to version 6.5, you need to
upgrade the operating system first. You need to upgrade the following operating systems first if
they did not support IPv6 in versions prior to 6.5:
Linux (Red Hat)
Linux (SUSE)
AIX
Solaris
HPUX
Note: Version 6.7 does not support IPv6 on the HPUX-IA operating system.
If you are upgrading from version 5.3. SP6 , 6, or 6 SP1 to version 6.7, the upgrade will not remove
the binaries of the Tomcat and WebLogic application servers. This is because Tomcat and Weblogic
are supported for client and UCF type applications, while JBoss is used for the Java method server.
Using Documentum Administrator, log into the repository that should be the global registry,
using an administrator account.
2.
In Classic view, in the left navigation tree, click the Administration node.
3.
In the page that appears, under the heading "User Management", click Search for Users.
92
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
4.
Search for the following user: "dm_bof_registry" (enter this value next to the User Name label,
and click Search).
5.
View the properties of this user "dm_bof_registry" (click the (i) icon).
6.
Make note of the users State and User Login Name. If the user State is Inactive, this repository
is not the global registry. To make this repository the global registry, follow the subsequent
procedures. If the global registry user is Active, you need to verify some information in your
dfc.properties file on your application servers.
The following step enable you to verify the entries in the dfc.properties file.
7.
From the application server machine, locate the dfc.properties file. Open this file in any text
editor. Ensure the following three attributes are set in the dfc.properties file:
dfc.bof.registry.repository =
dfc.bof.registry.username =
dfc.bof.registry.password =
Without the above three entries, the global registry will not be set. If these entries are missing
or values are not complete, you need to add and populate these values. See the following
procedures for more details.
Log into Documentum Administrator as an administrator in the repository where you want
to enable TBO/SBO functionality.
2.
In Classic view, in the left navigation tree, click the Administration node.
3.
In the page that appears, under the heading "User Management", click Search for Users.
4.
Search for the following user: "dm_bof_registry" (enter this value next to the User Name label,
and click Search).
5.
View the properties of this user "dm_bof_registry" (click the (i) icon). The properties page will
appear.
6.
From the properties page, ensure the following options and values are set to the following:
User State: Active
User Source: Inline Password
Restrict Folder Access: System
7.
For security purposes, change the default password (make a note of the new password).
8.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
93
Use the object ID in the following query to verify whether the configuration is locked:
SQL> select r_object_id, r_lock_owner from dm_sysobject_s
where r_object_id = '<object ID>'
2.
If the repository contains customized repository formats (dm_format objects), back up the
customized formats.
Repository formats are upgraded by the dm_apply_formats.ebs script, which reads values from
the formats.csv file. If the attributes of a format in the repository do not match the format
descriptions in the formats.csv file, the script overwrites the existing values with the values
in the file.
3.
94
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
The consistency checker is a script that looks for repository inconsistencies, such as users with
nonexistent groups, permissions sets with nonexistent users, and sysobjects that point to
nonexistent content files. Fixing inconsistencies in the repository improves the quality of the data
in the repository and results in a smoother upgrade. The syntax is:
dmbasic -fconsistency_checker.ebs -eEntry_Point -- repository_name
superuser password
repository_name is the name of the repository against which you are running the consistency
checker.
superuser is the username of a repository superuser
password is the password for the superusers account.
The results of the consistency checker are directed to standard output.
4.
5.
6.
For the upgrade on a Windows host, shut down the repositories and connection brokers.
a.
Click Stop.
For the upgrade on a UNIX or Linux host, shut down the repositories and connection brokers.
a.
For each repository, run the dm_shutdown_repository script, where repository is the name of
the Content Server to be stopped.
9.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
95
The Content Server configuration section in the installation chapter provides the procedure on
running the Content Server configuration program. Perform the procedure with the following
upgrade modification steps:
a.
At step 9 (Configure a repository), select Upgrade an existing repository and skip to step 12.
The upgraded repository will use the same configuration settings as the existing repository.
If you are upgrading a repository on a Sybase platform, the upgrade procedure may hang
if the database transaction log is too small. When the repository is upgraded, it opens a
long-running transaction while the upgrade script is running. If the transaction log is too
small, the transaction hangs with locked system tables because the database server cannot
write information to the transaction log. To continue with the upgrade:
1.
2.
3.
If steps 1 and 2 fail to resolve the issue and allow the upgrade to proceed, increase the
transaction log space.
11. If you upgraded from an installation using FAST fulltext indexing, and selected xPlore fulltext
indexing, you must restart Content Server again after you complete Content Server configuration.
12. After you complete the Content Server configuration, create a nonunique index on the
dm_sysobject.r_object_id and r_aspect_name properties by using the following MAKE_INDEX
command:
EXECUTE make_index WITH type_name='dm_sysobject',
attribute='r_aspect_name',use_id_col=true
The inclusion of the use_id_col argument set to true automatically causes Content Server to
include the r_object_id column in the index.
13. If you are upgrading a repository in a distributed environment that uses a BOCS and
asynchronous write jobs, create an index on the dmr_content_s(i_parked_state, r_object_id)
properties. Use the following MAKE_INDEX command to do so:
EXECUTE make_index WITH type_name='dmr_content',
attribute='i_parked_state',use_id_col=true,id_in_front=false
96
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
16. On a Windows upgrade, the Startup Type is set to Manual for the Documentum Docbase Service
repository name service. If you want the repository to automatically start after a server reboot,
navigate to Start>All Programs>Administrative Tools>Services, and set the Startup Type to
Automatic.
To resolve this issue, run the following command from the API command line in DA:
apply,c,NULL,PATCH_MATERIALIZED_OBJECTS,TYPE,S,dm_message_archive
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
97
The Update Statistics tool is installed in the active state, running once a week. Because this tool can be
CPU and disk-intensive, it is recommended that you run the tool during off hours for database use.
Consult with your RDBMS DBA to determine an optimal schedule for this tool.
Arguments
Table 9, page 98, lists the arguments for the tool.
Table 9. Update Statistics arguments
Argument
Datatype
Default
Description
-dbreindex
string
READ
-server_name
string(32)
-queueperson
string(32)
-window_interval
integer
120
98
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Guidelines
Run this tool after you perform large loading operations.
When the job is run with -dbreindex set to READ and the statistics need updating, the report will say:
-dbreindex READ. If rows appear below, the corresponding
tables are fragmented.
Change to -dbreindex FIX and rerun if you want to reindex
these tables.
When the job is run with -dbreindex set to FIX, the report will say:
-dbreindex FIX. If rows appear below, the corresponding
tables have been reindexed.
Change to -dbreindex READ if you do not want to reindex
in the future.
Report sample
The Update Statistics report tells you when the tool was run and which tables were updated. The
report lists the update statistics commands that it runs in the order in which they are run. Here is a
sample of the report:
Update Statistics Report:
Date of Execution: 06-04-96
update
go
update
go
update
go
update
go
update
go
. . .
End of
statistics dmi_object_type
statistics dm_type_s
statistics dm_type_r
statistics dm_type_r
statistics dmi_index_s
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
99
The output of the script is the same as the output for Windows.
The descriptors might already exist if you run the script a second time for the same global registry, or
if the global registry is a 6.5 repository. If the descriptors already exist, the output from the script is:
%Documentum%\product\6.5\install\admin>dmbasic -f dm_acs_install.ebs
-e UpgradeDescriptors -- <repository name>
<user name> <password>
Start upgrade of validation descriptors on docbase
<repository name>
Connected to docbase <repository name> as
user <user name>.
Upgrade of dm_validation_descriptor data succeeded.
100
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
101
RESERVED_ID,I,84
Type: dmr_content
Columns: i_parked_state
Include ID Field: Yes
ID in Front: No
Unique: No
ID (decimal): 89
apply,c,NULL,DROP_INDEX,RESERVED_ID,I,89
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dmr_content,ATTRIBUTE,S,i_parked_state,
USE_ID_COL,B,T,ID_IN_FRONT,B,F,UNIQUE,B,F,RESERVED_ID,I,89
Type: dm_acl
Columns: owner_name, object_name
Include ID Field: Yes
ID in Front: No
Unique: Yes
ID (decimal): None
apply,c,NULL,DROP_INDEX,NAME,S,<fill in name>
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_acl,ATTRIBUTE,S,owner_name,
ATTRIBUTE,S,object_name,USE_ID_COL,B,T,ID_IN_FRONT,B,F,UNIQUE,B,T
Type: dm_message_archive
Columns: i_sharing_parent
Include ID Field: No
Unique: No
ID (decimal): None
apply,c,NULL,DROP_INDEX,NAME,S,<fill in name>
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_message_archive,ATTRIBUTE,S,i_sharing_parent,
USE_ID_COL,B,F,UNIQUE,B,F
Type: dm_message_archive
Columns: message_id, message_link_count, parent_message_id
Include ID Field: No
Unique: Yes
ID (decimal): None
apply,c,NULL,DROP_INDEX,NAME,S,<fill in name>
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_message_archive,ATTRIBUTE,S,message_id,
ATTRIBUTE,S,message_link_count,ATTRIBUTE,S,parent_message_id,USE_ID_COL,B,F,UNIQUE,B,T
Type: dm_sysobject
Columns: i_folder_id
Include ID Field: Yes
ID in Front: No
Unique: No
ID (decimal): 16
apply,c,NULL,DROP_INDEX,RESERVED_ID,I,16
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_sysobject,ATTRIBUTE,S,i_folder_id,
USE_ID_COL,B,T,ID_IN_FRONT,B,F,UNIQUE,B,F,RESERVED_ID,I,16
Type: dm_sysobject
Columns: r_aspect_name
Include ID Field: Yes
ID in Front: Yes
Unique: No
ID (decimal): 85
apply,c,NULL,DROP_INDEX,RESERVED_ID,I,85
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_sysobject,ATTRIBUTE,S,r_aspect_name,
USE_ID_COL,B,T,UNIQUE,B,F,RESERVED_ID,I,85
102
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Type: dm_sysobject
Columns: owner_name
Include ID Field: No
Unique: No
ID (decimal): 93
apply,c,NULL,DROP_INDEX,RESERVED_ID,I,93
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_sysobject,ATTRIBUTE,S,owner_name,
USE_ID_COL,B,F,UNIQUE,B,F,RESERVED_ID,I,93
Type: dm_audittrail
Columns: id_2
Include ID Field: No
Unique: No
ID (decimal): 83
apply,c,NULL,DROP_INDEX,RESERVED_ID,I,83
apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_audittrail,ATTRIBUTE,S,id_2,
USE_ID_COL,B,F,UNIQUE,B,F,RESERVED_ID,I,83
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
103
104
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 11
Enabling FAST with Content Server 6.7
The Documentum 6.7 Content Server does not have support for the FAST indexing server enabled.
xPlore is the default indexing server. If you have used FAST and want to continue to use it while you
evaluate or migrate to xPlore, use these instructions for a new installation. You can chose to enable
FAST before configuring the Content Server, or you can enable FAST after configuring Content Server.
If you are upgrading to 6.7, chose whether to install FAST support or xPlore support during the
upgrade. If you are upgrading from Content Server 6.5 SP2 or SP3, you must do step 3 from the
procedureTo enable the FAST indexing server after configuring the Content Server, page 106, even
if you selected FAST support during the upgrade (dont do step 1 and step 2 if you selected FAST
support during the upgrade). If you chose xPlore during upgrade and later decide to enable FAST
instead, use the procedure, To enable the FAST indexing server after configuring the Content Server,
page 106.
Note: The FAST indexing server will not be supported by Microsoft after 2011. xPlore is a fully
functional replacement with many added features and better performance.
To enable the FAST indexing server before configuring the Content Server
1.
2.
Launch the Content Server configuration program with the following command for your
environment. Substitute the full path to fast.ini or place the file in the launch directory:
UNIX or Linux:
dm_launch_server_config_program.sh -config fast.ini
Windows:
Server_Configuration_Program.exe -config fast.ini
3.
If you are upgrading from Content Server 6.5 SP2 or SP3, do the following using iAPI. Substitute
your values for FAST_indexserver_hostname and desired FAST_search_base_port+2100. The default
FAST_search_base_port is 13000, so the default value for FAST_search_base_port+2100 that you
would use in the SET command is 15100:
iAPI>retrieve,c,dm_ftengine_config
iAPI>append,c,l,param_name
SET>fds_qrserver_host
iAPI>append,c,l,param_name
SET>fds_qrserver_port
iAPI>append,c,l,param_value
SET>FAST_indexserver_hostname
iAPI>append,c,l,param_value
SET>FAST_search_base_port+2100
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
105
iAPI>save,c,l
To enable the FAST indexing server after configuring the Content Server
1.
repository_name is the name of the repository against which you are running the consistency
checker.
username is the username of a repository superuser.
password is the superuser password.
fulltextHome is the path to the fulltext subdirectory of $DOCUMENTUM or
%DOCUMENTUM%.
isRemoteCS specifies whether the Content Server is remote. Not case-sensitive. Valid values: t
and f.
For example:
dmbasic -f fulltext_setup_for_fast.ebs -eSetupForFAST -- testenv admin N0123
c:\documentum\fulltext f
2.
3.
If you are upgrading from Content Server 6.5 SP2 or SP3, do the following using iAPI. Substitute
your values for FAST_indexserver_hostname and desired FAST_search_base_port+2100. The default
FAST_search_base_port is 13000, so the default value for FAST_search_base_port+2100 that you
would use in the SET command is 15100:
iAPI>retrieve,c,dm_ftengine_config
iAPI>append,c,l,param_name
SET>fds_qrserver_host
iAPI>append,c,l,param_name
SET>fds_qrserver_port
iAPI>append,c,l,param_value
SET>FAST_indexserver_hostname
iAPI>append,c,l,param_value
SET>FAST_search_base_port+2100
iAPI>save,c,l
106
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 12
Uninstalling Content Server
This chapter explains how to delete a repository or connection broker and how to uninstall an
existing Content Server installation. Do not uninstall an existing installation to upgrade to a new
Content Server release, because all upgrades based on an existing installation. Use the procedures in
this chapter only if you want to uninstall an existing Content Server, a repository and its contents, a
connection broker, or a Content Server software installation.
This chapter contains the following information:
Order of uninstalling components, page 107
Deleting a repository, page 108
Deleting a connection broker, page 109
Uninstalling the Content Server software, page 109
To delete a repository or connection broker or uninstall Content Server, you need to meet the
following requirements:
Be able to log in as the installation owner
Have sufficient database privileges to drop tablespaces or databases
Shut down and uninstall the index agent if full-text indexing is installed.
The Content Server Fulltext Indexing System Installation and Administration Guide provides
information about uninstalling full-text indexing components.
2.
3.
Shut down and uninstall the index server if full-text indexing is installed. The repository must be
shut down for this.
4.
5.
6.
7.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
107
Deleting a repository
Use these instructions to delete a repository.
To delete a repository you need to meet the following requirements:
Be able to log in as the installation owner
Have sufficient RDBMS privileges to drop tablespaces or databases.
Note: If the repository has a Content Transformation Services (CTS) product installed on it, you need
to uninstall the CTS product before deleting the repository. If you do not, the CTS product will not
be available in all other repositories.
To delete a repository:
1.
2.
3.
Click Next.
4.
On Windows, provide the installation owner password and click Next, then skip to step 9.
5.
6.
7.
Select Delete an Existing Repository, select the repository to delete, and click Next.
You are asked if you want to delete the component.
8.
Click OK.
The installer stops the Content Server and provides the location of the tablespace or database
deletion script.
This is $DOCUMENTUM/server_uninstall/delete_db/repository_name, where repository_name is
the name of the repository.
9.
Click OK.
10. Indicate whether to configure another repository or exit from the configuration program and
click Next.
An information dialog box appears.
11. Click Finish.
12. From the database, drop the database tables associated with the repository.
108
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
2.
3.
Click Next.
4.
On Windows, provide the installation owner password and click Next, then skip to step 9.
5.
6.
Select Create New, Upgrade, or Delete Connection Brokers and click Next.
7.
Select Delete an Existing Connection Broker, select the connection broker to delete, and click
Next.
8.
9.
Indicate whether to configure another connection broker or exit from the configuration program
and click Next.
If you indicated to configure another connection broker, the program returns to the connection
broker dialog box, and you can repeat the connection broker deletion procedure. If you indicated
not to configure another connection broker, an information dialog box appears.
2.
On Windows:
a.
Click Start > Settings > Control Panel > Add/Remove Programs.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
109
c.
f.
c.
e.
f.
Note: Do not uninstall the DFC Runtime Environment if any other EMC Documentum
software is installed on the host.
110
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 13
Installing Remote Content Servers
in Distributed or Load-Balanced
Configurations
This chapter provides instructions for installing and configuring remote Content Servers in
distributed or load-balanced content configurations.
If you are creating a new single-repository in a distributed or load-balanced content configuration, a
configuration program separate from the Content Server configuration program is used for installing
remote Content Servers and creating the storage areas on the remote hosts and related location objects.
Review the Distributed Content Guide before you install a distributed configuration.
This chapter contains the following topics:
Preinstallation requirements, page 111
Installing and configuring the remote Content Server, page 112
Upgrading a distributed or load-balanced configuration, page 114
Deleting a remote Content Server, page 116
Preinstallation requirements
The following requirements and limitations exist when you are installing remote Content Server
in distributed or load-balanced configurations:
The remote host must meet the same preinstallation requirements as the primary Content Server
host.
The database client software must be installed on remote Content Server hosts. The remote
Content Server configuration program must connect to the database to properly create the
following objects for the remote server.
server config
acs config
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
111
Copy the Content Server installation files from the installation media to the correct directories
on the host.
This step is identical to the process used to copy files onto the primary Content Server host. The
Content Server installation sections in the Content server installation chapter provide instructions.
2.
112
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
%dm_launch_cfs_server_config_program.sh
Click Next.
On Windows, the Installation Owner Password dialog box appears.
On UNIX or Linux skip to Step 5.
4.
5.
Type the hostname of the primary connection broker for the repository and verify or type the port
number on which the connection broker listens and click Next.
The port defaults to 1489. If you are using the default port number, ensure that the next port
number (1490) is available for use because the connection broker requires that two ports be
reserved.
6.
Select the repository for which you are installing the remote Content Server, type the username
and password for a superuser in that repository and click Next.
The repository list is populated with repositories known to the connection broker for which you
provided information in the previous step. The superuser name defaults to the Documentum
installation owners name.
7.
Type the name and port number for the connection broker on the current host, indicate whether
connection broker startup following a system restart is automatic or manual, and click Next.
The default values are Docbroker and 1489. If you are using the default port number, ensure that
the next port number (1490) is available for use because the connection broker requires that two
ports be reserved. The connection broker is started.
8.
Accept the default location of the data directory or browse to a different location and click Next.
The data directory is where content files are stored in the repository.
9.
Accept the default location of the share directory or browse to a different location and click Next.
The share directory is where clients, example code, and required libraries are stored.
10. Accept the default service name for the new remote Content Server or type a different name
click Next.
11. Click Finish.
The remote Content Server is configured and running.
12. The remote Content Server installation cloned a copy of the dm_server_config object from the
original repository. Examine the dm_server_config object to verify that all the app_server_name
and app_server_uri entries apply to the remote Content Server. For example, if an index agent or
Business Process Engine are installed on the original repository, you may have entries for them
that point to the original host machine on the remote host. Remove any of these attributes if they
are not applicable to the new remote Content Server installation.
13. To start the application server instance that is running the Java method server and Content
Server, do one of the following:
On Windows hosts, restart after the installation.
On UNIX or Linux distributed or load-balanced configurations, use Documentum
Administrator to set the Get method for each component of the distributed or load-balanced
store to Surrogate Get.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
113
114
On the primary host, use the instructions in Upgrading the Content Server software, page 94, to
upgrade Content Server, connection brokers, and repository.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
2.
On each remote host, use the instructions in Upgrading the Content Server software, page 94,
to upgrade Content Server, but cancel the process before running the repository configuration
scripts.
3.
Create an acs config object in the repository for the ACS server installed with each remote
Content Server.
For example, if there are three remote Content Servers, you need to create three acs config objects.
a.
The parameters are described in Table 10, page 115. The acs config object is created in server
config mode and uses the network locations, connection broker projection targets, and stores
from the associated server config object. If you need to change the mode to acs config mode,
in which you manually set network locations, connection broker projection targets, and
stores, use Documentum Administrator to change the mode and create the manual settings.
Do not manually modify the new acs config object by using the API or DQL.
Table 10. Parameters required by dm_acs_install.ebs script
Parameter
repository_name
user_name
password
acs_name
server_config_name
Java_method_server_port
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
115
Parameter
acs_protocol
CleanupCacheAcsObject
4.
CacheAcsDescriptionFile
HostName
If the remote Content Servers are installed in a different file-system path from the primary
Content Server, create new site-specific location objects for locations that are new in the upgraded
repository.
a.
b. Create site-specific dm_dba and auth_plugin location objects that contain the locations on
each of the remote sites of the dba directory ($DOCUMENTUM/dba on UNIX or Linux;
%DOCUMENTUM%\dba on Windows) and the authentication plugin.
c.
5.
In the server config object for the remote Content Server, set the auth_plugin_location and
dba_location to the location objects you just created.
116
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Before you delete the software installation, also delete any connection brokers on the host. Use the
instructions in Deleting a connection broker, page 109.
2.
3.
Click Next.
5.
6.
7.
Type the installation owners name and password and click Next.
The service is deleted.
8.
Click Finish.
2.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
117
118
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 14
Installing Content Server and Java
Method Server for High-Availability
This chapter describes how to install and configure Content Server and Java Method Server in
high-availability mode. This chapter contains the following information:
Overview, page 119
JMS HA configurations, page 121
Choosing an HA configuration, page 124
Supported operating systems, page 125
Preinstallation requirements, page 125
Installing and configuring Java Method Server in HA mode, page 125
Viewing and modifying JMS instances, page 132
Overview
Content Server and Java Method Server (JMS) each support high-availability (HA). Content Server
supports two HA types: failover and load balancing. JMS supports failover only.
Failover
In a failover setup, if one of the Content Servers fails, the other Content Servers in the failover
setup continue with the service.
Load balancing
Load balancing involves operating redundant Content Servers where the service load is balanced
between Content Servers to maximize performance. In a standard Content Server load-balancing
scenario, proximity values are used to determine which Content Server processes an item. In a
cluster scenario, third-party load-balancers are used.
JMS is a customized version of an application server for executing Content Server Java methods. EMC
Documentum provides a servlet called DO_METHOD to execute Documentum server methods.
The method server itself is a Java-based web application. It communicates with the Content Server
via HTTP calls. Each time a method is invoked, the Content Server makes an HTTP request passing
the name of the Java class which implements the method along with any specified arguments to a
servlet which knows how to execute the specified method.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
119
Technically, all EMC Documentum Java server methods are simple Java classes. JMS runs as an
independent process. You can stop or start the process without recycling Content Server. On
Windows platforms, the JMS can be run as a Windows service or as a process.
Before JMS can support HA, Content Server must be in a standalone HA configuration first.
You can also install additional private JMS instances. Before you can install additional JMS instances,
you must package all the web applications previously deployed to the default embedded JBoss
application server with the jmsPackage.bat batch file. You then deploy that file to the new JMS to
maintain consistency between the two JMS instances.
Additionally:
The default Java Method Server for a remote Content Server (RCS) does not participate in JMS
failover.
A JMS node must be bound to a Content Server host and cannot be installed on a stand-alone
independent machine.
JMS load balancing is not supported. A single Content Server cannot be explicitly associated to
multiple Java method servers.
If a repository serves many users, having multiple servers can provide HA and enhance performance.
You can also dedicate one server to a particular application or group of users and have other servers
120
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
available to everyone. High availability provides those options. The servers used for load balancing
must project identical proximity values to any given connection broker. In that way, when a DFC
client determines which server, it will randomly pick one of the servers. If the values are different, the
DFC client will always choose the server with the lowest proximity value. If a Content Server stops
and additional servers are running against the repository with proximity values less than 9000, the
client library, with a few exceptions, will gracefully reconnect any sessions that were connected to
the stopped server to one of those servers. The exceptions are:
If the client application is processing a collection when the disconnection occurs, the collection is
closed and must be regenerated again when the connection is reestablished
If a content transfer is occurring between the client and server, the content transfer must be
restarted from the beginning
If the client had an open explicit transaction when the disconnection occurred, the transaction was
rolled back and must be restarted from the beginning
If the additional servers known to a sessions connection broker do not have the same proximity
value, the client library will choose the next closest server for failover. Sessions cannot failover to
a Content Server whose proximity is 9000 or greater. Content Servers with proximity values set
9000 or higher are called remote Content Servers, usually located at remote, distributed sites.
Note: A client session can only fail over to servers that are known to the connection broker used by
that session. To ensure proper failover, make sure that Content Servers project to the appropriate
connection brokers and with appropriate proximity values.
JMS HA configurations
JMS supports the following HA configurations:
Content Server and JMS on a single host
Content Server and JMS on two hosts
Content Server and JMS on multiple hosts
Content Server HA deployment involves two or more Content Servers. JMS HA involves adding
JMSs to additional Content Servers such that each Content Server has a dedicated JMS. JMS HA is
automatically enabled by associating each Content Server with their dedicated JMS.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
121
When installing the first Content Server, JMS is installed by default. When adding a Content Server
on same host, the JMS for the second Content Server is not installed. Instead is shares the JMS of the
first Content Server.
122
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
123
Choosing an HA configuration
Choose an HA configuration based on available hardware and your business needs.
Considerations
If the performance bottleneck is somewhere other than on Content Server, for example, in disk access
or WDK applications, adding more Content Servers will not improve performance significantly. If
you are using full-text indexing and need to improve search performance, start with an investigation
on the full-text components.
124
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Performance
The high availability solution improves performance in general. A load-balancing HA model can
improve performance and availability, but it might require additional resources. A failover HA
model enhances availability.
Tip
The EMC Documentum System Sizing Tool dynamically generates estimates of your hardware
resource requirements based on your user and hardware profile. You can download the EMC
Documentum System Sizing Tool from the Powerlink site (http://powerlink.EMC.com).
Preinstallation requirements
Before you install and configure Content Servers and repositories, read the following chapter of
this guide:
Chapter 2, Preparing the Host for Content Server Installation
Chapter 3, Preparing the Database for Content Server Installation
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
125
Follow the instructions in Chapter 4, Pre-Installation Checklist to install the main Content Server.
2.
After the installation completes, run the Content Server configuration program following the
instructions in Chapter 4, Pre-Installation Checklist. The Content Server Configuration program
guides you through creating a repository.
The installation of the main Content Server also installs an instance of JMS. A single
dm_jms_config object for that instance of JMS is created in the repository.
126
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
2.
3.
When you are being prompted for the service name, choose a service name that is different from
that of the primary Content Server.
To prepare the JMS for HA and to verify the dm_jms_config objects setup:
By default the CFS configuration program would install Content Server as a remote Content
Server (RCS) and set its projection to the connection broker to have proximity values of 9001 and
9010. However, JMS HA at present does not support RCS configurations, so you need to make the
following changes manually:
1.
2.
Modify the DOCBROKER_PROJECTION_TARGET for a single host setting: Comment out the
second set of settings, and the proximity value of the first set. The default proximity value will
then be 1. For example:
[DOCBROKER_PROJECTION_TARGET]
host = cshost1
port = 1489
#proximity=9001
[DOCBROKER_PROJECTION_TARGET_1]
#host =
#port =
#proximity =
#host=cshost1
#port=1489
#proximity=9010
3.
4.
2.
3.
Read the Welcome dialog box, which lists the products to be installed, and click Next.
The software license agreement appears.
4.
5.
To continue, click I accept the terms of the license agreement and click Next.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
127
If you do not accept the license agreement terms, the Next button becomes unavailable, and
you cannot continue with the JMS addition.
6.
7.
8.
Type the admin user password and the listen port for the application server and click Next.
9.
10. Type the fully qualified domain name (FQDN) and click Next.
11. Type the primary installation owner user name and password, and click Next. The wizard
now deploys the web application package.
12. Click Finish to complete the addition of the JMS instance.
13. Use Documentum Administator to associate the second Content Server to the second JMS
instance.
2.
3.
Read the Welcome dialog box, which lists the products to be installed, and click Next.
The software license agreement appears.
4.
5.
To continue, click I accept the terms of the license agreement and click Next.
If you do not accept the license agreement terms, the Next button becomes unavailable, and
you cannot continue with the JMS addition.
6.
7.
8.
Type the admin user password and the listen port for the application server and click Next.
9.
10. Type the fully qualified domain name (FQDN) and click Next.
11. Type the primary installation owner user name and password, and click Next. The wizard
now deploys the web application package.
12. Click Finish to complete the addition of the JMS instance.
13. Use Documentum Administator to associate the second Content Server to the second JMS
instance.
128
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
The following graphic shows an upgrade from multiple embedded JMS instances, each connected to
its own Content Server on multiple hosts supporting one repository to multiple JMS instances set up
for HA with Content Servers on multiple hosts supporting one repository.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
129
Follow the instructions in Chapter 4, Pre-Installation Checklist to install the main Content Server.
2.
After the installation completes, run the Content Server configuration program following the
instructions in Chapter 4, Pre-Installation Checklist. The Content Server Configuration program
guides you through creating a repository.
The installation of the main Content Server also installs an instance of JMS.
On multiple hosts, you need to run the install program to extract all required files for each host.
2.
130
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
3.
4.
When you are being prompted for the service name, EMC recommends to choose a service
name that is different from that of the primary Content Server. See chapter 9 of this guide for
more details.
To prepare the JMS for HA and to verify the dm_jms_config objects setup:
By default the configuration program would install Content Server as a remote Content Server (RCS)
and set its projection to the connection broker to have proximity values of 9001 and 9010. However,
JMS HA at present does not support RCS configurations, so you need to make the following changes
manually:
1.
2.
Modify the DOCBROKER_PROJECTION_TARGET for a single host setting: Comment out the
second set of settings, and the proximity value of the first set. The default proximity value will
then be 1. For example:
[DOCBROKER_PROJECTION_TARGET]
host = cshost1
port = 1489
#proximity=9001
[DOCBROKER_PROJECTION_TARGET_1]
#host =
#port =
#proximity =
#host=cshost1
#port=1489
#proximity=9010
3.
4.
To verify that the dm_jms_config objects in the repository were set up correctly, use the JMS
Admin panel in Documentum Administrator.
There will be two dm_jms_config objects.
5.
Use the Documentum Administrator to associate the second JMS with the second Content Server.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
131
132
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 15
Installing Content Server with Microsoft
Cluster Services
This chapter describes how to install and configure Content Server to provide failover support under
Microsoft Cluster Services. Content Server supports Microsoft Cluster Services 2008. This chapter
contains the following information:
Preinstallation requirements, page 136
Overview, page 133
Choosing a configuration, page 134
Configuring an active/passive cluster, page 137
Creating additional cluster resources on Microsoft Cluster Services 2008, page 144
Configuring an active/active cluster, page 146
Upgrading Content Server installed with Cluster Services, page 148
Overview
Microsoft Cluster Services supports the following forms of clustering:
Active/passive clusters
In active/passive clustering, the cluster includes active nodes and passive nodes. The passive
nodes are on standby and are only used if an active node fails. In active/passive clusters, both
nodes support the same repository.
Active/active clusters
In active/active clusters, all nodes are active. One node is considered the primary node, and the
other node is considered the secondary node. If one node fails or is taken offline, the remaining
node takes on the additional processing operations. In active/active clusters, each node supports a
different repository.
In a cluster environment, every service that the cluster runs uses resources of the cluster node. Every
service has its own resources, such as hard drive, IP address, and network name, assigned to it. All
resources that a clustered service uses form a resource group. The connection broker and Content
Server are a part of this resource group. In a cluster, all resources form a virtual server that can move
from one physical server to another to provide failover support.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
133
Choosing a configuration
A Content Server installation supports two types of cluster service configurations:
active/passive
active/active
This chapter provides detailed installation instructions for both configurations. Choose the
configuration based on available hardware and your organizations business needs. Figure 10, page
135 illustrates Content Server and connection broker setup in an active/passive cluster.
134
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
In an active/passive configuration, both nodes support the same repository. Content Server and
connection broker run on the primary node. If the primary node fails, the secondary node that was on
standby takes ownership of the resource group. After the cluster resources are brought online on the
secondary node, the connection broker and Content Server start on the secondary mode.
In an active/active configuration, each node supports a different repository. Each node is considered
the standby to the other node. Each node owns its own resource group. Each resource group has
its own virtual IP address, a virtual hostname, shared disk, connection broker, and Content Server.
Figure 11, page 136 illustrates Content Server and connection broker setup in an active/active cluster.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
135
If a node fails or is taken offline, its resource group is moved to the remaining node in the cluster.
The remaining node then manages two resource groups. When the failed node is running again, the
cluster administrator can move one resource group back.
Preinstallation requirements
Before you install and configure Content Server and a repository under Microsoft Cluster Services,
read Chapter 2, Preparing the Host for Content Server Installation, and perform the preinstallation
tasks described there. Complete the checklist in Installation and configuration checklist, page 55.
136
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Whether you are configuring an active/passive cluster or an active/active cluster, set up the shared
disks to be used by the repositories. Ensure that the shared disks include a directory to use for
content storage.
If you are configuring an active/active cluster, the user who configures Microsoft Cluster Services
must have read and write permissions on both nodes on the directories where the connection broker
logs reside.
Note: Fulltext indexing is not supported in installations that use Cluster Services.
Use the MSCS Cluster Administrator utility to create a cluster resource group that contains the
following resources:
A virtual IP address
Content Server uses this IP address. Other products can share the IP address because the
connection broker and Content Server only listen on particular ports.
A virtual network hostname
The virtual network hostname is for the virtual IP address.
A shared disk partition
This is the location of the repository data directory, where content files are located.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
137
2.
Move the resource group between the primary and standby hosts to ensure that the virtual IP
address, virtual network hostname, and shared disk partition fail over properly.
a.
Ensure that the first node owns the resource cluster group.
2.
Click Next.
3.
Type the password for the installation owner and click Next.
The dialog box shows the username and domain for the currently logged-in user, who must be
the installation owner. When you click Next, the installation program validates the password.
4.
If you did not enable Trusted Content Services during installation, optionally select the check box
and type the Trusted Content Services license key and click Next.
5.
If you did not enable Content Services for EMC Centera during installation, optionally select the
check box and type the license key and click Next.
6.
7.
8.
b. Type a connection broker name (default: Docbroker) and the port number on which the
connection broker listens, or accept the defaults. The default port is 1489. If you are using the
default port number, ensure that the next port number (1490) is available for use because
the connection broker requires that two ports be reserved.
138
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
c.
Click Automatic to have the connection broker automatically start when the host starts, or
click Manual for manual startup.
9.
e.
Click Next.
f.
To enable Content Storage Services in the repository, select the check box, type the license
key, and click Next.
b. To enable Retention Policy Services in the repository, select the check box, type the license
key, and click Next.
c.
To enable Federated Records Services in the repository, select the check box, type the license
key, and click Next.
d. To enable Records Manager in the repository, select the check box, type the license key,
and click Next.
e.
To enable Physical Records Manager in the repository, select the check box, type the license
key, and click Next.
The Data Directory dialog box appears.
f.
Click Next to accept the default data directory location or browse for a new location.
The data directory is the location where content files are stored. Do not choose a directory
that is used by another repository for content file storage or any other purpose.
g. Click Next to accept the default share directory location or browse for a new location.
The share directory is where client products, sample code, and libraries are stored.
Note: The share directory is not the same as the $DOCUMENTUM_SHARED environment
variable. This environment variable sets the directory into which EMC Documentum
Foundation Classes and other components are installed.
h. Type the directory where the database client software is installed and click Next. If the
configuration program cannot locate the database client software required to connect to the
database, it asks you to identify the directory that contains the software.
i.
Type the name of the repository. Name and ID to assign to the repository, page 19 contains
information about repository name requirements.
Note: If you are installing on the second node, use the same repository name you used for
the first node.
j.
Type the repository ID. Name and ID to assign to the repository, page 19 contains information
about repository ID requirements.
Note: If you are installing on the second node, use the same repository ID you used for
the first node.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
139
Click Next.
10. Type connection broker connection information for the connection broker to which you want
the repository to broadcast its connection information. Express configuration broadcasts to
the default local connection broker
a.
11. Select the mode in which client applications connect to the repository.
Select Native for unsecure connections.
Select Secure for secure connections.
Select Native and Secure if clients can use either connection mode.
12. Click Next.
13. If you are installing on the first node, select Create a new database user account, then provide
database information.
a.
Choose the correct database connection for your database instance from the drop-down list.
Click Next.
f.
Accept the default paths and sizes for database storage or change them and click Next.
Choose the correct database connection for the database instance from the drop-down list.
140
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Use the account you created for the first node. This user is the repository owner.
c.
d. Click Next.
e.
f.
Click Next.
15. If you are installing on the first node, accept or modify Content Server initialization values.
Express configuration uses the default initialization file. The server.ini file contains Content
Server initialization information. If you are installing on DB2 or Oracle and you want to
modify the database parameters for the repository tables, edit the server.ini file during this
step. You cannot change these parameters after Content Server creates the database tables for
the repository. Appendix E, Defining Oracle or DB2 Database Parameters for Repository Tables
contains descriptions of the DB2 and Oracle parameters for repository tables.
To accept the files, click Next.
To edit the server.ini file, select the Server Initialization File and click Edit . After you have
edited and saved the file, click Next.
16. If you are installing on the second node, perform the following steps:
a) Select the Server Initialization File, click Edit server.ini file, set the following parameters,
and save it:
[DOCBROKER_PROJECTION_TARGET]
host = <MachineB>
port = 1489
[DOCBROKER_PROJECTION_TARGET_1]
host = <MachineB>
port = 1489
proximity = 200
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
141
Repository to use as the global registry, page 23 contains details on determining which repository
to designate as the global registry.
To use the current repository as a global registry, select Use this Repository and click Next.
To use a different repository as the global registry repository, select Specify a Different
Repository and click Next
To designate the global registry repository at a different time, select Do Later and click Next.
20. Type the connection information for the global registry.
If you chose the current repository as a global registry, type a username and password for the
global registry user and click Next. The default username is dm_bof_registry.
If you chose to use a different repository as a global registry, type the repository name and
the global registry users username and password. The repository must be known to the
connection broker.
If you chose Do Later, the global registry connection page does not appear.
A warning message to enable the global registry connection appears. Click CONTINUE.
21. Accept or modify the repository configuration scripts. Express configuration runs the scripts
without modification.
Appendix B, Content Server Installation Directories and Repository Configuration Scripts
contains information on what each of the scripts does.
To accept the scripts, click Next.
To edit a script, select it and click Edit. After you edit and save all the scripts you are
modifying, click Next.
Caution: Use caution in editing the scripts. Errors in the scripts can cause problems in
the repository.
When you click Next, the repository configuration scripts run, and the bundled DARs are also
installed. A message appears when these tasks are completed.
22. Click Next.
23. Choose whether to restart Content Server to enable SSL client connections.
To enable SSL client connections, click Restart repository now and click Next.
Content Server stops and is restarted.
To restart Content Server at a different time, click Restart repository later and click Next.
24. If you are installing on the first node, select Repository Headstart and click Edit Script.
25. Modify the Repository Headstart script to point to the location object of the shared drive on
which the repository resides.
a.
Modify the Repository Headstart script to point to the location object of the shared drive:
142
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
drive_letter:\documentum\data\repositoryname\content_storage_01
where drive_letter is the shared drive where the repository data directory resides and
repositoryname is the name of the repository.
b. Change them to:
status=dmAPISet("set,c,l,file_system_path",
"drive_letter:\documentum\data\
repositoryname\content_storage_01")
drive_letter is the shared drive where the repository data directory resides.
repositoryname is the name of the repository.
Example:
E:\documentum\data\repository1\content_storage_01
26. Run the default scripts unless you are familiar with the internal configuration of Content Server.
To run the default repository configuration scripts, click Next.
To edit additional repository configuration scripts, select the script and click Edit. Click Next
after you edit and save any of the scripts.
The scripts run and the repository is configured.
27. Click Finish.
28. Once you have finished setting up the two nodes against the cluster, confirm the virtual host name.
29. Disable clustering by changing the host name of one of the nodes to the virtual host name.
30. Confirm that the connection broker and Content Server launch correctly with the fix.
31. Change nodes virtual host name back to the original host name, and verify that it launches
correctly.
32. Repeat step 31, step 32 and step 34 until all nodes have new tickets.
33. Shut down Content Server and the connection broker.
34. Move the cluster group to the second node.
35. Use the instructions in Installing Content Server software on the nodes, page 138, and
Configuring Content Server, page 138, to repeat the installation and configuration procedures
for the second node.
36. To start the application server instance that is running the Java method server and ACS server,
restart the Windows hosts after the installation is completed.
Start Server Manager by clicking Start > Programs > Documentum > Documentum Server
Manager.
2.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
143
3.
4.
Click OK.
5.
6.
For example:
host = dmcluster1
7.
8.
9.
Navigate to Start > Programs > Administrative Tools > Failover Cluster Management. The
Failover Cluster Management console is displayed.
2.
Right-click the Services and Applications node and select the Configure a Service or
Applicationoption. The High Availability Wizard is displayed.
3.
Select Generic Service to configure for high availability and click Next. The Select Service
screen is displayed.
4.
Select the Documentum Docbroker Service connection broker service from the list and click
Next. The Client Access Point screen is displayed.
5.
6.
144
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
7.
Select the shared storage you want to assign to the specified service, and click Next. The
Replicate Registry Settings screen is displayed.
8.
9.
Click Next. The Summary screen is displayed confirming that the High availability was
successfully configured for the service or application.
10. Click Finish. When the configuration is completed, the Services and Applications node lists the
new service you configured.
11. Right-click the new service, and select Properties. The Properties dialog box for the service is
displayed.
12. In the General tab, select NODE1 and NODE2 in the Preferred owners list.
13. Click OK.
14. Right-click the Documentum Docbroker Service connection broker service, and select Properties.
The Properties dialog box is displayed.
15. In the General tab, ensure that the Use Network Name for computer name option is selected
by default, and click OK.
16. Right-click the Documentum Docbroker Service connection broker service in the console, and
select the Bring this resource online option. The resource is brought online and the Online icon is
displayed in the Status column of the Summary screen.
17. Right-click the configured service, select Add a resource > Generic Service. The New Resource
Wizard dialog box is displayed.
18. Select Documentum Docbase Service in the Select Service list of the Select Service screen.
19. Click Next. The Confirmation screen is displayed.
20. Click Next. The Summary screen is displayed confirming that the High availability was
successfully configured for the service or application.
21. Click Finish. The Documentum Docbase Service is added to the Other Resources list.
22. Right-click the Documentum Docbase Servicein the Summary screen, and select Properties. The
Properties dialog box for the service is displayed.
23. In the Dependencies tab, add the Documentum Docbroker Service.
24. In the General tab, ensure that the Use Network Name for computer name option is selected, and
click OK.
25. Right-click the Documentum Docbase Service in the Summary screen console, and select
the Bring this resource online option. The resource is brought online and the Online icon is
displayed in the Status column of the Summary screen.
Verifying failover
After you complete the preceding procedures, verify that failover works properly.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
145
To verify failover:
1.
On a client computer, ensure that the dfc.properties entries refer to the virtual network hostname
or virtual IP address.
2.
3.
4.
Move the resource group from the node where it is running to the other node.
5.
After the resource group comes online on the other node, verify that the client can run queries.
146
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
147
Verifying failover
After you complete the preceding procedures, verify that failover works properly.
To verify failover:
1.
On a client computer, ensure that the dfc.properties entries refer to both virtual network
hostname or virtual IP address.
2.
3.
4.
Move the two resource groups back and forth between the nodes.
5.
After a resource group comes online on a new node, verify that the client can run queries.
2.
3.
4.
5.
6.
Open the Services dialog box and verify that the application server was created correctly.
148
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
8.
9.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
149
150
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 16
Configuring Multiple Content Servers
on a Single Host for a Particular
Repository
You can run multiple Content Servers on a single host against a particular repository. This chapter
provides instructions for creating such a configuration.
This chapter contains the following topics:
Windows hosts, page 151
UNIX hosts, page 153
Windows hosts
Use these instructions after a repository is configured to create additional servers for that repository
on the repository host. The EMC Documentum Content Server Administration and Configuration Guide
provides instructions on configuring additional servers for a repository on remote hosts
Connect to the repository as a superuser by using Documentum Administrator and create a new
server config object by saving the object with a new object name.
For example, if the existing server config object is called caruso, call the new server config
object caruso1.
In Documentum Administrator, navigate to Administration > Basic Configuration. From the File
menu, select Save As... and save the config object with a new name.
2.
3.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
151
server_config_name=caruso1
Navigate to the \Winnt\System32\drivers\etc\ and open the services file in a text editor.
5.
6.
7.
b. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\.
c.
d. Use the Save Key menu to write out the key values for the existing Content Server service.
e.
f.
Restore the key values you wrote out to the new key.
g. Change the ImagePath variable to include the path to the new server.ini file and a new log file.
For example, if the existing ImagePath is
d:\Documentum\product\6.5\bin\dmserver_v4.exe -repository_name
test1 -security acl -init_file
d:\Documentum\dba\config\test1\server.ini -run_as_service
-install_owner dmadmin -logfile
d:\Documentum\dba\log\test1.log
Set the new Content Server to manual start mode using Start > Programs > Administrative
Tools > Services panel.
9.
10. Click Start > Programs > Administrative Tools > Services and start up the new Content Server.
11. Start IDQL and verify that the Content Server is running correctly:
$ IDQL caruso.caruso1 -Uusername -Ppassword
152
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
UNIX hosts
Use these instructions after a repository is configured to create additional servers for that repository
on the repository host. The EMC Documentum Content Server Administration and Configuration Guide
provides instructions on configuring additional servers for a repository on remote hosts.
To create this configuration, edit the etc/services file, which requires root privileges.
Connect to the repository as a superuser by using Documentum Administrator and create a new
server config object by saving the object with a new object name.
For example, if the existing server config object is called caruso, call the new server config
object caruso1.
In Documentum Administrator, navigate to Administration > Basic Configuration. From the File
menu, select Save As... and save the config object with a new name.
2.
3.
5.
6.
7.
Navigate to the $DOCUMENTUM/dba directory and make a copy of the Content Server startup
and shutdown scripts:
cp dm_start_caruso dm_start_caruso1
cp dm_shutdown_caruso dm_shutdown_caruso1
8.
9.
Change
logfile=$logdir/caruso.log
to
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
153
logfile=$logdir/caruso1.log
10. Change
./documentum -repository_name caruso -security acl -init_file
/trout1/documentum/dba/config/caruso/server.ini $@ >> $logfile 2>&1 &
to
./documentum -repository_name caruso -security acl -init1\_file
/trout1/documentum/dba/config/caruso1/server1.ini $@ >> $logfile 2>&1 &
to
DM_PID=`./iapi caruso.caruso1 -U$DM_DMADMIN_USER -P -e << EOF
grep 'root_pid' | sed -e 's/ .*[: A-Za-z]//'
13. Change
./iapi caruso -U$DM_DMADMIN_USER -P -e << EOF
to
./iapi caruso.caruso1 -U$DM_DMADMIN_USER -P -e << EOF
16. Start IDQL and verify that the Content Server is running correctly:
$ IDQL caruso.caruso1 -Username -Password
17. Check the log file for the new Content Server in $DOCUMENTUM/dba/log/caruso1.log.
154
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Chapter 17
Creating a repository copy to test an
upgrade
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
155
Precopying tasks
Before you create the repository copy, complete these tasks and note any appropriate values in
the Value column:
Table 11. Precopying tasks
Task
Resource
Value
Consult the
repository
administrator.
Consult the
repository
administrator.
Consult the
repository
administrator.
connection: ____________
drive: ____________
156
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Copying a repository
In the instructions that follow, the test repository is called the repository copy. The original repository
is called the production repository.
Caution: The instructions that follow assume that the production repository is running on the
network while the repository copy is tested. However, shut down the production repository or
take it off the network while you test the repository copy. Conflicts and data corruption can
result from having two repositories on the network with the same name and repository ID.
To copy a repository:
1.
2.
On the target host, create a new Content Server installation and repository (the repository copy)
of the same version number as the production repository.
Follow the instructions in the Chapter 4, Pre-Installation Checklist, for the Content Server
installation.
Note: When you create the repository copy, ensure that you use the same repository name,
repository ID, and repository owner name and password as the production repository.
When you create the repository copy, ensure that you use the same repository name,
repository ID, and repository owner name and password as the production repository.
Ensure that you use a different database instance from the instance used by the production
repository and that you provide the correct connection information when you install.
For example, under Oracle the tnsnames.ora on the host where the repository copy resides
must point to the Oracle instance used by the copy, not the instance used by the production
repository.
Ensure that the repository copy projects to a connection broker different from the connection
broker used by the production repository.
Copy the $DOCUMENTUM/dba/secure/aek.key dbpasswd.txt files from the original host to
the same location on the repository copy host.
3.
Apply to the repository copy any patches you applied to the production repository.
4.
5.
Use the database vendors tools to export all objects owned by the repository owner and export
the schema for the tables comprising the repository.
Contact the database vendor for any technical support you need to use the database tools.
6.
On the production repository hosts file system, create a backup of the $DOCUMENTUM/data/
repository_name directory. This is the directory containing the repositorys content files.
7.
8.
Connect as the database system administrator to the database instance that is serving the
repository copy. For example, on Oracle, connect as the System account.
9.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
157
The scripts are database-specific. Run the script using the tools provided by the database vendor.
10. Delete the physical database file from the file system.
The name and location of the physical file are in the dm_CreateTableSpace.sql script.
11. Create new tablespaces or databases for the repository copy by using the dm_CreateTableSpace.sql
script in $DOCUMENTUM/dba/config/repository_name/.
The scripts are database-specific. Run the script by using the tools provided by the database
vendor.
12. Import the database export taken from the production repository into the newly created
tablespaces or database.
13. Verify that the database tables have the correct value for the test system hostname by checking
the following values:
r_host_name and web_server_loc in dm_server_config_s
host_name in dm_mount_point_s
target_server in dm_job_s
projection_targets in dm_server_config_r
object_name in dm_acs_config_s
acs_base_url in dm_acs_config_r
14. Connect to the database that is serving the repository copy as the repository owner .
15. If any of the values in Step 13 are incorrect, use SQL Server to correct the values.
16. Set the server to rebuild the Documentum views with this SQL Server statement:
update dm_type_s set views_valid=0
17. If you are testing operations that require the content files, copy the content file backup from the
production repository to the file system of the repository copy.
18. Navigate to the DOCUMENTUM/dba/config/repository_name directory and open the server.ini
file in a text editor.
19. Ensure that the preserve_existing_types key in the SERVER_STARTUP section is set to TRUE:
preserve_existing_types=T
c.
158
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
e.
After making these changes, restart Content Server for the changes to take effect.
23. If you are testing the migration of a Web content management repository, modify the user objects
to reflect the new authentication domain.
a.
c.
24. If the Content Server and content files of the copy reside on a drive different from the drive
used by the production repository, use IDQL to update the file_system_path attribute of the
dm_location and dm_mount_point objects to the new location:
update dm_location objects
set file_system_path='newpath' where file_system_path='old path'
update dm_mount_point objects
set file_system_path='newpath' where file_system_path='old path'
25. Deactivate all jobs by changing the is_inactive attribute on all job objects to TRUE.
26. Upgrade the repository copy to and verify the upgrade.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
159
160
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Appendix A
Required Environment Variables for
UNIX and Linux
This appendix lists the required environment variables for UNIX, Linux, and the databases.
If you are installing Content Server on UNIX or Linux, you need to set certain environment variables
in the installation owners environment. If you use the dm_launch_server_config_program.sh
script to start the Content Server configuration program, all required environment variables,
except for those required by each database are set automatically. If you do not use the
dm_launch_server_config_program.sh script, you need to manually set all environment variables.
You can set all of the following variables, except LC_ALL and DISPLAY, by sourcing
$DM_HOME/bin/dm_set_server_env.sh or $DM_HOME/bin/dm_set_server_env.csh. Set the
variables LC_ALL and DISPLAY in the installation owners .cshrc file (C shell) or .profile file (Bourne
or Korn shells). Alternatively, set the variables in a file called by the .cshrc file or .profile file or
in other ways permitted by UNIX.
Environment variable
Description
Required values
DOCUMENTUM
DM_HOME
$DOCUMENTUM/product/
version_number
DOCUMENTUM_SHARED
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
161
Environment variable
Description
Required values
DISPLAY
localhost:0.0
LC_ALL
C
Caution: If this value is
not set correctly, the Java
method server will fail.
162
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Appendix B
Content Server Installation Directories
and Repository Configuration Scripts
This appendix describes the file structure, scripts, and configuration objects that are a part of a
Content Server installation. The following topics are discussed:
Content Server installation file structure, page 163
Scripts run during installation or upgrade, page 168
Configuration objects, page 171
_uninst
This directory contains the Content Server uninstaller.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
163
data
The files and directories in this category are the content storage areas. These directories must exist
and location objects must be defined for them in the repository before you start Content Server. The
installation procedure creates a default storage area and associated location object and a default
full-text index object and associated location object.
The data directory contains directories that store the data manipulated by users and Content Server.
The installation procedure creates a subdirectory for the repository in the data directory and in that
repository subdirectory, creates a content storage area.
The data includes the full-text indexes and the content files associated with objects in the repositories.
The location of these directories is the most flexible component of the configuration.
Most sites will want to add more storage areas and index directories, particularly as the repository
grows larger. The EMC Documentum Content Server Administration and Configuration Guide provides
information and instructions about adding additional storage areas and full-text index storage
directories.
dba
The dba directory contains the log and config directories and several files.
The log directory is where the Content Server places any log files generated by user actions during
a session with the Content Server. The Content Server creates any necessary subdirectories for
these log files under the log directory.
The config directory includes a subdirectory for each repository that contains the startup files for
Content Server.
fulltext
The fulltext directory contains the third-party full-text indexing software.
product
The product subdirectory contains the Content Server executables.
server_uninstall
This directory contains a script that you can run manually to destroy a repositorys database tables
after you delete the repository.
164
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
share
The share directory holds all the files that can be shared by the Content Server and the clients. Clients
that connect to the share directory remotely can benefit in file sharing and event notification. The
client must be using NFS software to receive these benefits. The EMC Documentum Content Server
Administration and Configuration Guide contains details.
The share directory has four subdirectories:
data
The data directory contains data that is read and written by the Content Server and the clients.
The data directory has several subdirectories. Ensure that these subdirectories can be mounted
by clients.
events
The events subdirectory contains a file for any user who has queued inbox items that have not
been viewed. The files are empty. They serve as a flag to the Content Server that items that
have not been viewed are in that users inbox.
common
The common subdirectory is where the Content Server puts copies of requested content files if
users are not using client local areas and if users do not specify an alternate location for the files.
clients
The clients subdirectory contains the win and unix subdirectories, which respectively contain
the files and executables for Windows and UNIX clients.
temp
The temp subdirectory is used by the Content Server as a temporary storage space. For
example, results generated by the execution of a procedure by using the Apply methods
DO_METHOD function are stored here.
sdk
The sdk subdirectory contains two subdirectories of files that are useful to software developers.
The two subdirectories are:
Include
This subdirectory contains the dmapp.h file and the import libraries.
example
This subdirectory contains code examples.
Additional directories
The directories that are created during installation are described in Table 13, page 166 .
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
165
Directory
Description
bin
convert
dba/auth
dba/secure/ldapdb
166
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Directory
Description
Certificate database location, represented in
the ldap_config object by the certdb_location
attribute, identifies the location of the certificate
database. The attribute value is the name of
the location object pointing to the certificate
database. The value is ldapcertdb_loc. The
directory that ldapcertdb_loc points to is
DOCUMENTUM\dba\secure\ldapdb.
example*
external_apps
fusion
include*
install
java
messages
Oracle
tcf
Uniscape
unix*
unsupported
webcache
thumbsrv
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
167
Directory
Description
win*
* Optional
jboss
Script name
Location
Purpose
headstart.ebs
$DM_HOME/install/
admin
dm_apply_formats.ebs
$DM_HOME/bin
Creates or updates
format objects, which
are required for
content file operations.
dm_cas_install.ebs
$DM_HOME/install/
admin
Creates a method,
location, template
type, folder structure,
and template object for
use of the electronic
signature.
csec_plugin.ebs
$DM_HOME/install/
admin
dm_routerconv_
install.ebs
$DM_HOME/install/
admin
168
Other
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Script name
Location
Purpose
templates.ebs
$DM_HOME/install/
admin
Creates default
templates that are used
by EMC Documentum
clients for creating
new documents in the
repository.
replicate_bootstrap.
ebs
$DM_HOME/bin
desktop_client.ebs
$DM_HOME/install/
desktop_client
Creates folders
required by
Documentum Desktop
and installs the default
SmartList .
disable_fulltext_jobs.
ebs
$DM_HOME/install/
admin
dfc.ebs
$DM_HOME/install/
admin
Loads default
objects required by
the Documentum
Foundation Classes.
Dfc_bof2.ebs
$DM_HOME/install/
admin
dfc_javadbexpr.ebs
$DM_HOME/install/
admin
dm_bpmmodules_
install.ebs
$DM_HOME/install/
admin
createMethodServerObject.ebs
$DM_HOME/install/
admin
csec_plugin_upgrade_
53.ebs
$DM_HOME/install/
admin
Upgrades the
plugin for using
content-addressable
storage areas.
toolset.ebs
$DM_HOME/install/
admin
Installs repository
administration tools.
Other
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
169
Script name
Location
dm_bpm_install.ebs
$DM_HOME/install/
admin
dm_wfTimer_
upgrade.ebs
$DM_HOME/install/
admin
Purpose
Other
Converts workflow
pre- and post-timers
set up in repositories
prior to version 5.3 to
the version 6.5 timer
implementation.
dmbasic -f
dm_wfTimer_
upgrade.ebs
-e Install -repository_
nameuserpassword
dm_setup_java_
lifecycle.ebs
$DM_HOME/install/
admin
create_fulltext_objects.
ebs
$DM_HOME/install/
admin
Creates repository
objects related to
full-text indexing.
dm_ldap_install.ebs
$DM_HOME/install/
admin
Creates or upgrades
the ldap config object
type and upgrades any
existing ldap config
objects.
dm_storageservices_
install.ebs
$DM_HOME/install/
admin
dm_emailTemplate_
install.ebs
$DM_HOME/install/
admin
dm_xml_install.ebs
$DM_HOME/install/
admin
dm_gwm_install.ebs
$DM_HOME/bin
Executes scripts
that install
workflow-related
types, methods,
folders, and jobs.
upgrade_java_
methods_51.ebs
$DM_HOME/install/
tools
ci_schema_install.ebs
$DM_HOME/install/
tools
170
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Script name
Location
Purpose
display_config_setup.
ebs
$DM_HOME/install/
tools
Configures the
repository for the
Documentum Offline
Client.
offline_config_setup.
ebs
$DM_HOME/install/
tools
Migrates offline
configuration settings
from the offline_config
object to the docbase
config object.
upgrade_
contentreplication_
job.ebs
$DM_HOME/install/
admin
dm_acs_install.ebs
$DM_HOME/install/
admin
dd_populate.ebs
$DM_HOME/bin
Other
Configuration objects
Each repository contains objects that together define your configuration. These objects include:
Server config object
Docbase config object
Fulltext index objects
Location objects
Mount point objects
Storage objects
Format objects
Method objects
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
171
As you make choices about how to configure the installation and repositories, modify these objects or
add new ones. The EMC Documentum Content Server Administration and Configuration Guide contains
details on configuration.
172
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Appendix C
Troubleshooting a Content Server
Installation
This appendix contains information for troubleshooting common Content Server installation
problems. This appendix contains the following sections:
Identifying the problem and resolution, page 173
Recovering from a failed repository configuration or upgrade, page 177
Enabling tracing in repository configuration scripts, page 177
Recovering from a stalled Content Server upgrade, page 178
Symptom
Cause
Fix
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
173
Symptom
Cause
Fix
Configuration of the
docbase fails with the
message 'user must be
a valid unix user'
exec(): 0509-036
Cannot load program
/u01/app/documentum/
product/5.2/bin/
dmisvaliduser because
of the following
errors: 0509-150
Dependent module
libldap50.so could not
be loaded. 0509-022
Cannot load module
libldap50.so. 0509-026
System error: A file
or directory in the
path name does not
exist.
1.
2.
3.
1.
2.
3.
The dm_ContentReplication
method has some parameter
arguments left over from
EDMS98.
***Failed to encrypt
passwords for
docbase ec_epac,
status -1057226550
**Operation failed **
174
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Symptom
Cause
Fix
[DM_CRYPTO_E_NO_LOCAL_
COMPONENT_STORE] error:
"No local component
store for server"
Please read error log
C:\WINNT\Temp\dm_chec_
bin.ServerConfigurator.
log for more
information.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
select object_name,
object_type from
user_objects where
status='INVALID';
175
The installer hangs when the number returned by the previous command exceeds 4000.
To work around this problem, do the following: Copy and paste the following into your Telnet
session, and run the installation as usual:
cd /tmp
mkdir bin.$$
cd bin.$$
cat > mount <<EOF
#! /bin/sh
exec /bin/true
EOF
chmod 755 mount
export PATH=`pwd`:$PATH
After the installation completes, delete /tmp/bin.$$ by running the following command (in the same
Telnet session):
rm -r /tmp/bin.$$
Change MAXAPPLS using the following db2 command: UPDATE DATABASE CONFIGURATION
FOR <database_name> USING MAXAPPLS 200 AUTOMATIC MAXLOCKS 80 AUTOMATIC
2.
176
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
2.
3.
4.
5.
Check Upgrade.
This takes you through the configuration steps again and reruns the scripts that create the
repository.
2.
3.
At the where you can modify the configuration scripts, open the problem script for editing.
4.
Immediately after the connect call, add the following line to the script:
sta$ = dmAPIExec("trace,c,4," & "trace_file_name")
5.
6.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
177
Use the following instructions to identify the cyclic group. After you locate the cyclic group, contact
EMC Documentum Technical Support for assistance in correcting the problem, which requires direct
SQL Server statements in the database.
2.
If you are on UNIX or Linux, restart the Content Server using the osqltrace option:
dm_start_repositoryname -osqltrace
3.
If you are on Windows, edit the Content Server startup command, then restart the Content Server.
a.
4.
e.
Click Okay.
f.
When the Content Server appears to be unresponsive, open the Content Server log and identify
the query that is looping.
If there is a cyclic group, the last query in the log is recorded multiple times and takes this format:
Thu Jun 28 13:33:17 2007 435439: 21547[1]
SELECT SB_.R_OBJECT_ID FROM repository_owner.dm_group_s SB_
WHERE (SB_.R_OBJECT_ID=:objectp AND SB_.I_VSTAMP=:versionp)
Thu Jun 28 13:33:17 2007 435608: 21547[1] :objectp = 1200fb8080000909
Thu Jun 28 13:33:17 2007 435608: 21547[1] :versionp = 0
In the preceding example, the cyclic group has the r_object_id of 1200fb8080000909.
5.
178
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
This query returns the name of the group, which you need for determining which group is
the cyclic group.
6.
The query returns the names of each group that is a member of the problem group.
7.
Repeat steps 6 and 7 iteratively for each subgroup until you locate the cyclic group.
9.
Contact EMC Documentum Technical Support for assistance in correcting the problem.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
179
180
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Appendix D
Object Type Categories for Oracle
Database Storage
This appendix lists the object types by their size category. An object types size category is used
in two contexts:
To determine where to create the object types tables and indexes if the optional
[FUNCTION_SPECIFIC_STORAGE] parameters are defined in the server.ini file
To determine the default initial and next extent allotments for the object types tables in the RDBMS
This appendix contain the following topics:
Type categories for tablespace specifications, page 181
Type categories for extent allocation, page 182
The categories for each context are not the same. Type categories for tablespace specifications, page
181, helps you to find the categories for tablespace determination and to Type categories for extent
allocation, page 182, shows the tables listing the categories for extent allotments.
Appendix E, Defining Oracle or DB2 Database Parameters for Repository Tables provides information
about setting the default storage parameters.
dm_process
dmi_dump_object_record
dm_assembly
dm_reference
dmi_linkrecord
dm_audittrail
dm_relation
dmi_load_object_record
dm_composite
dm_router
dmi_otherfile
dm_document
dm_script
dmi_queue_item
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
181
dm_folder
dm_smart_list
dmi_replica_record
dm_locator
dm_sysobject
dmr_containment
dm_note
dm_workflow
dmr_content
dm_procedure
dm_workitem
dm_reference
dmi_dump_object_record
dm_assembly
dm_relation
dmi_load_object_record
dm_document
dm_router
dmi_object_type
dm_folder
dm_sysobject
dmi_queue_item
dm_locator
dmi_containment
dmi_replica_record
dm_note
dmr_content
dmi_subcontent
dm_filestore
dm_relation_type
dm_blobstore
dm_foreign_key
dm_server_config
dm_distributed_store
dm_format
dm_store
dm_dump_record
dm_fulltext_index
dmi_change_record
dm_docbase_config
dm_linkedstore
dmi_expr_code
182
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
dm_docbaseid_map
dm_load_record
dmi_recovery
dm_extern_file
dm_location
dmi_session
dm_extern_free
dm_mount_point
dmi_sequence
dm_extern_store
dm_opticalstore
dmi_tdk_collect
dm_extern_url
dm_outputdevice
dmi_tdk_index
dm_federation
dm_registered
dmi_vstamp
dm_cabinet
dm_domain
dm_activity
dm_client_registration
dm_expression
dm_aggr_domain
dm_client-rights
dm_federation_log
dm_application
dm_cond_expr
dm_func_expr
dm_app_ref
dm_cond_id_expr
dm_group
dm_aspect_type
dm_component
dm_job
dm_audittrail
dm_cont_transfer_config
dm_job_request
dm_bocs_config
dm_dd_attr_info
dm_key
dm_builtin_expr
dm_dd_info
dm_ldap_config
dm_cabinet
dm_dms_config
dm_lightweight
dm_literal_expr
dm_public_key_certificate
dm_user
dm_media_profile
dm_query
dm_value_assist
dm_method
dm_qual_comp
dm_value_func
dm_nls_dd_info
dm-retainer
dm_value_list
dm_plugin
dm_script
dm_value_query
dm_policy
dm_smart_list
dm_validation_descriptor
dm_process
dm_staged
dm_workflow
dm_procedure
dm_type
dm_workitem
dmc_aspect_type
dmc_relationship_def
dmc_wfsd_element_string
dmc_calendar
dmc_routcase_condition
dmc_wfsd_parent
dmc_calendar_event
dmc_scope_config_relation
dmc_wfsdrp_boolean
dmc_completed_workitem
dmc_transition_condition
dmc_wfsdrp_date
dmc_datatable
dmc_type_info
dmc_wfsdrp_double
dmc_datatable_row
dmc_wf_package_skill
dmc_wfsdrp_integer
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
183
dmc_datatable_schema
dmc_wfsd_element
dmc_wfsdrp_parent
dmc_datatable_settings
dmc_wfsd_element_boolean
dmc_wfsdrp_string
dmc_module
dmc_wfsd_element_date
dmc_workqueue
dmc_preset_info
dmc_wfsd_element_double
dmc_workqueue_policy
dmc_preset_package
dmc_wfsd_element_integer
dmi_autittrail_attrs
dmi_dist_comp _record
dmi_package
dmi_registry
dm_expr_code
dmi_transactionlog
dmi_wf_timer
dmi_workitem
184
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Appendix E
Defining Oracle or DB2 Database
Parameters for Repository Tables
To improve performance and increase the throughput of the system, you might want to control where
repository information is stored. For example, you can store frequently used data on different disks
than less frequently used data. Defining database parameters to store data in different tablespaces
also partitions data into smaller, more manageable pieces.
When a repository is created, the system automatically creates object-type tables and indexes in the
underlying database. The object-type tables and indexes are described in EMC Documentum Content
Server Fundamentals.
If you do an express installation of Content Server, by default, Content Server creates all object-type
tables and indexes in the same tablespace. The size and number of the extents allotted for each
table are determined by default configuration parameters. If you do a custom Content Server
installation, you are prompted to configure the object-type tables and indexes, and you can create
them in separate tablespaces.
You can edit the server.ini file to change any configuration parameters when the repository is created,
before you start the Content Server.
On DB2, you can change the tablespace for the object-type tables and indexes. On Oracle, you
can change two parameters:
The tablespace for the object-type tables and indexes
The size of the extents allotted for system-defined object types
You cannot change the number of extents allotted for the object types.
Under Oracle 10, always create tablespaces as locally managed tablespaces (LMTs) using the
LOCAL value. If you have dictionary managed tablespaces (DMTs) under Oracle 10, use the
Oracle DBMS_SPACE_ADMIN package to convert DMTs to LMTs, for example,
SQL> exec dbms_space_admin.Tablespace_Migrate_TO_Local('Table_space1');
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
185
The Oracle documentation set contains details on extent management and DMT-to-LMT
conversion.
FUNCTION_SPECIFIC_STORAGE
Set the parameters in the [FUNCTION_SPECIFIC_STORAGE] section to define the tablespace for the
type tables and indexes for a particular category of object types. EMC Documentum sorts object types
into the categories large and small for the purposes of defining their tablespace.
Object types in the large category are those that are expected to have a large number of object
instances. For example, dm_SysObject is in the large category.
Object types in the small category are those that are expected to have very few object instances.
For example, dm_docbase_config is in the small category. Each repository has only one Docbase
config object.
The format of the [FUNCTION_SPECIFIC_STORAGE] section is:
[FUNCTION_SPECIFIC_STORAGE]
database_table_large=tablespace_name
database_table_small=tablespace_name
database_index_large=tablespace_name
database_index_small=tablespace_name
For example, to define a tablespace for the object-type tables in the large category, include the
following lines in the server.ini file, substituting the name of the tablespace:
[FUNCTION_SPECIFIC_STORAGE]
database_table_large=tablespace_name
For example, to put the indexes for the large category in the tablespace named production_1, include
the following lines in the server.ini file:
[FUNCTION_SPECIFIC_STORAGE]
database_index_large=production_1
TYPE_SPECIFIC_STORAGE
Set the parameters in the [TYPE_SPECIFIC_STORAGE] section in the server.ini file to define a
tablespace for the type tables or indexes for a specific object type.
The format of the [TYPE_SPECIFIC_STORAGE] section is:
[TYPE_SPECIFIC_STORAGE]
database_table_typename=tablespace_name
database_index_typename=tablespace_name
186
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
You can specify the type-specific parameters individually. For example, to put the object-type
tables for the dm_SysObject type the tablespace named sysobj_space, include the following lines
in the server.ini file:
[TYPE_SPECIFIC_STORAGE]
database_table_dm_sysobject=sysobj_space
If you want to put both the tables and indexes for an object type nondefault tablespaces, define the
tablespace for each. Defining a tablespace for an object types tables does not affect where the types
indexes are stored. The system creates the indexes in the default tablespace. Defining a tablespace for
a types indexes does not affect where the types tables are stored.
For example:
[TYPE_SPECIFIC_STORAGE]
database_table_dm_sysobject=sysobj_space
database_index_dm_sysobject=sysobj_idx_space
The object-type tables and indexes of any object type not specified in a type-specific parameter are
created in the default tablespace or, if specified, in the tablespace for the types category.
If the server.ini file includes both function-specific and type-specific parameters that apply to an
object type, the type-specific parameters override the function-specific parameters. For example,
suppose you add the following function-specific and type-specific parameters to the file:
[FUNCTION_SPECIFIC_STORAGE]
database_index_large=production_1
[TYPE_SPECIFIC_STORAGE]
database_table_dm_sysobject=sysobj_space
Both parameters apply to the dm_SysObject type because dm_SysObject is in the large category.
The object-type tables for dm_SysObject are created in the sysobj_space tablespace because the
type-specific parameter overrides the function-specific parameter.
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
187
default, object-type tables and indexes are allocated the minimum number of extents when they
are created.
The percentage increase default is 10 percent. This means that extents allotted after the second extent
are increased in size by 10 percent over the previously allocated extent. For example, if the second
extents size is 100 KB, then the size of the third extent is 110 KB, 10 percent greater than 100 KB. The
fourth extent would be 121 KB, 10% greater than 110 KB.
You can change the initial and next extent default sizes for an individual object type or for an entire
category by setting parameters in the server.ini file before the repository is created.
You can change the following parameters by using the Oracle ALTER TABLE command through
sqlplus:
Next extent
Minimum extent
Maximum extent
Percentage increase
The Oracle documentation contains instructions.
typename must be the internal name of a system-defined object type. It cannot be a user-defined
object type.
The database_ini_ext_typename parameter defines the size of the initial extent allotted to the type.
The database_next_ext_typename parameter defines the size of the second extent allotted to the type.
new_value is an integer. If you include K, the value is interpreted as Kilobytes. If you include M, the
value is interpreted as Megabytes. If you include neither K nor M, the value is interpreted as bytes.
For example, to change the defaults for dm_sysobject, add the following lines to the server.ini file:
[TYPE_EXTENT_SIZE]
database_ini_ext_dm_sysobject=new_value[K|M]
database_next_ext_dm_sysobject=new_value[K|M]
You can set either parameter or both for an object type. The section can include parameter
definitions for more than one object type. For example:
[TYPE_EXTENT_SIZE]
database_ini_ext_dm_sysobject=new_value[K|M]
database_next_ext_dm_sysobject=new_value[K|M]
database_next_ext_dm_user=new_value[K|M]
188
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
The database_ini_ext_large parameter defines the size of the initial extent allotted by default
to object types categorized as large.
The database_ini_ext_small parameter defines the size of the initial extent allotted by default to
object types categorized as small.
The database_ini_ext_default parameter defines the size of the initial extent allotted by default to
object types categorized as default.
The database_next_ext_large parameter defines the size of the second extent allotted by default
to object types categorized as large.
The database_next_ext_small parameter defines the size of the second extent allotted by default to
object types categorized as small.
The database_next_ext_default parameter defines the size of the second extent allotted by default to
object types categorized as default.
new_value is an integer. If you include K, the value is interpreted as Kilobytes. If you include M, the
value is interpreted as Megabytes. If you include neither K nor M, the value is interpreted as bytes.
For example, to change the default extent sizes for all large object types, add the following
to the server.ini file:
[FUNCTION_EXTENT_SIZE]
database_ini_ext_large=new_value[K|M]
database_next_ext_large=new_value[K|M]
You can set any combination of the parameters. It is not necessary to set the parameters for all
three categories. You can also set only one of the parameters for a category. To illustrate, the
following example sets the initial extent for objects categorized as large and the next extent for
object types categorized as default:
[FUNCTION_EXTENT_SIZE]
database_ini_ext_large=200K
database_next_ext_default=120K
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
189
You cannot change the storage parameters for user-defined object types.
On DB2, if you create a tablespace for objects of type dm_SysObject, then create a user-defined object
type whose supertype is dm_SysObject, the user-defined object type is not stored in the tablespace
for dm_SysObject. Instead, the user-defined object type is stored in the default tablespace, unless
you define the tablespace for dm_SysObject in the server.ini file.
190
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Index
A
accounts
installation owner, 29
repository owner, 18, 30, 41
active/active clusters, 147
described, 135, 146
first cluster resource group, 146 to 147
repository configuration, 147
server.ini file, 147
verifying failover, 148
active/passive clusters
configuring, 137
configuring the repository, 138
connection broker configuration, 143
creating resource groups, 137
creating resources, 144
described, 134
installing Content Server, 138
verifying failover, 145
administrative tool scripts, 80
aek.key file, 155
B
backing up key store files, 83
C
ci_schema_install.ebs script, 170
client connections, 20
clients directory, 165
cluster resource groups
creating, 137
resources, 137
cluster resources
creating, 144
code pages
supported, 28
common directory, 165
config directory, 164
configuration
basic server installation, 168
default, 168
file locations, 165
objects, described, 171
overview, 172
requirements, 32
configuration decisions
repository size, 18
configuring
repositories, 67, 73
configuring Content Server, 17
CONNECT privileges, 42
connecting to database, 17
connection broker
required ports, 21
connection brokers
described, 15
in resource groups, 133
Microsoft Cluster Services, 143
Content Server
configuration, 17
connection types, 20
Content Storage Services, 22
in resource groups, 133
installation owner, 29
internationalization, 28
Retention Policy Services, 22
Trusted Content Services, 22
uninstalling, 109
uninstalling Content Server, 107 to 109
Content Services for retention type store
described, 22
Content Storage Services, 22
content-addressed storage, 22
copying repositories, 155
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
191
Index
create_fulltext_objects.ebs, 170
CSEC. See Content Services for retention
type store
csec_plugin_upgrade_53.ebs, 169
cyclic groups, 178
D
data directories, described, 18, 164
database
code page, 40
database accounts, 17
database location, 136
database requirements
repository owner, 30, 42
database_refresh_interval key, 91
databases
DB2, 47
installation location, 17
Oracle requirements, 42
requirements, 40
requirements for upgrade, 90
SQL Server requirements, 44
Sybase, 46
UTF-8, 90
Windows requirements, 41
DB2
current configuration, 48
environment variables, 47
performance wizard, 47
repository owner requirements, 42
requirements, 47
dba directory, 164
dd_populate.ebs script, 171
desktop_client.ebs script, 169
dfc.ebs script, 169
directories
clients, 165
common area, 165
config, 164
content storage, 137
data, 18, 164
dba, 164
DM_HOME, 164
event subdirectory, 165
events, 165
log, 164
product, 163
required for installation, 32
SDK, 165
192
share, 165
temp, 165
version, 32
disks, shared, 137
display_config_setup.ebs script, 171
distributed configurations
installation requirements, 112
shared content model, 112
upgrading, 114
UTC time, 112
distributed content, 114
dm_apply_formats.ebs script, 168
dm_cas_install.ebs, 168
dm_change_password, 32
dm_check_password, 32
dm_gwm_install.ebs script, 170
DM_HOME environment variable, 32, 164
dm_ldap_install.ebs script, 170
dm_root_task script, 32
dm_routerConv_install.ebs script, 168
dm_wfTimer_upgrade.ebs, 170
dm_xml_install.ebs script, 170
docu, 19
Documentum Administrator
adding groups, 84
Documentum Content Intelligence
Services, 170
DOCUMENTUM environment variable, 32
Documentum Foundation Classes
dfc.ebs script, 169
Documentum Offline Client, 171
E
EMC Documentum Site Caching
Services, 112
EMC Documentum Web Publisher, 112
enabling repository configuration script
tracing, 177
environment variables, 32
DB2, 47
DM_HOME, 32
DOCUMENTUM, 32
installation owner environment, 161
LANG, 28
ORACLE_HOME, 43
Sybase, 46
events subdirectory, 165
exiting installation, 63
external password checking, 30
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Index
F
failover, 134
failover verification, 148
failover, verifying, 145
files
aek.key, 155
services, 33
Sybase configuration, 46
tnsnames.ora, 42 to 43
G
global registry
network locations, 23
SBOs, 23
groups, 84
installation owner, 30
H
hardware requirements, 25
headstart.ebs script, 168
host locales, 28
host preparation
UNIX, 31
hostname requirement, 27
hosts, 27
I
index agent
required ports, 21
index server
required ports, 21
installation owner
case-sensitivity of username, 29
described, 29
environment variables, 161
password, 29
required permissions On UNIX and
Linux, 30
root account, 29
Sybase requirements, 46
uninstalling Content Server, 107 to 109
username, 29
Windows requirements, 30
Windows rights, 30
installation owner group, 30
installing
copying server software, 55
sequence, 55
installing content server
required ports, 21
installing Content Server
basic configuration for server, 168
configuration requirements, 32
configuration scripts, 168
configuring repositories, 138, 147
connection brokers, 15
copying software, 59, 63
database, 47
DB2, 47
directory structure, 163
environment variables, 161
exiting, 63
hardware requirements, 25
Microsoft Cluster Services, 133
multiple servers on UNIX and
Linux, 151
multiple servers on Windows, 151
preparing, 25
repository size, 18
typical configurations, 15
UNIX group accounts required, 30
internationalization, 28
database code page, 40
server host code pages, 28
SQL Server, 40
Unicode, 40
UTF-8, 90
J
Java method server
required ports, 21
K
key store files, backing up, 83
L
LANG environment variable, 28
loadbalanced configurations, 112
local administrators group, 30
local database installations, 17
log directory, 164
logs, server installation, 80
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
193
Index
passwords, 29, 31
port numbers, 33
ports
native connections, 33
required, 21
secure connections, 33
postinstallation tasks
adding groups, 84
adding users, 84
administrative tool script, 80
PURGE AUDIT, enabling, 84
reviewing server installation logs, 80
preinstallation requirements
database, 17
database administrator account, 42
database code page, 40
DB2, 47
directories, 32
DM_HOME, 32
environment variables, 161
hostname, 27
hosts, 27
installation directory, 32
repository owner, 18, 41
supported code pages, 28
XWindows, 31
product directory, described, 163
PURGE AUDIT job, 84
N
native connections, 20, 33
network cards, 27
network location objects, 23
O
object replication, 114
object type categories, 181
ODBC configuration, 44
offline_config_setup.ebs script, 171
Oracle
CONNECT privileges, 42
database aliases, 43
environment variables, 43
ORACLE_HOME, 43
preinstallation requirements, 43
repository owner requirements, 42
repository sizes, 44
RESOURCE privileges, 42
TNS aliases, 43
tnsnames.ora file, 43
ORACLE_HOME environment
variable, 43
order of uninstalling, 107
194
R
remote database installations, 17
replicate_bootstrap.ebs script, 169
repositories
active/active clusters, 147
active/passive cluster, 137
configuring, 67, 73, 138, 147
copying, 155
global registry, 23
owner, 42
services file entries, 33
size, 18
user authentication, 31
users, 31
repository
ID, 19
name, 19
repository configuration failure, 177
repository configuration scripts
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
Index
ci_schema_install.ebs, 170
create_fulltext_objects.ebs, 170
csec_plugin_upgrade_53.ebs, 169
dd_populate_install.ebs, 171
desktop_client.ebs, 169
dfc.ebs, 169
display_config_setup.ebs, 171
dm_apply_formats.ebs, 168
dm_cas_install.ebs, 168
dm_gwm_install.ebs, 170
dm_ldap_install.ebs, 170
dm_routerConv_install.ebs, 168
dm_wfTimer_upgrade.ebs, 170
dm_xml_install.ebs, 170
headstart.ebs, 168
offline_config_setup.ebs, 171
replicate_bootstrap.ebs, 169
templates.ebs, 169
toolset.ebs, 169
upgrade_java_methods_51.ebs, 170
repository copies, 155
repository federations
upgrading, 114
repository owner
database privileges, 42
database requirements, 42
DB2, 42
described, 18, 41
Microsoft Cluster Services, 30
Oracle, 42
password, 31
RDBMS account, 18, 41
required Windows privileges, 42
SQL Server, 42
username, 30
Windows, 30
requirements
ports, 21
reserved terms, 19
resource groups, 133
RESOURCE privileges, 42
Retention Policy Services, 22
root account, 29
root password, 90
root task, 32
S
scripts
dm_root_task, 32
T
temp directory, described, 165
templates.ebs script, 169
Terminal Services, 114
testing an upgrade, 155
tnsnames.ora file, 42 to 43
toolset.ebs script, 169
troubleshooting
diagnosis, 173
enabling repository configuration
script tracing, 177
repository configuration failure, 177
stalled server upgrade, 178
Trusted Content Services
described, 22
port numbers, 33
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide
195
Index
services file, 33
U
Unicode, 40
uninstalling Content Server, 109
Content Server, 107
installation owner, 107 to 109
order, 107
requirements, 107 to 109
UNIX
host preparation, 31
installing multiple servers, 151
UNIX requirements, 32
directories, 32
environment variables, 32, 161
installation owner account, 30
root account, 29
semaphores, 31
services file, 33
shared memory, 31
shells, 161
space available, 32
XWindows, 31
unsecure connections, 20
upgrade_java_methods_51.ebs script, 170
upgrading Content Server
database_refresh_interval ey, 91
described, 87
distributed configurations, 114
distributed content, 114
effects on system, 87
object replication, 114
196
V
verifying failover, 145, 148
version directory, 32
virtual IP addresses, 133
virtual network hostnames, 133
W
Windows
installing multiple servers, 151
repository owner, 42
user authentication, 31
Windows requirements
database service, 41
installation owner account, 29
installation owner user rights, 30
local administrators group, 30
repository owner, 30
Terminal Services, 114
X
XWindows, 31
EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide