OpenText ™ Documentum ™

Content Server
Version 7.3, Patch 35

Patch Notes
 Legal Notice

This documentation has been created for software version 7.3, Patch 35.
It is also valid for subsequent software versions as long as no new document version is shipped with
the product or is published at https://knowledge.opentext.com.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2020 Open Text. All Rights Reserved.
Trademarks owned by Open Text.
Adobe and Adobe PDF Library are trademarks or registered trademarks of Adobe Systems Inc. in
the U.S. and other countries.
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.
 Table of Contents

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

Chapter 1 Compatibility Updates ................................................................................. 7

Limited Support for Compatible Linux Distributions .......................................... 8

Chapter 2 Patch Requirements .................................................................................... 9

Chapter 3 Installation ................................................................................................... 11

Windows Platform ............................................................................................ 11
All UNIX Platforms .......................................................................................... 12
Prerequisite to Upgrade to Content Server 7.3 on AIX ..................................... 13
Encrypting Keystore Password After WildFly SSL Configuration ......................... 13
Upgrading JDK and WildFly ............................................................................. 14
Anonymous SSL Communication for Content Server and DFC-based
Clients ............................................................................................................. 16
Upgrading to ODBC Driver 17.2 for SQL Server ................................................. 16

Chapter 4 Docker Patch ............................................................................................... 19

Chapter 5 Uninstalling the Patch ................................................................................. 23
Chapter 6 Fixed Issues ................................................................................................ 25
Patch 35 Fixed Issues List .................................................................................. 25
Patch 33 Fixed Issues List .................................................................................. 25
Patch 32 Fixed Issues List .................................................................................. 26
Patch 30 Fixed Issues List .................................................................................. 27
Additional Information for Fixed Issues in Patch 30 ........................................ 27
CS-119674 ................................................................................................ 27
Patch 28 Fixed Issues List .................................................................................. 27
Patch 25 Fixed Issues List .................................................................................. 28
Patch 23 Fixed Issues List .................................................................................. 29
Patch 21 Fixed Issues List .................................................................................. 29
Additional Information for Fixed Issues in Patch 21 ........................................ 30
CS-118009 ................................................................................................ 30
Patch 20 Fixed Issues List .................................................................................. 30
Patch 19 Fixed Issues List .................................................................................. 30
Patch 18 Fixed Issues List .................................................................................. 31
Additional Information for Fixed Issues in Patch 18 ........................................ 31
CS-117584 ................................................................................................ 31
Patch 17 Fixed Issues List .................................................................................. 31
Patch 16 Fixed Issues List .................................................................................. 32

3
Table of Contents

Patch 15 Fixed Issues List .................................................................................. 32

Additional Information for Fixed Issues in Patch 15 ........................................ 32
CS-59362 .................................................................................................. 32
CS-59366 .................................................................................................. 33
CS-58421 .................................................................................................. 34
Patch 14 Fixed Issues List .................................................................................. 34
Patch 13 Fixed Issues List .................................................................................. 34
Patch 12 Fixed Issues List .................................................................................. 35
Patch 11 Fixed Issues List .................................................................................. 35
Patch 10 Fixed Issues List .................................................................................. 35
Patch 09 Fixed Issues List .................................................................................. 35
Patch 08 Fixed Issues List .................................................................................. 36
Patch 07 Fixed Issues List .................................................................................. 36
Patch 06 Fixed Issues List .................................................................................. 36
Patch 05 Fixed Issues List .................................................................................. 37
Patch 04 Fixed Issues List .................................................................................. 37
Additional Information for Fixed Issues in Patch 04 ........................................ 38
CS-56968 .................................................................................................. 38
Patch 03 Fixed Issues List .................................................................................. 38
Additional Information for Fixed Issues in Patch 03 ........................................ 39
CS-51037 .................................................................................................. 39
Patch 02 Fixed Issues List .................................................................................. 39
Patch 01 Fixed Issues List .................................................................................. 40

Chapter 7 Known Issues .............................................................................................. 41

4
 Revision History

Revision Date Description

November, 2020 Patch 35 release.
May, 2020 Patch 33 release.
February, 2020 Patch 32 release.
November, 2019 Patch 30 release.
August, 2019 Patch 28 release.
July, 2019 Updated about the Red Hat OpenJDK support
in Chapter 1, Compatibility Updates.
May, 2019 Patch 25 release.
February, 2019 Patch 23 release.
January, 2019 Updated the information about iJMS in Chapter
1, Compatibility Updates.
December, 2018 Patch 21 release.
November, 2018 Patch 20 release.
October, 2018 Patch 19 release.
September, 2018 Patch 18 release.
August, 2018 Patch 17 release.
July, 2018 Patch 16 release.
June, 2018 Patch 15 release.
May, 2018 Patch 14 release.
April, 2018 Patch 13 release.
March, 2018 Patch 12 release.
February, 2018 Patch 11 release.
January, 2018 Patch 10 release.
December, 2017 Patch 09 release.
November, 2017 Patch 08 release.
September, 2017 Patch 07 release.
August, 2017 Patch 06 release.
July, 2017 Patch 05 release.
June, 2017 Patch 04 release.

5
Revision History

Revision Date Description

May, 2017 Patch 03 release.
April, 2017 Patch 02 release.
March, 2017 Patch 01 release.

6
 Chapter 1
Compatibility Updates

All certifications provided in this document are relevant to the current patch release.
After you apply this patch, your product's compatibility with other products will be changed
as follows:

Product Release Effective Patch Release

• Red Hat OpenJDK 8.0 Update 265 [4] Patch 35

• Oracle JDK 8.0 Update 271 [4] [8]

• Red Hat Enterprise Linux 7.9

Oracle JDK 8.0 Update 251 [4] Patch 33

• Red Hat OpenJDK 8.0 Update 242 [4] Patch 32

• Oracle JDK 8.0 Update 241 [4]

• Red Hat Enterprise Linux 7.7

• WildFly 17 [7] Patch 30

• Microsoft SQL Server 2016 SP2 [1]

• Oracle JDK 8.0 Update 221 [4] Patch 28

• Red Hat OpenJDK 8.0 Update 222 [4]

