Dfc 4.2.16 Patch Release Notes

Patch Release Notes for DFC 4.2.16

for Windows, Solaris, HP-UX, and AIX

March 2004

Copyright © 1994–2004 Documentum, a division of EMC 6801 Koll Center Parkway Pleasanton, CA 94566 All rights reserved. Printed in USA. DOCUMENTUM, NOW YOU KNOW, UNITING THE WORLD THROUGH CONTENT, and the Documentum logo are trademarks or registered trademarks of Documentum, a division of EMC, in the United States and throughout the world. All other company and product names are used for identification purposes only and may be trademarks of their respective owners.

Revision History The table lists the published versions of this document. Date

Changes

2004 March 17

First publication

Verification This release is binary compatible with DFC 4.2.14. It provides fixes for the customer reported problems listed in “Bugs Fixed” on page 3, plus a number of other bugs. This release is a patch to DFC 4.2.14. DFC 4.2.16 bears the same relationship to other Documentum products as DFC 4.2.14 does. Documentum supports DFC 4.2.16 in the same software environments as DFC 4.2.14. Refer to the DFC 4.2.14 Release Notes for specific information. Documentum installs the latest appropriate version of the DMCL client side library with DFC 4.2.16. This may be different from the version installed with DFC 4.2.14, but it is backward compatible. The table shows the version of DMCL shipped with DFC 4.2.16 for each platform: Windows

4.2.6q

Solaris

4.2.6o

HP-UX

4.2.8g

AIX

4.2.5c

Documentum reports fixed bugs for DMCL and Content Server together. There is no separate list of fixed DMCL bugs.

2

DFC Patch Release Notes

Bugs Fixed This release is a patch to DFC 4.2.14. It fixes the following bugs: Bug Number

Description

56262

XDQL returns org.xml.sax.SAXParseException: File 4.2.15 not found when the DTD for the XML Application includes a reference to an external file.

57582

Checkout of an XML document does not download the supporting documents to ...\XML Applications\<docbase name>\<xml application>.

4.2.15

57907

Superuser cannot cancel checkout.

4.2.15

58831

Checkin of a chunked XML file throws null pointer exception if setFilePath method has been called on a node.

4.2.15

59360

XDQL operations sporadically fail in the DFC parser calls, sometimes resulting in partial query results returned to the XDQL queries.

4.2.15

59837

Export of an XML document fails if a processing instruction precedes the DOCTYPE declaration.

4.2.15

60016

Checkin does not start a new branch when versioning is set to BRANCH_VERSION.

4.2.15

60670

4.2.15 Checkin and checkout of virtual document changes binding rule from “Default to current” to “Fix to current.”

61817

The removeChildRelative and removeParentRelative methods generate DM_QUERY_E_SYNTAX exception if the childLabel argument is not within single quotes.

4.2.15

61858

Checkin of an XML document as SAME VERSION causes the lifecycle is re-applied, demoting the document to the base state.

4.2.15

63323

Working with XML documents for which there is 4.2.15 a link rule with the peer option, removing the relation from the parent and checking the parent in as SAME VERSION leaves the relation in place.

DFC Patch Release Notes

Fixed In

3

4

Bug Number

Description

Fixed In

64248

The dexpn40.dll has concurrency problems.

4.2.15

65333

setMaxRows method does not properly limit the number of rows returned by XDQL queries.

4.2.16

66085

When DFC 4.2.15 reads a binary rendition, it 4.2.16 regenerates it. Other versions of DFC cannot load the regenerated rendition.

66753

The hasValueAssistance method of the DFC 4.2.15 class that implements IDfValidator returns java.lang.ArrayIndexOutOfBoundsException, causing Desktop Client 4.3.2a to display an error message.

69265

Under some conditions, power promoting a 4.2.16 change set containing a file with no effective date can result in a file with an incorrect year field in the effective date (2098 rather than 1998, for example).

69824

Owner of an XML virtual document can inadvertently cancel checkout by other users of components of the document.

4.2.16

70374

A newline character in the content of an XML element used to generate the object_name attribute of a chunk can lead to a corrupted documentum.ini file.

4.2.16

71660

If an application uses an entity rule and you 4.2.16 import an XML document in which an entity reference follows an element with no content, the operation proceeds without error, but the resulting document is malformed.

71283

Multiple cycles of (check out, check in as same version) can cause the checkin operation to fail with the error message “entities not declared.”

4.2.16

73266

Methods of the classes that implement IDfVersionPolicy and IDfVersionTreeLabels sometimes return incorrect version labels.

