IBM Lotus QuickPlace 3.0

Transcription

1 IBM Lotus QuickPlace 3.0 Release Notes Originally produced September 2002 for QuickPlace 3.0 for the Windows platform Revised November 2002 to incorporate information on QuickPlace 3.0 for the UNIX platform Revised December 2002 to incorporate information on QuickPlace 3.0a for the Windows platform Revised January 2003 to add release note for SPR# JNES5HKJ8K Revised February and March 2003 to incorporate information on AIX 5 support for 3.0, Active Directory support for 3.0a, new offline information, and the following SPR#s: SLAR5GQMMX, JNES5GQNVE, JNES5HLP6W, JNES5HLRNQ, SBRN594TNL, MJAS5KDR7V, MJAS5H4NVQ.

2 Copyrights Disclaimer THIS DOCUMENTATION IS PROVIDED FOR REFERENCE PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS DOCUMENTATION, THIS DOCUMENTATION IS PROVIDED "AS IS" WITHOUT ANY WARRANTY WHATSOEVER AND TO THE MAXIMUM EXTENT PERMITTED, IBM DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SAME. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION, DIRECT, INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES, ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS DOCUMENTATION OR ANY OTHER DOCUMENTATION. NOTWITHSTANDING ANYTHING TO THE CONTRARY, NOTHING CONTAINED IN THIS DOCUMENTATION OR ANY OTHER DOCUMENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF THIS SOFTWARE. Copyright Under the copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written consent of IBM, except in the manner described in the documentation or the applicable licensing agreement governing the use of the software. Copyright IBM Corporation 1985, 2002 All rights reserved. Lotus Software IBM Software Group One Rogers Street Cambridge, MA US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GS ADP Schedule Contract with IBM Corp. List of Trademarks Domino, Domino Designer, inotes, Lotus, Lotus Notes, Notes, QuickPlace, Sametime, are trademarks or registered trademarks of Lotus Development Corporation and/or IBM Corporation in the United States, other countries, or both. AIX, IBM and Tivoli are registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Active Directory, ActiveX, Microsoft, Outlook, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United State and other countries. All other trademarks are the property of their respective owners. 2

3 Table of Contents System Requirements... 4 Installing Critical Fixpack 1 ( CF1)... 6 To install CF1 on Windows NT or Windows To un-install CF1 on Windows NT or Windows 2000 or to determine whether it is installed... 7 To install CF1 on AIX or Solaris... 8 To uninstall CF1 on AIX or Solaris... 8 Description of fixes incorporated in QuickPlace 3.0a for the Windows platform... 8 Fixes related to upgrades... 8 Fixes unrelated to upgrades...11 Known Issues...13 Install...13 Upgrade...15 External User Directory...19 Notes.INI, QPConfig.XML, and Server Settings...24 Offline...26 Sametime...28 Place Catalog...30 Places...31 PlaceTypes...37 QPTool...40 Security...43 International...47 Browser...49 Calendar...51 Other...53 Documentation Updates...56 Setting up QuickPlace for offline users...58 Setting up QuickPlace to allow local users to take places offline...59 Setting up QuickPlace to allow external users to take places offline...61 Reducing download time with the DOLS Pre-Installer CD...64 QuickPlace offline Q&A

4 System Requirements You must install the QuickPlace 3.0 server on top of an IBM Lotus Domino server. You must also install the Critical Fixpack 1 on the Domino server. The following table describes the software requirements for QuickPlace. Refer to the Domino release notes at 12.lotus.com/ldd/doc/domino_notes/5.0.10/readme.nsf/1f cf98d c /4f0 e8e326aef4c bac0059e3a9?opendocument for hardware and memory requirements. Server operating systems IBM AIX 4.3.3, 5.1, 5.2 Solaris 8 Windows 2000 Windows NT 4 with Service Pack 6 Client operating systems Windows 98 Windows NT Windows 2000 Windows XP Professional Macintosh System 9 Browsers Internet Explorer 5.5 with Service Pack 2 Internet Explorer 5.1 (Macintosh) Internet Explorer 6 Netscape 4.79 Directories LDAP v3 compliant. QuickPlace Release 3 has been verified with Active Directory, iplanet, Domino, and Secureway directories. Native office suites Microsoft Office XP Microsoft Office 2000 Microsoft Office 97 with Internet Assistant Wizard 1 Authentication Netegrity SiteMinder 4.6 (not supported for UNIX ) Multi-Server/LTPA Domino/DSAPI Third-party products iplanet Portal Server 3.0 SP2 Tivoli PolicyDirector 3.8 IBM Network Dispatcher Install the Internet Assistant Wizard by doing a custom install of Office 97. The wizard allows native Office 97 documents to be saved as HTML. It's possible that Office 97 Service Release 2 installs the wizard automatically. IBM Lotus QuickPlace 3.0a is now supported with Active Directory IBM Lotus QuickPlace 3.0a is now supported with Microsoft Active Directory. This document describes the testing the QuickPlace product team has done to verify this support and the results of the testing. Note: Releases of QuickPlace prior to 3.0a are not supported with Active Directory. 4