• OpenJDK 8.0 Update 212 [4] [6] Patch 25

• Microsoft Active Directory 2016

• Red Hat Enterprise Linux 6.10

• Oracle JDK 8.0 Update 202 [4] Patch 23

• ODBC 17.2 [5]

• Oracle 12.2.0.1 Patch 19

• SMB 2.0, 3.0

• IBM Cloud Object Storage [3]

7
Compatibility Updates

Product Release Effective Patch Release

WildFly 11 Patch 17
iJMS 16.4 Patch 01 Patch 16

• Amazon S3 [2] Patch 15

• Dell EMC Data Domain 6.0, 6.1

• Microsoft SQL Server 2012 SP4 Patch 14

• Microsoft SQL Server 2016 SP1 [1]

[1] For additional information, see CS-55857 in Chapter 7, Known Issues.
[2] For additional information, see Additional Information for Fixed Issues in Patch 15, page 32.
[3] Bucket level WORM is supported on IBM Cloud Object Storage.
[4] For additional information about anonymous SSL communication, see Anonymous SSL
Communication for Content Server and DFC-based Clients, page 16.
[5] For additional information, see Upgrading to ODBC Driver 17.2 for SQL Server, page 16.
[6] Supports Red Hat OpenJDK also.
[7] For additional information, see Upgrading JDK and WildFly, page 14.
[8] You must install Microsoft Visual C++ 2015 (or later) Redistributable package.

Limited Support for Compatible Linux

Distributions
To recognize third-party certifications of RHEL and SLES compatible Linux distributions, limited
support is available based on publicly published claims from the alternative Linux distribution
vendor. Customers must use their discretion to determine the risk of the third-party compatibility
claim. In case of a Service Request, Support will attempt to reproduce and resolve the incident on
the related certified environment. For example, Support will attempt to reproduce the problem on
RHEL for Oracle Enterprise Linux. If the root cause analysis demonstrates that the problem is due to
incompatible distributions, the customer must engage the alternative Linux vendor for continued
investigation and resolution.

8
 Chapter 2
Patch Requirements

For product system requirements, refer to knowledge.opentext.com/go/matrix.

This patch only requires that you have the product installed.

9
Patch Requirements

10
 Chapter 3
Installation
Note: It is recommended to use the Content Server Patch Installer to apply the patch.

Windows Platform
1. Ensure that your system meets any requirements listed in Chapter 2, Patch Requirements.
2. Perform the following steps before running the Content Server Patch Installer:
a. Stop the Java Method Server.
b. Stop the Content Server.
c. Take a backup of files in the %DOCUMENTUM% directory.
3. To apply the patch using the Patch Installer:
a. If you are installing the patch using the patch installer for the first time in an upgraded
environment, rename patch-info.xml, if it is available in the $DOCUMENTUM/patch/
folder.
b. Download the patch package file for Windows and extract it to a temporary directory.
c. Run the following command to start the patch installation:
patch.exe LAX_VM %DOCUMENTUM%\java64\<JAVA_VERSION>\jre\bin\java.exe

Note:
• Change the full name of java.exe accordingly in the command if your Documentum
program directory is different.
• Ensure that you do not rename patch.exe before running the Patch Installer.
• By default, patch.exe runs in the GUI mode. If you want to run it in the Console mode,
add an argument “-i console”:
patch.exe LAX_VM <full name of a 1.8+ java> -i console

4. Perform the following tasks after the installation is complete:

a. Start the Content Server.
b. Start the Java Method Server.
c. Start the Index Agent and Index Server (if it exists).
5. Run the following command from %DOCUMENTUM%\patch\bin directory to deploy
MailApp.dar into the repository:
repositoryPatch.bat docbaseName installOwnerName

Note: Run this command for each repository in the environment.

11
Installation

All UNIX Platforms

1. Be sure that your system meets any requirements listed in Chapter 2, Patch Requirements.
2. If you are installing the patch using the patch installer for the first time in an upgraded
environment, rename patch-info.xml, if it is available in the $DOCUMENTUM/patch/ folder.
3. Before applying the patch:
a. Stop the Java Method Server.
b. Stop the Content Server.
c. Take a backup of files in the $DOCUMENTUM directory.
4. To install the patch using the patch installer:
a. Download the patch package file for Unix and extract it to a temporary directory.
b. Grant execute permission to the files.
c. Run one of the following commands to set the Content Server environment to the current
terminal:
$DOCUMENTUM/product/7.3/bin/dm_set_server_env.sh
Or
$DOCUMENTUM/product/7.3/bin/dm_set_server_env.csh

d. Start the patch installation with the following command and complete the installation:
• For Linux:
patch.bin LAX_VM $DOCUMENTUM_SHARED/java64/<JAVA_VERSION>/jre/bin/java

• For Solaris:
patch.bin LAX_VM $DOCUMENTUM_SHARED/java64/<JAVA_VERSION>/bin/sparcv9/java

• For AIX:
patch.bin LAX_VM $DOCUMENTUM_SHARED/java64/<JAVA_VERSION>/jre/bin/java

Note:
• Ensure that you select the linux_ora.tar.gz file as the patch Resource File entry to
proceed with Patch installation.
• The Patch installation will run in the GUI mode if your environment supports it.
Otherwise, the Patch installation automatically switches to the Console mode. If you
want to force patch.bin to run in console mode, add an argument -i console to
the command:
patch.bin LAX_VM <full name of a 1.8+ java> -i console

• Ensure that you do not rename patch.bin before running the patch installer.
e. Perform the following tasks after the installation is completed:
a. Start the Content Server.
b. Start the Java Method Server.
c. Start the Index Agent and Index Server (if they exist).

12
 Installation

Note:
• Replace $DOCUMENTUM with its actual value.
• Refer to the version.txt file available at the root location of the zip or tar file of your
product to determine the version of the patch you have currently installed.
5. Run the following command from the $DOCUMENTUM/patch/bin directory to deploy
MessagingApp.dar into the repository:
repositoryPatch.sh docbaseName installOwnerName

Note: Run this command for each repository in the environment.

Prerequisite to Upgrade to Content Server 7.3 on AIX

