open text document management, edocs edition release...

Open Text Document Management,

eDOCS Edition Release Notes eDOCS DM 5.3

December 2nd

, 2010

2 | eDOCS DM 5.3 Release Notes

Contents

1 Introduction .................................................................................................... 3

2 About eDOCS DM 5.3 ..................................................................................... 4 2.1 New Features ................................................................................................... 4

3 Packaging and Documentation .................................................................... 8

4 Supported Environments and Compatibility ............................................... 9 4.1 Server Machines .............................................................................................. 9 4.2 DM User Workstations ................................................................................... 11 4.3 Supported Applications .................................................................................. 11

5 Installation and Upgrade Notes .................................................................. 14 5.1 New Installations and Upgrades .................................................................... 14 5.2 Microsoft Office 2010 “.NET Programmability” .............................................. 14 5.3 DM Server ...................................................................................................... 15 5.4 DM Web Server .............................................................................................. 15 5.5 DM Extensions ............................................................................................... 15 5.6 RM Administrator ........................................................................................... 16

6 Configuration Notes .................................................................................... 17 6.1 Library Generation ......................................................................................... 17 6.2 Database Schema Changes .......................................................................... 17 6.3 DM API Changes ........................................................................................... 19

7 Fixed Issues.................................................................................................. 20

8 Known Issues ............................................................................................... 21 8.1 DM Server and DM Web Server .................................................................... 21 8.2 RM Administrator Tool and RM Extensions ................................................... 24 8.3 DM Extensions ............................................................................................... 25

9 Contact Information ..................................................................................... 30

Ti t le o f Doc ument

www.opentex t . com

For more information about Open Text products and services, visit www.opentext.com. Open Text is a publicly traded company on both NASDAQ (OTEX) and the TSX (OTC).

Copyright © 2010 by Open Text Corporation. Open Text and The Content Experts are trademarks or registered trademarks of Open Text Corporation. This list is not exhaustive. All other trademarks or registered trademarks are the property of their respective owners. All rights reserved.

1 Introduction

These Release Notes describe the latest updates to eDOCS DM 5.3. Open Text

recommends that you read these Release Notes in conjunction with the documentation

included with the software package. If any conflicts exist, the Release Notes supersede

the other documentation.

We also recommend that you check the Open Text Knowledge Center

