IBM Lotus QuickPlace 3.0.1

Transcription

1 IBM Lotus QuickPlace Release Notes Produced May 2003 for QuickPlace for the Windows platform Updated May 2003 to include information related to iseries platform support Updated June 2003 to include information related to UNIX platform support

2 2

3 Disclaimer THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS DOCUMENTATION, IT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS DOCUMENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS 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 IBM SOFTWARE. Licensed Materials - Property of IBM Copyright IBM Corporation 1999, 2003 All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GS ADP Schedule Contract with IBM Corp. Lotus Software IBM Software Group One Rogers Street Cambridge, MA List of Trademarks AIX, Domino, Domino Designer, IBM, iseries, Lotus, Notes, OS/400, QuickPlace, Sametime, and Tivoli are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. ActiveX, Microsoft, Outlook, Windows, and Windows NT are 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. 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. Other company, product, or service names may be trademarks or service marks of others. 3

4 Table of Contents System Requirements... 5 New Features and Enhancements in QuickPlace Fixes Incorporated in QuickPlace Upgrade Fixes Incorporated in QuickPlace 3.0a...11 Known Issues...14 Install...14 Upgrade...15 Partitioned Servers...20 Offline...20 Sametime...24 External User Directory...27 Notes.ini, qpconfig.xml, and Server Settings...35 Place Catalog...36 Places...37 PlaceTypes...44 QPTool...47 Security...50 International...54 Browser...56 Calendar...58 Other...59 Documentation Updates...63 QuickPlace Offline Q&A

5 System Requirements You must install QuickPlace on an IBM Lotus Domino server. The following table describes the current software requirements/support for QuickPlace Refer to the Domino release notes at 10.lotus.com/ldd/notesua.nsf/e18d5eb0b8be97d e50052ad16/ed9f54d b85256cd3004a891e?OpenDocument for hardware and memory requirements. Server operating systems IBM AIX 4.3.3, 5.1, 5.2 IBM OS/400 V5R1 or V5R2 (iseries ) 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 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. Note: The R Domino server is available in English only. However, you can use some of the content of international versions of Notes Clients, which are expected to be available between May and July 2003, to convert an English R server into a localized R server. A localized server is an English server with translated templates and several other translated files which provide a translated use experience. For more information, see the following link to the Lotus Developer Domain: 10.lotus.com/ldd/r5fixlist.nsf/8c4f0b18f61ab cb /5adeb0c1b6886 5

6 cb80055a8b8?OpenDocument. For instructions on configuring a Localized Server Kit, see the Domino Release Notes. New Features and Enhancements in QuickPlace The following features and enhancements are new in Release Support for partitioned servers You now can run QuickPlace on a partitioned Domino server running Windows or UNIX, in addition to an iseries server. The server must be configured for TCP/IP using IP Aliasing, not Port Mapping. Install a partitioned server then install QuickPlace on it. When you install multiple QuickPlace server partitions, each QuickPlace server is configured and run independently of the others. For information on configuring a Domino partitioned server, see Domino 5 Administration Help. Support for AIX and Solaris servers within the same cluster You now can use any combination of server platforms within a cluster. Previously you could not use AIX and Solaris servers within the same cluster. New My Places configuration settings My Places now lists places in a paged format (default 20 per page), with navigation buttons. This enhancement decreases My Places rendering time and can improve performance for users who are members of a large number of places. In addition, there are several new My Places qpconfig.xml settings you can use to filter and control the display of My Places output based on place size, membership, date of last modification or access, and anonymous access. In addition, the format of the output may be customized by specifying the number of places to display per page, which columns to display (title, size and last modified date), and whether to list the places by name in ascending or descending order. All of these settings are also configurable for one-time use through parameters appended to the My Places URL. These parameters allow end-users to generate a list of places that meet criteria they specify. For more information, see the chapter "Configuring Additional Server Settings" in the QuickPlace Administrator's Guide. New settings to specify distinguished name format There are new settings in qpconfig.xml you can use to resolve user authentication problems caused by specific formats of distinguished names. Use the dn_delimiter setting to enable QuickPlace to work with third-party authentication applications such as Netegrity SiteMinder when distinguished names in the user directory contain multi-character delimiters. Use the dn_incoming is native setting to enable QuickPlace to work with third-party authentication applications when distinguished names in the user directory use components other than the standard Domino name components cn, ou, and o. When distinguished names in the user directory contain cn as the second component, use the secondary_cn_component setting to prevent QuickPlace from converting the cn component to an ou component. For more information, see the chapter "Connecting to a User Directory" in the QuickPlace Administrator's Guide. 6

