CONTENTS

S.No Topic Page

No :
1 Checking system requirements 1
2 Installation model 2
3 Configurations on SQL Server host 2
4 Configurations on Content Server host 45
5 Validating installation 113
6 Post installation tasks 115

Present guide covers installation of SQL Server 2012 Express

edition and Content Server7.1 on Windows Server
2012/Windows Server 2008
For any optional requirements and steps mentioned in the
guide, refer to the Documentum installation guide at the EMC
website.

Checking system requirements

As per system and requirements guide of Documentum 7.1, the Hardware
requirements are
RAM 8GB
Disk Space 40 GB
 and
Database requirements are
Operating System/Database SQL Server 2012 SP1
Engine
Windows Server 2012 R2 compatible
SP1x64 Edition/x64
Windows Server 2008 R2 SP1 compatible
x64 Edition/x64

For specific OS and Database Engine requirements, please refer the Content
Server<version> system and requirements guide

INSTALLATION MODEL
Present installation guide follows basic model wherein
 Content Server and
 RDBMS
are installed on the same machine which is typically used in development and test
environments. In production environment, Content Server and RDBMS are almost
always installed on different machines for performance reasons.

Configurations on the SQL Server host

RDBMS REQUIREMENTS
(i)create a case –sensitive instance.
(ii) Install SQL Server in mixed or SQL Server authentication mode (preferred
modes).
(iii)Dictionary Order should be set to sort.
 The above requirements will be met at their respective places in installation
wizard
1. Download SQL Server from Microsoft website
http://www.microsoft.com/betaexperience/pd/SQLEXPCTAV2/enus/default.aspx

Or
 https://www.microsoft.com/en-in/download/details.aspx?id=29062

2. Run the installation wizard

Note:If SQL Server host has Windows Server 2012 OS, a .NET Framework error is
expected amidst installation. Before launching the wizard you are advised to
follow the resolution steps on page:21

o Extract files
o Select New SQL Server stand-alone installation or add features to an existing
installation
o You can skip the updates and ignore the error that commonly occurs due to
Internet security restrictions
o Click Next.
o Warnings can be skipped ,any errors listed should be resolved
o Accept license terms
o Click Next.
o Either select all or specific features required
o Instance configuration: Generally you can choose the defaultinstance. Named
instances would be used if you want to create multiple instances of SQL Server
o Review the disk requirements and click next when prompted

o Server Configuration
 Service Accounts tab

SQL Server Database Engine is needed to run SQL Server. Ensure that its startup
type is set to automatic because Content Server installation sometimes requires a
restart of the computer. After the restart, installation does not proceed correctly
unless the database starts automatically.
SQL Server browser service can be set to manual so that it will not use up a lot of
system recourses when you are not using the SQL Server.

 Collation tab
We will configure the requirements (i) and (iii) of RDBMS in this step.
Click on Customize button to select other than the default collation value
 We choose a value for SQL collation which has CS as suffix forcreating Case-
Sensitive instance and as described in the Collation description the sort order
code is 31 which stand for dictionary order

o Database Engine Configuration

Select mixed authentication mode and create an sa account

Leave all other values as default

o Click on next and then install
Note: if Operating System on which SQL Server is installed is Windows Server
2012, you will across the below .NET Framework error
Error while enabling Windows feature: NetFx3
 Clicking on OK and skipping the error though will lead to partial feature
installation

