The iPlanet™ Calendar Server 5.1 Release Notes document important information available at the time of the release, including:
Read this document before you install Calendar Server 5.1. For an online version, see the iPlanet documentation web site:
http://docs.iplanet.com/docs/manuals/calendar.html
After you install and start using Calendar Server 5.1, check this web site periodically to view the most up-to-date documentation.
In addition to performance enhancements and bug fixes, iPlanet Calendar Server 5.1 includes the following new features.
Calendar Express 5.1 has many new features that can help your end users to be more productive. These new features are described in the following document:
iPlanet hopes you will make this document available to your end users so that they can take advantage of these new features.
During installation, you can have the installation program save all Calendar Server configuration and customizable files that have these extensions:
The installation program generates a report that indicates which files have changed. After the installation has finished, you can use this report to merge your customizations from the saved files into the newly installed Calendar Server 5.1 files.
The ncs4migrate migration utility migrates Netscape Calendar Server 4.x calendar data to Calendar Server 5.1. For information about running ncs4migrate, see the iPlanet Calendar Server Installation Guide.
iPlanet Calendar Server 5.1 supports Netscape™ Directory Server 4.16 (in addition to 4.12) on all software platforms and iPlanet Directory Server 5.1 on all software platforms except Solaris 2.6 (5.6).
Calendar Server 5.1 includes the csdb utility check and rebuild commands to check and, if necessary, to rebuild a calendar database (caldb). For information about how to use these commands, see the iPlanet Calendar Server Administrator's Guide.
Calendar Server 5.1 supports Private and Time and Date Only (confidential) events and tasks in user calendars. When creating a new event or task in Calendar Express, a user can specify whether the event or task is Public, Private, or Time and Date Only (confidential):
For information about how to specify Private and Time and Date Only (confidential) events and tasks, refer to the Calendar Express Online Help.
To specify whether the Calendar Server filters (recognizes) Private and Time and Date Only (confidential) events and tasks, this release includes the new calstore.filterprivateevents parameter in the ics.conf file. If set to "no", the Calendar Server treats them the same as Public events and tasks. The default is "yes".
Calendar Express 5.1 end users can request to receive email notification messages whenever someone schedules or cancels an event on their calendars. The following new parameters in the ics.conf file determine whether this option is available to end users:
ine.invitation.enable controls the email notification for end users for an invitation to an event. If "yes" (the default), a notification is sent if the end user has requested it. If "no", a notification is not sent.
ine.cancellation.enable controls the email notification for end users for the cancellation of an event. If "yes" (the default), a notification is sent if the end user has requested it. If "no", a notification is not sent.
For information about how to set this feature in Calendar Express, refer to the Calendar Express Online Help.
The new service.http.renderhtml parameter in the ics.conf file controls the rendering of HTML and Javascript in text fields such as the description of an event or task. If "yes", rendering of HTML and Javascript is enabled. If "no" (the default), it is disabled.
The new local.lookupldap.search.minwildcardsize parameter in the ics.conf file specifies "0") means always do a wild-card search. The default is "3".
Calendar Server 5.1 supports the Java™ Message Service (JMS) API, which allows the data in an Event Notification Service (ENS) message to be in "text/XML" format in addition to "text/calendar" format. ENS messages can be sent for both Alarm Notifications and Calendar Update Notifications.
For more information, see the iPlanet Messaging and Collaboration Event Notification Service Manual.
iPlanet Calendar Server 5.1 includes these new WCAP commands:
For a description of these commands, see the iPlanet Calendar Server 5.1 Programmer's Manual.
iPlanet Calendar Server 5.1 provides support for high availability (HA) on Solaris servers by using the Sun Cluster 3.0 U1 product. A cluster consists of a primary node and a secondary node, with the Calendar Server running on the primary node. If a failure occurs on the primary node, the Calendar Server resources then failover to the secondary node to provide continuous availability.
For more information, see the "Sample iCS 5.1 HA Configuration" document.
The Calendar Server supports limited virtual domain mode, which allows customers to host multiple calendar sites on the same Calendar Server installation. Full virtual domain support is scheduled for a future release; however, a subset of virtual domain functionality is available with Calendar Server 5.1 (initially with the Calendar Server 5.0 patch 2 release). If you would like to use limited virtual domain mode, contact your iPlanet technical support representative.
For additional documentation, see the following article:
http://knowledgebase.iplanet.com/ikb/kb/articles/4950.html
This section contains information you should know before you install Calendar Server 5.1, including:
For installation information and instructions, refer to the iPlanet Calendar Server Installation Guide.
To install, reinstall, or upgrade the Calendar Server, you must have superuser privileges. On Solaris or other UNIX systems, you must login as (or become) root (user ID = 0). On Windows NT systems, you must login as an administrator who has full administration privileges for the system.
iPlanet Calendar Server 5.1 supports the following software platforms:
Table 3 shows the required patches for Solaris 8 (5.8). For the most current list of patches, check the patches_sparc_SunOS_5.8.list file in the instsupp/ directory after you unbundle the Calendar Server.
In Table 3, the revision number following the dash in each patch ID identifies the minimum patch revisions; later revisions are acceptable. You can download these patches from:
Patch ID
Description
Table 4 shows the required patches for Solaris 2.6 (5.6). For the most current list of patches, check the patches_sparc_SunOS_5.6.list file in the instsupp/ directory after you unbundle the Calendar Server.
In Table 4, the revision number following the dash in each patch ID identifies the minimum patch revisions; later revisions are acceptable. You can download these patches from:
Patch ID
Description
Solaris 2.6 (5.6) supports Netscape Directory Server 4.12 and 4.16 but not iPlanet Directory Server 5.1.
Note
Calendar Server 5.1 supports Microsoft Windows NT 4.0 with Service Pack 6a (or newer). You can download Service Pack 6a from the following web site:
http://www.microsoft.com/ntserver/nts/downloads/
On Windows NT servers with slower processors, the start-cal command might time out. If this happens, start the Calendar Server using the Windows NT Control Panel Services dialog box.
Note
Before you install Calendar Server 5.1 on HP-UX 11.0 servers, install the 9/01 HP-UX 11.0 Quality Pack, which is available from the following web site:
Before you install Calendar Server 5.1, use the settings shown in the following table as a baseline for kernel tuning. (These settings are based on an HP 9000 with 2 GB physical memory and 2 GB swap.)
Parameter
Description
New Setting
To modify the kernel, use HP-UX system administration tools (sam and kmtune), or to modify the kernel manually:
On HP-UX 11.0 servers, the Calendar Server is not started automatically after a successful installation or restart, even if you select these options during installation. You must start the Calendar Server manually using the start-cal command. (4525117).
iPlanet Calendar Server 5.1 supports these directory servers:
For more information about directory server requirements, see the iPlanet Calendar Server Installation Guide.
The hardware requirements to install iPlanet Calendar Server 5.1 are:
Calendar Express requires a JavaScript-enabled browser. For optimal performance, iPlanet recommends the following browsers for Calendar Server 5.1:
Browser
Solaris
Windows
Macintosh
Before you install Calendar Server 5.1, remove any *.so_pre-Hotfix_* files, especially any files that might be in the server-root/cal/bin/plugins directory. Otherwise, some of these files might be automatically loaded from this directory and cause inconsistent Calendar Server behavior.
If you are upgrading or reinstalling the Calendar Server, you can have the installation program save all Calendar Server configuration and customizable files that have these extensions:
The installation program generates a report that indicates which files have changed. After the installation has finished, you can use this report to merge your customizations from the saved files into the newly installed Calendar Server 5.1 files.
For information about using these migration utilities, see the iPlanet Calendar Server Installation Guide.
iPlanet Calendar Server 5.1 has the following known problems. If available, a workaround is provided for each problem.
HP-UX: Calendar Server is not started after a successful installation or restart (4525117)
On HP-UX 11.0, the Calendar Server is not started after a successful installation or restart, even if you select these options during installation.
Start the Calendar Server manually using the start-cal command.
Internet Explorer user can't export in XML format after having exported in iCal format (4525128)
If you export a calendar in Internet Explorer 5.5 or later in iCal format, you cannot then export the calendar in XML format. Internet Explorer does not display the Save window to select a location for the exported file.
Click the Internet Explorer Refresh button and then export the calendar. Or, go to another Calendar Express window such as View or Calendars, return to the Options window, and then export the calendar.
International characters display incorrectly in Calendar Express (4527700)
International characters entered in Calendar Server command-line utilities such as csresource using encoding other than UTF-8 display incorrectly in Calendar Express.
For command-line parameters that contain international characters to display correctly in Calendar Express, enter the characters using UTF-8 encoding.
Exported events cannot be modified when imported on another Calendar Server (4530547)
Events that are exported and then imported on a different Calendar Server cannot be modified by the new users. For example, if UserA exports a calendar and then UserB imports the calendar on another Calendar Server, UserA is still the organizer for the events, and userB cannot modify them.
Edit the exported file and change the organizer to the user who plans to import the calendar on the second Calendar Server.
logout.wcap call always returns a status of -1 (successful) even for a failure (4535769)
A logout.wcap call always returns -1 (successful) even if the logout has failed.
To check if a session is still valid, call the check_id.wcap command and then check the returned X-NSCP-WCAP-CHECK-ID property. If the value is zero (0), the session is invalid and the logout was successful. If the value is 1, the session is still valid and you must call logout.wcap to logout again.
Installing Portal Server after Calendar Server changes permissions on /var/opt (4535775)
If you install the Portal Server after installing the Calendar Server, permissions for the /var/opt directory are changed to 0700 (drwx------). A subsequent attempt to restart the Calendar Server (or a reboot) causes the following error:
Starting csadmind
Fatal error 70: Cannot open calendar database
csadmind is not started
Calendar service(s) not started
After installing the Portal Server, change the permissions for the /var/opt directory to 0775.
Calculating availability uses both invitee's and inform-only calendars (4535922)
When calculating availability for scheduling a new event, the Calendar Server uses both the invitee's calendars and calendars from the inform-only list. This implementation makes it more difficult to determine an appropriate time for the event, and the Calendar Server should use only the invitee's calendars.
System does not accept more than 75 users in Calendar Permissions view (4535964)
If you add users in the Calendar Permissions view, the Calendar Server does not accept more than 75 users.
To add more than 75 users, use the login.wcap and createcalendar.wcap commands. For a description of these commands, see the iPlanet Calendar Server 5.1 Programmer's Manual.
Email address changes are not carried to existing events and tasks (4535971)
If you change the email address in the Event Reminder option setting, reminders for any future events and tasks previously entered on your calendar will still be sent to the original email address.
Edit each event and task and specify a reminder with the correct email address.
Asia/Tehran time zone is not displayed in Calendar Express Options Settings view (4536390)
Although the Asia/Tehran time zone is in the Calendar Server 5.1 timezones.ics file, it is not displayed by Calendar Express in the Options Settings view.
Auto-provisioning feature cannot be disabled for first-time user login (4537234)
By default, the Calendar Server creates a default calendar when a new user first logs into the Calendar Server, and currently, there is no option to disable this feature.
None. However, a new configuration parameter to disable this feature is planned for a future release.
Spaces in group calendar names cause problems (4537454)
A leading or trailing space in a group calendar name causes the Calendar Server to create another group calendar without the space.
Do not use leading or trailing spaces in group calendar names.
Recurrence ID (RIDs) are not in ISO8601 format (4537733)
The Calendar Server does not convert RIDs to ISO8601 format.
Do the translation to the time_t format before passing back in the RID. That is, translate the creation date in ISO8601 to the Zulu version of ISO8601 and then to time_t.
Note Do not use the C mktime() functions, because they use the system's time-zone information, which might not map correctly to the Calendar Server or user's chosen time zone.
Not everyone has the calendar entry after a meeting has been scheduled (4538591)
To invite an attendee who does not have a default calendar to a meeting, you must specify the attendee's email address. The Calendar Server then sends an email message using "mailto:" to the attendee with the event details, but it does not create a default calendar for the attendee.
The Calendar Server creates a default calendar for a new calendar user in either of these situations:
For information about cscal, see the iPlanet Calendar Server Administrator's Guide.
Calendar Server allows double booking of calendars (4538774)
The Calendar Server allows double booking of a user's calendars even if user.allow.doublebook is set to "no" in the ics.conf file.
To prevent double booking for a user's calendar, run the cscal utility with the -k no option for each individual calendar.
Calendar is not searchable by other users although Availability and Schedule are checked (4538863)
A calendar created before the patch 4 release is not searchable by other calendar users unless Read permission is checked. Checking only the Availability or Schedule permissions does not make the calendar searchable.
If you have a calendar was created before patch 4 was installed, you might need to change its permissions to make it searchable. Refer to the Calendar Express Online Help for information about changing permissions.
Calendar Overview has inconsistent method for displaying tasks (4538960)
The Task/Event box, which appears just below the date banner for both the Overview and Day views, does not display tasks consistently.
Calendar Express displays tasks in the Task/Event box on the Overview and Day views as follows:
The Calendar Server does not display future tasks because a calendar might have hundreds (or even thousands) of future tasks, and displaying all of them would quickly overflow the Task/Event box. To view future tasks for a calendar, use the week or month view.
csbackup utility fails if target directory exists and -f option is not specified (4539252)
The csbackup utility fails if the target backup directory already exists (even if it is empty) and you do not specify the -f option. For example, the following command fails if backupdir exists:
# ./csbackup database backupdir
Include the -f option when you run the csbackup utility. For example:
# ./csbackup -f database backupdir
Server JavaScript returns fully qualified URLs rather than relative URLs (4539347)
After login, the Server JavaScript returns fully qualified embedded URLs, including the port number, rather than relative URLs. The fully qualified URLs cause problems if you are trying to use the Calendar Server with a load balancer or proxy server.
Export from Internet Explorer 5.5 does not work correctly (4540544)
If you are using Internet Explorer 5.5, the Calendar Express Export function saves the calendar as an HTML file and not in .ics or .xml format.
Search in new event using a wildcard (*) returns directory server error (4540607)
A search that uses a wildcard character (*) or a short substring in a new event returns the following error:
There was a problem with the directory server. (2)
The following problems can cause this error:
If the directory server is not down, avoid using the wildcard character or short substrings (such as "j", "t", "sh", or "sh*") in the search. Or, to configure the LDAP server to ignore the lookup limit, change the lookthroughlimit to -1 in the slapd.ldbm.conf file.
Installation program does not display default time zone or allow it to be set (4541260)
The default time zone for Calendar Server 5.1 is "America/New_York". The installation program does not display this default or provide a way to change it. Also, if the system default time zone (which is OS specific) is different from "America/New_York", the installation program does not attempt to find a Calendar Server time zone that matches it.
None during installation. However, for importing files after installation, you can set the following time-zone parameter in the ics.conf file:
! Timezone ID used when importing files.
calstore.default.timezoneID = "America/New_York"
Also, for more information, see:
http://knowledgebase.iplanet.com/ikb/kb/articles/4996.html
Calendar Express doesn't allow "last day of the month" for repeating events (4541444)
Calendar Express does not allow you to specify the "last date of the month" (regardless of the date) for a repeating monthly event.
To specify the "last date of the month" for a monthly event, schedule the event to repeat on the "31st day of the month." The Calendar Server then automatically adjusts the actual last day for months with fewer than 31 days.
User cannot set reminders to invitations before accepting or declining them (4552548)
If an user tries to set a reminder to an invitation before accepting or declining it, the action is not saved. Also, if a user brings up the invitation without accepting or declining it and then clicks OK, an error is logged to the http.log.
Do not set a reminder before accepting or declining an invitation.
Search doesn't return expected results if the search string contains an asterisk (4555547)
The search for a calendar doesn't always return the expected results if the search string contains an asterisk (*).
Try the search again without the asterisk, using a search string of at least three characters.
Events created on a Macintosh using Netscape Navigator 4.x contain corrupted data (4556675)
If you create a new event or task on a Macintosh using Netscape Navigator 4.x and then add a name, location, and description, extra characters are added at the end of the description.
If you need to create new events or tasks with a name, location, and description on Macintosh systems, use Netscape Navigator 6.x or Internet Explorer 5.x.
Email notifications cause problems with Netscape Communicator (4560460)
In Calendar Express, email notifications can cause problems with Communicator. Calendar Server 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 server-root/cal/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. It also will display a "Error: 3.0 Unknown: (::)".
For additional information about setting the calendar display name to the LDAP CN, see:
http://knowledgebase.iplanet.com/ikb/kb/articles/4964.html
New Calendar doesn't display in the Calendars view (4607517)
A calendar created through Calendar Express sometimes doesn't display in the list on the Calendars view, even though the calendar is listed as subscribed to. This problems occurs on a server with multiple CPUs.
Refresh/reload the browser to refresh the Calendars view.
Until date for a repeating event shows one day after original date (4622462)
Create a repeating event that repeats every weekday and set a specific Until date. Then, if you edit the event and click "Change repeat pattern", the new Until date is one day after the original Until date. For the repeating event, the Calendar Server is using Zulu time rather than the local time. Also, the default for the Until date is reset to Forever. If you click OK, the Until date for the event changes to Forever.
After you make your choices for a repeating event, review the choices and make sure that the default for the Until date is not set to Forever. If you have doubts, click Cancel and not OK.
Calendar Server doesn't create all instances if repeat until date is earlier than default (4625452)
Create a repeating event. On the Daily tab, click Every weekday and specify a repeat Until date earlier then the default Until date. The Calendar Server creates only one or two instances of the event.
Use the default Until date or a later date, and then delete the events you don't need.
Localization resource files are not current and need to be removed (4628091)
The installed localized resource files are not the latest versions and are out of sync with Calendar Server 5.1. As a result, if you specify a non-English language, the localized Calendar Express user interface is not the latest localized version.
The iPlanet Calendar Server 5.1 release will be localized in French (fr), German (de), Japanese (ja), and Spanish (es). Watch for an announcement regarding the release of these localized products. When the localized release you want is available, remove the old localized resource files and then upgrade to the new localized release.
The Calendar Server 5.1 documentation set includes:
The Calendar Express Online Help is available with the Calendar Express software. All other Calendar Server 5.1 documentation is available on the iPlanet documentation web site:
http://docs.iplanet.com/docs/manuals/calendar.html
The iPlanet Calendar Server 5.1 Installation Guide states the ncs4migrate utility is located in the server-root/cal/bin/ directory. For some releases, ncs4migrate is not available in this directory. See Migrating Data to Calendar Server 5.1 for more information.
The iPlanet Calendar Server 5.1 release will be localized in French (fr), German (de), Japanese (ja), and Spanish (es). Watch for an announcement regarding the release of these localized products.
For a Calendar Express end user to access a localized version of the Calendar Server, the character set required to render the particular language must be available in the end user's browser configuration.
If you have problems with iPlanet Calendar Server, 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 iPlanet customer support:
Useful iPlanet information can be found at the following locations:
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.
Sun, Sun Microsystems, the Sun logo, Java, iPlanet, and all Sun, Java, and iPlanet based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
Last Updated March 20, 2002