EMC

Documentum
®

System
®

ersion

V

7.2

Upgrade

and

Migration

Guide

www.EMC.com

1-508-435-1000

Hopkinton,MA01748-9103

CorporateHeadquarters

EMCCorporation

Legal Notice
Copyright © 1994-2016 EMC Corporation.All		Rights Reserv ed.
EMC believ es the information in this publication	is	accurate as of its publication	date.The	information is subject	to change
DISCLAIMS OR THE without notice. INFORMA TION IN ARRANTIES W IMPLIED OF ARRANTIES KIND THIS PUBLICA OF WITH TION IS PROVIDED THE AS “ ABILITY IS.” EMC TION FITNESS A THIS TION CORPORA MAKES TION, NO REPRESENT A AND TIONS ANY W MERCHANT TO RESPECT OR INFORMA IN FOR PUBLICA SPECIFICALL Y ARTICULAR P PURPOSE.
Use, copying, and distribution of any EMC softw	are	described in this publication	requires	an applicable softw are	license.
For the most up-to-date listing of EMC product	names, see EMC Corporation rademarks T on EMC.com.Adobe				and Adobe PDF
Library are trademarks or registered trademarks	of	Adobe Systems Inc.in the U.S.	and other countries.All other		trademarks
used herein are the property of their respectiv e	owners.
Documentation Feedback

Y

our

opinion

how

w

matters.W

e

w

e

can

make

our

ant

to

documentation

hear

from

ECD.Documentation.Feedback@emc.com

about

better

ou

y

easier

regarding

or

to

our

use,please

product

documentation.If

send

us

y

our

y

ou

hav

feedback

e

feedback

at

directly

T

able

of

Contents

Preface. .		.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.9
Chapter	1Upgrade																					and						Migration															Overview.																			.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.13
							Upgrade														and						Migration															.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.13
							Understanding																							Migration														.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.14
							Order										of				New							Product											Installation																	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.15
							Order										of				System										Updates													.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.16
Chapter	2Planning																					the						Documentum																					System												Upgrade.																	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.19
							System												Upgrade													Strategies														.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.19
							Changes														that						Impact											Content											Serv er										Upgrade													or				Migration														.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.22
											Linking to																the					32-bit								Oracle											Client								Library											on					Linux									.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.22
											Upgrading																Multiple													Repositories																		to				the					Same								V ersion											.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.23
							Mapping Y our Current																																	Configuration																					.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.23
							Designing																a		Documentum																				7.x					Configuration																				.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.26
											Addressing																	Hardw are															Concerns														.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.26
											Upgrading																Third-party																		Softw are													.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.27
											Planning														for					Global									Registries																. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.27
											Mapping														a		Documentum																					7.x					Configuration																				.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.28
							Planning															Upgrade												and						Migration															to			Documentum																					7.x				.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.28
											Setting												Up				a		T est							Environment																			.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.28
											Creating																	the					T est						Environment																				.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.28
											Migrating															a			TCS-Enabled																			Docbase												to				a		New							Serv er										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.29
											Client-First																	Migration															.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.29
							Planning															Upgrade												for					Repositories																		in			a			Federation																. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.30
											Guidelines																for					Upgrading																a			Distributed																	Configuration																				.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.30
							Planning															the				Upgrade													or				Migration															of			the						AEK							Key to									Lockbox														.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.31
							Enabling														Remote												Key Management																									.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.31
Chapter	3Upgrading																							Content														Server.														.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.33
							Upgrade														Checklist														.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.33
											Changing															the					Database														Operating															System										and						V ersion												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.35
											Preparing															DB2							databases														for					Upgrade													.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.36
											Migrating															the					Database														to				UTF-8									.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.36
											The							database_refresh_interv al																																					Key						.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.36
											Ensuring														the					Completion																		of			Automatic																asks T								Before									Upgrading																	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.36
											Ensuring														that						the						dm_serv												er_config													Object									is				Unlocked														.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.37
							Upgrading																	to			64-bit									Content												Serv							er			.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.37
											64-bit										ODBC									and						DSN							Libraries														.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.38
											Errors										During											Upgrade													.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.39
											Components																			Not							Supported															after							Upgrade													.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.39
											Migrating															Custom												Plug-ins													.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.40
											Upgrading																	Content											Serv							er			on					Red						Hat						Linux									5.x Systems																	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.40

3

able

T

of

Contents

	Upgrading the Content															Serv er						Softw are														.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.40
	Upgrading Content									Serv er Installed																				with								Cluster											Services										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.44
	Upgrading Content										Serv er									in a				Distributed																		or			Load-Balanced
	Configuration		. .	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.45
		Upgrading	the				BOCS										Serv er						.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.47
		Upgrading	the				DMS Serv er															.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.47
	P	ost-Upgrade	T	asks							.	.	.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.48
		Improving	P erformance																	after				Upgrade														.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.48
		Extending	the			Oracle											ablespace T												Size							.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.48
		Enhancements					after								Upgrade										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.49
		Reinstalling D2						Client Libraries																				.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.49
		Rebuilding	the				database													views							.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.49
Chapter	4Upgrade Scenarios.															.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.51
	Upgrading Content									Serv er 6.5												SP2						to			7.2						—				W indows/SQL																				Serv er										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.51
	Upgrading Content									Serv er 6.5												SP3						to			7.2						—				AIX/DB2 .												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.55
	Upgrading Content									Serv er 6.5												SP3						to			7.2						—				W indows/SQL																				Serv er										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.59
	Upgrading Content									Serv er 6.7												to			7.2					—				W				indows/Oracle																			.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.63
	Upgrading Content									Serv er 6.7												SP1						to			7.2						Linux/Oracle —																					.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.64
	Upgrading Content									Serv er 6.7												SP2						to			7.2						Solaris/Oracle —																						.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.68
	Upgrading Content									Serv er										7.0		to			7.2					—				W				indows/SQL																.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.72
	Upgrading Content									Serv er										7.1		to			7.2					—				Linux/Oracle .																			.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.75
Chapter	5Migrating Content									Server.												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.77
	Understanding			the					Migration Process																								.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.77
	Migration Checklist										.	.	.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.79
	Planning a Migration												.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.80
	Migration Methods									.	.	.	.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.81
		Method 1:Migrating															a	Repository														.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.82
		Method 2:Copying													a		Repository													.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.83
	Migrating Data			Using										SQL						Serv er							.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.85
	Consolidating		Repositories																	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.86
	Migrating Data			from								Earlier V ersions																				of				Content												Serv er								.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.90
	Migrating XML			Content													to			the		XML								Store									.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.90
	Using DQL to		Migrate												Content								to				an				XML								Store								.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.91
	Migrating Custom								Content												Serv			er			Methods															.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.91
	Migrating DocApps										and						BOF2					Modules														.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.91
	P	ost-Migration asks T											.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.92
Chapter	6Migrating DFC			Customizations.																										.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.93
	Jav a Class Changes									.	.	.	.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.93
	Configuring DFC						for					Nativ e IPv4														Operations																	.	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.94
	Configuring 6.7			Clients												to			ork W					with								Content												Serv er 7.x													.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.94
	Migrating Customizations																		to Business														Objects											.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.94
	Migrating DMCL						API							Calls							to	DFC							API							Calls .								.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.95
	Search Service		.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	. . . .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.95
	Full Format Specifications																		No Longer													Accepted														.	.	.	.	. .	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.95

4

																																																																able T							of			Contents
	Character		String								Handling Improv																										ed .				.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.95
	Aspects,	a	New							BOF								Module												T ype								for				Dev elopers																.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.96
	JMX Management														of			DfPreferences and																										dfc.properties																				.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.96
	DFC Deployment													.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.96
	Configuration							for					AAC									okens T										.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.97
	Setting	the		Maximum															Number													of				Results										P er					Source											.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.97
	DFC Does		Not						Support													Linked										Store								Storage											Areas.											.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.97
	External	Storage										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.97
	DFC Does		Not						Support													Optical											Storage										Devices												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.98
Chapter	7Migrating			DFS						Customizations.																													.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.99
	Upgrading			the					DFS								.NET							Productivity																		Lay er								.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.99
	Upgrading							from								a		V ersion												Earlier										Than							7.x					.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.100
	Upgrading							from								a		Pre–7.x												Minor									V ersion										or				Service											P ack								.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.101
	Restoring rusted T													Certificates																	after							Upgrading															UCF								.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.101
	rusted T Login							is			Disabled															By				Default . . . . . . . . . . . . . .																							.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.102
	Cookie	Consistency															Check										.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.102
	.NET Framew ork												Update												.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.102
Chapter	8Migrating		CMIS									Customizations. .																													.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.103
	getFolderP			arent							Returns Feed																				. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.103
Chapter	9Migration		Scenarios.																					.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.105
	Migrating		Content												Serv							er			6.5					SP2						to				7.2			—				W indows/SQL																						Serv er										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.105
Appendix AMigrating				DMCL									APIs									to				DFC.											.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.111
	Ov erview		.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.111
	Methods	with						no					corresponding																					DFC							method											.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.111
	Methods	with						corresponding DFC																													methods												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.112
Appendix BObject T		ype					and						Property															Changes.																	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.119
	New object				types								.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.119
	Changed	object								types									.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.120
	Changed	object								types									with new														properties .															.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.127
Appendix Cdfc.properties.														.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.129
	Ov erview		.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.129
	Changes	to			existing												key						names									.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.129
	dmcl.ini	key					migration														to				dfc.properties																			.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.132
	Obsolete	dmcl.ini											and							session											configuration																		options												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.133
	Obsolete	dfc.properties																				keys							.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.135
Appendix DLDAP Certificates.																				.	.	.	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	. .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.137

5

able

T

of

Contents

List

of

Figures

Figure	1.System	Installation	Order ,									New								Documentum																					System												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.15
Figure	2.System	Update Order ,						Existing											Documentum																					System												.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.16
Figure	3.System	Upgrade Scenarios											.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.21
Figure	4.Upgrade Steps from				32-bit Content																				Serv er										to				64-bit									Content													Serv er										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.38
Figure	5.Pre-7.x	32-bit Content						Serv er								Environment																				.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.78
Figure	6.Migration Process .		.	.	.	.	.	.	.	.	. .	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.79

6

able

T

of

Contents

List

of

ables

T

able T 1.Upgrade and	Migration													of Product												Components																				.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.13
T T T T T T able able able able able able 7.Memory 6.Customized 5.Client 4.Index 3.Application 2.Content Serv er Serv Serv er W Host Machine and Database Serv er Host orksheet W er Host orksheet W orksheet W orksheet . . . . . . . . . . . . . . . . . . . . . . . . . orksheet W . . . . . . . . . . . . . . . . . . . . . . . Documentum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Executables Components by Consumption																																																				. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	. . . . . .	.26 .25 .25 .24 .24 .23
able T 8.P arameters required by dm_acs_install.ebs																																					script										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.46
T T T T T T T T T able able able able able able able able able 17.Migration 16.Base 15.Base 14.Base 13.Base 12.Base 11.Base 10.Base 9.Base and and and and and and and and Upgraded Upgraded Upgraded Upgraded Upgraded Upgraded Upgraded Checklist Upgraded OS/DB/CS OS/DB/CS OS/DB/CS OS/DB/CS OS/DB/CS OS/DB/CS OS/DB/CS OS/DB/CS . . . . . . . . . . . . . . . .																					V ersions V ersions V ersions V ersions V ersions V ersions V ersions V ersions . . . . . . . . . . . . .												. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .									. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	. . . . . . . . .	.79 .76 .73 .68 .64 .63 .59 .55 .52
T T able able 19.DFS 18.Premigration asks T . . . . . .NET Productivity .													. . . . . . . . Lay er .						. . . . . . . . . . . . . Upgrade												.	. . . . . . . . . . Matrix										. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	.99 .80
T T able able 21.DMCL 20.Base and Upgraded API methods OS/DB/CS and V ersions corresponding																																	. . . . . . . . DFC								. . . . . . . . . . . . . . methods														. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	. .	.112 .105
able T 22.New object	types				.	.	.	. .	.	.	.	.	.	.	.	. . . . . . . . . . . . . . . . . . . . .																	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.119
able T 23.Changed object types										.	.	.	.	.	.	. . . .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.120
able T 24.New object properties											.	.	.	.	.	. . . .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.127
able T 25.Name changes for existing dfc.properties																																			since								v ersion													6.5					and						dfc.new
properties	.	. .	.	.	. .	.	.	. .	.	.	.	.	.	.	.	. . . .	.	.	.	.	.	.	. .	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.129
able T 26.dfc.properties		keys					migrated											from							dmcl.ini													file					.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.132
able T 27.Obsolete session configuration																					options										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.134
able T 28.Obsolete dfc.properties keys . . . .																					. . . . . . . . . . .										.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.	.135

7

able

T

of

Contents

8

Preface

6.6,

This

guide

6.7

SPx,

describes

7.0,

7.1

the

necessary

to

steps

to

upgrade

an

existing

7.x

implementation

Documentum

EMC

Documentum

6.5

SP2,

6.5

SP3,

Intended

audience

custom

This

guide

is

for

IT

personnel

applications.

who

are

upgrading

the

Documentum

system,

including

Documentum

Document

scope

This

guide

describes

how

to

upgrade

a

Documentum

system

and

migrate

customizations

to

the

upgraded	Content	Serv er.Refer	to	the	EMC	Documentum	Content	Server	Installation	Guide	for
additional	detailed	planning information.

Documentum

For

are

The

release

for

upgrade

an

earlier

this

guide

6.6

to

to

Documentum

v

provides

ersion,

first

upgrade

is

7.x

to

supported

from

Documentum

mov

6.5

SP2,

e

and

to

existing

then

6.5

to

SP2

onw

ards.If

upgrading

migration,

Documentum

instructions

to

includes

Documentum

in

system

appropriate

7.x.This

customizations

y

our

Documentum

guide

instructions

optimize

y

7.x.

ou

All

follow

All

behavior

This

"turned

by

it,

disabling

off

guide

in

by

unw

default

anted

for

new

behaviors

or

6.5

and

later

v

on

features,

in

this

document

activ

ating

earlier

where

to

features

a

new

that

hav

e

been

deprecated

