These release notes contain important information available at the time of the version 5.0p3 release of iPlanet Calendar Server 5.0. New features and enhancements, installation notes, known problems, and other late breaking issues are addressed here. Read this document before you begin using iPlanet Calendar Server 5.0p3.
These release notes can be found at the iPlanet documentation web site: http://docs.iplanet.com/docs/manuals/calendar.html. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.
For complete information, refer to the iPlanet Calendar Server 5.0 documentation at http://docs.iplanet.com/docs/manuals.iPlanet Calendar Server 5.0p3 includes the following features:
Horizontal Scalability Calendar Express 5.0p3 Free-Busy Search and Group Views Group Scheduling Resource Scheduling On-Behalf-of-Owner Scheduling Customization Tips & Programmer's Reference Horizontal Scalability
Supports hundreds of thousands of users through a scalable networked server-to-server, client server architecture. Supports Horizontal scalability to allow de coupling of iPlanet Calendar Server 5.0 to many front end servers with back end servers.
Calendar Express 5.0p3
iPlanet Calendar Express 5.0 allows users to publish their calendars on the web and provide a URL to their calendar. Users can export their calendar data in iCalendar or XML formats. iPlanet Calendar Express supports text based searches for events and tasks. Integration with the Event Notification Server 5.0 (ENS 5.0) will extend capability to wireless devices. iPlanet Calendar Express is accessible from wireless phones via a WAP gateway. It will also be supported on wireless devices including group scheduling via wireless phones. Calendars can be printed from the day, week, month, and year views.Added in the iPlanet Calendar Express 5.0p3 release is the ability to lookup calendar users from the user/group directory server when creating events. Also new is the ability to Accept or Decline all invitations when viewing the Invitations/Tasks box.
Free-Busy Search and Group Views
The server supports a FreeBusy search feature on multiple calendars. Calendar Express 5.0 also offers side-by-side group comparison views for a set of calendars to help with group scheduling.
Group Scheduling
iPlanet Calendar Server 5.0 is designed to perform Group Scheduling. In particular, Calendar Express 5.0 allows a user to create an event to which other Attendees are invited. The Attendees can accept or decline invitations. Attendees are typically people on the same calendar server, but this is not an absolute requirement. When iPlanet Calendar Server 5.0 detects that an Attendee is not on the calendar server, it can send the scheduling message (a request, reply, and so forth) via email as an IMIP message. This allows Calendar Express 5.0 users to schedule with Outlook users. Users can:invite others to events accept and decline events put invitations directly into a calendar, or send them via email view free/busy information for attendees of an event compare a group schedule (view attendees' schedules side-by-side) Resource Scheduling
Conference rooms, overhead projectors and other resources can be managed and scheduled using Calendar Express 5.0. Each resource is associated with its own calendar. In iPlanet Calendar Server 5.0, a calendar can also be configured to enable or disable the double book option. By default, a calendar associated with a resource has this option disabled, and a person's calendar has the double booking enabled by default.On-Behalf-of-Owner Scheduling
The Access Control model implemented in iPlanet Calendar Server 5.0 allows the owner of a calendar to specify another user as an owner that can act of behalf of them. For example, an executive can designate an administrative assistant as an owner, enabling the assistant to have complete access to all of the executive's calendars or any set of chosen multiple calendars. The administrative assistant can create group meetings on behalf of the executive and can accept or decline meetings on behalf of the executive. The executive can then decide not to give access to a personal calendar.Limited Virtual Domain Support
Virtual Domain support provides portals and ISPs a way to host multiple calendar sites on the same calendar installation. Full virtual domain support is scheduled for iCS 5.1, however. a limited subset of virtual domain functionality is included iCS 5.0. This Early Implementation functionality may allow customers to implement their virtual domain solutions in a limited fashion. If you would like to further investigate the use of this limited virtual domain capability contact your iPlanet Technical Support representative through your normal support channel.
See Technote #20010213-2.
This section contains important information you should know before installing the product. For complete installation related information and instructions, refer to the iPlanet Calendar Server Installation Guide.Hardware Requirements
The minimum hardware requirements for iPlanet Calendar Server 5.0 are:Approximately 500 MB of disk space for a standard installation. For production systems, you should plan at least 1 GB to support the product binaries. 128 MB of RAM. For production systems, you should have between 256 MB to 1 GB of RAM for best performance.
RAID storage for fast access (optional).Supported Platforms
iPlanet Calendar Server 5.0p3 supports the following operating systems at the appropriate version and patch levels:Solaris 2.6 and Solaris 8 (SPARC) require patches from the table below and can be obtained from your service provider or downloaded from the Web.
The number in parenthesis in the Solaris Version column is the output from the command 'uname -r' on that version of Solaris. The two digit number following the dash in each Patch Id is the revision of hat patch. The table lists the minimum patch revisions required by this release of the JDK and JRE; later revisions are acceptable. It is recommended that Libthread patch be applied last. In addition to the patches listed here, you may also want to install the latest patch cluster for your version of Solaris, which includes additional recommended and security patches. Solaris patch clusters are available for download on the Web; follow the appropriate links starting at http://sunsolve.sun.com.
Solaris Version PatchID Note Description 2.6 (5.6) 107733-09 required Linker Patch 2.6 (5.6) 105568-22 required Libthread Patch 2.6 (5.6) 105210-33 required LibC Patch 2.6 (5.6) 106040-15 required X Input & Output Method Patch 2.6 (5.6) 105633-50 required (1) OpenWindows 3.6: Xsun Patch 2.6 (5.6) 106409-01 required (2) Fixes the Chinese TrueType fonts 2.6 (5.6) 108091-03 required (3) SunOS 5.6: ssJDK1.2.1_03 fails with fatal error in ISO8859-01 Locales 2.6 (5.6) 105181-25 recommended Kernel Update (socket close/hang) 2.6 (5.6) 105669-10 recommended CDE 1.2: libDTSvc Patch (dtmail) 2.6 (5.6) 105284-37 recommended Motif 1.2.7: Runtime library patch For Solaris 8 Please install the latest "Recommended & Security Clusters" patch downloaded from http://sunsolve.sun.com (dated Oct. 19, 2000 or later in the patch readme file). Solaris Version Patch ID Note Description 8 (5.8) 109137-01 required SunOS 5.8: /usr/sadm/install/bin/pkginstall patch 8 (5.8) 109320-01 required SunOS 5.8: LP patch 8 (5.8) 108974-09 required SunOS 5.8: sd and uata driver patch 8 (5.8) 108977-01 required SunOS 5.8: libsmedia patch 8 (5.8) 108968-02 required SunOS 5.8: vol/vold/rmmount patch 8 (5.8) 108975-04 required SunOS 5.8: /usr/bin/rmformat and /usr/sbin/format patch 8 (5.8) 108528-06 required SunOS 5.8: kernel update patch 8 (5.8) 108875-07 required SunOS 5.8: c2audit patch 8 (5.8) 108652-24 required X11 6.4.1 Xsun patch 8 (5.8) 109951-01 required SunOS 5.8: jserver buffer overflow 8 (5.8) 109783-01 required SunOS 5.8: /usr/lib/nfs/nfsd patch 8 (5.8) 108879-04 required Solstice AdminSuite 3.0.1: Auditing, 'compat' in nsswitch.conf 8 (5.8) 108985-02 required SunOS 5.8: /usr/sbin/in.rshd patch A list of recommended patches can be found at http://access1.sun.com/patch.recommended/rec.html.
- Windows NT 4.0 with Service Pack 5
Note: On slower processor (200mhz or less) NT machines, the "start-cal" command might time-out. If this is the case then the iCS
services need to be started manually through Control Panel: Services
- HP/UX 11.0
Please see the notes concerning HPUX installation under the Known Problems and Limitations section of this document.
Configurable Kernel Parameters Description New Settings max_thread_proc maximum threads per process 8192 nkthread maximum threads in system 32768 maxdsiz max data segment size limit, heap memory use 1 GB (0x040000000) maxtsiz max text size use 64 MB (0x04000000) maxfiles_lim max number of open files per process 32768 nfile max number of files system wide 65536 ninode max number inodes in memory 32768 Use HP system administration tools (sam, kmtune) to modify the kernel, or if you want to do it manually, follow this procedure: Edit the file /stand/system to modify the kernel parameter you're interested in. This must be done with some care, the parameter must be listed exactly by name. Run 'mk_kernel -o /stand/vmunix'. This builds the new kernel, kernel function set, and marks the kernel for replacement on reboot. Reboot the system.
These numbers should serve as a baseline for kernel tuning. For our testing we used an HP 9000 machine with 2 Gb physical memory and 2 Gb swap.
Install the latest patch bundles available for your system from http://hp.com.
- AIX 4.3.3 (not currently supported)
Software Requirements
For Calendar Server 5.0p3, the following Netscape Communicator and Microsoft Internet Explorer versions are recommended:
Data Migration
From iCS 2.x to 5.0 -
A Migration tool is also available to sites with previously installed iCS 2.x. This tool provides data migration for calendar databases as well as for LDAP user preferences. Before using this tool, users should use csuser reset <userid> to clean up previous migration data on LDAP userprefs (if applicable). For users who did a previous iCS 2.x database migration, they should perform the migration again due to the changes in ACL. The complete instructions are provided in iPlanet Calendar Server 5.0 Installation Guide.From NCS and SCS to 5.x -
Migration tools for the Netscape Calendar Server and the Sun Calendar Server to iCS 5.x are not yet available in this release.If you are running NS Directory Server 4.12 or greater, and haven't put in any schema's, the installation program updates these schema's for you.
What's Fixed in this Release
- (412648) Netscape CS 4 data migration does not work.
- (460409) csadmind and cshttpd won't exit cleanly
- (511725) Cannot remove attendee on existing event
- (514128) Task overdue calculation faulty
- (514923) act-on-behalf of bits are not defined in csIAccessControl.h
- (515395) Current Calendar field is blank
- (517325) overdue tasks only show up when viewing current day
- (520117) Task at due at 12:00 AM does not render in views
- (522629) sync doesn't like CRLF in event details
- (523747) store events/todos: Non-organizer shouldn't PUBLISH/REQUEST
- (524534) duplicate repeating events when imported in Outlook
- (524542) Unable to delete events entered prior to Patch-01
- (525418) language of mail notifications set by ics.conf
- (525798) english strings appear in the UI of New Event
- (526007) Editing an event and changing it's calendar causes a changed copy
- (526582) Exporting huge calendar could crash server
- (526603) doublebyte in Group Details show corrupted
- (527089) csadmind core dumps when changing caldb.berkeleydb.ensmsg
- (527343) Tasks not reflected in Comparison view in task box
- (527498) set_userprefs/get_userprefs: If no admin access and pass in userid parameter, then will affect logged-in user
- (527530) Delete calendar doesn't work from Solaris Navigator 4.7
- (528088) New Group: We should return error when inputting bad chars
- (528109) Non default calendar reply does not work from Invitations list
- (528400) calendar's timezone doesn't trigger additional display info
- (528428) WCAP: need to filter group ID is set icsSet
- (529108) readable url needs TZ attached to it
- (529315) set_calprops wcap command returns multiple errorno values
- (529334) Search For Components: Task due date not shown
- (529433) All Task reminders refer to events
- (529607) get_freebusy.wcap XML not returning correct XML
- (529657) application cannot be contrained inside a frameset consistently
- (530595) Calendar searching does not work thru DWP
- (530786) availability view blocked by private (additional) calendar
- (530797) Set default calendar display name to LDAP first and last name
- (530930) Some event conflicts not caught - event order messed up
- (531266) import calendar does not work in netscape communicator 4.76
- (531276) user first name and last name are not stored correctly
- (531449) can not open ical file from outlook
- (531819) Tasks with no duedate/time missing "completed" checkbox
- (531821) allday Tasks display in a limited way (weekview, monthview)
- (531822) allday tasks in monthview print out dueTime information
- (531953) Unsubscribing to calendar problem
- (531956) Passwords containing the "&" character don't work
- (532312) Calendar Group with Blank name can't be deleted.
- (532622) Changing Appearance turns off reminder setting
- (532659) calendar display names with apostrophe get js error
- (533495) HPUX - setup -nodisplay does not work
- (533635) sync: passing "?" between WCAP command and parameters
- (533636) sync: WCAP.login not reaching iCS
- (533975) If Login is set to Group View, Calendars list will be incomplete
- (534516) OK button in New Cal Group dialog's Timezone tab cause JS error
- (534520) HPUX - Fonts overlap in Install GUI
- (534521) ./setup hangs after successfull installation and GUI termination
- (535079) search_cal_props hangs
- (535465) Remove or clarify error "Undefined" from invalid date range.
- (536248) csuser should store preferredlanguage attribute when creating user
- (536819) start date for a due task is set to 19700101T000000Z
- (537367) RFE:Need to enhance user/calender searches
Administration
- (526582) Exporting huge calendar could crash server. Large calendar could crash the server when exporting the data through the data translators. If the data is very large (i.e. > 1 megabyte), then the server could run out-of-memory and crash.
- (531276) User first name and last name are not stored corrctly in LDAP server when they contain Japanese characters.
Server configuration. The cn, givenname and sn is restricted to US-ASCII in 5.0p3 release (this is also the case with NMS/iMS). We plan on supporting this in 5.1 timeframe.
Installation
- Installing on HPUX we recommend using the install GUI on a X-Display Server that is directly connected (keyboard / mouse, and display) to the HPUX Server. There is a known problem with the HPUX JRE which 1) prevents the '-nodisplay' from working correctly 2) cause the setup GUI to hang after "Successful Installation has Finished. "
The problem is with the JRE implementation.
The following steps are a solution to a workaround:
1. Logon to the X-Display which is directly connected to the HP Server (using CDE Login) as 'root' .
2. Open a 'dtterm' window and make sure the DISPLAY variable is set correctly ( i.e.. hostname:0.0 )
3. Cd to /tmp and remove old JRE files:
# cd /tmp
# rm [0-9]-csnativetk*
# rm Hpux*
# rm csnativetk*
4. Cd to the patch location and execute './setup' to start the Install GUI
# cd $PATCH_LOCATION_DIR
# ./setup
5. Be sure to answer as follows for these specific questions:
Select Custom Installation
Unselect Startup Calendar Server After Installation
6. After the Install GUI finishes, the GUI window will close, but the './setup' command in the dtterm window will hang and not exit correctly. You must do
a <control-C> in the window to exit the setup.
7. Start up the Calendar Server
# cd /opt/iPlanet/CalendarServer/cal/bin/
# ./start-calServer
- (512121) UID not displayed in mail notifications. See corrections to the Administrators Guide.
Database Wire Protocol (DWP)
- The current limitation of DWP is that all calendar services, i.e., cshttpd, csadmind, csdwpd, enpd, and csnotifyd must be running on the same type of OS. Cross platform OS between cshttpd and csdwpd are not supported, i.e., users cannot setup a mixed platforms such as using Windows NT for csdwpd and Sun OS for cshttpd, or vice versa.
Calendar Express
(536838) Email notifications can crash Communicator. iCS 5.x notifications are optimized by default for the Outlook client. Notifications are sent out in multi-part MIME formats - text/plain, text/html, and text/calendar. These formats are defined in the <install>/bin/config/en directory. With these default formats the event notifications are not correctly rendered in Communicator. Being rendered in this case means that Communicator is trying to handle the text/calendar format that is optimized for Outlook. In Communicator it exposes the "More Details", "Accept", and "Decline" buttons that can crash Communicator. It also will desplay a "Error: 3.0 Unknown: (::)". There are workarounds:
- From the Communicator toolbar go to Edit: Preferences: Navigator: Applications and create an application to handle the ics extension. The mime format would be text/calendar2 and the application to use can be Notepad, Outlook, or something similar. This would have to be done on every user client and might not be the best choice for large deployments.
- In the <install>/bin/config/en directory modify the format files so that the text/html format comes after the text/calendar format. !!!! NOTE - This could disable the Outlook interoperability.
Setting calendar display name to the LDAP CN - See technote #20010228-1 Internationalization Issues
(518572) - It is not possible to create a group name containing extended characters. There is no workaround. (519293) - It is not possible to create a Calendar Name containing extended characters .There is no workaround. Potential Problems and Solutions
The following section details the known potential problems and solutions for the Calendar Server 5.0p3 release.
See also, Known Limitations and Considerations, and the following section, Corrections to the Documentation, for other issues that might affect product capability or use.
The following information under Updating the LDAP Schema has been REMOVED as the schema files are contained packaged server file and there is no reason to downloaded separately:Administrators GuideNote: You can download the most up to date iPlanet Calendar Server 5.0 schema files at http://www.iplanet.com/products/infrastructure/messaging/ics/index.html
! Forces requests for local calendar IDs to use remote DWProtocol.
(Used only to debug local machine.)
caldb.dwp.forceremote = "n"
! Specifies if a local database exists where "y" disables DWP and
"n" tells the server to use remote DWP only
caldb.localdb = "y"
! Where is the local database? If caldb.localdb is "n", this value
specifies the DWP host to use for localdb.
caldb.localdb.host = "localhost"
! Hostname of machine on which csdwpd is running.
service.dwp.calendarhostname = ""
2) The administrator
can modify and retrieve user preferences for any user via "get_userprefs.wcap"
and "set_userprefs.wcap".
For example,
if an administrator logs in using login.wcap, any user's preferences may
be retrieved or modified. For an administrator to have this privilege,
a server configuration preference must be set:
Note:
To use these new preferences, the administrator must use the "login.wcap"
command to log in as the administrator before issuing any other commands.
1. Added
error USERPREFS_ACCESS_DENIED (44)
Caller tried
to use "get_userprefs" or "set_userprefs" with the "userid" parameter.
The caller was not an administrator OR the server did not allow administrator
get/modify userpref access. If this occurs, the server will return
an error of 44.
2. Added
error NOT_ALLOWED_TO_REQUEST_PUBLISH (45)
Caller tried
to edit the component using a PUBLISH or REQUEST method. Only organizer's
are allowed to do this. (Thus caller was not the organizer.)
If this occurs,
the server will return an error of 45.
See updated
Error
code table 10-4
This command takes two parameters: "id" and "fmt-out".
The first parameter, "id", is required and is the unique identifier string (UID), which is the session ID to be validated. There is no default value.
The second parameter,
"fmt-out",
is optional. It is a string that specifies alternate output formats. The
default is "text/js".
In each
command the parameter is the same:
The parameter
takes one of three keyword arguments: "event", "todo",
or "all".
This argument
directs WCAP to return, respectively, only events, only todos, or both
events and todos. This parameter is not required. The default is "all",
returning both events and todos. If an unrecognized value for the component_type
parameter is passed in, the default value will be used.
The value
of "tzid"
must now be a time zone ID string, such as "America/Los_Angeles". Note
that these are not localized. If other ISO 8601 DateTime string parameters,
such as "rid", "dtstart" and "dtend", do not have a "Z" on the end, this
parameter determines the time zone to use.
The value
is no longer a quoted string, but is now a time zone ID string to match
the acceptable values for "tzid"
in the seven commands listed above.
The default
value of the "tzid"
parameter in all commands is the server's default time zone. This is a
change for "storeevents" and "storetodos".
This argument
is a string that tells WCAP which user's preferences to display or set.
This parameter can only be used by the administrator, and only if the server
configuration parameter
"service.admin.calmaster.wcap.allowmodifyuserprefs"
is set to "yes",
and the administrator is logged in as administrator using the "login.wcap"
command.
If the value of "convertCalid" is set to 1, WCAP converts incoming "^" character back to a ":". The default value for "convertCalid" is 0.
The "convertCalid" parameter is only recognized if the preference to be set is either "icsSet" or "icsSubscribed"; otherwise, it is ignored.
If you have problems with iPlanet Calendar Server 5.0p3, contact iPlanet customer support using one of the following mechanisms:So that we can best assist you in resolving problems, please have the following information available when you contact support:iPlanet online support web site at http://www.iplanet.com/support/online/
From this location, the CaseTracker and CaseView tools are available for logging problems.The telephone dispatch number associated with your maintenance contract Description of the problem, including the situation where the problem occurs and its impact on your operation Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem Detailed steps on the methods you have used to reproduce the problem Any error logs or core dumps
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.