5 Platforms / configurations included in this testing: The following platforms and configurations were tested: - Lotus QuickPlace 3.0a (Windows only) - Windows 2000 Server with Microsoft Active Directory enabled - QuickPlace communication with the Active Directory server via LDAP v3 - Internet Explorer IE5.5 SP2, IE6 The following were not tested with Active Directory and QuickPlace 3.0a: - QuickPlace for IBM AIX and/or Solaris - Netscape browser (on any client platform) - Macintosh client - Netegrity SiteMinder Testing Results: The following features were tested manually and found to work with Active Directory: 1. Basic Authentication 2. Multi-server session authentication 3. These QPTool commands: - changemember - changehierarchy - removemember - newsletter - sendmail 4. Super User 5. Place Catalog 6. Who can administer this server 7. Who can create new places on this server 9. Schema mapping 10. Custom filters 11. Member lookup customization 12. Narrow searches to a place name 13. QuickPlace/Sametime: - Awareness name links - Chat - Members Online window - Online Meetings In addition, over 1400 automated tests were done, primarily of end-user features. Note: Using places offline is currently not supported within an Active Directory environment. The following configurations are not supported in this QuickPlace release. Using a non-ldap external user directory. Connection to a Domino Directory over NRPC (the Notes protocol) is supported only during the upgrade process. After you have upgraded, you must switch to an LDAP-accessible external user directory -- either a non-domino directory or a Domino Directory on a Domino server running the LDAP task. IIS HTTP server Partitioned server install Cisco LocalDirector Clusters running ICM. Single-server authentication 5

6 Installing Critical Fixpack 1 ( CF1) Install Critical Fixpack ( CF1) to upgrade the Domino server with fixes that improves the server s operation with QuickPlace 3.0. The fixpack is installed by the Domino Incremental Installer CF1 provides the following fixes for Domino interoperation with QuickPlace: Related SPR SPR #MDEY5CCKBW SPR# MBAA592MFM SPR# JCAL4VPSRM SPR# VSEN4UNSXZ SPR# LCUN58NUVV SPR# VDSE59BEKK SPR# JNES5D7J24 SPR # JRUO5DNPQL Fix description Enables QPTool commands issued from the console to accept more than 9 arguments Removed the text "DSAPI user password" from the DSAPI authenticated users password field. When a cross certificate is in the Offline Domino Directory for a DOLS user, it will be deleted and recreated during reinstall. Corrects a problem in which DOLS crashes Internet Explorer when accessing a Mail File (using Mail50Ex.ntf) through the iplanet Portal Server. Reverse Proxy support has been added. There is an outstanding issue with the dolres.ntf template that causes an inability for the DOLWebControl to load when using a reverse proxy server and downloading a DOLs database from a remote system. The following workarounds are available: 1) Install the DOLS control first through another download path; or 2) The Domino Administrator could change the dolres.nsf javascript to create the correct URL that will load the DOLS control in the reverse-proxy environment. Fixed an access violation crash that could happen when reading or writing file attachments in a document that has a readers or readwriters field. Fixed a problem with LDAP Add operations, which caused group members which are not hierarchical (e.g. cn=scott Smith) to be stored in noncanonical format. This would cause problems with subsequent LDAP search operations which did membership searches (e.g. (&(objectclass=groupofnames)(member=cn=scott Smith)). A trailing slash would be added (Scott Smith/). Fixes an intermittent HTTP server failure that occurred with DOLS. Corrects a problem in which QuickPlace authorization failures could occur due to incompatibility with Domino Web Server User Cache 6

7 To install CF1 on Windows NT or Windows 2000 Follow these steps to install the fixpack on the Domino server that runs on Windows NT or Windows The fixpack is installed by the Domino Incremental Installer. 1. Install Domino if you haven't already. 2. Shut down the Domino server if it is running. 3. Insert and start the QuickPlace installation CD. If you are installing the fixpack from a network drive, navigate to the directory with the QuickPlace installation kit. 4. Open the DominoFixPack folder. 5. Double-click the file 5010_5010cf1ser.exe to begin the Incremental Installer. 6. Verify that the "Notes program files have been found in" box displays the path to the Domino server program directory. If the default path is not correct, specify the correct path. 7. Verify that the "and Notes data files have been found in" box displays the path to the Domino server data directory. If the default path is not correct, specify the correct path. 8. Click Next. 9. Click Next again to begin the upgrade. 10. When the upgrade is complete, click Close. To un-install CF1 on Windows NT or Windows 2000 or to determine whether it is installed Follow these steps to un-install CF1 from a Domino server on Windows NT or Windows 2000, should you decide you don't want to use it. You can also follow these steps to determine whether the fixpack is installed. 1. Insert and start the QuickPlace installation CD. If you are installing the fixpack from a network drive, navigate to the directory with the QuickPlace installation kit. 2. Open the DominoFixPack folder. 3. Double-click the file 5010_5010cf1ser.exe. 4. Verify that the "Notes program files have been found in" box displays the path to the Domino server program directory. If the default path is not correct, specify the correct path. 5. Verify that the "and Notes data files have been found in" box displays the path to the Domino server data directory. If the default path is not correct, specify the correct path. 6. Click Next. 7. If you see the words "Please, select release version to revert to" then CFP1 is already installed. 8. To un-install the fixpack, select "Release " in the box. 9. Click Next. 10. When you see the prompt "Congratulations, you have successfully reverted this product." click Close. Note You can also determine whether this fixpack has been installed by entering "show server" on the server console. If this fixpack has been installed you will see the server version number show CF1 after it (as below). 7