or

replaces

all

v

or

does

”

ersions.

except

refer

not

Documentum

later

applications.

new

focus

and

in

this

feature

6.5

changes

SP2

and

existing

that

custom

to

6.5

references

references

document

7.x.

refer

to

Documentum

7.2.

ersions

including

to

7.x

Documentum

Revision

history

The

following

changes

hav

e

been

made

to

this

document.

9

Preface

Revision

Date

Description

September 2016

Updated the “Preupgrade Tasks” sections for the Linux/AIX/Solaris upgrade scenarios in Chapter 4, Upgrade Scenarios.

June

2016

Added the notes about

standard jobs in the

section,

Upgrading the Content

Server Software, page

40

.

May

2016

Updated the section, Upgrading Content Server

in

a

Distributed or Load-Balanced Configuration,

page

45

.

July

2015

Added upgrade information from Red Hat Enterprise

Linux 6.4 to Red Hat Enterprise Linux 7.0.

May

2015

Added upgrade information for SUSE Linux

Enterprise.

February

2015

Initial publication.

Terminology

The following table

provides

a

definition

of

the commonly used terms

in this guide.

Term	Definition
Upgrade	Refers to moving seamlessly from				a previous version of
	the	software to a more recent		version.When hardware
	and	third-party applications are compatible with the new
	version, and the existing version supports direct upgrade,					an
	in-place move from an earlier			version of EMC products can
	be	performed.
Migration	Refers to moving customizations from one Content Server
	instancetoanother.Itcanrefertomovingfroman
	unsupported environment		to	a supported one, such as
	an	upgrade that cannot be	done in		place due to lack of
	compatibility or the need to		update/change hardware, or			the
	need	to move from an unsupported			operating system/platform
	to	a supported one.It can	also refer		to moving data from
	one	location, server, or repository			to another.The process	of
	migration involves creating		a repository and then copying			the
	content from the old repository to the new repository.
Compatibility	Referstosoftwarecomponentsthatareintendedto
	work together seamlessly.For example, different clients
	that	can independently modify objects in the repository
	without conflicts, or an environment				where Content Server
	applications, repositories, or		client		applications of different

10

Preface

v	ersions coexist	in	an implementation			(mixed	v	ersion
environments)		without		conflicts	or errors.

1

1

Preface

12

Chapter

1

Upgrade

and

Migration

T

This

chapter

provides

opics

include:

a

conceptual

ov

•Upgrade

and

Migration,

page

13

erview

of

upgrade

and

•Understanding Migration,			page	14
•Order	of	New Product Installation,			page	15
•Order	of	System Updates,	page	16

Upgrade

and

Migration

Overview

migration

of

a

Documentum

instance.

This

guide cov ers upgrade

and

migration of Documentum

platform applications.

Y ou

must be on Documentum

6.5

SP2 or later to

perform

an in-place

upgrade

to

Documentum

7.x.

Direct

in-place upgrade to

Documentum 7.x is supported

from Documentum

6.5

SP2,

but

only

if

the

existing operating system/database/hardw

are combination

is

also supported

for

Documentum

7.x.Otherwise,

a migration

is

required

to mov

e to

a

supported

platform.The EMC

Documentum

Y

requires

another

operating

Migration

and

The

Note:

system,

Envir

target

onment

and

and

System

Requir

hardw

ements

are

in

System

from

to

and

Guide

provides

7.x.

information

Guide

a

a

v

about

ersion

that

the

earlier

is

supported

with

y

of

the

operating

our

database,

refers

v

EMC

to

ersions

system

(for

a

fresh

migrate

objects.T

Documentum

Upgrade

on

and

v

Documentum

moving

provides

Migration

from

een

moving

ersion

to

ersion

to

included

source

6.5

an

instructions

upgrading

betw

same

Documentum

SP2.

unsupported

engagement

Linux).Migration

not

does

refer

to

with

13

shows

such

as

supported

one

v

example,

and

Solaris

database.It

operating

from

operating

system/database

platforms

to

files,

and

system/database

Archiv

e

installation

1,

existing

able

Professional

DocApps,

that

Services.

ou

can

page

customizations

Documentum

can

be

migrated,

(DAR)

or

business

components

upgraded,

both.

able

T

1.Upgrade

and

Migration

of

Product

Components

Component				Migrate	Upgrade
Content	Serv	er		X	X
Custom	DocApp/DAR		files	X

13

Upgrade

and

Migration

Overview

Component			Migrate	Upgrade
Service-based Business		Objects	X
(SBOs)
ype-based T Business		Object	X
(TBOs)
Jav	a methods		X	X

If

y

ou

are

installing

a

new Content Serv

er instance, mov

e

and modify (as

required)

the

custom

Jav

a

methods,

DocApps,

DARs,

SBOs, and TBOs

to

the new

Content

Serv er instance.

Note:

•DocApps, SBOs, TBOs (BOF2		v ersion), and Jav		a methods	bundled		as SBOs	continue to w	ork	in	an
upgraded Content Serv er.
•Y ou	can disable the new features		or activ ate prior features		that	hav	e been deprecated or		turned		off

by

default

for

Documentum

7.x.This

guide

does

not

describe

new

features,

except

where

they

change

or replace existing behavior

in custom applications.

Check

the installation guide for each

application that

y

ou are upgrading

for specific

considerations.

Before

y ou

perform the upgrade, check

the

list

of products that

are compatible

with

Documentum

7.x

provided

in

the

EMC

Documentum

Envir

onment

and

System

Requir

ements

Guide

.

The	EMC	Documentum Content Server System					Object Refer ence Guide provides information			about	new ,
changed, deprecated, and obsolete object							types and properties.
For	information about deprecated, new ,						and obsolete properties in dfc.properties		,	see
dfcfull.properties				.
Understanding Migration
Migration		is	a straightforw		ard process.Y		ou document the current configuration,	plan y our upgrade

configuration, and then upgrade the individual system components in								a sequence		that	minimizes
impact	on	y our users.
Migration		can be separated	into tw	o basic tasks:
•Install and configure Documentum 6.5 SP2 or later softw						are.
•Mov	e configurations and		customizations		to the new serv	ers.
—Enable features that y			ou w ant to keep.
—Disable new features			that y ou do not		w ant.
—Enable new features			for existing custom components.
The Chapter		5, Migrating Content		Serv er chapter provide more			information		about	the	migration

process.

Most

of

the new features

in

Documentum

6.5

SP2 and later

v ersions

are

enabled

by

default.This

guide

provides the

steps

for

enabling

new

features that

are

not enabled

by default.

14

Upgrade

and

Migration

Overview

Order

of

New

Product

Installation

Figure

1,

page

15 shows

the

recommended installation order

for

new Documentum

systems.The

server in

this diagram

is

the

host

for

the RDBMS, Content Serv

er ,

or Index

Serv

er.

Figure

1.

System

Installation

Order

,

New

Documentum

System

The recommended installation		and upgrade order for new Documentum systems		is	as follows.
1.Documentum Content		Serv er
2.Documentum Administrator (DA)
3.Documentum XML	Store
4.Documentum Content		Storage Services (CSS)
5.Documentum rusted T Content Services (TCS)
6.Documentum Content		Services for Centera (CSEC)
7.Documentum Content		Intelligent Services (CIS)
8.Documentum xPlore
9.Documentum High	olume V Serv er (HVS)
10.Documentum Content		ransformation T Services (CTS)
11.Documentum Thumbnail		Serv er
12.Documentum Branch Office Caching Services (BOCS)
13.Documentum Foundation		Services (DFS), including any custom	DFS applications
14.Documentum Content		Management Interoperability Services	(CMIS), including		any	custom

CMIS

applications

15

Upgrade

and

Migration

Overview

16.xCelerated

15.Documentum

Foundation

Platform

Classes

Composition

(xCP)

(DFC),

including

2.x

any

•Documentum	Process	Engine
•Documentum	Process	Integrator

custom

DFC

applications

The coexistence	of	xCP	2.x	and Documentum			6.7.x applications	on	the Documentum 7.x		platform
exists.The “Upgrading			to	enable	xCP	and Documentum clients		to	coexist”	section in the	EMC

coexistence

Documentum

xCP

System

and

Upgrade

and

Migration

Guide,

6.7.x

Release

6.7

SP2

provides

of

2.x

Documentum

applications

scenarios.

information

about

the

Order

of

System

Updates

in

Figure

this

Figure

diagram

2,

page

16

is

2.

System

shows

the

recommended

the

host

for

the

RDBMS,

Content

order

in

Serv

which

er

,

to

upgrade

or

Index

er.

system

Serv

Update

Order

,

Existing

Documentum

System

components.The

server

16

product

Caution:

v

ersion

For

Content

is

Serv

er

supported

,

host

by

the

Content

operating

Serv

system,

er

v

ersion

or

ou

RDBMS

y

are

upgrades,

ensure

installing.For

that

application

the

Upgrade

and

Migration

Overview

serv

er

operating

system

or serv er upgrades,

ensure

that

the

product

v ersion

is supported

by

the WDK-based

application

y ou are installing.The

EMC

Documentum

Envir onment

and System

Requir

ements

Guide

cov

ers

this

information.

is

functionality

v

one

Documentum

The

EMC

installing

In

some

cases,

a

new

y

v

ou

ersion.

must

uninstall

Envir

onment

upgrades

and

to

existing

Requir

are

Documentum

v

ements

Guide

ersion

system

installations

information

on

restrictions,

same

v

before

ersion

a

before

Documentum

product

generally

most

System

provides

compatibility.When

Serv

cases,

requires

upgrading

there

compatibility

to

the

client

Serv

upgrading

or

to

add

major

new

application

product

interoperating

conflicts

result

upgrading

Content

from

products

ersion

family.In

to

compatibility

er.In

these

er

applications

the

client

that

Content

cases,

especially

important.

17

Upgrade	and	Migration	Overview
18

Chapter

2

Upgrade

Planning

the

Documentum

System

Upgrading

a

system

requires

planning.Know

y

our

starting

point,

choose

a

destination,

then

pick

the

best route

to get there.This chapter provides some

practical

advice

for

plotting

y

our

course

from

Documentum 6.5

SP2,

6.5 SP3,

6.6, 6.7

SPx, 7.0,

and

7.1

to Documentum

7.x.

opics T

in this chapter include:

•System

Upgrade

Strategies,

page

19

•Changes	that Impact Content Serv er Upgrade	or Migration,			page	22
•Mapping	Y our Current Configuration, page 23
•Designing	a Documentum 7.x Configuration,	page	26
•Planning	Upgrade and Migration to Documentum		7.x,	page	28
•Planning	Upgrade for Repositories in a Federation,		page 30

System

Upgrade Strategies

Documentum A system upgrade

inv olv es dev elopment,

test, and production phases.

•Dev elopment

— In this phase,

y ou

mov

e customizations

from an

old product

v

ersion

to

the

new

v ersion

and then

v erify that they still w

ork properly.

est •T this In —

phase,

y ou deploy and run the full

set

of

products

to emulate

the

production

system

as closely

as possible.This

is frequently done

on

virtual hosts.Once all

y

our system

tests

pass, ou y can

upgrade

the production system.

•Production

—

In

this

customizations.

phase,

y

ou

upgrade

the

existing

production

system

in

place

with

the

v

erified

Note:

The Content Serv er/database component

(the repository)

is the only part

of

the system

for

which

there is an upgrade script.All

other system product components require

fresh installation.

The upgrade strategy

provided in

this section addresses upgrading all products

in

the

system

to

the

same v

ersion number

, resulting in

a

homogeneous system.

Figure

3, page 21 shows the high-lev

el decision

points inv olv

ed

when moving

from a test system

to

a production system.Functional testing of new

customizations

and manual migration

of existing

customizations into

new client v ersion is

a part

of the dev elopment phase.

19

Planning

the

Documentum

System

Upgrade

on

If

y

which

ou

w

ant

to

y

ou

can

upgrade

the

the

repository

,

upgrade.The

create

a

Setting

copy

Up

run

of

the

a

T

est

Environment,

production

28

repository

page

section

y

in

our

test

system

provides

more information about creating

a repository copy.If

y

ou

w

ant to

change

the database

operating

system,

y

ou can use

the utilities av

ailable

through

the third-party database

to export

the

database

and

import

it

into

a new

database instance

on

the different

operating system.After running

the Content

configuration

Bluefish,

Serv

If

instance

Serv

er

and

and

the

new

y

ou

er

are

and

database

performing

FME,

a

program

fresh

database

which

y

to

run

reestablish

Content

the

connection

Serv

er

to

third-party

upgrade,

this

data

betw

een

the

upgrade

y

our

migrate

utilities,

migration.

existing

the

entire

data

such

as

files

Content

Serv

er

instance,

install

can

use

to

repository.

to

P

the

artners,

new

are

instead

of

sev

eral

an

Content

ou

instances.There

Crown

perform

An

EMC Documentum

system requires

a

global registry repository

that

matches the

v ersion family

of

the

system

clients.The

global registry is

a central location

used

to store

common objects used

by

all	repositories, such as SBO netw ork		locations, BOCS settings,			and	user settings.After installing or
upgrading		the test system repository	, install	a global registry repository that				matches the v ersion of
the	client applications, and install the		client	softw are.If y our client			softw are	v ersions are to remain	as
the	same v	ersion as y our production	system,	y ou can copy the		customized files from y our production
system directly ov er to the same ersion v client instance on the						test	system.If	the client ersion v
softw are different, is migrate our y			customizations		to the new	client	files.

After

migrating

to

the

test

system,

ensure

that

y

our

system

is

running

properly

by

conducting

system

tests.After

all

y our system

tests pass,

y ou

can upgrade

the production system.T ypically ,

y

our

production

system is

taken

offline

for

a w eekend

while

performing

an in–place upgrade.

virtual

Note:

Y

ou

can

use

ou

virtual

can

machines,

y

sw

machine

ap

hosts

for

the

entire

system

or

out

preupgraded

system

images

on

for

the

system

components.Using

physical

host

to

same

copied

The

minimize

or

the

downtime

system

migrated

y

of

an

new

in-place

upgrade.

content

the

new

and

production

y

ou

contains

our

data

full-text

to

repository.

indexes

generated

since

