IBM Lotus Domino Document Manager Version 7.0 Release Notes © Copyright International Business Machines Corporation 1997, 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. These release notes include information on the following: * Description * Getting Started * Documentation Updates * Limitations and Known Problems * Contacting IBM Software Support * Trademarks ================================================================= DESCRIPTION ================================================================= IBM(R) Lotus(R) Domino(R) Document Manager lets users manage the complete life cycle of office documents from collaborative authoring to archival. Document Manager 7.0 includes enhancements to improve usability, administration, and serviceability. Usability Enhancements ---------------------- Expanded Notes(R) e-mail integration -- Desktop Enabler users can move Lotus Notes(R) e-mail content, file attachments, and header information directly to a Document Manager library, and choose which components to save. Now, administrators can enable the same Notes e-mail integration for users who do not have access to the Desktop Enabler (for example, users who run Lotus Notes on a Macintosh). Web browser support for the Macintosh -- Macintosh users can access Document Manager libraries via the Apple Safari browser. The Document Manager home page provides quick access to documents that are checked out or have been recently edited, documents that are in the active review or approval process, and documents and binders that have been defined as favorites. Extended access to Doc Manager Neighborhood -- The Doc Manager Neighborhood can be made to display in the Open dialog box and the Save As dialog box of additional selected applications, allowing users to view the library hierarchy, and open and save documents of the appropriate type. Application access to the Doc Manager Neighborhood must be enabled by the Document Manager administrator. eTrust SiteMinder integration -- Document Manager can participate in single sign-on with other Domino-based Lotus collaboration products and third-party applications that are set up to work with SiteMinder. Administrative Enhancements --------------------------- Updating user names -- When an individual user's ID changes, administrators can have Document Manager incorporate the change and update all occurrences of the user name in the library and its file cabinets. Updating library names -- Administrators can rename libraries when needed -- for example, to reflect organizational changes. Clearing locks -- In cases where a user is unable to check out a document (because the document is locked and cannot be unlocked through the user interface), an administrator can run an agent to clear the lock and reset the document to a checked in state. Serviceability Enhancements --------------------------- Enhanced installation logging -- When users install the Desktop Enabler, Document Manager records each step of the installation process in a log file. If installation does not complete successfully, the log file can help diagnose the underlying problem. LotusScript(R) method tracking -- Users can have Document Manager track entry and exit times for each LotusScript method that is called as they work in a library. The resulting logs are stored in the library log database and categorized by user and date so that multiple users who turn on logging at once can track and view results separately. Symbol file -- In the event of a Domino server crash on Windows(R), the Document Manager symbol file (DominoDocMgr.sym) can be used in conjunction with NSD to find out about Document Manager's status and activity at the time the problem occurred. Document Manager 7.0 also includes updates that address previously reported problems. The Document Manager 7.0 Fix List describes these issues and references the associated Software Problem Report (SPR) number. The Fix List will be available in early Autumn 2005 from Lotus Documentation at www.lotus.com/ldd/doc. The announcement letter for the IBM Lotus Notes and Domino 7 extended product family is available from the IBM Offering Information Web site at www.ibm.com/common/ssi. See the announcement letter for the following: * Offering information * Hardware and software requirements * Ordering information Supported Hardware and Software ------------------------------- The information below is subject to change with new releases of servers, clients, and browsers. 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." Server Platforms ---------------- Document Manager 7.0 can be used on the server platforms listed below when paired with an appropriate Domino server: * Microsoft(R) Windows 2000 Advanced Server and 2003 Server (with Domino V6.03, 6.5.1, 6.5.2, 6.5.3, or 7.0) * IBM AIX(R) V5.2 (with Domino V6.03, 6.5.1, 6.5.2, 6.5.3, or 7.0) * IBM AIX V5.3 (with Domino V7.0) * Sun Solaris 8 (with Domino V6.03, 6.5.1, 6.5.2, or 6.5.3) * Sun Solaris 9 (with Domino V6.03, 6.5.1, 6.5.2, 6.5.3, or 7.0) * IBM i5/OS(TM) Version 5 Release 3 (with Domino V6.03, 6.5.1, 6.5.2, 6.5.3, or 7.0) For information on platform system requirements, see the Document Manager Installation Guide. The Installation Guide is available in PDF (ddmddig.pdf) and NSF (ddmddig.nsf) formats in the \Docs directory on the Document Manager CD-ROM, and from Lotus Documentation at www.lotus.com/ldd/doc. For detailed information on Domino server requirements, see the Domino release notes. Document Manager 7.0 also supports Computer Associates eTrust (formerly Netegrity) SiteMinder 5.5 and 6.0. For information on setup and configuration, see the Document Manager Administrator's Guide. Windows Client -------------- To access Document Manager from a Windows client, you need one or more of the following: * IBM Lotus Notes V6.03, 6.5.1, 6.5.2, 6.5.3, or 7.0 * Microsoft Internet Explorer 6.0 * Desktop Enabler (included with Document Manager) The Desktop Enabler requires: * Microsoft Windows 2000 Professional or XP Professional * Pentium(R) 333 Mhz or higher, with 256 MB RAM or higher * 10 MB disk space to install the Desktop Enabler, plus 50 MB disk space for downloading temporary files Macintosh Client ---------------- To access Document Manager from a Macintosh client, you need: * PowerPC G5 processor, with 128 MB RAM (256 MB RAM or higher recommended) * Apple Macintosh O/S X v10.3x * Apple Safari 1.2.1 or later * IBM Lotus Notes V6.5x (for Lotus Notes e-mail integration only) For information on Notes client requirements, see the Notes release notes. For information on Internet Explorer or Safari, refer to the browser documentation. ================================================================= GETTING STARTED ================================================================= The Document Manager 7.0 CD-ROM includes these directories: \AIX contains the files needed to install on an appropriate AIX machine. \Docs contains the following documentation: * Document Manager Administrator's Guide (ddmadmgd.nsf) * Document Manager Installation Guide (ddmddig.nsf, ddmddig.pdf) * Document Manager User's Guide (ddmusrgd.nsf) * Document Manager Programmer's Guide (ddmddpg.nsf) * Document Manager & 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 reference copies of the license agreement file, [language].html, where [language] is a 2-character code that refers to the version language -- for example, en.html (English), es.html (Spanish), and so on. \OS400 contains the files needed to install on an appropriate eServer(TM) i5 or iSeries(TM) machine. \Solaris contains the files needed to install on an appropriate Solaris machine. \Src contains reference copies of external script files that are used by Document Manager code. \Templates contains Document Manager 7.0 templates, and reference copies of templates for the two prior releases. \W32 contains the files needed to install on an appropriate Windows machine. Installing/Upgrading -------------------- 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 .pdf and .nsf formats in the \Docs directory on the CD-ROM, and from Lotus Documentation at www.lotus.com/ldd/doc. * 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 "Limitations and Known Problems" section below before you begin installing or upgrading. Note: If you are using Domino.Doc(R) 3.0 or earlier, you must upgrade your server to Domino.Doc 3.1, and then upgrade from 3.1 to Document Manager 7.0. Domino.Doc is available via Web download from www.ibm.com/software/passportadvantage. For assistance, contact your local IBM representative or authorized IBM Business Partner. Additional Resources -------------------- For more information on Document Manager, including documentation on known issues, support, and future enhancements, see the following: * Readclnt.txt explains how to get started using the Document Manager Desktop Enabler. To view Readclnt.txt, open the Document Manager library in the Notes client, click Library Administration, and then click Download Client Software. * The Document Manager support site at www.ibm.com/software/lotus/support/dominodocmanager/support.html. * The Document Manager home page at www.lotus.com/dominodoc. * The Document Manager for i5/OS home page at www.ibm.com/servers/eserver/iseries/domino/related/domdoc.htm. ================================================================= DOCUMENTATION UPDATES ================================================================= The following documentation has been updated for this release: * Document Manager Administrator's Guide (ddmadmgd.nsf) * Document Manager Installation Guide (ddmddig.nsf, ddmddig.pdf) * Document Manager User's Guide (ddmusrgd.nsf) Corrections to the documentation are noted below. Document Manager Administrator's Guide -------------------------------------- In Appendix C, Best Practices, in the topic, "General recommendations," under "Binders," the last sentence should read: The default binder is best left unused, and can be hidden by using an @If(Title="Default Binder";...) condition in the view selection formula. ================================================================= LIMITATIONS AND KNOWN PROBLEMS ================================================================= This section describes limitations and known problems for Document Manager 7.0, and provides workarounds when available. As limitations and problems are discovered and resolved, IBM Software Support documents the issues and available solutions in technotes. To view all technotes for Document Manager, go to www.ibm.com/software/lotus/support/dominodocmanager/support.html. Installation and Upgrade ------------------------ > Proposed directory name does not default to lowercase. When an administrator creates a library replica, the default value displayed in the New Replica form's "Library path" field and "Configuration database path" is "DomDoc" (instead of "domdoc," the actual default directory used by Document Manager). Because UNIX(R) is case-sensitive, AIX and Solaris users who subsequently look for the replica library in the default Document Manager directory ("domdoc") will not find the replica there. (SPR #CCLI6EV5TY) > Install program backs up templates in wrong location. When you upgrade to Document Manager 7.0, the installation program saves backup copies of the previously installed Document Manager templates in a ddbu350 subdirectory, instead of a numbered ddbu subdirectory that corresponds to the release from which you are upgrading. If a ddbu350 subdirectory already exists, the installation program uses ddbu3501; if a ddbu3501 subdirectory exists, the program uses ddbu3502. (SPR #KMAS6EJLZR) To avoid confusion, after you finish upgrading, rename the ddbu subdirectory that was created during the upgrade process, so that it reflects the actual release from which you upgraded. For example, if you upgraded from Document Manager 6.5.1, rename the backup directory ddbu651. > Incorrect version information causes upgrade error. The Norwegian version of Domino.Doc 3.1 contains incorrect version information that causes an error when you try to upgrade to the Norwegian version Document Manager 7.0. (SPR #RCHG5YVFHL) To avoid this problem, correct the version number as described below before you upgrade to Document Manager 7.0: 1. In the Notes client, open the Domino.Doc Library template (domdoc.ntf). 2. Press CTRL + SHIFT and choose View - Go To. 3. In the Go To dialog box, select the (System Administration) view and click OK. 4. In the right pane, select the AboutBox document and open it for editing. 5. In the "Delversion" field, change the value from 3.0 to 3.1. 6. Save and close the document. 7. Repeat steps 1 - 6 for each existing library. Notes E-mail Integration ------------------------ > "Move e-mail to Document Manager" is visible in Site Admin library. The "Move e-mail to Document Manager" command is designed for use in a Notes mail database only, and should not appear on the Actions menu in the Domino.Doc Site Admin library. However, no harm is done and Notes e-mail integration is not affected. (SPR #KMAS6EJM6Q) > Document containing file attachment cannot be opened. When using Notes e-mail integration on the Macintosh, if the user selects the option "Save email body and attachments in separate documents" and then selects the option "Replace attachments in email with document links," both the Notes doclink and the URL hot link to the attachment display the document profile. Attempting to view the document with the Notes client results in the error "Path/file access error" because the Macintosh is not a supported Document Manager Notes client platform. To view the document, or perform other tasks in the library on a Macintosh, use a supported Web browser. (SPR #NMIL67JRWB) Editing Documents ----------------- > "No working or review copy" error in Library Log. When ODMA users edit a document (without first explicitly checking it out), then save and check in the updated document, the error "No Working or Review Copy" may appear in the library log database and in the domdoc.log file on the user's workstation. The error is caused by a timing issue in Document Manager and does not have any negative effect on the successful checking in of the document. If the ODMA user initially right-clicks on the document title and then chooses Check Out, the error does not occur. (SPR #HMON69WRAY) > 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). > Browser client does not delete local file after check-in. If you use the browser to 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) Supporting GB18030 ------------------ > 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) ================================================================= CONTACTING IBM SOFTWARE SUPPORT ================================================================= IBM Software Support provides assistance with product defects. Before you submit your problem to IBM Software Support, ensure that your company has an active IBM software maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: * For IBM distributed software products (including, but not limited to, Tivoli(R), Lotus, and Rational(R) products, as well as DB2(R) and WebSphere(R) products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online: Go to the Passport Advantage Web site at www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home and click How to Enroll. By phone: For the phone number to call in your country, go to the "Contacts" page of the IBM Software Support Handbook at techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region. * If you have a Subscription and Support (S & S) contract, go to the Software Service Request Web site at techsupport.services.ibm.com/ssr/login. * If you have IBMLink(TM), CATIA, Linux(TM), S/390(R), iSeries(TM), pSeries(R), zSeries(R), or another support agreement, go to the IBM Support Line Web site at www.ibm.com/services/us/index.wss/so/its/a1000030/dt006. * For IBM eServer software products (including, but not limited to, DB2 and WebSphere products that run in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web site at www.ibm.com/servers/eserver/techsupport.html. If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the "Contacts" page of the IBM Software Support Handbook at techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location. To contact IBM Software support, follow these steps: 1. Determine the business impact of your problem. 2. Describe your problem and gather background information. 3. Submit your problem to IBM Software Support. Determine the business impact of your problem --------------------------------------------- When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria: Severity 1 - The problem has a critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Severity 2 - The problem has a significant business impact: The program is usable, but it is severely limited. Severity 3 - The problem has some business impact: The program is usable, but less significant features (not critical to operations) are unavailable. Severity 4 - The problem has minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented. Describe your problem and gather background information ------------------------------------------------------- When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: * What software versions were you running when the problem occurred? * Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. * Can you re-create the problem? If so, what steps do you perform to re-create the problem? * Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, or other system components? * Are you currently using a workaround for the problem? If so, please be prepared to describe the workaround when you report the problem. Submit your problem ------------------- You can submit your problem to IBM Software Support in one of two ways: * Online: Go to the Submit and track problems tab on the IBM Software Support site at www.ibm.com/software/support/probsub.html. Type your information into the appropriate problem submission tool. * By phone: For the phone number to call in your country, go to the "Contacts" page of the IBM Software Support Handbook at techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution. ================================================================= Trademarks ================================================================= IBM, the IBM logo, AIX, DB2, Domino, Domino.Doc, eServer, IBMLink, i5/OS, iSeries, Lotus, Lotus Notes, LotusScript, Notes, OS/400, pSeries, Rational, s/390, Tivoli, WebSphere, and zSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Pentium is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds 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).