Documentum Content Server 5.2.5 SP2 Installation

Content Server Installation Guide
Version 5.2.5 SP2

July 2004
All Platforms
Copyright 1994-2004 Documentum, a division of EMC. All Rights Reserved.

DOCUMENTUM, NOW YOU KNOW, UNITING THE WORLD THROUGH CONTENT and the Corporate Logo are trademarks or registered trademarks of
Documentum, a division of EMC, in the United States and throughout the world. All other company and product names are used for identification purposes
only and may be trademarks of their respective owners.
Table of Contents
Preface
Chapter 1
Chapter 2
Chapter 3
...........................................................................................................................
Planning for Installation .........................................................................

About Installation .......................................................................................
Effects of Installation ..............................................................................
Operating Systems and Databases ..............................................................

Upgrade Paths to Windows Server 2003 Operating System ........................
8
8
Configuration Decisions ..............................................................................
Making Backups .........................................................................................
Upgrading DocBrokers ...............................................................................
Upgrading Content Server ......................................................................

Before You Upgrade ....................................................................................
Upgrading Distributed Configurations ....................................................
11
Upgrading the Server Software Installation on the Host ................................
11
Upgrading the DocBroker, the Server and the Docbase ..................................
13
Postinstallation Tasks .............................................................................

WDK Applications .....................................................................................
17
Setting the i_retain_until Attribute ...............................................................
17
Running Scripts Manually ...........................................................................

Apply Formats Script ..............................................................................
Docbase Tools Script ...............................................................................
Content Services for EMC Centera Script..................................................
Templates Script .....................................................................................
DFC Support Script ................................................................................
Content Intelligence Services Schema Installation Script ............................
Email Templates Components Script ........................................................
Display Configuration Setup Script ..........................................................
Data Dictionary Script.............................................................................
17
17
18
18
18
19
19
19
19
19
Chapter 4
Setting the i_retain_until Attribute
Chapter 5
Uninstalling Content Server
7
7
11
11
17
......................................................... 21
................................................................... 27
Table of Contents
List of Tables
Table 41.
UPDATE_RETAIN_UNTIL_DATE Arguments .................................................
24
Preface
Purpose of the Manual
This manual contains information and instructions you need to upgrade Documentum
Content Server on any platform from version 5.2.5 or 5.2.5 SP1 to version 5.2.5 SP2. It
describes requirements that must be met before you upgrade the server. It also provides
step-by-step instructions for upgrading.
Intended Audience
This manual is intended for the person upgrading Content Server from version 5.2.5 or
5.2.5 SP1 to 5.2.5 SP2. Typically, a system administrator upgrades the software.
Revision History
The following revisions have been made to this document:
Revision History
Date
Description
July 2004
First published
Related Documentation
You can find additional information about Content Server in the following manuals:
Content Server Fundamentals contains information on Docbases, DQL (Document

Query Language), objects and types, documents, virtual documents, and other
features of the Documentum system.
Content Server Administrators Guide contains information on configuring a

Documentum installation, managing Content Server, DocBrokers, full-text indexes,
Docbase security and many other subjects.
Documentum Distributed Configuration Guide contains information on implementing

and managing single- and multi-Docbase distributed configurations, object
replication, content replication, Docbase federations, and the architecture of
distributed configurations.
Content Server Object Reference Manual contains reference information on objects.
Preface
Content Server API Reference Manual contains reference information on server API
methods
Content Server DQL Reference Manual contains reference information on Document

Query Language (DQL)
Documentum System Migration Guide contains information on migrating your

Documentum installation from a previous release to Documentum 5.
These manuals are available on the Documentum download site or the product
distribution CD as PDF files.
Conventions
This manual uses the following conventions:
Typographic Conventions
Convention
Description
Represents a menu.
italics
Represents a term, or a variable for which

you must provide a value.
typewriter
Represents code samples, user input, and

computer output.
[] square brackets
Indicates an optional argument in method

command-syntax specifications.
{} curly braces
Indicates an optional argument that can

be repeated in method command-syntax
specifications.
Links in Server PDF Files