the

repository

20

w

as

Planning

the

Documentum

System

Upgrade

Figure

3.System

Upgrade

Scenarios

21

Planning

the

Documentum

System

Upgrade

or

Changes

that

Migration

Impact

This

section

describes

miscellaneous

changes

Content

that

can

affect

the

Server

Upgrade

migration

to

Content

Serv

er

7.x.

Linking to the				32-bit	Oracle Client Library on Linux
In Documentum 6.7, for Linux, the					w ay Content Serv	er links to the		Oracle Client library w as changed.
Prior	to	Documentum 6.7,		a static link to the 32-bit Oracle			Client	library w as used.From 6.7 onw	ards,
Content Serv er does not link with the					32-bit Oracle Client		library	at build time, but rather dynamically
links	to	it	at runtime.Consequently		, y ou must install	a 32-bit Oracle Client on the Content Serv			er
host,	and		add the directory	containing the client libraries			to the	appropriate environment v ariable

LD_LIBRARY_PATH (

for

Linux)

of

the

repository

owner

before

configuring

or

starting

Content

Serv

er.

In Documentum 7.1, all		the UNIX ports		of	Content	Serv	er are 64-bit.Therefore, the		32-bit	Oracle
client	libraries are not required and		the LD_LIBRARY_PATH environment					v ariable should		directly	be

set

to the 64-bit Oracle client libraries.

If

y ou are upgrading from

a Content

Serv

er

v

ersion

prior

to

Documentum 6.5

SP2,

the

earlier

v ersion of the repository

does not start when

Oracle

v ersion

is

upgraded to Oracle

11g

Release

2.Y

ou need to upgrade Content Serv

er

to

Documentum 6.7

to

perform any operations

with

the

repository before upgrade.

22

Planning

the

Documentum

System

Upgrade

and

If

ou

y

w

ant

are

to

upgrading

perform

any

from

Documentum

operations

with

6.5

SP2

or

6.5

SP3

or

the

repository

after

the

6.6

Oracle

or

6.7

v

or

ersion

to

7.0

upgrade

Documentum

7.x

to

Oracle

11g

Release

2,

the EMC

Documentum

Content

Server

Installation

Guide

for

instructions

on

configuring

the

repository

with Oracle.

Upgrading

Multiple

Repositories

to

the

Same

V

ersion

When upgrading

Content Serv

er

from 6.5

SP2

or later

to

7.x,

first

upgrade

the

softw

are

and then

the repository.

If Content

Serv

er

comprises

of

multiple repositories, ensure

that

y

ou upgrade

all repositories

to

7.x.Y ou

cannot hav

e multiple repositories

of

different

v

ersions

on

the

same W

indows host

since

different

method serv

er binaries

are

used for

different

v

ersions.If

y

ou

retain

a

repository at

a

6.5

SP2

v

ersion,

the

6.5

SP2

repository

uses

the

latest

7.x

method

serv

er

executable

to

launch

JMS

based

on the

registry entries

on the W indows

host.

It is recommended that

y ou upgrade

all

repositories

in

Content

Serv

er

to

the

same

v

ersion.

Mapping our Y Current Configuration

current

Complete

the

plan

which

documenting

The

T

time

following

y

to

ou

system

the

get

copy

v

(for

y

configuration

diagrams

our

and

sample

w

y

system.Y

ou

not,

be

ou

do

reflect

the

serv

er

,

full-text

host

indexing

may

orksheets

provide

hav

a

starting

copy

e

a

similar

of

point

for

infrastructure

much

of

this

information.If

current

of

already

to

keep

diagrams

the

existing

from

can

sure

help

one

system

to

with

T

erify

future

of

migrations.

that

able

2,

any

ake

existing

23

er

each

diagrams

current

and

client

serv

er

,

configuration.

configuration

Federated

Content

page

for

Serv

used

in

Serv

y

er

our

,

example,

Search

or application		serv er).
able T	2. Content		Server		and	Database Server		Host	W	orksheet
Item						alue V
Hardw areand
Processors
Memory
Operating system				and
v ersion
Content Serv		er	v ersion
RDBMS and		v ersion
Repository size						Number of objects:
						Storage space required:

23

Planning

the

Documentum

System

Upgrade

Global Registry?				[	]	Y es	[	]	No
Jav a/JRE	v ersion
DFC v ersion
Other product		v	ersion
Other product		v	ersion
Other product		v	ersion

able

T

3.Application

Server

Host

W

orksheet

Item						alue V
Hardw areand
processors
Memory
Operating			system		and
v	ersion
HTTP Serv			er	v ersion
Jav a		v ersion
DFC		v ersion
Otherproductand
v	ersion
Otherproductand
v	ersion
Otherproductand
v	ersion

able

T

4.Index

Server

Host

W

orksheet

Item						alue V
Hardw areand
processors
Memory
Operating			system		and
v	ersion
HTTP serv			er	v ersion
Jav a		v ersion
DFC		v ersion
Otherproductand
v	ersion

24

Planning

the

Documentum

System

Upgrade

Otherproductand
v	ersion
Otherproductand
v	ersion

able T		5.Client	Machine		orksheet W
Item					alue V
Operating system				and
v	ersion
Browser and			v ersion
Jav a		v ersion
Otherproductand
v	ersion
Otherproductand
v	ersion
Otherproductand
v	ersion

able

T

6.Customized

Components

W

orksheet

Product	Customized	Customization	Customization	Disposition
	Components	type	Description
				•6.5andlater
				Compatible
				•Needs	changes
				•Obsolete
				•6.5andlater
				Compatible
				•Needs	changes
				•Obsolete
				•6.5andlater
				Compatible
				•Needs	changes
				•Obsolete

25

Planning

the

Documentum

System

Upgrade

Designing

Documentum a

7.x

Configuration

performance

containing

RDBMS,

and

Documentum

This

section

discusses

7.x

global

multiple

in

high

some

of

the

design

data

decisions

y

ou

systems

the

same

host

repositories,

dispersed

machine.

are

must

make

before

implementing

a

where

to

are

Content

Serv

systems

services

improv

er

,

configuration.

registry

all

Content

traffic

on

Departmental

configurations

Enterprise

distributed

reside

Serv

or

ers,

configurations

e

and

geographically

environments.

Addressing

erify

V

that

the

hardw

Hardware

Concerns

are

y

ou

are

currently

using

will

continue

to

meet

y

our

needs

for

the

foreseeable

future.In particular

,

if y

ou hav

e been hosting more

than

one serv er

on a single

machine (for example,

Content Serv

er

and

an application serv

er), this

is

a

good

time

to

divide the functions betw een

tw

o

or

more serv

er hosts

to boost performance.When upgrading

to

Documentum

7.x, ensure that

at

least

10

GB of memory

is

av ailable.

Y ou

can

also make

an estimation

on

the

required

memory

by

calculating

the

memory

consumption

of

each

of

the

Documentum executables.The

following

table

lists

the

memory

consumption

for

each

executable

of Documentum

based

on

their

count.

able

T

7.

Memory

Consumption

by

Documentum

Executables

Documentum executable				name	Count	Memory consumption (MB)
DMBASICmethodserv			er		1	1
(Master)
Agent					5	2560
						Note:	Each	agent requires	512	MB
						of memory.
Jav	a Method Serv	er			1	1300
Agent executable					1	512
Documentum.exe					1	X
otal T					9	4.373	GB

Note: The table

lists

the memory

consumption for

a single

docbase

if

the database is installed

in

another machine.If

y ou hav

e multiple docbases,

multiply

the

total

memory

with the number

of

docbases.For example, if

y ou hav

e

tw o docbases,

the

total

memory

required

w ould be

8.6

GB

(that

is,

2

X

4.3).The

memory

consumptions

v

alues

are

deriv

ed

or

obtained

after

testing

the

product

in

the

EMC testing environment.Ev ery

effort

is made

to simulate

common

customer usage scenarios

but

actual results may

v

ary

due to differences

in hardw

are

and

softw

are

configurations, data,

and

other

ariables. v

26

Planning

the Documentum

System

Upgrade

Upgrading Third-party

Software

erify V

that

the

third-party softw are, such

as operating system,

database,

and so

on,

y

ou

are currently

using

with

the

existing v ersion is still supported,

or upgrade to

the supported

v ersions

as necessary.

If

the

third-party component

does

not hav

e

a direct

upgrade path

to

the supported

v ersion, then

there

is

no

direct upgrade

path

for

the Content

Serv

er upgrade.The EMC

Documentum

Envir onment and

System

Requir

ements

Guide

provides

Planning

for

Global

which

Designate

of

y

our

one

of

the

use

repositories

repositories

to

as

in

information

about

supported

third-party

softw

are

v

ersion.

Registries

our

the

y

v

ersion

global

6.5

or

later

system

as

ou

already

hav

the

global

r

egistry

.Decide

5.3

registry.If

y

e

a

Documentum

SP6,

6.0,	or SPx 6.0 global registry		, upgrade to Documentum 7.x.
During repository configuration,				y ou are prompted with the message		Do you want		to	add	this
repository to another		global	repository .Y		ou can select one of the following options:
•Y es
Provide the repository name and the login credentials (user login						name and	passw		ord)	of	the
global registry user		in that repository.The DFC instance on the				current host	is configured				to
access the remote		global	registry repository.

•No

Provide

a

user

login

name

and

passw

ord

for

the

global

registry

user

in

the

repository

y

ou

are

currently configuring.Record the login name						and passw ord;		use this login name	and passw	ord	to
configure other repositories			in	y our system	to	allow them	to access the global registry.The			local
DFC instance	is	also configured		to access this		global registry.

is

Regardless

of

for

created

whether

y

ou

designate

the

all

repositories.The

global

repository

as

registry

user

(

dm_bof_registry),

a

global

registry

or

not,

is

the

the

global

registry

user

whose

user

repository

account

DFC clients use to connect to

the

repository to access

required service-based

objects and

user

information.The user has read access

to objects in /System/Modules only.

•If

y

ou configure the repository as

a global

registry

, provide the user login name and passw

ord

for

the user and set the user state

to Active

.

This

can be any arbitrary user login name

and passw

ord.Do not use

the credentials

of the

repository or installation owners.

•If

y

ou do not configure the repository

as

a

global

registry

, the user is

created with

a default

v alue

for

the login name, and the user

state

is

set

to Inactive

.

If

y

ou

later

enable

the

repository

as

a

global

registry

,

use

Documentum

Administrator

to

change

the

user state

to Active

and provide

the

user with

a

user

login

name

and

passw

ord that

y

ou

choose.The EMC Documentum Content Server Installation

Guide

provides instructions

on

enabling

the

repository

as

a

global

registry.

27

Planning

the

Documentum

System

Upgrade

Mapping

page

forms

For

each

serv

er

for

used

23

).

host

a

Documentum

y

client

our

configuration,

current

7.x

Configuration

a

Mapping

planning

our

mapping

and

complete

