EMC ® Documentum ®

Foundation Classes
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

Revision History .................................................................................................................. 5

Chapter 1 Overview ..................................................................................................... 7

Resources ......................................................................................................... 7
Documentation and Support ......................................................................... 7
EMC Online Communities ............................................................................ 8
Providing Feedback .......................................................................................... 8
Documentation Feedback .............................................................................. 8
Product Enhancement Requests ..................................................................... 8

Chapter 2 Features and Updates ................................................................................. 9

Configuring Kerberos Credential Delegation Using the Kerberos
Delegation Utility ............................................................................................. 9

Chapter 3 System Requirements ................................................................................. 11

Chapter 4 Installation and Upgrade ............................................................................. 13
Chapter 5 Fixed Issues ................................................................................................ 15
Chapter 6 Known Issues .............................................................................................. 17
Additional Information About Limitations ......................................................... 22
SSLv3 connection from 7.0 DFC to pre-7.0 Content Server ............................... 22
Checkout and view files using Webtop in Internet Explorer ............................. 23
Limitations of DFC in a 64-bit JVM environment ............................................ 23
Evaluation of docbasic expressions in native code ....................................... 23
Operations involving the Windows registry ............................................... 24
OLE ......................................................................................................... 24
Required configuration for machine-only application access control
tokens .......................................................................................................... 24
Ensuring a correct jaxp.properties File ........................................................... 24
Setting permissions for multiple DFC users on Linux systems ......................... 25
Maximum number of results to retrieve per source by a query search .............. 25
Copying a keystore from a machine to another does not work ......................... 25
DFC Copy operation ..................................................................................... 26
Documentation................................................................................................. 26

3
Table of Contents

4
 Revision History

Revision Date Description

February 2015 Initial publication.

5
Preface

6
 Chapter 1
Overview

The EMC Documentum Foundation Classes 7.2 Release Notes contains customer-reported bug fixes
and platform compatibility updates. This document also includes a list of fixed problems, known
problems and limitations.
DFC is a key part of the Documentum software platform. While the main user of DFC is other
Documentum software, you can use DFC in any of the following ways:
• Access EMC Documentum functionality from within one of your company’s enterprise
applications.
• Customize or extend products.
• Write a method or procedure for Content Server to execute as part of a workflow or document
lifecycle.
In terms of Documentum functionality, DFC lies between Content Server and clients and are used for
server-side business logic and customization.

Resources
Product resources are available on the Web.

Documentation and Support