Each Server book contains many clickable cross-references to the other server books.
Cross-references to manuals other than the one you are reading only work if the PDF
files are all in the same directory on your PC and are named with the file names that they
have on the release CD and Documentum FTP site.
Chapter 1
Planning for Installation
This chapter contains the following topics:
About Installation, page 7
Operating Systems and Databases , page 8
Configuration Decisions, page 8
Making Backups, page 9
Upgrading DocBrokers, page 9
About Installation
Content Server 5.2.5 Service Pack 2 (SP2) is an incremental maintenance release of
Content Server 5.2.5. SP2 can be installed only to an existing 5.2.5 or 5.2.5 SP1 server
installation. You cannot create a new server software installation from the SP2 software
distribution package.
After you install SP2, you can continue to create new Docbases and DocBrokers by
running the Server Configuration Program. Use the instructions for creating new
Docbases and DocBrokers in the Content Server Installation Guide for release 5.2.5.
You cannot revert to Content Server 5.2.5 or 5.2.5 SP1 after Service Pack 2 is installed
except by destroying the Docbases and DocBrokers and restoring from a full Docbase
backup. The backup must include the database tables for the Docbase and Content
Server host file system, including the file storage areas.
Effects of Installation
Applying SP2 to an existing 5.2.5 or 5.2.5 SP1 Docbase:
Adds attributes to existing Docbase objects
Adds new types to the Docbase
Runs configuration scripts

For more information on the scripts, refer to Running Scripts Manually, page 17.
Upgrades the DocBrokers and Docbases on the Content Server host from version
5.2.5 or 5.2.5 SP1 to version 5.2.5 SP2
Backs up the earlier version of all changed files to $DOCUMENTUM/_5.2.5.SP2_

backup (UNIX) or %DOCUMENTUM%\_5.2.5.SP2_backup (Windows)
Writes a log file entry to username.ServerSPInstaller.log for every file copied and
every file backed up and replaced
Operating Systems and Databases

Service Pack 2 is supported on the same operating systems and databases as Content
Server 5.2.5 and 5.2.5 SP1. Refer to the release notes for 5.2.5 SP2 for complete
information on supported platforms.
Upgrade Paths to Windows Server 2003 Operating

System
Content Server 5.2.5 is not supported on Windows Server 2003. However, you may
install Content Server 5.2.5 on Windows Server 2003 and then immediately apply Service
Pack 2. Three upgrade paths are supported.
The first upgrade path is:
1.
Install Content Server 5.2.5 on Windows 2000.
2.
Install Service Pack 2.
3.
Upgrade the operating system to Windows 2003.
The second upgrade path is:

1.
2.
Upgrade the operating system to Windows 2003.
3.
Immediately install Service Pack 2.
The third upgrade path is:

1.
2.
Immediately install Service Pack 2.
Configuration Decisions
If Content Services for EMC Centera and Trusted Content Services were not enabled
when Content Server 5.2.5 was installed, you can optionally enable them when you
configure the Docbase after installing Service Pack 2.
Content Server 5.2.5 SP2 introduces a new feature, Content Storage Services (CSS),
which requires purchasing a Content Storage Services license. CSS provides tools for
determining content storage for new documents automatically by object type, format,
and other parameters, using assignment policies. Storage for existing documents can be
determined using migration policies. CSS is enabled during Docbase configuration.
Making Backups
The only way to roll back from SP2 to an earlier installation of Content Server 5.2.5 is by
restoring from a backup of the earlier Docbase. Ensure that you create a full Docbase
backup before you install SP2. The backup must include the database tables for the
Docbase and Content Server host file system, including the file storage areas.
Upgrading DocBrokers
If you are upgrading a server installation to SP2, you must upgrade any DocBrokers
in that installation.
You are not required to upgrade DocBrokers on remote hosts.
10
Chapter 2
Upgrading Content Server
This chapter describes how to upgrade to Content Server 5.2.5 SP2.

This chapter contains the following topics:
Before You Upgrade, page 11
Upgrading Distributed Configurations, page 11
Upgrading the Server Software Installation on the Host, page 11
Upgrading the DocBroker, the Server and the Docbase, page 13
Before You Upgrade