8 To install CF1 on AIX or Solaris Follow these steps to install the fixpack on the Domino server that runs on AIX or Solaris. Note: CF1 for AIX and Solaris is delivered separately from the QuickPlace 3.0 CD. 1. Install Domino if you haven't already. 1. Shut down the Domino server if it is running. 2. Insert and start the CD with the fixpack. If you are installing the fixpack from a network drive, navigate to the directory with the fixpack. 3. On the command line, enter./install. 4. At the installation settings screen, the incremental installer displays the Domino program and Domino data directories, and the name of the UNIX user and UNIX group who own them. If these are correct, press TAB to upgrade the server. 5. Once the Domino server is upgraded with the Critical Fixpack1, the incremental installer displays the files which have been replaced with upgraded versions. You should see, The installation has completed successfully. 6. Start the Domino server. The Lotus Domino server copyright paragraph should contain the new release number of the server, CF1 (not 50100). To uninstall CF1 on AIX or Solaris To uninstall the Critical Fixpack1, follow the steps to install the fixpack again. The incremental installer recognizes that you have already installed and asks if you d like to revert back to the previous version of Domino (50100). If you say yes, the incremental installer restores the old files. Description of fixes incorporated in QuickPlace 3.0a for the Windows platform The following tables describe the fixes incorporated in QuickPlace 3.0a for the Windows platform. These fix descriptions are organized by whether they relate to upgrades. Except where noted, QuickPlace 3.0 for the UNIX platform already includes these fixes. Fixes related to upgrades QuickPlace 3.0a for the Windows platform fixes several problems related to upgrades. If you previously upgraded a Windows server from QuickPlace 2.0x to 3.0, some of these fixes require additional steps to implement them when you upgrade to 3.0a. For one fix only, the first described in the table below, if you previously upgraded to 3.0 you must restore the release R2.0x places then upgrade the places to 3.0a to implement the fix. Note: if you upgrade from QuickPlace 2.0x directly to 3.0a, with the exception of SPR# HDAI5FESW7 (see below), the only step necessary is to upgrade places after 8

9 you install R3.0a by runing qptool upgrade on them. For more information on upgrading places see the Installation and Upgrade Guide. The following tables describes the upgrade-related fixes provided in QuickPlace 3.0a. It also describes any additional steps required to implement them if you previously upgraded to release 3.0. SPR # Description Additional steps necessary if you previously upgraded to R3.0 HDAI5FKTV8 Fixes a problem where if you ran qpmove in R2.0x on a place derived from a PlaceType, when you upgraded and refreshed the place you lost any data added by users (as opposed to data inherited from a PlaceType) before qpmove was run. This fix requires you to complete these steps after upgrading to R3.0a: 1. Restore a backup of the affected R2.0x places 2. Run qptool upgrade on the affected places. KHIA5FLTQ3 JALS5DVKWF CDUY5F9PHC HDAI5F9UBK HDAI5F9QBX Fixes a problem where installation stalled during upgrades of a large data set Fixes a problem where a page created from a custom form containing the field types Name Pop-up and Page Author displayed the field as undefined after an upgrade. Fixes a problem where places using the classic theme changed to the QuickPlace 3.0 default theme after an upgrade Fixes a problem where a place that used a tweaked default theme lost imported custom.gifs after an upgrade Fixes a problem where a place created from a PlaceType did not show the Customize link in the table of contents after an upgrade None None After upgrading from R3.0 to R3.0a, run qptool upgrade on the affected places After upgrading from R3.0 to R3.0a, run qptool upgrade on the affected places After upgrading from R3.0 to R3.0a, run qptool upgrade on the affected places 9

10 HDAI5FE23D JNES5FFN59 WQUN5ERQJQ JALS5ECPHY CLEY5F6K6T HDAI5FESW7 HDAI5FPTNU Fixes a problem where a member of super user group didn't see rooms in a place after an upgrade Fixes a problem where a R2.08 Default theme was not tweakable after an upgrade. Fixes a problem where customizations to discussion folders were lost after an upgrade Fixes a problem where features were enabled in a place created from a PlaceType after an upgrade even though the PlaceType used to create the place disabled the features in places. Fixes a problem where the Examples link no longer used in R3.0 still existed in the QuickPlace place after an upgrade Fixes a problem where a place created in R2.0x without an explicit theme selection changed to the default R3.0 theme after an upgrade Fixes a problem where when you installed the 11/01/02 R3.0 hot fix from Build , the Default Theme - Standard was not preserved in the QuickPlace place Server Settings and Create a After upgrading from R3.0 to R3.0a, run qptool upgrade on the affected places After upgrading from R3.0 to R3.0a, run qptool upgrade on the affected places After upgrading from R3.0 to R3.0a, recreate the customizations in the folder. After upgrading from R3.0 to R3.0a, from a Notes client change the value of the fields "h_isintoc" and "h_isdisabled." For more information, see the release note "Features disabled in a PlaceType are enabled in places after an upgrade" in the "Known Issues - Upgrade" section of the release notes. Alternatively, you can restore a backup of the place not yet upgraded to 3.0 and run qptool upgrade on the place using R3.0a. After upgrading from R3.0 to R3.0a, run qptool upgrade on the QuickPlace place, i.e.: load qptool upgrade -p quickplace To preserve the R2.0x theme selection: 1. Upgrade the QuickPlace server to R 3.0a. 2. Add this upgrade setting to qpconfig.xml and restart the server: <upgrade> <theme update_default_to_latest="false"/> </upgrade> 3. Run qptool upgrade on the affected places. For more information, see the release note "A place created in R2.06/R2.08 without an explicit theme selection changes to the default R3.0 theme after an upgrade" in the "Known Isses - Upgrade" section of the release notes. Note: These steps are also necessary if you are upgrading from R2.0x directly to R3.0a. For information on necessary steps to correct the problem, see the release note "Can't preserve the R2.0x Default Theme - Standard in some rooms of the QuickPlace place after installing the 11/01/02 hot fix" in the "Known Issues - Upgrade" section of the release notes. 10