(#1) .NET FRAMEWORK ERROR

About the error and its resolution

 The standard install of Windows 2012 does not even install binaries
required to enable this feature. If you want to enable it, you will need side-
by-side assembly source, usually the CD drive which has Windows Server
2012 installation media.
 In absence of installation media(which is most common case) follow these steps
I. Make sure that you are able to connect to the MSDN updates website, on a
VM it might require a person with Administrative privileges to configure some
Internet Security options
Link:http://www.update.microsoft.com/windowsupdate/v6/thanks.aspx?ln=en&
&thankspage=5

II. Configure group policy settings.

o Open run menu and type gpedit.msc , press enter
o Select Computer Configuration
o Administrative templates node
o Therein expand Select System node
 o Select specify settings for optional component installation and component
repair

 Enablespecify settings for optional component installation and component

repair
 Check Contact Windows Update directly to download repair content instead of
Windows Server Update Service(WSUS)
This step allows the server manager’s Add Roles and Features wizard to contact
the msdn update website directly to fetch required binaries to enable netfx
framework in absence of Windows Server 2012 installation media.
 Uncheck Never attempt to download payload from Windows Update
 Click on Apply
I. Add netfx3.5 feature
o Go to Server Manager
o Add Roles and Features
o Click Next
o Click Next
o Skip Roles
o Select .NET Framework 3.5 Features
o Click on install

o Close the wizard after installation

 In presence of installation media

METHOD 1:
Through Server Manager
o Go to Server Manager
o Add Roles and Features
o Click next
o Click Next
o Skip roles
o Select .NETFramework 3.5 feature
o Click on next and select specify an alternate path
o Specify path of installation media
o Click on install
 o Close the wizard

METHOD 2
Through CMD

o from the command prompt using the following command:

dism /online /enable-feature /featurename:NetFx3 /source:d:\sources\sxs

Configurations on Content Server host

If Content Server and SQL Server are installed on the same machine skip steps 1
and 2 and proceed to step 3

1. Install SQL Server native client

o download SQL Server native client from Microsoft website
https://www.microsoft.com/en-us/download/details.aspx?id=43339

o run the installer

o click next
o accept terms and conditions

o select features
o click next

o finish installation
2. Install SQL Server Management Studio
If the Operating System is Windows Server 2012 , perform the steps for
resolving .netfx3 not enabled error elaborated on page no. 20 before going
ahead with installation
o Download from Microsoft website
https://www.microsoft.com/en-in/download/details.aspx?id=29062
o Run the installer
o Skip product updates
o Install setup files
o Accept license terms
o Select feature
o Click on next
o Click on next
o On Windows Server 2012 the .NETFramework error (#1) will occur. Troubleshoot
it by following resolution steps on page no: 21; click on install.
 3. Set uprequired user accounts
o Installation owner account

The installation owner accountis an operating system account with appropriate

permissions to installContent Server and create repositories. The installation
owner account may be a local account onthe Content Server host or a domain
account in the domain where Content Server is installed. Theaccount must be a
member of the Administrators group on the local host.You can use a single
operating system account as installation owner formultiple Content Server
installations on the network
If the machine itself is logged into with Administrator
credentials , a separate installation account may not be
required
(Optional)Email account of installation owner and SMTP server
IP are required at the time of installation or upgrade by
Content Server to send mail notifications. An Email account
 can be set up and IP of computer hosting SMTP server can be
provided .

o Repository owner account

The repository owner account is a database user account that Content Server uses
to connect to thedatabase. This account owns all objects in the database and
gives Content Server access to thedatabase tables underlying the repository. Each
repository must have a unique repository owner.
You can create the repository owner (database user) account in one of these two
ways
Have Content Server automatically create the repository owner
account in the database when youcreate the repository during the
installation process.(As followed in the present guide)
Manually create the repository owner account in the database prior
to installing Content Server(refer tothe documentum install guide )

o Repository user accounts

Repository users are the end users in the repository. One or more such accounts
can be created after installing clients such as DA , D2.

4. Pre-installation steps
 Set the date and time formats to a four-digit year (yyyy) date in the
Windows regional settings
 Disable the user access control (UAC).
 Disable the Windows Update service.
 Enable the Computer Browser service (optional).
 Disable the IP Helper service from the Windows Services console and
restart the machine.
 In non-English operating systems, install the latest version of
Microsoft Visual C++ 2008Redistributable (64-bit) before creating a
repository. This will provide the correct operatingsystem runtime
libraries for the Content Server and other utilities.
 Setting up the services file
The services file must contain two entries for each repository running
on a host. Manually create theservice name entries in the services
file before you install the Content Server.
Path to service file C:\Windows\System32\drivers\etc
example
dm_repo1 1489/tcp #sql server network service
dm_repo1_s 1490/tcp #secure sever network service
 Note 1: Even if you are not using secure (SSL) connections, two
consecutive port numbers are stillrequired by Content Server.
If correct services file entries are not present during installation, the
installation will fail.
If you have multiple repositories on a single host, create a services
file entry for each repository.Ensure that the repositories use
different names and port numbers.
Note 2: If this host file is not edited properly, then during repository
creation you may encounter a Database home directory not found
issue

5. Prepare Microsoft SQL Server

Creating an ODBC data source for SQL Server
o From the Windows Start menu, select Administrative Tools > Data Sources
(ODBC).

Note: Ensure that you select a 64-bit ODBC data source.

o In ODBC Data Source Administrator, navigate to the System DSN tab and
click Add.
o In the Create New Data Source window, double-click SQL Server because
you have to connect to the SQL Server

o In the Create a New Data Source to SQL Server window, enter a name for
the data source andselect the SQL Server you want to connect to.

o Click Next.
 o Choose a SQL Server authentication method
if while installing SQL Server , you had selected SQL Server authentication
mode, check the same mode here and provide the sa account credentials
that you created then

You can either leave all other values as default or configure them as per
requirements and proceed next.
o Click on Finish and test the data source

Note:click on OK button on each dialog box and after exiting the data
source creation wizard open the System DSN tab again to verify that the
created data source exists there. If the data source is configured properly in
this step then during the repository creation, the installer will automatically
configure the data source name.

6. If the Content Server and SQL Server are on different machines, it is

necessary for Content Server host machine to be able to connect to the SQL
Server on other machine.
Perform the following steps if both servers are on same host as well .
o Open Management Studio
o Click on the connect button
o If during SQL Server installation, the selected authentication mode is SQL
Server Authentication mode, select the same here and provide the
password for sa account, created then.
 o Click on connect

o Perform the same connection steps on the SQL Server host also.

(#2) Connection errors (10061 , 121 , etc)

while trying the above connection 1 or more connection errors might occur , in
such case , try the following resolves

 Execute ping command to ascertain that the two hosts are connected on
the domain
ping <IP>
 Go to the SQL Server host ->Management Studio -> Rightclick on Server
Name on the left pane ->Properties->Connections and make sure that
theoption “allow connection with remote computers”ischecked.
 On Content Server host go to SQLserver Configuration Manager ->click on
“SQL Server Services” in the left pane. In the center pane, is a column that
lists the Process ID for each running service. Look for the PID in the row for
SQL Server.
Identify the port that the PID is listening on by typing into a command
prompt:

Netstat –ano | find /I “PID-Number-Of-SQL-Server”

If there is no result (as above) from the command, it implies that the TCP/IP
protocol is not enabled.
 Click on SQL Server Network Configuration in the left pane and right-click
TCP/IP protocol and select option Enable.

 Go to control panel on both the machines and make sure that UAC is
turned off.
 The system has to be restarted whenever prompted for the changes to take
effect
7. (Optional) Based on requirement you can also
o Configure Internationalization settings
o Prepare for Remote Key Management
refer to EMC documentum Installation Guide
8. Before getting started , pick the required version , for required Operating
System from EMC website :
https://emc.flexnetoperations.com/control/dctm/login?nextURL=%2F
control%2Fdctm%2Findex
The Content Server installation is broken down into two main processes

1) Run Content Server installer to copy Content Server program files from the
installation media into appropriate directories
2) Create Connection broker and repository

INSTALLING CONTENT SERVER BINARIES

1. Log on to the computer where you want to install Content Server as the
installation owner.
2. Run serverSetup.exeto launch Content Server Installer.
 3. Accept the license agreement and click Next.

3. Specify an installationdirectory for Content Server.

The installation directory name must not contain spaces. For example, do not use
c:\Documentum Products as the name of the installation directory.
On Windows, the default installation directory is C:\Documentum.
Click Next

5. On Windows, type the installation owner password.

Click Next

6. Set the administrator password and specify an available listening port for the
embedded application server used by Content Server:
• Admin User Password: The password must not have the ", ’, <, >, %, |, ^, &, ( ,
and ) characters.
The application server administrator username is set to admin by default.
• Listen Port: The port on which the application server listens for standard
administrationconnections. A total of 20 ports, starting from the one you specify,
will be used by theapplication server, and all of them must be available. The
default port number is 9080. Whether you accept the default port or choose
another one, do not change this port afterthe initial configuration.
Click Next.
7. Review the installation summary and click Install to begin installation.

