Documentum Content Server

EMC CONFIDENTIAL INTERNAL USE ONLY

EMC CONFIDENTIAL INTERNAL AND PARTNER USE ONLY
DELETE IF THIS IS A PUBLIC DOCUMENT

6.5 SP3 Patch 24 ReadMe

EMC
Corporate Headquarters
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com

Copyright 2012 EMC Corporation. All rights reserved.

Published August, 2012
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
T HE INFORMAT ION IN T HIS PUBLICATION IS PROVIDED AS I S. EMC CORPORAT ION
MAKES NO REPRE SENT AT IONS OR WARRANT IES OF ANY KIND WIT H RESPECT T O T HE
INFORMAT ION IN T HIS PUBLICAT ION, AND SPECIFICALLY DISCLAIM S IMPLIED
WARRANT IES OF MERCHANT ABILIT Y OR FIT NESS FOR A PART ICULAR PURPOSE.
Use, copying, and distribution of any EMC software describe d in this publication requires an applicable
software license.
For the most up-to-date listing of EMC product names, see EMC Corporation T rademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Revision History
August 2012: Initial Release

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Contents
About this Document .............................................................................................................................4
Dependencies..........................................................................................................................................4
Fixed Issues ............................................................................................................................................4
Known Problems and Limitations......................................................................................................... 5
Deployment Steps ..................................................................................................................................5
Windows ........................................................................................................................................5
All UNIX Platforms ......................................................................................................................7
Post Deployment Steps ........................................................................................................................10
Deployment Steps for Customization .................................................................................................11
Technical Notes....................................................................................................................................11

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

About this Document

About this Document

This document comprises bugs that have been fixed since the latest 6.5 SP3 patch release. It also
provides deployment steps for generic and customized deployments. Information in this
document can be used for applying Patch 24 for Documentum Content Server 6.5 SP3.

IMPORTANT: Documentum Content Server 6.5 SP3 has reached the standard
end of support in August 2012. Please note that Patch 24 is the final patch that
will be delivered for Documentum Content Server 6.5 SP3.
Audience
This document is intended for Documentum Content Server 6.5 SP3 customers who have
reported issues listed in the Fixed Issues section of this document and require the fixes provided
in Patch 24. This document is also intended for Documentum Content Server 6.5 SP3 customers
who want to upgrade to Patch 24.

Dependencies
The following tables list dependent bugs for Documentum Content Server:
Table 1 Dependent Fix in Docum entum Content Server 6.5 SP3 Patch 16
Defect ID

Fix Request ID

CS-33278

CS-33281

Dependent Bug ID
Fix Request ID: DFC- 9684
(Defect ID: DFC-9681)

Patch to Deploy

DFC 6.5 SP3 Patch 15

CS 6.5 SP3 Patch 16

Fixed Issues
Documentum Content Server 6.5 SP3 Patch 24 is a cumulative patch and includes fixes from all
earlier patches.
For information about fixes in an earlier patch of Documentum Content Server 6.5 SP3, see the
ReadMe of the relevant patch.
Documentum Content Server 6.5 SP3 Patch 24 comprises the following fixed issues:
Table 2

Fixed Issues in Documentum Content Server 6.5 SP3 Patch 24

Defect ID

Fix Request ID

CS-39157

CS-39159

CS-38762

CS-38945

CS-38306

CS-38676

CS-15775

CS-38542

CS-33980

CS-38476

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Description
In docbase log, Storage Plug-in Runtime Version is displayed
w ith junk characters.
A consumer user (default user in no roles) is able to modify a
relationship even though the relation type security type is set to
PA RENT and the user does not have WRITE per mission on
parent.
Verbosity in docbroker and repos itory logs are seen.
The follow ing error occurs w hile migrating the contents:
DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_W
RITE.
Dum pToAttrsStream is Empty [DFC_SESSION_TRANSA CTION_LOST] Transaction is invalid
because of the server.

Known Problems and Limitations

Known Problems and Limitations

NONE

Deployment Steps
Follow these generic steps to deploy the Documentum Content Server patch.