11 WQUN5EDLE9 SSEI5FTP9C Place rooms. Fixes a problem where external members in PlaceTypes were not upgraded to native directory format Fixes a problem where if you switched a server from using a Domino Directory via NRPC to an LDAP directory, then upgraded a place, users could not see the place listed under My Places if the user's name in the place used slashes as delimiters (the Domino format). These steps are only needed if you installed the hot fix. Follow steps described in the release note "External members in PlaceTypes not upgraded to native directory format" in the "Known Issues - Upgrade" section of the release notes. If you did not run qptool upgrade on a place in R3.0, you can do so in R3.0a without problems. If you ran qptool upgrade on a place in R3.0 after changing to an LDAP directory, use the qptool changemember command to change the format of the names in a place to the LDAP format. For example: Load qptool changemember -p place1 -p - sourcedn "cn=acme/o=marketing " -targetdn "cn=acme,o=marketing" Fixes unrelated to upgrades The following fixes provided in QuickPlace 3.0a for the Windows platform are unrelated to upgrades. Category SPR # Description Places MHKM5E4B6C Fixes a problem where tweaking the sidebar items in a theme and changing to graphic text caused the error "Sorry Quickplace unable to process your request at this time. MMGN5DNQYZ Fixes a problem where users had the option to put a page in the index during publish, copy, and move even though the Hide Index option (located in Customize Basics) was selected PKRR5EWSSK Fixes a problem where specifying a graphic when tweaking a theme causes the HTML tag rather than Go Up with an arrow to display in rooms. MMGN58NN84* Fixes a problem where a Domino Directory user who is manager of an inner room but a reader of the main room could not add a member to the inner room. AVEI5F9LEC Fixes a problem where a user attempting to open an imported page in a place created from a PlaceType got JavaScript errors if the name of the user who authored the imported page contained an apostrophe. RSCR5DXE3J Fixes a problem where when a user chose the option New Multiple Imported Pages and published the pages in the index, the first document showed the author s first and last name but subsequent documents showed the author s user ID. JWEI554BSD Fixes a problem where if a place allowed anonymous author access and the manager added a local group 11

12 called -Default-, author and reader lists displayed incorrectly when users published and checked out pages. Note that adding a local group called -Defaultis not recommended because it causes name ambiguity when it conflicts with the -Default- entry used in Domino. TDEY5EBG65 Fixes a problem where when there was only one custom form in a room and it was re-ordered such that it no longer was at the end of the list, that form would not appear in the Show/Hide forms list and Show/Hide would not work. SSHI5G2RAM* Fixes a problem caused by QuickPlace generating absolute URLs for pages when QuickPlace was used with products that manipulate URL paths. QuickPlace now generates only relative URLs. PlaceTypes HDAI5GHRQ5* Fixes a problem where after resaving an HTML form in a source place then refreshing the PlaceType and child place, a user could not create a page using the form in the child place. Browser MGAR5ERT49 Fixes a problem where tweaking a theme by choosing Tweak Sidebar Items Graphic Text causes Netscape to hang MHKM5E4BBL Fixes a problem where when using a Domino Directory with a Netscape browser you could not see the Add and Close buttons in the Add Members dialog box. Offline ICOR5EKHYR Fixes a problem where places cannot be used offline when the Domino server on which QuickPlace runs is run as a service instead of from the command line. Sametime SLAR5FKPNU Fixes a problem where the Chat feature displayed the names of members with multi-valued relative distinguished names (RDNs) incorrectly. Place Catalog Internation al HDAI5G2L4T BROK5FMRKK MHKM5EJ49N KHIA5GH5B9* KHIA5FWN2F Adds support for the NOTES.INI log setting QuickPlacePlaceCatalogQueryLogging=4 to provide more detailed logging of Place Catalog queries. This logging setting helps troubleshoot problems relating to My Places and the qptool report command. Greatly reduces the time QuickPlace takes to display My Places results. Fixes a problem where searching across places based on date did not return results Fixes a problem that prevented you from using DBCS characters to search all places. The problem is currently fixed only if the browser is Internet Explorer, not Netscape Navigator. Fixes a problem where Addin: Agent error messages display at the server console on a server running an operating system configured for Turkish. Calendar JALS5FSRME Fixes a misspelling of Mid-Atlantic Standard Time in the calendar. JALS5EHQND Fixes a problem where on the date daylight savings time began or ended the calendar omitted that date. 12

13 MTAI5E6C6D Fixes a problem where when a calendar event was cancelled, the event notification message received by a Lotus Notes 5 or Microsoft Outlook client showed "Rescheduled Event" in the subject instead of "Cancelled" QPTool HTTN5D2947 Fixes a problem that prevented you from sending mail to members of a group with a flat name using the qptool sendmail command with the -managers argument. HDAI5FUM4U Fixes a problem where the qptool changemember command deleted a user name from a place when the user was from an external directory and the specified source and target names differed only by the delimiter, for example, when changing slash delimiters to commas. PFKY5FBGL7 Fixes a problem where the qptool execute command wrote the xml output file using native platform encoding rather than UTF-8. Help PFKY5EPFN2 Fixed a typo in the Help topic Using mail in a place *Problem still occurs in QuickPlace 3.0 for the UNIX platform. Known Issues The known issues are categorized as follows: Install Upgrade External User Directory Notes.INI, QPCONFIG.XML and Server Settings Offline Sametime Place Catalog Places PlaceTypes QPTool Security International Browser Calendar Other Documentation Updates Install Append & to command for starting Domino on UNIX The UNIX installation documentation says that when running the server in production, run /opt/lotus/bin/server. It should be /opt/lotus/bin/server &. Without the '&', the server will crash when the user logs off the OS id. SPR#MJAS5GVMUN 13