8. Specify if you want to enter license keys for optional modules of Content
Server and click Next.
• Yes: In the next screen, select the optional modules you want to install and
entercorresponding license keys.
• No: You can always enter license keys for optional modules later using the
Content Serverconfiguration program.
9. Installer prompts you if you want to configure Content Server now.
• Configure now: Configure now and have the installer launch the configuration
program.If you choose this option, you will not be prompted to choose the
connection modes (Native, Secure, and Native and Secure). The configuration
program automatically creates aconnection broker in Native mode using the
default ports (1489 and 1490) and you proceed to create a repository.
Note: Ensure the default ports are available.
• Configure later: Configure later and exit the installer. You then manually launch
theconfiguration program to resume the installation process. If you choose this
option, you will be prompted to choose the connection modes (Native, Secure,
and Native and Secure). You must create a connection broker first in the
configurationprogram before creating a repository.
CREATING CONNECTION BROKER AND REPOSITORY
a) Connection Broker
Skip these steps if you chose Configure now in the installer, in which case
the installer automaticallylaunches the configuration program and creates a
connection broker for you using the default ports(1489 and 1490).
Follow these steps if you chose Configure later in the installer:
1. From $DM_HOME\install, run Server_Configuration_Program.exe to launch
the Content Server configuration program.
2. In the configuration options screen, choose Connection brokerand click Next.
3. Type the installation owner password and click Next.
4. Choose Add a connection brokerand click Next