Windows
To deploy the Patch:
Before replacing any of the binaries as listed in the next two sections in their specific locations,
perform the following steps:
1.

Stop the Java Method Server.

2.

Stop the Content Server.

3.

If you have configured FAST or Documentum xPlore, stop the IndexAgent and IndexServer.

4.

Back up the %DOCUMENTUM% directory.

5.

Perform the following steps to install the patch:

a.

Unzip the patch in the %DOCUMENTUM% directory. Copy all the binaries to the
respective folders within the %DOCUMENTUM% directory.

b. Manually copy some of the files from the unzipped files. Copy the following files from
the %DOCUMENTUM% directory to the specified locations:

%DOCUMENTUM%\jboss4.2.0\server\DctmServer_MethodServer\deploy\Server
Apps.ear\APP-INF\lib\dmldap.jar

%DOCUMENTUM%\jboss4.2.0\server\DctmServer_MethodServer\deploy\Server
Apps.ear\APP-INF\lib\server-impl.jar

%DOCUMENTUM%\jboss4.2.0\server\DctmServer_MethodServer\deploy\Server
Apps.ear\DmMethods.war\WEB-INF\lib\mthdservlet.jar
Note: Take a backup of the existing dfc.jar file from all locations in the Content
Server machine and replace it with new dfc.jar file in %DOCUMENTUM%
directory.

c.

If the xml store feature is configured, copy the following file from %DOCUMENTUM%
to the specified location:
%DOCUMENTUM%\jboss4.2.0\server\DctmServer_MethodServer\deploy\XhiveConne
ctor.ear\XhiveConnector.war\WEB-INF\lib\xhiveconnector.jar

d. If FAST is configured, copy the following files from the %DOCUMENTUM% directory
to the specified locations on the machine where IndexServer is configured:

%DOCUMENTUM%\jboss4.2.0\server\DctmServer_IndexAgent%N%\deploy\Inde
xAgent%N%.war\WEB-INF\lib\adminagent.jar

%DOCUMENTUM%\jboss4.2.0\server\DctmServer_IndexAgent%N%\deploy\Inde
xAgent%N%.war\WEB-INF\lib\server-impl.jar

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Deployment Steps

If DOCUMENTUM_SHARED environment variable is defined, you will need to copy

the files FASTQueryPlugin.dll and FASTQueryPlugin.pdb to the following location:

%DOCUMENTUM_SHARED%\..\IndexAgents\ftintegrity\FASTQueryPlugin.dll

%DOCUMENTUM_SHARED%\..\IndexAgents\ftintegrity\FASTQueryPlugin.pdb

If DOCUMENTUM_SHARED environment variable is not defined, you will need to

copy the files FASTQueryPlugin.dll and FASTQueryPlugin.pdb to the following
location:

C:\Program Files\Documentum\IndexAgents\ftintegrity\FASTQueryPlugin.dll

C:\Program Files\Documentum\IndexAgents\ftintegrity\FASTQueryPlugin.pdb

Note: If you are using a different drive (other than C: drive) or custom location for Index
Agent installation, then you will need to copy the files to respective location.
6.

After you copy the files from the %DOCUMENTUM% directory, delete the above files
specified in 5b and 5d from the %DOCUMENTUM% directory. This is required since the
%DOCUMENTUM% directory may cause a path resolution conflict.

7.

After copying the files, start the following services in the specified order:
a. Start the Content Server.
b. Start the Java Method Server.
c. Start the Index Agent and Index Server.

8.

Deploy the MessagingApp.dar file as follows:

a. You can install the DAR in two ways. Use java options as given in step (e) in which case
JDK is a prerequisite, and the other way is to use Composer. Refer to the EMC
Documentum Composer User Guide for more information.
b. Ensure that the dfc.properties file under the Content Server Composer Headless location
has a docbroker, which has access to the docbases you need to apply the patch to. For
example:
c. %DM_HOME%\install\composer\ComposerHeadless\plugins\com.emc.ide.external.dfc
_1.0.0\documentum.config
d. Create a file called DARInstall.xml at your preferred location, for example, C:\Temp.
e. Insert the dar (MessagingApp.dar location), docbase, username, password, domain into
the emc.install attributes accordingly.
<?xml version="1.0"?>
<project name="patchtarget" default="installdar">
<description>
This is the ant script code to install a dar in the docbase
</description>
<target name="installdar">

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Deployment Steps