14 Install on Solaris fails if /tmp folder has inadequate space Problem When you install QuickPlace on Solaris, if the /tmp folder has 42MB or less space available, you are forced to exit the install. Resolution Remove files from the /tmp folder or reboot the Solaris server to clear the /tmp folder, then install again. SPR #WQUN5FSTD7 The QuickPlace installer stops and disappears at the license screen Problem The QuickPlace installer stops and disappears at the license screen if the display setting is set to 16 color. Resolution Change display setting to 256 color or higher. SPR #KHIA5DTQ4P Uninstall QuickPlace before installing a different Domino version QuickPlace 3.0 only works on a Domino server. If you want to install a later release of Domino - please uninstall QuickPlace BEFORE installing another version of Domino. SPR #JNES5CXN9S Cannot uninstall QuickPlace on UNIX automatically Problem You cannot uninstall QuickPlace automatically on a server running UNIX. Resolution Uninstall QuickPlace manually. To uninstall, delete the data directory e.g. use the command rm -rf /local/quickplacedata. And delete the program directory e.g. use the command rm -rf /opt/quickplace. SPR #MJ5E5400QP If QP Admin same as Domino Admin you must add person record manually Problem When installing QuickPlace, if QuickPlace administrator's first name matches Domino administrator's first name, installation will not add the QuickPlace administrator's person record to Domino Directory (NAMES.NSF). Resolution Edit NAMES.NSF and manually add QuickPlace administrator's person record in the Domino Directory. SPR #THD9DE00QP Specify a QuickPlace administrator name and password that is not present in the external directory Problem When prompted during install for the name and password of the QuickPlace administrator, if you specify a name and password that is the same as one in the external directory, the administrator encounters problems such as not being able to see My Places. Resolution During install specify a QuickPlace administrator username and password that is not used in the external directory and use this name and password only for QuickPlace administration. SPR #LWOY5E3J76 14

15 Upgrade Forms hidden in places in Release 2.x are visible after an upgrade Problem If you hid forms in places in Release 2.x (by choosing Customize -> Forms- >Show/Hide), after you upgrade the places to Release 3.0 the previously hidden forms become visible. Resolution If the places with previously hidden forms were created from a PlaceType, do the following to correct the problem: 1. In the source place, choose Customize - Forms - Show/Hide forms to hide the forms. 2. Use the qptool refresh -pt <placetype list> to refresh the Placetype(s). 3. Use qptool refresh -p <place list> to refresh the places. If the places with previously hidden forms were not created from a PlaceType, instead do only step 1 on each of the places. SPR #HDAI5FSMB2 External members in PlaceTypes not upgraded to native directory format (Windows R3.0 to R3.0a upgrades only) Problem Upgrading a Windows server from Release 3.0 to Release 3.0a does not upgrade external member names in a PlaceType to the name format used in the external directory (native directory format). Therefore when you create a place from the PlaceType, the external members specified in the PlaceType cannot log into the new place. This problem does not occur when upgrading a UNIX server or when upgrading a Windows server from Release 2.0x to Release 3.0a. Resolution If the source place used to create the PlaceType is still available, do the following: 1. Use the QPTool upgrade command to upgrade the source place. 2. Delete the pre-3.0 PlaceType, and create a new 3.0 PlaceType from the upgraded source place. If the source place for the PlaceType is no longer available, use the qptool changemember command on each new place created from the PlaceType. Use the command to change the format of external user names that are taken from the PlaceType to the native directory format. For the sourcedn specify the external name that currently appears in the place. For the targetdn specify the distinguished name from the external user directory. Tip: Look at the h_alias field in the Member document in the place's contacts1.nsf database to determine the user's distinguished name from the external user directory. For example, use this command: qptool changemember -p placename -sourcedn "cn=user Name/ou=placename/ou=QP/o=cert" -targetdn "cn=user Name,ou=org unit, o=org" SPR#WQUN5EDLE9 Upgrading servers that run IIS Problem I have an existing server that runs with IIS, but IIS is not supported in QuickPlace 3.0. Resolution Because IIS is no longer supported in 3.0, if you are upgrading QuickPlace server running with IIS, you must make the following changes before you start the QuickPlace 3.0 server. 1. Remove the QuickPlaceIIS=1 setting from NOTES.INI 2. Add 'HTTP' task to the ServerTasks settings in NOTES.INI 15