5. Choose a connection mode in which the client will connect to the

connection broker:
• Native: Content Server listens for client connection requests only on
standard native ports.Content Server refuses requests for a secure
connection.
• Secure: Content Server listens for client connection requests only on a
secure TLS/SSL(Transport Layer Security/Secure Sockets Layer) port for
encryption. The client andContent Server do not use TLS/SSL authentication
to authenticate each other. However, theinformation exchanged between
the client and Content Server is encrypted. Content Serverrefuses
connection requests other than TLS/SSL connections.
• Native and Secure: Content Server accepts both native and secure
connection requests.
Click Next.

6.(Optional) Select Use certificatesif you want to enable SSL certificates.

Refer to documentum installation guide
7. Provide the connection broker information:
• Connection broker name: A unique name for the connection broker.
• Connection broker port: The port you specify and its subsequent port will
be used by theconnection broker and both must be available. The default
port is 1489. If you accept thedefault port, make sure that the next port
1490 is also available.
• Service startup type: On Windows, specify whether the connection
broker service startsautomatically at startup or is started manually.
8. Review the summary information and click Next.
9. When the connection broker setup is complete, choose to perform
additional configurations orfinish configuration
b) Creating Repository

1. If you are not in the Content Server configuration program, from

$DM_HOME\install, run Server_Configuration_Program.
2. In the configuration options screen, choose Repositoryand click Next.
3. Type the installation owner password and click Next.
 4. Choose Add a new repositoryand click Next.

5. Specify a Data directory pathfor storing content files and indicate whether it
resides on a SAN or NAS device.(refer to documentum installation guide)
The default data directory is $DOCUMENTUM/data.
Click Next.

6. Specify a share directory for storing client applications, code examples, and
libraries.
(Optional)The share directory can be on the Content Server host or on another
host that Content Servercan access over the network. Refer to documentum
installation guide.
The default share directory is $DOCUMENTUM/share.
Click Next.

7. Type the fully qualified domain name (FQDN) of the Content Server host
computer and clickNext.
(A fully qualified domain name specifies its exact location in the tree hierarchy of
the Domain Name System (DNS). For example, given a device with a local
hostname myhost and a parent domain name example.com, the fully qualified
domain name is myhost.example.com.)

8. Provide the following information for the repository:

