OpenText™ Documentum™
Foundation Classes
Release Notes
20.2
Contents
1 Introduction .................................................................................................................................... 4
1.1 Release Notes revision history .................................................................................................. 4
2 About Documentum Foundation Classes ................................................................................... 4
2.1 New features.............................................................................................................................. 4
Support for 64-bit DLL .................................................................................................. 4
3 Packaging and documentation ..................................................................................................... 5
4 Supported environments and compatibility ................................................................................ 5
4.1 Supported systems .................................................................................................................... 5
Hardware requirements ................................................................................................ 5
Operating system ......................................................................................................... 5
Supported systems for Docker environment ................................................................ 6
4.2 OpenText product compatibility ................................................................................................. 6
5 Installation and upgrade notes ..................................................................................................... 7
6 Fixed issues .................................................................................................................................... 7
7 Known issues ................................................................................................................................. 7
8 Contact information ..................................................................................................................... 16
Documentum Foundation Classes 20.2 Release Notes 3
1 Introduction
This Release Notes provide an overview of Documentum Foundation Classes 20.2, including new
features, delivery information, and supported platforms.
OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.
We also recommend that you check OpenText My Support ([Link] for any
patches or documentation updates that may have been posted after the initial release of this product.
Important
Documentum Content Server is now OpenText Documentum Server.
OpenText Documentum Server will be called Documentum Server
throughout this guide.
1.1 Release Notes revision history
Revision date Sections revised Description of revisions
2020-04-02 First release. All new content.
2 About Documentum Foundation Classes
This section provides an overview of Documentum Foundation Classes 20.2.
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 Documentum functionality from within one of your company’s enterprise applications.
• Customize or extend products.
• Write a method or procedure for Documentum Server to execute as part of a workflow or
document lifecycle.
In terms of Documentum functionality, DFC lies between Documentum Server and clients and are
used for server-side business logic and customization.
2.1 New features
Documentum Foundation Classes 20.2 includes the following new features.
Support for 64-bit DLL
Documentum Foundation Classes supports the 64-bit Dynamic-link Libraries (DLLs).
Documentum Foundation Classes 20.2 Release Notes 4
3 Packaging and documentation
Downloads and documentation for Documentum Foundation Classes are available on OpenText My
Support ([Link]
4 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.
Notes
• An OpenText product configuration running on a particular
environment is supported as long as versions of the components
in the environment (for example, operating system, database,
web server, browser, SSO, Directory Servers, and so on) are in
standard/primary support by their vendors.
• Software requirements are listed with release numbers. Software
updates—including patches, Service Packs, and equivalent
updates—sometimes introduce unanticipated changes.
Compatibility with software updates that are not listed here
cannot be guaranteed.
• All certifications provided in this document are relevant to the
current release. Certifications for patches are documented in the
Patch Notes documents published for the patch releases.
4.1 Supported systems
Hardware requirements
This section provides information on the hardware requirements.
Item Requirement
CPU 2 GHz or greater
Memory [1] 4 GB RAM
Disk space [2] 20 GB
[1] The amount of RAM that is available after taking into consideration all other RAM utilization
requirements.
[2] You must have sufficient free disk space to handle temporary content transfer files, which can
vary substantially from one enterprise to another.
Operating system
Operating system Processor
CentOS 7.x (7.5, 7.6), 8.x (8.1) x64
Documentum Foundation Classes 20.2 Release Notes 5
Red Hat Enterprise Linux 6.x (6.10) x64
Red Hat Enterprise Linux 7.x (7.7) x64
SUSE Enterprise Linux 12 SP1 x64
SUSE Enterprise Linux 15 SP1 x64
Ubuntu 16.04.x LTS x64
Ubuntu 18.04.x LTS x64
Windows Server 2016 x64 Edition x64
Windows Server 2019 x64 Edition x64
Notes
• Datacenter and Standard Editions are supported if available.
• X64-bit support only.
• Microsoft Hyper-V is supported for Windows Server 2016 and
2019.
• Red Hat maintains that all minor versions within a major release
are compatible. The number in parenthesis indicates the version
passed during certification.
• WildFly 17 is supported.
• Red Hat OpenJDK 11.0.5 is supported.
• Oracle JDK 11.0.5 is supported.
Supported systems for Docker environment
Application and component Tested vendor version
Docker 18.x
Docker Compose 1.24.0
YAML 3.7
Kernel 3.10
4.2 OpenText product compatibility
The section provides details about which versions of other OpenText products are compatible with this
release of Documentum Foundation Classes 20.2.
Documentum Foundation Classes 20.2 Release Notes 6
Note
For the latest compatibility information for OpenText products, refer to the
Compatibility Matrix ([Link] on
OpenText My Support.
Product name Versions
Documentum Server 20.2, 16.7.1, 16.7
5 Installation and upgrade notes
This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.
Before beginning installation, ensure that your system meets the requirements listed in Chapter 4,
Supported environments and compatibility. After installation, be sure to update your software to the
latest patched release, if any patches are available.
Documentum Platform and Platform Extensions Installation Guide contains installation instructions for
your product. Documentum System Upgrade and Migration Guide contains upgrade information for
your product. These documents are available from OpenText My Support
([Link]
6 Fixed issues
There are no fixed issues in this release.
7 Known issues
The following known issues exist in this release.
Documentum Foundation Classes 20.2 Release Notes 7
Issue number Issue description
DFC-15299 Authentication with password containing double colons (::) results in an error.
Unable to perform the RPS-related privileged operations using WildFly. This is a
DFC-13611
WildFly issue.
Workaround: Add the [Link] file in [Link]\META-INF in
Documentum Server and in [Link]\META-INF (only if WildFly is used as
application server) to give propagate action for RolePermission:
For example:
<xml version="1.0" encoding="UTF-8"?>
<permissions xmlns="[Link]
xmlns:xsi="[Link]
xsi:schemaLocation=[Link]
[Link]
version="7">
<permission>
<class-
name>[Link]</class-name>
<name>*</name>
<actions>propagate</actions>
</permission></permissions>
Certain mock tests with 7.3 DFC might encounter a JVM crash with the exception
DFC-13476
"Expecting a stackmap frame at branch target <<nn>> in method" where nn is
location in the stackmaptable.
The reason for this behavior is the new Java 1.7 bytecode format. In addition to
this, the bytecode verifier now performs more strict checks. DFC 7.3 has
upgraded to latest Java assist for JDK 8 support. However, the latest Java assist
bytecode manipulation still uses JDK 6 mode.
Workaround: Force the use of the old bytecode verifier in JDK 7 by adding the
VM runtime option: -XX:-UseSplitVerifier or setting –noverify
Documentum Foundation Classes 20.2 Release Notes 8
When DFC performs a check in operation, it finds the attribute name as
DFC-12559
ADD_LABEL and not as r_version_label resulting in the "value is too big for
attribute 'ADD_LABEL'. Value UTF-8 length is 71. Maximum length is 32" error
message. This is because DFC adds the version label value to the extended data
attribute ADD_LABEL during the check in operation. This is an expected
behavior as Documentum Server expects the version label value through
extended data attribute ADD_LABEL instead of sysobject's attribute
r_version_label.
When you configure the global repository after installing Documentum Server, a
DFC-11762
DFC_DOCBROKER_EXCLUDED warning message is generated in the JMS and
(CS-41543)
ACS log files. This problem occurs when the Teredo Tunneling Pseudo-Interface
is enabled.
Workaround: 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.
Removing a user using the method [Link] from a group object on
DFC-11635
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 [Link] method when an audit recording is
needed. This workaround only applies to groups with a small number of users,
because the SWAP operation in [Link] is needed to address the
performance issues for groups having a large number of users.
An error in DFC causes performance issues in multi-domain Kerberos
DFC-11529
authentication in Documentum REST Services.
Workaround: To achieve better performance, enable the ticket cache on the
server side.
When a DFC session is reconnected, the server generates an audit event and
DFC-11130
updates the login time.
DFC-10901 An invalid license exception occurs during multi-domain Kerberos authentication.
DFC only supports UTF-8 characters. Any software that uses other character
DFC-10666
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.
Documentum Foundation Classes 20.2 Release Notes 9
For the 7.0 release, changes were done to the DFC cryptography code. Also,
DFC-9900
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-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.
Using PIA, the client is unable to use the getContent() method to read data into
DFC-1376
memory. The recommended approach for reading the data into memory is to use
(DFC-6012)
a code snippet such as the following: [Link]
([Link]())
(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.
A .NET program using DFC reads the [Link] file only when the
DFC-1179
properties file is inside the C:\Documentum\Config folder. Placing the properties
(DFC-5815)
file in another folder in the CLASSPATH does not work.
The getChildRelatives method of a class that implements the IDfPersistentObject
DFC-1073
interface always returns the child_id of the dm_relation object, regardless of the
(DFC-5709)
value of child_label.
If you check out a replica of a document, the system checks the original
DFC-843 (DFC-
document out as well. If you check in the replica, the system checks the original
5480)
back in as well. However, DFC does not support checking out a replica, then
subsequently checking in the original directly.
When an XML document contains the pre-defined XML entities of > and ' or any
DFC-697 (DFC-
numeric entity in an XML attribute, the entity is expanded in an exported
5334)
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 ' ¥"/> will be exported as
<technology transfer="<<Analog> & "Digital ' Y/> where Y is the symbol for
Yen.
The DFC IDfExportOperation does not preserve the line sequence from original
DFC-695 (DFC-
XML content. For example, if the original sequence of elements is:
5332)
<books><book>
Sequence after export:
<books><book>
While this behavior might be unexpected, the XML content is still valid.
Documentum Foundation Classes 20.2 Release Notes 10
It is not possible to lock a rendition to prevent it from being deleted. For example,
DFC-452 (DFC-
when you try to export an object, and at the same time another user with
5093)
appropriate permission over the object deletes it, the deletion succeeds and you
will get an error.
DFC does not check, before deleting a document, to see if that document is a
NA
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.
You cannot use classes of the [Link] package within
NA
transactions in a multi-threaded environment.
DFC supports some OLE compound documents on Windows platforms. DFC
NA
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.
If you add an object to an IDfExportOperation more than once, but with different
NA
formats, the operation exports the object to a single file on the file system.
Workaround: Use separate export operations for the different formats.
The getDataType method of the IDfAttr interface and the getAttrDataType
NA
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 Documentum 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 methods.
The equals method of an IDfTime object returns a value of true if the method’s
NA
argument represents a time that is within one second of the time that the object
represents.
If you use an import operation to import a Windows file system folder and its
NA
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.
Documentum Foundation Classes 20.2 Release Notes 11
The xml:base attribute as specified by the XLINK language is not supported. You
NA
cannot import XML files containing this attribute. In particular, you cannot import
packages that use the SCORM standard for web-based learning systems.
DFC 5.3 uses a newer version of Xalan than previous DFC versions used. The
NA
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.
In an environment in which two Documentum Server instances control
NA
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.
The file download dialog box does not appear when attempting to perform file
NA
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.
To change the Internet Explorer 7, 9, 10, and 11 security settings to checkout and
view files using Webtop in Internet Explorer:
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.
Importing a document on Macintosh platform does not import (and later export)
NA
the 'File Comments' of the document, viewable through the 'Get Info...' operation.
The copy operation from one SSO to another SSO does not work.
NA
Documentum Foundation Classes 20.2 Release Notes 12
DFC validation methods obtain the locale from sessionconfig.session_locale and
NA
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.
Expression evaluation in native code will not work because it requires loading 32-
NA
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
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
Some DFC operations need to store state information. DFC can use either a file
NA
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.
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
DFC provides a mechanism for scanning and patching OLE links in Microsoft
NA
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.
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
If you are using application access control tokens configured to be valid only
NA
when sent from applications on particular host machines, you must set the
[Link] key in the [Link] 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.
Documentum Foundation Classes 20.2 Release Notes 13
Some operating systems might install a [Link] file, or that directory might
contain a [Link] file that was intentionally placed there. The purpose of
the [Link] file is to specify the way DFC implements the JAXP parser, by
providing the class names for the JAXP factories. An empty [Link] file
might cause DFC to use the default implementation provided by the operating
system. A [Link] file in the JAVA_HOME/lib/ directory overrides the
information in the manifest in [Link], 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: [Link]
In the case of a WDK application, the application server's error log shows the
following error:
[Link]:
Provider null could not be instantiated: [Link]
To resolve this problem, you can do one of the following:
• Rename the [Link] file on your local system
• Add lines similar to the following to the [Link] file:
[Link]=[Link].
[Link] [Link].
DfSAXParserFactory=[Link].
xerces_2_3_0.[Link]
[Link].
[Link]=com.
documentum.xerces_2_3_0.[Link].
DocumentBuilderFactoryImpl [Link].
DocumentBuilderFactory=[Link].
xerces_2_3_0.[Link]
[Link].
SAXParserFactory=[Link].xerces_2_3_0.
[Link] [Link].
TransformerFactory=[Link].
[Link]
Adjust the code for the specific Xerces version. You can also edit the
[Link] file to use a different JAXP parser from the one packaged with
DFC.
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
Documentum Foundation Classes 20.2 Release Notes 14
DFC uses an interprocess locking mechanism that uses lock files. This
NA
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.
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
The maximum number of results to retrieve per source by a query search is set in
NA
the parameter maxresults_per_source of the [Link] as follows:
[Link].maxresults_per_source=350
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
Copying a keystore from a machine to another does not work by design.
NA
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.
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
The copy preference should be set on the copy operation before adding the
NA
object to be copied to the copy operation.
For example:
[Link] (operation.COPY_REFERENCE);
IDfCopyNode node = (IDfCopyNode) [Link] (vDoc);
This limitation only applies when a stand-alone DFC installer is used on Windows
operating systems. This limitation does not apply when building web applications
using the bundled version of DFC ([Link]).
Documentum Foundation Classes 20.2 Release Notes 15
8 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
OpenText My Support: [Link]
For more information, visit [Link]
Copyright © 2020 Open Text. All Rights Reserved.
Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit [Link]
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept
no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.
16