<emc.install dar="C:\Temp\MessagingApp.dar"
docbase="mydocbase" username="user1" password="hello"
domain=""/>
</target>
</project>
f.

Run the following at the command line:

java -cp
%DM_HOME%\install\composer\ComposerHeadless\startup.jar
org.eclipse.core.launcher.Main -clean -data
%DM_HOME%\install\composer\ComposerHeadless\workspace application org.eclipse.ant.core.antRunner -buildfile
C:\Temp\DARInstall.xml

9.

Install the Workflow DAR (Workflow.dar). You can do this manually using the DAR
installer or Headless Composer. Refer to the EMC Documentum Composer User Guide for
more information.

10. Install the lifecycle.jar. The lifecycle.jar is included as part of a BOF Module, it exists as
content of a dmc_jar object in the docbase. The lifecycle.jar is not installed anywhere on the
file system under %DOCUMENTUM% or %DOCUMENTUM_SHARED%; it is only
installed in the docbase. Perform the following steps using iapi32 when you login as the
docbase install owner.
retrieve,c,dmc_jar where object_name = 'lifecycle.jar'
checkout,c,l
setfile,c,l,<pathname to lifecycle.jar from patch>
checkin,c,l

All UNIX Platforms

Before replacing any of the binaries as listed in the next two sections in their specific locations,
perform the following steps:
1.

Stop the Java Method Server.

2.

Stop the Content Server.

3.

If you have configured FAST or Documentum xPlore, stop the IndexAgent and IndexServer.

4.

Take a backup of the $DOCUMENTUM directory.

5.

Perform the following steps to install the patch:

a. Unzip the patch in the $DOCUMENTUM directory. All the binaries will be copied to
the respective folders within the $DOCUMENTUM directory.
b. Some of the files must be manually copied from the unzipped files. Copy the following
files from the $DOCUMENTUM directory to the specified locations:

$DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_MethodServer/deploy
/ServerApps.ear/APP-INF/lib/dmldap.jar

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Deployment Steps

$DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_MethodServer/deploy
/ServerApps.ear/APP-INF/lib/server-impl.jar

$DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_MethodServer/deploy
/ServerApps.ear/DmMethods.war/WEB-INF/lib/mthdservlet.jar

$DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_MethodServer/deploy
/XhiveConnector.ear/XhiveConnector.war/WEB-INF/lib/xhiveconnector.jar
Note: Take a back up of the existing dfc.jar file from all locations on the Content
Server machine and replace it with the new dfc.jar file in the $DOCUMENTUM
directory.

c. If FAST is configured, copy the following files from the $DOCUMENTUM directory to
the specified locations on the machine where Index Server is configured:

$DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_IndexAgent%N%/dep
loy/IndexAgent%N%.war/WEB-INF/lib/adminagent.jar.

$DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_IndexAgent%N%/dep
loy/IndexAgent%N%.war/WEB-INF/lib/server-impl.jar

$DOCUMENTUM_SHARED/../IndexAgents/ftintegrity/libFastQueryPlugin.*
Note: If you are using custom location for Index Agent installation, then you will
need to copy the files to respective location.

d. If xPlore is configured, copy the following files manually:

Copy all files under

$DOCUMENTUM/jboss4.2.0/server/DctmServer_MethodServer/deploy/ServerApp
s.ear/APP-INF/lib to $DOCUMENTUM_SHARED/
jboss4.2.0/server/DctmServer_MethodServer/deploy/ServerApps.ear/APP-INF/lib

Copy all files under

$DOCUMENTUM/jboss4.2.0/server/DctmServer_MethodServer/deploy/ServerApp
s.ear/DmMethods.war/WEB-INF/lib to $DOCUMENTUM_SHARED
/jboss4.2.0/server/DctmServer_MethodServer/deploy/ServerApps.ear/DmMethods.
war/WEB-INF/lib

