EMC ® Documentum ®

Foundation Services
Version 6.5 SP2

Release Notes
P/N 300-009-285 A02

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2007-2009 EMC Corporation. All rights reserved.
Published July 2009
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.

Revision History:
June 2009: Initial release
July 2009: First revision—added “HelloWorld sample throws runtime exception (DFS-733)”
 Table of Contents

Chapter 1 Product Description .................................................................................... 7

Chapter 2 New Features and Changes ......................................................................... 9

New features and changes in DFS 6.5 SP2........................................................... 9
RepositoryInquiry service ............................................................................. 9
Finer control over ACS content ...................................................................... 9
New features and changes in DFS 6.5 ................................................................. 10
Virtual document service .............................................................................. 10
ACL service ................................................................................................. 11
Lifecycle service ........................................................................................... 11
Comment service .......................................................................................... 11
Analytics service .......................................................................................... 11
Task Management service ............................................................................. 11
QueryStore service ....................................................................................... 11
RichText object ............................................................................................. 12
Support for Lightweight System Object (LwSO) types ..................................... 12
Enhanced support for aspects ........................................................................ 12
WSDL-first support ...................................................................................... 12
Services catalog ............................................................................................ 12
Native 64-bit support .................................................................................... 12
IPv6 support ................................................................................................ 13
UCF client improvements.............................................................................. 13
Search service enhancements ......................................................................... 13
Changes to client configuration to support multiple service modules ............... 13
Simplified Ant TaskDef declaration................................................................ 13
Support for repository name wildcard ........................................................... 14

Chapter 3 Fixed Problems ........................................................................................... 15

VirtualDocumentService update fails when parent is XML (DFS-614)................... 15
Object service getContentUrls operation does not return renditions
(DFS-16) ........................................................................................................... 16
Development guide gives incorrect publish manifest location .............................. 16

Chapter 4 Environment and System Requirements ..................................................... 17

Hardware requirements .................................................................................... 17
Web application server machine requirements ................................................ 17
Software requirements ...................................................................................... 18
Web application server environment .............................................................. 19
Java version support ..................................................................................... 24
Documentum Foundation Services environment ............................................ 26
Documentum Foundation Services SDK requirements .................................... 27
Backward compatibility for Content Server .................................................... 27
Additional operating environments ............................................................... 27
VMware support ...................................................................................... 27
IBM Logical Partitioning support ............................................................... 28
Citrix support........................................................................................... 28

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 3

Table of Contents

Siteminder support ................................................................................... 29

RSA support ............................................................................................ 29
Native 64-bit support ................................................................................ 29
Prerequisites to run Documentum 6.5x products in the native
64-bit mode .......................................................................................... 29
64-bit support in web application server environment ............................. 29
IPv6 support ............................................................................................ 30
Cross-product dependencies and interoperability ............................................... 30
Embedded products ......................................................................................... 31

Chapter 5 Known Problems and Limitations ............................................................... 33

Known problems .............................................................................................. 33
HelloWorld sample throws runtime exception (DFS-733) ................................ 33
Axis consumer that does not register the service context will throw
a SerializableException (DFS-670) .................................................................. 34
JAX-WS in JDK 6 conflicts with JAX-WS in DFS (DFS-691) .......................... 34
DFS Development Guide gives incorrect information regarding
Query maxResultCount (DFS-228) ................................................................. 34
PAYLOAD_CONTINUE_ON_EXCEPTION does not return
successful operation details (DFS-226) ............................................................ 34
Errors in SDK sample code (DFS-367) ............................................................ 35
Missing castor-1.1-xml.jar & bpmutil.jar (DFS-683).......................................... 35
Limitations....................................................................................................... 35
Problem with defining custom resource bundles (DFS-684) ............................. 36
Method name conflict on remote client generation (DFS-65) ............................ 36
Problem calling DFS from a BOF module ....................................................... 36
DFS runtime depends on service-specific Profiles (DFS-30) .............................. 37
Registered context tokens are not valid across service applications .................. 37
Failover is not supported when using registered service contexts or
cached queries .............................................................................................. 37
Installation of DFS not permitted on same machine as Content
Server 5.3 ..................................................................................................... 38
Namespaces that cause proxies to be generated in the same package................ 38
DateProperty incremented by one hour during marshalling/
unmarshalling .............................................................................................. 38
Schema Service cannot be called without administrator rights ......................... 38
Service-generation tools place JAX-WS generated class in service JAR .............. 39

Chapter 6 Migration Issues .......................................................................................... 41

Address change of WorkflowService and SearchService ...................................... 41
DFS 6.0 client and DFS 6.5 server UCF incompatibility ........................................ 41
DFS 6.5 client and DFS 6.0 server UCF incompatibility ........................................ 42
Structure of client configuration file has changed ................................................ 42
Restructured jars and .NET assemblies ............................................................... 43
Deprecation of DFS 6.0 exception model ............................................................ 43
RepackageServiceTask ...................................................................................... 44

Chapter 7 Technical Notes ........................................................................................... 45

Combining USER_TRANSACTION_HINT and PAYLOAD_
PROCESSING_POLICY (DFS-301) ..................................................................... 45
Setting MaxReceivedMessageSize for .NET clients (DFS-439) ............................... 46
Avoid extending the DFS data model ................................................................. 47
Avoid having dctm.jar on classpath when executing services (DFS-242) ............... 48

4 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Table of Contents

Including a resources file in a service ................................................................. 48

Avoid unintended updates to system properties ................................................. 48
Re-use cached ActivityInfo to avoid creating new UCF connections ..................... 48
Avoiding out of memory errors when running Ant scripts .................................. 50

Chapter 8 Documentation ............................................................................................ 51

Documentum Foundation Services documentation set ........................................ 51
Obtaining the correct documentation ................................................................. 51

Chapter 9 Software Media, Organization, and Files ..................................................... 53

Software media ................................................................................................ 53
Organization .................................................................................................... 53
Files ................................................................................................................. 53

Chapter 10 Installation................................................................................................... 55
Documentum Foundation Services not supported on Weblogic 10.3 ..................... 55
Deployment on Websphere 7 ............................................................................. 55
Deployment on application servers using JDK 6 ................................................. 56

Chapter 11 Troubleshooting and Getting Help .............................................................. 57

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 5

Table of Contents

List of Tables

Table 1. Web application server machine requirements ........................................................ 17

Table 2. Third-party product versions not supported in this release ...................................... 18
Table 3. Web application server environment ...................................................................... 20
Table 4. Java version support ............................................................................................. 25
Table 5. Documentum Foundation Services environment .................................................... 26
Table 6. VMware support .................................................................................................. 28
Table 7. IBM Logical Partitioning support ........................................................................... 28
Table 8. Citrix support....................................................................................................... 29
Table 9. Documentum Foundation Services IPv6 compliance ............................................... 30

6 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 1
Product Description

Documentum Foundation Services (DFS) is a Service Oriented Architecture (SOA) development

framework and a set of APIs to support a variety of tools and languages for consumer development.
This is a set of technologies that completely replaces the previous Web Services Framework. DFS
technologies include:

DFS technology Description

Enterprise Content A set of services that provide access to core Content Server platform
Services functionality (for example creating, updating, and fetching objects), as well
as extended services, providing an interface to functionality from a variety
of EMC content management and archiving products.
Data model The DFS data model provides a consistent, service-oriented approach to
modeling data exchanged in ECM business processes.
Runtime support Server-side support for Enterprise Content Services, and optional
client-side runtime support for Java and .NET. The client-side runtime
support (the productivity layer) is not required, but does provide
convenience functionality, such as the ability to invoke services in local and
remote modes (Java only), simplified security interface, enhanced UCF
content transfer support, as well as helper methods and constructors.
Tools Tools for generating services and client runtime support for existing
services. Based on JAX-WS, the DFS tools are integrated with Composer for
execution using a GUI, and with Apache Ant, for scripted execution.
SDK A software development kit for development of DFS consumers and
services, including optional client libraries for Java and .NET consumer
development, Ant-based tools for code-first and WSDL-first service
generation, client proxy generation, and service publication, as well as
sample Java and .NET consumers and sample services.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 7

Product Description

8 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 2
New Features and Changes

The following new features and changes are provided in DFS 6.5 SP2 and in the original release
of DFS 6.5.
• New features and changes in DFS 6.5 SP2, page 9
• New features and changes in DFS 6.5, page 10

New features and changes in DFS 6.5 SP2

This section describes new feature and changes that apply specifically to the DFS 6.5 SP2 service pack.
• RepositoryInquiry service, page 9
• Finer control over ACS content, page 9

RepositoryInquiry service
This new service gets a list of available Documentum Content repositories without requiring
authentication.

Finer control over ACS content