7 New settings to specify the distinguished name format of users who install places offline Administrators can use offline settings in the qpconfig.xml file to translate names in the external user directory that don't conform to the standard Domino name format so that users in that directory can take places offline. In previous releases, users could not take places offline if their names were in a format that Domino didn't recognize. For more information, see the chapter "Connecting to a User Directory" in the QuickPlace Administrator's Guide. Offline supported with Tivoli PolicyDirector and Directory Assistance Taking places offline is now supported in an environment that uses Tivoli PolicyDirector and Domino Directory Assistance. Offline supported with Netegrity SiteMinder Taking places offline is now supported in an environment with Netegrity SiteMinder. The DOLS DSAPI filter must be listed first. addmember and updatemember QPTool commands There are two new QPTool commands: addmember and updatemember. Use addmember to add external members to places. Use updatemember to update external member information in places, for example addresses, when the information changes in the user directory. For more information, see the chapter "Using QPTool Commands" in the QuickPlace Administrator's Guide. New argument for QPTool refresh You can use the -r argument with the QPTool refresh command to replace a place with its PlaceType design. Any changes made to elements directly in the place are overwritten if the elements originated from the PlaceType. New qpconfig.xml setting to clear the QuickPlace files from the browser cache Use the new clear_browser_cache setting in qpconfig.xml to clear QuickPlace temporary files from the browser cache upon user signout. For more information, see the chapter "Setting Up Security" in the QuickPlace Administrator's Guide. CGI variables no longer displayed in HTML source by default Common Gateway Interface (CGI) variables containing information about remote hosts and their users no longer display by default in HTML sources pages. Use the new cgi_variables setting in qpconfig.xml to display them. For more information, see the chapter "Configuring Additional Server Settings" in the QuickPlace Administrator's Guide. Option to initially inherit room membership from the parent room When you create a room, you can now choose to initially inherit its membership from the parent room. Previously, the only member in a new room was the creator with Manager access. For more information, see the Help. 7

8 Fixes Incorporated in QuickPlace The following tables summarize the fixes incorporated in QuickPlace Upgrade fixes SPR# HDAI5HKPT2 QPTR5K44TQ MJAS5KJSRJ RTAG5K7KEW THES5GYJJ3 Fix description Fixed upgrade problem when switching from Domino to LDAP directory where external groups from a place which were in the Domino directory but not in the LDAP directory caused the external groups view of contacts1.nsf to be corrupted and prevented members from signing into their places. Fixed problem in upgrading from 2.0.x where the QuickPlaceAdministratorsSUGroup added to the place databases was not given delete privileges, so the Super User could not delete any content from a place. If an upgrade to 3.0 or 3.0a created a QuickPlaceAdministratorsSUGroup on the place ACLs without delete privileges, qptool repair on the places will give the group delete access again and Super Users should be able to delete content in places. Fixed potential performance problem where the QuickPlace server was mistaking 3.0 and 3.0a places for 2.0.x places. Fixed a problem where switching from local users to an LDAP directory resulted in unassigned tasks when QP 2.08 places are upgraded to 3.0 QPTool command fixes SPR# Fix description QPTR5KS932 Fixed problem where qptool changehierarchy did not adjust security fields (e.g., h_readers and h_authors fields) for members of external groups since the command checked for member records in contacts1.nsf. Fixed similar problem with qptool changemember. MJAS5KMLPC QPTool repair fixes a problem whereby members could not read their own draft documents after changemember had been run. Offline fixes SPR# MJAS5KUPKG JNES5CLG8D JNES5C7Q66 JNES5CYGLZ continued Fix description Fixes a problem where administrators had lost Notes access to place databases through QuickPlaceAdministratorsSUGroup when the Offline feature was enabled. Note: This problem is not fixed on the UNIX platform. Fixed a problem where external users were unable to send from offline due to problem with Domino case-sensitive string compare Fixes a problem with intermittent crashes occurring after offline installs Fixes a problem that prevented offline installs when using Policy Director 8