e. If the following files are not customized and you are using them, take a backup of the
following files from the $DOCUMENTUM/dba directory and replace them with these
files from the specified locations:

f.

$DOCUMENTUM/product/6.5/install/external_apps/checkpass/dm_check_passwor
d

$DOCUMENTUM/product/6.5/install/external_apps/changepass/dm_change_pass
word

$DOCUMENTUM/product/6.5/install/external_apps/assumeuser/dm_assume_user

Run the $DOCUMENTUM/dba/dm_root_task to change the ownership of the copied

files to new owner, root (not the install owner). The file permissions for the three files
are also set correctly.
From 6.5 SP3 (Patch 01 onwards), oci 9.2.0.8 is being supported on UNIX platforms and
Oracle 9.2.0.8 is being shipped along with the patch packages (UNIX only). Rename the

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Deployment Steps

existing $DM_HOME/oracle directory to $DM_HOME/oracle_9205_backup. Copy the

"Oracle" directory included in the patch package to $DM_HOME.
However, during Patch 04 testing, we uncovered a regression (on HPUX, HPUX-IA and
AIX) with new Oracle libraries (oci 9.2.0.8) where the secure mode connection to the
docbroker is failing. The problem was sourced to an SSL handshake problem with newer
Oracle libraries. Work on a solution is in progress with Oracle.
There is no problem if only the native mode is set and you do not connect in secure mode.
Do not use the dual mode for secure_connect_mode option in docbroker.ini.
From Patch 05 onwards, the new Oracle libraries for HPUX, HPUX-IA and AIX are not
being shipped. For customers upgrading from base version to P05 and above, there is no
problem. However, customers who have already deployed P01-P04 on HPUX, HPUX-IA
and AIX will need to revert to older Oracle libraries (oci 9.2.0.5) if they want to use the
secure mode connection.
Note:
This is applicable only for Oracle-UNIX/Linux ports.
From Patch 04 onwards, new Oracle libraries (oci 9.2.0.8) are shipped only for Solaris
and Linux platforms.
6.

After copying the files from the $DOCUMENTUM directory, delete the files (specified in
Steps 5b and 5c) and folder jboss4.2.0 (specified in step 5d) from $DOCUMENTUM
directory. This is required since the $DOCUMENTUM directory may cause path resolution
conflict.

7.

After you copy the files, start the following services in the specified order.
a. Start the Content Server.
b. Start the Java Method Server.
c. Start the Index Agent and Index Server.

8.

Deploy the MessagingApp.dar as follows:

a. You can install the DAR in two ways. Use java options as given in step (e) in which case
JDK is a pre-requisite, and the other way is to use Composer. Refer to the EMC
Documentum Composer User Guide for more information.
b. Ensure that the dfc.properties file under the Content Server Composer Headless location
has a docbroker, which has access to the repositories you need to apply the patch to. For
example:
c. $DM_HOME/install/composer/ComposerHeadless/plugins/com.emc.ide.external.dfc_1.
0.0/documentum.config
d. Create a file called DARInstall.xml at your preferred location, for example,
$USER_HOME.
e. Insert the dar (MessagingApp.dar location), docbase, username, password, domain into
the emc.install attributes accordingly.
<?xml version="1.0"?>
<project name="patchtarget" default="installdar">

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Post Deployment Steps

<description>
This is the ant script code to install a dar in the docbase
</description>
<target name="installdar">
<emc.install dar="MessagingApp.dar" docbase="mydocbase"
username="user1" password="hello" domain=""/>
</target>
</project>
f.

Run the following at command line:

java -cp
$DM_HOME/install/composer/ComposerHeadless/startup.jar
org.eclipse.core.launcher.Main -clean -data
$DM_HOME/install/composer/ComposerHeadless/workspace application org.eclipse.ant.core.antRunner -buildfile
<DARInstall.xml path>

9.

Install the Workflow DAR (Workflow.dar). You can do this manually using the DAR
Installer or Headless Composer. Refer to the EMC Documentum Composer User Guide for
more information.