The DFS remote and local APIs by default return an ACS URL in response to a request for content,
if an ACS URL is available for the content. Beginning with this service pack, a consumer can gain
finer control over this behavior using the urlReturnPolicy property of ContentProfile. The value of
urlReturnPolicy is an enum constant of type UrlReturnPolicy, as described in the following table:

Value Behavior
ALWAYS Return UrlContent where URL content is available; fail with exception where URL
content is not available.
NEVER Return actual content; never return UrlContent.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 9

New Features and Changes

Value Behavior
ONLY Return UrlContent where URL content is available; return no content in DataObject
where URL content is not available.
PREFER Return UrlContent where URL content is available; return actual content where URL
content is not available.
The default behavior is the same as PREFER, which is backward compatible with previous DFS
releases.

New features and changes in DFS 6.5

The following new features and changes were provided in DFS for Documentum 6.5.
• Virtual document service, page 10
• ACL service, page 11
• Lifecycle service, page 11
• Comment service, page 11
• Analytics service, page 11
• Task Management service, page 11
• QueryStore service, page 11
• Support for Lightweight System Object (LwSO) types, page 12
• Enhanced support for aspects, page 12
• WSDL-first support, page 12
• Services catalog, page 12
• Native 64-bit support, page 12
• IPv6 support, page 13
• UCF client improvements, page 13
• Search service enhancements, page 13
• Changes to client configuration to support multiple service modules, page 13
• Simplified Ant TaskDef declaration, page 13
• Support for repository name wildcard, page 14

Virtual document service

DFS 6.5 was enhanced to provide full VDM support in addition to the import and export functions
supported in Documentum 6. Examples of the new features include reordering, binding rules,
enable VDM manipulations, ordering, assemblies, and so forth. DFS offers full parity with DFC via
new relationship abstractions.

10 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 New Features and Changes

ACL service
DFS 6.5 introduces a new service that enables management of Access Control Lists (ACL) on
persistent objects in the repository, including creation, update, and deletion of ACLs.

Lifecycle service
DFS 6.5 introduces a new service that enables management of lifecycles on persistent objects in the
repository including attaching and detaching lifecycles, and executing operations associated with
those lifecycles.

Comment service
The Comment service (which requires the DCE DocApp) provides a set of operations to associate
a comment-thread with any repository object.

Analytics service
The Analytics Service (which requires Content Intelligence Services) provides classification
capabilities on documents available in an EMC Documentum repository.

Task Management service

The Task Management service (which requires Process Engine) contains most of the functionality
defined in IBM-WebService-HumanTask Specification v1.0 that includes task list and task
management functions.
The Task Management service provides functionality to retrieve custom task lists for a user, work
queue, or work queue processor. It also provides functionality for handling and managing manual
tasks and notifications.

QueryStore service
The QueryStore service provides operations to handle queries such as:
• storing queries, with or without the corresponding results
• listing saved queries
• viewing a saved query, with the corresponding results, if any

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 11

New Features and Changes

RichText object
The DFS data model now includes a representation of a RichText repository object, which can include
formatted text and embedded images.

Support for Lightweight System Object (LwSO) types

The DFS data model has been enhanced to provide support for the Documentum High Volume
Server through its model for LwSOs. Repository objects can be materialized, dematerialized, and
re-parented using object service operations.

Enhanced support for aspects

The DFS data model has been enhanced to provide a simple facility for attaching and detaching
aspects from objects during object creation, retrieval, or update. This capability can be used in the
context of the Object service and VersionControl service.

WSDL-first support
DFS enables developers to generate web services and their clients from a WSDL document (service
contract). This new feature is integrated with Composer and scriptable using Ant, and can be used
to generate service source code stubs based on a WSDL, or to generate client side support for an
existing service based on a WSDL.

Services catalog
DFS 6.5 provides a service-level discoverability infrastructure which represents a new platform
capability. This capability is planned to be leveraged by other CMA projects such as EMC
Documentum Composer (the Documentum IDE) and others. This capability can also be leveraged
at design-time by any developer using the CMA platform for discovery of relevant services to the
application/solution development at hand. All services are cataloged and categorized by domain or
solution space. All DFS based services are published into the catalog.

Native 64-bit support

Documentum 6.5 introduces native 64-bit support for running on 64-bit operating systems. The
native 64-bit support takes full advantage of 64-bits of address space and the concurrent use of
more than 4 GB of executable memory. For a fully qualified native 64-bit environment, you must
have a 64-bit processor, 64-bit operating system, 64-bit JVM, and 64-bit application server. Support
continues to be offered on 32-bit platforms.

12 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 New Features and Changes

IPv6 support
This product is compliant with IPv4-IPv6 dual-stack and native IPv6 enabled environments. The
Environment and System Requirements chapter provides more information on IPv6 support for
the product.

UCF client improvements

In DFS 6 and 6 SP1, UCF client components were packaged with the DFS client libraries. In DFS
6.5, the UCF installer is downloaded from the DFS server at runtime, and subsequently installs
the UCF client application.
In addition, the security of the client runtime has been enhanced, so that by default it downloads only
signed jars. The UCF jars on the DFS 6.5 server application are signed.
These changes have resulted in some version compatibility issues between DFS 6.5 and previous
versions. For more information see DFS 6.0 client and DFS 6.5 server UCF incompatibility, page 41
and DFS 6.5 client and DFS 6.0 server UCF incompatibility, page 42.

Search service enhancements

Search results can now be displayed in clusters. Clusters group results dynamically into categories
based on the values of the results’ attributes.

Changes to client configuration to support multiple

service modules
Productivity layer client configuration files for both Java and .NET have been enhanced to allow
flexible runtime lookup of services. This allows more generic code and declarative setting of service
addresses in a single location. New overloaded factory methods have been introduced to implement
this feature for service instantiation and service context registration.

Simplified Ant TaskDef declaration

You can now reference the DFS SDK Ant tasks in your build files by including the emc-dfs-tasks.xml
file. By including this file, you can call the Ant tasks without declaring taskdefs for each Ant task that
you want to use. Referencing the emc-dfs-tasks.xml file is the preferred method for calling the DFS
SDK Ant tasks and requires Ant 1.7. The old method is still supported, but is deprecated. For more
information refer to the EMC Documentum Foundation Services 6.5 Development Guide.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 13

New Features and Changes

Support for repository name wildcard

In a RepositoryIdentity, you can use the “*” wildcard (represented by the constant
RepositoryIdentity.DEFAULT_REPOSITORY_NAME) in place of the repository name. In this case
DFS will authorize the credentials against the global registry. If no global registry is available, or if
the credentials are not valid on the global registry, the authentication fails.
IServiceContext context = ContextFactory.getInstance().newContext();
context.addIdentity(new RepositoryIdentity(RepositoryIdentity.DEFAULT_REPOSITORY_NAME,
"username",
"password",
""));
IObjectService service = ServiceFactory.getInstance()
.getRemoteService(IObjectService.class,
context,
"core",
"http://DfsHost:9080/services");

You can simplify things a bit by using BasicIdentity, which has an implied wildcard. The following
two instances of Identity are equivalent:
new RepositoryIdentity(RepositoryIdentity.DEFAULT_REPOSITORY_NAME,
"username",
"password")
new BasicIdentity("username", "password")

14 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 3
Fixed Problems

