Docu57862 Documentum Content Server 7.2 Release Notes
Docu57862 Documentum Content Server 7.2 Release Notes
Docu57862 Documentum Content Server 7.2 Release Notes
Content Server
Version 7.2
Release Notes
EMC Corporation
Corporate Headquarters
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Legal Notice
Copyright © 1994–2015 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks 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 respective owners.
Documentation Feedback
Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback
about how we can make our documentation better or easier to use, please send us your feedback directly at
[email protected]
Table of Contents
3
Table of Contents
4
Revision History
5
Preface
6
Chapter 1
Overview
EMC Documentum Content Server is the core of the EMC Documentum content management
platform. Content Server governs the content repository and enables a set of content management
services for controlling content and processes throughout distributed enterprises. Content Server
lets you store, manage, and deploy all types of content, including HTML and XML, graphics, and
multimedia. Content Server provides services such as the following:
• Integrated workflow
• Lifecycle and process automation
• Version control
• Security
• Data dictionary for capturing and configuring business rules
With Content Server, users can share and reuse trusted content on demand within and between
business units. Administrators can define, organize, automate, and monitor all the functions and
tasks of complex business processes.
This document includes information about Content Server functionality changes from the previous
release, and provides information on known issues, if any.
This document also includes information about distributed configurations, which includes but is
not limited to Documentum Messaging Services (DMS) and Accelerated Content Services (ACS).
Information about Branch Office Caching Services (which is also a component of distributed
configurations) is included in the EMC Documentum Branch Office Caching Services Release Notes.
For information about XML Store functionality changes, see EMC Documentum XML Store Release
Notes.
Documentum Foundation Services (DFS) is no longer installed with Documentum Content Server.
You must install a DFS server on a machine that is different from the one on which Content Server
is installed. For information about DFS functionality changes, see EMC Documentum Foundation
Services Release Notes.
Resources
Product resources are available on the Web.
7
Overview
Providing Feedback
Documentation Feedback
Your opinion matters. We want to hear from you regarding our product documentation. If you have
feedback about how we can make our documentation better or easier to use, please send us your
feedback directly at [email protected].
8
Chapter 2
Features and Updates
This section highlights the major functionality changes included in this release. Refer to the product
documentation for complete information about these features.
9
Features and Updates
10
Chapter 3
System Requirements
The EMC Documentum 7.2 Environment and System Requirements Guide contains the system
requirements information for your product. This documentation is available from EMC Online
Support.
11
System Requirements
12
Chapter 4
Installation and Upgrade
Before beginning installation, ensure that your system meets the requirements listed in Chapter 3,
System Requirements. After installation, be sure to update your software to the latest patched release.
• The EMC Documentum Content Server Installation Guide contains the instructions on installing and
configuring Content Server.
• The EMC Documentum System Upgrade and Migration Guide contains the instructions on upgrading
Content Server.
• The EMC Documentum Content Server Distributed Configuration Guide contains the instructions on
installing Documentum Messaging Services (DMS) and Branch Office Caching Services (BOCS).
For instructions on upgrading the entire Documentum system, see the EMC Documentum System
Upgrade and Migration Guide.
13
Installation and Upgrade
14
Chapter 5
Fixed Issues
This section identifies issues that have been resolved in this release.
15
Fixed Issues
16
Fixed Issues
17
Fixed Issues
18
Fixed Issues
19
Fixed Issues
20
Fixed Issues
21
Fixed Issues
22
Fixed Issues
23
Fixed Issues
24
Chapter 6
Known Issues
This section identifies known product issues and limitations that may affect your use of the product.
Workaround: Use the old passphrase for the new key and then manually change
the passphrase after the upgrade process.
CS-48939 After consolidation of repositories, the user_rename operation does not rename
the user on the migrated repository.
CS-48653 Authentication of the xDB superuser password fails while upgrading the
repository. This issue occurs in a combination of an environment having
repositories that are enabled with XML Store and also that are not enabled with
XML Store.
Workaround: Add the hostname (hostname value as shown in bold in the example)
in the xhiveaddress (xDB hostname) entry in $DOCUMENTUM_SHARED/<JBoss
version folder>/server/DctmServer_MethodServer/deployments
/XhiveConnector.ear/XhiveConnector.war/WEB-INF/web.xml, restart
the Java Method Server, and then start the upgrade process.
For example:
<init-param>
<param-name>xhiveaddress</param-name>
<param-value>AIXDB26166</param-value>
</init-param>
25
Known Issues
Workaround: Disable the non-anonymous SSL mode on the Content Server and
install the required DAR files using the Composer headless DAR deployer. Once
installed, enable the non-anonymous SSL mode.
CS-42794 Java libraries do not honor the expiration date of certificates for non-anonymous
SSL communication.
CS-42313 Content Server does not support mapped shared directory drive while configuring
repositories using the SAN or NAS devices.
26
Known Issues
2. For the appropriate client on the secondary host, select the following options:
• Enable trusted login
DEVRANDOM=/dev/urandom
export DEVRANDOM
CS-41543 When you configure the global repository after installing Content Server, the
DFC_DOCBROKER_EXCLUDED warning message occurs in the JMS, DFC, and ACS
log files. This is because the Teredo Tunneling Pseudo-Interface is enabled.
Or
• Disable the IP Helper service from the Services dialog to disable the tunneling
permanently.
27
Known Issues
28
Known Issues
However, you can ignore these warnings. The JBoss website contains more
information.
DC-7495 Warning messages are displayed in the server log directory while deploying
ACS, BOCS, and DMS. For example: Class Path entry <JAR1 NAME>
in "<JBOSS 7.x HOME>/server/DctmServer_DMS/deployments/DMS
.ear/dms-ws.war/WEB-INF/lib/<JAR2 NAME>” does not point to
a valid jar for a Class-Path reference.
However, you can ignore these warnings. The JBoss website contains more
information.
DFC-10601 Installation fails on Solaris 11 with the Segmentation fault (core dumped)
error.
Workaround:
1. Kill the running dm_crypto_boot processes, if any.
29
Known Issues
Workaround: Install the JCE plugin manually before you run the LDAP
synchronization job.
CS-45744 The dm_policy object that is attached with the dm_procedure object can only be
deleted by a superuser irrespective of the owner of the dm_policy object.
Workaround:
1. Unlink the dm_procedure object from the dm_policy object.
2. Delete the dm_policy object using the privileges used to create the dm_policy
object.
Workaround:
1. Start the repository and get the process id on which it is running.
3. Import the certificate and run the LDAP synchronization job in SSL mode.
4. Authenticate the LDAP user to update the hash value of the certificate in
the aout.log file.
5. Get the hash value of the certificate from the aout.log file.
6. Create a new copy of the existing certificate that you used for running the
LDAP synchronization job in the LDAP certdb location, name it with the
hash value, and authenticate the user.
Note: An error message appears when you try to run the LDAP
synchronization job again. For example: ERROR: Failed to load
certificate file /export/home/d72/dctm/dba/secure/ldapdb
/9e513170.0: Certificate file name is not named using
its expected SHA1 hash value 9f4080d1. This error occurs because
it loads the existing certificate and does not load the certificate you created.
Ignore the error message.
CS-44167 The EMC RSA plug-in for Documentum that allows Content Server to authenticate
users based on RSA ClearTrust single sign-on tokens does not support RSA
clustering. This is a RSA limitation.
30
Known Issues
If the number of configuration objects or URLs exceeds 2, the message may get
truncated when it gets stored in the DMS database. Therefore, it is recommended
to avoid such configurations of ACS config object(s). This is a limitation.
CS-43778 In a AIX with DB2 combination, creating a folder with name containing the special
characters ^^ results in an error.
CS-43570 If the number of file stores in Content Server are more than 100, any
additional file stores created do not work and results in the following
error: [DM_SESSION_E_STORESTAT_OVERFLOW]error: "The shared
memory segment for caching the ONLINE/OFFLINE status of
the Documentum Storage areas has reached its maximum size
(100). Update access may be incorrectly given to Offline or
ReadOnly storage area (28003039800002b7).". The file store status of
some of the stores may be incorrect. This is a limitation.
CS-42237 Auditing aspect attributes does not work.
CS-42094 Change object type to a subtype does not work for lightweight objects.
CS-41576 LDAP synchronization fails when you try to synchronize a high count of user data
from the Microsoft Active Directory with the java.net.ConnectException:
Connection timed out exception.
Note: If you do not set this value, or specify some other value, the default value
‘follow’ is set.
CS-41400 On UNIX and Linux, when both Content Server and connection broker are
configured for Certificate-based SSL, if certificate-related errors occur, the server is
unable to connect to connection broker. Repository/connection broker control is
not possible using IAPI. You have to manually kill all server started processes to
shutdown the server. This is a limitation.
CS-41252 When querying, agent_exec looses time because it also goes through jobs that are
dedicated to another server.
Workaround: To avoid time loss, set the value of the target_server attribute to
current server or ANY SERVER.
31
Known Issues
Note: The view gets updated whenever you use a type object for the first time in
Content Server. Otherwise, the view remains the same.
CS-40838 When two users perform a move operation of two folders simultaneously, the
r_folder_path and i_ancestor_id parameters contain incorrect values
causing folder inconsistencies in Oracle and SQL Server.
All argument names are mandatory and have to be passed to the Java method. If a
particular argument name has no value, pass an empty string.
CS-40563 ACCESS_VIOLATION found in the docbase log while running the business_policy
suite. This is because Oracle version 11.2.0.3 is not certified on Microsoft Windows
2012 Server.
Note: Oracle plans to certify the 11.2.0.4 database and client on the Microsoft
Windows 2012 Server. 11.2.0.4 is not released yet.
CS-40534 Querying for repeating attributes using DQL displays the result in the same order
as it is stored in the database.
Workaround: Use the "ORDER BY i_position DESC" clause with the DQL query.
CS-40474 Performance issue is encountered when promoting a document in lifecycle, within
a transaction. This occurs due to concurrent access to the dmc_tcf_activity object.
32
Known Issues
Workaround: Use the single quote if the password has a comma. For example:
API> encrypttext,c,'password,123'
33
Known Issues
Workaround: Explicitly provide a value for input argument -full_sync for the
LDAP synchronization job through Documentum Administrator before running
it: TRUE for full sync; FALSE for incremental sync.
CS-39232 acl_check_db cannot be set to TRUE with QBS. This is because DFC does not
support setRange with double security check in Content Server.
CS-37048 Content migration, encryption, de-duplication and compression of content in to
Atmos store is not supported.
CS-35195 On Linux, there is a short delay between the dormancy status of a repository
changes and the new dormancy status is projected to the connection broker. This
is a limitation.
CS-35117 dm_check_password utility does not work on Windows 2008 domains because of
Samba limitations. Instead, use the LDAP. This is a limitation.
CS-5772 HTML email does not work on Solaris, while the same email can be correctly sent
as HTML in Windows.
DC-6297 If one of the following errors occurs on DFC/UCF running on Tomcat 7.0, you
might need to set the HTTP request timeout to a value that is more appropriate
DC-6084 for your environment:
java.io.IOException: missing CR
34
Known Issues
When the ACS server and the global registry are of different versions, for example,
a 6.7 SP1 ACS and a 7.0 global registry, add the entry for the global registry to the
acs.properties file. This file is located in following location:
On Windows: %DOCUMENTUM%\jboss5.1.0\server\DctmServer
_MethodServer\deploy\acs.ear\lib\configs.jar\config\acs
.properties
On Linux: $DOCUMENTUM/jboss5.1.0/server/DctmServer
_MethodServer/deploy/acs.ear/lib/configs.jar/config/acs
/properties
DA-10459 Unable to access DFC client application when Kerberos SSO is configured using
Sun Login module "com.sun.security.auth.module.Krb5LoginModule required"
on the SUSE Linux environment. This happens when the application server is
configured with the SUSE Linux environment. The following error message is
displayed when you try to access Documentum Administrator:
35
Known Issues
Documentation
Issue Number Description
N/A Product documentation might contain references to client applications and
functionality that are not supported in the 7.x release, though these applications
and functionality may become compatible in a future release. Only those client
applications documented as compatible in the EMC Documentum 7.x Environment
and System Requirements Guide are supported in 7.x.
36