10. Install the lifecycle.jar. The lifecycle.jar is included as part of a BOF Module, it exists as
content of a dmc_jar object in the docbase. The lifecycle.jar is not installed anywhere on the
file system under $DOCUMENTUM or $DOCUMENTUM_SHARED; it is only installed in
the docbase. Perform the following steps using iapi while being logged in as the docbase
install owner.
retrieve,c,dmc_jar where object_name = 'lifecycle.jar'
checkout,c,l
setfile,c,l,<pathname to lifecycle.jar from patch>
checkin,c,l

Note: Refer to the version.properties 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.

Post Deployment Steps

10

If Centera Storage is being used, then retrieve the dm_plugin object from the IAPI, where the
object_name is CSEC Plugin. After retrieving the object, perform a Setfile operation on it,
with the file path of the new emcplugin.dll for Windows and libemcplugin.so/sl for Unix,
which was delivered with the new patch. Save the dm_plugin object and restart the Content
Server.

If the XML store is being used, then retrieve the dm_plugin object from IAPI, where the
object_name is 'xhive_win32shrlib_externalstorage'. After retrieving the object, perform a
Setfile operation on it with the file path of the new xstoreplugin.dll for Windows and

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

Deployment Steps for Customization

xstoreplugin.so/sl for UNIX, which was delivered with the new patch. Save the dm_plugin
object and restart the Content Server.

If Snaplock Storage is being used, then retrieve the dm_plugin object from IAPI, where the
object_name is Snaplock Connector. After retrieving the object, perform a Setfile operation
on it with the file path of the new netappplugin.dll for Windows and libnetappplugin.so/sl for
UNIX, which was delivered with the new patch. Save the dm_plugin object and restart the
Content Server.

If multiple dm_plugin objects are in use for Centera, Xml Store, Snaplock, then perform the
above steps for all such dm_plugin objects.
Note: These steps are only to be performed for Centera plugin and Snaplock plugin objects
and not all the dm_plugin objects that exist in the repository.
Example (Wi ndows):
IAPI> retrieve,c,dm_plugin where object_name=CSEC Plugin
IAPI> setfile,c,l,%DM_HOME%\bin\emcplugin.dll,win32shrlib
IAPI> save,c,l

Deployment Steps for Customization

NOT APPLICABLE

Technical Notes
The following note is specific to Documentum Content Server 6.5 SP3:

Ensure that you deploy the MessagingApp.dar file as per the instructions in the Deployment
Steps section, depending on your operating system, in order to incorporate all the fixes made
to the MessagingApp.dar file.

To get the resolution for CS-36254/CS-36258, Jboss must be configured to allow more
requests to be executed on an open session.
The export of large XML files from the XML store may fail as JBoss closes the connection,
before the file has transferred completely.
This problem occurs since there is a limit on the number of requests that can be made on an
open connection. This limit is determined by the value of the parameter called
'maxKeepAliveRequests' in the server.xml file located in the jboss-web.deployer.
The default value of this parameter is 100. The recommended value for high performing
systems is a value between 500 and 1500.

Locate the
%DOCUMENTUM%\jboss4.2.0\server\DctmServer_MethodServer\deploy\jbossweb.deployer\server.xml file.

Edit the file and locate the <Connector> element for the HTTP/1.1.

Add an attribute to the <Connector> element called maxKeepAliveRequests and set it

to a value between 500 and 1500.

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe

11

Technical Notes

Save the server.xml file and restart Jboss.

To get the resolution for CS-29535, run the display_config_setup.ebs (binary attached with
the patch package) and populated data_dictionary_en.txt ( binary attached with the patch
package) using the following query:
DM_Home\bin> dmbasic f DM_HOME\install\tool\display_config_setup.ebs eEntrypoint
-- <docbase name> <super user> <password>
DM_Home\bin> dmbasic f dd_populate.ebs -eEntry_point -- <docbase name> <super user>
<password> %DOCUMENTUM%/dba/config/<docbasename>/data_dictionary.ini

12

EMC Documentum Content Server 6.5 SP3 Patch 24 ReadMe