16 No browser error when you attempt to refresh a PlaceType before it is upgraded If you have upgraded your server, but have not yet upgraded PlaceTypes on the server, and you make changes in a PlaceType, the browser will say "A request will be submitted to refresh the PlaceType." You are led to believe the PlaceType will be refreshed. However, a PlaceType cannot be refreshed until it is upgraded. This is reflected in an error on the server console: qptool: processing placetype: ptfromplace1 QPException: Operation cannot be done until the pre-3.0 PlaceType has been upgraded with qptool upgrade This issue is release noted in "QPTool errors that result from administrative actions initiated from the browser do not display in the browser." Server administrators should be told not to change or refresh PlaceTypes until all PlaceTypes are upgraded. Upgrade places before PlaceTypes, and tell administrators not to refresh PlaceTypes until they are upgraded When upgrading places and PlaceTypes, you have two choices. You can either upgrade all places and PlaceTypes at once using load qptool upgrade -a, or upgrade places and PlaceTypes one or a few at a time, using load qptool upgrade -p/-pt placename(s) or PlaceType name(s). If you upgrade one or a few at a time, upgrade places first, then PlaceTypes. Also, you cannot change or refresh PlaceTypes until they are upgraded. Server administrators should be told not to change or refresh PlaceTypes until all PlaceTypes are upgraded. When upgrading a PlaceType or a place derived from a PlaceType, make sure the source is available on the server (UNIX only) When upgrading a PlaceType or a place derived from a PlaceType, make sure the source place of the PlaceType or the PlaceType of the derived place is available on the server. Otherwise, future updates to the source may not get pushed to the upgraded PlaceType or place. SPR #HDAI5FKTV8 Changes to the sort column of a place s Index folder is lost after an upgrade Problem If you changed the sort column of a place s Index folder in a previous release, the sort column reverts to the Title column after you upgrade to Release 3.0. Resolution Click Folder Options from the Index (where the setting is correct) then click Next and Finish. The column sort will be reset to the setting that existed before the upgrade. SPR #JALS5E6KMK The syntax for creating a place through a URL has changed from earlier releases Problem The syntax for creating a place through a URL used in previous releases no longer works. Resolution The following example shows how to correctly create a new QuickPlace from a URL in Release

17 w/?editdocument&presetfields=h_seteditcurrentscene;h_createmanager,h_editacti on;h_next,h_setcommand;h_createoffice,h_placetypename;h_stdplacetype,h_na me;urltest,h_username;john%20smith,h_setpassword;john,h_ address;jsmit nsf?opendatabase,h_ownerauth;h_external Note that in the above URL, the specified owner is a user that exists in an external directory. SPR #JEF66D00QP Reviewer s name related to a workflow review cycle shows in calendar after you upgrade a place Problem If a calendar page is in the midst of a workflow review cycle when a place is upgraded, the current reviewer's distinguished name will appear in the calendar. Resolution Once the reviewer edits or approves/rejects the page, the reviewer s name no longer appears. SPR #JALS5E6R6V A place created in R2.06/R2.08 without an explicit theme selection changes to the default R3.0 theme after an upgrade Problem In R2.06/R2.08 the Default Theme Standard was applied to places created without an explicit theme selection. How do you ensure that these places continue to use the R2.06/R2.08 Default Theme Standard after you upgrade them? Resolution To retain the R2.06/R2.08 Default Theme Standard in places created in those releases without an explicit theme selection, add the following setting to the qpconfig.xml file before you upgrade the places: <server_settings> <upgrade> <theme update_default_to_latest="false"/> </upgrade> </server_settings> By default or when you specify theme update_default_to_latest="true" in qpconfig.xml, QuickPlace upgrades places created in R2.06/R2.08 without an explicit theme selection to the R3.0 Standard Default Theme. The following table provides examples of upgrade outcomes, depending on R2.06/R2.08 theme selections and the upgrade settings. Theme selection in R2.06/R2.08 Default Theme Steel selected Default Theme Standard explicitly When you set them update_default_to_ latest="true" R3.0 Simple Steel (equivalent of R2.06/R2.08 Default Theme Steel) R3.0 Simple Standard Theme after upgrade When you set theme update_default_to_ latest="false" R3.0 Simple Steel (equivalent of R2.06/R2.08 Default Theme Steel) R3.0 Simple Standard When you do not specify in qpconfig.xml R3.0 Simple Steel (equivalent of R2.06/R2.08 Default Theme Steel) R3.0 Simple Standard 17

18 selected No selection (equivalent of R2.06/R2.08 Default Theme Standard) R3.0 Default Theme Standard (equivalent of R2.06/R2.08 Default Theme Standard) R3.0 Simple Standard (equivalent of R2.06/R2.08 Default Theme Standard)* (equivalent of R2.06/R2.08 Default Theme Standard) R3.0 Default Theme Standard *Note if you subsequently change the theme to the R3.0 Default Theme Standard and force another upgrade of the place, the upgraded place reverts to using the R3.0 Simple Standard theme. If a forced upgrade is done on a 3.0 place which uses the R3.0 Default Theme, whether it's a new R3.0 place or upgraded place, it will change to the 3.0 Simple Theme (equivalent of R2.06/R2.08 Default Theme). SPR #HDAI5FESW7 Can't preserve the R2.0x Default Theme - Standard in some rooms of the QuickPlace place after installing the 11/01/02 hot fix (Windows) Problem I install the 11/01/02 R3.0 hot fix from Build and set theme update_default_to_latest="false" in qpconfig.xml (see previous release note). When I run qptool upgrade on the QuickPlace place, the Server Settings room and Create a Place room do not retain the R2.0x Default Theme Standard as they should. This problem only occurs on the Windows platform, and if you installed the hot fix. Resolution Restore the R2.0x version of the QuickPlace place and run qptool upgrade on it again: load qptool upgrade -p quickplace. If the R2.0x version of the place is not available, do the following to create a simple agent that modifies the "h_skinname" field of the aesthetic setting document in the rooms. 1) Make a copy of all the files in < Data Directory>\QuickPlace\quickplace to back them up. 2) From the Notes client open Admin.nsf (the Server Settings room). 3) Do the following to create an agent that fixes the "h_skinname" field value: a) Choose Create - Agent from the menu. b) Type in a name for the agent i.e., "Fix Skin Name Agent". c) Leave the default value for "When should this agent run?", which is "Manually From Actions Menu". d) Leave the default value for "Which document(s) should it act on?", which is "Selected documents". e) Click "Add Action" button in the bottom to open the "Add Action" form. Leave the default value in the "Action" field, which is "Modify Field". f) Click the drop-down menu for "Field:" and choose "h_skinname". Leave "Value" empty so that it picks up the default theme later for UI display. Note: If "h_skinname" is not present in drop-down field list, then it's already set to default theme and there's no fix necessary. g) Save the agent. 4) Run the agent on aesthetic setting document: a) Go to the "System/Settings" view and select the "h_aestheticsettings" document. 18