Perform the following steps before upgrading to Content Server 7.3 on AIX:
1. Ensure to stop all the Documentum processes.
2. Rename the $DOCUMENTUM/dba/auth/libkerberos.so file and then proceed with the
upgrade process.

Encrypting Keystore Password After WildFly

SSL Configuration
Perform the steps to configure WildFly for SSL as described in Content Server chapter in Documentum
Platform and Platform Extensions Installation Guide.
Then, perform the following:

Encrypting keystore password using JCEKS and vault

1. Build a keystore for JMS. The keystore must be in the JKS format. For example:
keytool -genseckey -alias Vault -storetype jceks
-keyalg AES -keysize 128 -storepass password_j
-keystore C:\keystore\JKSVAULT1.store

2. Store the WildFly keystore password in the JKS keystore. Run vault.bat from the WildFly bin
directory.
vault.bat --keystore C:\keystore\JKSVAULT1.store
--keystore-password password_j
--alias Vault --vault-block vb --attribute jca-pass
--sec-attr password --enc-dir C:\keystore\
--iteration 95 --salt ABCD1234
...
...
</extensions>
<vault>
<vault-option name="KEYSTORE_URL" value="C:\keystore\JKSVAULT1.store"/>
<vault-option name="KEYSTORE_PASSWORD" value="MASK-03F2DNtm3kYzHmvARCHo2a"/>
<vault-option name="KEYSTORE_ALIAS" value="Vault"/>
<vault-option name="SALT" value="ABCD1234"/>
<vault-option name="ITERATION_COUNT" value="95"/>
<vault-option name="ENC_FILE_DIR" value="C:\keystore

13
Installation

"/>
</vault><management> ...

3. Modify the standalone.xml in %WildFly_HOME%\server\DctmServer_MethodServer

\configuration\standalone.xml. Add the output of vault from Step 2 in these tags:
</extensions>
<management>

4. Replace the value in the SSL identity with the substitution string generated after Vault Block:
by the keystore password in encrypted form.
For example, change the following:
Vault Block:vb
Attribute Name:jca-pass
Configuration should be done as follows:
VAULT::vb::jca-pass::1
keystore-password attribute value should be as follows:
<keystore path="C:\\keystore
jms1.keystore" keystore-password=
"${VAULT::vb::jca-pass::1}
"alias="tomcat1"/>

Note: You must put ${} around the value.

Upgrading JDK and WildFly

From Content Server 7.3 Patch 17, you can upgrade JDK and WildFly using the JDK and WildFly
upgrade utility.
1. Install the Content Server 7.3 <patch_version>.
2. Download the supported JDK version from the Oracle website.
3. Ensure that the new JDK version is installed within the Documentum directory. The existing JDK
is installed under the DOCUMENTUM\ java64 (or DOCUMENTUM/java64) folder.
4. Create a folder with the name as the JDK version number under the java64 folder, to retain the
format of the directory structure.
5. Install the JDK using the new folder.
6. Stop all Documentum-related services.
7. Unzip the jdk_wildfly_upgrade_win or jdk_wildfly_upgrade_linux file.
8. In the extracted folder, execute the JDKWildflyUpgradeUtility utility to upgrade the JDK
and/or WildFly using the upgrade utility wizard.
Note: Ensure that you port all the customizations (if any) manually to the supported version
of WildFly.
9. Restart all Documentum-related services.

14
 Installation

Note:
• Upgrading Java Method Server to WildFly is a one time procedure. This need not be executed
with every patch. Once upgraded to WildFly in patches, the patch installer will take care of
updating files within WildFly.
• In RCS upgrade, after the WildFly is upgraded, ensure to upgrade the CFS instance in the RCS
environment and then restart the Java Method Server.
• If your are configuring the WildFly 9.x or 11.x server in the HTTPS mode, then you must add the
read-timeout attribute in https-listener. The recommended value for read-timeout is
900000 (15 minutes). For example, add the value as shown in bold:
<subsystem xmlns="urn:jboss:domain:undertow:4.0">
<buffer-cache name="default"/>
<server name="default-server">
<http-listener max-post-size="4096" name="default"
redirect-socket="https" socket-binding="http"/>

<https-listener name="https" read-timeout="900000"

socket-binding="https" security-realm="UndertowRealm"
enabled-cipher-suites="TLS_DH_anon_WITH_AES_128_CBC_SHA,
SSL_DH_anon_WITH_3DES_EDE_CBC_SHA,
TLS_RSA_WITH_AES_128_CBC_SHA"/>
......
</subsystem>

• To re-initiate the XML Store plugin, perform the following:

1. Check out the XML Store plugin object.
2. Set the new library file to the existing plugin.
3. Check in the plugin object.
4. Update the XML Store object with the object ID of the new plugin object.
5. Restart the Content Server.
For example:
API> retrieve,c,dm_plugin where object_name = 'xhive_linuxshrlib_externalstorage'
...
6701d97d8000150b
API> checkout,c,l
...
6701d97d8000150b
API> setfile,c,l,/home/testqa/dctm/product/7.3/bin/xstoreplugin.so,linuxshrlib
...
OK
API> checkin,c,l
...
6701d97d8000150d
API> retrieve,c,dm_extern_free where name ='testenv_xhivestore'
...
6301d97d80000114
API> set,c,l,a_plugin_id
SET> 6701d97d8000150d
...
OK
API> save,c,l
...
OK

15
Installation

Anonymous SSL Communication for Content