(see

Y

document.Y

ou

can

use

the

same

configuration

Current

Configuration,

Documentum

Planning

Upgrade

7.x

and

Migration

to

6.5

minimize

The

migration

Now

that

y

paths

path.The

know

ou

recommended

y

our

starting

point

and

y

allow

is

our

destination,

y

a

get

y

ou

can

choose

the

6.5

best

and

later

upgrade

system.

and

configuration

in

this

section

but

y

our

users

migration

is

our

homogeneous

Documentum

to

continue

w

of

features

or

migration

or

described

until

our

y

the

users,

applications

the

full

orking

in

impact

on

cannot

benefits

Documentum

later

v

ersions

complete.

Setting

Up

a

T

est

Environment

migration

up

configurations

environment.Set

Before

a

migrating

test

as

y

our

production

system,

that

system,

includes

EMC

Documentum

the

a

same

copy

y

y

are,

recommends

RDBMS,

that

y

ou

and

set

softw

up

are

a

test

up

an

environment

y

our

production

allows

before

y

ou

to

hardw

of

our

systems,

including

production

as

w

ell

repository.Setting

as

troubleshoot

any

environment

problems,

practice

migrating

to

y

our

our

committing

changes

production

system.

Creating

the

T

est

Environment

Y ou cannot create copies

of more than

one repository

in

a

single

new installation

if

the

repositories

w ere created

in different

installations.

Use the instructions

for creating a repository

copy

on

the

same platform

as

the original

repository.

Before

The

procedure

is

not

supported

repository

,

for

create

moving

an

a

repository

in

upgrading

a

environment

which

from

to

one

test

platform

to

another.

the

upgrade

process.T

o

do

this,

create

a new installation

using

the

original

Content Serv

er

softw

are

v

ersion,

copy

the repository ,

copy

the content files,

and upgrade

that

copy.P

erform tests

on

the copy ensuring

to exercise standard

For

repository.

functionality

example,

and

customizations.After

the

upgraded

copy

if

y

ou

are

copying

tw

o

repositories,

P

aris

and

is

tested

London,

completely

,

upgrade

that

w

ere

created

in

the

original

separate

Content Serv er

installations,

ou y need to

copy them to separate Content Serv

er installations.Creating

a

repository copy requires y

ou to copy the aek.key and dbpasswd.txt files from the original

repository host

to the

repository copy host, because each repository copy must hav

e access

to

the

aek.key and

dbpasswd.txt files

from

its original installation.

If

y ou are copying

tw

o repositories,

oky T

o and Beijing, that

w ere created in

the same Content

Serv

er installation,

y ou can

create their copies in

the same new installation,

with the

aek.key

and

28

Planning the Documentum

System Upgrade

dbpasswd.txt files from

the original installation

copied

to the installation where

y ou

create the

copies.

The

Method 2:Copying a

Repository

, page

83

section in the Chapter

5, Migrating Content Serv er

chapter provides the steps

for copying repository. a

Migrating TCS-Enabled a

Docbase

to New a

Server

T o migrate content following steps: from an

encrypted store

in

a

source repository

to target a repository

, perform

the

1.Copy the content from

an encrypted store

to

a

non-encrypted

store on the source repository.

2.Copy the repository.The Method 2:Copying

a Repository

, page

83 section

in the Chapter 5,

Migrating

Content

Serv

er

chapter

provides

the

steps

for

copying

a

repository.

3.Create

a

new

encrypted

store

to

store

the

in

the

target

repository

encrypted

and

store

migrate

in

the

target

the

non-encrypted

newly

created

content

from

repository.

the

Client-First

Migration

the

If

y

our

system

uses

only

DFS,

custom

to

the

DFC,

or

or

custom

client

applications

first.Refer

installation

deployment

WDK

clients,

y

ou

for

hav

guide

e

the

the

option

client

of

for

migrating

application

detailed instructions.
ACS and BOCS		ersion V		Compatibility and Migration—P arallel			streaming from Accelerated
Content Serv	er (ACS)		is used only		if both ACS	and Unified Client Facilities (UCF) (WDK		or	DFS
applications)	are	v ersion		6.5 or later.P arallel streaming from Branch			Office Caching Services		(BOCS)

used

BOCS

the

Note:

is

only

When

y

if

ACS,

ou

6.7,

registry

BOCS,

and

the

the

v

UCF

are

v

ersion

ersion

6.5

as

2.1.For

6.5

or

later.

or

later

7.0,

using

upgrade

Documentum

to

BOCS

ersion

Administrator.For

v

,

update

BOCS

specify

the

6.0,

the

v

ersion

specify

BOCS

global

6.5

to

specify

BOCS

v

ersion

specification

in

the

v

ersion

as

2.0.For

as

2.3.

WDK

Clients

Compatibility

and

Migration—WDK-based

clients

are

compatible

with

Documentum

5.3 SP6 and

6.0 Content Serv ers.Based

on

the

v ersion to which

y ou

hav

e

migrated,

some

WDK features of that

v ersion

are

av ailable,

such

as

features that run

in Jav aScript

on

the

client.

Other

features

are not

av ailable until

y

ou complete

the migration

to

Documentum

6.5

or

later ,

such

as

lightw

eight system objects, data partitioning,

batch

processing, and

scoping.

Documentum

The

following

6.5

procedures

or

later

,

migrating

describe

the

steps

the

to

clients

migrate

first.

from

Documentum

5.3

SP6,

6.0,

or

6.0

SPx

T

o

migrate

from

Documentum

serv

in

a

er

v

and

5.3

client

SP6,

6.0,

or

6.0

2.Enable

1.Upgrade

the

application

the

global

registry

browsers.

in

ersion

6

repository

SPx

to

order

to

Documentum

support

v

ersion

7.x:

6

client

Documentum

provides

features

that

require

a

global

for

global

global

registry.The

repository.Documentum

EMC

Documentum

Content

instructions

5.3

SP6

enabling

a

registry

are

not

supported.

Server

6.5

or

clients

Installation

later

with

Guide

a

to

29

Planning

the

Documentum

System

Upgrade

5.Configure

4.Restart

3.Upgrade

the

Content

Content

er.

Serv

ersion

6.0,

y

Serv

ers

Serv

ou

can

er

in

place.

as

the

upgrade

Content

in

v

one

v

ersion

that

registry

6.5

er

or

serv

in

later

global

registry.If

y

the

same

ou

had

place

using

settings.

a

global

Federation

Planning

Upgrade

for

Repositories

in

a

users,

A

Federation

is

groups,

and

tw

o

or

more

repositories

lists

(ACLs)

that

access

control

in

are

bound

together

to

a

multi-repository

facilitate

management

of

global

distributed

configuration.One

repository	in the	set	is	the	gov	erning repository.The	remaining repositories are member repositories.
Keeping objects synchronized						in multiple repositories	can	be time consuming and error-prone	when

the w ork is done manually

in

each repository.A repository

federation automates

much

of

the

process.

Only certain combinations

of

different

repository v ersions can

w

ork together

as

a Federation.Plan

y our upgrade

so that all participating repositories are

supported.

When

y ou upgrade repositories (that w

ork together as

a Federation), ensure

that the upgraded

repository v ersions (in

a nonhomogeneous Federation)

can

w ork

together

as

a Federation.

The EMC Documentum

Content Server Distributed Configuration

Guide provides more information

about

configuration requirements in Federation. a

Guidelines

for

Upgrading

Distributed a

Configuration

Use

these

guidelines

when

deciding

how

to

upgrade

a

distributed

configuration.

different

Repository

Federations—EMC

v

ersions.In

a

mixed

v

Documentum

supports

federations

the

gov

erning

that

contain

repositories

first.

ersion

environment,

upgrade

repository

of

upgrade

If

Repositories

a

y

ou

hav

e

can

with

group

begin

Object

with

of

Replication—Upgrade

where

each

the

is

source

repository

,

both

a

source

can

apply

,

for

and

then

the

target

repositories.

if

then

the

objects

are

repositories

any

of

the

repository

a

target,

repositories.This

situation

example,

replicated

from repository A

to repository

B, repository

B

to repository

C,

and from repository

C

to

repository

A. Although

y ou can

replicate betw

een repositories

that

are

different

v ersions, attributes

that

are

only

in

the

new

er

v

ersion

cannot

be

replicated.

Repositories with Distributed				or Load-Balanced Content—Shut down				the primary		Content
Serv	er	and all remote	Content	Serv	ers.Upgrade the	primary Content	Serv	er first,	then	upgrade

the

remote Content

Serv

ers.

The

Upgrading Content

Serv

er

in

a

Distributed

or

Load-Balanced

Configuration,

page

45

section

provides

30

the

steps

for

upgrading

Content

Serv

er

in

a

distributed

or

load-balanced

configuration.

Planning

the

Documentum

System

Upgrade

Planning

the

Upgrade

or

Migration

of

the

AEK

Key

to Lockbox

From

the

7.2 release,

y

ou

can upgrade

the

AEK

key

to

a stronger algorithm during

the repository

upgrade

as follows:

•By

choosing stronger algorithm

for

the

AEK

key:Y ou

can upgrade

the AEK

key

algorithm

to

AES

128/192/256

algorithm.The

Post-Migration

asks

T

section

of

Migrating

Content

Serv

er

6.5

SP2

to

7.2

—

W indows/SQL Serv er

, page 105 contain the procedure for this process.

•By

enabling lockbox

for

the

AEK key:Y

ou can

mov

e an existing AEK key to

lockbox or

create

a

new

upgraded AEK

key

in

the lockbox.The

Post-Migration asks T section of

Migrating Content

Serv

er 6.5 SP2 to 7.2

— W indows/SQL

Serv er

, page 105 contain the procedure

for this process.

Note: During the upgrade process,

use

the same passphrase for

the

new

AEK key.After

the

upgrade

is complete,

change

the passphrase.Use dm_crypto_change_passphrase

to

change

the

passphrase and then

run the

dm_crypto_boot utility

with the

new

passphrase.

For example:

dm_crypto_change_passphrase-keynameCSaek[-lockboxlockbox.lb-lockboxpassphrase

<lockboxpassphrase>]-passphrasegenuine-newpassphraseglorious

Caution:

If

y

ou

select

the

Upgrade

AEK

key

option,

it

results

in

changing

the

AEK

key

and re-encrypting

the

repository

keys

and

other related

data

such as CNT files.Hence,

it

is

recommended

to take

a

backup of

the AEK

key and

CNT

files

before the upgrading

the AEK

key.

The EMC Documentum Content Server Installation Guide						contains detailed information		about	creating
strong AEK/lockbox options.
Enabling Remote Key Management
From Release	7.2 onw ards,	y	ou	can enable Remote	Key	Management (RKM)	for supported		upgrades

during

upgrade

or

post

upgrade.

Once y

ou enable RKM, the

Docbase Key (DBK), Login Ticket

Key

(L TK), File

Store

Key (FSK),

and

Priv

ate/Public Key (PPK) retain

the

same v

alue as

that before

upgrade, ev en if

y

ou upgrade the

AEK

key

algorithm.In the RKM

serv

er ,

the key

classes

need

to

be created with the

same

algorithm that

w

as

used

for

these

keys

before

upgrade.Only

the

v

alue

of

the

AEK

key

is

changed.

For	migration,	it	is recommended		that	y	ou enable remote	key management		after migration.
The	EMC Documentum			Content Server Installation Guide contains					detailed information		about

configuring

the

remote

key

management.

31

Planning	the	Documentum	System	Upgrade
32

Chapter

3

Upgrading

Content

Server

	This chapter describes how	to upgrade	from	a previous		release	and how	to upgrade		repositories
to	Content Serv er 7.x.Alw	ays consider	upgrading		one Documentum product				within	the	context
of	upgrading the entire Documentum		system.

Note:

Y

ou

cannot

upgrade

to

Content

Serv

er

7.x

from

a

v

ersion

earlier

than

6.5

SP2.If

y

our

current

installation is

an earlier

v ersion,

upgrade it to

Content

Serv

er

6.5 SP2

or

later before

y

ou

upgrade

to 7.x.

This chapter contains the following topics:

•Upgrade Checklist,

page 33

•Upgrading

to 64-bit

Content

Serv

er ,

page 37

•Upgrading

the Content Serv er Softw are, page

40

•Upgrading

Content

Serv er Installed

with Cluster Services,

page 44

•Upgrading

Content

Serv er in

a Distributed

or Load-Balanced Configuration, page

45

•P ost-Upgrade asks, T

page 48

Each

step

in

the

upgrade

process

must

be

to

a

platform

that

is

fully

supported

by

Documentum.

Depending on

the Content

Serv

er release

from

which

y

ou

are upgrading,

y

ou may

need

to

upgrade

the operating

system

or database.The documentation

provided

by

the operating system

or

database

v endor

contains information

on upgrading those

components

of

the

system.After

each

upgrade

step,

test

the

repository

to

ensure

that

all functions

are

normal.

upgrade Note: W		indows y our operating Serv er 2003 is not to system supported environment a supported environment a for Content upgrading Serv er 7.x.Y ou Content before Serv								must er.
	Caution: After			upgrading,		y ou cannot rev	ert	to previous	v ersions of Content Serv er.

Upgrade

Checklist

P

erform

the

following tasks

for upgrading

Content Serv

er:

1.Review

the

EMC

Documentum

Content

Server

Release

Notes.

2.Review

the

EMC

Documentum

Content

Server

Installation

Guide

.

33

Upgrading

Content

Server

3.If

y ou

are installing

the

xPlore indexing serv er

,

review the

EMC

Documentum

xPlor

e Installation

Guide

.

4.Review the Upgrading

to 64-bit Content Serv

er

,

page 37 section

on

what sequence

to

use

in

upgrading

y our installation, especially

if

y

ou

are

upgrading

from

a 32-bit

to

a 64-bit

Content

Serv er.

5.Back up the repository.For the steps, refer

to

the

EMC Documentum Content Server Administration

and Configuration Guide

.

6.Optionally

, y

ou can take

a backup of all

users

that

are

part of

the Admin

gr oup

and any

customized

attribute

like

group_address.

7.Decide whether to enable

extended services,

such as:

•Retention P		olicy	Services
•T rusted	Content		Services
•Content Services			for	EMC	Centera
•Content Storage			Services
•Records Manager

The

“Content

Serv

er

optional

modules”

section

in

the

EMC

Documentum

Content

Server

Installation

Guide provides more information.
8.T emporarily increase			the amount		of rollback	space	av ailable in the RDBMS. The number		of
rollback	segments should be			commensurate		with	the size of the repository and should be		in
segments	of equal size.Refer			to the database		documentation for the		steps.
9.Ensure that y ou hav		e	sufficient disk space on			the computer hosting the		database.
10.Run the	repository	consistency checker script				and	correct any errors	y ou find.The EMC
Documentum Administrator User Guide and Chapter							3, Upgrading Content Serv er provides		the
steps for	running the		consistency		checker.

11.Ensure

that

the dm_server_config

object

is

unlocked.The

Ensuring

that

the

dm_serv

er_config

Object

is Unlocked,

page

37

provides

more

information.

14.Shut

13.Close

12.Shut

down

the

down

the

repository

and

Serv

er

all

Manager

serv

ers

Documentum

any

local

connection

brokers.

34

running

against

User

Interface.

the

repository.

Upgrading

Content

Server

15.On

Linux/Solaris/AIX:

b.Modify

a.Set

the

$DOCUMENTUM

the

$DM_HOME

v

environment

ariable

in

the

v

7.x

.The

ariable

same

as

that

in

the

.cshrc

Content

base

or

v

Installation

to

ersion.

installation

EMC

owner

’

s

.profile

file

$DOCUMENTUM/product/

Documentum

Server

Guide

point

to

provides more

information.

c.Set

the $DOCUMENTUM_SHARED

environment

v

ariable

same

as

that

in

the

base

v

ersion.Do

not

delete

this

environment

v ariable.

d.Modify

the

library path

v ariable

in

the installation owner

’ s

.cshrc

or

.profile file

to point

to

the

location

of

the shared libraries required

by

the serv er.The

EMC

Documentum Content Server

Installation

Guide provides more

information.

e.If

y

ou

are using Oracle

as the database, modify the

$ORACLE_HOME environment

v ariable

to

point

to the 64-bit libraries.

f.Determine the root passw ord.This

is the operating

system

root passw

ord.The root passw

ord

is

required to complete

the upgrade.Refer

to the Linux/Solaris/AIX

documentation

for

more

information.

16.Determine

Server

the

Guide

installation

owner

,

and

the

username

and

passw

ord.Refer

Installation

consult

database

administrator.

to

the

EMC

Documentum

Content

17.Determine

the

names of

the

repositories

y ou

are upgrading.

18.Determine

the

Content Serv

er

v

ersion from which

y

ou

are

upgrading.

the

7.x,

C:\ProgramFiles\Documentum

directory

by

Note:

the

environment

the

In

a

fresh

installation

Documentum

.In

v

v

y

directories

installation

of

7.x,

all

example,

are

files

of

installed

in

in

a

fresh

a

installation,

single

the

directory

as

defined

as

%DOCUMENTUM%

is

existing

Documentum

ariable.For

.When

earlier

are

w

default

C:\Documentum

installation

7.x

ersions

ou

Documentum,

the

the

new

older

v

64-bit

Jav

ersions

the

default

directory

retained.Only

upgrade

of

Documentum

to

a

files

are

installed

in

the

new

directory.

Changing

the

Database

Operating

System

and

V

ersion

Content

database

When

migrating

y

migration

Serv

er

our

first

database

before

to

a

new

Content

operating

the

Serv

system

er.After

(host)

with

migrating

and

database

the

v

the

new

ersion,

complete

run

the

upgrading

program

to

database,

database

instance.

the

configuration

reestablish

repository

Then

upgrade Content

Serv er

to

upgrade

the

entire repository.

Refer

to

the database

v endor documentation

for information

on

migrating

the

repository

database

files	to	a	new	database instance.The Content			Serv	er	configuration program connects	Content
Serv	er	to	the	new database	host, unless	the database			connection string, database owner	name,	or

passw

ord has changed.

Note:

While upgrading

the

W indows

operating system,

the

\etc\services file

is replaced

as

a part

of the upgrade.Because of this,

the entries

that

w

ere

added for

the

repository

before the

upgrade is lost.After upgrading the operating system,

manually add

the

repository service entries

to

the

\etc\services

file.

35

Upgrading

Content

Server

Preparing

T

an

Prior

to

upgrading

page

8K

o

create

Content

DB2

databases

Serv

er

on

AIX

with

a

tablespace,

all

tables

run

into

the

the

for

DB2

new

Upgrade

database,

create

tablespace.

command:

size.Then,

an

8K

backup

temporary

following

a

temporary

tablespace

with

db2CREATETEMPORARYTABLESPACETEMPSPACE2PAGESIZE=8192

Migrating

the

Database

to

UTF-8

EMC

the

Serv

the

If

do

database

w

as

installed

not

functions

to

hav

e

supports

with

a

of

migrate

code

the

page

migrate

to

other

than

the

UTF-8

by

to

UTF-8

under

to

a

previous

UTF-8.

Content

Serv

existing

database

ersion

er.How

v

code

ev

of

to

Content

er

multilingual

ou

er

,

y

database

Serv

er

,

upgrade

,

use

Content

database

using

the

Documentum

upgrading

repositories

page.

•On Oracle,

y

ou

can migrate existing

repositories

to Unicode

using

the

tools

provided

by

Oracle.

Contact Oracle

for any support

y

ou

require

in migrating

the

database.

•On

DB2,

all repositories should hav

e

been created

by using Unicode.They

do

not need

to

be

migrated.If

the

DB2

repository does

not use Unicode, migrate

the

database

by

using IBM

tools.

Contact IBM

for

any

support y ou require.

•On

Microsoft

SQL

Serv

er

,

y

ou

cannot

migrate

the

database

to

Unicode.

The

database_refresh_interval

Key

the

default.The

During

that

Content

key

Serv

installation

1

updates

er

minute

type

or

or

it

caches

delete

upgrade,

from

as

the

change

are

checker

or

process

runs

process

is

set

to

types

the

server.ini

created

altered.Before

file.

once

per

minute

by

y

ou

upgrade,

ensure

Upgrading

Ensuring

the

Completion

If

y

ou

are

using

a

repository

of

Documentum

of

Automatic

6.5

or

earlier

,

ensure

that

asks

T

Before

all

automatic

tasks

are

completed before			shutting	down	the repository for upgrade;	otherwise, unfinished automatic				tasks
will	fail.
Use	the	following	Documentum		Query Language (DQL) query	to obtain	the number	of	activ	e
automatic tasks in			the repository:

r_runtime_statein(0,1)

r_auto_method_id>'0000000000000000'and

selectcount(r_object_id)fromdmi_workitemwhere

If the query returns

a nonzero

v alue,

activ

e

automatic tasks still must

be processed and y

ou must

w

ait

for them to complete.If

it returns

0,

the repository

contains no more activ

e automatic tasks, and

y ou

can safely stop

the repository.If the

query

returns

0, run the query

a

few

more times to

ensure that

no new automatic tasks

are being

generated.

36

Upgrading

Content

Server

Ensuring

If

y

ou

attempt

to

that

upgrade

the

dm_server_config

Object

Content

Serv

er

and

the

dm_server_config

object

is

Unlocked

is

locked,

the

upgrade

may fail.T

o check

if the

object

is locked,

log

in

to

y our

database

as the

database

owner

and

use

the

following

SQL query

to

get

the

object

ID

of the

serv

er configuration object:

SQL>selectr_object_idfromdm_server_config_s

Use

the

object

ID

in

the

following

query

to

v

erify

whether

the

configuration

is

locked:

wherer_object_id='<objectID>'

SQL>selectr_object_id,r_lock_ownerfromdm_sysobject_s

T

If

there

is

o

unlock

a

lock

owner

,

then

the

object,

use

the

following

object

the

SQL

is

locked.

(except

for

Oracle):

setr_lock_date=''wherer_object_id='<objectID>'

SQL>updatedm_sysobject_ssetr_lock_owner=''setr_lock_machine=''

For

Oracle,

use:

setr_lock_date=nullwherer_object_id='<objectID>'

Oracle>updatedm_sysobject_ssetr_lock_owner=''setr_lock_machine=''

Commit

the

change:

SQL>commit

Finally

,

restart

the

repository.

Upgrading

to

64-bit

Content

Server

Upgrading

to

the 64-bit Content

Serv

er

is supported only

if

there is an upgrade

path

on the

underlying

operating system

and

RDBMS.

For example, upgrading the 32-bit Content

Serv

er

on

32-bit

W indows Serv

er 2008

to the 64-bit Content Serv

er

is

not

supported

because there is

no

supported

upgrade path

from 32-bit

W indows Serv

er 2008

to

64-bit

W indows

Serv

er

2008.

If y

our operating system and database

meet

the

requirements specified

in

the EMC

Documentum

system

SP2

Envir

onment

or

later

must

and

System

64-bit.

to

Requir

64-bit

Content

ements

Serv

Guide

,

y

er

7.x.For

ou

can

directly

this

upgrade

from

the

32-bit

Content

Serv

er

6.5

operating

directly

be

upgrade

path,

underlying

Use

the

following

approach

to

upgrade

from

32-bit

Content

Serv

er

6.5

SP2

or

later

to

64-bit

Content

Serv

er 7.x:

1.Upgrade

the

operating

system

to the supported

v

ersion,

if

necessary.

2.Upgrade

the

database,

if necessary.

3.P

erform

one

of

the following steps depending on

the type

of

database

being

used:

•SQL

Server :Upgrade

or

install

a

64-bit

v ersion of the database client on the Content Serv

er

host

machine.When

y

ou

install

the 64-bit database client,

copy the

DSNs from

the

32-bit

ODBC driv er

to

the 64-bit driv er

if used

by

y our database.When

y ou redefine

the

DSN,

37

Upgrading

Content

Server

•Oracle

and

use

the

same

:Create

64-bit

and

database

from

ou

upgrade

lev

el

later

or

page

.

lev

38

el

ORACLE_HOME

of

client

library.For

more

information,

in

W

the

32-bit

indows

that

Content

errors

the

upgrade

see

64-bit

to

ODBC

the

file

DSN

the

of

the

64-bit

see

the

that

er

y

Libraries,

an

environment

v

the

entries

or

later

to

ariable

from

64-bit

logs,

points

location

into

TNSNAMES.ORA

errors

er

file.

Serv

file.Copy

to

6.5

SP2

client

in

is

the

64-bit,

Content

ou

must

replace

TNSNAMES.ORA

be

combination

er

Serv

can

7.x.

of

a

ignored.

plug-ins

the

TNSNAMES.ORA

32-bit

Content

connection

a

64-bit

from

hav

e

Serv

Y

4.Upgrade

ou

may

repository

not

since

32-bit

plug-ins

During

Content

database

supported.These

the

Serv

er

,

y

ou

32-bit

cannot

installed.Y

32-bit

authentication

with

the

authentication

64-bit

plug-ins.Y ou can find the plug-ins in the		%DM_HOME%\install\external_apps\authplugins
folder.
•Do	not probe log files before the entire	upgrade is		completed.P artial upgrade			is not supported.
Upgrade the binaries, the connection		broker	, and the repositories			at the same	time.
•For	operating systems that do not support IPv6 in			v ersions prior		to Documentum 6.5, upgrade		the
operating system first.For example, in		the case of		Red	Hat Linux,	y ou must upgrade the operating

system

first

if

it

did

not

support

IPv6

in

v

ersions

prior

to

Documentum

6.5.

•If the	32-bit Content Serv er			is	installed	on a 32-bit operating system, migrate the	repository			to the
64-bit	v ersion of	the operating			system	and then upgrade the Content Serv er.If the	64-bit		v ersion		of
the operating system			is not	supported,		y ou must upgrade the operating system	to	the supported
ersion v before upgrading the					Content	Serv er.

•If

y

ou

the

are

migrating

y

the

migration

Content

then

upgrade

Serv

er

our

database

to

a

new

program

er

to

operating

the

er.After

system

completing

and

database

the

v

with

ersion,

y

ou

database

the

new

must

instance;

run

perform

before

upgrading

Serv

to

Content

entire

reestablish

Serv

database

migration,

Content

configuration

the

repository

upgrade

repository.

Figure

4.

Upgrade

Steps

from

32-bit

Content

Server

to

64-bit

Content

Server

64-bit

ODBC

and DSN

Libraries

64-bit Content Serv

er requires 64-bit database

client libraries

for

the

Oracle database or Microsoft

SQL

Serv er.For

the Oracle database, update

the ORACLE_HOME

v

ariable

to the 64-bit installed

path, and

tnsnames.ora should

take the appropriate entries.For Microsoft SQL Serv

er ,

update the

DSN entry

from

38

32-bit

to

64-bit

and

v

erify

that

DSN

is

pointing

to

the

64-bit

SQL

libraries.

Upgrading

Content

Server

o

migrate

1.Run

the

64-bit

2.Note

T

the

ODBC

Serv

er

and

ODBC

DSN

follow

DSN

libraries

these

from

steps:

v

ersions

to

the

for

32-bit

Content

Serv

er

and

to

v

ersions

for

Content

the

32-bit

the

.The

ODBC

,

utility.Browse

Data

Source

are

C:\Windows\SysWOW64

dialog

box

DSNs

present

double-click

operating

odbcad32.exe

down

all

32-bit

Administrator

opens.

in

32-bit

DSN

entries.These

system

registry.

3.Run

the

64-bit

ODBC

DSN

utility.Browse

to

C:\Windows\System32

and

double-click

odbcad32.exe

the

ODBC

Data

.

4.In

Source

DSN

entries

ensuring

that

Administrator

the

same

v

alues

dialog

are

box,

as

in

on

used

step

the

System

2

and

DSN

click

tab,

OK

.

add

the

32-bit

Errors

During

Upgrade

If

y

ou upgrade from

32-bit

Content

Serv er 6.5 SP2

or

later to

64-bit

Content

Serv

er

7.x

using

the

errors.During second approach the described upgrade,

in at

Upgrading an to 64-bit stage Content where, for Serv intermediate

er , page 37 , y example, the

ou might encounter 64-bit database client

libraries

are installed with 32-bit Content Serv

er and

a 64-bit RDBMS

is running,

the system

will

be

in

an unstable ou state.Y can expect

to see errors

if any

of these systems

are running.V alidation

of

features

or functionality during

this intermediate

step

is

not

permitted.Continue

with

the

upgrade

and

run

the 64-bit Content

Serv

er installer

before

testing

the

system.

For

example,

if

y ou

are migrating from

6.5

SP2

to

64-bit Content Serv

er

6.7,

y

ou might

see

docbasic

connection errors	during the intermediate step of installing						32-bit Content Serv er 6.7.These	errors	are
expected.
When upgrading	a repository from	32-bit to			64-bit,	Content	Serv er automatically recompiles	the
docbasic expressions during their		execution.This recompilation occurs because the underlying
library changes	from 32-bit to 64-bit.
This recompilation process can increase				the execution time			of the method, which contains	these
expressions.If	a v ery small method	timeout			v alue	w as specified, the operation can result in		a
METHOD_TIMEOUT error.How ev		er	, the method			continues	running ev en after the timeout	error	is
reported.
Therefore, when	upgrading a repository			, w atch out		for	these timeout errors and ensure the	proper
state of the method before retrying		the operation.
Components Not Supported						after	Upgrade
F AST w as the	default search engine	prior to			the Documentum 6.6 Content Serv er.F AST is not
supported on	the 64-bit Content Serv er.At minimum, a disable the AST F component on the							64-bit
Content Serv er.It is recommended		that		y ou	uninstall the		F AST component during migration	from
32-bit Content	Serv er to 6.7 64-bit	Content Serv er 6.7.Documentum 7.x uses the xPlore search
engine.The EMC	Documentum xPlor	e Installation Guide provides information about migrating						F AST
data to xPlore.

39

Upgrading

Content

Server

Migrating

Custom

support

Migrate

32-bit

all

32-bit

custom

plug-ins

custom

plug-ins.

Plug-ins

to

the

64-bit

architecture.The

Systems

Upgrading

Content

Server

on

Red

64-bit

Hat

Content

Serv

er

does

Linux

5.x

not

Red

Hat Linux does not support

upgrading the operating system

from Linux

5.x

to 6.x.If

y

ou

w

ant

to

upgrade Content Serv

er

6.7

or earlier running on

a Red Hat Linux

5.x system

to

Content

Serv

er

7.x

that

runs

on Red Hat

Linux

6.x,

y

ou must follow

the migration procedure described

in Chapter

5,

Migrating

Content

Serv

Upgrading

er

.

the

Content

Server

Software

The length

of time

required

to

upgrade

a repository

depends

on

the

size

of

the

repository.Allow

sufficient time

for

backing up

the repository

and performing

the

upgrade.

T

o

upgrade

the

Content

Server

software:

2.If

1.Back

the

up

the

repository.Sev

contains

eral

third-party

repository

tools

repository

customized

formats

are

av

ailable

that

y

ou

can

use.

(dm_format

objects),

back

up

the

customized	formats.
Repository	formats	are	upgraded	by	the	dm_apply_formats.ebs	script,	which	reads	v	alues

from

the

formats.csv

file.If

the

attributes

of

a

format

in

the

repository

do

not

match

the

format descriptions in		the formats.csv file,	the	script ov erwrites	the existing v		alues with
the v alues in	the file.
3.Run the Consistency Checker tool.
Consistency	Checker is	a script that looks for	repository inconsistencies,			such as	users with
nonexistent	groups, permissions sets with nonexistent users, and				sysobjects that		point to
nonexistent	content files.Fixing inconsistencies		in	the repository improv		es the quality of		the	data
in the repository and results in a smoother upgrade.The syntax is:

superuserpassword

dmbasic-fconsistency_checker.ebs-eEntry_Point--repository_name

•r

epository_name

is

the

name

of

the

repository

against

which

y

ou

are

running

the

Consistency

Checker tool.

•superuser is

the username of

a repository superuser.

•password is

the passw

ord for

the superuser

’ s

account.

The

results of

the Consistency Checker

tool are

directed

to standard output.

4.Fix

the inconsistencies reported

by the

Consistency Checker

tool

as errors.

The

EMC Documentum Content Server Administration and

Configuration

Guide

provides

information

about the Consistency Checker

tool.

40

Upgrading

Content

Server

5.Upgrade	the	operating system	if	necessary.
6.Upgrade	the	database if necessary.

7.Disable

•On

•On

all

indows,

jobs.

Linux/Solaris/AIX,

W

disable

jobs

in

all

repositories

jobs

in

all

on

the

in

host.

disable

repositories

the

installation

y

ou

are

upgrading.

Note: Ensure that

y

ou make

a note of

the arguments

and

v alues

of the

standard jobs especially

of

the

LDAPSynchronization job, before

the upgrade.After

the upgrade,

these jobs will hav

e

the

default v alues and

arguments.Hence

it

is

recommended

to sav

e

the settings before the upgrade.

8.For

the upgrade on

indows W a host,

shut

down

the repositories

and connection brokers.

a.Click	Start		> Programs	> Documentum			> Server			Manager	.
b.Select	the	correct Content Serv			er	and click		Stop	.
c.Click	the	Connection Broker tab.
d.Select	each		connection	broker.
e.Click	Stop .

9.For

the

upgrade

on

a

Linux/Solaris/AIX

host,

shut

down

the

repositories

and

connection

brokers.

a.For

each repository

, run

the

dm_shutdown_

r

epository

script,

where

r

epository

is

the

name

of

the

Content

Serv

er

to

be

stopped.

b.Stop	each	connection broker using the dm_stop_docbroker		utility.
The	EMC	Documentum Content Server Administration	and Configuration		Guide	provides	the

steps

for

using

the

dm_stop_docbroker

utility.

10.Shut

down

the application

serv

er.

•T o

shut

down

the application serv er

on

W indows,

stop

the

service

called Documentum

Jav

a

Method

Serv er.Ensure

that

the application

serv

er

does

not

start automatically

after

a host

restart.

•T

oshutdowntheJav

aMethodServ

erserviceonLinux/Solaris/AIX,runscript

$DOCUMENTUM_SHARED

/< jbossfolder

>/server/stopMethodServer.sh

.

11.Run

the Content Serv er installation program.

a.T

o launch the 64-bit Content

Serv er

Installer:

•On W indows, run

serverSetup.exe .

•On Linux/Solaris/AIX, run serverSetup.bin

.

b.The installer displays a

message stating that

y

ou are trying

to upgrade the older

v

ersion

and asks if y ou w ant to

proceed.Click Y es

.

c.Accept the license agreement and click Next

.

d.P

erform one of the following steps:

•In the W indows installer

, type the installation owner password

and click Next

.

•In the Linux/Solaris/AIX

installer

, type

the

Root

User Password

and click Next .

e.Review the installation

summary and click

Install

to begin

installation.

41

Upgrading

Content

Server

f.Specify

if

y

ou

w

ant

to

enter

license

keys

for

optional

modules

of

•Y

Next.

es

:On

the

next

page,

select

corresponding

license

keys.

the

optional

modules

y

ou

w

ant

Content

Serv

er

and

to

install

and

enter

click

•No

:Y

ou

can

alw

ays

enter

license

keys

for

optional

modules

later

using

the

Content

Serv

er

g.T o	configuration program. launch the Content Serv er configuration program and configure			the	repository , select
Configure now and click Done .
	Note: When upgrading, if y ou select	this option	or the Configure	later	option,	y ou		will	be

prompted to select

the

connection modes

( Native

, Secure

,

and Native

and

Secure

)

for

the

repository upgrade.

During

the connection

broker upgrade,

y ou

will not

be prompted

to select

the connection

modes.

12.Upgrade

the

connection

broker.

a.If

y

ou

w ant to

manually

enable

the

use

of

certificates

when

upgrading

the

connection

broker ,

follow

these steps:

i.Stop the connection

broker

service.

ii.Modify

•cipherlist

•keystore_pwd_file

•keystore_file

•secure_connect_mode

file

broker.ini

by

adding

following

properties:

iii.Modify

•dfc.security.ssl.use_existing_truststore

•dfc.security.ssl.truststore_passw

•dfc.security.ssl.truststore

dfc.properties

the

file

by

ord

adding

following

properties:

examples.

the

The

iv.Restart

the

connection

broker

service.

EMC

Documentum

and

Content

Server

Installation

Guide

provides

and

the

v

more

information

y

ou

can

specify

with

about

broker.ini

dfc.properties

properties

alues

b.In

the

Documentum

Content

broker

and

click

Next

.

Serv

er

Configuration

Program

wizard,

select

Connection

c.In

the

W indows

installer

, type

the installation owner password

and

click

Next

.

d.Select

Upgrade

a connection broker

.

e.Select

the

connection broker to

upgrade from the

list, and

click Next

.

f.Complete

the configuration, select Perform additional configuration

,

and

click

Next

.

13.Upgrade	the repository.
a.Click	Upgrade	an	existing	repository	.

42

Upgrading

Content

Server

c.T

b.Select

the

the

the

and

Connection

repository

to

upgrade

Mode

Broker

select

for

Port

options,

from

and

the

list,

and

click

Next

.

ype

Connection

the

repository

and

Use

certificate

on

Broker

the

click

Host

Next

next

.If

page,

y

and

click

ou

Next

the

the

.

d.Select

Native

Connection

Secure

select

provide

Secure

or

required

details, and then

click Next

.

e.In

the W indows

installer

, type

the

SMTP

server

name

and

the

owner

’

s

email

address

and

click

the

Next

module

.

f.Select

g.Specify

Note:

y

ou

w

ant

ou

w

ant

to

activ

ate

to

change

only

screen

the

for

the

xDB

repository

ou

are

superuser

if

y

upgrading

passw

and

click

ord

Next

.

and

whether

This

y

click

Next

.

configuration

appears

from

pre-7.0

Content

Serv er 7.x. to

h.T ype the

repository

owner

password

and

the

Database administrator name

and password

,

and then

click

Next

.

Note: During

the upgrade

process,

a message

might appear

stating that

the repository

is not

running

av

ailable.Before

y

ou

by

checking

restart

upgraded

the

upgrade

click

the

Y

es

in

the

message

and

>\dba\log\<

box,

ensure

that

the

repository

is

up

>.log

and

file.

<

Documentum_Home

select

Finish

using

F

after

repository

click

and

Next

selected

.

Serv

er

indexing,

ou

i.After

completes,

configuration

complete

full-text

14.If

y

Content

from

an

Serv

installation

er

AST

y

ou

the

indexing,

configuration.

xPlore

full-text

again

Content

15.After

y

ou

complete

the

Content

Serv

er

configuration, create

a nonunique index

on

the

dm_sysobject.r_object_id

and

r_aspect_name properties

by using

the following

MAKE_INDEX

command:

attribute='r_aspect_name',use_id_col=true

EXECUTEmake_indexWITHtype_name='dm_sysobject',

Note:

include

The

inclusion

Before

the

of

the

use_id_col

index,

column

v

the

argument

set

to

r_object_id

y

ou

create

the

erify

in

index.

if

it

exists

true

automatically

causes

Content

already.

Check

if

dm_sysobject

has

Serv

er

to

an

index

on

r_aspect_name

and r_object_id.If

the

index

does not

exist,

then

create

it by

using the

abov

e

DQL.

16.If

y

ou

are upgrading

a

repository

in

a distributed environment

that uses

a

BOCS and

asynchronous	write	jobs,	create	an	index	on the dmr_content_s	( i_parked_state				,
r_object_id	) properties.Use			the	following MAKE_INDEX command			to	do	so:

attribute='i_parked_state',use_id_col=true,id_in_front=false

EXECUTEmake_indexWITHtype_name='dmr_content',

17.After

>

the

_HOME

upgrade

is

(for

example,

complete:on

W

indows,

delete

directory

On

%DOCUMENTUM%\<

Linux/AIX/Solaris,

OLD_JBOSS

delete

c:\documentum\jboss4.3.0

);

directory

$DOCUMENTUM_SHARED

/< OLD_JBOSS_HOME

>

.

18.Enable

all

the disabled

jobs.

a.In

Documentum Administrator

,

navigate

to

Administrator

>

Job

Management

>

Jobs

.

c.In

b.For

each

the

of

the

previously

window

,

Properties

set

disabled

jobs,

State

right-click

option

to

the

job

the

Active

.

and

select

Properties

.

43

Upgrading

Content

Server

arguments.Hence

Note:

After

the

set

upgrade

is

the

v

complete,

the

standard

jobs

alues

of

the

jobs

again

to

the

will

hav

v

e

custom

the

default

v

alues

and

alues

and

arguments

assigned

before upgrade.

19.On

a W indows

upgrade,

the Startup

T ype

is

set

to Manual

for

the Documentum Docbase

Service

r epository

name

service.If

y ou

w ant the repository to automatically

start after

a serv

er reboot,

to navigate to Start Automatic .

>

All Programs

> Administrative

ools T

>

Services

, and

set the Startup T

ype

20.Set

the

JA

A_HOME

V

and

complete

the

upgrade.

A

P

TH

environment

v

ariables

to

the

JDK

1.7

directory

after

y

ou

21.Optionally

,rundm_filestore_unique.class

in

%DM_HOME%\install\tools

Processing

$DM_HOME/install/tools (

in

backed

in

Linux/Solaris/AIX)

the

to

log

create

a

filestore

file.

to

the

lock

result

(success

or

that

y

failure)

ou

add

can

the

be

up

found

22.After

upgrade,

ensure

list

of

users

Admin

file

after

upgrade.

group.Also,

ensure

that

y

ou

manually update

the backed up customized

attribute.

Note:

If

y

ou

are upgrading Content

Serv er

in

a

cluster environment

and

are

using

a

non-default

datapath

for

Content

Serv

er

,

update

headstart.ebs

to

retriev

e

the

correct

location

object:

retrieve,c,dm_locationwherefile_system_pathlike'%content_storage_01%'

Cluster

Upgrading

Content

Services

Server

Installed

with

Use	the following procedure		to upgrade Content Serv er installed		with	Microsoft Cluster		Services.
This	procedure applies	to upgrades		on activ e/passiv e, activ e/activ	e, single-repository		, and
multirepository configurations.

T

o

upgrade

an

active/passive,

1.Shut

down

the

Content

Serv

ers

This

shuts

down

the

first

both

down

the

hosts.

node.

repository.

3.Restart

2.Shut

single-repository

on

both

nodes.

cluster:

Do

not

restart Content Serv

er on

the first node.

4.On

the

first node, upgrade

the Content Serv

er

softw

are.The

Upgrading

the

Content

Serv

er

Softw

are,

page

40

section

provides

the

steps.

7.T

If

6.Open

5.Upgrade

and

configure

the

dialog

repository

box

and

v

erify

Method

erify

that

is

Serv

it

er

and

connection

that

the

is

started,

broker.

the

Services

application

it

w

as

serv

the

est

Documentum

Jav

the

repository

to

v

a

created

functioning

correctly.

correctly.

er

w

as

created

8.Shut	down	the	repository		on	the	first	node.
9.Shut	down	the	first	node.

44

correctly.

Upgrading

Content

Server

10.Start	second the node.
11.Start	the connection broker on the second node.
12.Upgrade the Content Serv er softw are on the		second node.The Upgrading the Content				Serv
Softw	are, page section 40 provides the steps.
13.Start	the configuration program and select	Custom Configuration		.
14.Select	Upgrade and the repository to upgrade.
15.When	the configuration program reaches the	panel on	which scripts		are run, click Cancel	.

er

Do

16.T

o

start

not

the

run

the

scripts.The

application

application

serv

er

instance

that

serv

is

er

running

is

created

and

the

a

the

Jav

repository

is

Method

Serv

er

ACS

upgraded.

and

restart

the

W

indows

hosts

after

the

upgrade

is

completed.

serv

er

,

Load-Balanced

Upgrading

Content

Server

in

Configuration

a

Distributed

or

configuration.

Use

the

following

procedure

to

upgrade

the

Content

Serv

er

in

a

distributed

or

load-balanced

T

o

upgrade

a

distributed

or

load-balanced

configuration:

Note:

On

W

indows,

do

not

reboot

the

remote

hosts

by

using

erminal

T

Services.Reboot

the

remote

hosts directly

from

those

hosts.

1.On

the primary

host,

upgrade

Content

Serv er

, connection brokers, and

repository.

2.On

each remote

host,

upgrade

Content

Serv er

and connection broker

,

but

do

not

install

a

repository.

3.Run

Note:

4.T

o

the

cfsConfigurationProgram

an

Make

acsconfig

sure

that

y

ou

use

the

object

in

to

key

Upgrade

content-file

for

name

each

as

the

of

serv

er.

same

the

file

primary

the

ACS

host.

serv

create

repository

ers

installed

with

each remote Content

Serv

er

(that

is,

if there

are three remote Content Serv

ers,

create

three

acs

config objects),

run

one

of

the following scripts

on each remote Content

Serv

er host:

•Linux/AIX/Solaris:

•W

indows:%DM_HOME%\install\admin\dm_acs_install.ebs

$DM_HOME/install/admin/dm_acs_install.ebs

The

syntax

is

as

follows

CacheAcsDescriptionFileHostName

acs_nameserver_config_nameJava_method_server_portacs_protocolCleanupCacheAcsObject

dmbasic-fdm_acs_install.ebs-eInstall--repository_nameuser_namepassword

associated

mode

able

T

8,

page

and

uses

46

describes

the

netw

the

parameters.The

ork

locations,

object.If

acsconfig

broker

object

is

created

targets,

and

in

stores

serverconfig

connection

y

ou

must

projection

the

mode

to

from

in

the

serverconfig

change

acsconfigmode

,

which	y	ou manually	set netw ork locations,		connection broker projection			targets,	and	stores,	use
Documentum Administrator to change				the	mode	and create the	manual	settings.

Note:

Do

not

use

the

Documentum

API

or

DQL

to

modify

the

new

acs

config

object.

45

Upgrading

Content

Server

able

T

8.

Parameters

required

by

dm_acs_install.ebs

script

Parameter			Description and values
acs_name			Object name of the acsconfig		object y ou
			are creating.This name can	be any	arbitrary
			name, but the name must be	unique among
			the object names of acsconfig		objects
			and the serverconfig	objects	of both
			the primary Content Serv er	and any remote
			Content Serv er.
acs_protocol			Communication protocol used by		the ACS
			serv alid er.V v alues are http	and	https .
CacheAcsDescriptionFile			Filetostoreobjectdumpofcandidate
			dm_bocs_configobjects.See
			CleanupCacheAcs description.
CleanupCacheAcsObject			Set to F.
			Note: T w as only required	when upgrading
			fromapreviousv ersionfromwhich
			upgrading is no longer supported.
HostName			Fully-qualified domain name	of host.This
			v alue is used to set the acs_url		attribute
			of the dm_acs_config used	by the serv er
			named in dm_server_name	.
Jav a_method_serv		er_port	P ort where the application	serv er	on the
			remote Content Serv er host	listens, which
			w as provided during remote	Content Serv er
			installation.Do not change	this port number
			after the initial configuration.
passw	ord		P assw ord for the superuser	account.
repository_name			Name of the repository serv	ed by	the remote
			Content Serv er and its ACS	serv er	, where the
			acsconfig object is being	created.
serv er_config_name			Object name of the serverconfig object			of
			the remote Content Serv er.
user_name			Username of a user with superuser		privileges,
			for example, the installation	owner.

5.If

the remote

Content Serv ers are installed

in

a different file-system path from the

primary

Content Serv

er ,

create new

site-specific

location objects for locations that are new in

the upgraded

repository.

a.Using Documentum Administrator

, connect

to

the repository.

b.Create site-specific dm_dba and auth_plugin

location

objects that contain the

locations

on

each of the

remote sites

of $DOCUMENTUM/dba

(Linux/AIX/Solaris) or %DOCUMENTUM%\dba

indows) (W

and the authentication

plug-in.

46

Upgrading

Content

Server

c.In

the

and

the

serv

er

config

object

er.

to

the

for

the

remote

Content

y

ou

created.

Serv

er

,

dba_location

application

serv

location

objects

6.Start

set

Upgrading

A

BOCS

serv

er

is

a

caching

the

BOCS

serv

er.It

is

Server

a

separate,

optional

product

the

auth_plugin_location

with

its

own

installer.It

is

not

installed	with Content	Serv er.The		EMC	Documentum	Content	Server	Distributed	Configuration	Guide
provides	more information		about BOCS.

The BOCS

serv er one is component of distributed a configuration.When upgrading

the Content

Serv er in a

distributed configuration, y ou may

w ant

to upgrade

the BOCS

serv

er

as

w

ell to

use

latest features av ailable in

BOCS/ACS.

T o

upgrade

the BOCS

server:

1.Log on

as the owner of

the existing BOCS

installation.

2.Download and extract

the compressed distribution

file

to

a temporary

location on

the BOCS

serv er host.

3.Stop

the

current

BOCS

serv

er

and

its

components.

4.Follow

the installation steps provided in

the

“Installing

BOCS”

section

in the

EMC

Documentum

Content

Server Distributed Configuration Guide

.

5.Migrate

acs.properties from

the previous

v

ersion’ s

location

to

the new location.

Upgrading

the

DMS

Server

In	a distributed configuration,		the	DMS serv	er facilitates the	precaching	for BOCS	serv	er	and
asynchronous write		operations	for	remote users.The EMC Documentum			Content Server		Distributed

Configuration Guide

provides

more information

about

DMS.

Y ou

can only upgrade

DMS

from

7.0

to

7.1

because In Documentum

7.0, the

DMS installation

w

as integrated with Content

Serv

er.

T

o

upgrade

the

DMS

server:

1.Ensure

that

y ou

hav

e Content Serv

er 7.0 and DMS

7.0 installed

in

y

our environment.

2.Ensure

that

the connection broker

and the global repository

are

configured

for

Content

Serv

er

7.0.

page

3.Upgrade

40

.

Content

Serv

er

7.0

to

7.1.For

the

steps,

see

Upgrading

the

Content

Serv

er

Softw

are,

4.Upgrade	the connection			broker	and	global	repository	to	7.1.
5.Upgrade	DMS	to	7.1.

47

Upgrading

Content

Server

a.Use

the

Content

Serv

er

configuration

program

to

upgrade

DMS:

•Linux/AIX/Solaris:Run

$DM_HOME/install/Server_Configuration_Program.sh

and select Documentum

Messaging Service (DMS)

.

•W indows:Click Start > All

Programs >

Documentum

> Documentum Server

Manager

and on the Utilities tab,

click Server Configuration ,

and then select

Documentum

Messaging Service (DMS)

.

b.Complete the upgrade as instructed.

During

the DMS upgrade, the old DMS

installation

is

deleted from JBOSS

5.1.0

and DMS

7.1

is

installed

in JBOSS 7.1.1.

Post-Upgrade T asks

After

y ou upgrade Content Serv er to

7.x, perform

the

following

tasks

to improv

e the

ov erall

performance of Content Serv er.

Improving Performance after

Upgrade

T o

av

oid performance degradation after

upgrading

to

Content

Serv er 7.x, y

ou must configure

the

alues v

of the following tw parameters: o

•Number

operating

orker

of

w

of

method

serv

er

the

server.ini

on

threads:The

method_server_threads

number

of

dmbasic

jobs,

file,

set

method_serv

y

parameter

3

tune

=

this

v

affects

the

number

all

systems,

threads.Depending

in

the

er_threads

can

ou

alue.For

•Jav

a virtual machine

( JVM) heap memory:The java.ini file specifies the options

to

the

JVM,

which

is used by

the

dmbasic method

serv er.This includes settings

for

the minimum

and

maximum heap

memory for the JVM.

Depending on

y

our environment,

y ou

can tune

this

heap

memory in the

java.ini file:

—For

indow W ,

set

JAVA_OPTIONS="-Xcheck:jni-XX:+RestoreMXCSROnJNICalls-Xms256m-Xmx512m"

Xms

specifies

the

startup

heap

v

alue

and

Xmx

specifies

the

maximum

heap

size

for

the

Jav

a

heap.These

v

alues should

be

set or tuned

cautiously

to

av oid allocating

too much

or

too

little

heap memory.Allocating

too

much heap

memory reduces the system’

s memory for other

processes.Allocating

too little

causes

Jav

a

programs

to

crash with heap errors.

Extending the

Oracle

ablespace T

Size

After

y

ou upgrade Content Serv

er

from

6.5 SP2 and

later

to 7.x,

y

ou must manually extend

the

Oracle

tablespace size based on

y our requirements.This

is

because

the

default Oracle tablespace

size,

which

is

set

to

2 GB, might be

insufficient

and

may lead

to

tablespace-related issues in Documentum

7.x.

48

Upgrading

Content

Server

Enhancements

after

Upgrade

The

The

and

The

dmbasic

Jav

scalability.All

64-bit

Content

a

Method

Serv

er

are

utilizes

the

underlying

64-bit

which

and

w

Jav

is

a

ork

hardw

are

and

its

components

er.

64-bit

specifically

the

mentioned

better

for

performance

below.

er

installer.

features

Serv

er

serv

er

runs

supported

64-bit

Jav

a,

also

uses

the

except

those

with

Serv

bundled

Method

Content

Serv

method

Reinstalling

D2

Client

Libraries

because

D2

client

JARS

the

go

missing

Serv

on

Content

er

upgrade

Serv

er

operation

after

Content

a

new

Serv

er

is

JBOSS

Content

creates

upgraded

to

folder

,

where

7.x.This

the

D2

occurs

existing

client	JARs are not preserv ed.Therefore,		y	ou	must reinstall the	D2 client JARS		after upgrading the
Content	Serv er.The EMC Documentum D2			Installation Guide provides			the steps	for installing	D2.
Rebuilding the database					views
DQL	statements are translated	into SQL	statements that query			the database views.Content			Serv	er

after

creates

and

maintains

the

upgrade

these

views,

which

in

ou

some

need

to

completing

process,

y

rare

instances,

may

get

corrupted.In

such

cases,

rebuild

the

database

views.The

views_valid

attribute

indicates

the status

of the views.It

is

part

of

dm_type

object,

so there

is one views_valid

attribute

per Documentum object type.By

setting

the

v

alue

of

this attribute

to

false (0),

y

ou

can

force

the

Content

Serv

er

to

recreate

the

views.

1.Shut down

the

repository.

2.Connect

to

the

database

used

by

the

repository

through

a

SQL

Editor.Connect

as

the

repository

owner.

3.Update

the

views_valid

attribute

for

each

corrupted

object

type

using

the

following

command:

SQL>UPDATEdm_type_sSETviews_valid=0WHEREname='dm_document';

4.If

y

ou

types

using

are

not

the

sure

which

following

command:

views

to

rebuild,

y

ou

can

rebuild

the

views

for

SQL>UPDATEdm_type_sSETviews_valid=0;

all

the

existing

object

After

6.Restart

5.Commit

the

the

repository.

changes

in

the

database.

the

the

views

are

recreated,

views_valid

attribute

will

be

automatically

set

to

true

(1).

49

Upgrading

Content

Server

50

Chapter

4

Upgrade

Scenarios

upgraded

Serv

This

chapter

er

to

describes

some

of

the

supported

the

path

scenarios

for

for

7.2.Each

v

ersions

scenario

of

the

describes

operating

upgrade

system,

database,

and

the

upgrading

a

and

er

previous

v

ersion

y

the

of

base

Content

Content

Serv

er

,

Serv

steps

including

and

Content

the

ou

need

to perform for

the upgrade.

Note: Although there can

be multiple upgrade scenarios depending

on

the operating system/database

combination,

it is not possible

to

document

all

of those scenarios.This

chapter

only cov

ers the

upgrade

of AIX/Oracle from 6.6

to 7.2

How ev er

, for

a particular

operating system/database combination,

the

upgrade

steps

do

not

v

ary

platform,

much

across

use

Content

the

Serv

er

v

ersions.For

steps

cov

ered

in

example,

the

if

y

ou

are

upgrading

Content

Serv

er

Content

6.7

6.6

SP1

on

Linux/Oracle

to

7.2

—

upgrade

“Upgrading

Linux/Oracle” scenario.

This

chapter contains the

following topics:

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

6

.

5

S P

2

t

o

7

.

2

— W i n d o w

s /

S Q L

S

e

r

v

e

r

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

6

.

5

S P

3

t

o

7

.

2

— A I X / D B 2

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

6

.

7

t o

7

.

2

—

W

i n d o w s / O r

a c l e

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

6

.

7

S P

1

t

o

7

.

2

— L i n u x / O r

a

c l e

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

6

.

7

S P

2

t

o

7

.

2

— S o l a r i s / O

r a c l e

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

7

.

0

t o

7

.

2

—

W

i n d o w s / S Q

L

•U

p

g

r

n C a d i g o

n

t

e

n t

S

e

r

v

e

r

7

.

1

t o

7

.

2

—

L

i n u x / O r a c l e

Upgrading

Content

Server

indows/SQL W

Server

6.5

SP2

to

7.2

—

This	upgrade scenario provides the instructions		for upgrading the 32-bit Content Serv er SP2 6.5
installed on the W indows 2008 R2 (64-bit) operating					system and	using SQL	Serv er 2008 SP1		as the
database.The upgrade process inv olv es		a direct	upgrade of the			operating system to W indows Serv				er
2008	R2 SP1 (64-bit) and the upgrading	the database			to SQL Serv	er 2012.Finally , the 32-bit			Content
Serv	er 6.5 SP2 is upgraded to 64-bit Content Serv			er 7.2.
The	following table lists the base and	upgraded	v ersions of the Content Serv				er ,	operating system, and
database that are supported in this upgrade scenario.

51

Upgrade

Scenarios

able

T

9.Base

and

Upgraded

OS/DB/CS

ersions

V

		Base ersion V				Upgraded ersion V
Operating System		W indows 2008 R2	(64-bit)			W indows Serv	er 2008		R2	SP1
						(64-bit)
Database		SQL Serv er 2008 SP1				SQL Serv er 2012 SP1
Content Serv	er	32-bit Content Serv	er	6.5	SP2	64-bit Content	Serv	er	7.2
Preupgrade	asks T

2.If

1.Review

the

Chapter

are

installing

y

ou

3,

the

Upgrading

xPlore

Content

serv

er

Serv

indexing

,

review

er

the

chapter.

EMC

Documentum

xPlor

e

Guide

.

3.Back

up the repository.

4.Optionally

, y

ou can take a

backup

of all

users that are part

of

the Admin

gr

oup .Also,

y ou take the

backup

of the

customized attribute like group_address.

5.If the

repository contains customized repository formats

(dm_format objects),

back

customized formats.

Installation

ensure

up

the

that

6.T

emporarily

segments

rollback

of

that

the

y

increase

hav

e

the

amount

be

of

rollback

space

av

with

the

the

the

is:

size

ailable

the

in

the

RDBMS.

the

The

and

number

should

be

of

in

equal

segments

size.For

should

commensurate

disk

steps,

refer

space

on

to

tool.The

syntax

of

documentation.

repository

sufficient

the

computer

database

8.Run

7.Ensure

Consistency

ou

hosting

database.

Checker

<

dmbasic-fconsistency_checker.ebs-eEntry_Point--<

superuser

><

password

>

repository_name

>

10.Ensure

9.Fix

the

that

inconsistencies

reported

by

the

Consistency

object

is

Checker

the

dm_server_config

unlocked.

tool

as

errors.

Upgrade

asks

T

2.Apply

1.Upgrade

the

SP2

W

indows

patch

to

the

Serv

operating

SQL

system

er

2008

SP1.

to

W

indows

Serv

er

2008

R2

SP1

(64-bit).

3.Upgrade the database

to SQL

Serv

er

2012 SP1.

4.Update the DSN

entry

from 32-bit

to

64-bit

and

v

erify

that

DSN

is

pointing

to

the

64-bit

SQL

migrating

libraries.The

the

64-bit

ODBC

and

ODBC

and

DSN

DSN

Libraries,

libraries

from

v

5.Disable

the

64-bit

Content

all

jobs

in

Serv

er.

all

repositories

on

the

host.

page

38

section

provides

ersions

for

32-bit

Content

Serv

more

information

er

to

v

ersions

the

c.In

b.Right-click

a.In

Documentum

the

down

the

Properties

Administrator

,

job

and

select

window

set

and

,

navigate

to

Administrator

.

brokers.

as

Inactive

.

Properties

connection

State

the

6.Shut

repositories

>

Job

Management

>

Jobs

.

52

about

for

Upgrade

Scenarios

a.Click	Start	> Programs	> Documentum				> Server			Manager	.
b.Select	the correct Content			Serv	er	and click		Stop	.

c.On

the

Connection

Broker

tab,

select

each

connection

broker

,

and

then

click

Stop

.

7.T o

shut

down

the application serv

er

on

W indows,

stop

the

service

called Documentum Jav

a

Method

Serv er.Ensure

that the application

serv

er

does

not

start automatically

after

a host restart.

•Click

Start

>

Control

Panel

>

Administrative

ools

T

>

Services

,

select

the

Java

Method

Server

,

and

then

click Stop

.

8.During

the upgrade from

32-bit

to

64-bit,Content

Serv

,y er

ou

cannot

upgrade

the

authenticationplug-inswiththe64-bitplug-ins.Y

authenticationplug-insthaty

ouhav

einstalled.Y

ouneedtoreplacethe32-bit

oucanfindtheplug-insinthe

%DM_HOME%\install\external_apps\authplugins

folder.

9.Run

the

a.Run

Content

Serv

er

installation

program.

serverSetup.exe

(W

indows)

to

launch

the

64-bit

Content

Serv

er

Installer.

b.Click

Y

es when the installer displays

a

message

stating

that

y

ou

are

trying

to

upgrade

the

older

v

ersion and asks

if

y ou

w

ant

to

proceed.

d.T

c.Accept

the

the

license

agreement

owner

password

click

and

and

Next

.

ype

installation

y

the

if

installation

ou

w

ant

to

click

Install

to

Next

.

f.Specify

e.Review

summary

enter

license

and

click

for

modules

begin

installation.

of

Content

keys

optional

Serv

er

and

•Y

Next

es

.

:On

the

next

page,

select

the

optional

modules

y

ou

w

ant

to

install

and

enter

click

Services, corresponding license keys.Y for Content Services				EMC ou can enable Centera, Content extended services Storage Services, as such			rusted T Content and so on.
•No	:Y ou	can alw ays enter	license keys		for optional modules later using		the	Content	Serv	er

configuration

program.

g.T

o

launch

the

Content

Serv

er

configuration

program

and

configure

the

repository

,

select

Configure

the

Documentum

connection

now

and

10.Upgrade

a.In

the

broker.

click

Done

.

Content

Serv

er

Configuration

Program

wizard,

select

Connection

broker

and

click

Next

.

b.T

ype

the

installation

owner

password

and

click

Next

.

e.Complete

d.Select

c.Select

Upgrade

the

a

connection

configuration,

broker

broker

.

the

connection

select

to

upgrade

from

the

list

and

click

Next

.

Perform

additional

configuration

11.Upgrade

the

existing

repository.

,

and

click

Next

a.On

the

configuration

program

options

page,

select

Repository

and

then

click

Next

.

.

b.Select	Upgrade	an existing repository			.
c.Select	the repository		to upgrade	from	the	list,	and	click	Next	.

53

Upgrade

Scenarios

d.Y

ou

can

the

choose

a

backup

of

AEK

if

y

ou

key.For

ant

to

w

creating

upgrade

new

AEK

AEK

key

or

continue

with

the

existing

AEK

key.T

ake

key

,

refer

to

EMC

Documentum

Content

Server Installation 7.2 Guide

.

By enabling

the lockbox option,

y

ou can mov

e

the

existing

AEK

key

or

the new

AEK

key

into the lockbox.For more

infrmation on lockbox,

refer

to EMC Documentum Content

Server

7.2 Installation

Guide

.

e.T ype

the Connection

Broker

Port

and

Connection

Broker

Host

and

click

Next

.

f.Select

the

Connection

Mode

for

the

repository

and

click

Next

.If

y

ou

select

the

Secure

or

Native

and

Secure options,

select

Use

certificate

on

the

next

page,

provide

the

required

details,

and

then click

Next

.

g.T

ype

the

SMTP

server

w

ant

ant

name

to

and

to

the

owner

ate

for

the

s

xDB

and

the

’

repository

email

address

passw

and

and

click

Next

and

Next

.

.

j.T

i.Specify

h.Select

the

module

y

ou

whether

y

Repository

ou

the

activ

administrator

ord

click

owner

w

change

the

password

superuser

Database

click

name

Next

and

.

ype

and

then

click

Next

.

password

ou

k.Select

Finish

configuration

from

y

ou

and

click

Next

F

.

12.If

y

upgraded

indexing,

must

an

installation

restart

using

Content

AST

Serv

er

again

full-text

indexing,

after

y

ou

and

selected

the

Content

xPlore

configuration.

full-text

complete

Serv

13.After

y

ou

complete

the

Content

MAKE_INDEX

dm_sysobject.r_object_id

command:

and

Serv

er

configuration,

create

a

nonunique

index

on

the

r_aspect_name

properties

by

using

the

following

er

,

use_id_col=true

EXECUTEmake_indexWITHtype_name='dm_sysobject',attribute='r_aspect_name',

include

The

inclusion

the

y

ou

are

of

the

column

use_id_col

argument

the

in

set

to

true

automatically

environment

that

causes

uses

a

r_object_id

repository

in

index.

14.If

upgrading

a

distributed

Content

a

BOCS

Serv

er

and

to

asynchronous	write	jobs,	create	an	index	on the dmr_content_s	( i_parked_state				,
r_object_id	) properties.Use			the	following MAKE_INDEX command			to	do	so:

use_id_col=true,id_in_front=false

EXECUTEmake_indexWITHtype_name='dmr_content',attribute='i_parked_state',

Post-Upgrade

asks T

1.After the upgrade

complete, is delete directory

%DOCUMENTUM%\< OLD_JBOSS_HOME >

.

2.Enable all the

disabled jobs.

a.In Documentum Administrator

, navigate to

Administrator

> Job Management > Jobs .

b.For each

of the previously disabled jobs, right-click the job and

select

Properties

.

c.In the Properties window

, set the State option

to

Active

.

3.On

a W indows upgrade,

the Startup

T ype is set

to

Manual

for the Documentum Docbase

Service

r epository name service.If

y ou

w ant

the repository to

automatically

start after

a serv

er reboot,

to navigate to Start Automatic .

> All Programs >

Administrative

T

ools > Services

, and

set the Startup T

ype

54

Upgrade

Scenarios

4.Set

the

JAVA_HOME

and

PATH

environment

v

ariables

to

the

JDK

1.7

directory

after

y

ou

complete

the

upgrade.

5.Optionally

,

run

dm_filestore_unique.class

filestore

lock

file

after

upgrade.Processing

result

in

%DM_HOME%\install\tools

(success

or

failure)

can

be

found

in

the

to

log

create

a

file.

6.After

upgrade, ensure

that

y ou

add the backed up

list

of

users

to

the

Admin

group.Also,

ensure

that

y ou manually update the backed up customized

attribute.

7.After

the upgrade is complete,

perform the

following

checks:

a.Check whether the

< Docbroker >.log

file

in

the

< Documentum_Home

>\dba\log\

folder

contains any w arning messages related

to DM_DOCBROKER_W_SSL_HANDSHAKE

_F AILED.

b.Check

whether

the

<

Docbase

>.log

contain

any

exceptions

or

errors.

file

in

the

c.Check

for

error

messages

\log\server.log

file.

in

the

<

JBOSS_Home

<

Documentum_Home

>\dba\log\

folder

>\server\DctmServer_MethodServer

d.T

o

check

the

Documentum

v

ersion,

documentum-version

in

the

command

prompt,

run

the

following

command:

e.T

o

in

check

the

DFC

v

ersion,

ensure

the

command

prompt,

run

the

javaDfShowVersion

that

the

JRE

bin

path

following

command:

is

set

in

the

A

P

TH

v

ariable,

and

then

f.Y ou

can also

check the

Documentum

v ersion mentioned

in

the repository

and

connection

broker log files.

8.Review

the P ost-Upgrade T

asks,

page

48 section for

other post-upgrade

tasks

that

y

ou

might

need to

perform.

Upgrading

AIX/DB2

Content

Server

6.5

SP3

to

7.2

—

upgrading

The

installed

This

upgrade

on

the

upgrade

the

IBM

scenario

provides

inv

AIX

TL3

olv

to

DB2

es

6.1

the

instructions

upgrade

10.5

for

upgrading

and

using

P

the

operating

ack

3.Finally

,

DB2

the

9.7

32-bit

Content

Fix

to

P

IBM

ack

AIX

1

as

er

7.1

the

6.5

Content

Serv

er

Serv

SP3

6.5

and

operating

a

direct

system

Fix

of

TL3

database.

process

system

the

database

Enterprise

32-bit

SP3

is upgraded

to

64-bit Content

Serv er 7.2.

The

following table

lists the

base

and upgraded v ersions

of

the Content Serv operating , er system,

and

database that are supported able T 10.Base and Upgraded

in this upgrade scenario. OS/DB/CS ersions V

Base ersion V

Upgraded ersion V

Operating System

IBM AIX 6.1 TL3

IBM AIX 7.1 TL3

Database

DB2 9.7 Fix P ack 1

DB2 Enterprise 10.5 Fix

P

ack

3

Content Serv er

32-bit Content Serv

er

6.5

SP3

64-bit Content Serv er 7.2

55

Upgrade

Scenarios

Preupgrade

asks

T

an

2.Before

1.Review

the

Chapter

3,

Upgrading

Serv

er

an

Content

on

AIX

8K

Serv

with

er

chapter.

a

DB2

tablespace,

upgrading

8K

page

Content

size.T

o

database,

run

the

create

a

temporary

following

tablespace

with

create

temporary

command:

db2CREATETEMPORARYTABLESPACETEMPSPACE2PAGESIZE=8192

5.Optionally

4.Back

3.Backup

all

tables

into

the

new

tablespace.

of

all

up

take

the

repository.

,

y

the

backup

ou

can

take

a

of

the

backup

users

that

are

like

part

of

the

Admin

y

ou

customized

attribute

group_address.

gr

oup

.Also,

6.If

the

repository

contains

customized

formats.

customized

repository

formats

(dm_format

objects),

back

ensure

up

the

that

7.T	emporarily	increase the		amount of rollback space av	ailable in the RDBMS. The			number of
rollback segments should				be commensurate with the size	of the	repository and should			be	in
segments of		equal size.For		the steps, refer to the database documentation.
8.Ensure that y		ou	hav e sufficient disk space on the computer hosting				the database.
9.Run the Consistency Checker tool.The syntax is:
dmbasic-fconsistency_checker.ebs-eEntry_Point--< repository_name								>
<	superuser	><	password	>
10.Fix the inconsistencies reported by the Consistency Checker tool						as	errors.
11.Ensure that		the	dm_server_config object is unlocked.
12.Ensure that y		ou	perform	the tasks mentioned in step 15	in the Upgrade Checklist,			page	33 .

Upgrade

asks T

1.Upgrade the AIX operating

system

to IBM AIX

7.1 TL3.

2.Upgrade the DB2 database

to DB2

Enterprise

10.5 Fix

P

ack

3.

3.Disable

all jobs in all

repositories in

the installation

y ou

are

upgrading.

a.In

Documentum Administrator

, navigate

to

Administrator

>

Job

Management

b.Right-click the job

and

select Properties

.

>

Jobs

.

c.In

down

the

Properties

the

window

set

er

the

and

,

broker

to

dm_shutdown_repository

connection

State

the

brokers.

as

Inactive

.

4.Shut

repositories

repository

,

run

the

Content

Serv

connection

a.For

name

b.Stop

each

each

of

script,

where

on

be

using

stopped.

the

dm_stop_docbroker

utility

repository

is

the

the

command

line:

%dm_stop_docbroker[-Ppassword][-B[batch]][-Nport_number][-Sservice_name]

5.T

o

•Run

Serv

shut

down

the

that

application

the

serv

er

serv

on

AIX,

er

stop

not

the

service

called

host

Documentum

restart.

Jav

a

Method

the

er.Ensure

application

does

start

automatically

after

a

script

$DOCUMENTUM_SHARED/<

JBOSS

>/server/stopMethodServer.sh

.

6.Run

the

Content

Serv

er

installation

program.

56

Upgrade

Scenarios

a.Run

serverSetup.bin

to

launch

the

64-bit

Content

Serv

er

Installer.

b.Click

Y

es when the installer displays

a

message

stating

that

y

ou

are

trying

to

upgrade

the

older

v

ersion and asks

if

y ou

w

ant

to

proceed.

c.Accept

the

license agreement

and click Next

.

d.Review

the

installation summary and click

Install

to

begin installation.

e.Specify

if

y

ou

w ant

to enter license keys for

optional

modules

of

Content

Serv

er

and

click

•Y

Next

es

.

:On

the

next

page,

keys.Y

select

the

ou

corresponding

license

optional

can

enable

modules

extended

y

ou

w

ant

services

to

install

such

as

T

rusted

and

enter

Content

Services,		Content Services			for EMC Centera, Content Storage Services,			and	so	on.
•No	:Y ou	can	alw ays	enter	license keys	for optional modules later	using