What's New in Document Um 6.5 SP2
What's New in Document Um 6.5 SP2
What's New in Document Um 6.5 SP2
System
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748‑9103
1‑508‑435‑1000
www.EMC.com
Copyright © 2009 EMC Corporation. All rights reserved.
Published June 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.
EMC Documentum Technical Document
Table of Contents
Preface .............................................................................................................. 6
Intended Audience ..................................................................................... 6
Revision History ......................................................................................... 6
Preface
This document provides an overview of new features of the EMC Documentum ECM 6.5 SP2
release. The intent is to provide high‑level guidance for deployment planning purposes and not to
provide information about future product releases.
Note: All products listed in this document are not released at the same time, refer to respective
product Release Announcement.
The information contained in this document reflects the plan at the time of publishing. As
with any forward looking statements, this information is subject to change. Once the release
is available, greater detail for specific products can be found in the product release notes and
installation guides.
Intended Audience
The audience for this document consists of the internal EMC Documentum sales organization,
technical support, consulting deployment programs, partner programs, professional services,
developer programs, EMC partners, and EMC customers.
Revision History
The following changes have been made to this document.
Release Highlights
BOF1
BOF 1 is deprecated with target end of support in D7, and customers are strongly encouraged to
use BOF 2.
Product Highlights
This section provides a general overview of new Documentum 6.5 SP2 product features planned
for release with the stack. New features for Documentum 6.5 SP1 products released after the stack
are not addressed. Please note that all information is current at the time of writing and is subject
to change without notice.
Knowledge Worker
The Documentum Desktop client has been phased out. As a result, Desktop users can no longer
access DRLs (links to repository documents) embedded in e‑mail messages. Documentum
Webtop 6.5 SP2 provides existing Documentum Desktop client users with the DRLinvoker
application (DRLinvoker.exe.config) that enables them to access DRLs and open the relevant
linked documents. This tool converts the DRL into a Documentum Webtop Universal Resource
Locator (URL), and opens the linked document in a browser window.
Prior to Documentum 6.5 SP2, when a folder was deep exported to a location where a folder by the
same name already exists with all or some of the same files as those being exported, users were
prompted to overwrite each duplicate folder and file. The prompt for overwriting each folder and
file appeared with the Yes and No buttons.
With release 6.5 SP2 release, the following additional buttons are displayed while prompting users
to overwrite folders and files: Yes to all and No to all buttons. If the user clicks the Yes or No
button, the overwrite setting is applied to the current file. However, if the user clicks the Yes to all
or No to all button, the overwrite setting is applied to all files on which the deep export operation
is performed. In the context of UCF, the overwrite setting is applied to all files for that UCF client
session. Therefore, users are not prompted every time a duplicate folder or file is overwritten.
The most significant new feature in Version 6.5 SP2 of IRM Services for Documentum is the
ability to protect a PDF document at the document level. Prior to this release, only page‑level
protection was available, thereby requiring a separate key for each page that the user wished to
protect. In version 6.5 SP2, with document‑level protection, one key is required to protect the
entire document. Entire document protection processing time is significantly reduced, thereby
improving the end‑user experience and overall client‑side performance.
IRM Services for Documentum 6.5 SP2 enables developers to expose native IRM functionality in
WDK‑based client applications. Starting with version 6.5 SP1, IRM Services for Documentum has
provided native support for Documentum WDK‑based applications, thereby eliminating the need
to customize Webtop, Documentum Administrator, or TaskSpace.
Documents that have not been processed or that have been excluded for subsequent processings
are listed in status files. The files provide information to identify the documents and the cause of
the errors.
There are various problems that could cause unprocessed documents, for example, when the
file format is not supported or when the maximum file size is exceeded. The result is that no
classification has been done; however, it does not mean that the documents would not match any
category.
This feature is particularly interesting when documents must be classified in either of the
categories (as in e‑discovery use case). Documents listed in the unprocessed file will have to be
handled separately from CIS.
Several changes have improved CIS server’s error recovery. The main changes are the following:
• When CIS server starts, it checks that the memory allocated to CIS processing is sufficient. If
one increases the size limits or the number of threads in cis.properties, the size of the memory
of the JVM also need to be increased in startCIS.cmd. If the allocated memory is not sufficient,
CIS server does not start and logs an error.
• In prior versions, when the processing of a document set generated some errors, the
scheduling was cancelled in order for CIS administrator to fix the issues. From now on, the
scheduling is no longer cancelled and the document set will be processed again, even if there
are many errors.
• Documents that CIS server could not process are skipped during subsequent processings. The
list of unprocessed document is available as a log file.
Note that, as in previous versions, when CIS server hangs or stops because of an error, it does not
restart automatically. To do so, it is necessary to configure CIS Windows service.
JMX support
It is possible to administer CIS server using a JMX agent. The JMX Agent for CIS is accessible from
Documentum Administrator but also using Jconsole. For now, features implemented in current
release are: get server status and stop server.
The Vantage linguistic engine used by CIS has been replaced with Snowball stemmer. Snowball
stemmer extends Porter algorithms, which is widely used and a standard algorithm. This new
stemmer allows you to use the stemming for documents in English, French, German, Spanish,
Italian, Portuguese, Danish, Dutch, Norwegian, and Swedish, as before, but also in Romanian,
Russian, Finnish, Hungarian, or Turkish
While it does not change the way CIS processes documents and document sets —for example, the
language specified for a document set prevails over the language specified for a document—, it
may slightly modify the classification results if your category definitions are based on stemmed
keywords.
The same languages are supported for classification but you no longer need to install dictionaries.
Enhanced installer
CIS installer has been enhanced to automate some configuration tasks. When installing CIS,
you can now enable the repository for CIS use. This task had to be performed manually in
Documentum Administrator. It is now done automatically during the installation if the repository
is running and can be accessed at this time. You can still enable the repository manually in
Documentum Administrator, for instance if the repository cannot be accessed during CIS
installation. If the repository has already been enabled for another CIS instance, the configuration
is not modified by the CIS installer, but it may need to be modified in Documentum Administrator
for your new CIS to be effective on the repository.
The installer includes as well the change of the default port number used by CIS. The port
number is now based on the application server port number +19; hence, the default value is
8079 (it was 18460).
The installer also offers a new option reserved to EMC Documentum CenterStage Pro clients: the
entity extraction. Selecting this option installs additional components for the extraction of entities.
The entities are used to filter documents in CenterStage Pro clients.
After the installation, if CIS server cannot connect to the repository, it periodically tries to reconnect
to the repository. Attempts are made every minute for five minutes, then increasing the delay and
eventually trying every hour until successful or shut down. Therefore, CIS administrator no longer
needs to manually restart CIS server or enable the repository in Documentum Administrator.
Federated Search Services (FS2) 6.5 SP2 offers a new adapter available out‑of‑the‑box with FS2
server. This adapter allows you to search Windows desktops using Windows Search. It is possible
to search all types of contents or to limit the search scope. For example, you can search emails only
or documents only.
With Process Builder 6.5 SP2, the process debugger has the enhanced ability to load custom
Java methods from various locations.
If you use custom methods, the debugger now looks for the JAR file and load the methods from
the following locations:
• <Process Builder install location>/classes/custom directory
• <Documentum install location>/dba/java_methods directory when Content Server and Process
Builder are installed on the same machine
• Documentum repository if the methods are deployed as a BOF module
Process Builder logs messages using log4j. Standard console output is also diverted to the log file
(System.out and System.err).
When specifying a performer based on process data, you can select ALL attributes of a repeating
value for the following performer types:
• Some users from a group
• All users in group
During runtime, Process Engine creates workitems for all performers specified in the repeating
value attribute of the process data. This can be a mixture of individual user names as well
as group names.
The data mapper in many of the activity templates now includes several new enhancements:
The Note attribute of the package data for Source attributes is now a repeating attribute. This
enables process developers to map the task comments provided by the workflow supervisor and
task performers to the package where they are consolidated and preserved.
Mapping comments from the package to a structured data type enables you to capture multiple
performer comments along with the creation date, writer name, and note ID. The consolidated
comments can then be viewed in subsequent activities or mapped to the body of an email message
in a subsequent activity.
Process Data Mapping activities and Inbound initiate and step activities now preserve any
customizations when data is set on a package or attachment.
The Get Ticket function enables the system to generate a secure login for a specific user. The ticket
can be configured for one or more repositories, can be used more than one time, and can expire
after a designated amount of time has passed.
The BOF Module activity template now supports simple and complex repeating attributes in both
input and output message mapping of the data mapper.
FTP Read, FTP Outbound, and FTP Inbound activity templates now provide support for Public
Key Authentication for SFTP protocols. This improves security by providing a safe means of
authentication.
The Email Inbound and the SMTP activity templates have been enhanced to include:
• Select a preferred MIME type for Email Inbound activities
Select or type in the Preferred MIME Type for the message.
Select or type in the MIME type for the part of the email body for multipart/alternative
messages.
• Retrieve or set values of email headers
The Email Inbound activity templates have additional attributes that are specific to email
headers that enable you to create mappings that retrieve these values in the email headers
The SMTP activity template enables you to set values in the email headers for several key
attributes.
For increased security, both the Web Service Inbound and HTTP Inbound activity templates use
hashing instead of encryption to store passwords in the service definition.
The data mapper in many of the activity templates now includes several new enhancements:
The Note attribute of the package data for Source attributes is now a repeating attribute. This
enables process developers to map the task comments provided by the workflow supervisor and
task performers to the package where they are consolidated and preserved.
Mapping comments from the package to a structured data type enables you to capture multiple
performer comments along with the creation date, writer name, and note ID. The consolidated
comments can then be viewed in subsequent activities or mapped to the body of an email message
in a subsequent activity.
Process Data Mapping activities and Inbound initiate and step activities now preserve any
customizations when data is set on a package or attachment.
The Get Ticket function enables the system to generate a secure login for a specific user. The ticket
can be configured for one or more repositories, can be used more than one time, and can expire
after a designated amount of time has passed.
The BOF Module activity template now supports simple and complex repeating attributes in both
input and output message mapping of the data mapper.
FTP Read, FTP Outbound, and FTP Inbound activity templates now provide support for Public
Key Authentication for SFTP protocols. This improves security by providing a safe means of
authentication.
The Email Inbound and the SMTP activity templates have been enhanced to include:
Filter variables
Filter variables can now be used to limit the data displayed in dashboard reports to that ’owned’
by a specific dashboard user. Filter variables provide dashboard users with report data that only
they are permitted to see, while preventing them from seeing data that is not intended for them.
Filter variables are not the hard coded values typical of most filter expressions. Rather, they are
resolved during the execution of the report when the value for the variable is replaced with the
actual value of the user and his or her group. Filter variables work with any report where the
username and/or default group is captured.
The Crystal Reports servlet (crRepgen) has a new parameter in its URL that allows reports to be
exported to either CSV or PDF format. The parameter is export= and can be set to one of two
values: CSV or PDF. Instead of the Crystal Report viewer appearing, the browser prompts the user
to save the report as either a CSV or PDF file.
The Flex servlet (repgen), which services Simple Reports, can also be exported to CSV by way of
the export parameter. Simple Reports cannot be exported to PDF.
• Labels on a check box group or radio button group can have custom widths, page 19
Forms Builder now supports using a locale that is not country‑specific. For example, instead
of using ar_EG to specify Egyptian Arabic, you can just use ar to specify Arabic that is not
country‑specific. In Forms Builder, the form designer can add country‑less locales to the locale
configuration. Forms Builder will import and export a locale that is not country‑specific and the
Forms Builder menu will display locales that are not country‑specific. TaskSpace and Webtop are
able to load the correct form template locale. For the load order, if there is a form locale that exactly
matches the TaskSpace/Webtop locale, that locale is loaded (for example, ar_EG). If the exact locale
is not available in the form, the country‑less locale is loaded (e.g., ar). Otherwise English is loaded.
When creating a check box group or a radio button group, a custom width setting is possible for
labels. The custom width is set by selecting a row in the Column table in the Special tab for a check
box group or radio button group, clicking Modify, then selecting the Fixed Width option and
entering the desired width in number of pixels.
Accessibility issues have been addressed so that partial Section 508 compliance can be claimed.
The following Web Publisher components are not Section 508 compliant:
• Web Publisher Editor
• Web Contributor
• Page Builder
Web Publisher Contributor is a simplified Web Publisher user interface that has been redesigned
with Adobe Flex for this release. Web Publisher Contributor reflects the following features:
• Users can log in to Web Publisher Contributor directly from the Web Publisher login screen, or
they can switch to this interface during a Web Publisher session.
• Web Publisher Contributor reflects a dashboard paradigm; it consists of a navigation tree for
web cabinets, a search function, and a listing of the user’s content.
• Web Publisher Contributor can be configured to display the thumbnail and properties of
a file when the user hovers over the item.
Page Builder has the following new features for 6.5 SP2:
• Usability enhancements , page 21
• Sample components for ratings and feedback , page 21
• XDQL support in XML component, page 21
Usability enhancements
Sample components for gathering end‑user comments and ratings are provided with pre‑coded
forms files (XML) and handler files (JSP) so that developers can easily add these complex
components to Page Builder templates. The ratings component includes the ability to display the
average rating and the total number of ratings received. These components can be used together
so that end‑users can elaborate on their ratings by providing feedback and comments.
Interactive Delivery Services or Interactive Delivery Services Accelerated can be configured to
ingest feedback data back to the repository.
Page Builder’s XML component now supports XML/XSL with XDQL constructs.
New interface enhancements have been made to the IP Rights feature set of Digital Asset Manager.
These include:
• A Rights Manager can create Rights in any location within a repository and also reuse the
right at any point of time. A Rights Manager will be able to reuse this newly created right and
assign it to any files within the repository.
• To add IP Rights, a Rights Manager can select Add IP Right option in the context menu of a file.
The Active Downloads node in the Browse Tree allows quicker and easier access to current
active downloads.
Support for Microsoft Type 4 SQL server JDBC driver is packaged along with the product. The
user does not have to download the Microsoft SQL Server from the Microsoft website.
Note: When Content Server is configured for MS‑SQLServer database, ensure to update the
value of source_database_connection property with the database host name and port number
in webcache.ini. For example, update source_database_connection=jdbc:odbc:mssqlconnection to
source_database_connection=jdbc:sqlserver://10.31.107.144:1433.
New Certifications
New certifications are provided for xDB 9.0. DDS jar is packaged for xDB 9.0.
Ingestion Mechanism
IDS offers a bi‑directional capability of delivering (publish) content to a target and also pulling
content back to the repository. This is known as Ingestion. Ingestion is a process that pulls content
from the staging target back to the repository. You can select to ingest content using the Advanced
tab in Documentum Administrator.
The ingest operation has a lock and unlock feature similar to a publish operation. IDS uses a lock
object, the webc_lock object, to prevent simultaneous ingest operations for a particular content
delivery configuration. The object type is installed when the IDS source software is installed. The
lock object is created every time an ingestion job is initiated for a particular configuration. The
lock is cleared when an ingestion job is successfully completed.
Ingestion mechanism
IDSx offers a bi‑directional capability of delivering (publish/replicate) content to a target and also
pulling content back to the repository. This is known as Ingestion. Ingestion is a process that pulls
content from the staging target and/or replication targets back to the repository. You can select to
ingest content using the Advanced and the Replication tabs in Documentum Administrator.
The existing end‑to‑end test for a delivery configuration is extended to replication targets in a
content delivery configuration. Use the end‑to‑end tester to test your setup and to determine
whether a given content delivery configuration works. The end‑to‑end tester simulates a
replication operation and tests each element of the replication process to ensure that it works.
The elements tested include:
• The presence of all necessary files on the source and target hosts
• Connections to the repository, target host, staging target host to the replication target host,
and databases on the source and target hosts
• Whether the required RDBMS database tables can be created
• Whether the necessary information is provided by the initialization files and configuration
objects
• Creation of directories and files
New certifications
New certifications are provided for HP‑UX environment for IDSx 6.5 SP2.
The UDP connection checker tools are packaged along with the product. To check for the
UDP connection between two machines, you must run the UDP tools from the command line
terminal. For example, run the UDP receiver tool aspera‑udp‑rcv 33001 on the server , and run
the UDP sender tool aspera‑udp‑snd server‑ip‑address 33001 on the client. You must replace the
server‑ip‑address with the IP address of the accelerated data transfer server.
Microsoft Type 4 SQL server JDBC driver is packaged along with the product. The user does not
have to download the Microsoft SQL Server from the Microsoft website.
Note: When Content Server is configured for MS‑SQLServer database, ensure to update the
value of source_database_connection property with the database host name and port number
in webcache.ini. For example, update source_database_connection=jdbc:odbc:mssqlconnection to
source_database_connection=jdbc:sqlserver://10.31.107.144:1433.
For replication, IDSx uses a lock object, the webc_lock object, to prevent simultaneous replication
operations for a particular content delivery configuration. The object type is installed when the
IDSx source software is installed. The lock object is created every time a replication job is initiated
for a particular configuration. The lock is cleared when a replication job is successfully completed.
The ingest operation has a lock and unlock feature similar to a publish operation. IDSx uses a lock
object, the webc_lock object, to prevent simultaneous ingest operations for a particular content
delivery configuration. The object type is installed when the IDSx source software is installed. The
lock object is created every time an ingestion job is initiated for a particular configuration. The
lock is cleared when an ingestion job is successfully completed.
Replication can be invoked automatically after a publish operation. This is done by setting the
extra argument auto_replication value to true in Documentum Administrator.An extract of the
sample log file is given here:
May 14 09:44:23.326:S: INFO: Webcache publish completed successfully.
May 14 09:44:23.332:S: INFO: Invoking Auto Replication
May 14 09:45:16.045:S: INFO: Auto Replication log file name : rep rajiv_config1 20090514 09.4
May 14 09:45:16.045:S: INFO: Auto Replication completed successfully.
Adobe Graphics Server and its associated plug‑in are no longer part of .
EXIF is a standard for embedded metadata. This new plug‑in extracts EXIF metadata from all
applicable files.
Flash9 (F4V) is a new format supported by AVTS for 6.5 SP2. AVTS now uses Flash9 as the default
rendition format for video files. Prior to 6.5 SP2, quicktime streaming (MOV) was used as the
default rendition format upon importing video files.
Audio and video codecs for some file formats were updated in applicable profiles.
The xml name of the profile is ʺcondensePDF_adts.xml” and the display name in the
Transformation wizard is ʺMerge Documents To PDF and Condense the Whitespace”.
This profile merges multiple documents together and trims the whitespace at the end of each
document to save space. Instead of every document being inserted on a separate page, regardless
of how big the pages are, you can merge multiple documents into a single page of the PDF output.
For example, a legal document may have many ʺclauses” that need to be added to the end of a
document. These clauses (that will probably only be a couple of sentences each) can be stored in the
repository in their own separate document. When creating the final legal document, the user can
select all of the clauses to merge together and display on a single page at the end of the document.
This new plug‑in also allows EMCMF PDF documents to be transformed to PDF/A format.
Compliance
— This role is also a member of the RMA Privileged User role, and PRM Inventory Manager
Role.
• RMCE Contributor
— Can add documents/objects to a File making them a record.
— This role is also a member of the RMA Records Contributor role.
Archiving
Replicate SAP feature in CS SAP handles replication of SAP object attributes to Documentum
objects metadata.
The replicate SAP integrates the following functionality:
• Creates and updates the Documentum object from SAP object attributes according to the
mapping in webadmin. These conditions depend on the configuration of Replicate SAP Action.
• Installs the Documentum object for business partner and the opportunities object for SAP
Queries. After configuring them in SAP Queries those SAP queries executes successfully
at webadmin.
• In the Replicate SAP webAdmin page, on changing the SAP System Type dropdown to
CRM, SAP Query type dropdown is changed and contains SAP Queries corresponding to
CRM system only.
• In the Agent webAdmin page, on changing the SAP System Type dropdown to CRM, Action
dropdown is changed and contains Replicate SAP Actions corresponding to CRM system only.
Capture is no longer available as part of CS SAP at D6.5 SP2. Instead, InputAccel is available for
customer purchase to replace Capture functionality.
ERP services
The ERP Integration Service is a SOAP‑based API used for Content Services for SAP (CS SAP)
Agent functions. It is used to execute CS SAP actions and SAP queries using a predefined
interface. The service is a multi‑layered service library, built on the DFC, JAX‑WS, and EI Core
Library and the CS SAP Java Agent.
The ERP Integration class is a JAX‑WS and DFC based web service and operations provide SAP
integration functions, such as:
• Executing preconfigured actions used to establish links and replicate data between SAP and
Documentum.
• Executing SAP functions (BAPIs) and returning results.
Documentum Platform
A new group dm_read_all is introduced in D6.5 SP2 that gives the users read permissions, and
members of this OOTB group can read any object in the repository regardless of the ACL. This
group operates similar to dm_browse_all, instead of BROWSE permission it has READ permission.
The dm_read_all group is created during the server startup if the group does not exist already.
The membership of the group for session user everywhere (that is when constructing an object or
performing DQL statements) is checked for the READ permission before looking into the ACL. For
example, if a user is a member of the dm_read_all group, then the user is allowed to construct and
update any object in the repository even if the user does not have any permission in the associated
ACL. Similarly, if the session user belongs to the dm_read_all group, then the ACL predicate is not
constructed when converting a DQL statement to the corresponding SQL statement.
A new graphical user interface for Installing OEM edition is introduced in this release
Documentum Administrator
Prior to 6.5 SP2 release, you used the MIGRATE_CONTENT administration method to move
content from file stores, retention type stores, blob stores, and distributed stores to file stores,
retention type stores, and distributed stores.
Documentum Administrator 6.5 SP2 and later supports migration from external stores. However,
you cannot move files to external stores.
Application templates
The 6.5 SP2 release of DDS contains two application templates, a publishing template and an
archiving template. These application templates allow developers to build an application
quickly and easily. Instead of trying to build an application from scratch using GWT or another
UI interface, a developer can now start from a pre‑built application template and modify the
components to deliver a complete application in a shorter amount of time. All pieces used in the
template are modeled in such a way that they can be re‑used in other applications easily.
For example, the publishing template has a header, search form, search result list, table of contents
tree and preview, and includes all event handlers to tie the pieces together. The publishing
application template could be extended with the ability to add comments and rating.
Administration tool
The latest DDS administration tool includes a structured view of DDS configurations for
applications, stores, and data sets. A user can navigate through the current DDS configuration and
use form‑based dialogs for modifications and extensions. For example, users can now configure a
new DDS file system store with the administration tool, saving the user the trouble of manually
editing the underlying (XML) configuration files.
WSDL interfaces
With 6.5 SP2, DDS provides WSDL interfaces for XQuery and XProc services.
xDoc integration
DDS now provides xDoc integration in the XProc engine. The latest XProc engine contains custom
steps for xDoc, allowing the application designer to access xDoc functionality in the XProc
pipeline. Users can convert source documents in Word, PDF, and other formats, to XML for
further processing in XProc.
DDS now provides integration with XPression. The latest XProc engine contains custom steps
for XPression that allows application designers to transform a document template into one of the
output formats supported by xPression. The template can be static, for example created by DDS,
or be generated dynamically in the XProc pipeline.
xDB 9 support
In the 6.5 SP2 release, DDS is fully compatible with xDB 9.0.
RepositoryInquiry service
This new service gets a list of available Documentum Content repositories without requiring
authentication.
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.
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.
Table 1. New thirdparty product versions supported for the Documentum ECM 6.5 release
Note: This table is only mean to be a ʺhighlightʺ for the release. This newer version of 3rd
party products may not be supported by all our products so please refer to the product specific
table(s) to see the exact supported configurations.
1Java SE 6.0 support is for browser client, standalone DFC and for all application server supports Java 6.
2Sun Java System Application Server 9.1.1 was renamed to Sun GlassFish Enterprise Server v2.
4Windows Server 2008 Active Directory Application Mode (ADAM) was renamed to Active
Directory Lightweight Directory Services (AD LDS).