This section identifies problems and limitations, documented in the release notes of the applicable
minor version release or prior service pack(s), that have since been resolved. For a comprehensive list
of bugs fixed in this release, refer to the Powerlink website, using the procedure below.
Within two weeks of the release, a list of the fixed problems in the release will be posted on the
Powerlink website (http://powerlink.EMC.com).

To view the list of fixed problems:

1. Log into the Powerlink website.
You must have a software support agreement to log in and access the list of fixed bugs.
2. From the Powerlink menu bar, select Support > Knowledgebase Search > Documentation and
White Papers Search.
The Knowledgebase Search page appears.
3. In the Search For text box, enter Fixed.
4. In the Refine by Product text box, begin typing in the product name. Choose your product
from the list that appears.
5. Choose the product Version for which you would like to view fixed problems.
6. From the Select Document Type(s) list box, select Fixed Bugs List.
7. Click Search.
8. Scroll to the bottom of the page and select the fixed problems document from the list of search
results.

VirtualDocumentService update fails when

parent is XML (DFS-614)
When the VirtualDocumentService update operation attempts to attach child nodes to an XML parent
that has an associated XML application, it will fail to add the children and convert the parent to a
simple document. If your project does not require that the document in question be associated
with an XML application, you can get around this limitation by adding the following processing
instruction to the XML document, which will disassociate it from the XML application.
<?dctm xml_app="ignore"?>

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 15

Fixed Problems

Object service getContentUrls operation does

not return renditions (DFS-16)
The getContentUrls operation should return multiple content Urls for an object if that object has
renditions. At present the operation returns only the URL of the object’s primary content.

Development guide gives incorrect publish

manifest location
The EMC Documentum Foundation Services 6.5 Development Guide (version A01) gives the wrong name
and location for emc-dfs-publish-manifest.xml on pages 176 and 177. The text on page 176 should
read:
%DFS_SDK%/etc/emc‑dfs-publish‑manifest.xml

In the sample on page 177 the text should read:

-file %DFS_SDK/etc/emc-dfs-publish-manifest.xml

16 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 4
Environment and System
Requirements

This chapter lists the hardware (machine) requirements and software versions supported with this
release. Machine resources, non-Documentum software components (Operating System, Java
Runtime Environment, and so forth), and other EMC Documentum products determine the unique
environment for each EMC Documentum product. Hardware requirements, page 17, addresses basic
machine resource requirements. Software requirements, page 18, addresses specific software versions
that are required for the installation platform.
Documentum Foundation Services (DFS) is installed as part of the Content Server installation and
supports the same range of platforms as Content Server. Documentum Foundation Services can also
be installed separately on its own web application server or cluster.

Hardware requirements
This section lists nominal machine resources required for product installation and use.

Web application server machine requirements

The following table provides nominal resource requirements for Documentum Foundation Classes
on a web application server machine.

Table 1. Web application server machine requirements

Hard disk space [1] RAM [2] CPU

Minimum: 2 GB 800 Mhz (minimum), 1 GHz or
greater (recommended)
600 MB for one application

1 GB for two applications

Recommended:

800 MB for one application

1.2 GB for two applications

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 17

Environment and System Requirements

Note: The following specific notes apply to the web application server machine requirements table:
[1] You must also have sufficient free disk space to handle temporary content transfer files, which
can vary substantially from one enterprise to another.
[2] The amount of RAM that is available after taking into consideration all other RAM utilization
requirements.

Software requirements
This section provides information on supported software environments.
The tables in this section reflect the latest versions of third-party products, upon which the EMC
Documentum product depends, that are supported at the time of this release. EMC Documentum
recommends that you upgrade third-party products to the version listed for this release. If you
cannot upgrade your third-party products to the version listed for this release, EMC Documentum
continues to support all third-party product versions supported for EMC Documentum product
versions 6.x and 5.3x, with the following caveats:
• the third-party product is not of the same or earlier version than those versions listed in Table
2, page 18
• the third-party product version is still supported by the third-party vendor
• the third-party product version is forward compatible with the version supported in this release.
For information on currently supported environments and future updates, refer to the Product
Information System on the Powerlink website: http://powerlink.EMC.com.

Table 2. Third-party product versions not supported in this release

Product Category Third-party product Version

Windows 2000 SP2 Update Rollup 1
Mac OS X 10.2.8, 10.3.9
Solaris 8
Operating System
AIX 5.2
HP-UX HP-UX 11
Red Hat Enterprise Linux 3.x
Oracle 9i 9.2.0.8, 10.1.0.5
Database SQL Server 2000 SP4
DB2 UDB 8.1 FixPak 14, 8.2 FixPak 7

18 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

Product Category Third-party product Version

BEA WebLogic Server 8.1 SP6
Oracle WebLogic Server 10.3
Tomcat 5.0.28
Application Server
JBoss 5.0
IBM WebSphere AS 5.1.1.13, 6.0.2.17
Oracle AS 10g 9.0.4.3, 10.1.2
Mozilla 1.7.13
Browser Netscape 7.2
Safari 1.3.2
Sun JRE 1.4.2_13
JRE (Client) Microsoft JVM 5.0.0.3810
Apple Java 1.3.1 Release 2
Java (Server) Java 1.4.x
BEA WebLogic Portal 8.1 SP6
Portal Server
IBM WebSphere Portal 5.1.0.4

Web application server environment

Documentum Foundation Services runs in a web application server environment. The web
application server environment consists of a specific combination of operating system, web
application server, and JDK. The following table lists the supported web application server
environments for Documentum Foundation Services.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 19

Environment and System Requirements

Table 3. Web application server environment

Web application server

IBM Web- IBM
Sphere Ap- WebSphere
BEA plication Application
Apache Apache WebLogic Server V6.1 Server V7.0 Oracle AS Red Hat
Operating Tomcat Tomcat Server 9.2 Fix Pack 21 Fix Pack 1 10g R3 (10. JBoss EAP
system Processor 5.5.25 6.0.18 MP2 [3] (6.1.0.21) (7.0.0.1) 1.3.3.0) 4.3.0
Windows
Server 2003
R2 with IA-32, x64 X X X [2] X [2] X [2] X X
SP2 (32-bit
version)
Windows
Server 2003
IA-32, x64 X X X [2] X [2] X [2] X X
SP2 (32-bit
version)
Windows
Server 2008
IA-32, x64 X X X [2]
(32-bit
version) [5]
Windows
Server 2003
x64 [4] X X X [2] X [2] X [2] X X
R2 with SP2
x64 Edition
Windows
Server 2003
x64 [4] X X X [2] X [2] X [2] X X
SP2 x64
Edition

20 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

Web application server

IBM Web- IBM
Sphere Ap- WebSphere
BEA plication Application
Apache Apache WebLogic Server V6.1 Server V7.0 Oracle AS Red Hat
Operating Tomcat Tomcat Server 9.2 Fix Pack 21 Fix Pack 1 10g R3 (10. JBoss EAP
system Processor 5.5.25 6.0.18 MP2 [3] (6.1.0.21) (7.0.0.1) 1.3.3.0) 4.3.0
Windows
Server 2008
x64 [4] X X X [2]
x64 Edition
[5]
Ultra-
Solaris 10 SPARC [1] X X X [2] X [2] X [2] X X
[4]
AIX 5L V5.3 Power [1]
X X X X [2] X [2] X
TL9 [4]
AIX V6.1 Power [1]
X X X X [2] X [2] X
TL2 [4]
HP-UX 11i
PA-RISC 2.0
v2 Update 2 X X X X
[1] [4]
(B.11.23)
HP-UX 11i
Itanium 2
v2 Update 2 X X X X
[1] [4]
(B.11.23)
HP-UX 11i
PA-RISC 2.0
v3 Update 1 X X X X
[1] [4]
(B.11.31)

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 21

Environment and System Requirements

Web application server

IBM Web- IBM
Sphere Ap- WebSphere
BEA plication Application
Apache Apache WebLogic Server V6.1 Server V7.0 Oracle AS Red Hat
Operating Tomcat Tomcat Server 9.2 Fix Pack 21 Fix Pack 1 10g R3 (10. JBoss EAP
system Processor 5.5.25 6.0.18 MP2 [3] (6.1.0.21) (7.0.0.1) 1.3.3.0) 4.3.0
HP-UX 11i
Itanium 2
v3 Update 1 X X X X
[1] [4]
(B.11.31)
Red Hat
Enterprise IA-32 X X X X [2] X [2] X [2] X
Linux 4.7
Red Hat
Enterprise x64 [1] [4] X X X X [2] X [2] X [2] X
Linux 4.7
Red Hat
Enterprise IA-32 X X X X [2] X [2] X [2] X
Linux 5.3
Red Hat
Enterprise x64 [1] [4] X X X X [2] X [2] X [2] X
Linux 5.3
SUSE Linux
Enterprise
IA-32 X X X X [2] X [2] X [2] X
Server 10
SP2

22 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

Web application server

IBM Web- IBM
Sphere Ap- WebSphere
BEA plication Application
Apache Apache WebLogic Server V6.1 Server V7.0 Oracle AS Red Hat
Operating Tomcat Tomcat Server 9.2 Fix Pack 21 Fix Pack 1 10g R3 (10. JBoss EAP
system Processor 5.5.25 6.0.18 MP2 [3] (6.1.0.21) (7.0.0.1) 1.3.3.0) 4.3.0
SUSE Linux
Enterprise
x64 [1] [4] X X X X [2] X [2] X [2] X
Server 10
SP2
Note: The X symbol denotes the supported combination of operating system and web application server.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 23

Environment and System Requirements

Note: The following specific notes indicated by [ ] apply to the web application server environment
table:
[1] Support 64-bit version of operating system through the 32-bit compatibility mode.
[2] Clustering (failover) support. See general notes for exceptions below.
[3] BEA WebLogic web application server clustering support requires external load balancer or
Web Server acting as a load balancer.
[4] Support 64-bit version of operating system in native mode.
[5] Java 5.0.x is not supported with Windows Server 2008.
Note: The following general notes apply to the web application server environment table:
• The following Windows Server 2003 editions are supported: Standard, Enterprise, Data Center.
• IA-32 = Intel Architecture 32-bit
• x64 = 64-bit Architecture which includes AMD64 and Intel 64
• Support all the Java 5.0.x and 6.0.x version supported by each web application server. No support
for JDK 1.4.x.
• Support 32-bit version and 64-bit version of web application server.
• Web servers internal to the supported web application servers are supported.
• The Web server associated with a web application server, whether internal or external, must also
support chunked requests. This means that Web servers forward HTTP requests using chunked
transfer encoding (as described in the HTTP/1.1 protocol) to the back-end web application server.
If chunked requests are not supported then the client should use “UCF Alternative Chunking”
mode. For details on configuring and using “UCF Alternative Chunking” mode, refer to the
Web Development Kit Development Guide.
• Only the following forward proxy configurations are supported:
— Auto configuration script
— Explicitly specifying the proxy server (for example, the host and port)
— Auto detect settings, configured using ProxyCfg.exe (proxy configuration tool)
• BEA WebLogic 10.0 MP1 is supported. For the complete support matrix for BEA WebLogic 10.0
MP1 see the Documentum Foundation Services 6.5 Release Notes. Support for Oracle WebLogic
Server 10g Release 3 (10.3) is planned for a release to follow 6.5 SP2.
• English, Japanese, Korean, Russian (English with regional setting set to Russian) and Simplified
Chinese versions of the operating system are supported.

Java version support

The Java version support table consists of a specific combination of Java version, and web application
server.

24 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

Table 4. Java version support

Web application Server

IBM IBM
WebSphere WebSphere Sun Java
BEA Application Application Oracle Red Hat System
Apache Apache WebLogic Server V6.1 Server V7.0 AS 10g JBoss Applica- Sun GlassFish
Tomcat Tomcat Server 9.2 Fix Pack 21 Fix Pack 1 R3 (10. EAP tion Server Enterprise
Java 5.5.25 6.0.18 MP2 (6.1.0.21) (7.0.0.1) 1.3.3.0) 4.3.0 8.2 Server v2.1
5.0.x X X X X X X X X
6.0.x X X X X X

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 25

Environment and System Requirements

Documentum Foundation Services environment

The Documentum Foundation Services environment consists of a specific combination of operating
system, Java Runtime Environment (JRE), and processor. The following table lists the supported
platforms for Documentum Foundation Services.

Table 5. Documentum Foundation Services environment

Operating system Processor

Windows Server 2003 R2 with SP2 (32-bit
IA-32, x64
version)
Windows Server 2003 SP2 (32-bit version) IA-32, x64
Windows Server 2008 (32-bit version) IA-32, x64
Windows Server 2003 R2 with SP2 x64 Edition x64 [2]
Windows Server 2003 SP2 x64 Edition x64 [2]
Windows Server 2008 x64 Edition x64 [2]
Solaris 10 UltraSPARC [1] [2]
AIX 5L V5.3 TL9 Power [1] [2]
AIX V6.1 TL2 Power [1] [2]
HP-UX 11i v2 Update 2 (B.11.23) PA-RISC 2.0 [1] [2]
HP-UX 11i v2 Update 2 (B.11.23) Itanium 2 [1] [2]
HP-UX 11i v3 Update 1 (B.11.31) PA-RISC 2.0 [1] [2]
HP-UX 11i v3 Update 1 (B.11.31) Itanium 2 [1] [2]
Red Hat Enterprise Linux 4.7 IA-32
Red Hat Enterprise Linux 4.7 x64 [1] [2]
Red Hat Enterprise Linux 5.3 IA-32
Red Hat Enterprise Linux 5.3 x64 [1] [2]
SUSE Linux Enterprise Server 10 SP2 IA-32
SUSE Linux Enterprise Server 10 SP2 x64 [1] [2]

Note: The following specific note indicated by [ ] applies to the Documentum Foundation Services
environment table:
[1] Support 64-bit version of operating system through the 32-bit compatibility mode.
[2] Support 64-bit version of operating system in native mode.
Note: The following general notes apply to the Documentum Foundation Services environment table:
• The following Windows Server 2003 editions are supported: Standard, Enterprise, Data Center.
• IA-32 = Intel Architecture 32-bit
• x64 = 64-bit Architecture which includes AMD64 and Intel 64
• For Documentum Foundation Services in standalone mode, Java J2SE 5.0.x is supported. For
Documentum Foundation Services running in a web application server environment, all Java 5.0.x

26 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

versions supported by each web application server configuration are supported. No support for
Java 1.4.x.
• Clustering (failover) is supported with standalone Documentum Foundation Services installer
only. Failover not supported if application uses cached queries or registered service contexts.
• No clustering (failover) support for Documentum Foundation Services installed with Content
Server.
• SSO is supported.
• .NET Framework 3.0.x and 3.5.x are supported.

Documentum Foundation Services SDK requirements

This section provides information on Documentum Foundation Services SDK requirements.
For .NET consumers:
• .NET Framework 3.0.x or 3.5.x
• Visual Studio 2005 or 2008
Note: Sample solutions are compiled using Visual Studio 2008
For Java remote productivity-layer consumers and Java local API consumers:
• JDK 5 or 6
For building services:
• Ant 1.7.x

Backward compatibility for Content Server

In addition to the homogeneous stacks (5.3.x Content Server + 5.3.x Client and D6.x Content Server +
D6.x Client), the following deployment scenarios will be supported in D6.5:
• 5.3.x Content Server + D6.x Global Registry + D6.x Client
• D6.x Content Server + 5.3.x Global Registry + 5.3.x Client
• D6.x Content Server + D6.x Global Registry + D6.x Client

Additional operating environments

This section provides information on supported operating environments.

VMware support

The following table lists the VMware product versions supported on specific operating system(s).

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 27

Environment and System Requirements

Table 6. VMware support

Product Operating system Processor

Windows & Linux (See
VMware Server VMware website for the specific IA-32, x64
supported version)
Windows & Linux (See
VMware Workstation VMware website for the specific IA-32, x64
supported version)
VMware ESX Server N/A IA-32, x64

Note: The following general notes apply to the VMware support table:
• IA-32 = Intel Architecture 32-bit
• x64 = 64-bit Architecture which includes AMD64 and Intel 64
• Documentum fully supports all of our products other than index server 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 EMC Documentum product. VMware
supports only x86 microprocessor architecture.

IBM Logical Partitioning support

The following table lists the IBM Logical Partitioning (LPAR) product versions supported on specific
operating system(s).

Table 7. IBM Logical Partitioning support

Product versions Operating system Processor

IBM Logical Partitioning AIX 5L V5.3 TL9
Power
(LPAR) [1] [2] AIX V6.1 TL2

Note: The following specific note indicated by [ ] applies to the IBM Logical Partitioning support table:
[1] IBM Logical Partitioning is not supported for Index Server.
[2] LPAR specific tuning, performance guidelines, recommendations, and specific setup issues
would be provided and communicated directly by IBM to the customer. We are currently not
aware of any Documentum specific LPAR setup issues. We expect the customer to perform
relevant use case scenario based pre-production testing on LPAR. This support assumes that
these tests with relevant configurations perform successfully prior to going into production. If
the issue is determined to be related to incompatibility of the LPAR environment, EMC and the
customer will jointly pursue with IBM for resolution.

Citrix support

The following table lists the Citrix product versions supported on specific operating system(s).

28 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

Table 8. Citrix support

Product versions Operating system Processor

Windows Server 2003 SP2
Citrix XenApp 5.0 IA-32, x64
(32-bit version)

Note: The following general notes apply to the Citrix support table:
• IA-32 = Intel Architecture 32-bit
• x64 = 64-bit Architecture which includes AMD64 and Intel 64

Siteminder support

eTrust Siteminder Policy Server 6.0 SP5 is supported for all supported web application servers and
operating systems, except there is no Firefox browser support.

RSA support

RSA Access Manager 6.0.4 is supported for all supported web application servers and operating
systems.

Native 64-bit support

Documentum 6.5x introduces native 64-bit support such that 64-bit Documentum applications can
run on 64-bit operating systems.

Prerequisites to run Documentum 6.5x products in the native 64-bit mode

You must ensure that your 64-bit environment comprises the following prerequisite components
before you run the Documentum 6.5x products:
• 64-bit processor
• 64-bit operating system
• 64-bit Java Virtual Machine
• 64-bit web application server (if needed). Ensure that the web application server is bundled with
64-bit Java Virtual Machine.

64-bit support in web application server environment

Documentum 6.5x continues to support 32-bit versions of the Microsoft Windows operating system.
In the 64-bit domain, Documentum 6.5x does not support 64-bit versions of the Microsoft Windows
operating system. However, as an exception, Documentum 6.5x provides native support of the

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 29

Environment and System Requirements

64-bit version of Microsoft Windows Server 2003 for web application server- and portal server-based
products.
Note: The following general notes apply to Native 64-bit support in Documentum 6.5x:
• Check your web application server documentation for information about configuration changes
you need to make to run Documentum 6.5x product on a 64-bit platform. For example, the IBM
WebSphere Application Server V6.1 Fix Pack 13 (6.1.0.13) ships with platform-specific 32-bit
and 64-bit installers.
• For information about tuning a 64-bit Java Virtual Machine and garbage collection parameters,
refer to the Java Virtual Machine documents of the relevant vendor.
• Porting the 32-bit Documentum 6.5x application to a 64-bit platform: Documentum 6.5x product
must install a 64-bit compatible Java Virtual Machine before porting the 32-bit Documentum
6.5x application to a 64-bit platform.

IPv6 support

Documentum 6.5x now supports dual-stack (IPv4 or IPv6) and native IPv4 operation. In addition
to this, Documentum 6.5x products which are Java based applications also support native IPv6
operation. Support for dual-stack operation enables Documentum 6.5x products to use the
appropriate protocol (IPv4 or IPv6) when communicating with third-party products and other
Documentum products.
Documentum Foundation Classes determines the operating mode, and by default, DFC is configured
for dual-stack and native IPv6 operation. The Documentum Foundation Classes Installation Guide
provides information on how to configure DFC for native IPv4 operation.
Note: Information on protocol support for third-party products is provided in the third-party
product documentation.

Table 9. Documentum Foundation Services IPv6 compliance

Dual-Stack
Product Native IPv6
(IPv4 & IPv6)
Documentum Foundation Services X X
Documentum Foundation Classes X X
Note: The X symbol denotes the support started with 6.5 release.

Cross-product dependencies and

interoperability
This section lists Documentum products that are depended on in order to achieve a basic level of
functionality and lists related Documentum products that enhance overall functionality.

30 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Environment and System Requirements

You may have to install some of the listed products on separate host or client machines due to
differences in the Documentum Foundation Classes versions included with those products. Before
installing a product, check the product’s Release Notes for supported configurations.
The 32-bit version of Documentum 6.5x products can run in the 32-bit native mode and the 64-bit
compatibility mode. However, the 64-bit version of Documentum 6.5x products can run only in
the 64-bit native mode.
For Documentum Foundation Services, the following products are prerequisites:
• Content Server 5.3, 5.3 SPx, 6, 6 SP1, 6.5, 6.5 SP1 or 6.5 SP2
— Business Object Framework dependencies
Some services delivered with DFS depend on Service-based Business Objects (SBOs). Because
SBOs are downloaded to the service dynamically from the Global Registry, environments that
use these services must have a correctly configured global registry, and the global registry
credentials must be set in the DFS dfc.properties file when DFS is deployed. The following
paragraphs provide details about specific services.
CommentService is dependent on SBOs included in the DCE DAR (formerly DocApp). The
CommentService will not work with the default DAR installed by Content Server version 6,
version 6.5, version 6.5 SP1 or version 6.5 SP2. To get CommentService functionality, clients
must update to the latest DCE DAR (version 6.5 SP2).
The Workflow service is not supported on Content Server 5.3 or 5.3 SPx. It requires Content
Server 6, 6 SP1, 6.5, 6.5 SP1 or 6.5 SP2, which include the required DAR.
The TaskManagement service requires that the latest Process Engine be installed on the
Content Server. Process Engine installs the BPM DAR, which contains SBOs and modules
required by the service.

Embedded products
Installing EMC Documentum products includes the following additional products.
For Documentum Foundation Services:
• Documentum Foundation Classes 6.5 SP2
• Red Hat JBoss Enterprise Application Platform 4.2.0 CP01
• Unified Client Facilities 6.5 SP2
• Integration with ACS/BOCS (distributed content)
Note: JBoss is only embedded when you use the installer or the Java Method Server. It is not
embedded if you deploy Documentum Foundation Services on another web application server.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 31

Environment and System Requirements

32 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 5
Known Problems and Limitations

This section identifies problems and limitations that may affect your use of the product.
EMC Documentum makes the latest information about customer-reported issues and known
problems are posted on the Powerlink website (http://powerlink.EMC.com). You must have a
software support agreement to log in and access the list of issues.

Known problems
This section describes known defects in EMC Documentum Foundation Services that may affect
your use of the product.
• HelloWorld sample throws runtime exception (DFS-733), page 33
• Axis consumer that does not register the service context will throw a SerializableException
(DFS-670), page 34
• JAX-WS in JDK 6 conflicts with JAX-WS in DFS (DFS-691), page 34
• DFS Development Guide gives incorrect information regarding Query maxResultCount
(DFS-228), page 34
• Errors in SDK sample code (DFS-367), page 35
• Missing castor-1.1-xml.jar & bpmutil.jar (DFS-683), page 35
• PAYLOAD_CONTINUE_ON_EXCEPTION does not return successful operation details
(DFS-226), page 34

HelloWorld sample throws runtime exception (DFS-733)

When a client invokes the HelloWorldService sample service, a NoClassDefFoundError is thrown.
This is caused by an incorrect pathelement setting in the <packageService> Ant task. To correct the
problem, modify the <pathelement> location attribute within <packageService> that references dfc.jar
so that it references all of the jar files in the dfc library folder, as follows:
<pathelement location="${dfs.sdk.libs}/dfc/*.jar"/>

You must then repackage and redeploy the HelloWorld sample.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 33

Known Problems and Limitations

Axis consumer that does not register the service

context will throw a SerializableException (DFS-670)
The AxisDfsNoRegistrationConsumer sample included in emc-dfs-sdk-6.
5\samples\WSDLBasedConsumers will throw a SerializableException because of
incorrect namespaces in the SOAP message. To fix the sample, add one lie of code before addHeader,
as shown below:
public void callSchemaService()
{
...
header.declareDefaultNamespace("http://context.core.datamodel.fs.documentum.emc.com/");
client.addHeader(header);
...

JAX-WS in JDK 6 conflicts with JAX-WS in DFS (DFS-691)

The JAX-WS version used by DFS is 2.1.4; however, the JAX-WS version used in JDK 6 is 2.0. This can
occasionally lead to errors. To work around this problem:

1. Copy jaxb-api.jar , jaxb-impl.jar and jaxws-api.jar from %DFS_SDK%/lib/java/jaxws.

2. Paste them into %JAVA_HOME%/jre/lib/endorsed (if endorsed folder doesn’t exist then create it).
3. Restart the Java process.

DFS Development Guide gives incorrect information

regarding Query maxResultCount (DFS-228)
The maxResultCount field of the QueryExecution class determines the maximum number of query
results that will be returned by the Query service. By default, the limit is set to 100. If this value is
set to -1, the defined maximum limit will be used, which is set in the dfs-runtime.properties file in
the entry dfs.query_cache_policy.query_max_result. In DFS as shipped, this value is set to 500. You
can set this to a higher value if needed; however, if you expect the query to return a large number of
results you may wish to use cached query processing.

PAYLOAD_CONTINUE_ON_EXCEPTION does not

return successful operation details (DFS-226)
If the PAYLOAD_PROCESSING_POLICY service context property is set to IServiceContext.
PAYLOAD_CONTINUE_ON_EXCEPTION, DFS services do not return expected information about
operations that did succeed, if any of the operations in a batch process fails. The default behavior of
DFS services is IServiceContext.PAYLOAD_FAIL_ON_EXCEPTION.
This feature will be deprecated in a future release, so we recommend that consumers do not set
PAYLOAD_PROCESSING_POLICY.

34 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Known Problems and Limitations

Errors in SDK sample code (DFS-367)

The following errors were found in the samples shown in the Enterprise Content Services 6.5 SP1
Reference.
In example 328 on page 76 (Modifying repeating properties), the names of the actions do not match
their meanings:
ValueAction appendAction = new ValueAction(ValueActionType.INSERT, 0);
ValueAction deleteAction = new ValueAction(ValueActionType.APPEND, 1);

The first variable would be better named insertAction, the second variable appendAction.
In example 340 on page 94 (Creating a lightweight object with shared parent), the second
sharedParent should be lightObject:
DataObject sharedParent = new DataObject(new ObjectIdentity(defaultRepositoryName),
shareTypeName);
sharedParent.getProperties().set("object_name", "mySharedParent");
DataObject lightObject = new DataObject(new ObjectIdentity(defaultRepositoryName),
lightTypeName);
sharedParent.getProperties().set("object_name", "myLightObject");

Missing castor-1.1-xml.jar & bpmutil.jar (DFS-683)

Two jar files are missing from DFS, which results in a ClassNotFound exception when you use the
TaskManagement service. To work around this, you can:

1. Extract emc-dfs.ear.
2. Locate castor-1.1-xml.jar and bpmutil.jar in a Taskspace, Process Builder, or Webtop installation.
3. Copy these files to emc-dfs\APP-INF\lib.
4. Repackage and deploy emc-dfs.ear.
5. If you are using the DFS SDK Java library, copy these files to emc-dfs-sdk-6.5\lib\java\bof.

Limitations
This section describes limits on the usability of current functionality. The limitations may be part of
the product design or may result from issues with associated third-party products.
• Problem with defining custom resource bundles (DFS-684), page 36
• DFS runtime depends on service-specific Profiles (DFS-30), page 37
• Registered context tokens are not valid across service applications, page 37
• Failover is not supported when using registered service contexts or cached queries, page 37
• Installation of DFS not permitted on same machine as Content Server 5.3, page 38
• Namespaces that cause proxies to be generated in the same package, page 38

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 35

Known Problems and Limitations

• DateProperty incremented by one hour during marshalling/unmarshalling, page 38

• Schema Service cannot be called without administrator rights, page 38
• Service-generation tools place JAX-WS generated class in service JAR, page 39

Problem with defining custom resource bundles

(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 would be defined as "resource.bundle.3" and the one defined in local-dfs-runtime.properties
would override it. Users of this approach should be aware that this could cause a future migration
issue.

Method name conflict on remote client generation

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

Problem calling DFS from a BOF module

The JAX-WS implementation uses the thread context class loader, rather than the class loader of
the executing class. For this reason when calling a DFS service from a BOF module or Java server
method, it is necessary to set the current class loader to the class loader of the module, as 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 of the calling object’s class before
calling the DFS service.
try
{

36 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Known Problems and Limitations

ClassLoader classClassLoader = this.getClass().getClassLoader();

Thread.currentThread().setContextClassLoader(classClassLoader);
// ...call DFS service
}

3. Very importantly, in a finally block, reset the class loader to the previously saved thread class
loader.
finally
{
Thread.currentThread().setContextClassLoader(oldContextClassLoader);
}

DFS runtime depends on service-specific Profiles

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

Registered context tokens are not valid across service

applications
A registered service context can be shared only by services that are executed in the same server-side
process. Typically this means that the services are deployed in the same EAR file on the application
server. This limitation means that the client must be aware of the physical location of the services that
it is invoking and manage service context sharing based on shared physical locations.
Registration of service context is not required, so to avoid this problem, do not register the service
context.

Failover is not supported when using registered service

contexts or cached queries
In clustered environments, failover is not supported for registered service contexts and cached
queries. If you require failover support, do not register service contexts or use cached queries.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 37

Known Problems and Limitations

Installation of DFS not permitted on same machine as

Content Server 5.3
Because of a potential security problem, deployment of DFS on the same machine as Content Server
5.3 is not supported. The conditions that cause the security risk are as follows:
• OS administrator is “Administrator”.
• Administrator was used to install Documentum 5.3
• Administrator was used to create the repository on the machine, which means that Administrator
is a superuser.
• Administrator was used to install DFS on that machine.
Under these conditions, the DFS service is running as Administrator, which can potentially give a
user who knows the Administrator name superuser access to the repository. This problem has been
corrected in subsequent versions of Content Server.

Namespaces that cause proxies to be generated in the

same package
When creating custom services, a conflict occurs when you have two services that have the following
namespaces: http://a.b.c.d and http://b.c.d/a In this case, when JAX-WS tries to generate the client
proxies for these two services, they will be generated in the same package (d.c.b.a), so you will
only be able to call the first service in the classpath. Avoid assigning namespaces in this way to
prevent this situation.

DateProperty incremented by one hour during

marshalling/unmarshalling
This behavior was documented as a bug for the Documentum 6 release of DFS. It has been determined
that this behavior is caused by interaction between JAXB and the Java Development Kit, and that
it impacts only dates prior to 1990.
The JDK does not compensate for Daylight Savings Time for dates before 1981, and it compensates
incorrectly for dates from 1981 through 1990.
This remains a DFS limitation, which will only impact data with dates prior to 1990 that need to be
accurate to the hour.

Schema Service cannot be called without administrator

rights
The Schema service will not work when invoked using a user name that does not have administrator
privileges.

38 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Known Problems and Limitations

As a workaround an administrator can register dm_docbase_id map as a registered table.

Service-generation tools place JAX-WS generated class

in service JAR
When a service is generated using the DFS service-generation tools, artifacts generated by JAX-WS,
rather than the expected client-defined data classes, are archived in JAR files created by the tools,
if the data class resides in the same package as the service endpoint, and if the data class does not
appear in the service signature.
For example, suppose you define the following data objects that are used by a service:
• com.service.SomeService
• com.service.DataClassA
• com.service.DataClassB
Suppose as well that DataClassB extends DataClassA. The service has only the following method:
SomeService.theOnlyMethod(DataClassB)
In this case, when generating JAX-WS artifacts the generated DataClassA will not be deleted and will
be archived in the resulting JAR file, rather than the client defined class.
You can repair the JAR file by removing the class generated by JAX-WS and replace it with the
client defined class file.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 39

Known Problems and Limitations

40 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 6
Migration Issues

The following section address issues related to compatibility of DFS 6.5 with previous releases
and upgrade to DFS 6.5 from a previous release.
• Address change of WorkflowService and SearchService, page 41
• DFS 6.0 client and DFS 6.5 server UCF incompatibility, page 41
• DFS 6.5 client and DFS 6.0 server UCF incompatibility, page 42
• Structure of client configuration file has changed, page 42
• Restructured jars and .NET assemblies, page 43
• Deprecation of DFS 6.0 exception model, page 43
• RepackageServiceTask, page 44

Address change of WorkflowService and

SearchService
In DFS 6.0 the WorkflowService and SearchService were in the core domain. In DFS 6.5 have been
moved to the bpm and search domains, respectively, but they are still available in the core domain for
backward compatibility. Their core domain location is deprecated and will no longer be available in a
future release, so clients that access these services should be modified to use the new domain.

DFS 6.0 client and DFS 6.5 server UCF

incompatibility
UCF content transfer will not succeed if the client is DFS version 6.0 or 6.0 SP1 and the server is
DFS version 6.5.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 41

Migration Issues

DFS 6.0 and 6.0 SP1 clients package the UCF installer (ucf-installer.jar) in the DFS SDK. When this
packaged installer attempts to install UCF from the DFS server, it detects that the server UCF
component is newer, and the installation fails. There are two possible solutions:
• Upgrade the DFS clients to version 6.5.
• Apply the most recent DFS hotfix to the DFS 6 SP1 clients. The hotfix can be obtained from
ftp://ftp2.lss.emc.com/DFS/6.5.
DFS 6 clients may need to upgrade to DFS 6 SP1 before applying the hotfix.

DFS 6.5 client and DFS 6.0 server UCF

incompatibility
UCF content transfer will not succeed using the default client runtime settings if the client is DFS
version 6.5 or 6.5 SP1 and the server is DFS version 6.0 or 6.0 SP1.
The DFS 6.5 client dynamically downloads and installs UCF components from the DFS server
application. The client by default requires that the downloaded jars be signed. Because the jars on the
DFS 6.0 (or 6.0 SP1) server are not signed, the download will fail.
There are two possible solutions:
• Upgrade the DFS servers to version 6.5.
• Alter the client configuration on the clients so that they will accept unsigned jars.
To implement the second solution on Java clients, modify dfs-client.xml as follows:
<DfsClientConfig defaultModuleName="core"
registryProviderModuleName="core"
requireSignedUcfJars="false">

To implement the second solution on .NET clients, modify app.config as follows:

<ConfigObject type="Emc.Documentum.FS.Runtime.Impl.Configuration.ConfigObject,
Emc.Documentum.FS.Runtime"
defaultModuleName="core"
registryProviderModuleName="core"
requireSignedUcfJars="false">

Be aware that allowing unsigned jars may entail some security risk and implement this change only if
you are certain that the clients can trust downloaded jars

Structure of client configuration file has

changed
The structure of the Java and .NET configuration files used by productivity layer clients has changed.
The configuration files (e.g. dfs-client.xml, or app.config) will need to be updated when migrating
applications for DFS 6 or DFS 6 SP1 to DFS 6.5. For details, examine the configuration files provided
with the SDK samples, and refer to the Documentum Foundation Services 6.5 Development Guide.

42 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Migration Issues

Restructured jars and .NET assemblies

The packaging of jar files and .NET assemblies has changed, so Java classpaths and .NET assembly
references will need to be updated for client applications developed using DFS 6 or DFS 6 SP1.

Deprecation of DFS 6.0 exception model

DFS 6.5 introduces improved serialization of exceptions, while maintaining backward compatibility
with DFS 6.0 client applications. With services that were generated using DFS 6.0 (including
SP1), all exceptions specified in the original source are replaced in the generated WSDL with a
SerializableException. In DFS 6.5 the generated service WSDL will throw the original exceptions and
the more generic ServiceException. For example:
original service source method: throws MyServiceException
DFS 6.0 WSDL: throws SerializableException
DFS 6.5 WSDL: throws MyServiceException, ServiceException
For clients that use the productivity layer, this difference is handled transparently by the client
proxies. However, for clients that do not use the productivity layer, the DFS 6.0 WSDL will present a
different service operation interface than the source that was used to generate the service.
To maintain backward compatibility with applications developed for earlier versions of DFS, services
delivered with DFS 6.5 that were previously delivered with DFS 6.0 SP1 (for example, the Object
service and Query service) will use the deprecated exception model. Services that are new to DFS
6.5 will use the new exception model.
If you have developed a custom service that you wish to upgrade to DFS 6.5, but for which you wish
to continue to use the deprecated exception model, you can use the following annotation attribute to
specify that the deprecated model be used. This attribute can be used with either the DfsPojoService
or DfsBofService annotation:
useDeprecatedExceptionModel = true\false

For example, to specify usage of the deprecated model with a pojo service, you would use an
annotation like:
@DfsPojoService(targetNamespace = "http://core.services.fs.documentum.emc.com/",
useDeprecatedExceptionModel = true)

The default value of this attribute is “false”.

If you upgrade custom services to 6.5 without setting this attribute, DFS 6 clients will display a
SOAPFaultException with a message and no stacktrace, instead of the expected MyServiceException
with message and stacktrace.
Note: For guidelines on creating custom exceptions in DFS 6.5 services, refer to the Documentum
Foundation Services Development Guide.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 43

Migration Issues

RepackageServiceTask
The RepackageService ant task should not be used for updating services from DFS 6.0 SP1 to DFS
6.5. To update services, you must regenerate them from Java source using the service build tools
via Ant or Composer.

44 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 7
Technical Notes

This section provides supplemental technical information.

• Combining USER_TRANSACTION_HINT and PAYLOAD_PROCESSING_POLICY (DFS-301),
page 45
• Setting MaxReceivedMessageSize for .NET clients (DFS-439), page 46
• Avoid having dctm.jar on classpath when executing services (DFS-242), page 48
• Including a resources file in a service, page 48
• Avoid unintended updates to system properties, page 48
• Re-use cached ActivityInfo to avoid creating new UCF connections, page 48
• Avoiding out of memory errors when running Ant scripts, page 50

Combining USER_TRANSACTION_HINT and

PAYLOAD_PROCESSING_POLICY (DFS-301)
Note: Please note that there is a known problem with PAYLOAD_PROCESSING_POLICY, described
in PAYLOAD_CONTINUE_ON_EXCEPTION does not return successful operation details (DFS-226),
page 34 and that PAYLOAD_PROCESSING_POLICY may be deprecated in a future release.
Transactional behavior for a service operation is enabled by setting the USER_TRANSACTION_HINT
runtime property in the service context. The Documentum Foundation Services 6.5 Development Guide
does not document system behavior when transactional behavior is used in combination with
PAYLOAD_CONTINUE_ON_EXCEPTION, as shown here:
context.SetRuntimeProperty(IServiceContext.USER_TRANSACTION_HINT,
IServiceContext.TRANSACTION_REQUIRED);
context.SetRuntimeProperty(IServiceContext.PAYLOAD_PROCESSING_POLICY,
IServiceContext.PAYLOAD_CONTINUE_ON_EXCEPTION);

The expected behavior is that the payload policy should be honored first, then the transaction policy.
For example, suppose that we use the Object service to create objects based on a DataPackage that has
two DataObject trees. We use PAYLOAD_CONTINUE_ON_EXCEPTION with transaction support
to create the objects. At runtime, a leaf in the first DataObject tree fails and all others succeed. In
this case only the objects in the second DataObject tree would be created; the creation of the first
DataObject tree would be rolled back. If no transaction support were used, some leaves from the first
DataObject tree would be created, as well as the entire second DataObject tree.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 45

Technical Notes

Setting MaxReceivedMessageSize for .NET

clients (DFS-439)
DFS exceptions can sometimes result in SOAP messages that exceed size limits defined for the .NET
consumer. The DFS SDK provides an app.config in which the default values are increased across all
declared bindings as follows:
• maxBufferSize is increased to 1000000 instead of default 65536
• maxBufferPoolSize is increased to 1000000 instead of default 524288
• maxReceivedMessageSize is increased to 1000000 instead of default 65536
You may wish to use these or similar values in your .NET consumer.
Be aware that the app.config provided with the SDK is oriented toward productivity-layer consumers.
In productivity-layer-oriented app.config, the DfsDefaultService binding acts as the configuration for
all DFS services, except for DFS runtime services (the AgentService and ContextRegistryService),
which have separate, named bindings declared. The following sample shows the DfsDefaultService
binding as delivered with the SDK.
<binding name="DfsDefaultService"
closeTimeout="00:01:00"
openTimeout="00:01:00"
receiveTimeout="00:10:00"
sendTimeout="00:01:00"
allowCookies="false"
bypassProxyOnLocal="false"
hostNameComparisonMode="StrongWildcard"

maxBufferSize="1000000"
maxBufferPoolSize="10000000"
maxReceivedMessageSize="1000000"

messageEncoding="Text"
textEncoding="utf-8"
transferMode="Buffered"
useDefaultWebProxy="true">

<readerQuotas maxDepth="32"
maxStringContentLength="8192"
maxArrayLength="16384"
maxBytesPerRead="4096"
maxNameTableCharCount="16384" />
<security mode="None">
<transport clientCredentialType="None"
proxyCredentialType="None"
realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
</binding>

A WSDL-based consumer will by default introduce a per-service binding application configuration

file into the overall solution, so in this case you will need to configure the binding for every service.
The following example shows the declaration generated for the ObjectServicePortBinding with
default values:
<binding name="ObjectServicePortBinding"
closeTimeout="00:01:00"
openTimeout="00:01:00"

46 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Technical Notes

receiveTimeout="00:10:00"
sendTimeout="00:01:00"
allowCookies="false"
bypassProxyOnLocal="false"
hostNameComparisonMode="StrongWildcard"
maxBufferSize="65536"
maxBufferPoolSize="524288"
maxReceivedMessageSize="65536"
messageEncoding="Text"
textEncoding="utf-8"
transferMode="Buffered"
useDefaultWebProxy="true">
<readerQuotas maxDepth="32"
maxStringContentLength="8192"
maxArrayLength="16384"
maxBytesPerRead="4096"
maxNameTableCharCount="16384" />
<security mode="None">
<transport clientCredentialType="None"
proxyCredentialType="None"
realm="" />
<message clientCredentialType="UserName"
algorithmSuite="Default" />
</security>
</binding>

If you are concerned about preventing users from declaring too small a value for such attributes, you
can programmatically check and override the declared values, as shown here:
System.Reflection.FieldInfo appConfigInfo = typeof(ContextFactory)
.GetField("appConfig",
System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
System.Reflection.FieldInfo agentServiceBindingInfo = typeof(AppConfig)
.GetField("m_agentServiceBinding",
System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
System.Reflection.FieldInfo contextRegistryServiceBindingInfo = typeof(AppConfig)
.GetField("m_contextRegistryServiceBinding",
System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
System.Reflection.FieldInfo defaultServiceBindingInfo = typeof(AppConfig)
.GetField("m_defaultServiceBinding",
System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
BasicHttpBinding binding = new BasicHttpBinding();
binding.MaxReceivedMessageSize = 0x7fffffffL;
binding.MaxBufferSize = 0x7fffffffL;
agentServiceBindingInfo.SetValue(appConfigInfo.GetValue(contextFactory), binding);
contextRegistryServiceBindingInfo.SetValue(appConfigInfo.GetValue(contextFactory), binding);
defaultServiceBindingInfo.SetValue(appConfigInfo.GetValue(contextFactory), binding);

Avoid extending the DFS data model

We strongly recommend that custom data models do not extend the DFS data model classes. We
recommend using aggregation rather than inheritance to leverage the existing DFS data model in
custom classes. This maximizes interoperability and enables use of the pre-packaged JAXB bindings.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 47

Technical Notes

Avoid having dctm.jar on classpath when

executing services (DFS-242)
You should avoid having dctm.jar on the client classpath when executing services. This can cause the
DFS client runtime to use the wrong version of JAXB. Documentum installers that install DFC can
add dctm.jar to the classpath.

Including a resources file in a service

To include a resource in a service it is necessary to get the ClassLoader for the current thread, for
example:
Thread.currentThread().getContextClassLoader().getResource("some.properties");

Avoid unintended updates to system properties

Updates to system properties during an update or checkin can produce unexpected results and
should be avoided unless you explicitly intend to change a system property. The update and checkin
operations (and other operations as well) will attempt to update any properties that are populated in
a DataObject provided by the operation. These properties can only be modified by a superuser, so the
attempt will generally result in a permissions error. If the user making the update is a superuser,
unintended changes to system properties may cause side effects.
When you initially populate the properties of the DataObject (for example, using the result of an
Object service get or create operation), avoid setting the PropertyFilterMode to ALL, if you plan
to pass the result into a checkin or update operation. Instead, you can set the property filter to
ALL_NON_SYSTEM. (The default is operation-specific, but this is generally the default setting
for Object service get and similar operations.)
If you do need to modify a system property, you should strip other system properties from the
DataObject prior to the update.

Re-use cached ActivityInfo to avoid creating

new UCF connections
When using client-orchestrated UCF (in which you populate an ActivityInfo, which is passed to the
service or set in a registered service context), to avoid creating new UCF connections on the server,
you must cache the ActivityInfo on the client and pass the same instance in all service operation calls.
For example, suppose that you want to optimize a batch import by controlling the
AutoCloseConnection flag. In this case you will want to set AutoCloseConnection to false for
all transfers except the last, before which you must set AutoCloseConnection to true to close the
connection. The following Java sample caches an ActivityInfo and passes it to a private batchimport
method, which uses the ActivityInfo in its invocation of the Object service create method.

48 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Technical Notes

ContextFactory theContextFactory = ContextFactory.getInstance();

IServiceContext theContext = theContextFactory.newContext();
RepositoryIdentity theRepositoryIdent = new RepositoryIdentity();
theRepositoryIdent.setRepositoryName( theRepository );
theRepositoryIdent.setUserName( theUser );
theRepositoryIdent.setPassword(thePassword );
theContext.addIdentity( theRepositoryIdent );

theContext = theContextFactory.register(theContext, "core", theUrl );

theContext.setProfiles( new ArrayList<Profile>() );

ActivityInfo theInfo = new ActivityInfo(false);

for ( int i = 1; i < 3; i++ )
{
batchImport(theContext, theInfo);
}
theInfo.setAutoCloseConnection(true);
batchImport(theContext, theInfo);

The batchimport method does the work of setting up the context and DataObject and invoking
the create operation:
private static void batchImport(IServiceContext theContext, ActivityInfo theInfo)
{
try
{
OperationOptions theOptions = new OperationOptions();

ContentTransferProfile theTransferProfile = new ContentTransferProfile();

theTransferProfile.setTransferMode(ContentTransferMode.UCF);
theTransferProfile.setActivityInfo( theInfo );
theOptions.setContentTransferProfile( theTransferProfile );
ContentProfile theContentProfile = new ContentProfile();
theContentProfile.setFormatFilter( FormatFilter.NONE );
theOptions.setContentProfile( theContentProfile );

theOptions.setPropertyProfile( getPropertyProfile() );

ServiceFactory theServiceFactory = ServiceFactory.getInstance();

IObjectService theObjectService =
theServiceFactory.getRemoteService(IObjectService.class,
theContext,
"core",
theUrl );

DataPackage theDataPackage = new DataPackage();

for ( int i = 1; i < 2; i++ )
{
DataObject theDataObject = new DataObject(new ObjectIdentity(theRepository),
"dm_document");
PropertySet thePropertySet = new PropertySet();
thePropertySet.set("object_name", "test_" + i);
theDataObject.setProperties( thePropertySet );
FileContent theFileContent = new FileContent( "C:\\\\AIS_Test\\\\MyAttachment4.doc",
"msw8" );
theFileContent.setRenditionType( RenditionType.PRIMARY );
theDataObject.getContents().add( theFileContent );
theDataPackage.addDataObject( theDataObject );

}
theObjectService.create(theDataPackage, theOptions);
System.out.println("File imported");
}

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 49

Technical Notes

catch ( Exception e )
{
System.out.println( e.getMessage());
}
return;
}

If instead you create a new ActivityInfo for each operation, the server will start fresh UCF connections
and the optimization will not work.

Avoiding out of memory errors when running

Ant scripts
To avoid out of memory errors when running DFS build tools in Ant, you may need to set the
ANT_OPTS environment variable. For running in a UNIX shell, DOS, or Cygwin, set ANT_OPTS to
“-Xmx512m -XX:MaxPermSize=128m” to solve an OutOfMem and PermGen space error.
For running in Eclipse, set the Window -> Preferences -> Java -> Installed JREs -> Edit > Default VM
Parameter to “Xmx512m -XX:MaxPermSize=128m”

50 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 8
Documentation

This section describes the documentation related to this product.

Documentum Foundation Services

documentation set
These documents comprise the Documentum Foundation Services documentation set for this version
of the product:
• EMC Documentum Foundation Services Release Notes, version 6.5 SP2 (this document)
• EMC Documentum Foundation Services Deployment Guide, version 6.5 (P/N 300-007-213-A02)
• EMC Documentum Foundation Services Development Guide, version 6.5 (P/N 300-007-214-A02)
• EMC Enterprise Content Services Reference, version 6.5 SP2 (P/N 300-009-506-A01)
Note that the DFS 6.5 development and deployment guides have both been released as second
editions (version A02). If you have the first edition (A01), please update your copy.
Note that the EMC Enterprise Content Services Reference covers EMC content management and
archiving services that are not delivered as part of DFS.

Obtaining the correct documentation

The Powerlink website (http://powerlink.EMC.com) contains the downloadable packages for specific
product versions along with the release notes, installation guide, and other relevant documentation
associated with the product version. To locate product documentation, navigate to Support >
Technical Documentation and Advisories > Software ~ D ~ Documentation, then select the product
name and version number.
Note: The majority of Content Management products are listed under Software D > Documentum
?, where ? = a letter, or letters, in the alphabet.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 51

Documentation

Product documentation that is available online from the application (as online help) does not appear
as a separate item; it is automatically downloaded and installed with the software.

52 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 9
Software Media, Organization, and
Files

This section describes the media in which the software is available, the organization of the product
components in the available media, and the file names for all available product components which
can be downloaded.

Software media
This product is available as an FTP download from the Powerlink website (http://powerlink.EMC.com).
You should have received instructions through email regarding how to download products.

Organization
The Powerlink website (http://powerlink.EMC.com) provides access to https://EMC.subscribenet.
com/control/dctm/index, which provides a complete listing of the products available for download.

Files
The following modules/files comprise the contents of this release:
• Documentum Foundation Services for AIX, Version 6.5 SP2(tar)
• Documentum Foundation Services for HPUX IA64, Version 6.5 SP2 (tar)
• Documentum Foundation Services for HPUX, Version 6.5 SP2 (tar)
• Documentum Foundation Services for Linux, Version 6.5 SP2 (tar)
• Documentum Foundation Services for Solaris, Version 6.5 SP2 (tar)
• Documentum Foundation Services for Windows, Version 6.5 SP2 (zip)
• Documentum Foundation Services SDK for UNIX, Version 6.5 SP2 (tar.gz)
• Documentum Foundation Services Ear File for All Platform, Version 6.5 SP2 (ear)

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 53

Software Media, Organization, and Files

• Documentum Foundation Services War File for Tomcat, Version 6.5 SP2 (war)
• Documentum Foundation Services SDK for Windows, Version 6.5 SP2 (zip)
• Documentum Foundation Services Development Guide, Version 6.5 (pdf)
• Documentum Foundation Services Deployment Guide, Version 6.5 (pdf)
• Documentum Foundation Services Release Notes, Version 6.5 SP2 (pdf)
• Enterprise Content Services Reference Manual, Version 6.5 SP2 (pdf)

54 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 10
Installation

The instructions for installing the product are provided in the Documentum Foundation Services 6.5 SP1
Deployment Guide. This section describes any additional installation issues.
Ensure that your system meets the requirements listed in Chapter 4, Environment and System
Requirements before you install the software.

Documentum Foundation Services not

supported on Weblogic 10.3
The Documentum Foundation Services SP1 Release Notes incorrectly stated that deployment of DFS on
Weblogic 10.3 was supported. Weblogic 10.3 is not currently supported, but will be supported in
a future release.

Deployment on Websphere 7
Deployment on Websphere 7 differs from deployment on Websphere 6. Use the following
instructions:

1. Deploy the DFS EAR file using the Integrated Solutions Console.
2. Go to Application, Application Types, WebSphere enterprise applications.
3. From the list of applications, select emc-dfs.
4. From Detail Properties select Class loading and update detection.
5. Change Class loader order to Classes loaded with local class loader first (parent last).
6. Change WAR class loader policy to Single class loader for application.
7. Click OK and save changes.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 55

Installation

Deployment on application servers using JDK 6

If you are deploying on a supported application server that uses JDK 6, follow the instruction
documented under JAX-WS in JDK 6 conflicts with JAX-WS in DFS (DFS-691), page 34.

56 EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes

 Chapter 11
Troubleshooting and Getting Help

EMC Documentum technical support services are designed to make your deployment and
management of EMC Documentum products as effective as possible. The Customer Guide to
EMC Software Support Services provides a thorough explanation of the EMC Documentum
support services and policies. You can download this document from the Powerlink website
(http://powerlink.EMC.com) by navigating to Support > Request Support > Software Customer
Guide and Offerings.

EMC Documentum Foundation Services Version 6 .5 SP2 Release Notes 57