Server and DFC-based Clients
For SSL communication, by default, DFC searches the value of dfc.security.ssl.truststore
(property for certificate) in dfc.properties. If found, DFC uses the Certificate-based SSL
communication. Otherwise, DFC defaults to the cipher-based anonymous SSL supported by Java.
However, Oracle JDK/OpenJDK 8.0 Update 201 and later do not support anonymous ciphers for SSL
or TLS communication and results in the following exception:
DfDocbrokerException:: THREAD: main; MSG: [DFC_DOCBROKER_REQUEST_FAILED]
Request to Docbroker "XX.XXX.XX.XX:1489" failed; ERRORCODE: ff; NEXT: null
at com.documentum.fc.client.DfDocbrokerException.newRequestFailedException
(DfDocbrokerException.java:13) at com.documentum.fc.client.impl.docbroker
.ServerMapBuilder.getMap(ServerMapBuilder.java:72)
...
Caused by: DfIOException:: THREAD: main; MSG: [DM_SESSION_E_RPC
_ERROR]error: "Server communication failure"; ERRORCODE: 100; NEXT: null
at com.documentum.fc.client.DfIOException.newCommunicationFailureException
(DfIOException.java:16) at com.documentum.fc.client.impl.connection
.netwise.AbstractNetwiseRpcClient.sendMessage(AbstractNetwiseRpcClient
.java:216)
...
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert:
handshake_failure at java.base/sun.security.ssl.Alert.createSSLException
(Alert.java:128) at java.base/sun.security.ssl.Alert.createSSLException
(Alert.java:117)

OpenText strongly recommends to use Certificate-based SSL communication.

However, if you want to use anonymous SSL communication, perform the following:
1. In Oracle JDK/OpenJDK 8.0 Update 201 or later, open the java.security file from
<java_home>\jre\lib\security\.
2. Find the line starting with jdk.tls.disabledAlgorithms.
3. Remove anon from the list of disabled algorithms.
4. Save your changes.

Upgrading to ODBC Driver 17.2 for SQL Server

1. Download and install the ODBC driver 17.2.
2. Create a new system DSN using the ODBC driver 17.2. For example, sqldsn17.
3. When you create new repository, select the newly created DSN as the data source.
4. To upgrade to ODBC driver 17.2 for the existing repository:
a. Stop the repository.

16
 Installation

b. Update the database_conn attribute in server.ini with the new DSN to indicate the
server to point to the latest DSN.
c. Restart the repository.
Note: Upgrading of Content Server having ODBC 17.2 to Documentum Server 16.4 and all patch
versions up to Documentum Server 16.4 P10 is not supported.

17
Installation

18
 Chapter 4
Docker Patch

For RHEL, perform the following steps:

1. Create a Linux (RHEL) Docker base image with 7.3 Content Server.
2. Create a dummy container with following steps: For example:
docker run –ti contentserver/rhelora/stateless/cs:7.3.000 bash

3. Install patch like classic model.

Note: Refer to Installation section for Patch installation. For Docker patch, Content Server related
prerequisites may not be applicable.
4. Save the container after installing the patch with following command: For example: docker
commit --change='CMD ["/bin/sh", "-c", ".$DM_DOCKER_HOME/configure
-stateless-server"]' f5f3587b4393 contentserver/rhelora/stateless/cs:7
.3.0010.0026
5. Perform the Seamless upgrade of Content Server on Docker environment steps to create the patch
container.
Note: It is recommended to use same docker host to perform seamless upgrade.
6. In Composer, you must update the dfc.properties file to install DAR.
Perform the following steps:
a. Update the dfc.properties for Composer with host details by using the following
location:
${DM_HOME}/install/composer/ComposerHeadless/plugins/com.emc.ide
.external.dfc_1.0.0/documentum.config/dfc.properties
b. Run the following command to install DAR. For example, java -Ddar=${DM_HOME}
/install/DARsInternal/<MailApp.dar/MessagingApp.dar/Workflow.dar>
-Ddocbase=$ {DOCBASE_NAME} -Duser=$ {INSTALL_OWNER_USER} -Ddomain=
-cp ${DM_HOME}/install/composer/ComposerHeadless/startup.jar
org.eclipse.core.launcher.Main -data ${DM_HOME} /install/composer
/workspace -application org.eclipse.ant.core.antRunner -buildfile
${DM_HOME} /install/composer/deploy.xml
Note: You must install all the MailApp.dar, MessagingApp.dar, and Workflow.dar DAR
files.
7. (After running the migration utility) For the XML Store functionality on seamless upgrade, update
web.xml with the seamless container details at $Documentum/<WildFly_Version>/server
/DctmServer_MethodServer/deployments/XhiveConnector.ear/APP-INF/classes.

19
Docker Patch

For example:
<init-param>
<param-name>xhiveaddress</param-name>
<param-value>seamlesscontainerhostname</param-value>
</init-param>
<init-param>
<param-name>Content-Server-Version</param-name>
<param-value>7.3.0170.0122</param-value>
</init-param>
Update dfc.properties with the seamless container details at $Documentum/<WildFly
_Version>//server/DctmServer_MethodServer/deployments/XhiveConnector
.ear/APP-INF/classes.
After you complete seamless upgrade, verify if the patch container functions as expected. Then, you
can shut down the primary container and use patch container.

For CentOS and Ubuntu, perform the following steps:

1. Install the supported version of Docker, Docker Compose file, and netshare plugin in your host
machine.
2. Start the Docker process from the service. For example: service docker start
3. Start the Docker netshare plugin. For example: ./docker-volume-netshare
--basedir=/var/lib/docker/volumes --verbose=true nfs
4. Share $DOCUMENTUM/data, $DOCUMENTUM/share, $DOCUMENTUM/xhive_storage,
$DOCUMENTUM/<JBoss or WildFly version folder>/server/DctmServer
_MethodServer/deployments/XhiveConnector.ear if the existing Content Server (7.1 or
7.2 or 7.3) does not use the remote file system for data.
5. Provide all the required details in the seamlesscs.conf file. Read the description of every
field and provide valid values for each parameter. For example, the seamlesscs.conf file
contains the following:
• Documentum Content Server Image name. If the image is a TAR file, then load the image into
local registry with the following command and update the exact Content Server image name:
#docker load -i imagetarfilename.
• IMAGE_NAME = 10.31.4.205:5000/contentserver/centos/stateless/cs:7.3.0000
• Docbase configuration details.
• Base machine IP: For example, External_IP = 10.31.86.164.
• Container host name. For example, CONTAINER_HOSTNAME = centseamless.
• Container name. For example, CONTAINER_NAME = centseamless.
6. Export the environment variables. The Content Server chapter in Documentum Platform and
Platform Extensions Installation Guide contains the instructions.
7. Run the seamless_config.sh script.
8. (Only for Ubuntu) Run the following command to install DAR. For example, java
-Ddar=${DM_HOME} /install/DARsInternal/MailApp.dar -Ddocbase=$
{DOCBASE_NAME} -Duser=$ {INSTALL_OWNER_USER} -Ddomain= -cp
${DM_HOME}/install/composer/ComposerHeadless/startup.jar org.eclipse
.core.launcher.Main -data ${DM_HOME} /install/composer/workspace