Review the Content Server Installation Guide for version 5.2.5 in addition to this document.
Ensure that all required settings and parameters are correct.
On Windows, you must add DFC_install_location\jdk\142_04\bin to the PATH system
environment value. On UNIX, ensure that all environment variables are set correctly.
Upgrading Distributed Configurations

In multiserver and distributed configurations, upgrade the server software and run the
server configuration program on all of the secondary hosts.
Upgrading the Server Software Installation on

the Host
Use these instructions to upgrade the server software installation on the host.
To upgrade the software installation to SP2:
1.
Log in to the host system using the installation owner account.

This is the account used to install the existing Content Server and Docbase(s).
2.
Disable all jobs.
11
3.
On Windows, disable jobs in all Docbases on the host.
On UNIX, disable jobs in all Docbases in the installation that you are upgrading.
Shut down the Docbases and DocBrokers.
On Windows, click StartoProgramsoDocumentumoServer Manager, select

the correct Docbase, and click Stop; click the DocBroker tab, select each
DocBroker, and click Stop.
Shut down all Docbases and DocBrokers on the host.
On UNIX, run the dm_shutdown_Docbase script, where Docbase is the name of the
Docbase to be stopped, then stop each DocBroker using the dm_stop_docbroker
utility. (For instructions, refer to Chapter 7, The DocBroker, in the Content
Server Administrators Guide.)
Shut down all Docbases and DocBrokers in the installation that you are
upgrading.
4.
If you have Apache Tomcat or any other application server running as the Java
method server, shut it down.
To shut down Tomcat on Windows, stop the service called Documentum Java
Method Server.
To shut down Tomcat on UNIX, run the script

$DM_HOME/tomcat/bin/shutdown.sh.
5.
Connect to the Documentum download site.
6.
Navigate to the correct product directory.
7.
Navigate to the server version corresponding to your operating system and database.
8.
Copy the compressed distribution file to a temporary directory on the Content

Server host.
9.
Navigate to the files location on the host.
10. Extract the file.
On Windows, double-click the file.
On UNIX, uncompress and untar the file:

% tar xvf filename
The following files are extracted from the compressed file:

ContentServerSP.exe (on Windows) or ContentServerSP_operatingsystem.bin (on
UNIX)
dfcSetup.jar
server.jar
suite.jar
jdkSetup.jar
11. Start the installation program.
On Windows, double-click the file named ContentServerSP.exe.
On UNIX, type
% ContentServerSP_operatingsystem.bin
12
and press Enter, where operatingsystem is the operating system on which you
are installing.
A Welcome dialog box is displayed.
12. Click Next
The installation program collects information about the host and the Documentum
installation. The installation program indicates that an earlier version of the server
exists on the host and asks if you want to upgrade.
13. Click Yes.
The Documentum Foundation Classes Optional Features dialog box is displayed.
14. To install the DFC developer documentation, check the checkbox.
15. On Windows, optionally check the checkbox to install the Primary Interop Assembly
Check the Primary Interop Assembly Installer checkbox to request installation of a
Microsoft installer package (.msi file) for the DFC primary interop assembly (PIA),
or leave the box unchecked if you do not wish to have the package installed. The
installer places the installer package for the DFC PIA into the setup subdirectory of
the program root.
16. Click Next.
An informational dialog box is displayed with information about SP2 and
instructions to stop Docbases, DocBrokers, and the Java method server.
17. Click Ok.
A dialog box is displayed, listing the products and support components to be
installed.
18. Click Next.
DFC is upgraded and the new server software is installed.
19. Choose when to configure the server.
To configure the server immediately, choose Configure server now and click
Next.
To configure the server at another time, choose Configure server later and click
Next.
A panel saying that the software has been installed is displayed.

20. Click Next.
Upgrading the DocBroker, the Server and the

Docbase
This section provides instructions for upgrading the DocBrokers, Servers, and Docbases
on the host. Perform this part of the upgrade after you upgrade the software installation.
On Windows, this part of the upgrade is after the system restarts.
13
To upgrade the Docbase, Content Server, and the DocBroker:
1.
Start the configuration program.
On UNIX, type these commands:

% cd $DM_HOME/install
% Server_Configuration_Program.bin
On Windows, log in to Windows as the Documentum installation owner.
If the setup process on Windows does not continue automatically, follow these steps:
a.
Restart the host manually.
b.
After the reboot is completed, log in as the Documentum installation owner.
c.
Click StartoProgramsoDocumentumoServer Manager.
d.
On the Utilities tab, click Server Configuration.
A Welcome dialog box is displayed.

2.
Click Next.
3.
On Windows, type in the installation owners password and click Next.

The installer verifies the password.
4.
If you did not enable Trusted Content Services during installation, optionally choose
to enable TCS, type in the license key, and click Next.
5.
If you did not enable Content Services for EMC Centera during installation,
optionally choose to enable the feature, type in the license key, and click Next.
6.
Choose Custom Configuration and click Next.
7.
Check both checkboxes.

It is a requirement that you upgrade the DocBrokers and Docbases in the installation.
8.
Upgrade the DocBrokers.
a.
Choose Upgrade an Existing DocBroker.
b.
Select the DocBroker to upgrade.
c.
Click Next.
The DocBroker is upgraded.
d.
Choose whether to upgrade additional DocBrokers on the local host or continue

with server configuration.
e.
If you are upgrading additional DocBrokers, perform steps a-d as required.
f.
Click Continue with server configuration and then click Next.

The Docbase Configuration dialog box is displayed.
9.
To complete the process of enabling Trusted Content Services:
a.
b.
c.
d.
14
Choose Enable secure connection in an existing 5.2 Docbase.

Click Next.
Select the connection mode.
Click Next.
The dmcl.ini file is updated.
e.
Click Restart now.

The Docbase is stopped and restarted.
f.
Click Configure an additional Docbase.
10. Choose Apply Service Pack 2 to existing Docbase, select the Docbase, and click
Next.
A dialog box asks if you are sure you want to apply the service pack.
11. Click Yes.
12. Choose whether to accept or modify the Docbase configuration scripts.
In general, you do not need to edit these scripts.
To accept the scripts, click Next.
To edit a script, select it and click Edit Script. After you edit and save the
scripts, click Next.
The scripts run and the Docbase is configured.

13. To install new DocApps for applications that exist in your Docbase, check the
checkboxes and click Next.
Caution: If Web Publisher 5.2.5 SP1 is installed in the Docbase, do not reinstall the
Web Publisher DocApp or Accelera DocApp.
14. Optionally choose to enable Content Storage Services (CSS), then type in the license
key and click Next.
15. Choose whether to configure additional Docbases on the host.
To configure additional Docbases, check the checkbox and click Next, then skip
back to Step 10.
To continue, click Exit from server configuration and clickNext.
A summary dialog box is displayed.

16. Click Finish.
The server and Docbase upgrade is complete.
15
16
Chapter 3
Postinstallation Tasks
This chapter describes any tasks that must be done after the product is installed but before it can
be used.
This chapter contains the following major topics:
WDK Applications, page 17
Setting the i_retain_until Attribute, page 17
Running Scripts Manually, page 17
WDK Applications
If you are running any WDK applications against a Docbase that has been upgraded to
5.2.5 SP2, restart the application server after the Docbase upgrade.

If a Docbase is licensed for Content Services for EMC Centera and its storage
areas include content-addressed stores using retention dates, execute the
UPDATE_RETAIN_UNTIL_DATE apply method after it is upgraded to 5.2.5 SP2. For
instructions, refer to Chapter 4, Setting the i_retain_until Attribute.
Running Scripts Manually

A number of scripts are executed during Docbase configuration. If any do not run
correctly, run them manually after the upgrade is completed.
Apply Formats Script

