OpenText™ Documentum™

Foundation Services CE 21.3

Release Notes
Contents
1 Introduction .................................................................................................................. 3
1.1 Release Notes revision history ..................................................................................... 3
2 About Documentum Foundation Services 21.3 ................................................................ 3
2.1 New features in 21.3 .................................................................................................. 4
2.1.1 Support for new service ................................................................................... 4
2.2 New features in 21.2 .................................................................................................. 5
2.2.1 Support for new services ................................................................................. 5
2.2.2 Support for Tomcat packaged with Java Method Server........................................ 5
3 Packaging and documentation ....................................................................................... 5
4 Supported environments and compatibility ..................................................................... 5
4.1 Supported systems .................................................................................................... 6
4.1.1 Hardware requirements ................................................................................... 6
4.1.2 Application server requirements ........................................................................ 6
4.1.3 External web servers....................................................................................... 8
4.1.4 Operating environments................................................................................... 9
4.1.5 DFS client interoperability layers ..................................................................... 10
4.1.6 Cloud platforms ............................................................................................ 11
4.2 OpenText product compatibility .................................................................................. 11
5 Installation and upgrade notes ..................................................................................... 12
6 Fixed issues................................................................................................................ 12
6.1 Fixed issues in 21.3.................................................................................................. 12
6.2 Fixed issues in 21.2.................................................................................................. 12
7 Known issues.............................................................................................................. 12
8 Contact information..................................................................................................... 17

Documentum Foundation Services 21.3 Release Notes 2

1 Introduction
This Release Notes provide an overview of Documentum Foundation Services 21.3, including new
features, delivery information, and supported platforms.