20
 Docker Patch

-application org.eclipse.ant.core.antRunner -buildfile ${DM_HOME}

/install/composer/deploy.xml
9. To verify the installation, check the logs at /opt/dctm_docker/logs/<hostname>.log
inside the container.
You must update all the configuration parameters in the seamlesscs.conf file based on your
configuration. All the patching is done with seamless upgrade. The seamless_config.sh file is
the script that picks the seamlesscs.conf as the parameter inside the script. The script would
generate the YML and passes the YML file as a parameter to docker-compose. Docker compose
would define and then run container docker application. It would configure the application services
and also run those configured services.
Note: (Only for CentOS and Ubuntu) To use WildFly 17.x, change the value of the WildflyVersion
parameter located at $DM_HOME/install/external_apps/MigrationUtil/config.xml in
the secondary environment during the migration process. For example (as shown in bold):
Change
<entry key="WildflyVersion">wildfly9.0.1</entry>
To
<entry key="WildflyVersion">wildfly17.0.1</entry>

21
Docker Patch

22
 Chapter 5
Uninstalling the Patch

Perform the following steps to uninstall the patch you applied using the patch installer:
1. Stop the Java Method Server and Content Server.
2. Run the following command:
• For UNIX, run the following command in the $DOCUMENTUM/patch/bin folder:
csPatchUninstall.sh

• For Windows, run the following command in the %DOCUMENTUM%\patch\bin folder:

csPatchUninstall.bat

3. Start the Content Server and Java Method Server.

4. If you have run repository Patch to update your repositories, run it again to re-install the earlier
DARs.
The binaries are reverted to the previously installed version of Content Server patch.

23
Uninstalling the Patch

24
 Chapter 6
Fixed Issues

This section identifies issues and limitations that are fixed by applying the patch.
Patches are cumulative. As of its publication date, this document lists the fixes for all released patches
for this product.

Patch 35 Fixed Issues List

Issue ID Description
CS-126622 Segmentation violation error occurs when you
try to to unlink folder from the home folder.
CS-126542 The primary Documentum Server crashes
intermittently.
CS-126504 When a user calls the placeholder generation,
the repository crashes.
CS-126384 Inconsistencies with the i_ancestor_id and
r_folder_path attributes after an upgrade
process.
CS-126343 Segmentation violation errors reported in the
repository logs.

Patch 33 Fixed Issues List

Issue ID Description
CS-123559 When you run the LDAP synchronization job,
the A User with same user_name exists
in the docbase with a different
identity warning message appears.
CS-123304 Issues when using the DM_GROUP_LIST
_LIMIT environment variable.

25
Fixed Issues

Issue ID Description
CS-122983 When you use the SEARCH DOCUMENT
CONTAINS clause in DQL, it results in an error.
CS-121914 Documentum Server fails to store content to
the S3 storage with the Bytes read is not
equal to contentlength; error.
CS-122880 Removing an attribute from a type with many
attributes results in data corruption.
CS-122862 When version label at position 0 is not a number
during a check-in operation, it results in a stack
dump exception.
CS-122814 When fetching all the dm_jms_config objects
configured for a given server_id from the
repository, Documentum Server generates an
incorrect SQL query for the Oracle database.
CS-121473 When a repository is using Galactic
objectIDs, client applications fail with the
DM_DFC_E_CLASS_NOT_FOUND error.
CS-56026 Failed to create or alter type to add a check or
constraint for a repeating property by DQL.

Patch 32 Fixed Issues List

Issue ID Description
CS-122649 When you try to save objects after the upgrade
process, the application becomes slow.
CS-122642 Jobs fail intermittently with the DM_SESSION_E
_CLIENT_AUTHENTICATION_FAILURE error.
CS-121267 When you run the dm_jms_admin job, it returns
SUCCESS even when JMS is not available.

26
 Fixed Issues

Patch 30 Fixed Issues List

Issue ID Description
CS-121198 Job report format is not correctly set in the ebs
scripts for Windows.
CS-120923 Issue while trying to create a LWSO object using
Batch, Retention Policy, and xCP DataType
aspects attached to it.
CS-119674 Issue when adding the MSG file (Outlook email)
of type dm_email_message as a child to PST
virtual document. Additional Information for
Fixed Issues in Patch 30, page 27 contains more
information.

Additional Information for Fixed Issues in Patch 30

CS-119674

A flag, Checkin_MSG_Descendant is introduced in the mailapp.properties file. If the value of

the flag is set to true, the .MSG file is added as a child to a virtual document. If the value of the flag is
set to false, the .MSG file cannot be added as a child to a virtual document.

Patch 28 Fixed Issues List

Issue ID Description
CS-120866 Link or unlink operations causes the
DM_FOLDER_E_CANT_ADD_LINK2 error.
CS-120711 DQL UPDATE with WHERE clause as
"r_object_id in('<OBJ_1>','<OBJ
_2>')" returns more than two values as
"objects_updated" and is dependent on
number of values at repeating attribute.
CS-120681 Users are unable to log on to Webtop when SSL
is enabled for LDAP configuration.
CS-120381 Buffer overflow issue in DQL.

27
Fixed Issues

Patch 25 Fixed Issues List

