1. If you are not in the Content Server configuration program, from $DM_HOME\install, run Server_Configuration_Program.exe(Windows) or dm_launch_server_config_
program.sh(UNIX and Linux) to launch the configuration program.
2. In the configuration options screen, choose Repository and click Next.
3. Type the installation owner password and click Next.
4. Choose Add a new repository and click Next.
5. Specify a Data directory path for storing content files and indicate whether it resides on a SAN or NAS device.
The data directory must not be a top-level directory on a SAN or NAS device such as
\\x.x.x.xwhere x.x.x.x is the IP address. For SAN or NAS, enter the complete path including a shared device. Here is an example of a valid data directory on a SAN or NAS device:
\\x.x.x.x\folder1\folder2.
The default data directory is $DOCUMENTUM/data.
Click Next.
6. Specify a share directory for storing client applications, code examples, and libraries.
The share directory can be on the Content Server host or on another host that Content Server can access over the network.
If you specified a data directory that resides on a SAN or NAS device in the previous step, the share directory is automatically created as a sibling on the same level as the data directory. For example, if the data directory is \\x.x.x.x\Documentum\data where x.x.x.x is the IP address, the following share directory is automatically created: \\x.x.x.x\Documentum\share.
The default share directory is $DOCUMENTUM/share.
Click Next.
7. Type the fully qualified domain name (FQDN) of the Content Server host computer and click Next.
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 consist of letter, numbers, or underscores (_). The first character must be a letter. All letters and numbers in the name must be ASCII characters. Do not include spaces or non-alphanumeric characters. The repository name docu is reserved by the system.
• Repository ID: Valid repository IDs are shipped with the Content Server software. You can also specify your own repository IDs. The repository ID can be any number from 1 to 16777215 and must not start with a zero (0). Each repository ID must be unique on the network. You can request for additional repository IDs from the EMC support web site (http://support.emc.com) to ensure that each of your repository IDs is unique.
• Description: Optionally, type a brief description of the repository.
• Authentication domain: The default domain if the user does not specify a Windows domain when connecting to the repository. Choose the domain with the largest number of users. The configuration program automatically fills in this information.
• Service startup type: On Windows, specify whether the repository service starts automatically at 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.
• Use certificates: Select if you want to enable SSL certificates.
If Use certificates is selected, provide the DFC trust store information:
• TrustStore: The location of the DFC trust store. For example,
$DOCUMENTUM\dba\secure\dfc.keystore
• Password: The password of the trust store file.
Select Use Default Java TrustStore if you want to use the default DFC Java trust store.
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 and the repository do not use TLS/SSL authentication to authenticate each other. However, the information exchanged between the client and the repository is encrypted.
• Native and Secure: The repository accepts both native and secure connection requests.
If you choose Secure or Native and Secure as the connection mode, the Use certificates option will be visible.
Select Use certificates if you want to enable SSL certificates.
If selected, provide the following information:
• Keystore file name: The name of the keystore file in the PKCS#12 format.
• Keystore password file name: The password of the keystore file.
• Cipher list
Provide the DFC trust store information:
• TrustStore: The location of the DFC trust store. For example,
$DOCUMENTUM\dba\secure\dfc.keystore
• Password: The password of the trust store file.
Select Use Default Java TrustStore if you want to use the default DFC Java trust store.
Click Next.
11. Configure your relational database management system (RDBMS).
a. Choose whether to create a new database and a repository owner (database user with the database 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 account has privileges to create and delete databases and perform other database administrative tasks.
• Database name: The name of the database Content Server uses to store content metadata as well as system and repository information.
• Repository Owner Account Name and Password: The database user account with the database owner role that has read and write access rights to the database.
Click Next.
c. Configure the data file or data devices information: The configuration program automatically fills in the information for Data device file path and Log device file path.
Click Next.
12. (Only for Windows) 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 will use 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 is displayed, 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 current repository. Do not use the installation owner or the repository owner credentials.
Client applications and other repositories will use this login name and password to connect to the global registry. Record the credentials so that you can provide this information when installing other Documentum products that require global registry access.
• No: The Specify whether to use another repository screen is displayed.
— Yes: Designates an existing repository as the global registry.
Type the information about the repository you want to use as the global registry:
Connection Broker Host and Port
Select Use certificates if you want to enable SSL certificates.
The current repository will be configured to access the remote global registry.
Note: You can change the global registry designation and edit connection information after installation through Documentum Administrator or the dfc.properties file. The EMC Documentum Content Server Administration and Configuration Guide contains the instructions on enabling a repository as a global registry.
— No: The global registry is not configured. You can manually add the global registry through Documentum Administrator or the dfc.properties file.
14. Choose the modules you want to activate for the repository.
If you chose XML Store module, specify the following:
• XML Store deployment mode to enable XML Store.
• Set the xDB superuser password.
• Provide the XML Store port and directory location.
Click Next.
15. Review the summary information and click Next.
16. Choose to perform additional configurations or finish configuration.
Note: Always click Finish to exit the Content Server configuration program; otherwise, you will have to manually start the application server services.