• Repository name: The name for a repository can have up to 32 characters, and
must consistof letter, numbers, or underscores (_). The first character must be a
letter. All letters andnumbers in the name must be ASCII characters. Do not
include spaces or non-alphanumericcharacters. The repository name docu is
reserved by the system.
• Repository ID: Valid repository IDs are shipped with the Content Server
software. Youcan also specify your own repository IDs. The repository ID can be
any number from 1 to16777215 and must not start with a zero (0). Each
repository ID must be unique on thenetwork.
• Description: Optionally, type a brief description of the repository.
• Authentication domain: The default domain if the user does not specify a
Windows domainwhen connecting to the repository. Choose the domain with the
largest number of users. Theconfiguration program automatically fills in this
information.
• Service startup type: On Windows, specify whether the repository service starts
automaticallyat startup or is started manually.Click Next.

9. Provide the connection broker information and specify if you want to enable
SSL certificates:
• Connection Broker Port: Type the connection broker port number.
• Connection Broker Host: Type the host name.
•(Optional)Use certificates: Select if you want to enable SSL certificates. Refer to
documentum installation guide
Click Next.

10. Choose a connection mode for the repository:

• Native: The client connects to the repository through a non-TLS/SSL port.
• Secure: The client connects to the repository through a secure TLS/SSL port. The
client andthe repository do not use TLS/SSL authentication to authenticate each
other. However, theinformation exchanged between the client and the repository
is encrypted.
• Native and Secure: The repository accepts both native and secure connection
requests.
(Optional)If you choose Secure or Native and Secure as the connection mode, the
Use certificates optionwill be visible. Refer to documentum installation guide
Click Next.

11. Configure your relational database management system (RDBMS).

a. Select whether to create a new database and a repository owner (database
user with thedatabase owner role) or use existing ones.

b. Type or review the following information:

• Data source name: The ODBC data source used to connect to the database
server.
• Administrator name and Administrator password: The database administrator
accounthas privileges to create and delete databases and perform other database
administrativetasks.
• Database name: The name of the database Content Server uses to store
content metadataas well as system and repository information.
• Repository Owner Account Name and Password: The database user account
with thedatabase owner role that has read and write access rights to the
database.
Click Next.

Note : the name of Data Source should be automatically configured by installer if

the System DSN is created properly. If there is a problem in populating Data
Source , check the Creating an ODBC data source for SQL Server module on page
no : 63
c. Configure the data file or data devices information: The configuration program
automaticallyfills in the information for Data device file pathand Log device file
path.
Click Next.

12.Provide the SMTP information:

• SMTP server name: The name of the SMTP server or the IP address.
• Owner’s email address: The installation owner’s email address that Content
Server willuse for email notifications.

This is a required field.

If a valid SMTP server host name is not available, enter an invalid one.
If the configuration program fails to connect to the SMTP server you provide, a
warning isdisplayed, but you can still proceed with the installation.

You can modify the SMTP server host name after installation.
Click Next.
13. Specify if you want to use the repository you just created as a global registry
or to use another one:
• Yes: Designates the repository just created as the global registry.
Type the Login name and Password information for the global registry user in the
currentrepository
• No: The Specify whether to use another repository screen is displayed. Refer to
documentum installation guide pg. 58

14. (Optional) Choose the modules you want to activate for the repository.
Click Next.
15. Review the summary information and click Next.
16. Choose to perform additional configurations or finish configuration.

VALIDATING INSTALLATION
o ReviewContent Server installation and configuration logs
Content Server Installer and configuration program both create log files.
The log files are mostly storedin on the installation owner’s desktop.
 Check for any errors or exceptions.
o Open Documentum Server Manager

o Review Repository and DocBroker logs

 Start the services in following order
DocBroker -> Repository
 Stop the services in following order
Repository -> DocBroker

DOCBROKER LOG
In the docbroker tab , go to view log
  Each time DocBroker is started , an entry stating : “Docbroker has
started . Process id : xxxx" is created with a different process id . No
entry is created which explicitly states that docbroker service is
stopped

REPOSITORY LOG
In the Repository tab , go to view log
 There should be no errors in the log

POST INSTALLATION TASKS

For performing optional, as required post installation tasks, refer to Documentum
Installation Guide.