Issue ID Description
CS-120016 When you run the dm_DMClean job using
the -clean_content_in_parallel,
-parallel_degree, and -clean_now
parameters, the job does not work and crashes
with the ACCESS_VIOLATION error.
CS-119812 LDAP SSL authentication does not work.
CS-119780 The WARM sessions and COLD sessions do not
get released timely in Content Servers except the
primary Content Server.
CS-119709 The dmqdocbroker command does not connect
to the connection broker on any ports other than
1489 without using the hostname value.
CS-119743 Workflow agent does not process workitem after
SQL Server 2016 database fail over from one
node to another node using Microsoft Cluster
Service.
CS-119426 Unable to link the document even if the user has
CHANGE_LOCATION extended permissions after
upgrading from Documentum 6.7 SP2.
CS-59110 Some commit operations fails with the
DM_SESSION_W_CANT_BEGIN_TRANSACTION
error.
CS-58148 When completing a workitem, it results in an
exception and workflow does not proceed.
CS-57787 dm_check_password results in a
Segmentation fault error while
using a wrong password for a valid user.
CS-57542 Installation of remote Content Server does not
work if a – (dash) is included in the value for
hostname.
CS-56272 UserRename as part of the dm
_LDAPSynchronization job does not
provide the option to preserve lock on updated
objects.
CS-56007 Content Server process gets stuck with infinite
loop.

28
 Fixed Issues

Patch 23 Fixed Issues List

Issue ID Description
CS-119558 DATEADD function in DQL does not work in
PostgreSQL.
CS-119316 Incorrect behavior of the check_security method
during the upgrade process.
CS-119040 smail crashes when you try to send or receive
emails.
CS-118679 a_current_status of the dm_StateOfDocbase job
does not get updated.
CS-118530 When you use the dm_DMClean job or method
while considering ACLs, it causes high memory
usage and crashes.
CS-56611 Movecontent.ebs script does not expose all
the arguments for the MIGRATE_CONTENT
method.
CS-56367 LDAP DA test functionality is hiding the
exception hit.
CS-56310 dm_saveasnew event does not work properly.

Patch 21 Fixed Issues List

Issue ID Description
CS-119034 Custom jobs running with a_special_app set to
‘Workflow’ or a_special_app set to ‘Workflow
Job’ do not produce a job log.
CS-118009 When you rename users in LDAP Server
and run the dm_LDAPSynchronization job
with rename_user_option set to false, it
results in warnings in report and creation of
dmi_queue_items. Additional Information for
Fixed Issues in Patch 21, page 30 contains more
information.

29
Fixed Issues

Additional Information for Fixed Issues in Patch 21

CS-118009

You must add the new job argument ignore_warning_message and set it to true before running
the dm_LDAPSynchronization job to avoid creating dmi_queue_items and the warning messages in
job report.

Patch 20 Fixed Issues List

Issue ID Description
CS-118786 When you run the dm_DMClean job, Content
Server crashes intermittently with the
DM_SESSION_E_HEAP_CREATION_FAILURE
error.
CS-118716 Data loss using PostgreSQL during the
multithreading or multiserver import operation.
CS-118650 When you try to modify the type using
additional attributes, it results in an error.
CS-118568 When you migrate millions of objects from local
stores to S3 stores, it results in thousands of
warning messages.
CS-118543 Content Server crashes intermittently after
upgrading to 16.4 with TNS connection timeout
error messages.
CS-59171 CTS processing results in the DM_CONTENT_E
_CONTENT_SAVE_FAILURE error.

Patch 19 Fixed Issues List

Issue ID Description
CS-118504 Database is either not connected or not reachable
during the workflow process.

30
 Fixed Issues

Patch 18 Fixed Issues List

Issue ID Description
CS-118145 When you run the D2JobLifecycleBatch job,
it fails with the DM_SESSION_E_CLIENT
_AUTHENTICATION_FAILURE error.
CS-118117 Unable to establish communication between
LDAP server and the Content Server using TLS
1.2.
CS-117584 Documentum Content Server does not store the
old value of workflow_disabled when the
value of user_state is changed. Additional
Information for Fixed Issues in Patch 18, page 31
contains more information.

Additional Information for Fixed Issues in Patch 18

CS-117584

With this fix, user_state overrides workflow_disabled values which means that if user_state is active
then only workflow_disabled value is considered. If you want to revert to the old behavior, you can
create the WFD_RESET_ON_USER_STATE environment variable and set it to 1.

Patch 17 Fixed Issues List

Issue ID Description
CS-117718 When you update the mapping table DQL from
a custom job, it results in the yacc stack overflow
error.
CS-117618 Minimum Owner Permission when set to
Browse still allows a owner to read.
CS-56313 When you add mapping for user_group_name
of dm_user in order to set default group
of LDAP users, it causes the LDAP
synchronization job to fail with the
DM_OBJ_E_VERSION_MISMATCH error.

31
Fixed Issues

Patch 16 Fixed Issues List

Issue ID Description
CS-117768 External connection broker for docker
(docbroker2.ini file) does not allow more than 42
IP addresses.

Patch 15 Fixed Issues List

Issue ID Description
CS-117417 Workflow reporting Edit Document option does
not find workflows.
CS-117368 When you run the check_security DQL for a
user belonging to many groups, it results in the
yacc stack overflow error.
CS-59366 [Amazon S3 support] All Documentum
connections to S3 storage does not follow
enterprise security policies. Additional
Information for Fixed Issues in Patch 15, page 32
contains more information.
CS-59362 [Amazon S3 support] Amazon S3 content store
with TCS and CSS is not supported. Additional
Information for Fixed Issues in Patch 15, page 32
contains more information.
CS-59156 Increased memory usage with Content Server
7.3 on AIX/DB2 after upgrading from 7.1.
CS-58421 [Amazon S3 support] Performance issues with
ViPR and S3 stores. Additional Information for
Fixed Issues in Patch 15, page 32 contains more
information.
CS-56903 Documentum Content Server 7.3 OpenStack
Swift Store does not support Swift API Version 1.

Additional Information for Fixed Issues in Patch 15

CS-59362

To apply this fix, perform the following and then restart the WildFly server to perform the push or
pull operations:
1. Apply the latest patch and start the repository.

32
 Fixed Issues

