Enough of theory, right? Let us now get geared up for a plunge into the Documentum ocean!
The assumption here is that you have understood the need for a WCM system, have analyzed your business needs well, and are enthusiastic to haul out the most from the Documentum WCM product suite.
Make sure that you have procured the adequate licenses from Documentum before we begin our journey. Download the correct versions of the various Documentum products from Documentum's download site:
https://documentum.subscribenet.com
Remember that you will need to enter a valid login and password before you get access to the software installables.
Once you have downloaded the executables from the Documentum site, the most important question you face is where to start from. The other critical aspects that come to mind are: what is the correct installation sequence, any pre-requisites, things to be aware of, and so on and so forth.
Sit back and relax—quite a bit of homework has been done for you. Figure 5.1 is a chart you can follow for installation sequence. This should not be treated as the best possible Documentum installation sequence, but in most projects it will work out well.
Figure 5.1: Documentum Installation sequence
We will be installing Content Server 5.2.5 SQL Server for Windows (base install) and then updating it with the SP2 (service pack 2) patch.
It is strongly recommended that you go through the complete Release Notes and Installation manuals for the Documentum software in question. What has been mentioned in the book is just the checklist that one should follow and what one needs to be specifically cognizant of.
To begin, download the following Content Server software installers from the Documentum site:
Content_Server_5.2.5_windows_sql.exeContent_Server_5.2.5_SP2_windows_sql.exe
Please note that throughout the book we will be referring to the Documentum product versions 5.2.5 SP2 on a Windows environment with SQL Server DB, IIS Web server, and Tomcat application server. The installation steps and configurations will pertain to the specific product version 5.2.5 SP2 only. For an upgrade path or for knowing more about the latest Documentum suite versions, please get in touch with your local support for Documentum.
Note
There can be only one Content Server installation on a Windows host. Do not attempt to install two content servers on the same Windows machine. However, this is possible in the case of a UNIX or Linux environment. Moreover, on UNIX and Linux systems, multiple installations can be created on a single host, including installations of different versions of the Server. For example, both 5.2 and 5.3 installations can exist on a single UNIX host!
Once Content Server has been installed, multiple Docbases can be created for the Content Server in question.
Figure 5.2 mentions some of the prerequisites for starting the installation of Content Server:
|
Entity |
Comments |
|---|---|
|
Database |
Should be available either locally or remotely and should be setup correctly. Code page should be set in accordance with Content Server's UTF-8 code page. For SQL Server you can use any collation (i.e. code page) Case-sensitive SQL Server should be installed with row-level locking. SQL Server client should be installed on the Content Server machine irrespective of whether DB is local or remote. Docbase owner (i.e. the Database user) is the account used to connect to underlying RDBMS. This should be available. |
|
SMTP Server |
SMTP server should be available on the network or be present on the Windows 2000 machine. |
|
Network |
Properly set up TCP/IP network should be available. |
|
Environment Variables |
Set the PATH system variable to point to 'Java' |
|
Installation Owner |
The user who installs Content Server software should have a valid OS account. Limitations for installation owner's user name: Consists of numbers, letters, hyphens (-) and underscores (_). The first character should be a letter. All characters must be ASCII. If SQL Server DB is installed in a different domain from Content Server, the installation owner should be a valid user in the remote domain. |
|
Hardware |
700 MB hard disk space, 512 MB RAM, and minimum 400 MHz CPU. |
|
Java Runtime Environment |
Sun JRE 1.3.1, 1.4.1 (and IBM J2RE 1.3.1 for AIX OS) |
|
Others |
For supported combinations of Windows OS, RDBMS versions and JRE, please refer to Release Notes from Documentum. |
Note
Do not use spaces in the name of the installation directory for Documentum. For example, do not install under C:Documentum Installation.
No further delays! Let us kick-off the installation of Content Server 5.2.5 and then subsequently install the SP2 patch over it.