(https://knowledge.opentext.com/) for any patches or documentation updates that may

have been posted after the initial release of eDOCS DM 5.3.

https://knowledge.opentext.com/



2 About eDOCS DM 5.3

The eDOCS DM 5.3 release includes the resolved issues from the DM 5.2.1 CU5

cumulative update. That is, a later cumulative update will contain everything that an

earlier CU contained, plus any new modifications. A list of Fixed Issues contained in this

release can be found here.

For information about issues fixed in Release 5.2.1 CU5, see the release notes:

DM and RM 5.2.1 CU5 Release Notes

2.1 New Features

2.1.1 Multiple File Formats per Application

The ability to use multiple file extensions is introduced in eDOCS DM 5.3. This allows

users to save versions of a document with different file extensions that are supported

within that application. For example, Word documents can be saved in other file

extensions besides *.doc, such as *.docx or *.rtf.

The File Type drop-down menu appears on the Save As Version dialog box and in

the Save user interface for any type of document that has multiple file type support.

Some file extensions require that only a new document be created. For example, if a

user wants to save a PDF version of a Word document, a “New Doc Only” flag is

entered into the database, which means that all options except for New Document

will appear unavailable to the user.

The save to “New Document Only” option is to prevent a user from saving a

document as a new version which cannot be opened later by the authoring

application. As an example MS Word can save to PDF however Word cannot open a

PDF document. Since this is the case DM will save the PDF with the profile

application field set to ACROBAT. If, a new version of a MS Word document was

saved as a PDF the user will receive an error when they subsequently try to open it

with MS Word.

Additional details on how to configure, edit, enable or disable the file type options of

this new feature can be found in Chapter 8 of the eDOCS DM Administration Guide

under the section “Using Multiple File Extensions”.

2.1.2 eDOCS DM Suite ISO Image

The eDOCS DM 5.3 software is delivered as an .ISO image that can be downloaded

from the Open Text knowledge center and then extracted to a hard drive or CD.

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/3551049/11569762/11568658/customview.html?func=ll&objId=11568658&objAction=browse&viewType=1#DMRM60

http://mimage.opentext.com/support/ecm/secure/releasenotes/dm52/dm521cu5releasenotes.pdf


The eDOCS DM 5.3 software is posted as an ISO-9660 image file on the Open Text

knowledge center and included in the eDOCS DM 5.3 sub folder which can be found

by clicking here.

An ISO-9660 image file is an exact representation of the CD or DVD including the

content and the logical format. To make a copy of the software you can write the

image file to a blank CD-R or DVD-R, resulting in an identical copy of the original disc

including file name and volume label information. The content of the image files may

be accessed directly using third party tools. Using this method you can directly start

the master set-up in the image file.

There are many third party applications that are available for reading and extracting

files from an .ISO image. If you do not currently have an application that works with

.ISO images, a comparison of several applications and their .ISO features is available

by clicking here.

2.1.3 Microsoft Windows Installer (MSI) Based Installs

The eDOCS DM 5.3 software image has a master installer for the suite which allows

you to select from a program wizard which software you would like to install.

Once you have extracted the files you can select which modules to install by starting

the master installer eDOCSSuiteInstall.exe and selecting the individual module from

the module.

The software can also be installed by manually selecting one of the following

individual .MSI installation programs from the software image:

1. eDOCS DM 5.3 Server.msi

2. eDOCS DM 5.3 Web Server.msi

3. eDOCS DM 5.3 Extensions (x86).msi

4. eDOCS DM 5.3 Extensions (x64).msi

5. eDOCS DM 5.3 DM API.msi

6. eDOCS DM 5.3 Workflow Server.msi

7. eDOCS RM 5.3 Administration Tool.msi

8. eDOCS DM 5.3 Document Server Sentry Agent.msi

9. eDOCS DM 5.3 Document Server Security Service.msi

Section 2.1.4 of this document provides additional information on the scripting and

configuration options.

The Windows Installer Development Tools web site contains several tools and

utilities such as ORCA.exe to help you customize the MSI installation programs.

We will be providing a “eDOCS DM 5.3 MSI Installer Whitepaper” which will be

published to the “eDOCS Champion Toolkit” workspace on the Knowledge Center.

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/12312351

http://en.wikipedia.org/wiki/Comparison_of_ISO_image_software

http://msdn.microsoft.com/en-us/library/aa372834(v=VS.85).aspx

https://knowledge.opentext.com/knowledge/llisapi.dll/open/15664314


2.1.4 MSI Scripted Installs

The MSI installer can be launched from a command line or batch file with feature

selection done through properties passed to MSIEXEC.EXE.

The serial numbers for each feature can be specified using

OT_SERIALNUMBER_##="<password>" where ## is replaced by 17 for the DM

Server, 37 for the RM Server and 42 for Content Caching. The passwords are

specified using OT_PASSWORD_## with the same number substitution.

Below is a sample installation script to install everything except the RM Server; it

includes the serial numbers and passwords for the DM Server and Content Caching

passed in on the command line.

ADDLOCAL="ALL" starts with all features selected.

Msiexec.exe /q /i DMServer.msi ADDLOCAL="ALL"

REMOVE="RMServerFeature" OT_SERIALNUMBER_17="17-XXXX-XXX-

XXXXXXXX" OT_PASSWORD_17="xxxxxxxx"

OT_SERIALNUMBER_42="42-XXXX-XXX-XXXXXXXX"

OT_PASSWORD_42="xxxxxxxx"

The same features could be selected by specifying only the desired features on the

command line, such as the following:

Msiexec.exe /q /i DMServer.msi

ADDLOCAL="DMServerFeature,ContentCacheFeature"

OT_SERIALNUMBER_17="17-XXXX-XXX-XXXXXXXX"

OT_PASSWORD_17="xxxxxxxx" OT_SERIALNUMBER_42="42-XXXX-XXX-

XXXXXXXX" OT_PASSWORD_42="xxxxxxxx"

The /q switch causes the install to run without a user interface in "quiet" mode. The /i

switch specifies the MSI to install.

Please consult the “Specifying Features on a Command Line for Scripted Installs”

section of the eDOCS DM 5.3 Installation Guide for additional options.

2.1.5 Windows Communication Foundation (WCF)

Support for Windows Communication Foundation has been added as a

communication method between the DM Extensions and the DM Server.

This feature adds the WCF bindings of NetTCP and HTTP to the DCOM

communication protocol.

Chapter 1 of the eDOCS DM Administration Guide under the section “Network

Bindings Configuration” includes the detailed configuration information.

Details on how to optimize the Windows Communication Foundation protocols can be

found in Appendix A of the eDOCS DM Administration Guide under the section

“Windows Communication Foundation (WCF) Tuning.”


2.1.6 Support for Microsoft Office 2010 (32 bit)

Integration with Microsoft Office 2010 (32 bit version) Word, Excel, PowerPoint,

Project and Visio and Outlook are included with the eDOCS DM 5.3 Release.

New Features specific to Office 2010:

Customize your experience by modifying the DM Ribbon, creating your own

DM Ribbon, adding DM actions to a personal Tab, adding DM actions to the

Quick Access Toolbar.

DM integration with the new Microsoft Backstage interface.

Enhanced Word document compare and merge functionality

Support for the PowerPoint Reuse slide feature

Application Integration based on Microsoft Visual Studio Tools for Office

(VSTO)

2.1.7 SQL Generation Uses SQL-92 Standard

With eDOCS DM 5.3, the SQL generation in the DM system meets the SQL-92

standard. In addition, access to MS SQL databases is changed to be ODBC by

default, rather than DBLib, which is no longer supported with Microsoft SQL 2005 and

Microsoft SQL 2008.

Any new libraries on MS SQL 2005 or later versions will no longer be created in Compatibility Mode 80 (SQL 2000 mode); instead, they will be created in the mode of the database server, either 90 for MS SQL 2005 or 100 for MS SQL 2008.

You can raise the compatibility of any existing libraries (databases) to the level appropriate for the server version (either 80 or 90) so they can support using the SQL Server Native driver, which is more efficient than the old SQL Server driver.

Access to Oracle will still use the pre-existing Oracle *.dll files.

This impacts add-on products; you will need to update your SQL to conform to the SQL-92 standard of performing JOINS in the FROM clause of the SQL statement. Consult SQL-92 standard documentation for more information.


3 Packaging and Documentation

The software documentation is included in the .ISO image and will be extracted to the

Documentation folder on the CD/DVD Image.

The documentation is also available on the Open Text Knowledge Center under the

eDOCS DM 5.3 folder by clicking here.

The following product documentation is available:

eDOCS DM 5.3 API Overview Guide.pdf eDOCS DM 5.3 Webtop Customization Guide.pdf eDOCS DM RM 5.3 Data Dictionary.pdf

eDOCS DM RM 5.3 Designer Guide.pdf eDOCS DM 5.3 API Overview Guide.pdf eDOCS DM 5.3 Administrator Guide.pdf eDOCS DM 5.3 Extensions API Programmers Guide.pdf eDOCS DM 5.3 - Using DM Extensions.pdf eDOCS DM 5.3 Installation Guide.pdf eDOCS DM 5.3 - Using DM Webtop.pdf eDOCS DM 5.3 Imaging.pdf eDOCS DM 5.3 Library Maintenance Tool.pdf eDOCS RM 5.3 API Reference Guide.pdf eDOCS RM 5.3 Administration Guide.pdf eDOCS RM 5.3 Extensions User Guide.pdf

eDOCS DM 5.3 WorkFlow Administration Guide.pdf

eDOCS DM 5.3 WorkFlow User Reference Guide.pdf

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=16707646&objAction=browse&viewType=1


4 Supported Environments and Compatibility

The following tables list the supported environments for the eDOCS DM 5.3 Release.

4.1 Server Machines

4.1.1 DM Server

Processor Windows Server 2003 with Xeon processor 1.9 Ghz or greater

Windows Server 2008 R2 minimum 1.4 GHz (x64 processor) or better

Memory 2 GB or greater (1 GB minimum) 1

Operating System Microsoft Windows 2008 R2 Server – 64 Bit

Microsoft Windows 2003 Server R2 (32 bit)

Citrix XenServer 5.x

Microsoft Terminal Server

DM Server as a Virtual Machine 2

Databases Microsoft SQL Server 2005 and 2008,2008 R2 in Compatibility Mode (80) or SQL-92 standard (mode 90 &100)

Oracle 10g R2

Oracle 11g R2

1 For Optimal SQL server performance, we recommend a dedicated server-class

machine with a minimum of 2GB of RAM.

2 Open Text will support customers who run DM products on supported operating

systems, irrespective of whether they are running in a virtual environment or not.

Open Text supports "operating systems," not specific hardware configurations.

Accordingly, Open Text does not explicitly support the virtualization application

since it operates as a hardware abstraction layer.

The virtualization applications like VMware or Microsoft Hyper-V, support a set of

certified operating systems and hardware, and the customer and the virtualization

vendor will be responsible for any interactions or issues that arise at the

hardware or operating system layer as a result of their use of virtualization

software.

Open Text will not require customers to recreate and troubleshoot every issue in


a non-virtual environment; however, Open Text does reserve the right to request

our customers to diagnose certain issues in a native certified operating system

environment without the virtual environment. Open Text will only make this

request when there is reason to believe that the virtual environment is a

contributing factor to the issue.

While DM products are expected to function properly in virtual environments,

there might be performance implications, which can invalidate DM's typical sizing

and recommendations. Analysis must be performed within the context of the

specific application to be hosted in a virtual environment to minimize potential

resource contention, which can have significant impact on performance and

scalability, particularly under peak load.

4.1.2 Document Server

Operating System Novell Netware 6.5

Microsoft Windows 2008 Server, 2008 Server R2 Microsoft Windows 2003 Server Microsoft Windows 2000 Server EMC Centera

Open Text Archiving for eDOCS (Read-Only)


4.1.3 DM Web Server

Processor Windows Server 2003 with Xeon processor 1.9 Ghz or greater

Windows Server 2008 R2 minimum 1.4 GHz (x64 processor) or better

Memory 2 GB or greater (1 GB minimum)

Operating System Microsoft Windows 2008 R2 Server – 64 Bit

Microsoft Windows 2003 Server R2 (32 bit)

Citrix XenServer 5.x

Microsoft Windows Terminal Server

Web Server Internet Information Server (IIS) 6.0 or 7.0

Client Microsoft Internet Explorer 7 or 8

Mozilla Firefox 3.6

4.2 DM User Workstations Processor Minimum: Pentium 4 – 1.8GHz, 1GB

RAM with Win XP, Min 2GB with Vista or 7.

Recommended: Any dual core processor (x86 or x64) running 2GHz or higher. 2GB of RAM with Win XP, 4GB with Vista or 7.

Memory 1GB or greater (recommended)

Operating System Microsoft Windows 7 – 64 bit version

Microsoft Windows 7 – 32 bit version

Microsoft Windows XP (SP3)

Microsoft Vista (SP2) (32 bit)

VMWare Workstation2

Web Browser Microsoft Internet Explorer 7 or 8

Mozilla Firefox 3.6

4.3 Supported Applications

4.3.1 Integrated Applications

The following table lists the applications supported with eDOCS DM 5.3:


Microsoft Word 2003 3 ,2007, 2010 (32 bit)

Microsoft Excel 2003 3 ,2007, 2010 (32 bit)

Microsoft PowerPoint 2003 3 ,2007, 2010 (32 bit)

Microsoft Project 2003 3 ,2007, 2010 (32 bit)

Microsoft Visio 2003 3 ,2007, 2010 (32 bit)

Adobe Reader and Acrobat 8.0, 94

Freedom Scientific JAWS 11

Dragon Naturally Speaking 10.1

Corel Presentations X3 and X5

Corel Quattro Pro X3 and X5

Corel WordPerfect X3 and X5

Lotus 1-2-3 9.7 and Millennium Edition 9.8

Lotus Word Pro 9.7 and Millennium Edition 9.8

3 Although Microsoft Office 2003 is listed as a supported application for DM 5.3,

we have performed minimal testing with Microsoft Office 2003 and determined

that integration is possible.

Open Text encourages customers to upgrade to Microsoft Office 2007 or

Microsoft Office 2010; however, if that is not possible, we will continue to accept

support cases from customers using DM 5.3 with Microsoft Office 2003.

4 With the release of eDOCS DM 5.2.1 CU 4 and greater the Adobe Reader and

Adobe Acrobat version 9 or greater products are integrated using the DM

Interceptor module


4.3.2 Email Applications

Microsoft Outlook 2003 3 ,2007, 2010 (32 bit)

Lotus Notes 7.0.4, 8.5.2

Novell GroupWise 7.0, 8.0

4.3.1 Open Text Supported Products

Open Text Email Filing Version 3.2 will be released in January and include support for DM 5.3 and Microsoft Office 2010.

Wireless DMS for eDOCS Is currently undergoing final QA and a notice

of support or product update will be provided

in January or prior.

eDOCS Integration for SharePoint Is currently undergoing final QA and a notice



eDOCS Integration for Autodesk AutoCAD Is currently undergoing final QA and a notice



Open Text Email Archiving for Microsoft Exchange Version 9.7.1

Open Text Archiving for eDOCS Enterprise Library Services 10.1


5 Installation and Upgrade Notes

The eDOCS DM 5.3 Installation Guide.pdf is included in the .ISO image and will be

extracted to the Documentation folder on the CD/DVD Image.

The documentation is also available on the Open Text Knowledge Center under the

eDOCS DM 5.3 folder by clicking here.

The following items are additional details which are to be used in conjunction with the

Installation documentation.

5.1 New Installations and Upgrades

The DM 5.3 Server software can be installed on a Windows Operating system which

has not had a previous installation of the DM software. The DM 5.3 software also

supports upgrades from a previous version of DM 5.1.0.5 or 5.2.1.

5.1.1 Microsoft .NET Framework 3.5

The .NET Framework 3.5 is a prerequisite for all products. To install, please

download the Framework from the Microsoft Download Center. You must install .NET

Framework 3.5 on both the client and server machines.

5.1.2 Microsoft Office 2007 PIA’s

The Office 2007 Programmable Interop Assemblies (PIA) are a pre-requisite for the

Application Integration with DM 5.3 Extensions. To install, please download the

redistributable PIA’s from the Microsoft Download Center.

http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-

A28C-B864D8BFA513&displaylang=en

5.2 Microsoft Office 2010 “.NET Programmability”

When installing Microsoft Office 2010 you will need to expand the options for the

individual modules (Word, Excel, etc…) and check to see if the sub-item “.NET

Programmability Support” is set to “Run from My Computer” for the install.

If Office 2010 is already installed on the computer, go to the Control Panel, select Add

or Remove Programs, then select Office 2010>Change. Select the sub-item “.NET

Programmability Support” for the installed Office applications.

The DM 5.3 Application Integration requires that the Office 2010 Programmable Interop

Assemblies be installed on the user’s desktop for the DM integration to work.

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=16707646&objAction=browse&viewType=1

http://www.microsoft.com/downloads/search.aspx?displaylang=en


http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en

http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en


5.3 DM Server





5.3.2 Custom STP files for the DM Indexer (DM-21752)

In DM 5.2.1 if you have non default index settings such as a custom STP file when

you apply DM 5.3 the custom file will not be upgraded to DM 5.3.

If you have a custom STP file, custom.stp for example, in the C:\Program

Files\Hummingbird\DM Server\SSK\fultext directory before you perform the upgrade it

will not be copied to the new indexer directory.

After the installation of DM 5.3, copy the custom.stp file from the C:\Program

Files\Hummingbird\DM Server\SSK\fultext directory to the C:\Program Files\Open

Text \DM Server\SSK\fultext directory.

Also if you have set specific compress times or backup pauses durations for DM

5.1.0.5 or DM 5.2.1 they will be reset to the default values as well unless you copy

your custom.stp file to the C:\Program Files\Open Text \DM Server\SSK\fultext

directory.

5.4 DM Web Server





5.5 DM Extensions





5.5.2 Windows Help (WinHelp) not included with Windows Vista or 7

The Help files delivered with DM 5.3 were created in Windows Help (WinHelp)

format. The Windows Help format is not supported, nor included, with Windows Vista





operating systems. You can download the WinHelp.exe application and use it to view

DM Help files on Windows Vista or Windows 7 operating systems. Download the

appropriate Winhelp.exe application from Microsoft’s web site at the following

location: http://support.microsoft.com/kb/917607. However, the following known issue

has been reported by Microsoft. When you open a Help topic (by pressing F1 or by

selecting Help>Contents and Index), the following error message appears: “There

was a problem running the macro. (1037).” After this initial error, you can continue

using the Help files. For more information and workarounds to this issue, consult

Microsoft’s Article ID 917607 at the following location:

http://support.microsoft.com/kb/917607.

5.6 RM Administrator

5.6.1 Installation

Pre-Requisites

The RM Administration Tool is used to set up and administer a records

management system for RM. The RM Administration Tool can be installed on

any computer with an appropriate SQL client for your database and that has

access to your DM Server and your database.

For full functionality of the RM Administration Tool, your primary group must

be DOCS_SUPERVISORS and you should be a member of

RECORDS_MANAGERS .

The computer on which you install the RM Administration Tool must have

access to your DM Server and your database server, and it must have the

appropriate drivers for your database.

The DM Client API and the DM API must be installed on the machine where

you are installing the RM Administration Tool. If these modules are not

present, the installation program will install them for you.

When the RM Administration Tool starts, it attempts to find the files RM.INI

and PCDOCS.INI. If it tells you that it cannot locate one or both of these files,

obtain valid copies of these files and place them in the folder where RM

Administration Tool is installed.

http://support.microsoft.com/kb/917607

http://support.microsoft.com/kb/917607


6 Configuration Notes

6.1 Library Generation

The DM 5.3 Release Library Generator (tblcomp.exe) program will support upgrading

a DM 5.1.0.5 or 5.2.1 library to the DM 5.3 database schema.

The database changes that have been made with DM 5.3 are listed below in section

6.2.1 of this document.

6.2 Database Schema Changes

6.2.1 APP_FILE_EXTNS Table (DM-18778)

As of DM 5.3, the APP_FILE_EXTNS table was added. The APP_FILE_EXTS table

allows users to save versions of a document with different file extensions.

APPS_LINK Foreign key to the APPS table.

Version Introduced: 5.3

Data Type: Integer

LANGUAGE The language code that filters the Extension/Descriptions based on

the users language, such as EN-US.


Data Type: VarChar (5)

EXTENSION The file extension of the file to be saved, such as DOCX.



DESCRIPTION The description of the File Extensions, such as Word Document.



ORDER_NO The order column number allows the Extensions/Descriptions to be

listed in a specific order.


Data Type: Integer


NEW_DOC_ONLY When the value is Y, the user can save to a new document

only; this supports saving through an application where that application cannot

reopen the file, such as PDF from Microsoft Word. When the value is N, the user gets

all of the standard Save As options.


Data Type: Char (1) (Y or N)

DISABLED When the value is Y, the Extension is disabled and will not appear as a

Save As option. When the value is N (or blank), the Extension will appear in the Save

As options.


Data Type: Char (1) (Y or N)

6.2.2 DOCSERVERS.CONNECTION_INFO

This field is used to store the Enterprise Library Connection Information.

DOCSERVERS.CONNECTION_INFO varchar(254)

6.2.3 Changes to DOCS_UNIQUE_KEYS table to support system

sequences only for MS SQL environment

The DOCS_UNIQUE_KEYS table is NO LONGER used for 5.3 due to locking issues

that may occur under intense system usage in previous versions of DM 5.2.1 or prior

or DOCS Open 4.1. or prior.

The DM 5.3 version now has a new table for each sequence in the system. The

sequence tables all start with SEQ_sequencename.

To support this change the SP_NEXTKEY stored procedure has been modified to get

the next sequence number from these new sequence tables.

By default the 4 standard sequences created by Library Generator (Tblcomp) are:

SEQ_SYSTEMKEY – holds the next SYSTEM_ID sequence value

SEQ_PROFILE – holds the next DOCNUMVER sequence value

SEQ_VERSIONS – holds the next VERSION_ID sequence value

SEQ_NEEDS_INDEXING – holds the next disposable SYSTEM_ID

sequence value for the NEEDS_INDEXING table

NOTE: that if you have created a sequence for use in your own applications, you will

need to go and create a replica sequence SEQ_* table for your sequences to work

with the newly modified SP_NEXTKEY stored procedure


NOTE: if you work in a mixed eDOCS DM and DOCS OPEN environment then you

need to patch your DOCS Open installations so they utilize these new sequences

6.3 DM API Changes

6.3.1 Retrieving Data for Multiple File Types (DM-18731)

As of DM 5.3, client machines obtain the File Extensions available based on the

Application and the language code, such as EN-US, FRCA, or EN. Application cache

objects on the server maintain a list of languages and associated file extensions and

description lists. Access to the data is available as an extension on the

VersionSearch search object.

The call information for the DM API is as follows:

// we need to get the File Extensions PCDSearch searchObj = new PCDSearch(); searchObj.AddSearchLib(CurrentLibrary); searchObj.SetSearchObject("VersionsSearch"); searchObj.SetDST(DST); searchObj.AddSearchCriteria("PCD_APP_ID", txtAppId.Text); searchObj.AddSearchCriteria("PCD_LANGUAGE", txtLanguage.Text); string[] retProps = { "EXTENSION", "DESCRIPTION", "FILE_FORMAT", "NEW_DOC_ONLY" }; foreach (string prop in retProps) searchObj.AddReturnProperty(prop); // execute the search int hRes = searchObj.Execute();

Then get the return rowset as per normal handling for a search object.


7 Fixed Issues

All issues that have been previously resolved in DM 5.2.1 or a subsequent Cumulative

Update have been included in DM 5.3 release.

In addition the DM 5.3 release includes fixes to issues that were opened against

previous versions of DM where those issues still remain open in those previous releases.

You can find the issues that have been resolved in this release by searching the Open

Text Knowledge Base for “5.3” or “This issue is resolved in DM 5.3” from this area. You

will also need to remove the checkmark for All Products and select DM RM for your

search.

https://knowledge.opentext.com/knowledge/llisapi.dll/open/12678460


8 Known Issues

8.1 DM Server and DM Web Server

8.1.1 Data Execution Prevention for DM Administrator Tools

When you attempt to run any of the DM Administrator Tools on Windows Server 2003

or 2008 R2 – 64 bit an error message appears and the application might stop

unexpectedly.

You have two options for changing the default Data Execution Protection settings on

your server.

Select Start>Control Panel>System, select the Advanced Tab>Performance

Settings, select the Data Execution Prevention tab. Select the option for “Turn

on DEP for essential Windows programs and services only.”

OR, Select Start>Control Panel>System, select the Advanced

Tab>Performance Settings, select the Data Execution Prevention tab. Select

the option for “Turn on DEP for all programs and services except those that I

select:” and select the Add option. From the Add option browse to the

Program Files > Open Text > DM Server > Program and select the individual

.EXE files for the DM server utilities you would like to run from the server.

Please review the following Knowledge Base articles for additional details:

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=12940954&objAc

tion=ArticleView

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=12946274&objAc

tion=ArticleView

8.1.2 DM Administrator Tools on Windows Server 2008

If you are not using the shortcuts that were created when the software was installed

and you want to use them by selecting the executable, you need to:

1. Select the individual application, such as Library Maintenance.

2. Right-click and select “Run As Administrator.”

8.1.3 Co-existence with DOCS Open 4.1 (DM-18489)

With DM 5.3 a change was made to the DOCS_UNIQUE_KEYS logic to avoid sql

blocks during heavy usage. The table is used to issue unique keys during requests to

add documents to the system – the change will allow it to use the SEQ_SYSTEMKEY,

SEQ_PROFILE, SEQ_VERSIONS, SEQ_NEEDS_INDEXING tables instead of the

DOCS_UNIQUE_KEYS table.

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=12940954&objAction=ArticleView





This patch will allow the DOCS Open 4.1 Desktop to be used in a mixed environment

with eDOCS DM 5.3 while organizations perform a phased migration.

This patch should only be used when DOCS Open 4.1 is run against a SQL200x compatible (compatibility level 80) database created for eDOCS DM 5.3. Only the DM 5.3 Server Admin tools should be run on an eDOCS DM 5.3 database and the DOCS Open 4.1 Administrator tools should no longer be used.

The Patch will be made available on the Open Text Knowledge Center and can be found in the DOCS Open patch directory by clicking here.

Do NOT implement DM 5.3 with DOCS Open in a mixed environment until this patch has been applied.

8.1.4 Multiple modules on the same DM Server

When upgrading a DM Server to version 5.3, it will remove all previous DM 5.1.0.5 or

5.2.1 shortcuts from the Start menu items. For example, if DM Server and the DM

Workflow Server are on the same machine, once the DM Server is upgraded, the DM

Workflow shortcuts won’t exist on the DM Server until the DM Workflow Server is

upgraded. In summary each server upgraded will require that all other eDOCS

products on that machine to be upgraded as well.

8.1.5 DM Server Performance Counters on Windows 2008 R2 (DM-23171)

The 64-bit Windows Server versions of the Performance Monitor are unable to show

the eDOCS DM Server counters because eDOCS DM Server is a 32 bit application. In

order to display these counters, one will need to run the 32-bit perfmon.exe located in

C:\Windows\SysWOW64.

8.1.6 Error 1053 when attempting to start the DM WebAdmin Service (DM-

22816)

When the DM Webtop is installed it creates a Windows Service that is called Open Text

eDOCS DM WebAdmin Host which has a startup type set to manual. If you try to start

the service you will receive an error “1053: Service did not respond….”.

When the DM Administrator is working within the DM Admin section of the DM Webtop

the service will be started and stopped as required by DM. This is working as designed

and the service should not be manually started.

8.1.7 DM Administrator Shortcuts with Windows UAC Enabled

When you install DM Server on a Windows Server 2008 R2 which has UAC enabled,

you will need to use the shortcuts that the DM Server installation program created. If

you want to have shortcuts on your desktop you will need to copy the ones the DM

Installation created with the install and can alter them so long as you leave the

c:\...AdminShell.exe at the front of the target setting. You also need to be aware that

when you edit one you may not see the AdminShell preface because the textbox isn’t

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/3551049/11569762/11570304/customview.html?func=ll&objId=11570304&objAction=browse&viewType=1


wide enough to show the entire contents. You may just see the last portion

…\tblcomp.exe for example. You need to make sure that you scroll to the beginning

of the entry to make sure the AdminShell is included.

The following table describes the behavior that will occur when using AdminShell.exe

depending on the UAC setting that is in use:

Items in Green are the recommendation options.

Type of User

Domain Admin

Domain User with Local Admin Rights Domain User

Local Administrator Local User

UA

C Settin

g

Always notify

Application launches with a full administrative token; no prompt

Application launches with a full administrative token; prompt for consent

Application launches with a full administrative token; prompt for credentials



Notify me only when programs

try to make

changes to my

computer






Notify me only when programs

try to make

changes to my

computer (do not dim my

desktop)






Never Notify



Program doesn't launch. Message saying you require Administrator rights to run this program


Program doesn't launch. Message saying you require Administrator rights to run this program


8.1.8 Shortcuts for Library Maintenance and Generator Errors (DM-22974)

When upgrading from DM 5.2.1 CU 5 on Windows 2003 SP2 to DM 5.3, you may

receive an error message when trying to use the Open Text shortcuts for the Library

Maintenance or Library Generator programs. This issue is intermittent for the upgrades

of this environment.

Resolution: You will need to reboot the server and the error messages will no longer

appear.

8.1.9 Full Text Indexer Error Message (DM-23281)

When the DM Server Indexer is configured with an index and if the DM Server is not

configured to have an indexer, the user may receive an error message 0x8004033B

instead of the correct warning message of "No Full-Text Index configured for searching

this library. Please notify your administrator."” when the users performs an Advanced

Content search.

Resolution: The DM Server can be configured to have at least one index for the DM

Server. The issue is still under investigation.

8.2 RM Administrator Tool and RM Extensions

8.2.1 RM Administrator Tool Custom Reports on Windows 2008R2 or 7 – 64

bit (DM-23184)

You will need to define a 32-bit data source for the custom reports to work.

Using Windows Explorer browse to the \Windows\SysWOW64 directory and execute

odbcad32 by double clicking it

You will be using the 32 bit version of ODBC which is required by the crystal reports

component within the RM Administrator Tool. You will need to define an ODBC data

source for the DM library.

8.2.2 RM Administrator Tool Installed after DM Extensions (DM-23312)

When you install the RM Administration Tool on a user’s desktop which has the DM

Extensions previously installed, there will be an error when they subsequently try to

save a document to DM.

Resolution: There are several resolutions for this issue.

The RM Administration Tool and the DM API can be installed first on the desktop and

then install the DM Extensions.

Re-running the DM Extensions install and selecting the repair option will reset the

registry.


Or, after installing the RM Administration Tool you will need to change the following

registry key:

HKLM\SOFTWARE\Hummingbird\PowerDOCS\Forms\LookupForm

To: {FBDC1964-9E00-11D4-83FC-00C04F8EEC5A instead of Use Internal Form

8.2.3 RM Administration Tool Logging with UAC

If for some reason you need to enable logging for this module and you have UAC

enabled on the desktop, you will also need to make the following changes:

Run Notepad with Run as administrator rights and add the following section to the

win.ini file:

[Docs Open Logging]

Logtofile=1

Run the RM Administration Tool

The RM Administration Tool will say that the log is being saved in the

c:\windows\docslog.txt however since the user doesn’t have rights to this location

because of UAC protection it will actually save the file under

c:\Users\<username>\AppData\Local\VirtualFileStore\Windows\docslog.txt

8.3 DM Extensions

8.3.1 RM Extension or DM Imaging upgrade Serial Numbers (DM-23141)

The end user will be prompted to enter the serial number for the 5.1.0.5 or 5.2.1 RM

Extensions or DM Imaging software.

The eDOCS DM 5.3 Extensions (x86).msi or eDOCS DM 5.3 Extensions (x64).msi

installation programs can be edited using a third party tool like Microsoft ORCA to

include the serial number and password so that the end user is not prompted to enter

the password.

RM Extensions

To include the serial number for the RM Extensions open the appropriate MSI package

and search for the registry value of: reg0DF9AD2FA12101704368B91318EB855D and

change the value field from [OT_SERIALNUMBER_32] to [32-XXXX-XXX-XXXXXXXX]

to your license key.

You will also need to change the activation key by searching for the registry key

reg03412074384BEFA934BB122079F43EA3 and change the value from

[OT_ENCRYPTEDPASSWORD_32] to [XXXXXXXXXX] to the activation code you

received with your serial number.


DM Imaging

To include the serial number for the DM Imaging open the appropriate MSI package

and search for the registry value of: regFB0B51DBD684CA8C0E08EA4126773E6E

and change the value field from [OT_SERIALNUMBER_28] to [28-XXXX-XXX-

XXXXXXXX] to your license key.

You will also need to change the activation key by searching for the registry key

reg0EAF1943A71D3CD30C955B53DD7EEBBE and change the value from

[OT_ENCRYPTEDPASSWORD_28] to [XXXXXXXXXX] to the activation code you

received with your serial number.

Using a Batch File

You can also create a batch file that launches the msi installation program with a

command line parameter that includes the serial numbers and activation codes using

the following syntax:

msiexec /l*v "%TEMP%\dmext.log" /i "C:\eDOCS DM 5.3 Extensions (x86).msi"

OT_SERIALNUMBER_28=28-0100-001-00000000 OT_PASSWORD_32=1234abcd

OT_SERIALNUMBER_32=32-XXXX-XXX-00000000 OT_PASSWORD_32=XXXX1234

8.3.2 DM Viewer on Windows 7 – 64 bit (DM-22514)

When running the DM Extensions for Windows Explorer on Windows 7 – 64 bit, the DM

Viewer shows up as a tab option in the 3 pane view. If the user selects or has a

document selected when they pick the DM Viewer tab, the display will be blank and the

document will not be shown.

Resolution: The user will need to right mouse click and select the View option to see

the document.

The DM administrator can disable the DM Viewer using the client deployment utility or

edit the eDOCS DM 5.3 Extensions (x64).msi to disable the DM Viewer TAB to prevent

the user from selecting it.

To disable the DM viewer the following registry key needs to be set to:

[HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\PowerDOCS\Explorer\AddOns\

Viewer]

"Disable"=dword:00000001

8.3.3 Compare and Merge Focus with Word 2007 (DM-23233)

When using the "Compare and Merge" feature in MS Word 2007, the Quick Retrieve

window appears behind the Compare and Merge dialogue when choosing the first

document if the ThreadedUI is enabled. The Compare and Merge dialogue stays in the

background behind the MS Word window. You have to minimize the MS Word window

in order to see the Compare and Merge dialogue and choose the second document.


The ThreadedUI uses the following registry keys:

[HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\AppIntegration]

"ThreadedUI"=dword:00000001

HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Hummingbird DM Application

Integration\Installation\Microsoft

"ThreadedUI"=dword:00000001

8.3.4 Select a Word Document when Selecting Insert Picture (DM-21186)

From within Word 2010 when you select the Insert button the Word application is

expecting to insert a picture. When the DM Quick Retrieve is displayed, if you select a

picture, it will be inserted. If you select a Word document, you will be returned to the

main document and it will show a blank icon that says” This image cannot be

displayed”.

In Word 2007 the user would receive a warning message that it the “Graphics is

Unable to convert the file”. With Word 2010 the warning no longer appears and the

user is returned to the main document with “This image cannot be displayed” error

message.

Resolution: This is working as designed due to a limitation in the native third party

application.

8.3.5 Document Information Error in Offline Mode (DM-23271)

When you are offline and open a document from Attache, when you select the DM -

Document Information action, you will receive an error stating 'unable to cast COM

object'System_COM Object'.

Resolution: This issue is still under investigation.

8.3.6 DM Workflow Extensions Require DCOM

The DM Workflow extensions software requires that the DM Extensions be configured

with DCOM to communicate with the DM Server. The Windows Communication

Foundation enhancements are not supported with the DM Workflow Extensions.

8.3.7 GroupWise Upgrade from 5.2.1 (DM-23316)

When upgrading from a GroupWise and DM 5.2.1 to DM 5.3 the email integration will

not be selected by default in the DM Extensions 5.3 wizard, the end user will need to

select the email integration feature for the integration to be installed.


8.3.8 Unknown Publisher with Smart Check In Check Out (DM-23309)

When installing from the DM Webtop the Smart Check In Check Out feature and if

UAC is enabled on the end users desktop, they will be prompted to confirm if they want

to proceed with installing a program from an unknown publisher. It they select yes the

Smart Check In Check Out functionality will be installed.

8.3.9 Unknown Publisher when installing DM Imaging with UAC enabled

(DM-23308)

When installing from the DM Imaging software with UAC enabled on the end users

desktop, the user will be prompted to confirm if they want to proceed with installing a

program from an unknown publisher.

8.3.10 DM Imaging installation on UAC enabled system (DM-23013)

The DM Imaging needs to be installed as an Administrator with UAC disabled for some

DLL’s to be registered.

The problem is caused by TabCtrl32.ocx and Tab32x20.ocx not being registered by the

installation. These modules are located in the system32 directory.

Resolution: If they are registered manually, DM Imaging will work. Also, if the msi is run

as an administrator, the DLL’s will also be registered.

This issue is still under investigation.

8.3.11 PowerPoint 2010 no message is displayed when the DM Add in is

disabled (DM-22453)

To enable the enhanced crash detection for PowerPoint 2010 you can manually add

the following registry key and restart PowerPoint 2010, or edit the DM Extensions

MSI package and change the registry key to:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\User

Settings\OpenText.DM.PowerPoint]

"Count"=dword:00000001

8.3.12 The Initializing… remains displayed in the background (DM-23346)

The “Initialization….” Message that is displayed when the save user interface is first

invoked will remain in the background of the user’s desktop until they exit from DM.

This can be resolved by changing the following registry key on the desktop or by

editing the MSI package.


HKCU\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Forms\QR, create a

DWORD named OpenFirst. A setting of 3 will expand the SaveUI tree automatically if

a location was chosen already or if the last saved to item is used.

Ti t le o f Doc ument

www.opentex t . com

For more information about Open Text products and services, visit www.opentext.com. Open Text is a publicly traded company on both NASDAQ (OTEX) and the TSX (OTC).

Copyright © 2010 by Open Text Corporation. Open Text and The Content Experts are trademarks or registered trademarks of Open Text Corporation. This list is not exhaustive. All other trademarks or registered trademarks are the property of their respective owners. All rights reserved.

9 Contact Information

Open Text Corporation

275 Frank Tompa Drive

Waterloo, Ontario, Canada, N2L 0A1

Telephone:

Canada/USA: 1-519-888-7111

International: +800-499-6544

Fax: +1-519-888-0677

Knowledge Center: https://knowledge.opentext.com/

For more information, visit http://www.opentext.com


http://www.opentext.com/

open text document management, edocs edition release...

Documents