2. Create an S3 store type from IAPI: create type dm_s3_store with supertype dm_store
3. Install $DM_HOME/install/DARsInternal/S3Plugin.dar
4. Create the S3 store object.
The store is configured with the following information:
• java_access: Name of the module (S3 plugin) which the store object represents. The
default value is S3 Plugin for dm_s3_store type objects.
• base_url: S3 storage service URL. Format is http://<X.X.X.X>/<BUCKET> where
— X.X.X.X: URL of S3 store service and the URL format is http://hostname:port.
— BUCKET: Name of the S3 bucket used to push the content. This name is mandatory.
Bucket should be preconfigured in S3 storage service and is accessible using the following
credentials:
— credential_id: Access Key (user id or access key to access the store service).
— credential_key: Password for accessing the store. DFC encrypts or decrypts this
password before storing and passing it on to the plugin.
Once it is configured, the store is accessible as any other Documentum Content Server store.
For more information on Amazon S3, refer to the Documentum Server 16.4 Administration and
Configuration Guide.

CS-59366

Set the appropriate values in the s3.properties file in %DOCUMENTUM%\<WildFly version

folder>\server\DctmServer_MethodServer\deployments\acs.ear\lib\configs.jar.
Then, restart the WildFly server to perform the push or pull operations.
For proxy:
#PROXY_HOST=
#PROXY_PORT=
#PROXY_USER=
#PROXY_PASSWORD=

For secure connection:

• enable-md5: Set it to true to enable this property.
• enable-v4signing: Set it to true to enable this property.
• mds-multipart-threshold: When enable-md5 is enabled, the default value 10 MB is used
for multipart threshold.
Note: For WORM-enabled S3 stores, you must enable the enable-md5 and enable-v4signing
properties.

33
Fixed Issues

CS-58421

For performance improvement:

Use the use-random-in-filename property in the s3.properties file in
%DOCUMENTUM%\<WildFly version folder>\server\DctmServer_MethodServer
\deployments\acs.ear\lib\configs.jar. Set it to true to enable this property.

Patch 14 Fixed Issues List

Issue ID Description
CS-117337 Permission issues with old documents after
migrating from TaskSpace to xCP 2.3.
CS-59339 When you run the migration utility to change the
repository ID that has Trusted Content Services
with encrypted filestore, it results in an error.

Patch 13 Fixed Issues List

Issue ID Description
CS-59168 DQL query to update using a subselect for date
causes an access violation.
CS-59088 UserRename method fails on the dmi_registry
objects.
CS-58947 Issue with time_stamp_utc time zone offset
when using * in the select query.
CS-58876 Hardcoded “s0” used in the .ebs scripts causes
failure in the upgrade process.
CS-57724 When the authentication trace is enabled,
dm_change_password prints old and new
passwords in plain text in the repository log.
CS-56262 Query generated for ROW_BASED does not
work for Documentum Connector for Microsoft
SharePoint.
CS-55907 URL that D2 uses to change pages in Thumbnail
Widget is not valid when the rendition is in an
encrypted filestore.

34
 Fixed Issues

Issue ID Description
CS-55886 DM_SESSION_E_RPC_ERROR error occurs and
Assertion fails in repository and JMS logs.
CS-54046 Repository crashes with the "Exception
00000000C0000005 (ACCESS_VIOLATION)
occurred at 0000000076E50E91" exception.

Patch 12 Fixed Issues List

Issue ID Description
CS-58988 Delegation of a task to a user fails intermittently
with an error.
CS-53052 Importing a certificate chain results in only the
root certificate getting appropriately converted.

Patch 11 Fixed Issues List

Issue ID Description
CS-58480 LDAP synchronization job activates the
inactivate users in the repository.

Patch 10 Fixed Issues List

There are no fixes associated with this patch.

Patch 09 Fixed Issues List

Issue ID Description
CS-55907 URL that D2 uses to change pages in Thumbnail
Widget is not valid when the rendition is in an
encrypted filestore.
CS-55884 DM_SESSION_E_RPC_ERROR error occurs and
Assertion fails in repository and JMS logs.

35
Fixed Issues

Patch 08 Fixed Issues List

Issue ID Description
CS-57767 Permissions issues with old documents after
migrating from Taskspace to xCP 2.3.
CS-57749 When retrieving content from a distributed
store, the ACS read URLs are not being
generated based on the network location of user
connection.
CS-56846 LDAP synchronization fails with the DM_LDAP
_SYNC_E_LDAP_NAMING_EXCEPTION
exception.
CS-54979 The user_login_domain attribute could not be
configured in the dm_ldap_config object.

Patch 07 Fixed Issues List

Issue ID Description
CS-57309 DQL causes parser error resulting in DB cursor
issue when return_range keyword is used.
CS-57182 LDAP SSL authentication fails.
CS-57086 NULL Pointer exception occurs if invalid entries
are added to odbc.ini.
CS-56908 Workflow agent does not commit SQL
Transactions on dmi_queue_item_s and causes
the Index agent to hang.

Patch 06 Fixed Issues List

Issue ID Description
CS-57091 D2 should use URL function to retrieve
thumbnail rendition, and do not encode again.

36
 Fixed Issues

Patch 05 Fixed Issues List

Issue ID Description
CS-57173 User is not able to access to LDAP configuration
in DA after failure to create many LDAP config
objects.
CS-57161 Error "[DM_QUERY_E_CURSOR_ERROR]
error: "A database error has occurred during the
creation of a cursor.
CS-57094 Terminating workflows causes database sessions
till docbase crashes.
CS-57074 Emails being overwritten on Export.
CS-57060 User's not able to update custom plugin name in
user_source/group_source attribute.
CS-57005 Duplicate key value violates unique constraint
"dm_usage_log_index" in DB log.
CS-57002 DFC sysobj.setStorageType() save method fails
which causes r_content_id of dm_sysobject not
updating with the new content_id.
CS-56928 DQL issue with strings over 2000 characters in
Linux.
CS-56912 LDAP Nested Sync is failing with the
DM_GROUP_E_CANT_FIND_USER error.

Patch 04 Fixed Issues List

Issue ID Description
CS-56968 dm_usage_log has improper timestamp on
PostgreSQL. Additional Information for Fixed
Issues in Patch 04, page 38 contains more
information.
CS-56883 DQL Query failed with error when
OPTIMIZE_ON_BASE_TABLE is used.
CS-56765 Migration Utility does not use DOCUMENTUM
_SHARED to resolve DFC properties file paths.
CS-56759 Migration Utility issues with database_conn
property in server.ini - Oracle TNS alias not
accepted.
CS-56698 Default thumbnail URL doesn't work if default
thumbnail files are stored in distributed storage
and the first component is Read-Only.