9 SPR# QPTR5KKCKN JNES5F7Q8U JNES5JESF2 JNES5GQNVE Fix description Fixes a problem where user was prompted for notes ID during offline install as Multi-valued RDN with UID. Fixes a crash problem that occurred when a user does not set offline password Fixes a problem where iplanet distinguished names don't work with DOLS. The fix involves using name translation rules configured in the offline section of qpconfig.xml. For more information, see the chapter "Connecting to a User Directory" in the QuickPlace Administrator's Guide. Fixes a problem where Active Directory users cannot install offline. The fix involves using name translation rules configured in the offline section of qpconfig.xml. For more information, see the chapter "Connecting to a User Directory" in the QuickPlace Administrator's Guide. External User Directory fixes SPR# Fix description BTLW5ES69J Fixed crash problem when authenticating as a flat, double byte character set (DBCS) name from a Domino LDAP directory. SSEI5JER4B New dn_incoming_is_native and dn_delimiter settings in qpconfig.xml fixes authentication problem with QuickPlace configurations using Netegrity Siteminder and users with either distinguished names beginning with UID or with a component delimiter other than "," or ";". MBAS5FDKKF Fixed a problem where the QuickPlace server was changing distinguished names such as uid=1234,cn=joe Smith,ou=Sales,o=Org into uid=1234,ou=joe Smith,ou=Sales,o=Org which caused single sign on to fail. There is now a new qpconfig.xml setting, secondary_cn_component, to prevent the conversion. See the Administration Guide for details. MPUL58CGY3 Fixed problem where external member information was only updated when a- member profile was updated. Administrators will now use the new qptool updatemember command to synchronize QuickPlace data with the external directory. JRUO5FTSW2 Fixed a problem where QuickPlace was not properly handling external user names with "\," in the distinguished name. HDAI5FMUTZ Fixes a probem where What's New displayed membership info for non-members who are directory users SBRN5J7VKT Fixed a problem where flat named users from a Domino LDAP directory could not view or edit pages for which the author of the page had given reader or editor privileges, respectively. MJAS5KSQ5U Fixed the ability to explode external groups in the notify scene for non-domino LDAP directories. 9

10 Place fixes SPR# MJAS5HRQ8Z QPTR5JPAK3 MJAS5DTK5D TESA5KB45F GWA20C00QP HDAI5HYLB2 TESA5G8N9B WWAG54MJZQ CFAL5GVJB8 MPUL5G3MYR MESA599KRT RSCR5GQC82 RSCR5DXE3J Fix description You will no longer see the warning, "Checking this option will mail your password over the network for external users" when adding an external user to a place. For local users only, you will get a dialog box stating that the password will be sent over the network. Fixed a problem that prevented anonymous users from using the Advanced Search feature. Fixed a problem where member names were displayed with a value other than display_name as set in qpconfig.xml. If the server does not have a qpconfig.xml file or the server administrator has not changed the defaults for user and group display_name, member names will be displayed as the cn component of the distinguished name. The only exception to this is in the members view and on the member profile page where common_name as set in qpconfig.xml (or cn component of the distinguished name as the default) is shown. Fixed problem where What's New was not showing the "added by" value for the user who made the change. Fixed problem for multiple imported pages where author's full name was only on last imported page. Fixed problem where publishing a page based on a custom form returns the user to the page instead of the folder list. Fixed "invalid recipient" errors when assigning tasks or creating a page based on a form with workflow with Active Directory users. Fixed a problem where folders reported the wrong number of documents when parent/child docs are moved out. Fixed a problem where users unable to sort by column "Due Date" Fixed a problem where toggling Room Security options resulted in all user access levels not displayed to Readers and Authors Fixed error which occurred when publishing a page based on a custom form for which the form designer changed the case of a field name in a subsequent edit of the form. Rooms now have the option of inheriting their initial membership from the parent room. Fixed a problem where author's full name was only on last imported page by fixing HuUiDoc.cpp:SetAlternateNameToCurrentUser( ) to use the displayname as the alternate name 10

11 International fixes SPR# Fix description MPUL5JQJT6 Fixed qptool changemember problem where it failed on members starting with uppercase Baltic characters MHKM5FWDSH Used UTF-8 encoding to fix problem searching for double byte character strings across places. TCHU5J9DY4 TCHU5DWJNU XML API fixes SPR# KHIA5GZQ9Q TTUY5JFQBK KHIA5J3PCD Other fixes SPR# MGAR5CKNLZ TEDS5K5UD9 Fixed problem downloading a file attachment if the filename contained a character represented by two code points. Fixed a problem where enabling UTF8 resulted in garbage characters displayed in user created Themes. Fix description Fixed problem where removing a member through the XML API was failing. Fixed a problem where we were not returning the proper failure message when creating a person with an empty DN via the XML API. Fixed problem where get_member_places in the XML API did not return date/time values in ISO8601 format Fix description More information given in qpconfig_sample.xml for configuration parameters for the URL needed for a custom portal implementation of <my_places>. Fixed a problem where Sametime view menu and change status menu options did not work correctly Upgrade Fixes Incorporated in QuickPlace 3.0a QuickPlace 3.0a fixed several problems related to upgrades, which are now incorporated in release If you are bypassing release 3.0a and upgrading from 2.X or 3.0 directly to 3.0.1, some of these fixes require additional steps to implement them. These steps are described in the following table. SPR # Description Additional steps necessary 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. If you upgrade from R3.0 to R3.01, this fix requires you to complete these steps after the upgrade: 1. Restore a backup of the affected 2.0X places 2. Run qptool upgrade on the affected places. continued 11

