content server release notes

Content Server Release Notes

Version 5.3 SP1December 2005

Copyright © 1994-2005 EMC Corporation. All rights reserved.

Revision History:September 2005: Initial Release.December 2005: Added thesaurus limitation on AIX; information on LDAPSynOnDemand; addeddm_mail_message and data dictionary issue; adding information on content duplication checking;added a full-text indexing documentation correction; updated Requirements chapter.

Table of Contents

Chapter 1 Product Description .............................................................................. 9

Chapter 2 New Features and Changes ................................................................... 11New features for Version 5.3........................................................................ 11New features for Service Pack 1 ................................................................... 13Changed features ....................................................................................... 15Removed features ....................................................................................... 15Removed in 5.3....................................................................................... 15Removed in 5.3 SP1 ............................................................................ 16

Chapter 3 Environment and System Requirements ............................................... 17Hardware Requirements ............................................................................. 17Content Server Machine Requirements .................................................... 17

Software Requirements ............................................................................... 18Content Server Environment ................................................................... 19Exceptions ......................................................................................... 20Notes ................................................................................................. 21

Full-Text Index Server Environment......................................................... 22Exceptions ......................................................................................... 23Notes ................................................................................................. 23

Index Agent Administration Tool Environment ........................................ 23Notes ................................................................................................. 23Exceptions ......................................................................................... 24

Additional Operating Environments ........................................................ 24Exceptions ......................................................................................... 24Notes ................................................................................................. 24

Cross Product Dependencies ....................................................................... 24

Chapter 4 Fixed Problems ..................................................................................... 27Fixed bugs ................................................................................................. 2781615 ..................................................................................................... 2792461 ..................................................................................................... 2895049 ..................................................................................................... 2896471 ..................................................................................................... 2996486 ..................................................................................................... 29

Chapter 5 Known Problems and Limitations ......................................................... 31Known problems ........................................................................................ 3189623 — Indexing failure due to batch loss ............................................... 3190418 — Inability to search specially formatted text in PDFs ..................... 3298441 — Error signing documents larger than 50 M .................................. 32102498 — Error setting environment variables for indexingsoftware on Solaris 9 platform ................................................................. 32103073 — Numerous warning messages in index agent log file .................. 32103719 — ROW_BASED DQL hint failure ................................................ 32

Content Server Release Notes 3

Table of Contents

103726 — ACS server base URL ............................................................... 33104774 —Windows/SQL Server upgrade problem .................................... 33104927 — Switching index modes causes error from IA jsp page ................ 33105039 — Electronic signature (esignature) failure .................................... 33105082 — Indexing content stored on NAS devices .................................. 34105111 – Network locations in Portals login page ...................................... 34105181 — Error when installing remote Content Server ............................. 34105197 — Microsoft Word and Excel templates in upgradedrepositories ............................................................................................ 34105219 — Location linking failure for Java lifecycles in some cases............. 35106055 — Problem with LDAP configuration with SSL.............................. 35106298 — Retention dates in Centera stores .............................................. 35106820 — Thesaurus on AIX ................................................................... 36109155 —Workflow promotion failures on Windows ContentServer hosts............................................................................................ 36

Limitations................................................................................................. 36Viewing the index agent log file............................................................... 36Error indexing text or XML files .............................................................. 37Createaudit API limitation ...................................................................... 37Failover to ACS limitation (bug 105202) ................................................... 38

Chapter 6 Technical Notes ..................................................................................... 39Installation notes ........................................................................................ 39Platform-independent installation and upgrade notes ............................... 40Full release......................................................................................... 40Installation manual ............................................................................. 41Content Server upgrade paths ............................................................. 41Content Server and index server on the same host ................................ 41Installing remotely.............................................................................. 41Upgrading DFC.................................................................................. 41Upgrading a repository configured for Documentum Clientfor Outlook ........................................................................................ 41Workaround if repository upgrade fails while executing theBPM installation script ........................................................................ 42Default settings in docbase config may affect client access ..................... 43Resolving type cache problems on clients after upgrade ........................ 43Moving repositories across platforms and the AEK.key file ................... 44Setting the server_os_codepage and client_codepage on theJapanese Content Server...................................................................... 44The database_refresh_interval Key ...................................................... 44

Windows-specific installation notes and issues ......................................... 44Windows installation owner account ................................................... 44Installing the Korean data dictionary information onJapanese Windows ............................................................................. 45Upgrading distributed configurations .................................................. 45

Installation issues for all UNIX platforms ................................................. 45Change for Tomcat application server startup....................................... 45New command line for launching repository configuration ................... 46_s entry in the Service Names file......................................................... 46

Installation issues specific to AIX ............................................................. 46Upgrading on AIX with DB2 ............................................................... 46C++ runtime library version................................................................. 46AIX host requirement ......................................................................... 46

Installation issues specific to HP-UX ........................................................ 47Installing on HP-UX when the device name for the tempdirectory is longer than 15 characters ................................................... 47

Environment variables (UNIX and Linux) ................................................ 47Installation issues specific to Sybase......................................................... 47

4 Content Server Release Notes

Table of Contents

Repository upgrade may hang on Sybase platforms .............................. 47Configuration Notes ................................................................................... 48Content Storage Services license requirement ........................................... 49DNS requirement for web-based client hosts in distributedenvironment .......................................................................................... 49Apache Tomcat application server ........................................................... 49Content Server failover change ................................................................ 49Index needed for Retention Policy Services............................................... 50New user authentication attributes .......................................................... 50Host machine requirements for Surrogate Get and contentreplication.............................................................................................. 50The vpd.properties File .......................................................................... 50New directories in installation ................................................................ 51New directory for full-text .................................................................. 51New directory for language files (Oracle Only) ..................................... 51

The oldest_client_version attribute .......................................................... 51Surrogate Get change.............................................................................. 51DMCL exception handling on UNIX platforms ......................................... 52Heap corruption and continue on exception ......................................... 52DMCL stack trace files ........................................................................ 52Obtaining a DMCL stack trace on Solaris 9 ....................................... 53Obtaining a DMCL stack trace on Solaris 8 ....................................... 53Obtaining a DMCL stack trace on AIX 5.2 or 5.3 ............................... 53

Storage policy updates ............................................................................ 54Setting default_app_permit in docbase config .......................................... 54Changes to the dm_event_sender script arguments................................... 54Job trace files .......................................................................................... 55Content-addressed storage notes ............................................................. 55Storage location of ca store plug-ins ..................................................... 55Required permissions on Centera host ................................................. 55Setting clocks and time zones for Centera hosts and ContentServer hosts........................................................................................ 56Specifying multiple Centera IP addresses in ca store objects .................. 56Setfile, Setcontent, and Removerendition changes ................................ 56

Note regarding the Shutdown method and Windows platforms ................ 57Updating the federation methods ............................................................ 57Migrating to Documentum Content Services for EMC Centera(CSEC) 5.3 from CSEC 1.2c or Prior.......................................................... 57What migration does .......................................................................... 58Migrating the objects .......................................................................... 58

Auditing content migration in lifecycle actions ......................................... 60Usability Notes........................................................................................... 60String datatype maximum length on SQL Server ...................................... 61Dmbasic lifecycles and Retention Policy Services ...................................... 61DQL hints and FTDQL queries ................................................................ 61Remote hosts failed or ACS not available messages................................... 61Workaround for bug 81615 ...................................................................... 61WORKFLOW_AGENT_DIED error ......................................................... 62Tracing default for surrogate get is changed ............................................. 62Supported versions in repository federations............................................ 62Java method server ................................................................................. 63Printing from lifecycle programs ............................................................. 63Indexable formats ................................................................................... 63File store mapping for full-text indexing on NAS devices .......................... 64Index agent warning message.................................................................. 64

Chapter 7 Documentation ...................................................................................... 65Content Server documentation set ............................................................... 65


Table of Contents

Obtaining the correct documentation ........................................................... 66Documentation corrections and clarifications ............................................... 66Content Server 5.3 SP1 Release Notes, September 2005 .............................. 66Content Server Fundamentals ................................................................. 66Content Server Installation Guide ............................................................ 67Content Server Full-Text Indexing Installation Guide ................................ 67Disk space requirements for indexing and installation .......................... 67

System Migration Guide, Migrating Content Server chapter ...................... 68Activity object type............................................................................. 68Workflow object type .......................................................................... 68

Content Server Administrator’s Guide, Full-Text Indexing chapter............. 69Content Server Administrator’s Guide, Content Managementchapter .................................................................................................. 69Content Server Administrator’s Guide, Protecting RepositoryObjects chapter....................................................................................... 69

Documentum Object Reference Manual ....................................................... 705.3 FCS Object Reference Manual correction ................................................. 70Content Server API Reference Manual ......................................................... 70Content Server DQL Reference Manual ........................................................ 71

Chapter 8 Software Media, Organization, and Files ............................................... 73Software media .......................................................................................... 73Organization .............................................................................................. 74Files........................................................................................................... 74

Chapter 9 Installation ............................................................................................. 77

Chapter 10 Troubleshooting and Getting Help ........................................................ 79


Table of Contents

List of Tables

Table 3–1. Content Server Machine Requirements ............................................................ 18Table 3–2. Index Server Machine Requirements ................................................................ 18Table 3–3. Content Server Environment ........................................................................... 19Table 3–4. Index Server ................................................................................................... 22Table 3–5. Index Agent Administration Tool .................................................................... 23Table 3–6. 5.3 SP1 Additional Operating Environments..................................................... 24Table 3–7. Cross Product Dependencies ........................................................................... 25Table 6–1. dm_migrate_to_ca_store.ebs Arguments .......................................................... 59


Table of Contents


Chapter 1Product Description

Content Server is the core of the EMC Documentum content management platform. Content Servergoverns the content repository and enables a rich set of content management services for controllingboth content and processes throughout distributed enterprises. Documentum Content Server lets youstore, manage, and deploy all types of content, including HTML and XML, graphics, and multimedia.Content Server provides services such as integrated workflow, lifecycle, and process automation;version control, robust security, and a data dictionary for capturing and configuring business rules.

With EMC Documentum Content Server, users can share and reuse trusted content on demand withinand between business units. Administrators can define, organize, automate, and monitor all thefunctions and tasks of even complex business processes.

The SP1 release adds to these capabilities. For example, the release adds distributed support forweb-based users, full-text indexing enhancements, row-based querying capabilities, and contentstorage enhancements. For a listing of all new features, refer to Chapter 2, New Features and Changes.

The SP1 release is a full release. It does not need to be applied to an existing 5.3 installation.


Product Description


Chapter 2New Features and Changes

This section lists new features in the Content Server 5.3 set of releases.

New features for Version 5.3This section describes features that are new to Content Server. Some of the features listedbelow were introduced in the 5.2.5 SP releases and will only be new to you if you areupgrading from 5.2 or 5.2.5. Those features are noted in the list.

Content Server 5.3 contains the following new and enhanced features:

1. New indexing implementation and architecture

For information about this, refer to the Content Server Administrator’s Guide. TheContent Server Installation Manual contains procedures for setting up and using thenew implementation.

2. New querying ability called FTDQL.