For the latest product documentation and support materials, including White Papers and Technical
Advisories, refer to EMC Online Support (https://support.emc.com). Check regularly for new and
updated documentation to ensure that you have the latest system information.
Note: Documentation installed, or packaged with the product on the download center, is current at
the time of release. Documentation updates made after a release are available for download from
EMC Online Support (https://support.emc.com).

7
Overview

EMC Online Communities

Visit EMC Community Network (community.emc.com) for peer contacts, conversations, and content
on product support and solutions. Interactively engage online with customers, partners and certified
professionals for all EMC Products.

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].

Product Enhancement Requests

Help us to improve the products that you use. Use our Enhancement Request System, available from
many product support pages, to tell us what you would like to see in future releases.

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.

Configuring Kerberos Credential Delegation

Using the Kerberos Delegation Utility
Constrained delegation restricts delegation to specific services that are configured on an Active
Directory service account. Constrained delegation uses a series of service tickets instead of the
transmission of the user’s Ticket Granting Tickets (TGT). You can now use the Kerberos Delegation
utility to delegate the credentials.

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 (https://support.emc.com).

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 Foundation Classes 7.2 Installation Guide contains information about how to
install DFC 7.2 on your application servers.

13
Installation and Upgrade

14
 Chapter 5
Fixed Issues

This section identifies issues that have been resolved in this release.

Issue Number Description

DFC-12745 System throws an exception from xQuery while
running DQL in the same session.
DFC-12510 dm_WFReporting job cutoff_time_utc is taken
from time_stamp and not from time_stamp_utc
attribute.
DFC-12446 Periodically it is observed that the sessions
building are up after upgrading to DFC 6.7 SP2
and eventually running out of sessions.
DFC-12302 "No max result parameter available" error is
thrown when generating xQuery with DFC.
DFC-12272 Copying of objects with rendition = 3
(keep_rendition) between 2 docbases failed on
webtop due to format object id not being fixed.
DFC-12233 Incorrect error message when supplied date
does not exist.
DFC-12171 When viewing the virtual documents
with deleted child objects, exception is
thrown if compound_integrity is set to F in
dm_server_config.
DFC-12150 The a_contain_desc field for dmr_containment
of a vdm increases in length, if hashCode
function returns a negative value.
DFC-12141 Virtual document structure shows wrong
versions of child documents.
DFC-12089 IDfContext.getSources() documentation should
be more precise about the behavior
DFC-12052 For any node actions which are marked with
error code in DFC, set error message details on
the node. This is used by UCF/WDK to take
appropriate action.

15
Fixed Issues

Issue Number Description

DFC-12039 With dfc.session.global_pool_enabled=true we
get an exception DFC_SESSION_HANDLE
_DYNAMIC_FAILURE
DFC-12007 A repeating, not null, not blank attribute doesnot
raise an error when no value is entered.
DFC-11968 A session leak occurs when an invalid DQL
query is passed to the IDfSearchService using
IDfQueryManager.newPassThroughQuery.
DFC-11950 Out of memory exception occurs, when more
than 35 thousand objects are created under a
single transaction of a session.
DFC-11893 If the docbroker is blocked forever (like
purposefully blocking it through telnet or some
network issues), then the new connections are
also blocked due to internal synchronization
even though they can be served through other
available docbroker. DFC will set SO_TIMEOUT
option on docbroker socket, so when docbroker
request is idle for specified time, then socket
will timeout and continues with next available
docbroker.

16
 Chapter 6
Known Issues

This section identifies known product issues and limitations that may affect your use of the product.

Issue Description
Number
DFC-12824 When you use Java bundled with Documentum to generate the certificates using the
command keytool.exe -genkey -alias tomcat -keyalg RSA -keystore
jms.keystore -storepass password, the following error appears:

keytool error: java.lang.IllegalArgumentException:

publicKey's is not X.509, but X509

Workaround: Change the following text in java.security file located at

C:\Program Files\Documentum\java\1.7.0_72\jre\lib\security\java.security:
security.provider.1=com.rsa.jsse.JsseProvider
security.provider.2=com.rsa.jsafe.provider.JsafeJCE
security.provider.3=com.rsa.jsse.JsseProvider
security.provider.4=com.rsa.jsafe.provider.JsafeJCE
to
security.provider.1=sun.security.rsa.SunRsaSign
security.provider.2=com.rsa.jsafe.provider.JsafeJCE
security.provider.3=com.rsa.jsse.JsseProvider
security.provider.4=sun.security.provider.Sun
DFC-11762 When you configure the global repository after installing Content Server, a
/CS-41543 DFC_DOCBROKER_EXCLUDED warning message is generated in the JMS and ACS log
files. This problem occurs when the Teredo Tunneling Pseudo-Interface is enabled.

Workaround: To work around this problem, disable the Teredo Tunneling

Pseudo-Interface by using the following command.
netsh interface teredo set state disabled
Alternatively, disable the IP Helper service from the Windows Services console. This
method also disables the Teredo Tunneling Pseudo-Interface.

17
Known Issues

Issue Description
Number
DFC-11749 Authentication to client applications like TaskSpace, Webtop, and Documentum
Administrator fails due to changes in the RSA encryption algorithm (FIPS).

Workaround: To enable your client such as TaskSpace 6.7 SP2 to work with Content
Server 7.1, you must perform the following steps to update the dm_bof_registry user
password since Content Server 7.1 uses a different encryption algorithm (FIPS/SHA1)
than the one that earlier versions of Content Server use (MD5):
1. Decrypt the dm_bof_registry user password using the decrypt API of the
RegistryPasswordUtils class in DFC 7.1 to get the plain text password.

2. Encrypt the plain text password using the encrypt API of the
RegistryPasswordUtils class in DFC 6.7 SP2 on the client.

3. Place the encrypted password in dfc.properties on the client.

From a command prompt, execute the following command to generate the

encrypted form of the global registry user’s password:
java -cp dfc.jar com.documentum.fc.tools.RegistryPasswordUtils
password_of_user
where password_of_user is the clear-text password of the global registry user.
DFC-11130 When a DFC session is reconnected, the server generates an audit event and updates
the login time.
DFC-10901 An invalid license exception occurs during multi-domain Kerberos authentication.
DFC-10666 DFC only supports UTF-8 characters. Any software that uses other character
encoding to integrate with DFC may encounter problems. This limitation mainly
CS-38188 affects SSO software, such as SiteMinder, when clients try to authenticate with
non-UTF–8 characters.
DFC-10601 Installation fails on Solaris11 with the Segmentation fault (core dumped)
error.

Workaround: To install on Solaris11, copy libucb.so.1 from the /usr/ucblib/

folder on Solaris10 to the /lib folder on Solaris11.
DFC-10310 If you attempt to use secure connection from a 7.0 instance of DFC against an earlier
release of Content Server, the connection fails. DFC and Content Server secure
connections from 7.0 onwards uses TLS for encryption but earlier releases used
SSLv3. SSLv3 connection from 7.0 DFC to pre-7.0 Content Server, page 22, provides a
workaround.
DFC-7934 The include_content_and_markup option is not implemented. Selecting this
option in the XML application builder does not work.
DFC-4445 Copying an object in Webtop will copy subscriptions to the object, as well.

18
 Known Issues

Issue Description
Number
DFC-1376 Using PIA, the client is unable to use the getContent() method to read data into
(DFC-6012) memory. The recommended approach for reading the data into memory is to use a
code snippet such as the following:
dfclientX.ByteArrayInputStreamToString (sysObject.getContent())
(The return value of getContent() is not a defined class in C#/.NET.) This approach
works for ASCII data. For non-ASCII data, only a small portion of the data is read .

Workaround: Use getFile(filename). This workaround has performance and security

considerations.

DFC-1179 A .NET program using DFC reads the log4j.properties file only when the properties
(DFC-5815) file is inside the C:\Documentum\Config folder. Placing the properties file in another
folder in the CLASSPATH does not work.
DFC-11735 DFC 6.7 SP2 running in the secure mode is not compatible with Content Server 7.1
that has certificates created for both DOCBROKER and DOCBASE. This combination
causes the following error message:
DfException in TDfSummaryLogManager.java: unable to make
docbase connection! DfDocbrokerException:: THREAD: main; MSG:
[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker "dualcs:1489"
failed; ERRORCODE: ff; NEXT: null
DFC-11635 Removing a user using the method IDfGroup.removeUser from a group object
on which an audit trail event is enabled causes insert-related audit information to
be unexpectedly recorded in the audit trail record in addition to the delete-related
audit information.

Workaround: Use the IDfGroup.remove method when an audit recording is

needed. This workaround only applies to groups with a small number of users,
because the SWAP operation in IDfGroup.removeUser is needed to address the
performance issues for groups having a large number of users.
DFC-11529 An error in DFC causes performance issues in multi-domain Kerberos authentication
in Documentum REST Services.

Workaround: To achieve better performance, enable the ticket cache on the server
side.
DFC-9900 For the 7.0 release, we made changes to the DFC cryptography code. We replaced the
non-FIPS 140–2 MD5 algorithm with SHA1. This means that beginning with the DFC
7.0 release, all passwords will be encrypted using the new algorithm. Older (pre-7.0
release) DFC clients that attempt decrypt post–7.0 release encrypted passwords will
fail. However, a post-7.0 release DFC can still decrypt pre-7.0 release encrypted
passwords (with a warning), for backward compatibility.
DFC-1073 The getChildRelatives method of a class that implements the IDfPersistentObject
(DFC-5709) interface always returns the child_id of the dm_relation object, regardless of the
value of child_label.

19
Known Issues

Issue Description
Number
DFC-843 If you check out a replica of a document, the system checks the original document out
(DFC-5480) as well. If you check in the replica, the system checks the original back in as well.

However, DFC does not support checking out a replica, then subsequently checking
in the original directly.
DFC-697 When an XML document contains the pre-defined XML entities of > and ’ or any
(DFC-5334) numeric entity in an XML attribute, the entity is expanded in an exported document.
The numeric entities are expanded for those characters that are not in the character
set of the exported document. This means that the markup
<technology transfer="<Analog> & "Digital ' &#165;"/>
will be exported as
<technology transfer="<Analog> & "Digital ' Y/>
where Y is the symbol for Yen.
DFC-695 The DFC IDfExportOperation does not preserve the line sequence from original XML
(DFC-5332) content. For example, if the original sequence of elements is:
<books>
<book>
Sequence after Export:
<books><book>

While this behavior might be unexpected, the XML content is still valid.
DFC-452 It is not possible to lock a rendition to prevent it from being deleted. For example,
(DFC-5093) when you try to export an object, and at the same time another user with appropriate
permission over the object deletes it, the deletion succeeds and the you will get an
error.
N/A DFC does not check, before deleting a document, to see if that document is a child of
a virtual document in another repository. For example, assume Doc A, in repository
1, is the root document, Doc B is a child of Doc A that lies in repository 2, and Doc C
is a child of Doc B that lies in repository 1.

DFC does not report an error if you delete Doc B, but the containment object that
bound Doc B to Doc A still exists in repository 1. As a result, if you log into repository
1, it looks to DFC as if Doc B is still part of Doc A. If you then perform operations on
Doc A, DFC might report errors.
N/A You cannot use classes of the com.documentum.operations package within
transactions in a multi-threaded environment.

20
 Known Issues

Issue Description
Number
N/A DFC supports some OLE compound documents on Windows platforms. DFC
supports only the following:
• OLE compound links in Word and PowerPoint

• External sheet and cell references in Excel formulas

In particular, DFC does not support OLE compound documents in Access, Outlook,
or Visio. It does not support circular references in links.

Compound documents (for example, OLE and XML) cannot be children of virtual
documents.
N/A If you add an object to an IDfExportOperation more than once, but with different
formats, the operation exports the object to a single file on the file system.

Workaround — Use separate export operations for the different formats.

N/A The getDataType method of the IDfAttr interface and the getAttrDataType method
of the IDfTypedObject interface can return unexpected values. The datatype they
return for an attribute that is part of a query collection is the type that Content
Server returns. This might differ from the datatype that the IDfSysObject interface
specifies for that attribute. The type returned might vary with the server’s underlying
relational database.

Workaround — Structure your application in such a way that you do not need
to invoke these method.
N/A The equals method of an IDfTime object returns a value of true if the method’s
argument represents a time that is within one second of the time that the object
represents.
N/A If you use an import operation to import a Windows file system folder and its
contents into a repository, and if the folder contains a shortcut to a file or folder in
another folder, DFC does not import the file or folder referenced by the shortcut.

Workaround — Explicitly import the files or folders referenced by the shortcut.

N/A We do not support the xml:base attribute as specified by the XLINK language. You
cannot import XML files containing this attribute. In particular, you cannot import
packages that use the SCORM standard for web-based learning systems.
N/A DFC 5.3 uses a newer version of Xalan than previous DFC versions used. The
new Xalan conforms more closely to the XSLT standard with regard to omitting
whitespace. This might make the output of existing transformations appear on fewer
lines than they did with the earlier Xalan.

Workaround — To preserve line breaks, use explicit commands in your template.

N/A In an environment in which two Content Server instances control repositories that
have the same name and project to different connection brokers, some DFC methods
fail to execute correctly if they try to access both repositories.

21
Known Issues

Issue Description
Number
N/A The file download dialog box does not appear when attempting to perform file
transfer operations such as checkout, view and edit in Webtop.

Workaround: This issue appears to be related to the security settings in Microsoft

Internet Explorer 7, 9, 10, and 11. If the security settings in Internet Explorer 7, 9, 10,
and 11 are set to medium (or higher), you will not be prompted to download the
file. Adding the site as a trusted site, as well as customizing the security settings for
trusted sites to allow prompting for file downloads, might resolve the issue.

The Checkout and view files using Webtop in Internet Explorer, page 23 section
provides information on how to change the Internet Explorer 7, 9, 10, and 11 security
settings.
N/A Importing a document on Macintosh platform does not import (and later export) the
’File Comments’ of the document, viewable through the ’Get Info...’ operation.
N/A The copy operation from one SSO to another SSO does not work.
N/A The Limitations of DFC in a 64-bit JVM environment, page 23 section provides
information on limitations of DFC in a 64-bit JVM environment.
N/A DFC validation methods obtain the locale from sessionconfig.session_locale and use
that locale in data dictionary queries. If the data dictionary does not have information
for that locale, the queries return an empty result set, rather than information for the
most closely matching locale.

Workaround: Before using DFC validation methods, ensure that

sessionconfig.session_locale contains a locale for which the data dictionary contains
locale-specific values.

Additional Information About Limitations

This section includes supplemental information about limitations.

SSLv3 connection from 7.0 DFC to pre-7.0 Content

Server
A workaround to allow SSLv3 connections from 7.0 DFC to pre-7.0 Content Server is to edit the file:
$JAVA_HOME/jre/lib/security/java.security
and add the following line:
com.rsa.cryptoj.jsafe.fips140initialmode=NON_FIPS140_MODE
However, you should be aware that modifying the file in this way allows DFC to use non-FIPS 140–2
validated encryption modules for the connection.

22
 Known Issues

Checkout and view files using Webtop in Internet

Explorer
This section describes the procedure to change the Internet Explorer 7, 9, 10, and 11 security settings
to checkout and view files using Webtop in Internet Explorer.

To change the Internet Explorer security settings:

1. In Internet Explorer, go to Tools > Internet Options > Security tab.
2. Select Trusted sites. Click the Custom level button in the section entitled Security level for
this zone.
3. In the Security Settings>Trusted Sites Zone dialog box, scroll to the Downloads section and
enable Automatic prompting for file downloads.
4. Click OK twice to exit the Security Settings and Internet Options dialog boxes.
5. Close and restart browser.
You should now be able to checkout and view files using Webtop in Internet Explorer 7, 9, 10, and 11.

Limitations of DFC in a 64-bit JVM environment

The following limitations only apply when a stand-alone DFC installer is used on Windows operating
systems. These limitations do not apply when building web applications using the bundled version
of DFC (dfc.jar).

Evaluation of docbasic expressions in native code

Expression evaluation in native code will not work because it requires loading 32-bit dlls, which does
not work in a 64-bit JVM environment.

Workaround — To make this work in a 64-bit JVM environment, you can convert C++ expressions to
Java expressions using the following methods:
• dmc_MigrateDbExprsToJava: Used to migrate expressions defined for multiple object types.
• dmc_MigrateDbExprsToJavaForType: Used to migrate expressions defined for a particular type.
For example:
apply,c,NULL,DO_METHOD,METHOD,S,
dmc_MigrateDbExprsToJava,SAVE_RESULTS,
B,T,ARGUMENTS,S,-docbase Imaging1 -user dmadmin
-ticket <your_ticket_or_password>-select all -listExprsOnly false

23
Known Issues

Operations involving the Windows registry

Some DFC operations need to store state information. DFC can use either a file or Windows registry
to store this state information. DFC has native implementation of Windows dll for using the Windows
registry. This dll is a 32-bit dll file and cannot be loaded in a 64-bit JVM environment.

Workaround — For Documentum 6.0 and later versions, the default registry mode is ‘file’.
Therefore, this issue does not occur unless ‘windows’ registry is explicitly configured for usage. For
running DFC in a 64-bit JVM, use file based registry.

OLE

DFC provides a mechanism for scanning and patching OLE links in Microsoft Office documents.
DFC has native implementations in the form of Windows dlls for scanning and patching these links.
These dlls are 32-bit dll files and cannot be loaded in a 64-bit JVM environment.

Workaround — Currently, there is no workaround available.

Required configuration for machine-only application

access control tokens
If you are using application access control tokens configured to be valid only when sent from
applications on particular host machines, you must set the dfc.machine.id key in the dfc.properties
file used by those client applications. The key must be sent to the machine ID of the host from which
the AAC token is sent.

Ensuring a correct jaxp.properties File

Some operating systems (for example, AIX) might install a jaxp.properties file, or that directory might
contain a jaxp.properties file that was intentionally placed there. The purpose of the jaxp.properties
file is to specify the way DFC implements the JAXP parser, by providing the class names for the
JAXP factories. An empty jaxp.properties file might cause DFC to use the default implementation
provided by the operating system.
A jaxp.properties file in the JAVA_HOME/lib/ directory overrides the information in the manifest in
dfc.jar, which points to the XML parser and transformers that come with DFC. This might lead to
errors such as the following:
Content transfer: Server returned HTTP response code: 500 for URL:
http://torcanary:8003/webtop/wdk5-xmlutil?operation=4

In the case of a WDK application, the application server’s error log shows the following error:
javax.xml.parsers.FactoryConfigurationError:
Provider null could not be instantiated:
java.lang.NullPointerException

24
 Known Issues

To resolve this problem, you can do one of the following:

• Rename the jaxp.properties file on your local system
• Add lines similar to the following to the jaxp.properties file:
javax.xml.transform.DfTransformerFactory=org.apache.xalan.
processor.TransformerFactoryImpl
com.documentum.xml.jaxp.DfSAXParserFactory=com.documentum.
xerces_2_3_0.xerces.jaxp.SAXParserFactoryImpl
com.documentum.xml.jaxp.DfDocumentBuilderFactory=com.
documentum.xerces_2_3_0.xerces.jaxp.
DocumentBuilderFactoryImpl
javax.xml.parsers.DocumentBuilderFactory=com.documentum.
xerces_2_3_0.xerces.jaxp.DocumentBuilderFactoryImpl
javax.xml.parser.SAXParserFactory=com.documentum.xerces_2_3_0.
xerces.jaxp.SAXParserFactoryImpl
javax.xml.transform.TransformerFactory=org.apache.xalan.
processor.TransformerFactoryImpl

Adjust the code for the specific Xerces version.

You can also edit the jaxp.properties file to use a different JAXP parser from the one packaged with
DFC. The EMC Documentum XML Application Development Guide contains more information.

Setting permissions for multiple DFC users on Linux

systems
DFC uses an interprocess locking mechanism that uses lock files. This mechanism relies on allowing
different OS users to write the lock file. The Linux operating system creates lock files using the
file mode creation mask (umask) of the current process. Depending on the value of this mask, the
operating system might assign different read/write permissions to the current user and to other users.
In that case, an IOException can occur when a second user tries to acquire the lock. This problem can
occur even if the two users are not logged in at the same time.
In order to avoid this problem, all users must be able to read and write the lock file. You can use the
shell command umask 011 in the application server’s startup script to accomplish this.

Maximum number of results to retrieve per source by

a query search
The maximum number of results to retrieve per source by a query search is set in the parameter
maxresults_per_source of the DFCfull.properties as follows:
dfc.search.maxresults_per_source=350

Copying a keystore from a machine to another does

not work
Copying a keystore from a machine to another does not work by design.

25
Known Issues

WARNING: Keystores are not swappable, copyable or shareable. They are sensitive security
information. If one needs, for any reason, to change a keystore, then stop the client, delete the
keystore, and restart the client. On restart, the client will create a new keystore. All the privileges
associated with the destroyed keystore, however, will be lost.

DFC Copy operation

The copy preference should be set on the copy operation before adding the object to be copied to the
copy operation.
For example:
operation.setCopyPreference (operation.COPY_REFERENCE);
IDfCopyNode node = (IDfCopyNode) operation.add (vDoc);

Documentation
Issue Number Description
DFC-12579 Intelligent Session Management (ISM): The Intelligent Session Management
(ISM) enhancements in Documentum 7.0 helps to improve the overall performance
and scalability through lower context switches on the Content Server and lower
number of active sessions on the Content Server.

ISM feature is enabled by default. It can be turned ON/OFF through dfc.properties,

dfc.compatibility.useD7SessionPooling. When this option is enabled,
on IDfSessionManager.release(), a connection associated with the session is
freed immediately to the level-2 pool. This allows efficient use of the connection
resources. Level-1 pool still caches persistent objects, only connection associated
with the session is freed to level-2 pool for reuse by other user requests. Any
access to the cached objects of level-1 pool, DFC internally re-associates connection
to the session. When this property is enabled, dfc.session.pool.mode should have
default value of level-2. It is recommended not to set dfc.session.pool.mode with
level-1 as it completely disables session pooling.

For backward compatibility, this option can be set to false. When set to false, the
DFC session optimizations will not be used and the session always encapsulates
the underlying connection. This might reduce session scalability as connection
associated with the session is freed to the level-2 pool only when the session
expires (5 seconds by default).
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.

26