12 SPR # Description Additional steps necessary CDUY5F9PHC Fixes a problem where places using the classic theme changed to the QuickPlace 3.0 default theme after an upgrade If you upgrade from R3.0 to R3.0.1, after the upgrade run qptool upgrade on the affected places HDAI5F9UBK HDAI5F9QBX HDAI5FE23D JNES5FFN59 WQUN5ERQJQ JALS5ECPHY CLEY5F6K6T continued 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 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 If you upgrade from R3.0 to R3.0.1, after the upgrade run qptool upgrade on the affected places If you upgrade from R3.0 to R3.0.1, after the upgrade run qptool upgrade on the affected places If you upgrade from R3.0 to R3.0.1, after the upgrade run qptool upgrade on the affected places If you upgrade from R3.0 to R3.0.1, after the upgrade run qptool upgrade on the affected places If you upgrade from R3.0 to R3.0.1, recreate the customizations in the folder. If you upgrade from R2.X to R3.0.1, 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 from R2.0x to R3.0.1" in the "Known Issues - Upgrade" section of the release notes. Alternatively, you can restore a backup of the place not yet upgraded to and run qptool upgrade on the place using R If you upgrade from 3.0 to 3.0.1, after the upgrade run qptool upgrade on the QuickPlace place, i.e.: load qptool upgrade -p quickplace 12

13 SPR # Description Additional steps necessary HDAI5FESW7 Fixes a problem where a place created in R2.0x without an explicit theme selection changed to the default R3 theme after an upgrade To preserve the 2.0x theme selection: 1. Upgrade the QuickPlace server to 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 theme after an upgrade" in the "Known Isses - Upgrade" section of the release notes. SSEI5FTP9C 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). If you upgrade from R3.0 to R3.0.1 and you did not run qptool upgrade on a place in R3.0, you can do so in R3.0.1 without problems. If you ran qptool upgrade on a place in R3.0 after changing to an LDAP directory and then upgrade to R3.0.1, 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" 13

14 Known Issues The known issues are categorized as follows: Install Upgrade Partitioned Servers Offline Sametime External User Directory Notes.INI, QPCONFIG.XML and Server Settings Place Catalog Places PlaceTypes QPTool Security International Browser Calendar Other Documentation Updates Install 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. This problem does not occur with iseries servers. Resolution Change display setting to 256 color or higher. SPR #KHIA5DTQ4P Uninstall QuickPlace before installing a different Domino version QuickPlace works only on a Domino server. If you want to install a later release of Domino, uninstall QuickPlace BEFORE installing another version of Domino. SPR #JNES5CXN9S Specifying a QuickPlace administrator name that is a name in the external user directory causes problems Problem When prompted during install for the name of a QuickPlace administrator, if you specify a name that is the same as one in the external user directory, the user encounters problems such as not being able to see My Places. Resolution During install specify a QuickPlace administrator username that is not used in the external directory. SPR #LWOY5E3J76 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 14