FTDQL is a subset of the SELECT statement syntax that queries the fulltext indexrather than the repository. Using FTDQL provides performance benefits. For details,refer to the SELECT statement description in the Content Server DQL Reference Manual.

3. The ability to use SSL communications between Content Server and client libraries isnow part of the standard server package. It is no longer controlled by the TrustedContent Services license.

4. Enhancements to ACLs that provide additional flexibility in assigning object-levelsecurity

5. Ability to define groups as dynamic groups

6. Support for Java in lifecycle entry criteria, actions on entry, post-entry actions, andvalidation programs

7. New workflow functionality, including


New Features and Changes

• Support for XPath specifications in route case conditions

• New workflow timer implementation, including the ability to use a timer toautomatically resume suspended activities

• Support for work queues

• Ability to define the number of tasks required to complete an activity (5.2.5 SP1)

• Ability to limit the number of output ports selected by a user upon completion ofa task (5.2.5 SP1)

• Ability to define transition behavior when multiple, contradictory (revert andforward) ports are selected (5.2.5 SP1)

• Ability to define a task subject, using parameters resolved at runtime, to providemore information for task owners (5.2.5 SP1)

• Ability to record a component name in the package object, for use in the tasksubject (5.2.5 SP1)

8. New attributes for users. The attributes are:

• user_login_name

• user_login_domain

• user_password

• restricted_folder_ids

The user_login_name and user_login_domain attributes replace user_os_name anduser_os_domain for authentication purposes. The user_password attribute stores auser password if the user is validated using a password stored in the repository.

The restricted_folder_ids attribute is used if you want to restrict a user’s access to aparticular set of folders.

For information about using these attributes, refer to the Content ServerAdministrator’s Guide.

9. Global login tickets and application access tokens

10. Ability to use digital shredding to remove content files stored in file store storageareas. (This feature requires a Trusted Content Services license.)

11. A change to the connection pooling implementation that changes how theconnect_recycle_interval value in the dmcl.ini file is interpreted

12. The Content Storage Services license, an optional license for Content Server thatallows you to define storage and migration policies for content files (5.2.5 SP2)

13. The Collaborative Services license, an optional license for Content Server thatprovides support for the Collaborative Editions of EMC Documentum clients.



14. Support for Retention Policy Services, an optional product that allows you to defineretention policies to govern document retention in the repository.

15. During installation, on UNIX and Linux platforms, most required environmentvariables are now set by a script. Environment variables (UNIX and Linux), page47, describes this change in more detail.

New features for Service Pack 15.3 Service Pack 1 introduces the following new features:

1. Distributed content support for web-based users

This new feature supports fast access to content for remote users accessing arepository through web-browsers. The feature includes a new service, AcceleratedContent Services, represented by the ACS server. The ACS server is installed withContent Server. It also supports Branch Office Caching Services, an optional productthat provides the BOCS server.

The new distributed model for web-based users is fully described in the DocumentumDistributed Configuration Guide.

2. A new, automated installer for remote Content Servers in distributed contentinstallations

3. Full-text indexing enhancements, including:

• Ability to partition an index

• Thesaurus searching

• Ability to index multiple repositories with one index server installation

• Ability to install indexing software on a platform that differs from the ContentServer host installation platform

• Search summary results and term-hit highlighting in the summary

For information about these configuration options, refer to the Content ServerAdministrator’s Guide. The supported platforms for indexing software are describedin Chapter 3, Environment and System Requirements.

4. Support for content compression and duplicate content checking and prevention

Content compression is supported for file store and content-addressed storage areas.

Duplicate content checking and prevention is a feature supporting content archiving,particularly of email and its attachments. If enabled, it ensures that only one copyof an attachement or content file is archived regardless of how many users arerecipients of the mail. This feature is supported for file store storage areas.



5. New DQL hint, ROW_BASED

The ROW_BASED hint directs Content Server to return results as rows, rather thanin an object-based format. This affects not only the format of the returned results, butalso some syntax rules for the SELECT statement. For example, it loosens constraintson how repeating attributes can be referenced in the query. It also affects what isreturned by an asterisk (*) in the selected values list. For a full description of its use,refer to the Content Server DQL Reference Manual.

6. Support for new workflow functionality, including

• Ability to define a skill level for users performing workflow tasks

This feature is available only through Business Process Manager.

• Changed implementation of the workflow agent’s master session, to allowmultiple workflow agents to execute against the same repository.

The new implementation allows each agent’s master session to claim a set ofwork items, ensuring that there are no conflicts if multiple agents are runningagainst a repository.

7. Batch processing for object replication jobs

You can configure the job to dump and load the objects in batches, thereby reducingrequirements for temporary disk space and limiting lost work when a failure occurs.For information, refer to the Documentum Distributed Configuration Guide.

8. Two new arguments for the Content Replication job:

• -batch_size, which allows users to configure the size of the batches used toprocess the content files being replicated

• -source_servers, which allows users to identify the servers to which the job is toconnect

9. A set of scripts supporting high availability. The scripts provide running or stoppedstatus information about Content Server, the connection broker, and the index agent.The scripts can be integrated into commercial monitoring packages. For a list of thescripts, refer to the Content Server Administrator’s Guide.

10. Dmclean has a new argument, -clean_aborted_wf. If specified, the method removesall aborted workflows in the repository.

11. Saveasnew API has a new argument, to indicate where to store new copies of content

12. Lock API has a new argument.

The argument, validate_stamp, controls whether the vstamp value is validatedbefore a lock is placed on an object.



Changed featuresFor a listing of the changes to the object type hierarchy, DQL, and DMCL API thatsupport the new features, refer to the EMC Documentum 5.3 System Migration Guide.Other changes include:

1. The distributed content model is changed in many details. Refer to the DistributedContent Guide for details of the new implementation.

2. The LDAP Synchronization job is now run by the Java method server.

3. In distributed content configurations, remote Content Servers with a proximityvalue of 9000 or higher cannot be used for data requests if the primary ContentServer is not running.

4. The dm_SurrogateGet and dm_ContentReplication methods now use a global loginticket to connect to the target repositories. (Refer to Host machine requirements forSurrogate Get and content replication, page 50 and Surrogate Get change, page51for the implications of this change.)

5. Repository sessions cannot fail over to Content Servers with proximity values 9000or greater.

Removed featuresThis section lists the features that are removed from the product.

Removed in 5.3

The following features are removed from the product in 5.3:• The pre-5.3 architecture for fulltext indexing is no longer supported• Term-hit highlighting is not supported in the current 5.3 indexing implementation.• The SEARCH TOPIC clause of the SELECT statement is deprecated.• Various object types and attributes

The change in indexing architecture is reflected in the removal or deprecation ofa number of object types and attributes. For a listing of these, refer to the EMCDocumentum 5.3 System Migration Guide.

• ADD_FTINDEX and DROP_FTINDEX options for ALTER TYPE DQL statement



These syntax options are obsolete because the new indexing implementationindexes all attributes regardless of data type and regardless of the attribute’s origin(system-defined or custom).

Removed in 5.3 SP1

The following features are removed from the product in 5.3 SP1:• ContentRepl.cnt password file

Surrogate get and content replication jobs, the two features that used this file, nowuse global login tickets instead.

• RECOVER_TIMEOUT_TASKS administration method

The method is replaced by the RECOVER_AUTO_TASKS administration method.• setupdist utility

The setupdist utility is no longer used for setting up distributed contentenvironments.


Chapter 3Environment and SystemRequirements

This chapter lists the hardware (machine) requirements and software versions supported withthis release. Machine resources, non-Documentum software components (Operating System, JavaRuntime Environment, and so forth), and other Documentum products determine the uniqueenvironment for each Documentum product. Hardware Requirements, page 17 addresses basicmachine resource requirements. Software Requirements, page 18 addresses specific software versionsthat are required for the installation platform.

Content Server operates on a single Content Server environment (see Table 3–3, page 19), with asecond server used to manage full-text indexing.

Hardware RequirementsThis section lists nominal machine resources required for product installation and use.Your individual machine requirements will vary depending on factors such as thenumber of products installed, size of your deployment, number of users, and networklatency. The Documentum System Sizing Guide provides an in-depth analysis of systemsizing requirements for implementation and deployment of Documentum systems.The Documentum System Sizing Tool dynamically generates estimates of your hardwareresource requirements based on your user and hardware profile.

You can download the Documentum System Sizing Tool from the CustomerNet Web site:http://customernet.documentum.com/developer/downloads/DCTMSystemSizingTool.zip

Content Server Machine Requirements

The following table provides nominal resource requirements for the Content Server hostmachine and the index server host machine. You can run Content Server and the indexserver on the same host machine; however, you will need to ensure that the cumulative


http://customernet.documentum.com/developer/downloads/DCTMSystemSizingTool.zip

Environment and System Requirements

minimum installation requirements listed in both Table 3–1, page 18 and Table 3–2, page18 are met. For best performance, we recommend that you run the index server andContent Server on separate host machines.

Table 3-1. Content Server Machine Requirements

Hard Disk Space RAM* CPU Display

700 MB 512 MB See the SupportedProcessor Typecolumn for youroperating system inTable 3–3, page 19.

A video cardcapable ofdisplaying aminimum of 256colors (SVGA), or800 x 600

Table 3-2. Index Server Machine Requirements

Hard Disk Space RAM** CPU

700 MB to install, plus atleast 3GB to run the indexserver

2 GB See the SupportedProcessor Type columnfor your operating systemin Table 3–4, page 22.

* * The amount of RAM that is available after taking into consideration all other RAMutilization requirements.

Software RequirementsThis section provides information on supported software environments.

The tables in this section reflect the latest version(s) of third-party products,upon which the Documentum product depends, that are supported at thetime of this release. Version(s) of third-party products supported with priorservice packs and the 5.3 base release are also supported with this release. Forinformation on currently supported environments and future updates, refer toProduct Information System on the Documentum Technical Support web site:http://support.documentum.com/support/productinfo/dmproductinfo.asp. For detailedinformation about the policies governing supported products, refer to the CustomerGuide available on the Documentum Technical Support web site: http://support.documentum.com/wcmprodData/sppt_svcs/Customer_Guide_Support_Services.pdf.


http://support.documentum.com/support/productinfo/dmproductinfo.asp

http://support.documentum.com/wcmprodData/sppt_svcs/Customer_Guide_Support_Services.pdf


Content Server Environment

A Content Server environment consists of a specific combination of operating systemand RDBMS, and, optimally, an index server host machine for the full-text index server.The following table lists the supported Content Server environments for Content Server.

Table 3-3. Content Server Environment

Operating System Supported Processor Type RDBMS

AIX 5L V5.2 ML5 Power DB2 Universal Database(UDB) 8.1 FixPak 7a, 8.1FixPak 8, 8.2, 8.2 FixPak 1

AIX 5L V5.3 ML1 Power DB2 Universal Database(UDB) 8.1 FixPak 7a, 8.1FixPak 8, 8.2, 8.2 FixPak 1

AIX 5L V5.2 ML5 Power Oracle 9i Release 2 (9.2.0.6)

AIX 5L V5.2 ML5 Power Oracle 10g Release 1(10.1.0.3)

AIX 5L V5.3 ML1 Power Oracle 9i Release 2 (9.2.0.6)

AIX 5L V5.3 ML1 Power Oracle 10g Release 1(10.1.0.3)