37
Fixed Issues

Issue ID Description
CS-56687 Issues with relation of dm_user.user_state and
workflow_disabled attributes.
CS-55790 DQL to SQL translation causing
DM_QUERY_E_CURSOR_ERROR error.

Additional Information for Fixed Issues in Patch 04

CS-56968

In Postgres, you must manually change the datatype of first_use and latest_use columns to timestamp
without time zone in the dm_usage_log table. You must connect to postgres DB and run the following
SQL queries:
alter table dm_usage_log alter column first_use type timestamp without
time zone
alter table dm_usage_log alter column latest_use type timestamp without
time zone

Patch 03 Fixed Issues List

Issue ID Description
CS-56656 Content Server crash in a distributed
environment when the LogPurge job is
scheduled to run at same time.
CS-56647 Installation of Content Server 7.3 Patch 01 does
not update all the dfc.jar files.
CS-56594 dm_bear_trap: Unexpected exception,
(SIGSEGV: segmentation violation: (11) at
(Connection Failure)) after 20 hours of running.
CS-56606 PostgreSQL: DATEDIFF on days, months and
years not working.
CS-56567 FixFolder had failed during the multilevel
correction which has been addressed as a fix
with this request.
CS-56515 dm_UserRename_java is causing a full table
scan on the dmi_queue_item.

38
 Fixed Issues

Issue ID Description
CS-56356 Docbase configuration will fail with PostgreSQL
ODBC drivers 09.06.
CS-51037 Parallel Processing in dmclean : Performance
Improvement for large objects. Additional
Information for Fixed Issues in Patch 03, page 39
contains more information.

Additional Information for Fixed Issues in Patch 03

CS-51037

You can configure the dm_DMClean job with the following additional parameters:
• batch_size: Configure to enable batch_size option. The default value is 2000.
• DM_USE_PARALLEL_CLEAN_TEMP_TBL: This is a dm_docbase_config object argument. If you
enable this argument, by using the following command, it uses a temp table to fetch orphan object
instead of original content object table. This prevents full table scan.
reterive,c,dm_docbase_config
append,c,l,r_module_name
DM_USE_PARALLEL_CLEAN_TEMP_TBL
append,c,l,r_module_mode
1
Save,c,l
After you run the commands, you must restart the docbase.
batch_size - if enable content parallel option, each iteration fetch batch_size objects to clean.
DM_USE_PARALLEL_CLEAN_TEMP_TBL - environmental variable. if enable this arguments, it
uses temp table to fetch orphan object instead of original table(dmr_content_s). it helps avoid full
table scan issue.

Patch 02 Fixed Issues List

Issue ID Description
CS-56477 user_or group in dm_alias not affected.
CS-56439 Access Violations in postgres environment.
CS-56380 After patch P02/05 RPC bindFile checks
permissions to all documents that share
dmr_content.
CS-56189 Postgres throws the operator does not exist:
integer !=- integer DB error.
CS-55981 StateOfDocbase job - French Locale Support.

39
Fixed Issues

Patch 01 Fixed Issues List

Issue ID Description
CS-56256 skill_values_string appears to have an issue to
remove values but also during remove adds a
duplicate value.
CS-55086 DM_WORKFLOW_W_PERFORMER
_UNRESOLVED warning observed when
activities are assigned to a group with only other
groups as members.

40
 Chapter 7
Known Issues

This section identifies issues and limitations that might affect your use of the product after you
apply the patch.

Issue ID Description
CS-120271 Patch does not work if you rename or remove the WildFly 9.0.1 folder
after upgrading to WildFly 11. This is a design limitation.

Workaround: Do not rename or remove the WildFly 9.0.1 folder after

upgrading to WildFly 11.
CS-119926 Migration from a physical 7.1 Content Server to a 7.3 Content Server in a
Docker environment fails.

Workaround: In any multi-node environment, ensure that you validate

the dfc.properties file where the local host environment details be
on the higher priority compared to the remote environment details.
For example:
dfc.docbroker.host[0]=<local container>
dfc.docbroker.port[0]=<local port>
dfc.docbroker.host[1]=<remote container>
dfc.docbroker.port[1]=<remote port>
CS-117630 Unable to import a document that has a file size more than 10 MB.

Workaround: Set max-post-size="0" in standalone.xml (in the

http-listener name="default" tag) of WildFly.
CS-59183 Oracle release 11 client has a memory leak issue. This is a limitation from
Oracle. If you are using Oracle release 11 OCI/OCCI client, you must
apply the 17532729 patch version of Oracle to avoid memory leakage.
Ensure that you apply the patch to the correct ORACLE_HOME.
CS-57784 Netegrity plugin of Content Server is upgraded to CA 12.52 CR 07
[FullVersion=12.52.107.2259]. However, the dm_netegrity.dll
file is not included by default in the patch as it requires upgrading
CA Siteminder also in machine with testing effort. If you want to
upgrade the Netegrity plugin, you can compile it with CA 12.52 CR
07 [FullVersion=12.52.107.2259] version or contact OpenText Global
Technical Services to obtain the DLL file.

41
Known Issues

Issue ID Description
CS-56179 Setting HA_SETUP_ENABLED is causing a workflow to have Content
Server affinity for its whole activities, whatever they are sequential or
parallel. If a Content Server crash, all associated workflows are stuck
or paused state.

Workaround: Manual steps required to move these workflows/work

-items to an available Content Server.

Fetch all completed work-items of associated crashed Content Server’s

workflows and then set a_wq_name of work item to available Content
Server config name. Then rest of work-items will be processed through
configured Content Server.
CS-55857 Content Server installer fails to verify the database home directory
when it is installed with SQL Server 2016.

Workaround:
1. Install Microsoft SQL Server 2014 ODBC database driver (client) on
the machine that is used to install Content Sever. This driver is used
to create an ODBC data source with the SQL Server 2016 database.

This configuration is best created when the SQL Server database

resides on a machine separate from the Content Server installation.

2. Proceed with the installation once an ODBC data source is created

by following the steps as outlined for a regular Content Server
installation.

42