15 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 Upgrade iplanet and SecureWay directory users can't install offline after an upgrade from R3.0a to R3.01 Problem After upgrading from R3.0a to R3.01, users in an iplanet or SecureWay directory can't install places offline. Resolution Run the qptool repair command on the places which have this issue. Users should then be able to log on. For information on the qptool repair command, see the QuickPlace Administrator's Guide. SPR #QPTR5LXBJE External user whose name contains an LDAP delimiter and space delimiter can no longer log in to 3.0a place Problem An external user or group added to a 3.0a place whose distinguished name contains a comma space delimiter (or other LDAP delimiter with a space) can no longer log in to the place after an upgrade to Resolution Run the qptool repair command on the place to fix the names in the place. SPR #QPTR5LNBK9 Changehierarchy and removemember commands not working on a 3.0a place when external names use an LDAP delimiter and space delimiter Problem External users or groups added to a 3.0a place whose distinguished names contain a comma space delimiter (or other LDAP delimiter with a space) are not affected by the qptool changehierarchy or removemember commands after an upgrade to The commands work on the names on a 3.0a server. Resolution Run qptool repair on the affected places to fix the names. For information on the qptool repair command, see the QuickPlace Administrator's Guide. SPR #QPTR5LXE78 Super user name containing international characters is not deleted after an upgrade from R2 Problem A super user whose name contains international characters is not deleted from places after you upgrade from R2 to R3. Resolution Do any of the following: Before upgrading to R3, disable Super User or change to a Super User without international characters using the Admin Utility. Then enable Super User through qpconfig.xml after upgrading to R3. Enable a R3 Super User through qpconfig.xml after upgrading, sign in as the new Super User, and delete the old Super User entry in each place. Write a Domino agent to delete the Super User document from each Contacts1.nsf database and from the ACL on Main.nsf, Contacts1.nsf, and PageLibraryxxx.nsf files for all places on the server. SPR #QPTR5LV982 15

16 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 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 Users whose place access is controlled through membership in an external group cannot access pages or rooms after an upgrade from R2 to R3 Problem Users whose place access is controlled through membership in an external group can no longer access pages or rooms after you upgrade the place from R2 to R3. Resolution This problem occurs because the names of the members of the group are not upgraded to the R3 native directory format because they aren't stored in the Contacts1.nsf database of the place. Instead members of external groups are stored in security fields in the place, such as in h_authors and h_readers fields. For example, the name of a user cn=jane doe,o=acme in the user directory whose access to a place is controlled through an external group, is stored in the h_authors field of a page she created as cn=jane doe/ou=placename/ou=qp/o=dominocertifier because QuickPlace R2 converted the native LDAP names to the scoped QuickPlace names. QuickPlace R3 now stores the names in the native LDAP format. To correct the problem, change these R2-formatted names in a place to the format in which they appear in the user directory. To change the name of one user, use the qptool changemember command, specifying R2 formatted name as the source name and the name used in the directory as the target name. For example, specify: >load qptool changemember -p place1 -sourcedn "cn=jane doe/ou=place1/ou=qp/o=acme" -targetdn "cn=jane doe,o=acme" Or to change the names of multiple users that are in the same name hierarchy in the user directory, use the qptool changehierarchy command. Only use changehierarchy if there are no local members of the place. For example, specify: >load qptool changhierarchy -p place1 -sourceh ou=place1/ou=qp/o=acme -targeth o=acme SPR# QPTR5KS932 Upgrading servers that run IIS Problem I have an existing server that runs with IIS, but IIS is not supported in QuickPlace 3. Resolution Because IIS is no longer supported in QuickPlace 3, if you are upgrading QuickPlace server running with IIS, you must make the following changes before you start the QuickPlace 3 server. 1. Remove the QuickPlaceIIS=1 setting from NOTES.INI 2. Add 'HTTP' task to the ServerTasks settings in NOTES.INI 16

17 No browser error when you attempt to refresh a PlaceType before it is upgraded If you have upgraded your server from R2 to R3, 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. Child place does not inherit unchecked "Online Meeting" from source place after an upgrade Problem If you upgrade a child place created in R2.08, and next upgrade the source place and the PlaceType, if you later uncheck "Online Meeting" in the source place, refresh the PlaceType, and then refresh the child place, the child place does not inherit the change -- "Online Meeting" remains checked. Resolution To work around this problem, upgrade the source place first, then the PlaceType, and last the child place. Or uncheck the "Online Meeting" setting manually in the child place. SPR #HDAI5HUPTK Upgrade places before PlaceTypes, and tell administrators not to refresh PlaceTypes until they are upgraded When upgrading places and PlaceTypes from R2 to R3, 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. 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 Release 2, the sort column reverts to the Title column after you upgrade to Release 3. 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 17

18 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 Release 2 no longer works. Resolution The following example shows how to correctly create a new QuickPlace from a URL in Release 3. 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 h@acme.com,h_setreturnurl; th;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 from R2 to R3, 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 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 to R3? 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 Standard Default Theme. The following table provides examples of upgrade outcomes, depending on R2.06/R2.08 theme selections and the upgrade settings. 18

