EMC® Documentum® Content Server Version 6.5 SP2 Installation Guide 300-007-195-A02 EMC Corporation Coporse Headquarter: Hopkinton, MA 01748-9103 1-508-435-1000 nn EMC com,Copynight® 1992- 2009 EMC Corporation. Allrights everved, Published June2009 EMC believer he agormaton in this publication is acurse a ofits publicaion date, Theinformation se abject to change ‘thot notice. pu ® ™ ‘THE INFORMATION IN THIS PUBLICATION Is PROVIDED ASIS. EMC CORPORATION MAKES NO REPRESENTATIONS GR WARRANTIES OF ANY FIND WITH RESPECT T0 THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE ‘Use, copying, and ditbution of any EMC softuare described inthis publication requires am applicable sftwarelicense For themort up-to-datelising of EMC product names, ee EMC Corporation Tademazks on EMC com. ‘All other trademarks used herein ae theprop ty of the respective rma.Table of Contents Preface Chapter 1 Chapter 2 Planning for Content Server Installation Content Server and repository overview Content Server installation models Basic installation model Singlerepository model with content stored at primary site Singlerepository distributed model with content in a distributed storage area. Multirepository distributed modal by using object replication. Multirepository distributed model working as afederation. Configuration decisions Location for installing the rdational database. Usemame Content Server will use to connect to the database Size of repository to create Location for storing the content files Name and D to assign to therepository. Connection brokers to which to project Content Server information Permit orrequire secure SSL. connections Authenticate users Ports to reserve for Content Server use. Repository to use as the global registry Extended services products to license Preparing the Host for Content Server Installation Host preparation checklist Hardware and network environment requirements Intemnationalization 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 ‘The installation ownerin SQL Server repositories, Setting up the repository owner account Repository owner account naming requirements Settung up repository user accounts Preparing UNIX and Limuchosts edimemory and semaphore requirements XWindows requirement. The mp directory. Root user password Setting Documentum environment variables Setting up the services file EMG Documentum Contant Server Version 65, SP2 Intalaton GuideTable of Contents Chapter 3 Chapter 4 Chapter 5 Preparing Windows hosts Setting the PATH Environment Var able Running WDK Applications on the Content Server Host. Restricted Characters Regional Settings SMTP Server on Windows Preparing the Database for Content Server Installation Database preparation checklists. Requirements or all databases Database codepage Database versions. Database service on Windows Repository owner account. Database administrator account. Oraclerequirements Entries in mmames oraiile. Oracle repository sizes SQL Server requirements Configuring an ODBC Data Source for SOL Server SQL Server repository sizes, Sybase requirements. Sybase repository sizes DB2 requirements. DB2 performance wizard requirements Running multiple Content Servers on the DB2 host. DB2 repository sizes Installing Content Server Installation and configuration checklist Installing Content Server software on aUNDX or Linux host. Installing Content Server software on a Windows host. Configuring Content Server and the repository on aUNIX or Linux host Running the administrative tool script manually Configuring Content Server and the repository on a Windows host Reviewing the Content Server installation logs. Completing the Installation Running dm_root_task manually on UNIX or Linc hosts Changing the default passphrase Binding Content Server to anetwork card Configuring JBoss application servers for SSL. Changing the installation owner account, Backing up key store files. Starting Content Server and the connection broker. Adding users and groupsto arepository Enabling jobs after installation. Enabling the purge audit job Creating additional repositories or connection brokers. 75 75 76 76 76 7 79 79 80 80 80 a EMC Documentum Content Server Veision 65, SP2 Installation Guide“able of Contents Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Upgrading Content Server Upgrade checklist. ‘Migrating the database to UTF-8 The database refresh interval key. Oracle optimization setting Completing workflows before an upgrade Upgrading sequence considerations, Upgrading from 5x Upgrading the Content Server software Using the update statistics tool ‘Arguments Adding desmiptorsto aglobal registry Uninstalling Content Server Order of uninstalling components Deleting arepository Deleting a connection broker Uninstalling the Content Server software Installing Documentum Messaging Services Configuration requirements ‘The dms properties file File administration Changing the JMX user password. Specifying the cleanup interval for expired messages Preinstallation requirements. Installing DMS Uninstalling DMS. On Windows hosts On UNIX and Linux: hosts Stating and stopping DMS (On Windows hosts On UNIX and Linux: hosts Installing Remote Content-File Servers in Distributed or Load-Balanced Configurations Preinstallation requirements. Installing and configuring the content-file server Upgrading a distibuted orload-ba anced configuration Deleting acontent-fle server Installing Content Server with Microsoft Cluster Services Overview Choosing a configuration. Preinstallation requirements. Configuring an activelp assive cluster. Creating the duster resource group Installing Content Server software on the nodes Configuring Content Server Configuring the connection brokers. EMG Dacumentum Content Server Version 65, SP2 Intalaton Guide 83 83 86 86 86 86 7 7 88 a1 a1 93 95 95 96 7 7 99 99 100 100 100 100 101 101 104 104 105 105 105 106 107 107 108 109 2 us us us 7 us us ng 9 124Table of Contents Chapter 11 Chapter 12 Appendix A Appendix B Appendix C Appendix D Creating additional cluster resources. Verifying failover, Configuring an active/active duster. Creating the first duster resource group. Installing Content Server software on the hosts Configuring Content Server on the first and second nodes, Configuring the second cluster resource group. Modifying serverini and dfc properties Creating the connection broker generic serviceresource, Creating the Content Server service resource Verifying failover, Upgrading Content Server installed with Cluster Services. Configuring Multiple Content Servers on a Single Host for a Particular Repository Windows hosts, UNDChosts Creating a repository copy to test an upgrade Creating the test environment Precopying tasks Copying arepository Required Environment Variables for UNIX and Linux Content Server Installation Directories and Repository Configuration Scripts Content Server installation file structure. uninst data. dba. fulltet. product. server_uninstall share Additional directories Scripts run during installation or upgrade, Configuration objects. ‘Troubleshooting a Content Server Installation Identifying the problem and resolution. Error during session construction on Solaris DB2 Recovering from a failed repository configuration or upgrade. Enabling tracing in repository configuration sipts Recovering from a stalled Content Server upgrade. Object Type Categories for Oracle Database Storage ‘Type categories for tablespace specifications, ‘Type categories for extent allocation ‘Object types categorized aslarge Object types categorized as small Object types categorized as default. 125 128 wz 17 128 128 128 128 129 129 130 130 133 133 135 137 137 138 139 3 9 ug ug 150 150 150 150 150 151 151 154 157 159 159 162 162 163 163 165 165 166 166 166 167 EMC Documentum Content Server Veision 65, SP2 Installation Guide“able of Contents AppendixE Defining Oracle or DB2 Database Parameters for Repository Tables 169 Defining the tablespace 169 FUNCTION_SPECIFIC_ STORAGE 170 TYPE_SPECIFIC_STORAGE 170 Defining the Oracle extent sizes V7 Changing storage parameters for individual object types on Oracle 172 Changing storage parameters for categories of types on Oracle 172 User-defined object types. 173 EMC Documentum Contant Server Version 65, SP2 Intalation Guide 7Table of Contents Figurel Figure2 Figure3 Figured. Figure 5. Figure6 Figure? Figures. Figured. List of Figures Repository structure Basic installation model and component installation order: BOCS servers at remote sites communicating with the primay site. Remote sites using primary site's ACS server. BOCS servers at remote sites communicating with the primay site. Object replication model Federation model Activelpassive duster Active/active cluster. u 15 Vv 18 19 20 20 us 7 EMC Documentum Content Server Version 65, SP2 Installation Guide“able of Contents Table Table2 Table3 Tabled Tables Tables. Table? Tables Tabled. Table10. Table 11 Table 12. Table 13. Table 14. Table 15. Table 16. List of Tables Host preparation checklist General database installation and configuration checklist Oracle database installation and configuration checklist. DB2 database installation and configuration checklist DB2 database installation and configuration checklist 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 sipts. ‘Troubleshooting checklist EMC Documentum Contant Server Version 65, SP2 Intalation Guide 29 a 2 B B B 4 56 83 a1 Mi 138 43 152 154 159‘Table of Contents 10 EMC Documentum Content Server Vesion 6.5, SP2 Installation GuidePreface Purpose of the manual ‘This guide contains information and instructions you need to irutll or upgrade EMC Documentum Content Server. If you are installing fulltext indedng, consult the Content Server Fulltext Indexing System Installation anid Administration 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 Deseription June 2009 Initia publication EMC Documentum Contant Server Version 65, SP2 Intalation Guide "Preface 2 EMC Documentum Content Server Vesion 6.5, SP2 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 * Content Server and repository overview, page13 * Content Server installation models, page 14 Basic installation model, page 15 + Singlerepository model with content sored at primary ste, page 16 + Singlereposttory distubuted model with contentin a dishibuted storage area page 18 + Multirepository distibuted model by using object replication, page 19 + Multixepository distibuted model working as afederation, page 20 + Configuration decisions, page 21 Content Server and repository overview Content Server software manages the repository and provides content management capabilities. The repository consists of three main components: afile store containing the content assets, attribute tables within arelational database, and fulltext indexes. A repository can store its content files in any of the following: ‘+ Directories on the Content Server host's file system, ‘+ Directories on aremote host to which Content Server has access + A-vaniety 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 the repository are composed of content files (the source file in its native format) and attributes (aso 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. ‘The repository uses the metadata to organize the content, and users can use metadata to search for content. Metadatais stored in tablesin arelational database as sets of attributes. A configurable and extensible set of attributes is stored for each item. A set of attributes can indlude attributes with a single value, EMC Documentum Contant Server Version 65, SP2 Intalation Guide 1Planning for Content Server instalation such as the document’ globally unique identifier. Attributes can also have multiple values, such as Keywords that desabe the content Figure 1, page 14 shows the basic structure of arepository. Figure 1. Repository structure Repository 1D | Date | Tone | Author | Sect 1 | Date | Time | Author | Svbect 1 [Date | Tine | Author [ Sobect Content Files Database Tables Full-text Indexes A dent application views the repository as a single repository whose implementation details are irrelevant 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 dataremain synchronized. Content Server installation models ‘You can install Content Server and the repository by following different moddls: + Basic installation model, page 15 + Singlerepository model with content stored at primary ste, page 16 + Singlereposttory distubuted model with contentin a distributed storage area page 18, + Multirepository distibuted model by using object replication, page 19. + Multixepository distibuted model working as afederation, page 20 14 EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation Basic installation model A basic installation of Content Server consists of several interrelated components + File stores, which contain the content files for objects stored in the repository + Arelational database, which stores metadata about the content files. + Content Server; which manages the repository. Content Server itself consists of several distinct process and components, induding an application server reserved forits intemal use. The Coutert Server Administration Guide contains information about theintemal structure of Content Server. ‘+ A connection broker, which provides rep ository connection information to client applications. + Documentum Foundation Classes (DFC), which provide the programming interface that client applications use to communicate with Content Server. + An SMTP server, which Content Server uses to send tasks and notification messages to user mailboxes when necessary. ‘You can install Content Server in different configurations. In the most basic configuration, whichis typically used in development environments, the Content Server, database, and content files al reside on the same host. In production environments, the Content Server, database, and content files are almost always installed on different hosts for increased performance Figure2, page 15 shows abasic installation model and the order in which components areinstalled, Figure 2. Basic installation model and component installation order are poston, ‘You can install and start a connection broker on the Content Server host as patt of the installation process, or the Content Server can project to one or more connection brokers located on a different host, thereby making itself avalableto cient applications. Chapter 4, Installing Content Saver provides details on installing and starting a connection broker. When a cient application wants to connect to arepository, the fellowing 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 Serveris using, 3. The dient application uses that information to open a connection to Content Server. EMC Documentum Contant Server Version 65, SP2 Intalation Guide 6Planning for Content Server instalation 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. ‘Thefile stores, relational database, and SMTP server must beinstalled 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, Prepaing 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 aremote 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. ‘The installation or deployment guide for the application, such as the Webtep Deployment Guide, contains information about installing client applications. Single-repository model with content stored at primary site Inthis modal, remote users connect through web browsers by using aWDK-based client application. ‘They access content stored at the primary site through either an ACS or BOCS server ‘+ AnACS serveris dedicated to processing content request. It does not process metadatanor does it wnite content to storage. ‘+ ABOCS server is a cache server that communicates with ACS servers, It does not process metadata nor does it write content to storage. ‘Two configurations for this model est: ‘+ The configuration includes aBOCS server, and dients at remote sites use the BOCS server to access content as shown in Figure 3, page 17. 6 EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation Figure 3. BOCS servers at remote sites communicating with the primary site Prenay ste (Munich) {net ioe = munich) g 2 content sera wi estore acs ' a Wied server Remote sta (@argatr) (roves = anglers) Rema 8 Tokj0) (net lce = ohyo) ‘+The configuration includes an ACS server, and clients at remote sites use the ACS server at the primary site as shown in Figure 4, page 18: EMC Documentum Contant Server Version 65, SP2 Intalation Guide wPlanning for Content Server instalation Figure 4. Remote sites using primary site's ACS server Play se Muh Inetioe= muon) gs Content server wi estore aes Bie urate te (Bangslors] | Remote a Tokyo) Inetloc= sangre) inetios= tokyo) ‘The Distributed Configuration Guide provides details about this model Single-repository distributed model with content ina distributed storage area In this model, content is stored in a distributed storage area with multiple comp onent storage areas as, shown in Figure 5, page 19 8 EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation Figure 5. BOCS servers at remote sites communicating with the primary site Prmary Sto (Yunch) tate smh 8 08 ‘Sore cl) / \ ~ © Woe 2 Digrtedsioe cists Sire ‘monet 2 a Canposents Canes Sere Ganataste —_—Rapote ste | Connt Sener "ee arn fee me wetkentars) tlormsene) “gy Cena Sore cone Serer wes wes we Cen J eb Cont Renote sie Fano Sto ‘se orn) Web Cet J Web cent Renote sie Feat ste ‘Gon Ta ‘The Distributed Configuration Guide provides details about this moda, Multirepository distributed model by using object replication In this modal, objects consisting of content and metadata are distributed between repositories. ‘The distribution can occur through user-defined object replication jobs, orintemally, when auser manipulates objects from multiple rep ositories in onerepository session. Figure6, page 20 illustrates object replication: EMC Documentum Contant Server Version 65, SP2 Intalation Guide 1°Planning for Content Server instalation Figure 6. Object replication mode! London ‘The Distributed Configuration Guide provides details about this moda, Multirepository federation tributed model working as a A federation modal consists of multiple repositories where oneis the governing repository and the remainder are member repositories. Placing multiple repositories into a federation model ensures that users, groups, and ACLs remain synchronized across all repositories in the federation. Figure?, page 20 illustrates the federation model: Figure 7. Federation model Member Site (Spain) =] Governing Site (Munich) epson Member Site (London) Repos ‘The Distributed Configuration Guide provides details about this moda, » EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation 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, Installing Content Server provide checklists where you can record your decisions for reference during the instalation procedure. + Location for installing the relational database, page 21 + Username Content Server will use to connect tothe database, page 22 + Size of repository to create, page 22 + Location for storing the content files, page 22 + Name and ID to assign to the repoattory, page 23 + Connection brokers to which to project Content Server information, page23 + Permit or require secure SSL connections, page 24 + Ports to reserve for Content Server use, page 25 # Repository to use as the global registry, page 25 * Extended services products to license, page 26 Location for installing the relational database ‘You can instal the relational database that stores repository metadata either locally on the same host as Content Server or remotely on a separate host running any operating system supported by the database vendor. For example, Content Server can be installed on aWindows host and use adatabase installed on a Solaris host. In aproduction environment, the database is almost always installed on a separate host for performance reasons, Before you install Content Server — Install the database management system and create a database in which Content Server will create the repository metadata tables. If you install the database on a separate host, also install the database client software on the Content Server host. + Forremote database installations, verify that you can connect to the database by using a database client from the system where you intend to install Content Server, * Forlocal database installations on aUNDChost, verify that the system path includes theinstallation directory forthe database. On Windows hosts, theinstaller up dates the system path automatically. Chapter3, Preparing the D atabase for Content Server Installation provides details about installing the relational database EMC Documentum Contant Server Version 65, SP2 Intalation Guide aPlanning for Content Server instalation Username Content Server will use to connect to the database Content Server connects to the database with auser account called the repository owner account. The repository owner must have a database user account, This database user account must provide Content Server with access to the database tables underlying the repository. ‘You can create the repository owner account in the database before installing Content Server, or you can allow the Content Server configuration program to create the account. The account must have the appropriate privileges to perform the following tasks: = Connect to the database © Createtables, views, and indexes in the database ‘+ Insert records (rows) into the tables + Drop tables, views, and indexes Before you install Content Server — Decide whether to create the database account for the repository yourself or allow the Content Server configuration program to create the account. If you allow the Content Server configuration program to create the database account, it automatically grants the account the proper privileges. If you create the account in advance, grant the account the proper privileges as desaibed in Repository owner account, page 45 Size of repository to create Duringrepository configuration, you are asked to choose arepository size. Therepository size option determines the size of the tablespaces within the database, how data and indexes are distributed within the database, log file sizes, and whether these settings can be configured, Before you install Content Server — Decide what size of repository to create, based on theprojected amount of content that will be stored in the repository. The details and initial sizes differ depending on the database vendor. The individual sections for each database vendor in Chapter 3, Preparing the Database for Content Server Installation provide details. Location for storing the content files Arrepository can store its content files in a variety of storage areas, such as + Ina directory structurein the Content Server host's file system or on aremote host + Onaretention type store + In ardlationa database as binary large objects (BLOBs), or as datain varchar fidlds + Ina etamal storage area such as alegacy system Largerepositories can have multiple file storage areas, of different types, with defined business rules that specify which content is stored in which storage areas 2 EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation ‘The Content Server installation program creates one file-system storage area which is used asthe default storage area After the initial installation, you can add additional storage areas and the ‘business rules for dividing content between them by using Documentum Administrator. The Content Server Administration Guide and to the Documentum Acininistrator User Guide provideinformation and instructions about adding additional storage areas, Before you install Content Server — Choose alocation for the default content file storage area, ‘which theinstallation program calls the data directory. The data directory can be on the Content Server host or on another host that Content Server can access over thenetwork. Ensure that thelocation you choose for the data directory has sufficient free space for the content files that will be added to it. ‘The Content Server configuration program creates the data directory on the local host in the directory. Documentum\ data unless you provide a different location, Name and ID to assign to the repository Each repository requires auniquename and ID of up to 32 characters. The name must condst of letters, numbers, or underscores (). The first character must be aletter. Therepository name cannot include spaces ornonalphanumaric characters. All letters and numbers in thename must be ASCII characters, The repository name " docu’ isresarved by EMC Documentum ‘The repository ID can be any number from! to 16777215 and must not start with azero. Valid repository IDs are shipped with the Content Server software. You may also choose your own repository IDs, provided that each repository has arepository ID that is uniquein your network and conforms to other repository ID requirements. You can request additional repository IDs from EMC Documentum, which ensures that the ID for each repository is unique. You can submit arequest for a repository ID from the following link on the EMC Powerlink web site http://powerlink.eme.com Before you install Content Server — Decide on arepository name and repository ID for thenew repository you will create. Connection brokers to which to project Content Server information ‘When Content Server stats it automatically broadcasts information about itself to one or more connection brokers. Each connection broker that receives the broadcast adds the Content Server to its list of avallable servers. Before you install Content Server — ‘+ Record the hostname and port number for each edsting connection broker to which you want to broadcast Content Server connection information, + Decide whether you need to create additional connection brokers on the Content Server host. ‘The Content Server configuration program by default creates a connection broker on the Content Server host and configures the Content Server to broadcast its connection information to that connection broker. You have the option to create multiple connection brokersif, for example, you ‘want different brokers for different client applications. If you want Content Server to broadcast its EMC Documentum Contant Server Version 65, SP2 Intalation Guide 2Planning for Content Server instalation connection information to esting connection brokers on remote hosts, you can configure this option after the installation, ‘+ Identify an open port for thenew connection broker to listen on. The default port for the default connection broker is 1499. If you are using the default port number, ensure that thenext port number (1490) is available for use because the connection broker requires that two ports be reserved. If you create multiple connection brokers on the host, assign a unique port number to each broker Permit or require secure SSL connections (Client applications can connect to Content Server through a standard native port or through asecure port that uses Secure Sockets Layer (SSL) for encryption. During repository configuration, you are asked what type of connection clients will useto connect to the repository. The choices are ‘+ Native — Content Serverlistens for client connection requests only on ports that arenot SSL ports, Content Server refuses requests for a secure connection, ‘+ Secure — Content Server listens for client connection requests only on a secure SSL port. The client and Content Server do not use SSL authentication to authenticate each other. However, the information exchanged between the cient and Content Server is encrypted. Content Server refuses connection requests other than SSL. connections, ‘+ Native and secure — Content Server accepts both native and secure connection requests Before you install Content Server — Decide what type of dient connections to accept. Authenticate users User authentication typically occurs when auser attempts to connect to arepository. Content Server determines whether the user is avalid, active repository user and, if so, authenticates the username and password. You can perform user authentication using one of the following methods: The default mechanism ‘The default mechanism authenticates the user against the operating system. + Accustom 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. + AnLDAP directory server If you use a directory server, you have the following options: — Authenticate against the directory server directly, using a secure or anonsecure connection, — Authenticate using an LDAP-enabled dm_check_password program. + A authentication plugin 24 EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation Authentication plugins provide an altemate way to customize user authentication, EMC Documentum provides one authentication plugin with Content Server. The plugin allows you to usetheNetegnity SiteMinder Policy Server with Content Server. The plugin supports Web-based Single Sign-On (SSO) and strong authentication. © Aninline password ‘Avuser can be authenticated using an encrypted password that is stored in the user_password attribute of the user object. Ports to reserve for Content Server use Content Server and its components use anumber of ports on the host: ‘= Content Server uses two consecutive port numbers for native cient connections and secure client connections. — On Windows hosts, set the port numbers by using the Content Server configuration program. — On UNDX and Linux hosts, set the port numbers in the services file before installing Content Server. Setting up the services file. page 36 provides details on how to set port numbers in the services file. ‘+ The application server that Content Server installs listens on one port for administration standard connections. By default, st uses port 9080. ‘+ The connection broker requires two ports on which to listen, The default connection broker portis, 1489. If you areusing the default port number, ensure that thenext port number (1490) is available for use because the connection broker requires that two ports be reserved. Before you install Content Server — Identify available ports to use for Content Server and its components. Make sure none of the selected ports are being used for other purposes. Repository to use as the global registry ‘When an EMC Documentum installation includes multiple repositories, certain installation-wwide elements are shared among all repositories. For example, a distributed configuration uses objects called network locations which Content Server uses to determine which storage areas are physically close to which client applications. All repositories share the same network location objects ‘To manage these installation-wide elements, each EMC Documentum installation includes a central repository called the global registry. The global registry is arepository like any other repository. except that all other repositories connect to it when they need an installation-wide element. When you install arepository, either identify it as the global registry or designate how to connect to another global registry repository. Ifyou have a onerepository implementation, that repository can be both a content repository and a global registry. If you have a Content Server implementation larger than a depatmental one, you. might consider creating a separate repository and designate that repository to bethe global registry only. EMC Documentum Contant Server Version 65, SP2 Intalation Guide 28Planning for Content Server instalation ‘The Content Server configuration program enables you to do the following now or later ‘+ Use the current repository as a global registry. Specify a different repository as a global registry. A global registry user is created in all repositories, regardless of whether therepository is configured as a global registry. ‘+ Ifyou configure the repository as a global registry, you provide the usemame and password for the global registry user and the user stateis set to Active ‘+ Ifyou donot configure the repository as a global registry, a global registry useris created with the default usemame dmm_bof_registry and the user stateis set to Inactive This user hasread access to objects in a few folders in the System cabinet of the repository only. Before you install Content Server — Determine whether the repository you create will be a global registry. Ifyou areinstalling a single production repository, designateit as a global registry. Ifthe site has multiple production repositories, designate only one repository as a global registry. To designate anew repository as a global registry provide ausemame 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 usemame and password so that you can provideit when installing other EMC Documentum products that require global registry access. ‘The user must have read access to objects in the /System/Modules and /SystemiN etworkLocations folders. Donot use the repository owners credentials or the installation owner's credentials. Ifyou plan to connect to an existing global registry repository, provide the repository name the usemame, and the password of the global registry userin 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 alater time. If you select this option, use Documentum Administrator to identify the global registry and enter the appropriate connection information. The Content Server Ahuistration Guide provides instructions Extended services products to license ‘You can use the Content Server installation program to activate extended service features by entering the license code for those features. You can activate extended service features either at installation ‘time by using the installation program or later by using the Content Server configuration program. ‘The extended feature licenses available from the Content Server installation program are: ‘+ Trusted Content Services provides additional security features, such as enarypted file stores, in which content files are encrypted and secure socket layer (SSL) communications between Content Server and DMCL, ‘= Content Services for EMC Centera and Network Appliance SnapLock adds support forretention, type stores, which provide content storage with guaranteed retention and immutability. SnapLock is afeature of Filer, aNAS storage system from Network Appliance You can create a SnapLock volumein one of two modes: Enterprise and Compliance. The difference between the Ey EMC Documentum Content Server Version 65, SP2 Installation GuidePlanning for Content Server instalation ‘two modesis that on the Compliance SnapLock volume, a default (and minimum) retention of 30 years is applied to the content files created in that volume ‘+ High-Volume Server is an extension of Content Server that supports features implemented to solve conunon problems with large content stores. The three broad areas of enhancements that make up High-Volume Server are — Lightweight system objects — Batch operations and currency scoping — Database Partitioning ‘= Content Storage Services enables you to define business rules to govern where content files are stored ‘+ Retention Policy Services is a compliance-oriented feature that gives you control over how long and under what circumstances documents and other objects areretained in arep ository. + Records Manager provides archiving options for business records ‘Physical Records Manager (PRM) enables management of paper assets by providing library services to reserve, borrow, and retum physical objects. PRM also includes barcode management capability for tracking physical objects. ‘Trusted Content Services, Content Services for EMC Centera, SnapLock, and High-Volume Server are installation-wide options, so if you enable them for one repository, their features are available in all repositories. If you want to enable them after you have already installed Content Server, you need torun the Content Server installation program again and enable these options. The other extended services options are enabled in each repository separately. ‘The Content Server Fundamentals Guide provides details about these products and the features they enable. Before you install Content Server — Identify which extended services to enable and obtain the license code for those services. EMC Documentum Contant Server Version 65, SP2 Intalation Guide aPlanning for Content Sever instalation 28 EMC Documentum Content Server Vesion 6.5, SP2 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. Chapter3, Prep aring 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 31 + Intemationalization settings, page 32 * Setting up user accounts, page 33 © Preparing UNDC and Linux: hosts, page 35 Host preparation checklist Use the following checklist to prepare the host for Content Server installation In the Value column, enter the required value that you will be prompted for during database installation and configuration, Table 1. Host preparation checklist Task Resource Value Validatethehardware configuration Content Server Release Motes Validate the operating system Content Server Release Motes and operating system-database configuration combination. Ensure that the Content Serverhost’s video card uses aminimum of 256 colors. EMC Documentum Contant Server Version 65, SP2 Intalation Guide 2Preparing the Host for Content Server Installation Task Resource Value ‘On UNIX and Linux hosts, ensure Shared memory and semaphore that atleast 2MB of shared memory requirements, page35 is allocated and that semaphores are enabled (On Windows, obtan thename of the SMTP hostname: SMTP host that the Content Server ‘will use for email notifications. Decide whether to use an LDAP Appendix C, "Using an LDAP directory server. Directory Server,” in the Content Server Administration Guide and Content Server Release Notes Decide whether to create the Setting up theinstallation owner repository owner account and account, page 33, and consult database storage areas manually or the database administrator. allow the installer to create them. Create any necessary accounts and Setting up user accounts, page groups on the operating system and 33 in the database On UNIX and Linux, create my Setting up the services file page required services file entries. 36 On UNIX and Linu: optionally Preparing UNDX and Linux createtheinstalation directory. hosts, page 35 (On UNIX and Linux, obtain the root root password password. 2 EMC Documentum Content Server Version 65, SP2 Installation GuidePrepatng the Host for Content Server Installation Task Resource Value ‘On Windows, detamine the This domain is the default domainname Windows domain where users are domain if users do not specify authenticated. aWindows domain when they connect. Choose the domain with thelargest number of users. Determine the port numbers to “The default connection broker. port number be used by the repository and portis 1489. If you are using connection broker the default port number, ensure that thened port number (1490) Port number: is available for use because the. | ——__—. connection broker requires that two ports be reserved Setting up the services file page 36 provides information on port numbers under UNIX. Determine the hostname where the hostname connection broker will run. Hardware and network environment requirements A Content Server installation has the following hardware and network requirements ‘+ Thehost for Content Server must meet the hardware and operating system requirements listed in the Content Server Release Notes. Depending on which Content Server model you are installing requirements forhardware, disk space software, and other environment and system requirements might vary. TheEnvirouneut ‘aud System Requirements section of the Content Server Release Notes contains the detailed Content Server installation environment and system requirements. ‘+ Thehost’s name must use only ASCII characters. ‘+ Ifyou are installing on ahost that uses multiplenetwork cards, by default Content Server binds to the first network card, EMC Documentum Contant Server Version 65, SP2 Intalation Guide aPreparing the Host for Content Server Installation Internationalization settings Content Server nuns in the UTF-$ 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 1S0-8859_1, the host locale would typically be set to aEuropean language English, French, Gaman, Italian, Portuguese, or Spanish). If the host localeis set to French, acient that connects to the Content Server without specifying a dient localeis served French data dictionary labels. If the host locale is one of the languages supported by EMC Documentum, the data dictionary information for that localeis 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 dictionaryini file. Installing additional data dictionary information can affect server performance, and EMC Documentum only supports the languages that are shipped with Content Server. The Content Server Administration Guide provides information on leading additional data dictionary information, — On Windows hosts, the host localeis set in the Regional Settings dialog box. — On UNDX and Linux hosts, the host localeis set with the LANG environment variable Database code page, page 4d contains information about setting the database code page. Content Server Fundamentals provides complete information on Content Server intemationalization. Server host code page Content Server may be installed on computers that run the following operating system code pages + ForU-S. and Westem European sites, 150-8859_1 (Latin-1) + ForKorem sites, EUCKR + For Japanese sites that use UNDX EUCIP + For Japanese sites that use Windows, Shift_IS + For Chinese sites with locale 2h, ms936 + For Russian with locale mu, Windows-1251 Firewalls All the server-side components of Content Server, such as index server, index agent, and Documentum Administrator, must be behind afirewall. Only the client side applications, such as Webtop are supported outside the firewall 2 EMC Documentum Content Server Version 65, SP2 Installation GuidePrepatng the Host for Content Server Installation Setting up user accounts Before installing Content Server, you need to create operating system user accounts for the users involved in managing and using Content Server and its repository. Set up the user account for the installation owner and provide the account with the rights necessary to install Content Server. In most cases, you also need to create operating system user accounts for the repository owner (corresponding to the database user account that Content Server uses to connect to the repository database) and for end users who access the repository. The following sections describe the user roles and the rights they need to have. Setting up the installation owner account ‘The installation owner account is used to install Content Server and create arepository. The installation owner must have an operating system account with appropriate permissions, as described in Required rights for an installation owner account, page 33. Content Server runs under the installation owner's account. The installation owner can perform all administrative or maintenance tasks associated with the installation or the repository. ‘The installation owner account may be alocal account on the Content Server host or a domain. account in the domain where Content Server is installed. The account must be amember of the local host's Administrators group. However, the installation owner account must of be the same account as the Windows Administrator. On UNIX or Linux, do not use the root account as the installation owner account. ‘You can create an operating system account to use exclusively for Content Server installation and repository maintenance. You can use a single operating system account as installation owner for multiple Content Server installations on the network Installation owner account naming requirements ‘The installation owner's usemame must consist of letters, numbers, dashes (-) or underscores (_). The first character must be aletter. All characters must be ASCII characters. ‘The installation owner's password must consist of letters, numbers, dashes, underscores, or periods. Note: On Windows hosts, user accounts are not case-sensitive, but Content Server installation fails if you connect to the host by using the mcorrect casein the usemame. For example, if the account is set up as JPSmith and you connect as jpsmith, you can log in to the host, but Content Server installation fails Required rights for an installation owner account ‘The installation owner must have the following user rights + Act as part of the operating system © Create atoken object EMC Documentum Contant Server Version 65, SP2 Intalation Guide 2Preparing the Host for Content Server Installation + Increase quotas + Login as aservice + Login locally + Replace aprocesslevel token. On astandard Windows system, these rights are automatically inherited with membership in the local Administrators group. The Setup program checks for theserights and grants themif necessary. ‘The installation owner must have Full Control permission on the directory into which Content Servers being installed. The installation owner must also have write permission on the directory, from which the installation program is run, On UNIX or Linux hosts, the installation owner must haveread, wnite, and execute permission on the /tmp directory. ‘The installation owner must have an email account on the SMTP mail server. To support extemal password validation, set up a group account whose members are the installation owner, any other Content Server administrators, and repository owners. This will be the group that owns the extemal password validation program. (On UNIX and Linuchosts, set several environment variables in the installation owner's environment. ‘The Content Server configuration script sets the required variables by default. If you do not use the Content Server configuration saipt, you need to manually set the environment variables discussed in Appendix A, Required Environment Variables for UND and Linux. The installation owner in SQL Server repositories If SQL Servers installed in a different domain from Content Server, the EMC Documentum, installation owner must be a valid user in the remote domain. Setting up the repository owner account ‘Therepository owner operating system account is used to connect to the database. The repository owner owns all objects in the database. Each repository must have a unique repository owner. To create anew repository you need arepository owner account. If you want to use the option to use an existing database account when you are creating anew repository, you must have a database user account established already. (On Windows hosts, set up a Windows account for the repository owner. For installations that use DB2 databases, the repository owner must be a valid Windows user on the host where the database isinstalled. To use Microsoft Cluster Services, the repository owner must have an account in the domain in which you install the repository. Repository owner account naming requirements ‘Therepository owner's usemame must consist of letters, numbers, dashes (-) or underscores (_). The first character must be aletter. All characters must be ASCII characters. 34 EMC Documentum Content Server Version 65, SP2 Installation GuidePrepatng the Host for Content Server Installation ‘Therepository owner's password must consist of letters, numbers, dashes, underscores, or periods Setting up repository user accounts Repository users are the end usersin therepository. These users may own documents or other objects that are stored in arepository, but they have no particular responsibilities for the maintenance of either the repository or the installation. On Windows, ifthe default user authentication is used, each user must have a Windows account in the domain where Content Server is installed. If LDAP authentication or inline password authentication is used, this is not arequirement On UNIX and Linux, end users who want to run aprogram whose executable isin $DM_HOME/bin must have $DM_HOME/bin in their path. For example, application developers who are wniting and testing Docbasic procedures need to have $DM_HOME/bin in their paths. Preparing UNIX and Linux hosts If you are running Content Server on UNIX or Linux, create the instalation owner's account and set ‘variables in the installation owner's environment before you install. Also create two group accounts whose member areinstallation owner and ensure that the shared C library is available ‘This section covers these topics, which include requirements in addition to configuring the installation owner's environment correctly. Shared memory and semaphore requirements Content Server's shared memory and semaphore requirements are ‘© Configure the host with at least two megabytes of shared memory for Content Server. + Content Server uses asemaphore Ensure that semaphores are enabled on the host. XWindows requirement Windows must be installed on the UNDX host to run the graphical installation program, and the xterm program must be in the installation owner's 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 ADX, fust/binyX11 ‘Verify that the xterm program is in one of the preceding paths or in an altemate location and add that location to the PATH variable EMC Documentum Contant Server Version 65, SP2 Intalation Guide 38