EMC ® Documentum ®

Documentum Foundation Services

Version 6.7 SP2

Release Notes

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
© Copyright © 1999–2013 EMC Corporation. All Rights Reserved.

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. Adobe and Adobe PDF
Library are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarks
used herein are the property of their respective owners.
Documentation Feedback
Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback about how we can
make our documentation better or easier to use, please send us your feedback directly at IIGDocumentationFeedback@emc.com
 Table of Contents

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

Chapter 1 Overview ..................................................................................................... 7

Resources ......................................................................................................... 8
Request for Input and Feedback ........................................................................ 8

Chapter 2 Feature and Updates ................................................................................... 9

Features and updates in Service Pack 2 .............................................................. 9
Multi-Domain Support for Kerberos .............................................................. 9
Security Fixes ............................................................................................... 9
Features and updates in Service Pack 1 .............................................................. 9
Features and updates in Base Release ................................................................. 10
WebSEAL integration ................................................................................... 10
Native .NET support for UCF ........................................................................ 10

Chapter 3 System Requirements ................................................................................. 11

Chapter 4 Installation and Upgrade ............................................................................. 13
Chapter 5 Fixed Issues ................................................................................................ 15
Fixed in Service Pack 2 ...................................................................................... 15
Fixed in Service Pack 1 ...................................................................................... 16
Fixed in the Base Release ................................................................................... 18

Chapter 6 Known Issues .............................................................................................. 19

Additional information about known issues ....................................................... 24
Limitation of the reference implementation WebSealIvUserHandler
(DFS-2810) ................................................................................................... 24
Hostname constraint pertaining to the .NET UCF client .................................. 24

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 3

Table of Contents

4 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Revision History

Revision Date Description

February 2013 Initial Revision

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 5

Preface

6 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Chapter 1
Overview

Documentum Foundation Services (DFS) provides a set of technologies that enables service-oriented
programmatic access to the EMC Documentum Content Server platform and related products.
Documentum Foundation Services is a service layer over a Documentum Foundation Classes client,
which connects to one or more repositories managed by Content Server.
The EMC Documentum Foundation Services 6.7 SP2 Release Notes contains customer-reported bug
fixes and platform compatibility updates. This document also includes a list of fixed problems,
known problems and limitations.
The following table lists some of the technologies that are included in Documentum Foundation
Services:

Documentum Foundation Services technology Description

Web services The Documentum Foundation Services web
services are Simple Object Access Protocol
(SOAP)/Web Service Definition Language
(WSDL)-based services deployed in a supported
Java servlet container.
Java services Documentum Foundation Services can also be
deployed as a local Java API using class libraries
provided in the Software Development Kit
(SDK). In a local application, the Documentum
Foundation Services Java services run in the
same Java Virtual Machine (JVM) as the service
consumer.
Data model The Documentum Foundation Services WSDL
interface and corresponding class libraries define
a service-oriented data model for representing
objects and properties, and for profiling service
operation options.
Java productivity layer Optional client-side libraries for Java consumers
of Documentum Foundation Services.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 7

Overview

Documentum Foundation Services technology Description

.NET productivity layer Optional client-side libraries for .NET consumers
of Documentum Foundation Services.
Tools for generating services Service-generation tools based on Java
application programming interface (API) for
XML based Web Services (JAX-WS), and Ant,
which generate deployable Documentum
Foundation Services services from annotated
source code, or from WSDL. These tools also
generate client-side runtime support for Java
clients. Client-side .NET classes are generated
using the Documentum Foundation Services
Proxy Generator utility.