19 Theme selection in R2.06/R2.08 Default Theme Steel selected Default Theme Standard explicitly selected No selection When you set them update_default_to_ latest="true" R3 Simple Steel (equivalent of R2.06/R2.08 Default Theme Steel) R3 Simple Standard (equivalent of R2.06/R2.08 Default Theme Standard) R3 Default Theme Standard Theme after upgrade When you set theme update_default_to_ latest="false" R3 Simple Steel (equivalent of R2.06/R2.08 Default Theme Steel) R3 Simple Standard (equivalent of R2.06/R2.08 Default Theme Standard) R3 Simple Standard (equivalent of R2.06/R2.08 Default Theme Standard)* When you do not specify in qpconfig.xml R3 Simple Steel (equivalent of R2.06/R2.08 Default Theme Steel) R3 Simple Standard (equivalent of R2.06/R2.08 Default Theme Standard) R3 Default Theme Standard *Note if subsequently you change the theme to the R3 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 R3 place which uses the R3 Default Theme, whether it's a new R3 place or upgraded place, it will change to the R3 Simple Theme (equivalent of R2.06/R2.08 Default Theme). SPR #HDAI5FESW7 Features disabled in a PlaceType are enabled in places after an upgrade from R2.0x to R3.0.1 (Windows only) Problem If you upgrade a Windows server from R2.X to R3.O.1, features may be enabled in a place created from a PlaceType even though the PlaceType used to create the place disables the features in places. Resolution After upgrading from R2.X to R3.0.1, 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 values to specify. Note that rather than changing the fields, you can restore a backup of the place not yet upgraded to R3.0.1 and run qptool upgrade on the place using R 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" 19

20 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. Partitioned Servers Can't uninstall a specific QuickPlace server on a partitioned server Problem When you have multiple QuickPlace servers installed on partitioned servers, when you use the uninstall program to uninstall QuickPlace, all the QuickPlace servers are uninstalled. This limitation does not apply to iseries servers. Resolution This is a limitation for this release. SPR #QPTR5K6BUA Can't reinstall QuickPlace on a partitioned server after previously uninstalling Problem If use the uninstall program to uninstall QuickPlace, if you then re-install QuickPlace on a partitioned server that was not the last partitioned server installed on the computer, you get a message indicating that QuickPlace is already installed and asking you whether to upgrade or install in a different location. Resolution This is a limitation for this release. SPR #WS4BAE00QP Offline Note: See "QuickPlace offline Q&A" at the end of these release notes for answers to common questions about configuring QuickPlace for offline use. Hotfix required for offline use To support offline use, you must install a hotfix provided in the \DOLS directory on the QuickPlace CD or Web kit. For more information, see the QuickPlace Installation and Upgrade Guide. Offline use in a Netegrity SiteMinder environment In R3.0.1 you can use the Offline feature in a Netegrity SiteMinder environment. To do so, you must list the DOLS DSAPI filter first in the list of DSAPI filters on a server enabled for offline use. The DSAPI filters are listed in the "DSAPI filter file names" field on the Internet Protocols - HTTP tab of the Server document in the Domino Directory. 20

21 New rooms not installing to offline place during sync Problem When you install a place offline, DOLS installs any rooms that are part of the place. However, if new rooms are then added to the online place, those rooms do not get downloaded offline during subsequent synchronizations. Resolution Do the following to download the new rooms to the offline place: 1) Open the place online. 2) Click "Work Offline" in the table of contents. 3) Check the rooms you want to synchronize offline. 4) Complete synchronization. SPR#THES5LGQLD and #MCUN5GKHNA Offline users can't edit their member profiles when Sametime is enabled and the place name begins with "QuickPlace" Problem If you've enabled Sametime integration with QuickPlace, users cannot see the View Profile link in the Members view needed to set their offline passwords in member profiles if the name of the place begins with the string "QuickPlace." Resolution To work around this problem, temporarily disable the chat functionality and use qptool register -install to rename the place to begin with something other than "QuickPlace." Or, leave chat active and add the offline password by clicking on the author link of a page and then clicking the View Profile menu link to bring up the member profile. SPR #MPUL5F6LNZ Users with flat names can't take places offline Problem Users with flat names (name without distinguishing components) can't take places offline. Resolution You can use the offline name_translation setting in qpconfig.xml to correct this problem. The following example translates flat names to the hierarchy OU=flatname,O=acme: <offline enabled="true"> <name_translation enabled="true"> <from_directory_name> <!-- Translate flat name to one in "OU=flatname,O=acme" hierarchy --> <translate from="^([^/=]+)$" to="cn=\1/ou=flatname/o=acme" /> </from_directory_name> <to_directory_name> <translate from="cn=(.+)/ou=flatname/o=acme" to="\1" /> </to_directory_name> </name_translation> </offline> The "^([^/=]+)$" expression in the regular expression matching the flat name means one or more occurrences of any character except a forward slash (/) or an equal sign (=). For more information on name_translation setting, see the chapter "Connecting to a User Directory" in the QuickPlace Administrator's Guide. SPR #JNES5DHDU8 Offline user whose common name contains a period (.) prevents other users from opening a place offline Problem When an offline user (either local or external) whose common name contains a period (.) installs a place offline, other offline users cannot install and open the place offline. 21