19 b) From the top menu, select Actions- Fix Skin Name Agent. Now the agent has run on the selected document. Repeat the above steps on CreateHaiku.nsf (Create a Place room). SPR #HDAI5FPTNU Features disabled in a PlaceType are enabled in places after an upgrade (Windows only) Problem After you upgrade a Windows server from R3.0 to R3.Oa, features are enabled in a place created from a PlaceType even though the PlaceType used to create the place disables the features in places. This problem does not occur if you upgrade from R2.0x to R3.0a. Resolution After upgrading from R3.0 to R3.0a on the Windows platform, from a Notes client change the value of the fields "h_isintoc" and "h_isdisabled." The following table describes where to locate the fields and what value to specify. Note that rather than changing the fields, you can restore a backup of the place not yet upgraded to R3.0 and run qptool upgrade on the place using R3.0a. Disabled feature Document to fix How to Fix Members (in top room) h_members in top room set h_isintoc to "0" and Room Security (in inner rooms) database h_security in inner room databases Basics h_roombasics set h_isdisabled to "1" Decorate h_decorate set h_isdisabled to "1" Forms h_forms set h_isdisabled to "1" Rooms h_rooms set h_isdisabled to "1" PlaceTypeOptions h_placetypeoptions (in set h_isdisabled to "1" top room only) Custom Themes h_skins (in top room only) set h_isdisabled to "1" PlaceBots h_agents set h_isdisabled to "1" Customize (in top room) and Room Options (in inner rooms) h_tailor* set h_isintoc to "0" *Fix if all features in Customize are disabled. External User Directory "O.K. with Anonymous access" means it will use credentials Problem When setting up the LDAP user directory for the QuickPlace server with specific credentials, you notice the message "O.K. with Anonymous access" instead of "OK with credentials" when saving the settings. Resolution This is only a problem with the string presented on save. QuickPlace will access the directory using the credentials you provided. SPR #MTAI5DA7UQ 19

20 User Directory set to localhost or causes server crash Problem The administrator sets the user directory for the QuickPlace server to an LDAP directory using localhost or as the server name and you get random crashes of the server. Resolution Set the LDAP directory to the DNS name of the server. Using the string "localhost" or the address for a directory on the same machine as the QuickPlace server is not supported. SPR #MJAS5E3KVQ When a name from an external directory contains cn as its second component, by default QuickPlace converts the component to ou in place ACLs Problem When the second component of a user name in an external directory is cn, by default QuickPlace converts the cn component to ou in the ACLs of places. For example, if the distinguished name of a user in an external directory is uid=abrown,cn=users,dc=acme,dc=com, by default QuickPlace instead uses this name in place ACLs: uid=abrown,ou=users,dc=acme,dc=com. This conversion can prevent a user from signing in to the place using the name with the cn component from the external directory. Resolution This issue may be addressed in a future release. SPR #MBAS5FDKKF DBCS user name must be hierarchical in LDAP Domino directory Problem When using Domino Directory as LDAP server, flat DBCS user names cause the Domino LDAP server to crash when QuickPlace user is authenticated. Resolution DBCS user names have to be hierarchical in the Domino Directory. SPR# BTLW5ES69J Cannot add members from the user directory on Windows NT server Problem An NT Domain as an external directory choice is not supported on the QuickPlace for AIX server. SPR#MHKM54UBVL QuickPlace is not automatically aware of changes to user information in an external directory Problem When you change user information in an external directory other than user passwords, QuickPlace is not automatically aware of the changes. For example, if you change a user s address in the external directory, the QPTool sendmail command continues to send mail to the old address. Resolution The first time you add a user from an external directory as a member of a place, QuickPlace copies the user information from the directory -- with the exception of the user password -- to a user profile document in the contacts1.nsf database of the place. QuickPlace uses the profile document to determine user information such as the user's first name, last name, and address. If you change the user information in the external directory, the user or a manager of the place must open the corresponding member information page in edit mode and then save it. This triggers QuickPlace to pull the latest user information from the external directory into the contacts1.nsf database. SPR #HTTN5D39UC 20