Resources
For the latest product documentation and support materials, including White Papers and Technical
Advisories, refer to EMC Online Support (https://support.emc.com). Check regularly for new and
updated documentation to ensure that you have the latest system information.
Note: Documentation installed, or packaged with the product on the download center, is current at
the time of release. Documentation updates made after a release are available for download from
EMC Online Support (https://support.emc.com).

Request for Input and Feedback

Your opinion matters. We want to hear from you regarding our product documentation. If you have
feedback about how we can make our documentation better or easier to use, please send us your
feedback directly at IIGDocumentationFeedback@emc.com.

8 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Chapter 2
Feature and Updates

This section highlights the major functionality changes included in this release. Refer to the product
documentation for complete information about these features.

Features and updates in Service Pack 2

This section describes the following new features for Documentum Foundation Services 6.7 SP2:

Multi-Domain Support for Kerberos

Documentum supports Kerberos in two-way trusts between multiple domains in the same forest only.
Note: Multiple-domain Kerberos is supported only on JDK 1.6 or later.

Security Fixes
The following security fixes are included in Documentum Foundation Services 6.7 SP2:
DFS-3858

Features and updates in Service Pack 1

This release of Documentum Foundation Services consists only of bug fixes; there are no changes.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 9

Feature and Updates

Features and updates in Base Release

This section describes the following new features and changes for Documentum Foundation Services
6.7:
• WebSEAL integration, page 10
• Native .NET support for UCF, page 10

WebSEAL integration
Documentum Foundation Services 6.7 provides support for integrating applications with IBM Tivoli
Access Manager for e-business WebSEAL.
IBM Tivoli Access Manager for e-business WebSEAL is a high-performance, multi-threaded web
server that applies fine-grained security policy to a protected network. WebSEAL incorporates
back-end web application server resources into its security policy, and can provide single sign-on
(SSO) solutions. WebSEAL acts as a reverse web proxy by receiving HTTP or HTTPS requests from
a web browser and delivering content from its own web server or from back-end web application
servers. Requests passing through WebSEAL are evaluated by its own authorization service to
determine whether the user is authorized to access the requested resource.
EMC Documentum can integrate with WebSEAL, its SSO solution, or any other SSO solution
supported by WebSEAL. The related IBM documentation provides more information about installing
and configuring the WebSEAL server. Obtain this documentation from the IBM website.
For information regarding integration of DFS applications with WebSEAL, refer to the Documentum
Foundation Services Development Guide and the Documentum Foundation Services Deployment Guide.

Native .NET support for UCF

Unified Client Facilities (UCF) is an EMC technology that orchestrates direct transfer of content
between a client computer and a Documentum repository. UCF is fully integrated with DFS, and
can be employed as the content transfer mechanism in many types of DFS consumer application.
The DFS 6.7 SDK provides client libraries to support UCF content transfer using .NET components.
The .NET libraries are integrated into the DFS productivity layer runtime to simplify usage by
productivity layer applications. Applications that do not use the productivity layer can use the .NET
UCF client libraries directly in their applications outside of the DFS productivity layer runtime.
Web applications can package the UCF client libraries into an ActiveX object to enable UCF content
transfer between a browser and a Content Server. Clients that use the .NET libraries do not need to
have a Java Runtime Engine installed on their system.

10 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Chapter 3
System Requirements

EMC Documentum 6.7 SP2 Environment and System Requirements Guide contains the system
requirements information for your product. This documentation is available from EMC Online
Support(https://support.emc.com).

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 11

System Requirements

12 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Chapter 4
Installation and Upgrade

Before beginning installation, ensure that your system meets the requirements listed in Chapter 3,
System Requirements.
EMC Documentum Content Server Installation Guide and the EMC Documentum Foundation Services
Deployment Guide contains installation and deployment information for your product. This
documentation is available from EMC Online Support (https://support.emc.com).
When deploying the Documentum Foundation Services Productivity layer, the following steps are
required and differ depending on the version of Weblogic being used:
• For Weblogic 10.3, comment out the <prefer-applicationis i-resources> elements from
weblogic-application.xml.
• For Weblogic 10.3.5, comment out the <prefer-application-packages> elements from the
weblogic-application.xml.
For more information on deployment, refer to the Documentum Foundation Services Deployment Guide.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 13

Installation and Upgrade

14 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Chapter 5
Fixed Issues

This section identifies issues that have been resolved in this release.
Service Packs are cumulative. The current release contains fixes from all previous Service Packs
and Patches.

Fixed in Service Pack 2

Issue Number Description
DFS-3858 In previous releases, trusted login was enabled by default. Now trusted
login is disabled by default.

The Documentum Foundation Services (DFS) client can access DFS

services with a wrong password. This is because of the trusted login
being enabled by default and has been fixed by introducing an option
"dfc.session.allow_trusted_login" in DFS configuration.
DFS-4042 UCF. NET client cannot be launched due to permission issue if DFS .NET
client is running as Microsoft Office add-in.
DFS-4508 The customer receives the following DFS error when using the DFS .NET
Productivity Layer: "System.InvalidOperationException: Instance validation
error: ’STOPPED’ is not a valid value for Status."
DFS-4396 Using DFS Object Service to create document under folder A fails if there
is a document B having the same "object_name" as folder A, and A and
B are under a same parent folder.
DFS-4333 If a double value is set for an attribute of type integer, an exception is thrown
and the server hangs unless it is restarted.
DFS-4299 "Unexpected CryptoAPI failure generating seed" occurs intermittently when
generating seed.
DFS-4211 Some of the data was not parsed in TaskManagementService Complete
operation at DFS .NET productivity layer. The fix refactored
TCompleteTaskData class and makes the data serialization succeed.
DFS-4075 Customer hit intermittent java.lang.IllegalStateException when deploying
DFS in Tomcat.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 15

Fixed Issues

Issue Number Description

DFS-4042 UCF. NET client cannot be launched due to permission issue if DFS .NET
client is running as Microsoft Office add-in.
DFS-4009 Certain PDF files cannot be imported by .Net UCF native client.
DFS-3949 The DFS .NET client productivity layer checks the session consistency, which
should be done by DFS/UCF Server.
DFS-3932 Even if proper post transfer action is specified, local application fails to
launch for document whose name includes Japanese characters. This is a
UCF bug and the fix has been included in Documentum Foundation Services.
DFS-3839 When using search services , there is no way to know if the indexer supports
wildcard characters to map to the conditions such as BEGINS_WITH,
ENDS_WITH etc., (for e.g., xPlore supports wild cards)
DFS-3801 Documentum Foundation Services cannot update attribute "i_partition"
since 6.6 P12. This is a regression caused by underlying DFC change. DFC
has fixed the regression.
DFS-3693 When the disk has no available space, the UCF export operation fails and
logs an error at the client level. However, no errors are reported to the
server. Due to this, the DFS client does not fail until it times out.
DFS-3691 When you perform a DFS operation through a DFS Web Services consumer
developed using Java and

a similar DFS operation is performed through a Web Services consumer

developed using .NET, the Web Service consumer using DFS.NET takes
time to respond.

The DFS.NET Web Service consumer takes more time to respond even when
the Web Service instance is reused.
DFS-1380 ObjectService.get() throws an exception E_OPERATION_CHAIN_GET_
FAILED_WITH_TREE_DUMP with cause E_CANT_LOAD_RELATIONS in
a specific use case. This is root caused by underlying DFC.

Fixed in Service Pack 1

Issue Number Description
DFS-3771 We fixed the problem where DFS users cannot enable trusted login using
the dfc.session.allow_trusted_login option in dfc.properties. This is because
DFS disables trusted login at the code level.
DFS-3753 We fixed the problem where the DFS .NET productivity layer does not
have the required methods (related to Facets) for calling the SearchServices
functionality.

16 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Fixed Issues

Issue Number Description

DFS-3693 We fixed the problem that occurred when the disk has no available space,
the UCF export operation fails and logs an error at the client level. However,
no errors are reported to the server. Due to this, the DFS client does not
fail until it times out.
DFS-3691 We fixed the problem where the DFS operation takes more time to respond
while using the .NET productivity layer client.
DFS-3648 We fixed the problem where if you use QueryStoreService.listSavedQueries
service in the Documentum Foundation Classes diagnostic mode, session
and collection leak occurs.
DFS-3565 We fixed the problem where the DFS 6.6 .NET Productivity Layer
fails to retrieve a new UCF ID if the UCF content transfer is parallel
(multi-threaded).
DFS-3475 An error (java.lang.NullPointerException) occurs during UCF content
transfer on Java Runtime Environment 1.6 update 22 and later versions.
DFS-3448 We fixed the problem where an error occurs when you import a Microsoft
Word 2007 file that contains an Object Linking and Embedding (OLE) link
to a Microsoft Excel 2007 file. Documentum Foundation Services fails to
import Microsoft Office 2007 files that contain OLE links.
DFS-3298 Previously, DFS retrieved UCF content with EXPORT and VIEW modes,
respectively, depending on the rendition type. Now, the DFS client can use
any content retrieval related API to get UCF content. Enables users to specify
the content retrieval mode for UCF content using the ContentRegistryOption
DFS-3143 We fixed the problem where Documentum Foundation Services.NET client
cannot transfer content using Documentum Foundation Services 6.6 and
earlier servers.

If content transfer operations are performed between Documentum

Foundation Services 6.7 .NET Productivity Layer client and a Documentum
Foundation Services 6.6 (or earlier) server, set the use.native.ucf property in
the App.Config file to false:
<appSettings> <add key="use.native.ucf" value="false"/>
</appSettings>
DFS-2977 We fixed the problem that occurs when Documentum Foundation Services
6.7 with Content Server 6.5 SP3 repository, the yacc stack overflows and a
parser error occurs.
DFS-2975 We fixed the problem in the Documentum Foundation Services orchestrated
UCF consumption mode, where if you use Documentum Foundation
Services client 6.7 to access Documentum Foundation Services 6.6 and
earlier servers and set an uninitialized ActivityInfo class in the UcfContent
instance, the content transfer operation fails.

//Setting an uninitialized ActivityInfo class

in the UcfContent instance UcfContent content = new
UcfContent(filepath, format); content.setActivityInfo(new
ActivityInfo(autoCloseConnection));

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 17

Fixed Issues

Issue Number Description

To resolve the problem, initialize the ActivityInfo class in the

ContentTransferProfile profile of OperationOptions or ServiceContext object
as follows:
//ContentTransferProfile must be used by ServiceContext
or OperationOptions ContentTransferProfile ctp = new
ContentTransferProfile(); ctp.setActivityInfo(new
ActivityInfo(autoCloseConnection));

Fixed in the Base Release

Issue Number Description
DFS-1223 We fixed the issue in which an exception occurred when the ObjectService
get operation retrieved all folder objects in a repository in a single call.
DFS-721 We fixed the issue in which the Query service returned incorrect data for
some queries under the following conditions:
• The query contained an r_object_id attribute and a repeating attribute
in its SELECT clause.

• The query result contained multiple objects with the same r_object_id.

18 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Chapter 6
Known Issues

This section identifies known product issues and limitations that may affect your use of the product.

Issue Number Description

DFS-3854 An out of memory error may occur when uploading a large file in MTOM
transfer mode to JBoss 5.1 CE, embedded in the Content Server.

Workaround — Use another supported application serve, such as Jbos 4.3

EAP, or transfer the file using UCF instead of MTOM.
DFS-4471 If you want to reuse a UCF connection, it is highly recommended that
you reuse the connection between continuous operations. Otherwise, the
connection may expire.
DFS-3807 The current Java Productivity Layer for the Documentum Foundation
Services (DFS) is not directly compatible with WebSphere Application
Server (WAS) 7. Custom Axis2 proxies must be used to allow WAS 7 to
consume the Java Productivity Layer. Please refer to the section Consuming
DFS with Axis2 in the Documentum Foundation Services Development Guide
for detailed information. Note that the Java Productivity Layer is directly
compatible with WAS 6.1.

The Java Productivity Layer was designed to accelerate the development of

JAVA client applications that consume the services from a DFS Server. The
Java Productivity Layer is a separate technology component with different
support considerations from the DFS Server itself.

Certified application servers for the Java Productivity Layer are documented
in the Documentum 6.7 SP1 Environment and System Requirements Guide
delivered with this release.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 19

Known Issues

Issue Number Description

DFS-3431 When a service is generated using the Documentum Foundation Services
service-generation tools, artifacts generated by JAX-WS are archived in JAR
files if the data class resides in the same package as the service endpoint.

For example, if a service uses the com.service.SomeService,

com.service.DataClassA, and com.service.DataClassB data objects, the
following results occur:
• DataClassB will extend DataClassA

• The service will have the SomeService.theOnlyMethod(DataClassB)

method

• While generating JAX-WS artifacts, the generated DataClassA is not

deleted. This generated class is archived in the resulting JAR file, and not
in the client defined class.

In this case, when generating JAX-WS artifacts, the generated DataClassA

is not deleted. This generated class is archived in the resulting JAR file,
rather than the client defined class.

To repair the JAR file, remove the class generated by JAX-WS and replace
it with the client-defined class file.
DFS-3429 The Java Development Kit (JDK) does not compensate for Daylight Savings
Time for dates before 1981, and it compensates incorrectly for dates from
1981 through 1990. This Documentum Foundation Services limitation only
impacts data with dates prior to 1990.
DFS-3427 When creating custom services, a conflict occurs when you have two services
containing the following namespaces: http://a.b.c.d and http://b.c.d.a. When
JAX-WS tries to generate the client proxies for these two services, they are
generated in the same package (d.c.b.a) and you can call the first service in
the classpath. Avoid assigning namespaces in a format that is specified in
the description of this issue.
DFS-3425 In clustered environments, failover is not supported for registered service
contexts and cached queries. If you need failover support, do not register
service contexts or use cached queries.
DFS-3423 Only services that are executed in the same server-side process can share a
registered service context. Services are deployed in the same EAR file on the
application server. This limitation implies that the client must be aware of
the physical location of the services which it invokes. In addition, the client
must manage service context sharing based on shared physical locations.

Registration of service context is not required. To avoid this problem, do not

register the service context.
DFS-3421 The JAX-WS implementation uses the thread context class loader, rather
than the class loader of the executing class. Therefore, when calling
a Documentum Foundation Services service from a Business Object

20 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Known Issues

Framework (BOF) module or Java server method, set the current class loader
to the class loader of the module. It is described in the following procedure:
1. Save the ContextClassLoader of the current thread.

ClassLoader oldContextClassLoader = Thread.

currentThread().getContextClassLoader();

2. In a try block, set the current class loader to the class loader in the class
of the calling object before calling the Documentum Foundation Services
service.

try { ClassLoader classClassLoader =

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

3.
In a finally block, reset the class loader to the previously saved thread
class loader.

finally { Thread.currentThread().setContextClassLoader
(oldContextClassLoader); }
DFS-3419 The following limitations apply to Kerberos support in this release:

• Due to the multi-tiered nature of Documentum Foundation Services

applications, Kerberos integration is based on delegated authentication.
All Kerberos tokens provided to Documentum Foundation Services
through the web services API must be “forwardable”. The local Java API
accepts only Kerberos Ticket Granting Tickets (TGTs).

• Documentum Foundation Services services do not accept Simple and

Protected GSSAPI Negotiation Mechanism (SPNEGO) tokens. However,
the Kerberos utility provided with the DFS Software Development Kit
(SDK) includes a method for unwrapping SPNEGO tokens.

• Registering a ServiceContext with Kerberos credentials is not supported.

• Kerberos-based message level security is not supported.

• Support for .NET integration is limited to remote web services API (in the
client productivity layer). There is no Kerberos Utility for .NET.

• Wrapped GSSAPI Kerberos tokens are not supported.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 21

Known Issues

DFS-3393 When applications that use different versions of SOAP with Attachments
API for Java (SAAJ) are deployed on the same Java Virtual Machine (JVM),
the deployment fails and an exception occurs.

The resolution is as follows:

• Ensure all applications that use SAAJ have the same version of SAAJ,
when they are deployed on the same JVM.

• When you have to deploy a third party application that does not
contain SAAJ and Documentum Foundation Services or Documentum
Foundation Services based applications on the same JVM, remove SAAJ
related JAR files from Documentum Foundation Services or Documentum
Foundation Services based applications for a successful deployment.
DFS-2809 The Documentum Foundation Classes client causes a performance
degradation when using the WebSealIvUserHandler JaxWS handler
included in the Documentum Foundation Services SDK. It is recommended
that you do not use this handler in production systems until this limitation
is addressed. For details, see Limitation of the reference implementation
WebSealIvUserHandler (DFS-2810), page 24.
DFS-1383 The DFS .NET client is based on WCF (Windows Communication
Framework), which provides three modes for MTOM content transfer:
buffer, streaming, and chunk. For streaming and chunk modes, WCF
requires that the corresponding service operation (such as get or create) take
only one argument (the input stream). This conflicts with the design of DFS,
such that DFS can only use the MTOM buffer mode with a .NET client. This
results in unusually high memory requirements,

Workaround — There are several options for working around this

limitation:
• First, for content download operations, enable ACS/BOCS and make use
of it. To ensure that the urlContent type is returned by DFS, use the
urlReturnPolicy setting. The client can use the urlContent returned by
DFS to request content transfer from the ACS server.

• For content upload operations, use UCF as the content transfer mode.
UCF will orchestrate content transfer in both directions between the client
and the ACS server.

• Ensure that both the DFS .NET client and JVM that runs the DFS server
have enough memory to buffer the content.

For additional detail on this limitation, refer to the EMC Documentum

Foundation Services Deployment Guide.

22 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes

 Known Issues

DFS-1167 Unified Client Facilities (UCF) requires a 32-bit JVM and is incompatible
with a 64-bit JVM. This has implications for Documentum Foundation
Services Java and .NET clients.

A Java client that uses UCF content transfer mode must run in a 32-bit JVM.

.NET clients that use UCF content transfer mode launch UCF as a separate
Java process. This process must run in a 32-bit JVM. .NET clients can ensure
that UCF runs in a 32-bit JVM by setting the JAVA_HOME or JRE_HOME
environment variable to point to a 32-bit JVM.
DFS-687 JBoss log generates error messages although Documentum Foundation
Services services are available. This is an issue in JBoss and not a
Documentum Foundation Services issue.

The resolution is to change the log level of java.util.logging to WARNING:

edit $JAVA_HOME/jre/lib/logging.properties,
change ".level= INFO" to ".level= WARNING"
DFS-684 The current process of defining a new resource bundle consists of defining
a new property in dfs-runtime.properties, incrementing the index of the
property.

In dfs-runtime.properties:

resource.bundle = dfs-messages resource.bundle.1 =

dfs-services-messages resource.bundle.2 = dfs-bpm-services-
messages
In local-dfs-runtime.properties:
resource.bundle.3 = my-custom-services-messages

The limitation of this approach is that if a new resource bundle is required

for core services in a future release, it can be defined as "resource.bundle.3"
and the one defined in local-dfs-runtime.properties will override it. This
approach can cause a future migration issue.
DFS-65 When generating multiple services in the same package that have the same
method names, the generation on the client side overwrites the generated
classes where there are name conflicts. The services must be in separate
packages or have different method names.
DFS-30 When you create custom services, extending the Profile class or subclasses
is not permitted. For new services, you can use properties (passed to the
service in OperationOptions or in the service context) as an alternative to
creating new profiles.
N/A UCF client is intended for a single user, either using a browser in a web
application, or a using a thick client. Using UCF is not supported on the
middle tier of a distributed application. Typically the middle tier would be a
web application functioning as a DFS consumer.

EMC Documentum Foundation Services Version 6.7 SP2 Release Notes 23

Known Issues

Additional information about known issues

This section includes supplemental information about known issues.

Limitation of the reference implementation

WebSealIvUserHandler (DFS-2810)
The Documentum Foundation Classes client causes a performance degradation when using the
WebSealIvUserHandler JaxWS handler included in the Documentum Foundation Services SDK. It
is recommended that you do not use this handler in production systems until this limitation is
addressed. The reference implementation of the IBM Tivoli Access Manager WebSEAL server-side
handler, WebSealIvUserHandler, included in the SDK, extracts the IBM Tivoli Access Manager
WebSEAL IV-USER header from the request message, and saves it into a Documentum Foundation
Services PrincipalIdentity. This identity is then added to the local service context to act as a trust login.
This simple handler works in most of scenarios but has a performance limitation caused by session
consumption in the underlying Documentum Foundation Classes layer. It is easy to reach the
maximum session count in a heavily trafficked or concurrent environment. You can rectify the
performance degradation using the following dfc.properties settings:
• Increase dfc.session.max_count (the default is 1000)
• Decrease dfc.session.pool.expiration_interval (the default is 5)

Hostname constraint pertaining to the .NET UCF client

The hostname of the machine on which you deploy the DFS server must comply with the following
constraint:
The hostname must be a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9),
minus sign (-), and period (.).
Otherwise, the .NET UCF client installation fails. For example, the hostname cannot contain the
underscore sign (_).
For more information about the hostname constraint, see RFC-952.

24 EMC Documentum Foundation Services Version 6.7 SP2 Release Notes