HP-UX 11 PA-RISC 2.0 Oracle 9i Release 2 (9.2.0.6)

HP-UX 11 PA-RISC 2.0 Oracle 10g Release 1(10.1.0.3)

HP-UX 11i version 2Update 2 (B.11.23)

PA-RISC 2.0 Oracle 9i Release 2 (9.2.0.6)


PA-RISC 2.0 Oracle 10g Release 1(10.1.0.3)


Itanium Oracle 9i Release 2 (9.2.0.6)


Itanium Oracle 10g Release 1(10.1.0.3)

Red Hat Enterprise Linux3.0 Update 4

Intel (x86) Oracle 9i Release 2 (9.2.0.6)

Red Hat Enterprise Linux3.0 Update 4

Intel (x86) Oracle 10g Release 1(10.1.0.3)

Solaris 8 UltraSPARC Oracle 9i Release 2 (9.2.0.6)



Operating System Supported Processor Type RDBMS

Solaris 8 UltraSPARC Oracle 10g Release 1(10.1.0.3)

Solaris 8 UltraSPARC Sybase Adaptive ServerEnterprise (ASE) 12.5.3ESD #2

Solaris 9 UltraSPARC Oracle 9i Release 2 (9.2.0.6)

Solaris 9 UltraSPARC Oracle 10g Release 1(10.1.0.3)

Solaris 9 UltraSPARC Sybase Adaptive ServerEnterprise (ASE) 12.5.3ESD #2

SuSE Linux EnterpriseServer 9 SP1

Intel (x86) Oracle 9i Release 2 (9.2.0.6)

SuSE Linux EnterpriseServer 9 SP1

Intel (x86) Oracle 10g Release 1(10.1.0.3)

Windows 2000 SP4 Intel Pentium DB2 Universal Database(UDB) 8.1 FixPak 7a, 8.1FixPak 8, 8.2, 8.2 FixPak 1

Windows 2000 SP4 Intel Pentium Oracle 9i Release 2 (9.2.0.6)

Windows 2000 SP4 Intel Pentium Oracle 10g Release 1(10.1.0.3)

Windows 2000 SP4 Intel Pentium SQL Server 2000 SP3a

Windows Server 2003 SP1(32-bit version)

Intel Pentium DB2 Universal Database(UDB) 8.1 FixPak 7a, 8.1FixPak 8, 8.2, 8.2 FixPak 1


Intel Pentium Oracle 9i Release 2 (9.2.0.6)


Intel Pentium Oracle 10g Release 1(10.1.0.3)


Intel Pentium SQL Server 2000 SP3a

Exceptions

Unless otherwise noted:



• The following items are not supported for HP-UX on Itanium:

— EMC Centera support

— eSignature manifestation

— Netegrity Single Sign-on• The following features are not supported for Linux operating systems:

— eSignature manifestation

— Netegrity Single Sign-on• Content Server support for Solaris with Sybase is not available for Japanese or Korean

Notes

Unless otherwise noted, the following products are supported with this release ofContent Server:• EMC Centera Cluster: Centera SDK 2.4• LDAP Servers:

— Active Directory for Windows 2000 & 2003

— Oracle Internet Directory Release 9.2.0.1

— Sun Java System Directory Server 5.2Unless otherwise noted:• The RDBMS may be installed on a different machine from Content Server. See the

Content Server Installation Guide for detailed descriptions of the Content Server andRDBMS installation environment.

• XWindows is required for the GUI installer on UNIX operating systems.• The following Windows 2000 editions are supported: Server, Advanced Server,

Data Center Server• The following Windows 2003 editions are supported: Standard, Enterprise, Data

Center• The operating systems listed in this table include virtualized versions of the

operating system running in any version of VMware Intel-architecture (VMware ESXServer, GSX Server and Workstation).

• English, Japanese, and Korean operating systems are supported.• AIX requires C++ runtime version 6.0.0 (Important: AIX Version 7 C runtime is

not supported.)• We also support 100% Intel compatible processors. Customers will have to obtain

the 100% compatibility statement and guarantee/assurance from the processor and



OS vendors and log bugs directly with those vendors if any compatibility issuesare discovered.

• For Content Server running with Oracle 10g (10.1.0.x) databases, the minimumrequired version is 10.1.0.3.

• For Content Server running with IBM DB2 databases, IBM states that DB2 8.1FixPak 7a is functionally equivalent to DB2 8.2 and DB2 8.1 FixPak 8 same as DB28.2 FixPak 1.

• A private copy of a Tomcat application server is installed by Content Server. Thisapplication server is required for full-text indexing, LDAP user synchronization,Java Lifecycles, and ACS/BOCS features.

• Localized versions of the following RDBMS are supported with this release ofContent Server:

— Oracle

— SQL Server

Full-Text Index Server Environment

The following tables provides information about supported environments for a full-textindexing server:

Table 3-4. Index Server

Operating System Processor

Windows 2000 Server SP4 Intel Pentium

Windows Server 2003 SP1 (32-bit version) Intel Pentium

Solaris 8 UltraSPARC

Solaris 9 UltraSPARC

AIX 5L V5.2 ML5 Power

AIX 5L V5.3 ML1 Power

HP-UX 11 PA-RISC 2.0

HP-UX 11i version 2 Update 2 (B.11.23) PA-RISC 2.0

HP-UX 11i version 2 Update 2 (B.11.23) Itanium

Red Hat Enterprise Linux 3.0 Update 4 Intel (x86)

SuSE Linux Enterprise Server 9 SP1 Intel (x86)



Exceptions

The following exceptions apply:• No multi-node support.• No multi-node partitioning support.• The index server cannot be installed on the Microsoft Cluster Services environment,

but if installed on a separate host, the index server can index and respond to queriesfrom a repository installed on Microsoft Cluster Services.

Notes

Localized Chinese, Japanese, and Korean operating systems are supported.

Index Agent Administration Tool Environment

Table 3-5. Index Agent Administration Tool

Operating System Browser Java Plug-in

Windows 2000 SP4 Internet Explorer 6.0 SP1 Sun JRE 1.4.2_08

Windows 2000 SP4 Internet Explorer 6.0 SP1 MS JVM 5.0.0.3810

Windows XP SP2 (32-bitversion)

Internet Explorer 6.0 SP1 Sun JRE 1.4.2_08

Windows XP SP2 (32-bitversion)

Internet Explorer 6.0 SP1 MS JVM 5.0.0.3810


Internet Explorer 6.0 SP1 Sun JRE 1.4.2_08


Internet Explorer 6.0 SP1 MS JVM 5.0.0.3810

Notes

None



Exceptions

None in this release

Additional Operating Environments

Table 3-6. 5.3 SP1 Additional Operating Environments

Product Operating Environment

VMware Workstation, GSX Server, ESX Server

eTrust Siteminder Policy Server 5.5 SP3 Supportedwith Content Server-supportedenvironments.

Exceptions

For the additional operating environments supported with this release, the followingexceptions apply:• No support for HP-UX 11i version 2 Update 2 for Itanium.• No support for Linux platforms.• eTrust Siteminder is not supported on the Linux operating system.• Netscape and Firefox Web browsers are not supported with eTrust Siteminder.

Notes

Documentum fully supports all of our products running on an OS being virtualizedwithin any version of VMware Intel-architecture as long as that OS is supported bythe appropriate Documentum product.

Computer Associates eTrust SiteMinder was formerly known as Netegrity SiteMinder.

Cross Product DependenciesThe following table lists optional and required versions of products that are dependedon in order to enable additional features.



You may have to install some of the products listed in Table 3–7, page 25 on separatehost or client machines due to differences in the DFC versions included with thoseproducts. Before installing a product, check the product’s Installation Guide for supportedinstallation configurations.

Table 3-7. Cross Product Dependencies

EMC Products Included by Installer

N/A • DFC 5.3 SP1**• EMC Centera SDK• Tomcat

* Interoperability with all other 5.3.x version Documentum client products, while notrequired to enable full functionality, is supported.

By default, Content Server with Collaboration Services or RPS enabled can acceptonly version 5.3 clients. See the product documentation for instructions on how tochange this setting.

For information about the supported configurations for products listed in this table,see the Release Notes for the product.

** This version of DFC works properly with any Documentum client product withversion number 5.2.5 or 5.3, with the exception of the following DFC features, whichwork only when DFC is accessing Content Server version 5.3 or 5.3 SP1:• Fetching service-based object (SBO) implementations from a repository’s globalregistry (Pre-5.3 Documentum systems do not have global registries.)

• Web Services 5.3


Chapter 4Fixed Problems

This section identifies problems and limitations, documented in the release notes of the applicableminor version release or prior service pack(s), that have since been resolved.

Within two weeks of a release we post a more comprehensive list of fixed bugs on the CustomerNetsite. You must have a software support agreement to log in and access this list of fixed bugs.