OpenText recommends that you read this 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 (https://support.opentext.com) for any
patches or documentation updates that may have been posted after the initial release of this product.

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

April 2021 First release. All new content.

July 2021 All sections. Updated for the 21.3 release.

2 About Documentum Foundation Services 21.3

This section provides an overview of Documentum Foundation Services 21.3.

Documentum Foundation Services provides a set of technologies that enables service-oriented

programmatic access to the Documentum Server platform and related products. Documentum
Foundation Services is a service layer over a Documentum Foundation Classes c lient, which
connects to one or more repositories managed by Documentum Server.
The following table lists some of the technologies that are included in Documentum Foundation
Services:

Documentum Foundation Services 21.3 Release Notes 3

 Technology Description

Web services The Documentum Foundation Services web services are Simple Object
Access Protocol (SOAP)/Web Service Definition Language (WSDL)-
based services deployed in a supported Java servlet container.

Java services Documentum Foundation Services can also be deployed as a local Java
API using class libraries provided in the Software Development Kit (SDK).
In a local application, the Documentum Foundation Services Java
services run in the same Java Virtual Machine (JVM) as the service
consumer.

Data model The Documentum Foundation Services WSDL interface and

corresponding class libraries define a service-oriented data model for
representing objects and properties, and for profiling service operation
options.

Java Optional client-side libraries for Java consumers of Documentum

productivity Foundation Services.
layer

.NET Optional client-side libraries for .NET consumers of Documentum

productivity Foundation Services.
layer

Tools for Service-generation tools based on Java application programming

generating interface (API) for XML based Web Services (JAX-WS), and Ant, which
services generate deployable DFS services from annotated source code, or from
WSDL. These tools also generate client-side runtime support for Java
clients. Client-side .NET classes are generated using the Documentum
Foundation Services Proxy Generator utility.

2.1 New features in 21.3

Documentum Foundation Services 21.3 includes the following new feature:

2.1.1 Support for new service

The following new service method is supported:
• completeWorkitem

Documentum Foundation Services 21.3 Release Notes 4

2.2 New features in 21.2
Documentum Foundation Services 21.2 includes the following new features.

2.2.1 Support for new services

The following new service methods are supported:
• registerEvent
• unRegisterEvent
• getPermission
• getLinkedRepeatingString
• hasAttributes
• removeRendition
• markVersion
• updateNonCurrentVersion
• saveAsNew
• dateTimeToIDfTime
• getDCTMLoginTicket
• terminateWorkflow

The OpenText Documentum Enterprise Content Services Reference Guide contains more
information.

2.2.2 Support for Tomcat packaged with Java Method Server

Documentum Server supports Tomcat packaged with Java Method Server. Starting with the 21.2
release, Tomcat is packaged with Java Method Server instead of WildFly.

3 Packaging and documentation

Downloads and documentation for Documentum Foundation Services are available on OpenText My
Support (https://support.opentext.com).

4 Supported environments and compatibility

This section provides details about supported platforms, systems, and versions for Documentum
Foundation Services 21.3.

The Supported environments and compatibility chapter in OpenText Documentum Foundation

Services 21.2 Release Notes contains details about supported platforms, systems, and versions for
Documentum Foundation Services 21.2.

Documentum Foundation Services 21.3 Release Notes 5

 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.
• Sof tware 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

4.1.1 Hardware requirements

Item Requirements

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.

4.1.2 Application server requirements

Documentum Foundation Services 21.3 Release Notes 6

Operating system/ Application server
processor
Apache Apache Pivotal Pivotal JBoss EAP IBM Liberty WildFly Oracle
Tomcat Tomcat vFabric tc vFabric tc 7.3 20.x 17.x, 19.x WebLogic
8.5.x 9.x Server 3.2.x Server 4.x 14.1.1.x

CentOS 7.x (7.6, 7.7),

X X X X X
8.x (8.2, 8.3)

RHEL 6.x (6.10)

X X X

RHEL 7.x (7.7, 7.8),

X X X X X X X X
8.x (8.2, 8.3)

SUSE 12 SP4, SP5 X X X X X

SUSE 15 SP1, SP2 X X X

Ubuntu 16.04.x,
X X X X
18.04.x, 20.04.x

Windows Server 2016 X X X X

Windows Server 2019 X X X X X X

Documentum Foundation Services 21.3 Release Notes 7

 Notes
• X indicates supported combination.
• Blank cell indicates unsupported combination.
• x64 = 64-bit Architecture which includes AMD64 & Intel 64.
• x64 processor of operating system is supported.
• x64 edition of Windows Server and Red Hat Enterprise Linux operating
systems is supported.
• RHEL indicates Red Hat Enterprise Linux operating system.
• Enterprise Linux edition of SUSE is supported.
• Datacenter and Standard Editions of Windows Server are supported.
• Microsoft Hyper-V for Windows Server is supported.
• To recognize third-party certifications of RHEL and SLES compatible
Linux distributions, OpenText will provide limited support based on
publicly published claims from the alternative Linux distribution vendor.
OpenText recommends using your discretion to determine the risk of
the third-party compatibility claim. In case of a Service Request,
OpenText Global Technical Services will attempt to reproduce and
resolve the incident on the related certified environment. For example,
OpenText Global Technical Services will attempt to reproduce the
problem on RHEL for Oracle Linux. If the root cause analysis
demonstrates that the problem is due to incompatible distributions, you
must engage the alternative Linux vendor for continued investigation
and resolution.
• Red Hat maintains that all minor versions within a major release are
compatible. The number in parentheses indicates the version passed
during certification.
• If you use the JAX-WS library to build a custom service in
Documentum Foundation Services, Java versions 1.7.x are not
supported. In this case, you must use Java versions 1.6.x.
• Only Oracle JDK is supported for the Oracle WebLogic installation.
• Supports 64-bit version of application server.
• Supports only 64-version of JDK.
• Supports 64-bit version of operating system in native mode.
• Red Hat OpenJDK 11.0.11 is supported.
• Oracle JDK 11.0.11 is supported.
• AdoptOpenJDK 11.0.11 (HotSpot) is supported.

4.1.3 External web servers

This section describes the certified external web servers supported by the server portion of DFS.

Documentum Foundation Services 21.3 Release Notes 8

 External web server Clustering support

Apache 2.4.x Failover, Load Balancing

Microsoft Internet Information Server (IIS) 8.0 Failover, Load Balancing

Microsoft Internet Information Server (IIS) 8.5 Failover, Load Balancing

IBM HTTP Server Version (8.5.5.x) Failover, Load Balancing

Notes
• The listed web servers are supported when available on
version of operating system specified in the Application
server environment requirements table and also is
supported by the application server.
• The listed web servers are supported with single sign-on
supported by Documentum Foundation Services and if
the environment is supported by the single sign-on
products.
• Clustering is supported for a standalone DFS server and
requires sticky sessions.
• No clustering (or failover) support for DFS installed with
Documentum Server.
• Failover is supported for a standalone DFS server,
provided that client applications do not use cached
queries or registered service contexts.
• Failover is not supported for UCF operation, both DFS-
orchestrated UCF and client-orchestrated UCF.

4.1.4 Operating environments

4.1.4.1 Virtual environments

• Microsoft Azure
• Amazon Web Services
• Citrix XenApp 7.15, 7.5, 7.6
• Docker 18.x, 19.x, 20.x
• Microsoft Hyper-V
• VMware vCenter 5.5, 6.0, 6.5, 6.7
• VMware vCloud Director 5.1, 5.5
• VMware Virtual Desktop Infrastructure
• VMware vSphere 5.5, 6.0, 6.5, 6.7
• VMware vSphere Hypervisor (ESXi) Server 5.5, 6.0, 6.5, 6.7

Documentum Foundation Services 21.3 Release Notes 9

 Notes
• Documentum fully supports all our products running on a
guest operation system supported by the version of VMware
products listed as long as that same version of operating
system is supported by the appropriate OpenText
Documentum product.
• VMware ESXi 5.0 will install and run only on servers with 64-
bit x86 CPUs.
• Microsoft Azure and Amazon Web Services are supported
virtualization environments.
• The f ollowing OpenText/public cloud providers are supported
with underlying Kubernetes orchestration and HELM
packaging: OTK, Microsoft Azure, Amazon Web Services,
Google Cloud Platform, and Red Hat OpenShift.
• Docker image/container and supported third-party
components is: CentOS 8.x/Red Hat OpenJDK
11.0.9/Apache Tomcat 9.x

4.1.4.2 Cluster environments

• Oracle RAC for all supported version on Oracle

• Oracle multitenant containers

4.1.5 DFS client interoperability layers

This section details the requirements for the client-side interoperability layers of DFS.

4.1.5.1 .NET

The .NET interoperability layer requires .NET 4.1 to be installed on the client.

4.1.5.2 JAVA

The Java interoperability layer has been certified for use within these application server / operating
system combinations:

• Apache Tomcat 8.5.x, 9.x

• JBoss EAP 7.3
• Pivotal vFabric tc Server 3.2.x, 4.x
• IBM Liberty 20.x

Documentum Foundation Services 21.3 Release Notes 10

4.1.6 Cloud platforms
4.1.6.1 Operating systems

• Red Hat Enterprise Linux 7.0 and later

• CentOS
• Ubuntu

4.1.6.2 Platforms

• Private cloud
o OpenText cloud platform
• Public cloud
o Microsoft Azure cloud platform
o Google Cloud Platform
o Amazon Web Services cloud platform

4.1.6.3 Application and components versions

Application and component Tested vendor version

Docker 18.x, 19.x, 20.x

Docker Compose 1.29.1

YAML 3.7

Kernel 3.1

Helm 3.x (3.6.1)

Kubernetes (client) Refer to OpenText Documentum Server

Release Notes.

Kubernetes (server) Refer to OpenText Documentum Server

Release Notes.

4.2 OpenText product compatibility

The section provides details about which versions of other OpenText products are compatible with this
release of Documentum Foundation Services 21.3.

Note
For the latest compatibility information for OpenText products, refer to the
Compatibility Matrix (https://knowledge.opentext.com/go/matrix) on
OpenText My Support.

Product name Versions

Documentum Server 21.3, 21.2, 21.1, 20.4, 20.3, 20.2, 16.7.1, 16.7, 16.4, 7.3

Documentum Foundation Services 21.3 Release Notes 11

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.

OpenText Documentum Platform and Platform Extensions Installation Guide contains installation
instructions for your product. This document is available from OpenText My Support
(https://support.opentext.com).

6 Fixed issues
6.1 Fixed issues in 21.3
There are no fixed issues in this release.

6.2 Fixed issues in 21.2

There are no fixed issues in this release.

7 Known issues
The following known issues exist in this release.

Issue number Issue description

DFS-5966 UCF installation fails with the following error:

com.emc.documentum.fs.rt.ServiceInvocationRuntimeException:
<UCF_HOME>\shared\bin\<BUILD>\UCFWin32JNI.dll: Can't find dependent
libraries; java.lang.UnsatisfiedLinkError at
*com.emc.documentum.fs.rt.impl.pip*e.DfsPipe.process(DfsPipe.java:104)
Visual Studio used to build the UCF and DFS dlls are upgraded to 2013.
Workaround: Install Microsoft 2013 redistributable x32/x64 to load the DLLs.

DFS-5529 When user tries to add first comment to a document using DFS, the user
requires WRITE permission. After the comment is applied, subsequent
modification to the comments requires only RELATE permission.

Documentum Foundation Services 21.3 Release Notes 12

 Issue number Issue description

DFS-5118 Namespace declaration on Envelope layer in SOAP message.

Workaround:
1. Download the jax-ws2.2.8 jar files.
2. Stop the DFS server.
3. Take a backup of your DFS lib folder. You will need this folder to revert
any changes that you make.
4. Copy all jar files that you have downloaded in Step 1 to the DFS lib folder.
Select Yes to overwrite current files.
5. Start the DFS server.

DFS-3432 When a service is generated using the Documentum Foundation Services

service-generation tools, artifacts generated by JAX-WS are archived in JAR
files if the data class resides in the same package as the service endpoint.
For example, if a service uses the com.service.SomeService,
com.service.DataClassA, and com.service.DataClassB data objects, the
following results occur:
• DataClassB will extend DataClassA
• The service will have the SomeService.theOnlyMethod(DataClassB)
method
• While generating JAX-WS artifacts, the generated DataClassA is not
deleted. This generated class is archived in the resulting JAR file, and not
in the client defined class.
In this case, when generating JAX-WS artifacts, the generated DataClassA is
not deleted. This generated class is archived in the resulting JAR file, rather
than the client defined class.
To repair the JAR file, remove the class generated by JAX-WS and replace it
with the client-defined class file.

DFS-3429 The Java Development Kit (JDK) does not compensate for Daylight Savings
Time for dates before 1981, and it compensates incorrectly for dates from
1981 through 1990. This Documentum Foundation Services limitation only
impacts data with dates prior to 1990.

DFS-3427 When creating custom services, a conflict occurs when you have two services
containing the following namespaces: http://a.b.c.d and http://b.c.d.a. When
JAX-WS tries to generate the client proxies for these two services, they are
generated in the same package (d.c.b.a) and you can call the first service in
the classpath. Avoid assigning namespaces in a format that is specified in the
description of this issue.

DFS-3425 In clustered environments, failover is not supported for registered service

contexts and cached queries. If you need failover support, do not register
service contexts, or use cached queries.

Documentum Foundation Services 21.3 Release Notes 13

 Issue number Issue description

DFS-3423 Only services that are executed in the same server-side process can share a
registered service context. Services are deployed in the same EAR file on the
application server. This limitation implies that the client must be aware of the
physical location of the services which it invokes. In addition, the client must
manage service context sharing based on shared physical locations.
Registration of service context is not required. To avoid this problem, do not
register the service context.

DFS-3421 The JAX-WS implementation uses the thread context class loader, rather than
the class loader of the executing class. Therefore, when calling a
Documentum Foundation Services service from a Business Object Framework
(BOF) module or Java server method, set the current class loader to the class
loader of the module. It is described in the following procedure:
1. Save the ContextClassLoader of the current thread.
ClassLoader oldContextClassLoader =
Thread.currentThread().getContextClassLoader();
2. In a try block, set the current class loader to the class loader in the class
of the calling object before calling the Documentum Foundation Services
service.
try { ClassLoader classClassLoader =
this.getClass().getClassLoader();
Thread.currentThread().setContextClassLoader
(classClassLoader); // ...call DFS service }
3. In a finally block, reset the class loader to the previously saved thread
class loader.
finally {Thread.currentThread().setContextClassLoader
(oldContextClassLoader); }

DFS-3419 The following limitations apply to Kerberos support in this release:

• Due to the multi-tiered nature of Documentum Foundation Services
applications, Kerberos integration is based on delegated authentication.
All Kerberos tokens provided to Documentum Foundation Services
through the web services API must be “forwardable”. The local Java API
accepts only Kerberos Ticket Granting Tickets (TGTs).
• Documentum Foundation Services services do not accept Simple and
Protected GSSAPI Negotiation Mechanism (SPNEGO) tokens. However,
the Kerberos utility provided with the DFS Software Development Kit
(SDK) includes a method for unwrapping SPNEGO tokens.
• Registering a ServiceContext with Kerberos credentials is not supported.
• Kerberos-based message level security is not supported.
• Support for .NET integration is limited to remote web services API (in the
client productivity layer). There is no Kerberos Utility for .NET.
• Wrapped GSSAPI Kerberos tokens are not supported.

DFS-3044 For Oracle on Linux, count(*) in a query returns a double. This issue is
caused by Oracle on Linux.

Documentum Foundation Services 21.3 Release Notes 14

 Issue number Issue description

DFS-1383 The DFS .NET client is based on WCF (Windows Communication

Framework), which provides three modes for MTOM content transfer: buffer,
streaming, and chunk. For streaming and chunk modes, WCF requires that
the corresponding service operation (such as get or create) take only one
argument (the input stream). This conflicts with the design of DFS, such that
DFS can only use the MTOM buffer mode with a .NET client. This results in
unusually high memory requirements.
Workaround: There are several options for working around this limitation:
• First, for content download operations, enable ACS/BOCS and make use
of it. To ensure that the urlContent type is returned by DFS, use the
urlReturnPolicy setting. The client can use the urlContent returned by DFS
to request content transfer from the ACS server.
• For content upload operations, use UCF as the content transfer mode.
UCF will orchestrate content transfer in both directions between the client
and the ACS server.
• Ensure that both the DFS .NET client and JVM that runs the DFS server
have enough memory to buffer the content.
For additional detail on this limitation, refer to the Documentum Platform and
Platform Extensions Installation Guide.

DFS-687 JBoss log generates error messages although DFS services are available.
This is an issue in JBoss and not a Documentum Foundation Services issue.
The resolution is to change the log level of java.util.logging to WARNING:
edit $JAVA_HOME/jre/lib/logging.properties,
change ".level= INFO" to ".level= WARNING"

DFS-684 The current process of defining a new resource bundle consists of defining a
new property in dfs-runtime.properties, incrementing the index of the
property.
In dfs-runtime.properties:
resource.bundle = dfs-messages resource.bundle.1
= dfs-services-messages resource.bundle.2
= dfs-bpm-services-messages
In local-dfs-runtime.properties:
resource.bundle.3 = my-custom-services-messages
The limitation of this approach is that if a new resource bundle is required for
core services in a future release, it can be defined as "resource.bundle.3"
and the one defined in local-dfs-runtime.properties will override it.
This approach can cause a future migration issue.

Documentum Foundation Services 21.3 Release Notes 15

 Issue number Issue description

DFS-65 When generating multiple services in the same package that have the same
method names, the generation on the client side overwrites the generated
classes where there are name conflicts. The services must be in separate
packages or have different method names.

DFS-30 When you create custom services, extending the Profile class or subclasses is
not permitted. For new services, you can use properties (passed to the service
in Operation Options or in the service context) as an alternative to creating
new profiles.

DC-5809 If there is not enough disk space on UCF Java or .Net client, the following
message is displayed:
com.documentum.ucf.common.UCFException: There is not
enough space on the disk
When this error occurs, a partial file is created and is not deleted.

Documentum Foundation Services 21.3 Release Notes 16

8 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

OpenText My Support: https://support.opentext.com

For more information, visit www.opentext.com

Copyright © 2021 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
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.

17