21 250 character limit in the <search_ui_hint> There is a 250 character limit on the search_ui_hint string in the look ui dialog box which is customizable through a QPCONFIG.XML setting. SPR #MJAS5DFNVJ Directory user's information not updated until record is viewed Problem When external directory user s information is changed in the directory, the changes will not be seen if place manager opens members view (listing all members). Resolution The information is not updated until one of the following occurs: the member record is edited; the member logs in; an is sent to the member. SPR #MPUL58CGY3 You cannot add new users with automatic lookup if more than one match is found Problem The automatic lookup feature in QuickPlace takes the input string entered and searches for all possible matches in the directory. It does this by doing a wildcard search using the input string. If more than one match is found, the entry is not added to the place as a new user, and the searcher is informed that more than one match is found. For example, a search on Joan Smith finds Joan Smith and Joan Smithe. At this point QuickPlace can not add one of these entries to the place with the confidence it is adding the "correct" one, so it fails. Resolution The workaround is to use the Lookup UI to find the entry you want. SPR #HX0C0C00QP The authentication, group_lookup, and group_membership search filters take only one string as input The authentication, group_lookup, and group_membership search filters configured through the qpconfig.xml file take only one string as input -- you can specify only {0}. The user_lookup filter can take two strings as input -- you can specify {0} and {1}. SPR #HTTN5DGBVV Text in <member_lookup_ui> settings appears in ui In the <member_lookup_ui> settings in QPCONFIG.XML if text is used as prefix or suffix to the field name, then this text is also displayed in the UI of the directory lookup dialog. For example, if <member_lookup_ui> <column_name><person>sn</person></column_name> <column_disambiguate><person>mail</person></column_disambiguate> </member_lookup_ui> is changed to <member_lookup_ui> <column_name><person>carrotsnlettuce</person></column_name> <column_disambiguate><person>lentilmailasparagus</person></column _disambiguate> </member_lookup_ui> then the lookup ui appears like this: carrotjoneslettuce lentiljjones@iris.comasparagus SPR #MJAS5DFMM8 21

22 Don t use the QuickPlace XML API to create a place with an external directory group as a manager Problem The QuickPlace XML API interface incorrectly allows you to create a place using an external directory group as manager, although external groups are not supported as place managers in Release 3.0. If an external group is a manager of a place its members cannot access the place. Resolution Do not use the XML API to add external groups as place managers. SPR #TTUY5D2QGH Paging icons sometimes missing from results of user searches of a Domino Directory Problem When using broad search criteria, for example show all, to find a name in an external directory that is a Domino Directory, the icons that allow you to navigate multiple pages of results are sometimes unavailable. Resolution Narrow your search to display fewer results. SPR #AVEI5B8PB8 Using the type-in method to add users from an external directory does not always work Problem You are using the type-in method to add users from external directory and can't add users by "lastname,firstname" even though the user_lookup filter is sn,givenname. Resolution Currently when you use the type-in method to search for a name to add, you can specify only the first attribute of the user_lookup filter but not the second attribute. If just lastname finds a unique entry in the directory, the user will be added to the place correctly. (You can also add members by typing the fully distinguished name (cn=joe smith,ou=orgunit,o=org or joe smith/orgunit/org). If your user_lookup filter is uid={0} and you want to add users in the text area by uid, you must also change the search_ui_index value in QPCONFIG.XML to be uid. SPR #MJAS5DXSAV Responses to a discussion page can show the original author s full distinguished name rather than the display name Problem If a user signs into a place as a member of an external group and creates a discussion page, the author s display name (common name, by default) as configured in qpconfig.xml shows in the page. However responses other uses add to that page show the author s full distinguished name instead. Resolution When the user signs in and creates the original page, QuickPlace can retrieve the user's display name from the external directory to display in the page. However, when another user creates a response, QuickPlace looks for the author's display name in the place s contacts1.nsf database. Since the author in this case signs into the place as member of an external group, there is no information on the author stored in the contacts1.nsf database, so QuickPlace displays the author s distinguished name in responses instead. There is no workaround for this. #MJAS5DTK5D 22

23 External Membership Management between the API and UI differs Problem When you add external members through the UI, you cannot successfully do so unless you can access the external directory at the time of the operation. But using the API you are allowed to add members even though the external directory cannot be reached. This can cause problems later on when connecting because there are no indications of a problem during the membership management process through the API. Resolution Before using the API to add members from an external directory, make sure the server can connect to the directory. SPR #TTUY5D2TS4 The super user feature is not working when the Domino Directory is the user directory selection Problem The super user functionality will not work with the Domino Directory. Resolution The Domino Directory as a user directory is only supported during the upgrade process. Administrators must switch to Domino Directory with LDAP to get the 3.0 super user functionality. #MJAS5CHNRW Two users in an external directory with the same distinguished name are considered as one user in QuickPlace Problem Two users in the external directory have the same distinguished name (DN) but differ in other attributes such as uid and password. You add both users to a place and only one is added. Resolution Distinguished names in the directory must be unique. In a change from 2.0.x, duplicate users will show in the member lookup user interface. Since the two users share one DN, both will be able to sign in and will be considered the same user by QuickPlace. Add a middle initial or another distinguishing character to one of the users in the external directory so that the DNs are no longer ambiguous. SPR #MPUL5BGKUA Adding large numbers of local members Problem If your server is set up with an external directory and you try to add a large number of local members at a time, you will get an error. Resolution Add the local members in smaller batches. This problem does not exist when adding large numbers of members from the external directory. SPR #LZHG54J49J External directory user names cannot contain DN delimiters or single quote Problem QuickPlace cannot accept distinguished names which have delimiter characters, or open ended ". Delimiter characters are used in parsing DN's for legality, and this violates the name. Additionally, DN's can be sent via URL and ; and, have special meanings in URLs. Users with these names cannot be made members of a place. Resolution Distinguished names with delimiters are not supported in QuickPlace 3.0. SPR #CLEY5CPKQF A place and external directory user cannot have the same name Problem User will get a QuickPlace error if they attempt to create a place with an Internet name (not a title) which matches exactly an external directory user s name. The place gets created but you cannot log into it. Resolution This is not supported. You must use a different place title. SPR #HXBDF200QP 23