IBM Lotus Domino Document Manager 6.5.1 Release Notes March 10, 2004 This is a slightly revised version of the readme.txt file that shipped with Document Manager 6.5.1. The only difference is in the first paragraph of Section 5, "Installing / Upgrading." ================================================================= 1. Table of Contents ================================================================= 1. Table of Contents 2. CD-ROM Contents 3. What's New? 4. Requirements 5. Installing / Upgrading 6. Documentation Updates 7. Known Problems and Limitations 8. For More Information 9. Copyright and Trademark Information ================================================================= 2. CD-ROM Contents ================================================================= The Document Manager 6.5.1 CD-ROM includes these directories: \AIX contains the files needed to install on an appropriate AIX(R) machine. \Docs contains updated copies of the following documentation: * Document Manager Administrator's Guide (ddmadmgd.nsf) * Document Manager Installation Guide (ddmddig.nsf, ddmddig.pdf) * Document Manager Programmer's Guide (ddmddpg.nsf) * Document Manager User's Guide (ddmusrgd.nsf) * Document Manager and Lotus Workflow Integration Guide (ddmddwf.nsf) Once Document Manager has been installed, the above .nsf files can be found in the Document Manager subdirectory that was specified during installation. \License contains copies of the license agreement file, [language].html, where [language] refers to the version language (for example, english.html, spanish.html, and so on). Please review the contents of the license agreement file and ensure you agree before installing Document Manager. \OS400 contains the files needed to install on an appropriate iSeries(TM) machine. \Solaris contains the files needed to install on an appropriate Solaris machine. \Src contains external script files used by Document Manager code, for reference. \Templates contains Domino.Doc(R) 3.5 and Document Manager 6.5.1 templates, for reference. \W32 contains the files needed to install on an appropriate Windows(R) machine. ================================================================= 3. What's New? ================================================================= > Product name This release marks a change in product name from Lotus(R) Domino.Doc to IBM(R) Lotus Domino(R) Document Manager. While much of the user interface and documentation have been updated to reflect the new product name, some existing references to "Domino.Doc" have been retained to ensure a smooth upgrade process. > Faster search performance Response time for domain searches is faster in this release if you access Document Manager via HTTP. If you use the browser client, you'll also notice new advanced search options including search word variants and fuzzy search. > Improved Web browser client interface The enhanced browser client features a consolidated Site Map for quicker access to libraries, cabinets, binders, and documents. The Site Map is also easier to resize -- just click and drag the border to the width you want. > Enhanced Notes(R) e-mail integration Now you can move Lotus Notes(R) e-mail content including header information, body text, and file attachments to a Document Manager library, and choose which components to save. You can also replace the original file attachments in a Notes e-mail message with a link to the corresponding new document in the library. > Improved instant messaging integration IBM Lotus Instant Messaging and Web Conferencing (Sametime(R)) users can save chat transcripts as new documents in a Document Manager library directly from the Lotus Instant Messaging and Web Conferencing Connect Client. > Lotus Workflow integration on non-Windows platforms Lotus Workflow integration is now available on supported AIX, Solaris, and iSeries platforms in addition to Windows. To enable Lotus Workflow integration, Document Manager and Lotus Workflow must be installed on the same server. > LDAP integration When setting up Document Manager libraries, administrators can choose whether to enable Light Directory Access Protocol (LDAP) integration for user directory assistance. LDAP integration is available when you use either the browser client or the Desktop Enabler with HTTP protocol, and requires that Document Manager be running on a Domino 6 server. > Streamlined user authentication with single sign-on Once you connect to a Document Manager library via the browser client, you no longer need to log in again if you switch to using an integrated application or the Windows Explorer during the same work session. Single sign-on for Web browsers also lets you switch between using Document Manager and other Domino-based applications without needing to re-authenticate. > Improved access control for binders Administrators can assign a new Binder Creator access level to restrict who can create and modify binders in file cabinets. > API changes New properties have been added to the API class and Library class to support single sign-on. Custom applications can use these properties to enable and set cookies, enable libraries to share cookies, and control display of the login dialog box. ================================================================= 4. Requirements ================================================================= Because this information is subject to change with new releases of servers, clients, and browsers, IBM maintains up-to-date information on the Web. To see the latest information, go to Lotus Support Services at www.ibm.com/software/lotus/support. From there, search for document #7002980 "Domino.Doc Compatibility Matrices for Client, Server, and Web Browser." Platforms --------- Document Manager 6.5.1 can be used on these platforms: * Microsoft(R) Windows 2003 Server Windows 2000 Advanced Server Windows NT 4.0 * AIX 5.1 or 5.2 * iSeries OS/400(R) V5R1 or V5R2 * Solaris 8 or 9 For information on platform system requirements, see the Document Manager Installation Guide. Domino Servers and Notes Clients -------------------------------- Document Manager can be used with Domino Server and Notes Client releases 5.0.12, 6.0.3, 6.5, and 6.5.1. For information on Domino server and Notes client requirements by platform, see the Domino/Notes 6.5.1 release notes. Web Browsers ------------ Document Manager can be used with these browsers: Netscape Communicator 4.78, 4.79 Microsoft Internet Explorer 5.5 (SP2), 6.0 For information on Document Manager Client (Desktop Enabler) requirements, see Readclnt.txt (located in the Document Manager library). ================================================================= 5. Installing / Upgrading ================================================================= For important information regarding recommendations for upgrade order and supported configurations for the Notes Domino 6.5.1 Extended products, please refer to technote #1162481 on the Web at www.ibm.com/support. Installing Document Manager is a straightforward process, but it is important to perform the install tasks in a specific order. For detailed instructions on installing and upgrading, see the Document Manager Installation Guide. The Installation Guide is available in two formats in the \Docs directory on the CD-ROM. * To view or print ddmddig.pdf, use Acrobat Reader (available from Adobe at www.adobe.com). * To view or print ddmddig.nsf, use the Notes client. If you encounter an error message such as "Cannot write or create file. (file or disk is read-only)," copy the file to your local hard drive, right-click on the file, choose Properties, and deselect "Read-only." For additional notes, read the "Known Problems and Limitations" section below before you begin installing or upgrading. Note: If you are using Domino.Doc 3.0 or earlier, you must upgrade your server to Domino.Doc 3.1, and then upgrade from 3.1 to Document Manager 6.5.1. Lotus Instant Messaging and Web Conferencing (Sametime) integration ------------------------------------------------------------------- To ensure that users can access the Document Manager "Who Is Online" feature, Lotus Instant Messaging and Web Conferencing (Sametime) must be configured correctly. Sametime and Document Manager must be running on separate Domino servers, and the Sametime Secrets database (STAuthS.nsf) and Tokens database (STAuthT.nsf) must be replicated from the Sametime server's data directory (on Windows servers, this is typically c:\lotus\domino\data) to the Document Manager data directory on both the Document Manager master server and replica server. ================================================================= 6. Documentation Updates ================================================================= Corrections to the documentation are noted below. Document Manager Installation Guide -------------------------------------- In the "Installing Document Manager on AIX or Solaris" chapter, in the topic, "Performing master server pre-installation tasks for AIX or Solaris," remove step 8. In the "Installing Document Manager on iSeries" chapter, in the topic, "Performing master server pre-installation tasks for iSeries," remove step 9. Document Manager Administrator's Guide -------------------------------------- In Chapter 2, "Understanding Document Manager," in the topic, "About Document Manager and instant messaging integration," the last sentence in the second paragraph should read as follows: Sametime and Document Manager must be running on separate Domino servers, and the Sametime Secrets database (STAuthS.nsf) and Tokens database (STAuthT.nsf) must be replicated from the Sametime server's data directory (on Windows servers, this is typically c:\lotus\domino\data) to the Document Manager data directory on both the Document Manager master server and replica server. ================================================================= 7. Known Problems and Limitations ================================================================= > "Illegal Exception" error occurs when installing on AIX. If you are installing on an older AIX machine, you may encounter an error message, "Illegal Exception," which generates a coredump. If this occurs, contact Lotus Support Services for the required fix. (SPR #TPAS5VURQF) > Members of nested group in reviewer list cannot complete review. In the browser client, when specifying reviewers for a document, you can select a group and then select a second group that is a member of the first group and add it to the reviewer list. However, the option that allows individual members of the second group to complete the review is not present in the browser client interface. (SPR #AMIA5TQCK5) > APRVCURRENT field cannot be used in search. If a document has not been submitted for approval, the APRVCURRENT field is not added to the document form and therefore cannot be used in a query. To address this issue, you can add a form to the file cabinet template that contains the field APRVCURRENT, then refresh the design of all existing file cabinets. (SPR #LTOT4CEJYR) > When using domdoc.ini to limit file system access, the administrator cannot change the dialog box preference for Word or PowerPoint after initial installation/configuration. If the administrator installs the Document Manager Desktop Enabler, then uses a domdoc.ini file to hide the My Computer icon in the common ODMA dialog boxes without reconfiguring Word and PowerPoint (via the Application Preferences tab in the Document Manager Desktop Administrator) to use the ODMA interface, the end-user will not be able to reset Word or PowerPoint to use the ODMA dialogs. (SPR #RGOE5BJKNS) To fix this problem, delete domdoc.ini. Then, log in as the end- user, open the Desktop Administrator, and change the Word and PowerPoint settings to "ODMA Dialogs." Log out, then log in as the administrator, and recreate domdoc.ini in the directory where the Desktop Enabler is installed (typically c:\lotus\dominodoc). > Temp files are not removed after launching view files. (SPR #CWIR5BJPLH) > Document Manager does not prompt to check in Visio document. After you edit an existing Microsoft Visio document and close the application, Document Manager does not prompt you to check in the document. To fix this problem, you need to define a Visio launch association in the library database as described below. (SPR #CDAY4ZZR3Q) 1. Open the library database. 2. Click Library Administration. 3. Click Create Launch Associations. 4. Enter the following information in the appropriate field: ODMA Format: VSD File Extension: vsd Application ID: Visio Description: Microsoft Visio 2000 5. Click Save, and then click Close. > Browser client does not delete local file after check-in. If you check out and edit a document with a non-ODMA file attachment (for example, a .txt file), the file is not removed from the temp directory on the local machine when you check the document back in. (SPR #CDAY59JHMB) > No option to exclude documents when cloning a file cabinet. When cloning an existing file cabinet, you cannot choose to exclude the documents and clone only the file cabinet structure. All documents and binders in the file cabinet are automatically cloned as well. If the clone is connected to the same library as the original file cabinet and there is more than one document with the same unique ID, searches will not work correctly. To avoid problems, delete any copied documents from the new clone before attaching it to a library. (SPR #KMAS57DJAR) > User is prompted twice to log in when editing Excel file. If Excel is not open and the user tries to open and edit a Document Manager document that has an Excel file attachment, the user is prompted twice to log in. (SPR #NMIL5BWPHF) > Desktop Administrator setting does not work for Excel 97. Users cannot enable Excel 97 for use with Document Manager via the Document Manager Desktop Administrator. (SPR #SYMN5C3JPN) To enable or disable Document Manager Office dialogs in Excel 97: 1. From the Tools menu, choose Add-Ins. 2. Do one of the following: - To use Document Manager Office dialog boxes, select Ddocstartup. - To use native Excel dialog boxes, deselect Ddocstartup. 3. Click OK. 4. From the Tools menu, choose Customize. 5. Select Worksheet Menu Bar and then click Reset. 6. Select Standard and then click Reset. 7. Click OK. > Document action produces error in previously refreshed binder. When using the Windows Explorer in dual pane mode, performing a document action in a binder results in an error if the binder was previously refreshed. For example, if you right-click on a binder and choose Refresh, then right-click on one of the binder documents in the right pane and choose View, an error message displays. This occurs only if Notes protocol is used for the library connection and if Internet Explorer 6.x is installed. To avoid this problem, install an earlier version of IE, or close the Explorer and reopen it without doing a refresh. (SPR #LSWN5C5M8M) > Enabling GB18030 support for simplified Chinese characters. Document Manager uses the following registry key to enable support for GB18030 characters: HKEY_LOCAL_MACHINE/Software/Lotus/Domino.Doc Desktop Enabler/Intl/AsciiFileName By default, all language versions of Document Manager set this registry key to "N" when Document Manager is installed. Administrators should ensure that this registry key is set to "Y" on workstations where users need to save a Microsoft Office or ODMA document that contains GB18030 characters in either the file name or document title. In addition, users must save such documents to a binder that contains only ASCII file names. (SPR #FMYL5UQD7F) Document Manager uses ActiveX technology when binders use the ActiveX design instead of Notes folders to display their contents, and when displaying search results. Because the Document Manager ActiveX controls do not support GB18030, equivalent functionality is provided. Administrators can configure Document Manager to always use Notes folders instead of the ActiveX control to display binder contents, and to display search results in an alternate Notes form. Administrators can use these agents in the Document Manager library to turn access to ActiveX functionality on or off: - EnableActiveX - DisableActiveX After running the DisableActiveX agent, you cannot use the ActiveX design to display binder contents (Document Manager automatically use the Notes folders design), and search results are displayed in a Notes form that does not use ActiveX. In addition, users are no longer prompted to install the Document Manager ActiveX controls. To restore access to ActiveX functionality, run the EnableActiveX agent. After Document Manager is installed, it uses the ActiveX technology by default. This is equivalent to running the EnableActiveX agent. To use GB18030 characters in the text fields displayed in the Binder table of contents or in search results (Document Title, Author Name, or Document Type), you should run the DisableActiveX agent. This disables use of the ActiveX technology for the entire library. (SPR #RPHX5VGL52) ================================================================= 8. For More Information ================================================================= For more information on Document Manager, including documentation on known issues, support, and future enhancements, see: * Readclnt.txt, located in the Document Manager library. To view the file, open the library in the Notes client, click Library Administration, and then click Download Client Software. * Documentation in the \Docs directory on the Document Manager CD-ROM and in the Document Manager directory on your server. * Lotus Support Services at www.ibm.com/software/lotus/support. * Document Manager home page www.lotus.com/dominodoc. * Document Manager (Domino.Doc) for iSeries home page at www.ibm.com/eserver/iseries/domino/related/domdoc.htm. * developerWorks product page for Document Manager (Domino.Doc), at www.ibm.com/developerworks/lotus. ================================================================= 9. Copyright and Trademark Information ================================================================= Licensed Materials - Property of IBM © Copyright IBM Corporation 1997, 2004 All rights reserved. IBM, AIX, Domino, Domino.Doc, iSeries, Lotus, Lotus Notes, Notes, OS/400, and Sametime are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be the trademarks or service marks of others. Excluded Components © Copyright Info-ZIP 1990-1999 All rights reserved. For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals: Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. Redistributions of source code must retain the above copyright notice, definition, disclaimer, and this list of conditions. 2. Redistributions in binary form must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. 3. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, and dynamic, shared, or static library versions--must be plainly marked as such and must not be misrepresented as being the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s). =================================================================