22 Resolution To correct the problem, use the offline name_translation setting in qpconfig.xml to translate a period in any common name to something else. For example, specify the following in qpconfig.xml: <offline enabled="true"> <name_translation enabled="true"> <from_directory_name> <!-- workaround for dot (.) in name: --> <!-- For external users in the "ou=people1,ou=acme" hierarchy: --> <translate from="cn=(.+)\.(.+)/ou=people1/o=acme" to="cn=\1_dot\2/ou=people1/o=acme" /> <!-- Generic translation rule for local users in any Quickplace: --> <translate from="cn=(.+)\.(.+)/ou=(.+)/ou=qp/o=(.+)" to="cn=\1_dot\2/ou=\3/ou=qp/o=\4" /> </from_directory_name> <to_directory_name> <translate from="cn=(.+)_dot(.+)/ou=people1/o=acme" to="cn=\1.\2/ou=people1/o=acme" /> <translate from="cn=(.+)_dot(.+)/ou=(.+)/ou=qp/o=(.+)" to="cn=\1.\2/ou=\3/ou=qp/o=\4" /> </to_directory_name> </name_translation> </offline> For more information on this setting, see the chapter "Connecting to a User Directory" in the QuickPlace Administrator's Guide. SPR #QPTR5KQ45T Offline users with translated names can't send from a place Problem When you use the name_translation setting in qpconfig.xml, offline users whose names are translated cannot send from a place. Resolution A fix will be considered for a future release. SPR:JNES5KKKJT A user who installs offline to Windows 2000 client is prompted for Web Application password Problem A user who installs a place offline to a Windows 2000 client gets prompted to supply a Web Application password. Resolution Enter your offline password and confirm it and Offline install will complete. This is the correct behavior if you are running multi-server session based authentication, client certificate SSL, or any other internet authentication security where the internet password is not available to the DOLS download control when you go offline. SPR #QPTR5K7QTJ Offline not supported for user names with accented characters Problem When a user's name in a place contains accented characters, for example "aà", the user cannot install the place offline and sees an error when attempting to do so. Resolution Do not add user names with accented characters to places that are used offline. SPR #YH253900QP 22

23 To take places offline using Directory Assistance, start nhttp before Domino To take places offline with DOLS in an environment using Directory Assistance, you must start the notes http task before starting the Domino server. To do this, do the following: 1) Open a command prompt. 2) Navigate to the Domino program directory. 3) Enter the command: nhttp. The Domino http task starts. 4) In a separate command prompt, enter the following command: nserver. The Domino server starts. SPR#SBRN5F8REJ External users in group only cannot access rooms offline Problem Offline External user only listed in the ACL of a room via an external group is unable to enter said room when offline. Resolution This is a Software Limitation. A fix will be considered for a future release. SPR #JNES5C7PP8 Offline not working for external users after changemember or changehierarchy commands used Problem After using the QPTool changemember or changehierarchy command, the offline functionality is not working for the affected users. Resolution Before using the changemember command to change a user or the changehierarchy to change several users, instruct the affected offline external users to synchronize data. After you run changemember or changehierarchy, you must reinstall the offline places. SPR #MJAS5DGNEH Offline is not working for a super user Offline functionality is not supported for a super user SPR #JNES5D7GDH Taking a place offline with PolicyDirector Using the Alt Download URL with PolicyDirector is recommended to take places offline with PolicyDirectory, so that offline downloads come from a server dedicated to downloads. SPR #JNES5BNEL2 Offline problems if EXTMGR_ADDINS=nqpextmgr.dll is not set in notes.ini Problem If EXTMGR_ADDINS=nqpextmgr.dll is not set, this may cause problems for Authors and Readers. Contacts and Rooms will not replicate to the client if an Author or Reader is not a member by name. Resolution Add EXTMGR_ADDINS=nqpextmgr.dll. SPR #KHIA5BZ4EE Error occurs while trying to download druser.id Problem Offline load qp as a member of external group: when installing offline, an error occurs while trying to download druser.id Resolution Users who are members of a place via an external group cannot go offline; they need to be added explicitly to the place. SPR#: JL8C6D00QP 23