The dm_apply_formats.ebs script is located in $DM_HOME/bin. It updates the format
objects that are defined in the formats.cvs file. (The formats.cvs file is located in
17
$DM_HOME/install/tools (UNIX) or %DM_HOME%\install\ools (Windows). The

syntax for running dm_apply_formats.ebs manually is
dmbasic -f dm_apply_formats.ebs -e testmain -P noreport DocbaseName
UserName Password $DM_HOME/install/tools/formats.csv trace
where DocbaseName is the name of the Docbase you are upgrading, UserName is the user
name of a Superuser, and Password is the Superusers password.
Docbase Tools Script

The toolset.ebs script is located in $DM_HOME/install/admin (on UNIX) or
%DM_HOME\install\admin (Windows). It installs Docbase administration tools. The
syntax for running toolset.ebs manually is
dmbasic -f toolset.ebs -e ToolSetup -P DocbaseName
$DM_HOME/install/admin ""
where DocbaseName is the name of the Docbase you are upgrading. Ensure that you
pass in "" as the third argument.
Content Services for EMC Centera Script

The csec_plugin_upgrade_525_sp2.ebs script is located in $DM_HOME/install/admin
(on UNIX) or %DM_HOME%\install\admin (Windows). It updates the plugin
object required by Content Services for EMC Centera. The syntax for running
csec_plugin_upgrade_525_sp2.ebs manually is:
dmbasic -f csec_plugin_upgrade_525_sp2.ebs -e Install -P DocbaseName
UserName Password $DM_HOME OSName
where DocbaseName is the name of the Docbase you are upgrading, UserName is the
user name of a Superuser, Password is the Superusers password, $DM_HOME is
$DOCUMENTUM/product/version_no, and OSName is Windows, Solaris, HPUX, or
AIX.
Templates Script
The templates.ebs script, located in $DM_HOME/install/admin, creates dm_document
objects in order to enable creation of new objects with Documentum Desktop. Certain
applications require default template files when opened. The syntax is:
dmbasic -f templates.ebs -P DocbaseName UserName Password
$Documentum $DM_HOME -e Install
18
DFC Support Script

The dfc.ebs script, located in $DM_HOME/install/admin, loads the initial default
objects for the Documentum Foundation Classes. The syntax is:
dmbasic -f dfc.ebs -P DocbaseName UserName Password -e
Install
Content Intelligence Services Schema Installation

Script
The ci_schema_install.ebs script, located in $DM_HOME/install/tools, installs all types
necessary for the Content Intelligence Services application. The syntax is:
dmbasic -f ci_schema_install.ebs -P DocbaseName UserName
Password -e EntryPoint
Email Templates Components Script

The dm_emailTemplate_install.ebs script creates the objects for the email template
feature. The script is located in $DM_HOME/install/admin. The syntax is:
dmbasic -f dm_emailTemplate_install.ebs -P Docbasename
Username Password -e install
Display Configuration Setup Script

The display_config_setup.ebs script is located in $DM_HOME/install/tools. It adds the
default display configuration objects for Webtop and Desktop. The syntax is
dmbasic -f display_config_setup.ebs -P Docbasename
Username Password -e EntryPoint
Data Dictionary Script

The dd_populate.ebs script is located in $DM_HOME/bin. It populates the data
dictionary with attribute and type information from data files.
Edit the $DOCUMENTUM/dba/config/Docbase_name/data_dictionary.ini file to add or
remove data dictionary language support for the different locales, then run the script.
The syntax for running dd_populate.ebs manually is
dmbasic -f dd_populate.ebs -e Entry_Point -P DocbaseName UserName
Password $DOCUMENTUM/dba/config/docbase_name/data_dictionary.ini
19
where DocbaseName is the name of the Docbase you are upgrading, UserName is the user
name of a Superuser, and Password is the Superusers password.
20
Chapter 4
Release 5.2.5 SP2 introduces a new attribute for the dm_sysobject type called
i_retain_until. This attribute records the most restrictive retention date for objects whose
content is stored in content-addressed storage with a retention date. The most restrictive
date is the retention date farthest in the future, and it may be specified for a primary
content file or a rendition.
The attribute value is displayed by Documentum Webtop, so users can view an objects
retention date. Documentum Administrator displays the attribute value also, and users
with appropriate privileges can change its value through Documentum Administrator.
Upgrading Content Server to 5.2.5 SP2 adds this attribute to the dm_sysobject type
definition and to all SysObjects in the Docbase. However, upgrading does not set the
attribute. After you upgrade, if a Docbase is licensed for Content Services for EMC
Centera and its storage areas include content-addressed stores using retention dates,
you must execute a new administration method, UPDATE_RETAIN_UNTIL_DATE.
This sets the attribute for those objects whose content files have retention dates. This
chapter contains the reference information for executing this method. You must have
Superuser privileges to execute the method.
During normal user operations, this attribute is set by:
Execution of a SET_CONTENT_ATTRS administration method by Content Server
Execution of a Setcontentattrs API method by the client DMCL.

Note: The Setcontentattrs method is not atomic. The attribute values set by this
method are not saved to the Docbase until a Save is issued, either by the DMCL or by
the application (if the transaction is an explicit transaction).
This attribute is only set if the executing Content Server or client DMCL is at the
5.2.5 SP2 level. If you run pre-5.2.5 SP2 Documentum clients, specifically Webtop,
against a 5.2.5 SP2 server, the attribute is not updated when users modify content
in content-addressed storage areas. When you do upgrade the client, executing
UPDATE_RETAIN_UNTIL_DATE once again, after the upgrade, is recommended, to
update the i_retain_until attribute for objects that may have been modified using the
pre-5.2.5 clients.
Observe the following guidelines for executing UPDATE_RETAIN_UNTIL_DATE:
You must have Superuser privileges to execute the method.
If any affected object is checked out while the method executes, subsequent attempts
to check in the object fail due to a version mismatch error. Consequently, it is
21
strongly recommended that you execute the method in a quiet Docbase and that all
objects are checked in.
Executing this method does not reset the r_modify_date on the objects. However, it
updates the i_vstamp. Because of this, if objects are part of a replication job, they are
re-replicated.
22
UPDATE_RETAIN_UNTIL_DATE
Purpose
Sets the i_retain_until attribute in SysObjects.
Syntax
To update the attribute for a single SysObject:
EXECUTE update_retain_until_date
FOR sysobject_id
dmAPIGet("apply,session,sysobject_id,UPDATE_RETAIN_UNTIL_DATE")
To update the attribute for all objects that satisfy a DQL query:
WHERE_CLAUSE=qualification[,BATCH_SIZE=integer]
dmAPIGet("apply,session,NULL,UPDATE_RETAIN_UNTIL_DATE,
WHERE_CLAUSE,S,qualification[,BATCH_SIZE,I,integer]")
23
Arguments
Table 41. UPDATE_RETAIN_UNTIL_DATE Arguments
Argument
Datatype
Value
Description
WHERE_CLAUSE
qualification
Specifies a valid DQL

WHERE clause qualification.
(Refer to the description of
the SELECT statement in the
DQL reference manual for a
full description of WHERE
clause qualifications.)
The qualification must be
enclosed in single quotes. All
attributes referenced in an
expression of the WHERE
clause must belong to the
dm_sysobject type. Any
literal string values in the
WHERE clause must be
escaped with an additional
single quotation mark when
the method is executed using
dmAPIGet().
BATCH_SIZE
integer
Defines the maximum

number of SysObjects that
may be updated in a single
transaction.
The default is 500.
Note: If this is set to 0 or a
negative number, Content
Server resets it to 500.
Return Value
The method returns a collection with one query result object. That object has one
attribute, named result, that records the number of objects modified by the method.
Permissions
You must have Superuser privileges to execute this method.
24
General Notes
This method affects only objects that have one or more primary content files or renditions
stored in a content-addressed storage area with a retention date. The method sets the
i_retain_until attribute of the object to the most restrictive of the retention dates specified
for the primary and rendition content files that are stored in the content-addressed
storage areas.
The most restrictive date is defined as the date that is farthest in the future from the
current date.
Caution: Executing this method updates the i_vstamp attribute of affected objects.
Because the method updates i_vstamp, if an affected object is checked out when the
method executes, checking in the object will fail with a version mismatch error. It is
strongly recommended that you execute this method when there is little or no activity in
the Docbase and that all objects that may be affected are checked in before executing the
method.
The value for the i_retain_until attribute is computed based on information retrieved
from the content-addressed storage system. Because of this, there may be a small
difference between the retention date specified when the object was created and the
date for the i_retain_until attribute that is set by the UPDATE_RETAIN_UNTIL_DATE
method. The retention period in seconds is retrieved from the storage system and is
added to the r_creation_date attribute of the object to compute the retention date.
The method does not reset the r_modify_date attribute of the affected objects.
The method logs messages in the server log.
Related Administration Methods

None
Examples
The following examples update the attribute for the document identified by
090000013573af2c:
FOR 090000013573af2c
dmAPIGet("apply,c,090000013573af2c,UPDATE_RETAIN_UNTIL_DATE")
These examples update 200 SysObjects that store email messages:

WHERE_CLAUSE=subject=email_msg
,BATCH_SIZE=200
dmAPIGet("apply,c,NULL,UPDATE_RETAIN_UNTIL_DATE,
25
WHERE_CLAUSE,S,subject=email_msg,BATCH_SIZE,I,200")
26
Chapter 5
Uninstalling Content Server
You cannot uninstall or back out Service Pack 2 except by restoring from a full Docbase backup,
including database tables and the Server host file system.
To delete a Docbase or DocBroker, or to uninstall the Server software, use the instructions in the
Content Server Installation Guide for version 5.2.5.
27

Documentum Content Server 5.2.5 SP2 Installation

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Documentum Content Server 5.2.5 SP2 Installation

Загружено:

Авторское право:

Доступные форматы

Content Server Installation Guide

Version 5.2.5 SP2

Copyright 1994-2004 Documentum, a division of EMC. All Rights Reserved.

Planning for Installation .........................................................................

Operating Systems and Databases ..............................................................

Configuration Decisions ..............................................................................

Making Backups .........................................................................................

Upgrading DocBrokers ...............................................................................

Upgrading Content Server ......................................................................

Upgrading the Server Software Installation on the Host ................................

Upgrading the DocBroker, the Server and the Docbase ..................................

Postinstallation Tasks .............................................................................

Setting the i_retain_until Attribute ...............................................................

Running Scripts Manually ...........................................................................

Setting the i_retain_until Attribute

Uninstalling Content Server

Content Server Installation Guide

UPDATE_RETAIN_UNTIL_DATE Arguments .................................................

Content Server Installation Guide

Content Server Fundamentals contains information on Docbases, DQL (Document

Content Server Administrators Guide contains information on configuring a

Documentum Distributed Configuration Guide contains information on implementing

Content Server Object Reference Manual contains reference information on objects.

Content Server Installation Guide

Content Server DQL Reference Manual contains reference information on Document

Documentum System Migration Guide contains information on migrating your

Represents a term, or a variable for which

Represents code samples, user input, and

Indicates an optional argument in method

Indicates an optional argument that can

Links in Server PDF Files

Content Server Installation Guide

This chapter contains the following topics:

About Installation, page 7

Operating Systems and Databases , page 8

Configuration Decisions, page 8

Making Backups, page 9

Upgrading DocBrokers, page 9

Adds attributes to existing Docbase objects

Adds new types to the Docbase

Runs configuration scripts

Content Server Installation Guide

Planning for Installation

Backs up the earlier version of all changed files to $DOCUMENTUM/_5.2.5.SP2_

Operating Systems and Databases

Upgrade Paths to Windows Server 2003 Operating

Install Content Server 5.2.5 on Windows 2000.

Install Service Pack 2.

Upgrade the operating system to Windows 2003.

The second upgrade path is:

Install Content Server 5.2.5 on Windows 2000.

Upgrade the operating system to Windows 2003.

Immediately install Service Pack 2.

The third upgrade path is:

Install Content Server 5.2.5 on Windows 2003.

Immediately install Service Pack 2.

Content Server Installation Guide

Planning for Installation

Content Server Installation Guide

Planning for Installation

Content Server Installation Guide

This chapter describes how to upgrade to Content Server 5.2.5 SP2.

Before You Upgrade, page 11