4.2.16

73378

Removing a child from the parent of a virtual document and checking in the parent as a new version results in losing a child from the old version.

4.2.16

4.2.16

DFC Patch Release Notes

Files in This Patch This release contains a full DFC distribution.

Installing This Patch Follow the procedure specified in the appropriate one of the following sections. The installation procedure differs between Windows systems and Unix systems.

Windows Warning: On a Windows system you can have only one DFC installation, so you must remove any previous installation before installing this version. Be sure to reboot after uninstalling DFC. Note: If you wish to use the Documentum versions of Xalan and Xerces, then any other versions of Xalan or Xerces must not appear ahead of dfc.jar in the CLASSPATH environment variable Note: If the DFC installer detects a version of the Microsoft JVM with build number less than 5.0.3802, it automatically upgrades it. You can determine the version of your JVM by viewing the properties of the msjava.dll file in the System directory. Look at the Version tab in the standard Windows Properties dialog box. ➤

To install DFC on a Windows system:

1.

Save all work and close open applications.

2.

Use the Add/Remove Programs section of the Windows control panel to remove Documentum DFC Runtime Environment.

3.

Reboot. After the reboot, do not run any other programs before proceeding.

4.

Run setup.exe from the DFC distribution. Normally, you download a zip file from the FTP site, unzip it, and find setup.exe among the extracted files. The only option is to specify an installation location or accept the default.

DFC Patch Release Notes

5

Solaris, HP-UX, or AIX Installing DFC on a Unix system falls into the following cases: ■ Upgrade the version of DFC that an installation of Documentum Content

Server uses. ■ Create or replace an instance of DFC that differs from the one a server

uses—either on the server machine or on a separate machine.

Upgrading DFC on an Installation of Content Server To upgrade DFC on an existing server installation, you must find the following files and replace them with new versions from the DFC distribution: ■ The class files ❒ dfc.jar on all Unix systems ■ The DMCL library ❒ libdmcl40.sl on HP-UX

Ensure that this file has execute permission. ❒ libdmcl40.so on AIX or Solaris

The filename is the same on both platforms, but the files are not interchangeable. ■ The Docbasic expression evaluation library ❒ libdexpn40.sl on HP-UX

Ensure that this file has execute permission. ❒ libdexpn40.so on AIX or Solaris

The filename is the same on both platforms, but the files are not interchangeable. Note: Do not use any other files from the distribution. If the installed DFC is for use by a RightSite installation, perform the following procedure. ➤

To use DFC with RightSite:

1.

Within the RightSite installation directory hierarchy, find the directory /product/classes

2.

6

Copy the newly installed dfc.jar into classes.

DFC Patch Release Notes

3.

Make classes the working directory and execute the following command: jar xf dfc.jar

4.

Delete the copy of dfc.jar from classes.

Creating or Replacing a Non-Server DFC Instance To create or replace a non-server DFC instance (which can be on the same machine as the server), you must use all of the files from the distribution. ➤

To install a non-server DFC instance on a Unix system:

1.

Choose or create an installation directory (for example, /user/bin/dfc_aix).

2.

Copy all of the DFC distribution files into the installation directory. If the directory contains an existing DFC installation, simply overwrite the files. The new ones have the same names as the old ones. For HP-UX, ensure that all shared libraries have execute permission.

3.

Set environment variables for any user who uses this DFC instance. ■ CLASSPATH

Include full path to dfc.jar. ■ Library path variable: ❒ LD_LIBRARY_PATH for Solaris ❒ SHLIB_PATH for HP-UX ❒ LIBPATH for AIX

Full path to installation directory. ■ PATH

Full path to installation directory. ■ DMCL_CONFIG (optional)

Documentum clients require a file called dmcl.ini to identify a DocBroker for DFC to use to establish a session with a Docbase. Set DMCL_CONFIG to the full path to the DMCL configuration file. For example, /user/bin/ dfc_aix/dmcl.ini. If you do not set DMCL_CONFIG, DFC looks for dmcl.ini in its home directory (for example, /user/bin/dfc_aix), then in the directory pointed to by LD_LIBRARY_PATH. 4.

If the installed DFC is for use by a RightSite installation, perform the following steps: a. Within the RightSite installation directory hierarchy, find the directory /product/classes

DFC Patch Release Notes

7

b. Copy the newly installed dfc.jar into classes. c. Make classes the working directory and execute the following command: jar xf dfc.jar

d. Delete the copy of dfc.jar from classes.

8

DFC Patch Release Notes