24 Installing QuickPlace offline on Windows XP Professional Problem Users on a Windows XP Professional client computer cannot install places offline using DOLS. Resolution The place must be installed by a user with administrative rights to the workstation (an administrator). Once the place is installed, a user with limited rights or guest rights can use the place. The same is true for Windows NT and Windows 2000 client platforms. NOTE: Microsoft Windows XP Home Edition is not supported. SPR#: JNES5HKJ8K Offline author/reader see sync errors in LiSM sync status line Problem Offline author and offline reader see sync errors in Lotus inotes Sync Manager (LiSM) when they complete a time sync for the first time, and every time they sync thereafter. Author sees this error: Last sync status: Sections:2 - Errors:1 - Docs Received:0 - Docs Sent:0 Reader sees this error: Last sync status: Sections:2 - Errors:2 - Docs Received:0 - Docs Sent:0 Resolution These errors are expected. They are due to ACL limitations on Authors and Readers in the QuickPlace ACLs. QuickPlace Authors and Readers who install offline may see errors during synchronization; this is due to the fact that the offline sync manager pulls and pushes information to the source server. Authors and Readers may NOT be allowed to write information to the server in certain cases. SPR#: JNES5AFP8X Offline: Cannot install places with the same name from two different servers Problem If a user installs two offline places that have the same name from two different servers, only the most recently installed place will open offline; the other offline place is unusable. Resolution This is a known limitation of DOLS (Domino offline Services). SPR#: JNES5AKF9B User must fill in offline password Problem Users who forget to fill in their Offline Passwords in their Member Records cannot install offline and they see an Error 500 message. Resolution Make sure that users who plan to go offline add Offline Passwords to their Members Records. SPR: JNES5A8EAC Sametime Online awareness not working for users whose sign in names contain accented characters Problem Online awareness does not work for users who sign in using names that contain accented characters. Resolution Users should sign in with names that do not contain accented characters. SPR #QPTR5LVCUW Users have trouble scheduling meetings from a place Problem Users can't schedule meetings from a place, although they can schedule meetings directly from Sametime. Resolution This problem can have a variety of causes, some of which are: 24

25 The name used for integration with Sametime and QuickPlace in stconfig.nsf is not in the [SametimeAdmin] role. Add the user name to the role. The password for the user name is mistyped in qpconfig.xml. Correct the password in qpconfig.xml. Sametime uses the Domino Directory over NRPC but QuickPlace uses an LDAP directory. Correct by using the LDAP directory for both products. You've restarted the Sametime server but haven't restarted QuickPlace. Restart QuickPlace after restarting the Sametime server. SPR#WQUN5JRM7K Users have trouble scheduling meetings on an AIX server Problem Users can t schedule meetings from a place on an AIX server. Resolution To correct the problem, try the following: 1. Make sure that the STCore.jar, STMtgManagement.jar, and ibmjsse.jar files are in /opt/lotus/notes/latest/ibmpow. 2. The JavaUsersClasses line in the notes.ini file must be less than 256 characters. This limitation may require that you create symbolic links to the.jar files mentioned above. To create the links, create a directory called 'x' and create the symbolic links to those files there. Then, in the notes.ini javauserclasses path, use /x/stcore.jar instead of /opt/lotus/notes/latest/ibmpow/stcore.jar. For example use: JavaUserClasses=/x/STCore.jar:/x/STMtgManagement.jar:/x/ibmjsse.jar rather than: JavaUsersClasses=/opt/lotus/notes/latest/ibmpow/STCore.jar:/opt/lotus/note s/latest/ibmpow/stmtgmanagement.jar:/opt/lotus/notes/latest/ibmpow/ibmjs se.jar 3. Make sure your settings in the qpconfig.xml file are correct for your meeting server, and that the ACL of STConfig.nsf on the sametime server has the roles necessary for that user to create meetings. See the instructions for configuring Sametime in the QuickPlace Installation and Upgrade Guide. 4. Make sure that you are not using SSL (https) in the URL for the meeting server (Server Settings, Other Options). SPR #QPTR5MQ5Y6 "Join the Meeting" button not working for Macintosh users Problem Macintosh users can see the "Join the Meeting" button but the button doesn't work. Resolution The "Join the Meeting" feature is only supported on Windows clients for this release. SPR #QPTR5JVBA8 External users with flat names cannot join online meetings that they publish Problem External users that have flat names cannot join online meetings that they publish. Resolution Users who publish online meetings in a place should have names with distinguishing components rather than flat names. SPR #QPTR5LLBU8 25