To view the comprehensive list of fixed bugs, log in to CustomerNet (http://customernet.documentum.com/support) and navigate to Search Support → Bugs and Feature Requests. On the search pageclick the Show Fixed Bugs Lists link.

Fixed bugsThis section lists the tier 1 bugs that have been fixed since the last release of the product.

81615

When a work item generated from an activity that has its performer set to “All Users in aGroup” is completed, the remote_pending attribute of the associated dmi_queue_item isleft set to T. (It should be set to F at that point.) As a result, the QueueMgt administrationjob does not remove those queue items.

This bug is regarded as fixed because a usable workaround is supplied. For instructions,refer to Workaround for bug 81615, page 61.


http://customernet.documentum.com/support

Fixed Problems

92461

The index agent fails to start against Content Server if the dctm-server.jar file isin the user’s $CLASSPATH environment variable when startupIndexAgent.sh orstartupAllIndexAgents.sh is executed.

This bug is specific to the Solaris, Linux, AIX and HP-UX platforms.

95049

On HP Itanium, the index agent gives the following error message in the index agentlog file:2005-03-07 14:49:26,192 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reported2005-03-07 14:49:26,193 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reported 2005-03-07 14:49:27,373 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reported2005-03-07 14:49:30,023 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reported2005-03-07 14:49:35,863 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reported2005-03-07 14:49:39,082 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reported2005-03-07 14:49:41,703 WARN FdsIndexer [Thread-7][DM_INDEX_AGENT_PLUGIN]Callback for ID :_NO_KEY_ON_ERROR_ already reportedThis problem affects the procserver binary on HP-UX ia64 only. To work around theproblem, enable lazy swap allocation for the procserver binary. If lazy swap allocationis enabled, the procserver processes will allocate swap space as required instead ofreserving swap space ahead of time.

To perform the work around for 95049:

1. Stop all instances of the procserver binary.

2. Use following command to enable lazy swap allocation:chatr +dz enable binary

where binary is the path to the procserver binary. You must have write access to thebinary and there cannot be any instances of the binary running when you issuethe command.


Fixed Problems

96471

Deleting an index agent using the index agent configuration program fails to delete thedm_ftindex_agent_config object from the repository if the index agent was created inMIGRATION mode and then changed to NORMAL mode before you deleted it.

To work around this bug:

1. After deleting the index agent, fetch the object ID of its dm_ftindex_agent_configobject.

2. Use a Destroy API method to delete the object.

96486

The functionality represented by the dm_docbase_config.trust_by_default attribute doesnot work as expected for multiple repositories. Setting the attribute to F (FALSE) doesnot prohibit a user from logging in with a global login ticket if the issuing repository isnot a trusted repository.


Fixed Problems


Chapter 5Known Problems and Limitations

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

Note: This section and the Technical Notes section may refer to platforms or features that are notsupported for this release of your product. Check Chapter 3, Environment and System Requirements,to verify requirements.

EMC Documentum makes the latest information about customer-reported issues and knownproblems available at CustomerNet site. You must have a software support agreement to log inand access the list of issues.

Log in to CustomerNet (http://customernet.documentum.com/support) and navigate to SearchSupport→ Bugs and Feature Requests. On the search page click the Show Fixed Bugs Lists link.

Known problemsThis section describes known defects in EMC Documentum software that may affectyour use of the product.

89623 — Indexing failure due to batch loss

Some documents failed to be indexed with the error message from dmi_queue_item as:DOCUMENT_ERROR Batch probably lost during processing

This bug happens when some XML documents cause problems in the index server’sdocument processor, causing the entire batch to fail. If a batch of documents (usuallya maximum of five) fails with this error, submit the dmi_queue_items persisted in thewarning state with this error one by one, preferably when the repository is not beingactively used so that only one item gets into each batch submitted to the index serverby the index agent.



Known Problems and Limitations

90418 — Inability to search specially formatted text inPDFs

Some text in specially formatted areas in some PDF documents is not searchable.

98441 — Error signing documents larger than 50 M

This bug existed in CAS -bug 68013. But now exists with TCS. Signing documentsthrough CAS that exceed 50mb in size will fail to include the content. The signature pageis included in the resulting PDF but the content of the file is missing.

102498 — Error setting environment variables forindexing software on Solaris 9 platform

[Index server install] On Solaris 9 environment, environment variables are not setproperly by executing setupenv.csh even though the proces returns the message:"Environment variables successfully set."

103073 — Numerous warning messages in index agentlog le

IA log has hundreds messages like this: "WARN FdsIndexer [Thread-39][DM_INDEX_AGENT_PLUGIN] Callback for ID :08000928800027d8 already reported" following by"ERROR DSAPICallback [RequestProcessor[1033]]Callback error - Could not send eventto client!

This typically occurs when attempting to delete objects that are not in the index. Thewarnings do not indicate a problem in the index and may be ignored.

103719 — ROW_BASED DQL hint failure

ROW_BASED hint does not work in conjunction with fulltext search.



103726 — ACS server base URL

The ACS server base URL is formed from the value of the r_host_name attribute of theserver config object at the time the ACS server is installed. The value of r_host_nameis identical to the value returned by the operating system’s hostname command. Ther_host_name value is therefore determined by how the host computer is set up.

Depending on how a network is configured, some browser hosts cannot resolve the ACSserver base URL. To work around this problem (for example, if you need a fully-qualifieddomain name in the ACS server base URL or if you need to point to a specific networkcard), modify the acs_base_url attribute of the acs config object. The format of the ACSserver base URL saved in the acs_base_url attribute is:protocol://r_host_name:Java_method_server_port/ACS/servlet/ACS

Use the API or DQL to modify the value of the r_host_name portion of the URL.

104774 — Windows/SQL Server upgrade problem

Installer hangs during upgrade of 5.3 to 5.3 SP1 on Windows (SQL Server) if theinstallation log becomes very large. The log files are created in the install directories(C:\Documentum, C:Program Files\Shared, etc.). The workaround is to delete the logfiles.

104927 — Switching index modes causes error fromIA jsp page

The Index Agent jsp page caused an internal server error when the migration mode wasswitched to normal mode against an upgraded AIX/DB2 repository.

105039 — Electronic signature (esignature) failure

The esignature functionality is broken. Error message is:DM_SYSOBJECT_E_ESIGN_SIGNATURE_METHOD_FAILED "Method ’esign_pdf’ failed. Arguments: "testenv" "tuser2" "object_id" "/export/pug1/irina/dctm/share/temp/addesignature/dm_esign_1007720_0900385780004b90_49



105082 — Indexing content stored on NAS devices

Attempts to index content stored on NAS devices may generate the following error:DocumentRetriever :ERROR Retrieval error: Couldn’t open file <file path/name> ERROR Processor error status: DataNotAvailable Not read permission

This error is recorded in the dmi_queue_item’s message attribute. It may occur when allthe following conditions are met:• Content Server and index server are on different host machines.• The content files are stored on a NAS storage device• The index agent is configured to pull content using GetpathTo resolve this error, edit the <local_mount> element or elements in the IndexAgent.xmlfile that reference the storage area or areas on the NAS device. Add two backslashesimmediately after the opening <local_mount> element. For example, assume thefollowing references a storage are on an NAS device:<local_mount>\\100.2.4.32\share3\c\data_for_example\content_storage_1</local_mount>

After editing, it is now:<local_mount>\\\\100.2.4.32\share3\c\data_for_example\content_storage_1</local_mount>

105111 – Network locations in Portals login page

The Portals login page displays a list of default network locations, but does not mapautomatically to the client’s correct network location.

105181 — Error when installing remote Content Server

On UNIX, you may see the following error while installing a remote Content Server:Failed to connect to docbase repository_name as user user_name

This indicates that the server has attempted to run the headstart script before the serveris completely started. To work around the problem, re-execute the panel.

105197 — Microsoft Word and Excel templates inupgraded repositories

In an upgraded repository, attempting to create a new document from a MicrosoftWord or Excel template throws an error in Word or Excel. This indicates that the



templates are corrupted. New templates exist in the upgraded installation in the$DM_HOME/install/workspace/templates directory. Use Setfile to replace the corruptedtemplates with the new templates.

To install new Word and Excel templates:

1. Start IAPI and connect to the repository.

2. To replace the Word template, type the following commands:retrieve,c,dm_document where object_name = "Blank Word 97 / 2000 Template"setfile,c,l,path_to_template_directory/msw8template.dotsave,c,l

3. To replace the Excel template, type the following commands:retrieve,c,dm_document where object_name = "Blank Excel 97 / 2000 Template"setfile,c,l,path_to_template_directory/excel8template.xltsave,c,l

105219 — Location linking failure for Java lifecyclesin some cases

When a Java lifecycle is attached to a document, the document is not linked to the locationspecified in the Location Expression of a state if the location folder has Korean name.

106055 — Problem with LDAP conguration with SSL

If an ldap config object with SSL enabled is set to server config object, reinit fails onSolaris repositories.

106298 — Retention dates in Centera stores

When a Centera content-addressed store is used, you cannot set a retention date pastthe date January 1, 2038 for content files in the store. This restriction applies to boththe retention date set on the store itself and to retention dates set by Retention PolicyServices, provided that a Centera store is in use. If the retention date is later than January1, 2038, the content files have no retention set.



106820 — Thesaurus on AIX

Thesaurus searching does not work on the AIX operating system.

109155 — Workow promotion failures on WindowsContent Server hosts

When WF_PromoteLifecycle is used for promotion in a workflow instance, the workflowfails.

There are two workarounds:• Install Java on the Content Server host.

Dmbasic will then use the Java you install instead of using the Java installed byContent Server.

• Set the PATH environment variable to include the correct directories:cmd>setenv PATH "$PATH;C:\Program Files\Documentum\jre\142_04\bin\client"

LimitationsThis section describes limits on the usability of current functionality. The limitationsmay be part of the product design or may result from issues with associated third-partyproducts. The following topics are included:• Viewing the index agent log file, page 36• Error indexing text or XML files, page 37• Createaudit API limitation, page 37

Viewing the index agent log le

If you are using a browser on the Windows 2000 platform to view the index agent log filefrom the Index Agent Admin Tool, you must click Open twice to see the log file.



Error indexing text or XML les

The following error when indexing a text or XML file indicates that the mime_typeattribute in the format object is not set correctly:ERROR DocumentException: EXOpenExport() failed: no filter available for this file

To resolve the error, set the format’s mime_type attribute to:text/plain

Createaudit API limitation

The Createaudit method, used to create audit trail entries for custom events, currentlydoes not record attribute values in the audit trail entry’s attribute_list attribute. To workaround this issue, you can use the Create, Set, and Save API methods to create the audittrail entry.

If the total length of the attribute names and values that you want to record is greaterthan the size of the attribute_list attribute, use Create, Set, and Save to also create admi_audittrail_attrs object to store the overflow. If you require an audittrail attrs objectfor the overflow, you must create and save that before you save the audittrail object.

Here is the sequence of actions needed:API>create,c,dm_audittrail...<audittrail_obj_id>API>set,c,l,attribute_listSET>’attr1=value’,...’attr14=value’...OKAPI>Create,c,dmi_audittrail_attrs...<audittrail_attrs_obj_id>API>set,c,<audittrail_attrs_obj_id>,attribute_listSET>’attr15=value’,’attr16=value’...OKAPI>set,c,<audittrail_attrs_obj_id>,audit_obj_idSET><audittrail_obj_id>...OKAPI>save,c,<audittrail_attrs_obj_id>...OKAPI>set,c,<audittrail_obj_id>,attribute_list_idSET><audittrail_attrs_obj_id>...OKAPI>save,c,<audittrail_obj_id>



Failover to ACS limitation (bug 105202)

If the Webtop application is running in HTTP mode and a connection attempt to an ACSserver fails, the application cannot failover to connect to another ACS server.


Chapter 6Technical Notes

This section provides configuration and usability notes for current product features. The followingsubsections are included:• Installation notes, page 39• Configuration Notes, page 48• Usability Notes, page 60

Installation notesThis section contains information about installation requirements and installationprocedures that supplements the information in Content Server Installation Guide. Thefollowing additional information is presented:• Platform-independent installation and upgrade notes, page 40, including

— Full release, page 40

— Installation manual, page 41

— Content Server upgrade paths, page 41

— Content Server and index server on the same host, page 41

— Installing remotely, page 41

— Upgrading DFC, page 41

— Workaround if repository upgrade fails while executing the BPM installationscript, page 42

— Default settings in docbase config may affect client access, page 43

— Resolving type cache problems on clients after upgrade, page 43

— Moving repositories across platforms and the AEK.key file, page 44


Technical Notes

— Setting the server_os_codepage and client_codepage on the Japanese ContentServer, page 44

— The database_refresh_interval Key, page 44• Windows-specific installation notes and issues, page 44, including

— Windows installation owner account, page 44

— Installing the Korean data dictionary information on Japanese Windows, page 45

— Upgrading distributed configurations, page 45• Installation issues for all UNIX platforms, page 45

— Change for Tomcat application server startup, page 45

— New command line for launching repository configuration, page 46

— _s entry in the Service Names file, page 46• Installation issues specific to AIX, page 46

— Upgrading on AIX with DB2, page 46

— C++ runtime library version, page 46

— AIX host requirement, page 46• Installation issues specific to HP-UX, page 47

— Installing on HP-UX when the device name for the temp directory is longer than15 characters, page 47

• Environment variables (UNIX and Linux), page 47• Installation issues specific to Sybase, page 47

— Repository upgrade may hang on Sybase platforms, page 47

Platform-independent installation and upgrade notes

The items in this section apply to all host platforms.

Full release

Content Server 5.3 SP1 is a full release that can be used to create new installations.Content Server 5.3 SP1 does not need to be applied to an existing 5.3 installation.


Technical Notes

Installation manual

Use the version of the Content Server Installation Guide dated September, 2005. It containsthe most recent information on installing Content Server.

Content Server upgrade paths

For information on supported upgrade paths, refer to the Content Server Installation Guide.

Content Server and index server on the same host

If the Content Server and index server are installed on the same host, the values in thehardware requirements tables for the two components must be added together. Forexample, the Content Server requires a minimum of 512 MB of RAM and the indexserver requires a minimum of 2 GB of RAM. If they are installed on the same host, aminimum of 2.5 GB of RAM is required.

Installing remotely

Displaying the installer remotely across platforms is not supported. For example,remotely displaying from Solaris to Solaris usually works, but Solaris to an HP UXServer or Exceed is not supported.

Upgrading DFC

Upgrading DFC from the version installed by a particular Content Server version isnot supported.

Upgrading a repository congured for Documentum Client forOutlook

Upgrading a repository configured for Documentum Client for Outlook (DCO) failswhen the data dictionary population script runs. To avoid this problem, you must use anew version of the headstart.ebs script, not the version distributed with the full ContentServer 5.3 SP1 installation package.


Technical Notes

To install Content Server 5.3 SP1 with the updated headstart.ebs script:

1. Obtain the new headstart.ebs script from the Technical Support web site and saveit to a temporary location on the Content Server host.The script is attached to Support Note 44393.

2. Install the Content Server software using the standard installation package.

3. Copy the new headstart.ebs script from the temporary location to$DOCUMENTUM/product/5.3/install/admin/ (UNIX and Linux) or%DOCUMENTUM%\product\5.3\install\admin (Windows) on the Content Serverhost.If you have multiple repositories in the same software installation, you only needto replace headstart.ebs in this location. The same scripts are used to upgrade eachrepository.

4. Run the Content Server configuration program.

Workaround if repository upgrade fails while executing the BPMinstallation script

Use the following workaround if the upgrade for a repository fails while executing theBPM Queue Management Support script and the error is:Folder ’Queue Management’ already existsCreate folder ’Work Queue Categories’[DM_QUERY_E_UP_BAD_FOLDER]error: "You have specified aninvalid folder path, /System/Queue/Management, in your LINK or MOVE TO clause."

To work around the error:

1. Open the dm_bpm_install.ebs script in a text editor.The script is found in %D_HOME%\install\admin ($DM_HOME/install/admin).

2. Replace the following line:ObjectID = dmAPIGet("retrieve,c,dm_folder where object_name=’" &FolderName & "’")

withObjectID = dmAPIGet("retrieve,c,dm_folder where object_name=’" &FolderName & "’ and FOLDER(’" & ParentFolder & "’)")

3. Save the change.

4. On the installation dialog box, check the “Retry the failed script box”.

5. Click Next to continue.


Technical Notes

Default settings in docbase cong may affect client access

If you install or upgrade Content Server with either a Collaborative Services license or aRetention Policy Services license, the procedure sets:• dm_docbase_config.oldest_client_version attribute to 5.3• dm_docbase_config.check_client_version attribute to TThese settings mean that Content Server will accept connection requests fromDocumentum client applications only if the applications are at or above the 5.3 versionlevel.

The oldest_client_version attribute identifies the lowest version level of a Documentumclient that is expected to connect to the repository. This value is used by the DFC todetermine which XML chunking algorithm to use for XML content when the content issaved to the repository. (Refer to The oldest_client_version attribute, page 51 for moreinformation about this.) It is also used in conjunction with the check_client_versionattribute setting to control access to the repository in general.

When check_client_version is T, Content Server checks the value in oldest_client_versionand does not accept connection requests from Documentum client applications olderthan the version specified in oldest_client_version.

Caution: You can change the settings. However, allowing users to connect from pre-5.3clients will allow users to bypass the retention controls enforced by Retention PolicyServices (RPS) if you have RPS enabled and retention policies defined and assigned toobjects. Additionally, pre-5.3 clients will not recognize the access controls imposed byrooms (a feature of Collaboration Services).

Resolving type cache problems on clients after upgrade

When users start a client such as Desktop Client or Webtop, the DMCL is initialized andstarted. As part of that process, the DMCL creates a client-side type cache. The cache isheld as long as the DMCL continues to run. The DMCL continues to run while the user isconnected. Even if a user’s repository session (in Desktop Client or Webtop) times out orthe user disconnects from the repository, the DMCL continues—it does not stop.

If a repository upgrade occurs while the DMCL is running, the client-side type cachebecomes inconsistent with the repository. Users will receive errors when they attempt toaccess the repository after the upgrade.

To resolve this issue, after the repository is upgraded, users on Windows client hostsmust log out of Windows and application servers must be rebooted.


Technical Notes

Moving repositories across platforms and the AEK.key le

Bug number 67875 has been fixed. An AEK.key file created in one platform, such asWindows, can be used on a UNIX platform and an AEK.key file created on a UNIXplatform can be used on a Windows platforms. This now makes it possible to move arepository between platforms without AEK errors.

Setting the server_os_codepage and client_codepage on theJapanese Content Server

In the Japanese environment, some jobs and methods do not run correctly if theserver_os_codepage attribute of the server config object and the client_codepage keyof the dmcl.ini file are set differently. When you install the server in the Japaneseenvironment, ensure that client_codepage in the dmcl.ini file on the server host is set tothe same code page as the server_os_codepage server config attribute.

The database_refresh_interval Key

During server installation or upgrade, the change checker process runs once per minuteby default. The process updates type caches as types are created or altered.

If you are upgrading, ensure that the database_refresh_interval key is set to 1 minute orremove it from the server.ini file.

Windows-specic installation notes and issues

This section contains information specific to the Windows platform.

Windows installation owner account

OnWindows, user accounts are not case-sensitive, but Content Server installation fails ifyou connect to the host using the incorrect case in the user name. For example, if theaccount is set up as JPSmith and you connect as jpsmith, you can log in to the host, butserver installation fails.


Technical Notes

Installing the Korean data dictionary information on JapaneseWindows

When you are installing Content Server on a Windows machine in the Japanese locale,automatically installing the data dictionary information for the Korean locale does notfunction properly.

To install the Korean locale, you must run the data dictionary population scriptfrom a remote client which is running on Korean Windows. The script is found in%DM_HOME%\bin. The command line to execute the script is:dmbasic -fdd_population.ebs -eLoadDataDictionary --docbase_name docbase_owner owner_passworddata_dictionary_ko.txt

Upgrading distributed congurations

If you are upgrading a distributed configuration on Windows, do not reboot the remotehosts using Terminal Services. Reboot the remote hosts directly from those hosts.

Installation issues for all UNIX platforms

This section contains installation information for all UNIX platforms.

Change for Tomcat application server startup

When Tomcat application server is started on a UNIX platform, it now passes thefollowing to Java:-Djava.libary.path=$DOCUMENTUM_SHARED/dfc

This change means that any user-defined value in:• LIBPATH on AIX• SHLIB_PATH on HP-UX• LD_LIBRARY_PATH on Solaris or Linuxwill not be used by Tomcat for Java methods or by the ACS server. If yourequire that directories other than $DOCUMENTUM_SHARED/dfc be searchedwhen loading native code shared libraries, it is now necessary to edit the file$DM_HOME/tomcat/bin/setenv.sh.


Technical Notes

New command line for launching repository conguration

The command line that starts repository configuration program has changed from priorreleases. Refer to the Content Server Installation Guide for the new command line.

_s entry in the Service Names le

With this release, SSL communications are no longer controlled by the Trusted ContentServices license. Because of this change, an <service_name>_s entry in the etc/services fileis now required for all repositories. For information about setting up this service entry,refer to the Content Server Installation Guide.

Installation issues specic to AIX

This section contains information specific to the AIX platform.

Upgrading on AIX with DB2

If you are on Content Server 5.2.5 or any 5.2.5 Service Pack version of the server and thedatabase is DB2 8.1.5, use the following upgrade order:

1. Upgrade Content Server to 5.3 SP1.

2. Upgrade DB2 to version 8.1 FixPak 7a.

C++ runtime library version

If you are installing Content Server on an AIX host, version 6.0 of the C++ runtime librarymust be installed on the AIX host.

AIX host requirement

With this release, there is no longer a requirement for AIX to be in 32-bit mode. (TheContent Server Installation Guide released in March, 2005, incorrectly lists 32-bit mode as arequirement for Content Server on AIX.)


Technical Notes

Installation issues specic to HP-UX

This section contains information specific to sites running on the HP-UX operatingsystem.

Installing on HP-UX when the device name for the temp directory islonger than 15 characters

InstallShield cannot reliably install on HP-UX when the device name for the tempdirectory is longer than 15 characters. To work around this problem, start the installerusing the is:tempdir flag and point the installer to a temp directory on a device thathas a shorter path. The syntax is:installer_name -is:tempdir new_directory_namewhere installer_name is the name of the installer executable and new_directory_name is thetemp directory you have chosen. For example:serverHPUXSuiteSetup.bin -is:tempdir /export/plecomet1/mydir

Environment variables (UNIX and Linux)

In prior releases, all required environment variables were set manually on the UNIXplatforms. With this release, all the required variables, with five exceptions, are set bya script during installation. However, there is a bug in the process that occurs whenyou are upgrading an existing repository. For information about which variables areset, which must be set manually, and a workaround for the upgrade bug, refer to theContent Server Installation Guide, in the section titled “Upgrading the Connection Broker,the Server, and the Repository”.

Installation issues specic to Sybase

This section contains information specific to sites running on the Sybase RDBMS.

Repository upgrade may hang on Sybase platforms

On Sybase platforms, upgrading a repository may hang if the database transactionlog is too small. When the repository is upgraded, it opens a long-running transaction


Technical Notes

while the upgrade script is running. If the transaction log is too small, the transactionhangs with locked system tables because the database server cannot write information tothe transaction log.

If you encounter this problem, perform the following procedure. After you complete theprocedure, the repository upgrade procedure should be able to continue.

To continue with an upgrade on the Sybase platform:

1. Issue the following command on the Sybase database:sp_dboption db_name,’trunc log on chkpt’,true

where db_name is the name of the database created for the Documentum repository.

2. Issue a checkpoint command to truncate the transaction log.

3. If steps 1 and 2 fail to resolve the problem and allow the upgrade to proceed, increasethe transaction log space.

Conguration NotesThis section contains information about the configuration of your installation. Thefollowing topics are included:• Content Storage Services license requirement, page 49• DNS requirement for web-based client hosts in distributed environment, page 49• Apache Tomcat application server, page 49• Content Server failover change, page 49• Index needed for Retention Policy Services, page 50• New user authentication attributes, page 50• Host machine requirements for Surrogate Get and content replication, page 50• The vpd.properties File , page 50• New directories in installation , page 51• The oldest_client_version attribute, page 51• Surrogate Get change, page 51• DMCL exception handling on UNIX platforms, page 52• Storage policy updates, page 54• Setting default_app_permit in docbase config , page 54• Changes to the dm_event_sender script arguments, page 54• Job trace files, page 55• Content-addressed storage notes, page 55• Note regarding the Shutdown method and Windows platforms, page 57


Technical Notes

• Updating the federation methods, page 57• Updating the federation methods, page 57• Migrating to Documentum Content Services for EMC Centera (CSEC) 5.3 from CSEC

1.2c or Prior, page 57• Auditing content migration in lifecycle actions, page 60

Content Storage Services license requirement

A Content Storage Services license is required to use the content duplication checkingand prevention feature.

DNS requirement for web-based client hosts indistributed environment

In a configuration that includes ACS or BOCS servers, the machines hosting the Webbrowsers must be able to resolve the base URLs defined for the ACS or BOCS serversusing DNS. (The base URLs for the servers are recorded in the acs config object for theserver and are defined through Documentum Administrator.) This means that the clienthosts must have access to DNS entries for the ACS and BOCS server machines.

Apache Tomcat application server

Apache Tomcat, installed with Content Server, is required by EMC DocumentumContent Server. It supports a variety of features and licenses in the server. Use of analternative application server, instead of Apache Tomcat, is not supported.

The Tomcat instance must be running in order to run the LDAP Synchronization joband the ACS server.

Content Server failover change

Starting with Release 5.3 SP1, repository sessions cannot fail over to Content Servers withproximity values 9000 or greater.


Technical Notes

Index needed for Retention Policy Services

If you are installing Retention Policy Services (an optional product license), you mustcreate an index on the i_retainer_id attribute of the dm_sysobject object type. This indexis required for proper functioning of Retention Policy Services. Use the MAKE_INDEXadministration method to create the index. Executing it through the API Apply method,the syntax is:apply,c,NULL,MAKE_INDEX,TYPE_NAME,S,dm_sysobject,ATTRIBUTE,S,i_retainer_id

New user authentication attributes

Release 5.3 added new attributes to user objects that are now used in place of theprevious attributes user_os_name and user_os_domain. The new attributes areuser_login_name and user_domain_name. For information about these attributes andtheir use in user authentication, refer to the Content Server Administrator’s Guide.

Host machine requirements for Surrogate Get andcontent replication

The methods invoked by the surrogate get feature and content replication now use globallogin tickets to connect to the target repositories. That generated ticket is valid for fiveminutes. To ensure that surrogate get and content replication jobs work properly usingthe ticket, the host machine on which the method runs and the host machine of the targetContent Server must both be using UTC time and the clocks must be synchronized.

The vpd.properties File

On UNIX hosts, the installer creates a file called vpd.properties in the installationowner’s home directory. The vpd.properties file contains information on which productsthe user has installed. The vpd.properties file is critical to the successful operation ofDocumentum software. Do not edit or remove this file unless instructed to do so byDocumentum Technical Support.


Technical Notes

New directories in installation

The following directories are added to the directory structure of a basic Content Serverinstallation.

New directory for full-text

A basic Content Server 5.3 installation now includes the following directorynot found in the directory structure of previous releases. This directory is%DOCUMENTUM%\fulltext ($DOCUMENTUM/fulltext).

New directory for language les (Oracle Only)

A basic Content Server 5.3 installation contains an additional directory not found inthe directory structure of previous releases. This directory is %DM_HOME%\Oracle($DM_HOME/Oracle). This directory will contain the language files needed by Oracle.During installation, the environment variable, ORA_NLS33 is set to that location. Do notremove that directory or reset that variable.

The oldest_client_version attribute

In release 5.x, the DFC handles XML chunks internally in a new manner. To use this newimplementation, all Documentum clients must be at the 5.x level.

To determine whether to use the new or old implementation, the DFC is using a newattribute in the docbase config object. The attribute is called oldest_client_version(string32). It identifies the oldest Documentum client version that is accessing theDocbase. The attribute should be set manually after you update the Docbase.

If it is not set or is not set to 5.x, the DFC assumes that the Docbase cannot use the newimplementation.

Surrogate Get change

The dm_SurrogateGet method is reconfigured to use the dmbasic method server if thatserver is running. (If the dmbasic method server is not enabled, dm_SurrogateGet is runby Content Server.) Because the method is running in the dmbasic method server, it


Technical Notes

now writes information on each content file it retrieves into the method server log file.The messages are pre-pended with identifying information to distinguish them frommessages written by other methods.

DMCL exception handling on UNIX platformsNote: Release 5.2.5 introduced the DMCL exception handling feature. In that release,it was supported only on Windows platforms because its behavior on UNIX platformshad not been fully investigated. For 5.2.5 SP1, after further investigation, support wasextended to UNIX platforms, with the exception of Linux. The DMCL excepton handlingfeature is not supported on Linux. (No new source code was introduced for UNIXsupport.)

Release 5.2.5 SP1 added supports for DMCL exception handling on UNIX platforms,with the exception of Linux. The feature is supported by three attributes:• terminate_on_exception• exception_count• exception_count_intervalFor general instructions on setting these attributes to enable the feature, refer to thesection “Configuring DMCL Exception Handling” in Chapter 6, Clients and Sessions, ofthe Content Server Administrator’s Guide.

Heap corruption and continue on exception

On UNIX platforms, the DMCL data structures are in the global process heap.Consequently, there is no way to validate the DMCL after an exception. Therefore, onUNIX, the DMCL is always allowed to continue on exception. Typically, if this happens,the DMCL encounters more exceptions and terminates after some number of exceptions.(The actual number depends on how the exception_count and exception_count_intervalattributes are set. Refer to the System Administrator’s Guide for information about thoseattributes.)

DMCL stack trace les

When a DMCL exception occurs, a description of the exception and a DMCL stacktrace is written to a file. The file is named dmcl_err_pidpid_number_date_time.txt (Forinformation about the format of the name and where the file is stored, refer to thedocumentation in the Content Server Administrator’s Guide.)


Technical Notes

On some UNIX platforms, additional configuration, not described in the Content ServerAdministrator’s Guide, is required to obtain the stack trace. Those platforms are:• Solaris 9• Solaris 8• AIX 5.2 or 5.3The following sections describe how to obtain DMCL stack traces on those platforms.

Obtaining a DMCL stack trace on Solaris 9

On Solaris 9, a DMCL stack trace is not included in the error report filegenerated by the DMCL by default. To include a stack trace, set theDM_ENABLE_DMCL_STACK_TRACING environment variable to 1 in the applicationserver environment:DM_ENABLE_DMCL_STACK_TRACING=1

Obtaining a DMCL stack trace on Solaris 8

On Solaris 8, you cannot include a stack trace in the file that contains the exceptiondescription. Use the following procedure to obtain a stack trace on Solaris 8.

To obtain a stack trace on Solaris 8:

1. Set the following environment variable to 1 in the application server environment:DISABLE_DMCL_EXCEPTION_HANDLING=1

2. Reproduce the problem.

3. Run the UNIX command pstack on the resulting core file, redirecting the outputto a file.For example:pstack core > core.out

The stack trace is recorded in the file (core.out in the example).

Obtaining a DMCL stack trace on AIX 5.2 or 5.3

On AIX 5.2 or 5.3, a DMCL stack trace is not included in the error report file generated bythe DMCL by default. To produce a stack trace in that file, use the following procedure.

To produce a stack trace on AIX 5.2 or 5.3:

1. Install the patch APAR IY53004.


Technical Notes

2. Set the DM_ENABLE_DMCL_STACK_TRACING environment variable to 1 in theapplication server environment:DM_ENABLE_DMCL_STACK_TRACING=1

Storage policy updates

The DFC maintains a cache of storage policy information. The cache is updatedat intervals defined by the dfc.storagepolicy.validation.interval property in thedfc.properties file. The default interval is 5 seconds. You can reset the interval.

If you increase the interval, then it takes longer for policy changes to be recognizedby the storage policy engine in the DFC. If you decrease the interval, changes may beavailable for use sooner but performance may be degraded.

For information about the location of the dfc.properties file and how to set properties,refer to the DFC Release Notes for 5.3.

Setting default_app_permit in docbase cong

The lowest permit to which the default_app_permit attribute in the docbase config nowmay be set is Browse. Prior to release 5.2.5 SP3, the lowest acceptable setting was None.

Installing 5.3 does not reset this attribute if it is set, even if it is set to None. Nor is anerror or warning generated.

Note: A None setting does not prevent users from viewing the object when the objectis selected using DQL. The lowest level that can be enforced when using DQL to selectobjects is Browse.

Changes to the dm_event_sender script arguments

The order of the arguments in the dm_event_sender script has changed. If you havecustomized this script, you must move the customizations to the new script. Donot use the older version. Using the older version will result in the removal of thedm_mailwrapper.sh file after the first execution because the temp_file_name$ argumentis now in the position formerly occupied by the mailScript$ argument.


Technical Notes

Job trace les

Typically, each system administration job generates an individual trace file. However, ifthe dmcl.ini file used by the Content Server executing a job has the trace_file key set, thetracing information generated by the job is recorded in the location defined by that key.When that occurs, Documentum Administrator cannot display the trace file for the job.

Note: Content Server uses the dmcl.ini file found in %DOCUMENTUM%($DOCUMENTUM) on the server’s host machine.

Content-addressed storage notes

The following notes address configuration and usability items for content-addressedstorage areas.

Storage location of ca store plug-ins

The content of dm_plugin objects created for ca store plug-ins must be assigned to a filestore storage area. The storage area can be encrypted. Do not store such content ina ca store storage area.

Required permissions on Centera host

If the connection string specified in dm_ca_store.a_storage_params[0] specifies a Centeraprofile as part of the string, the Centera permissions assigned to the profile must be:• read• write• delete• existsIf there is no profile specified in the connection string, the connection to the Centera hostuses the anonymous profile. In such cases, the anonymous profile must also have theCentera read, write, delete, and exists permissions.

The profile used by a connection that is requesting a privileged delete must haveprivileged delete permissions.

To ensure that security is maintained, do not give other applications any permissions tothe Centera pool that Documentum Content Server uses.


Technical Notes

Setting clocks and time zones for Centera hosts and ContentServer hosts

The actual retention date stored in the Centera host for a content file is calculated usingthe clock on the Centera host machine. Consequently, to ensure calculation of correctretention periods, the time zone information and the internal clocks on Centera hostmachines and Content Server host machines must be set to matching times (within thecontext of their respective time zones). For example, if the Content Server host is inCalifornia and the Centera host machine is in New York, when Content Server’s time is1:00 p.m. PST, the time on the Centera host should read 4:00 p.m. EST.

Failure to synchronize the times may result in incorrect retention dates for the storedcontent.

Specifying multiple Centera IP addresses in ca store objects

When a ca store is created for a Centera storage system, index position 0 of thea_storage_params attribute is set to the IP address of the Centera node. With CenteraSDK 2.1 (packaged and installed with Content Server), a_storage_params[0] can containa comma-separated list of IP addresses, each representing a Centera node. When thatlist is passed to the appropriate SDK function, the SDK connects to the first availableCentera node in the list.

Setle, Setcontent, and Removerendition changes

The behavior of the Setfile and Setcontent methods was changed in release 5.2.5 SP3.Previously, a user or application could execute these methods against an existingdocument in a content-addressed storage area to replace a current page in thedocument without checking out the document. That is no longer true. A document in acontent-addressed storage area must be checked out before executing either method toreplace an existing content page.

Similarly, you must now check out a document to execute a Removerendition method toremove a rendition of the document that is stored in a content-addressed storage area.


Technical Notes

Note regarding the Shutdown method and Windowsplatforms

On Windows platforms, the Shutdown method does not use the Window servicemanager to shutdown the server. Consequently, all of the associated processes may notbe shut down appropriately. Therefore, on Windows platforms, it is recommendedthat you shut down a server through the Windows service manager rather than usingthe Shutdown method.

Updating the federation methods

If you have a federation whose members are a mixture of Docbase versions, including5.2.5, 5.2.5 SP1, 5.2.5 SP2, 5.2.5 SP3, 5.3, and versions prior to 5.2, you must update themethod_verb attribute for the following federation methods in those Docbases in thefederation that have a version of 5.2 or earlier:• dm_ldif_import• dm_ldif_export• dm_ldif_copy• dm_ldif_statusSet the method_verb attribute to:java dm_ldif_import

Note: It is not necessary to update the method_verb attribute for the methods inDocbases with versions of 5.2.5 SP1, 5.2.5 SP2, 5.2.5 SP3, or 5.3.

Migrating to Documentum Content Services for EMCCentera (CSEC) 5.3 from CSEC 1.2c or Prior

Use the procedures and information in this section to migrate objects stored in aCentera storage system using Content Services for EMC Centera version 1.2c or prior toDocumentum Content Services for EMC Centera version 5.3 SP1. If you are currentlyusing CSEC versions 5.2.5, 5.2.5 SP1, 5.2.5 SP2, 5.2.5 SP3, or 5.3, migration is notnecessary—ignore this section.

Caution: Performing the migration procedure described here does not remove the priorversion of CSEC. It is strongly suggested that you do not continue to use the old versionto store content in the Centera storage system after migrating to CSEC 5.3 SP1. If youdo, you must re-run the migration and full-text scripts to migrate and index any content


Technical Notes

stored using the old version, as that content cannot be handled using CSEC 5.3. Toensure that content is not archived using the older version of CSEC, stop the CSECArchiver that is part of the older product.

What migration does

Migrating to CSEC 5.3 SP1 does not actually move any content. The migration simplyupdates the dmr_content objects and the SysObjects that contain that content to reflectthe implementation of CSEC for 5.3 SP1.

All the operations performed during migration are performed within a single transaction.The transaction is committed if all operations succeed or aborted if any operation fails.

For each content object to be migrated, the migration operation

1. Retrieves the r_object_id and set_file attribute values of the content object.

2. Uses the set_file attribute value to create a relative path to the content.

The Documentum CSEC 5.3 SP1 plug-in uses the relative content path to access thecontent.

3. Updates the dmr_content object.

The i_contents attribute is set to the relative content path, the storage_id attribute isset to the object ID of the CA storage area, and the data_ticket attribute is set to 1.

4. Determines which SysObject objects have that content as page zero and, for thosemeeting that criteria, sets the a_storage_type attribute to the name of the CA storeobject and increments the i_vstamp attribute.

The SysObjects are checked out prior to updating and unlocked after being updated.

Migrating the objects

Documentum provides a script to migrate objects from CSEC 1.2c or priorto CSEC 5.3 SP1. The script is dm_migrate_to_ca_store.ebs. It is found in%DM_HOME%\install\admin ($DM_HOME/install/admin).

You can migrate all objects with content in a particular storage area at once or you canmigrate them in batches. If you want to migrate in batches, set the constant MaxMigratein the dm_migrate_to_ca_store.ebs script before running the script. By default, theconstant is set to 2147483647, which effectively means “migrate all objects”. The defaultentry in the script looks like this:Const MaxMigrate As Long = 2147483647


Technical Notes

Use a text editor to set the constant to any positive integer to migrate only that number ofobjects when the script is executed. For example, suppose you set the constant as follows:Const MaxMigrate As Long = 1000

When the script runs, only 1000 content objects are migrated.

To migrate objects to CSEC 5.3 SP1:

1. Create a ca store storage area for the migrated objects.Use Documentum Administrator to create the storage area. Refer to the online helpif needed.

2. Run the dm_migrate_to_ca_store.ebs script.The syntax for the script is:dmbasic -f dm_migrate_to_ca_store.ebs -pdocbasenameusername password current_storage_name ca_store nametrace_level -eEntryMigrate|EntryReport

Note: You can direct the output of the script to a text file. To do so, append thefilename to the end of the command line using the following format:>filename.txt

Table 6–1, page 59, describes the script arguments.

Table 6-1. dm_migrate_to_ca_store.ebs Arguments

Argument Description

docbasename Name of the Docbase that contains the storage areas.

username User name used by the script to connect to theDocbase. This is the user’s user_os_name value. Thismust be the Docbase owner.

password Password for the user account identified in username

current_storage_name Storage name of the storage used by CSEC 1.2c (orprior)

(The default name for this storage area is typicallydm_safe_store.)

ca_store_name Name of the CA store storage area. This is the CAstore object’s object_name.


Technical Notes

Argument Description

trace_level This argument is optional. Valid values are 0 (notracing) to 10. The default is 0.

EntryMigrateorEntryReport

EntryMigrate performs the migration operations.

EntryReport generates a report listing the objects thatwould be migrated, but does not actually performthe migration.

If you turn on tracing for the method, the trace file is named dm_migrate_to_ca_store_trace.out and is stored n the current working directory.

Auditing content migration in lifecycle actions

In release 5.2.5 SP3, the DfChangeStorageAction lifecycle function was changed. Thefunction now moves primary content by resetting the a_storage_type attribute andmoves renditions by calling MIGRATE_CONTENT. Consequently, if you are auditingcontent movement (the dm_move_content event) for a particular document, the audittrail is only generated for any renditions moved when the move is a result of anexecution of DfChangeStorageAction.

Usability NotesThis section contains miscellaneous items regarding the use and usability of the product.The following topics are included:• String datatype maximum length on SQL Server, page 61• Dmbasic lifecycles and Retention Policy Services, page 61• DQL hints and FTDQL queries, page 61• Remote hosts failed or ACS not available messages, page 61• Workaround for bug 81615, page 61• WORKFLOW_AGENT_DIED error, page 62• Tracing default for surrogate get is changed, page 62• Supported versions in repository federations, page 62• Java method server, page 63• Printing from lifecycle programs, page 63• Indexable formats, page 63• Indexable formats, page 63


Technical Notes

• File store mapping for full-text indexing on NAS devices, page 64• Index agent warning message, page 64

String datatype maximum length on SQL Server

For a repository installed on a SQL Server database, the maximum length of the stringattribute is 4000 characters. (The Documentum Object Reference incorrectly documents themaximum length for SQL Server as 7000.)

Dmbasic lifecycles and Retention Policy Services

If a lifecycle is written in dmbasic and an object is attached to the lifecycle, a retentionpolicy cannot be assigned to that object. This is because lifecycles written in dmbasicbypass DFC and BOF, as well as BOF customizations, and are processed directly bythe DMCL API. Retention policies are enforced by DFC and BOF. It is recommendedthat you write lifecycles in Java.

DQL hints and FTDQL queries

With the exception of ROW_BASED, all DQL hints may be used within an FTDQL query.The ROW_BASED hint may not be used within an FTDQL query.

Remote hosts failed or ACS not available messages

If the acs log file contains a “Remote Hosts Failed” or “ACS not available” message,the cause is likely one of the following:• The ACS server is not running.• The file the user requested cannot be retrieved from the storage area• One of the repositories configured in the acs.properties file is down.

Workaround for bug 81615

When a work item generated from an activity that has its performer set to “All Users in aGroup” is completed, the remote_pending attribute of the associated dmi_queue_item is


Technical Notes

left set to T. (It should be set to F at that point.) As a result, the QueueMgt administrationjob does not remove those queue items.

The QueueMgt administration job is responsible for removing old and unneeded queueitems from the repository. The job does not remove queue item objects that haveremote_pending set to T.

The remote_pending attribute designates which queue items need to be copied to aremote repository. In this case, when the work items are first generated, the attributeis set to T so that any users in the group whose home repository is a remote repositoryreceive the task. The dm_DistOperations job is responsible for generating those remotequeue items, based on the setting of the remote_pending attribute.

To work around this bug, you can create a job sequence, run dm_DistOperations beforerunning dm_QueueMgt. The dm_DistOperations job will reset the remote_pendingflag to F.

WORKFLOW_AGENT_DIED error

When a Content Server is started, the procedure may log the following error:[DM_WORKFLOW_W_AGENT_DIED]

This error means that the workflow agent stopped and was restarted during the serverstartup process. So long as the agent is running after the Content Server is started andrunning, you can ignore this error in the log.

Tracing default for surrogate get is changed

Tracing surrogate get operations is now turned off by default. Instructions for turning iton are found in the Documentum Distributed Configuration Guide.

Supported versions in repository federations

For release 5.3 SP1, a federation can contain any mix of 5.1 and higher repositories.However, if the governing repository is a 5.3 or 5.3 SP1 repository, keep in mind thefollowing caveats:• Prior releases do not support dynamic groups. Consequently, any dynamic groups

defined in the governing repository are propagated to any pre-5.3 members asstandard, non-dynamic groups.


Technical Notes

• Similarly, prior releases do not support access restricting (AccessRestriction,ExtentendRestriction) entries in ACLs. If the federation’s federation mode isreplicating ACLs with those kinds of entries to pre-5.3 member repositories, theentries are ignored by pre-5.3 Content Servers.

• The restricted_folder_ids attribute for users (introduced in release 5.3) is a localattribute. This means that any restricted users in the governing repository arepropagated as unrestricted users in the member repositories. (If the member is a 5.3repository, you can set that attribute locally if desired.)

Java method server

Caution: The Content Server installation program installs and configures an instanceof Apache Tomcat as the Java method server and to run the ACS server. Do not usethis Tomcat instance for any other purpose, including running Documentum WDKapplications such as Documentum Administrator or Webtop.

Additionally, the Tomcat application server is currently the only application serversupported for use with Documentum Content Server. No other application server canbe used.

Printing from lifecycle programs

If you issue a print statement in a program executed as entry criteria, action-on-entry,or post-entry action, you must direct the statement’s output to a file. If you do not,the print statements go nowhere.

Indexable formats

Format objects in the repository define which file formats Content Server recognizes.These format objects also identify which formats are indexable (through the can_indexattribute). However, the format objects often represent multiple versions of the sameformat. For example, the format object for the MS Word format may represent multipleversions of MSWord. In some instances, not all versions of the format can be indexed. Fora list of indexable formats and versions, refer to the Content Server Administrator’s Guide.


Technical Notes

File store mapping for full-text indexing on NAS devices

If you are mapping file stores and your full-text index is on a NAS device, use fourslashes (////) in the indexagent.xml file.

Index agent warning message

The index agent some displays a warning message “No web server port for statusprovided, logging of status done to debug log.” The message is harmless and can beignored.


Chapter 7Documentation

This section describes the documentation related to this product.

Content Server documentation setThe following document titles comprise the Content Server documentation set:• Content Server Release Notes , version 5.3 SP1• Content Server Installation Guide, version 5.3 SP1• Content Server Full-Text Indexing Installation Guide, version 5.3 SP1• Content Server Fundamentals, version 5.3 SP1• EMC Documentum Object Reference Manual, version 5.3 SP1• Content Server API Reference Manual, version 5.3 SP1• Content Server DQL Reference Manual, version 5.3 SP1• Content Server Administrator’s Guide, version 5.3 SP1• EMC Documentum Distributed Configuration Guide, version 5.3 SP1• Content Server Combined IndexThe PDFs of the Content Server Fundamentals, the Distributed Configuration Guide , theContent Server Administrator’s Guide, and the reference manuals contain clickable links tothe other manuals. The Content Server Combined Index contains clickable index entriesfor the core manuals. Clicking the links and index entries opens the correct PDF tothe referenced page.

Note that on some systems, the correct PDF opens, but to the first page of the manual,not to the referenced page.


Documentation

Obtaining the correct documentationThe product documentation for each EMC Documentum product is availablefor download from the same page as the software at the Download Center (https://documentum.subscribenet.com). The release notes and any applicable installationguide appear as separately downloadable items. Any product documentation that isavailable from the application as online help does not appear as a separate item; it isautomatically downloaded and installed with the software.

You can also go to CustomerNet to download product documentation, order printeddocumentation, or participate in the technical publications customer survey. Log in toCustomerNet (http://customernet.documentum.com/support) and navigate to SearchSupport → Documentation. To locate product documentation, select the product andversion number on the search page, then click the Search button. To order printedversions or complete the customer survey, click the appropriate link in the upper right ofthe page.

If the documentation you are looking for is not available in printed form from either ofthe above sites, you can purchase it from Nexstra (email: [email protected], phone:866-568-0650).

Documentation corrections and claricationsThis section lists corrections to the product documentation.

Content Server 5.3 SP1 Release Notes, September 2005

The September version of this release note indicated that LDAP and object replication arenot supported on the HP Itanium platform. LDAP and object replication are supportedon the Itanium platform. The September release note was incorrect and those limitationsare removed in the current release note.

Content Server Fundamentals

Content Server Fundamentals is in the process of being refocused on• Providing information about the basic features and behaviors of the Content Server

(rather than “how to” information)• Describing behaviors in terms of the DFC, rather than the DMCL API.


https://documentum.subscribenet.com


Documentation

As part of this refocusing effort, the information about creating workflows using the APIhas been removed, and the workflows and lifecycle chapters are rewritten from thecontext of the user interface products (Workflow Manager, Business Process Manager,and Lifecycle Editor) more typically used to create and manage these features.

The appendix called “Using DQL” has been moved to the DQL Reference Manual.

Content Server Installation Guide

The Content Server Installation Guide contains preinstallation requirements and databaserequirements information for all operating systems and databases, whether the particularplatform has been released or not. The release notes for each Content Server versionindicate which platforms are supported and released.

The September version of the installation guide states on p. 22 and p. 70 that only theEnglish version of each database is supported. This is incorrect. Localized versionsof SQL Server and Oracle are supported.

Content Server Full-Text Indexing Installation Guide

The section on disk space requirements in the Content Server Full-Text Indexing InstallationGuide is updated as follows:

Disk space requirements for indexing and installation

The disk space requirements for full-text indexing and installing the software are asfollows:• Sufficient space to install the indexing software

Refer to the Content Server release notes for this space requirement.• On UNIX and Linux, a minimum of 1GB of free space in the /tmp directory during

installation.• If the index server and full-text index are on the same drive, a minimum of 3 GB

of free space is required on that drive.• If the index server and full-text index are on different drives, a minimum of 3 GB of

free space is required on each drive (6 GB total).• Sufficient space for the full-text index

Depending on the content being indexed, this may vary from approximatelyone-third the space taken up by the content files to several times the amount of


Documentation

space taken up by the content files. For example, 10 GB of content may produce anindex ranging in size from 3 GB to 35 GB.

• Transient space for full-text indexing operations

During the time period when the index server is adding entries to an index, a copyof the index is used for querying operations. After the index entries are added,the updated index is used for querying and the copy is deleted. Before the copy isdeleted, the disk space used by the index may increase by as much as 50% over thedisk space used before the index updates began.

System Migration Guide, Migrating Content Serverchapter

The section titled “Workflow Object Type” is incorrect. The following subsections,Activity Object Type and Workflow Object Type, contain the correct information.

Activity object type

The following two attributes in the object type are deprecated:• pre_timer• post_timerThese attributes are superceded by the pre_timer_increment and post_timer_incrementattributes in the activity object type. In 5.3, pre_timer and post_timer can only be set if auser uses Workflow Manager to create an activity definition. Business Process Managersets the pre_timer_increment and post_timer_increment attributes instead.

When a repository is upgraded, the values in the pre_timer and post_timer activityattributes are multiplied by 60 and the result recorded in pre_timer_increment[0] andpost_timer_increment[0]. (pre_timer and post_timer values are interpreted as hours,while pre_timer_increment[0] and post_timer_increment[0] values are interpreted asminutes.)

Similarly, if a user sets the either deprecated attribute through Workflow Manager, whenthe activity definition is saved, the value is converted to minutes and saved also in thecorresponding 5.3 attribute (pre_timer_increment[0] or post_timer_increment[0]).

Workow object type

The following two attributes of the dm_workflow object type are obsolete:


Documentation

• r_pre_timer• r_post_timerWhen a repository is upgraded, the dm_wfTimer_upgrade.ebs script is executed.This script finds all existing dm_workflow objects that have values for r_pre_timer,r_post_timer, or both and creates timer objects representing those values.

Content Server Administrator’s Guide, Full-TextIndexing chapter

Two sections in the 5.3 SP1 Content Server Administrator’s Guide are obsolete and will beremoved from future versions of the manual:• In the “Format” chapter on page 66, the section called “The topic_transform and

topic_format attributes”

The topic_transform and topic_format attributes apply only to Content Serverversions before 5.3, which used the Verity full-text indexing software.

• In the “Full-Text Indexing” chapter on page 306, the section called “Indexing Contentin Nonindexable Formats”

The section applies only to Content Server versions before 5.3. The correctinformation on indexing content in nonindexable formats is called “How formatobjects determine which renditions are indexed.” It is on page 292.

Content Server Administrator’s Guide, ContentManagement chapter

The content duplication checking and prevention feature requires a Content StorageServices license.

Content Server Administrator’s Guide, ProtectingRepository Objects chapter

In the chapter called Protecting Repository Objects, Table 11–7, Usage of genericattributes in API events, contains incorrect information for the Addrendition andRemoverendition events. The descriptions of these events state that the attributeid_2 stores the object ID of the content object representing the rendition. The correctinformation is that the id_1 attribute records that object ID.


Documentation

Documentum Object Reference ManualThe following items are incorrectly documented in the manual:• Maximum length of the string datatype on SQL Server

The manual currently says the maximum is 7000. The correct value is 4000.• rend_backing_store attribute in dm_server_config object type

The description of this attribute should read “obsolete.”• topic_format and topic_transform attributes in dm_format object type

The descriptions of these attributes should read “obsolete.”• user_password attribute in dm_user object type

The description of the user_password has a typographic error. The literal valueshown as “inline_password” is incorrect. It should be “inline password” (nounderscore).

5.3 FCS Object Reference Manual correctionThe Object Reference Manual published for the 5.3 FCS release of Content Serverincorrectly describes the value stored in dm_user.user_login_domain for LDAP users.The correct description of that value for LDAP users is:

“If the user is an LDAP user, the attribute stores the object name of the LDAP configobject representing the LDAP directory against which the user is authenticated.”

Note: The attribute description is correct in the 5.3 SP1 documentation.

Content Server API Reference ManualThe sections on the Assume and Authenticate API methods are not correct in oneparticular: Windows unified login does not work with the Assume and AuthenticateAPI methods.


Documentation

Content Server DQL Reference ManualThe SELECT statement description fails to note that all DQL hints except ROW_BASEDmay be used within an FTDQL query.


Documentation


Chapter 8Software Media, Organization, and Files

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

Software mediaThis product is available as FTP file downloads from the Documentum productdownload site (SubscribeNet). You should have received instructions through emailregarding how to download products from Documentum’s download site. The URLbelow takes you to the download site login page. If you cannot locate your password,use the password finder at the bottom of the page. Your user name is your email address.

Download Site: https://documentum.subscribenet.com

Review the product versions available for your platform. For technical support, visit theDocumentum Support site at http://support.documentum.com/Support.

If you receive error numbers 5227 or 5504 from the download site, you need to registerfor download access.

To register for download access:

1. Navigate to https://documentum.subscribenet.com.

2. Enter your Documentum technical support login name and password.If you do not know your login name or password you must request access fromDocumentum technical support by clicking Request Access.

3. Once you have logged on to Documentum’s technical support Web site, click AdminAssistance.

4. In the Request Type drop-down list, select Product Access Request.

5. Fill out the form and click Submit.



http://support.documentum.com/Support


Software Media, Organization, and Files

OrganizationThe Documentum Download Center provides a complete listing of products availablefor download. The https://documentum.subscribenet.com/control/dctm/product?cert_num=3731241&child_plne=003896&manu=DCTM&ityp=sw link takes you to the areacontaining all the product downloads comprising Content Server.

FilesThe following files comprise the contents of this release after the compressed ContentServer distribution file is untarred or unzipped:

• bofcollaborationSetup.jar• bofworkflowSetup.jar• consistency_checker.ebs• dfcoperatingsystemSetup.jar• serveroperatingsystemSetup.jar• serverWinSuiteSetup.exe (Windows) or serveroperatingsystemSuiteSetup.bin (UNIX

and Linux)• serveroperatingsystemSuiteSetup.jar• tcfSetup.jar• tomcatoperatingsystem4127Setup.jarThe following files comprise the contents of this release after the compressed full-textindexing distribution file is untarred or unzipped:• dfcoperatingsystemSetup.jar• fulltextoperatingsystemSuiteSetup.jar• fulltextWinSuiteSetup.exe (Windows) or fulltextoperatingsystemSuiteSetup.bin (UNIX

and Linux)• indexAgentoperatingsystemSetup.jar• IndexServer.jar• indexServerSetup.jar


https://documentum.subscribenet.com/control/dctm/product?cert_num=3731241&child_plne=003896&manu=DCTM&ityp=sw


• tomcatoperatingsystem4127Setup.jar


Chapter 9Installation

If your system meets the requirements listed in Chapter 3, Environment and System Requirements,you are ready to install the software. Installation instructions, for new installations and upgrades, arefound in Installing Documentum Content Server. For additional important installation information,refer to Installation notes, page 39.


Installation


Chapter 10Troubleshooting and Getting Help

Documentum’s technical support services are designed to make your deployment andmanagement of Documentum products as effective as possible. The Customer Guideto Support Services provides a thorough explanation of Documentum’s support servicesand policies. You can download this document in PDF form from CustomerNet(http://customernet.documentum.com/support/customer-guide.htm)


http://customernet.documentum.com/support/customer-guide.htm

content server release notes

Documents