Sun ONE Calendar Server 6.0 Release Notes

Sun™ ONE Calendar Server 6.0 Release Notes

Version 6.0

Part Number 816-6715-10

January 20, 2004

Important After you install Sun ONE Calendar Server 6.0, you must add one of the Calendar Server patches as described under Required Calendar Server 6.0 Patches.

These Release Notes contain important information available at the time of release of Sun ONE Calendar Server 6.0, including:

You can find the most up-to-date version of these Release Notes on the following documentation Web site:

http://docs.sun.com/coll/S1_CalendarServer_60

Read these Release Notes before you install and configure Calendar Server and then check this Web site periodically to view the most up-to-date documentation.

Sun™ ONE Calendar Server was formerly iPlanet™ Calendar Server.

 

Revision History

Table 1  Revision History 

Date

Description of Changes

January 20, 2004

Revised workaround for bug 4947880 under Known Issues.

December 23, 2003

Revised patch and HA information under Required Calendar Server 6.0 Patches.

December 9, 2003

Added bugs 4963237, 4961879, and 4961879 under Known Issues.

December 8, 2003

Initial release of the Release Notes.

 

Required Calendar Server 6.0 Patches

After you install Calendar Server 6.0 using the Sun Java™ Enterprise System Installer, you must apply the latest revision of one of the following Calendar Server patches using the patchadd command, depending on your platform:

You can download either patch from the SunSolve Patch Support Portal:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage

For information about these patches, including a list of problems fixed, refer to the respective patch Readme file, which is also available on the SunSolve Patch Support Portal.

Multiple Front-End/Back-End Servers

If your site has configured Calendar Server on multiple front-end/back-end servers, apply the patch on all front-end and back-end servers.

High Availability (HA) Configuration

If your site has configured Calendar Server 6.0 for high availability (HA), apply the patch only on the primary node that is running Calendar Server and not on any of the secondary nodes. However, first make sure the Calendar Server HA service is operational before applying the patch.

To apply the patch:

1. Stop the Calendar Server HA service:

scswitch -n -j cal-resource

where cal-resource is the Calendar Server resource name.

2. Apply the patch only to the node where the Calendar Server packages are installed. For example, to check for these packages:

# pkginfo SUNWics5
application SUNWics5 Sun ONE Calendar Server Release 6.0, (Server)

3. If the patchadd command is successful, restart the Calendar Server HA service:

scswitch -e -j cal-resource

 

About Calendar Server, Version 6.0

Calendar Server is a scalable, web-based solution for centralized calendaring and scheduling for enterprises and service providers. Calendar Server supports personal and group calendars for both events and tasks as well as calendars for resources such as conference rooms and equipment. For a list of new features, see the following section, What’s New in Calendar Server, Version 6.0.

What’s New in Calendar Server, Version 6.0

Calendar Server 6.0 includes these following changes and new features:

Installation and Configuration Changes

The installation and configuration of Sun ONE Calendar Server 6.0 on Solaris™ Operating Systems has the following changes from previous Calendar Server releases:

Hosted (Virtual) Domain Support

A Calendar Server 6.0 installation can be configured as a number of hosted (virtual) domains (similar to the existing hosted domain support in Sun ONE Messaging Server). Each hosted domain shares the same instance of Calendar Server, which allows different domains to exist on a single server. Users login to their respective domain. If allowed, they can search for users in other domains and then schedule calendar events with those users.

Note

A Sun ONE Portal Server 6.2 Calendar Channel does not support a Calendar Server hosted domain configuration.

The new csdomain utility manages Calendar Server attributes in the LDAP directory for a hosted (virtual) domain. These attributes are part of the icsCalendarDomain object class. The new csdomain utility can:

The csuser, csattribute, and csresource utilities support the -d domain option, which specifies the name of a hosted (virtual) domain. If -d is not specified, the utility uses the domain from the service.defaultdomain parameter in the ics.conf file.

If your site is configured for hosted domains, you must fully qualify each calendar ID (calid) and user IDs with the domain name in all WCAP commands. For example: jsmith@sesta.com.

For more information about hosted domains, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Single Sign-On (SSO) Through Sun ONE Identity Server

Sun ONE Communications servers, including Calendar Server and Sun ONE Messaging Server (Messaging Server), can implement SSO using Sun™ ONE Identity Server 6.1. For more information, refer to the Sun ONE Calendar Server 6.0 Administrator’s Guide.

High Availability (HA) Configuration

On Solaris Systems (SPARC Platform only), system administrators can configure Calendar Server 6.0 for high availability (HA) using Sun Cluster. Both the HAStorage and HAStoragePlus storage types are supported. For more information, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Note

For a Calendar Server HA configuration, always specify “no” to each of these questions during configuration:

  • Start Calendar Server after successful configuration
  • Start Calendar Server on system startup

Secure Sockets Layer (SSL) Support

Calendar Server 6.0 supports the Secure Sockets Layer (SSL) protocol to encrypt data between calendar client end users and Calendar Server. System administrators can configure Calendar Server to encrypt only the Calendar Server login or an entire calendar session. For more information, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Load Balancing of Processes Across Multiple CPUs

By default, Calendar Server 6.0 distributes the HTTP service (cshttpd process) and the Distributed Database service (csdwpd process) across multiple CPUs for a server. For more information, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Authentication Between Front-end and Back-end Servers Using DWP Connections

Calendar Server 6.0 provides authentication between front-end and back-end servers that are using a DWP connection. To set up this authentication, you must set parameters in the ics.conf file on both the front-end and back-end servers. For more information, including the parameters you must set, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Calendar Database Enhancements

New Database Version

Calendar Server 6.0 uses Berkeley DB version 3.2.9. If you have an earlier version of Calendar Server that uses Berkeley DB version 2.6, you must upgrade your calendar database to version 3.2.9. For more information, see the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems.

Delete Log Database

Calendar Server 6.0 includes the Delete Log database (ics50deletelog.db) to store deleted events and todos (tasks). The new cspurge utility allows the manual purge of entries in the Delete Log database. For more information, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Web Calendar Access Protocol (WCAP) Changes

Note

If your site is configured for hosted domains, you must fully qualify each calendar ID (calid) and user IDs with the domain name in all WCAP commands.

For example: jsmith@sesta.com

Other changes and additions to WCAP commands include:

Event Notification Service (ENS) Additions

ENS messages can be sent for both calendar update notifications and for alarm notifications. Calendar Server 6.0 includes three new alarm notifications and a new alarm notification parameter. For more information about these additions, see the Sun ONE Messaging and Collaboration 6.0 Event Notification Service Manual.

Alarm Notifications

Three new alarm notifications have been added:

Alarm Notification Parameter

The URI parameter has been added for all alarm notifications.

New Default Port Number for ENS enpd Process

Calendar Server and Messaging Server require different versions of the Event Notification Service (ENS) process, enpd. In past releases, both Calendar Server and Messaging Server used 7997 as the default ENS port number, which caused problems when the products were running on the same server.

To allow two different enpd versions to run on the same server, Calendar Server and Messaging Server must use different default enpd port numbers. Therefore, Calendar Server now sets the default ENS port number to 57997 as follows:

service.ens.port="57997"

If you are having problems running Calendar Server and Messaging Server on the same server, check the Calendar Server service.ens.port parameter and set it to a new value, if needed.

New LDAP Schema Version

Calendar Server 6.0 supports Sun ONE Schema, v.2 Native or Compatibility Mode and Sun ONE LDAP Schema, v.1. Therefore, several new LDAP schema object classes and attributes have been added. For more information, see Sun ONE Messaging and Collaboration 6.0 Schema Reference Manual.

Auto Provisioning Configuration Parameter

Auto provisioning of calendar users is configurable using the new local.autoprovision parameter in the ics.conf file:

The default is “no”. To allow auto provisioning, this parameter must be present in the ics.conf file and set to “yes”. The anonymous calendar is always created, even if the parameter is set to “no”.

In hosted (virtual) domain mode, Calendar Server also checks the domain to see if it is calendar enabled. A domain is calendar enabled if it has the LDAP icsCalendarDomain object class. If the domain does not have this object class, auto provisioning of calendar users is not allowed, regardless of the value of local.autoprovision.

LDAP Data Cache

The LDAP data cache ensures that LDAP data is available immediately after it has been committed, even if the LDAP directory server is configured to include a delay in the availability of committed data. If your site uses a master/slave LDAP configuration that introduces a delay in the availability of committed LDAP data, the LDAP data cache can ensure that your clients have accurate LDAP data. For more information, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Required LDAP mail Attribute for Calendar Server Users

Calendar Server 6.0 (and later) requires users to have the LDAP mail attribute for both user and resource calendars. Each resource calendar must have an email address, even if the email address is not actually used.

You might specifically need to add the LDAP mail attribute using the Calendar Server csresource or csuser utility or a directory server utility such as ldapmodify.

For more information, refer to the Sun ONE Calendar Server 6.0 Administrator’s Guide.

New CLI Utilities

Calendar Server includes the following new CLI utilities:

For more information, see the Sun ONE Calendar Server 6.0 Administrator’s Guide.

Client User Interface (UI) Features

Free/Busy Check box

A new check box is available for use when creating a new event. When the Free/Busy check box is marked while you are creating an event, others with Read or Availability permissions for your calendar will see the time of this event blocked out as busy.

Invitees List Changed

When creating a new event, the organizer of the event is no longer automatically included in the Invitees list. However, the event does appear in the organizer’s calendar.

Refresh View Option

For Calendar Express end users, the Refresh View option improves performance by using calendar data in the browser cache to refresh a view rather than requiring an update from the Calendar Server database. When the Refresh View option is configured for a site (in the ics.conf file), Calendar Express displays Refresh View on all calendar views on the View tab.

XSL Rendering in Client Browser

Calendar Server 6.0 performs client-side rendering by downloading the XSLT processing to the end user’s browser, which in turn reduces the processing that must be done by Calendar Server. In the current release, this applies only to Internet Explorer 6.0 or later.

New Recurrence Model for Recurring Events

Calendar Server now uses a new model for recurring events. Changes to the Calendar Express user interface (UI) are as follows:

Bugs Fixed in Calendar Server 6.0

Table 2 describes the most important bugs fixed in the Calendar Server 6.0 release.

Table 2  Fixed Bugs in Calendar Server 6.0

Number

Description

4905305

SSL parameters caused problem in cshttpd process.

4904425

SSL parameters are missing in the ics.conf file.

4903642

SSL parameters are not added to ics.conf during an upgrade.

4903639

csmonitor displays invalid credentials even when they are correct.

4903119

Client-side rendering and SSL used together causes a blank page.

4899279

Incorrect “count” and “until” XPROPS data when RRULE exceeds recurrence bound.

4898088

Event request messages with Thai/Arabic characters are corrupt.

4894598

Change needed for “A email address...” message.

4888995

Organizer's free/busy time is not displayed in a group scheduling event.

4884815

Installation failed to start Calendar Server.

4884232

csadmind has problems after running func_todo_replace_tzidout.txt test.

4880751

cshttpd process experiences problems when connecting to SSL port.

4880605

Modifying todo summary loses dtDue information.

4880274

import WCAP command with default fmt-out format returns -5990 error.

4879269

set_user_prefs returns ERRNO 26 even when working properly.

4860929

storeevents with large string as summary returned ERRNO 60.

4855183, 4812916

If back-end server is restarted, front-end server must be restarted too.

4837841

New event with long description causes back-end DWP server problem.

4813597

import/export in XML format fails for events that contain Japanese characters.

4793258

ics2migrate encounters problems during functional test run.

4781251

cscal create utility no longer creates calendars for existing users in LDAP.

4773771

After upgrade user cannot create new event with 800x600 screen resolution.

4769090

cscal utility returns error when creating a valid calendar.

4752013

Searching calprops returns calendar without proper permission.

4751092

Calendar store becomes unavailable due to transaction ID wrapping.

4749067

csuser utility cannot create users with LDAP CLD plug-in enabled.

4738461

replace=1 in storeevents.wcap command doesn’t work with a recurring events.

4737358

cshttpd process listens on all IP addresses.

4734453

csmig migration utility is missing the description for usage examples.

4734450

csmig migration utility usage examples are incorrect.

4729674

import.wcap does not trigger ENS notification.

4725163

cscomponents delete does not trigger ENS notification.

4625452

Calendar Server doesn’t create all instances if repeat until date is earlier than default.

4622462

Until date for a repeating event shows one day after original date.

4560460

Email notifications cause problems with Netscape Communicator.

4556675

Events created on a Macintosh using Netscape Navigator 4.x contain corrupted data.

4555547

Search doesn’t return expected results if the search string contains an asterisk.

4552548

User cannot set reminders to invitations before accepting or declining them.

4541444

Calendar Express doesn’t allow “last day of the month” for repeating events.

4541260

Installation program does not display default time zone or allow it to be set.

4540544

Export from Internet Explorer 5.5 does not work correctly.

4539252

csbackup utility fails if target directory exists and -f option is not specified.

4538960

Calendar Overview has inconsistent method for displaying tasks.

4538774

Calendar Server allows double booking of calendars.

4538591

Not everyone has the calendar entry after a meeting has been scheduled.

4537733

Recurrence IDs RIDs are not in ISO8601 format.

4537598

Users cannot login to Calendar Server after running the cstool refresh command.

4537454

Spaces in group calendar names cause problems.

4537234

Auto-provisioning feature cannot be disabled for first-time user login.

4535775

Installing Portal Server after Calendar Server changes permissions on /var/opt.

4535769

logout.wcap call always returns a status of -1 successful even for a failure.

4527700

International characters display incorrectly in Calendar Express.

4526762

Reminder emails should be encoded per user’s LDAP preferredLanguage attribute.

4525128

Internet Explorer user can’t export in XML format after having exported in iCal format.

Hardware/Software Requirements and Recommendations for Calendar Server 6.0

This section describes the hardware and software required and recommended for this release of Calendar Server.

Hardware Requirements and Recommendations

Software Requirements and Recommendations

Supported Software Platforms

Required Patches for Supported Software Platforms

Note

After you install Calendar Server 6.0 using the Sun Java™ Enterprise System Installer, you must add one of the following patches using the patchadd command, depending on your platform:

  • Solaris Operating System SPARC® Platform: 116577-01
  • Solaris Operating System x86 Platform: 116578-01

You can download either patch from the SunSolve Patch Support Portal:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage

The following tables list the required and recommended patches for the Solaris 8 Operating System on SPARC and x86 platforms:

Calendar Server 6.0 does not require any patches for the Solaris 9 Operating System.

The revision number following the dash in each patch ID identifies the minimum patch revisions; later revisions are acceptable.

All of the required Calendar Server patches will be installed automatically during the installation process. You also can download all of the recommended patches from:

http://sunsolve.sun.com/

Table 3  Required Patches for Solaris 8 (5.8) Operating System SPARC Platform 

Patch ID

Description

110934-03

SunOS 5.8: pkgtrans, pkgadd, pkgchk and libpkg.a patch

109320-03

SunOS 5.8: LP jumbo patch

108974-11

SunOS 5.8: dada, uata, dad, sd and scsi drivers patch

108977-01

SunOS 5.8: libsmedia patch

108968-05

SunOS 5.8: vol/vold/rmmount patch

108975-04

SunOS 5.8: /usr/bin/rmformat and /usr/sbin/format patch

108528-09

SunOS 5.8: kernel update patch

108652-34

X11 6.4.1 Xsun patch

109783-01

SunOS 5.8: /usr/lib/nfs/nfsd patch

108985-02

SunOS 5.8: /usr/sbin/in.rshd patch

112668-01

SunOS 5.8: /usr/bin/gzip patch

112611-01

SunOS 5.8: /usr/lib/libz.so.1 patch

108434-06 (32-Bit)

32-Bit Shared library patch for C++

108435-13 (64-Bit)

64-Bit Shared library patch for C++

112279-02

SunOS 5.8: pkgrm patch

110615-09

SunOS 5.8: sendmail patch

109147-24

SunOS 5.8: linker patch

 

Table 4  Required Patches for Solaris 8 (5.8) Operating System x86 Platform

Patch ID

Description

108436-10 or latest

Shared library patch for C++

109148-23 or latest

Required by 108436

108653-29 or latest

Xsun patch

108529-09 or latest

Kernel update patch

110935-03 or latest

pkg commands patch

112612-01 or latest

zlib patch — required by IS SSO libs

112280-02 or latest

pkgrm failed

110616-09 or latest

sendmail patch

ja locale:

 

109952-01 or latest

Input method

Supported Directory Servers

Calendar Server 6.0 supports the following directory servers:

 

Recommended Browsers for Client Computers

Sun ONE Calendar Express 6.0 requires a JavaScript-enabled browser. For optimal performance, the following browsers are recommended:

Table 5  Recommended Browser Versions for Calendar Server 6.0

Browser

Solaris Systems

Windows

Macintosh

Netscape™ Communicator

7.0

7.0

—

Microsoft Internet Explorer     

—

5.5 or 6.0       

6.0

Mozilla

1.2 or 1.4

1.2 or 1.4

—

New Information

This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:

Installation Notes

This section contains information you should know before you install Calendar Server 6.0, including:

 

Caution

Calendar Server does not support Network File System (NFS) mounted partitions. Do not install or create any part of Calendar Server; including executable, database, configuration, data, temporary, or log files on an NFS-mounted partition.

 

Required Privileges

To run the Sun Java™ Enterprise System installer or the Calendar Server 6.0 configuration program on Solaris Systems, you must log in as or become superuser (root).

Java Enterprise System Installer

On Solaris Systems, you install Calendar Server 6.0 using the Sun Java™ Enterprise System installer. The Java Enterprise System installer installs the Sun component product packages, including Calendar Server 6.0, and the shared components that are used by the various products.

The Java Enterprise System installer installs Calendar Server SUNWics5 and SUNWica5 packages in the /opt/SUNWics5 directory. For more information about the Java Enterprise System installer, refer to the Sun Java™ Enterprise System Installation Guide.

Caution

If you have a previous version of Calendar Server 6.0 installed at your site, the Java Enterprise System installer will overwrite existing Calendar Server files, including any files you have customized. If you have any customized files; such as XSL, XML, GIF, HTML, configuration (.conf), or time-zone files, you should back up those files before running the Java Enterprise System installer.

If you have Calendar Server 5.x installed at your site, you must follow specific steps to upgrade to the 6.0 release — particularly if you customized your 5.x release.
For more information about upgrading, refer to the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems.

Calendar Server Configuration Program

After installing Sun ONE Calendar Server using the Java Enterprise System installer, you must configure Calendar Server as follows:

  1. Run the Directory Server Setup Script (comm_dssetup.pl) to configure Sun ONE Directory Server 5.x (unless you already ran the script while configuring Messaging Server 6.0).
  2. Run the Calendar Server Configuration Program (csconfigurator.sh) to configure your site’s specific requirements.

You must run comm_dssetup.pl to update the LDAP schema. Calendar Server does not provide a warning prompt or display error messages in the configurator log if the LDAP schema needs to be updated. (4935521).

For more detailed instructions, refer to the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems.

New Installation Directory Structure

Calendar Server 6.0 has the new installation directory structure shown below in Figure 1.

Figure 1  Calendar Server 6.0 Installation Directory Structure

/opt/SUNWics5/cal/
                   bin/ --> /opt/SUNWics5/cal/lib/
                   classes/
                   config/ --> /etc/opt/SUNWics5/config/
                   csapi/
                   java/
                   lib/
                   sbin/
                   tools/
                   uicust/
                   uninst/

For Java Enterprise System Release 1, Calendar Server 6.0 provides the links shown in Table 6.

Table 6  Calendar Server 6.0 Directory Links

This previous location...

Links to this new location...

Old 5.x: /opt/SUNWics5/cal/bin/data

/opt/SUNWics5/cal/data

Old 5.x: /opt/SUNWics5/cal/bin

/opt/SUNWics5/cal/lib

Old 5.x: /opt/SUNWics5/cal/bin/config

Previous 6.0 locations:

/opt/SUNWics5/cal/config

/opt/SUNWics5/cal/lib/config

/opt/SUNWics5/cal/sbin/config

/etc/opt/SUNWics5/config

Caution

The links shown in Table 6 will not be available in a future release. You will then need to modify any scripts, applications, or other directory or file references to use the new locations shown in Table 7.

Table 7  New Calendar Server 6.0 Directory Locations 

Utility or File

Old and New Locations

Administrator utilities: start-cal, stop-cal, csattribute, csbackup, cscal, cscomponents, csdb, csdomain, csexport, csimport, csmonitor, csplugin, cspurge, csrename, csresource, csrestore, csschedule, csstats, cstool, and csuser

Migration utilities: cs5migrate, csmig, csvdmig, and ics2migrate

Scripts: icsasm, legbackup.sh, legrestore.sh, and private2public.pl

old: /opt/SUNWics5/cal/bin

new: /opt/SUNWics5/cal/sbin

Administrator utilities: csstart and csstop

old: /opt/SUNWics5/cal/bin

new: /opt/SUNWics5/cal/lib

Configuration files: ics.conf, version.conf, counter.conf, and sslpassword.conf

LDAP server update files: 60iplanet-calendar.ldif, ics50-schema.conf, and um50-common-schema.conf

old: /opt/SUNWics5/cal/bin/config

new: /etc/opt/SUNWics5/config

Mail formatting (*.fmt) files

old: /opt/SUNWics5/cal/bin/config/language

new: /etc/opt/SUNWics5/config/language

where language is en, de, es, fr, ja, zh-TW, or zh-CN.

Schema IDIF files: 20subscriber.ldif, 50ns-value.ldif, 50ns-delegated-admin.ldif, 55ims-ical.ldif, 50ns-mail.ldif, 56ims-schema.ldif, 50ns-mlm.ldif, 60iplanet-calendar.ldif, 50ns-msg.ldif

old: /opt/SUNWics5/cal/bin/config

new: /etc/opt/SUNWics5/config/schema

Library (.so) files

SSL utilities: certutil and modutil

old: /opt/SUNWics5/cal/bin

new: /opt/SUNWics5/cal/lib

Session database

old: /opt/SUNWics5/cal/bin/http

new: /opt/SUNWics5/cal/lib/http

Counter statistics files: counter and counter.dbstat

old: /opt/SUNWics5/cal/bin/counter

new: /opt/SUNWics5/cal/lib/counter

timezones.ics file

old: /opt/SUNWics5/cal/bin/data

new: /opt/SUNWics5/cal/data

Links created for each Calendar Server command line utility and libamsdk.so to provide backward compatibility:

NOTE: These links (and bin -> lib) were created for this release only and they will be removed in the next release.

old: /opt/SUNWics5/cal/lib/csrestore

new: /opt/SUNWics5/cal/sbin/csrestore

old: /opt/SUNWics5/cal/lib/csresource

new: /opt/SUNWics5/cal/sbin/csresource

old: /opt/SUNWics5/cal/lib/csimport

new: /opt/SUNWics5/cal/sbin/csimport

old: /opt/SUNWics5/cal/lib/csexport

new: /opt/SUNWics5/cal/sbin/csexport

old: /opt/SUNWics5/cal/lib/csdb

new: /opt/SUNWics5/cal/sbin/csdb

old: /opt/SUNWics5/cal/lib/cscomponents

new: /opt/SUNWics5/cal/sbin/cscomponents

old: /opt/SUNWics5/cal/lib/cscal

new: /opt/SUNWics5/cal/sbin/cscal

old: /opt/SUNWics5/cal/lib/csbackup

new: /opt/SUNWics5/cal/sbin/csbackup

old: /opt/SUNWics5/cal/lib/libamsdk.so

new: /opt/SUNWics5/cal/libamsdk.so.2

old: /opt/SUNWics5/cal/lib/csuser

new: /opt/SUNWics5/cal/sbin/csuser

old: /opt/SUNWics5/cal/lib/cstool

new: /opt/SUNWics5/cal/sbin/cstool

old: /opt/SUNWics5/cal/lib/csstats

new: /opt/SUNWics5/cal/sbin/csstats

 

Solaris Packages

The Java Enterprise System installer installs or upgrades a series of Solaris packages (shown in Table 8) that you can later configure to suit your site’s requirements.

If the same version of a particular package is already installed on your server, the installation program will not install that package again and will note that the package already exists. If an older version of a package exists on your server, the installer program will ask you if you want to install the newer version of the package.

Table 8  Solaris Packages

Package

Description

SUNWicu

International Components for Unicode User Files

SUNWicu

International Components for Unicode User Files

SUNWsasl

Simple Authentication and Security Layer (SASL)

SUNWtls

Network Security Services

SUNWldk

LDAP C SDK

SUNWamcom

Sun ONE Identity Server Policy Agent

SUNWj3rt

Java Virtual Machine and Core Class Libraries

Database Version

Calendar Server 6.0 uses Berkeley DB version 3.2.9. If you have an earlier version of Calendar Server that uses Berkeley DB version 2.6, you must upgrade your calendar database to version 3.2.9 using the cs5migrate utility.

Calendar Server 5.x to 6.0 Upgrade Process

If you have Calendar Server 5.x installed at your site, you must follow specific steps to upgrade to the 6.0 release, particularly if you have customized your 5.x release. For more information, refer to the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems.

If you need help with the upgrade from 5.x to 6.0, contact your Sun Microsystems technical support or sales account representative for assistance.

Calendar Server 6.0 Migration Utilities

Updated versions of migration utilities are available in the Calendar Server 6.0 release. The following migration utilities are available to migrate calendar data to Sun ONE Calendar Server:

 

Caution

Before You Migrate

Before you run a migration utility, it is very important to first check with your Sun Microsystems technical support or sales account representative to ensure that you have the latest version of the utility.

If your site is configured for limited virtual domain mode or multiple instances of Calendar Server, contact your Sun Microsystems sales account representative for an evaluation of your migration requirements and to ensure that you have the specific migration utility that supports those requirements.

For information about using all of the migration utilities, see the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems.

cs5migrate

The cs5migrate utility:

csmig

The csmig utility migrates a calendar database that was created before the Calendar Server 6.0 release to a new database that supports the LDAP Calendar Lookup Database (CLD) plug-in.

csvdmig

The csvdmig utility modifies the calendar database and the LDAP directory server data in a manner that allows sites to use hosted (virtual) domains.

ics2migrate

The ics2migrate utility migrates Calendar Server 2.x data and LDAP user preferences to Calendar Server 6.0.

ncs4migrate

The ncs4migrate utility migrates Netscape Calendar Server 4.x calendar data to Calendar Server 6.0.

If you plan to migrate Netscape Calendar Server 4.x calendar data, contact your Sun technical support representative or account manager to obtain the latest version.

csrename

The csrename utility names calendar users in the calendar database and in the LDAP directory server (Calendar Server attributes with the “ics” prefix).

Directory Server Performance

To improve the performance of your LDAP directory server, especially if you are using calendar searches of the LDAP directory consider the following items:

Indexing the LDAP Directory Server Attributes

To improve performance when Calendar Server accesses the LDAP directory server, add indexes to the LDAP configuration file for the following attributes:

Calendar searches of the LDAP directory server are enabled by the following parameter in the ics.conf file:

service.calendarsearch.ldap = "yes" (Default)

To determine if the calendar search performance of the LDAP directory server can be improved, try the following LDAP command:

ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"

where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Express Subscribe > Calendar Search dialog.

Tests have shown that with 60,000 entries, the above search took about 50-55 seconds without indexing icsCalendarOwned. After indexing, the above search took only about 1-2 seconds.

For more information about adding directory server indexes, refer to the Sun ONE Directory Server Configuration, Command, and File Reference on the following Web site:

http://docs.sun.com/coll/S1_ipDirectoryServer_51

Checking and Setting the Size Limit and the Look Through Limit Parameters

To determine if the Look Through Limit (nsslapd-lookthroughlimit) and Size Limit (nsslapd-sizelimit) parameters are set to appropriate values, try the following command:

ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"

where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Express Subscribe > Calendar Search dialog.

If the LDAP server returns an error, the nsslapd-sizelimit or the nsslapd-lookthroughlimit parameter might not be large enough. Follow these guidelines to set these parameters:

Calendar Server 6.0 Documentation

Calender Server 6.0 includes the following documentation. Part numbers (if applicable) are in parentheses.

Sun ONE Calendar Express 6.0 Online Help is available with the Calendar Express software. Other Calendar Server 6.0 documentation is available on the following Web site:

http://docs.sun.com/coll/S1_CalendarServer_60

Known Issues

This section contains a list of the more important known issues at the time of the Calendar Server 6.0 release. This section covers the following topics:

 

Users provisioned before configuring hosted domains cannot create events. (4963237)

Users who were provisioned at a site before the site is configured for hosted domains cannot subsequently create an event or task. Calendar Server returns an error stating that the user does not have the access privilege needed to perform the operation.

Workaround:

For a site to used hosted domains, perform these steps:

  1. Run the csvdmig utility to migrate the installation to use hosted domains. For information about running csvdmig, refer to Chapter 3, “Migrating Calendar Server Data” in the Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems.
  2. Set the hosted domain parameters in the ics.conf file. For example, service.virtualdomain.support must be set to “yes”.

    3. For a list of all parameters that you must set, see Chapter 8, “Using Hosted Domains” in the Sun ONE Calendar Server 6.0 Administrator's Guide.

  3. Set up your directory server organization depending on the version of the LDAP schema you are using—Sun ONE LDAP Schema, v.2 (compatibility or native mode) or Sun ONE LDAP Schema, v.1.

    4. Chapter 8, “Using Hosted Domains” in the Sun ONE Calendar Server 6.0 Administrator's Guide includes descriptions if these schema organizations.

  4. For each domain, add the icsCalendarDomain object class to the domain entry in the directory server, and set icsStatus to “active” and domainAccess to the ACL you want to use for access control.
  5. Create any new domains and users using the Sun ONE Identity Server commadmin CLI utility or the Calendar Server csdomain and csuser utilities.

 

csdomain add or modify LDAP attribute returns an error. (4964855)

The Calendar Server csdomain and the Sun ONE Identity Server commadmin CLI utilities return an error if you try to add or modify an LDAP attribute.

Workaround:

To add or modify an LDAP attribute, use the Directory Server ldapmodify command with an LDIF file.

csdomain fails to delete a domain. (4961879)

The Calendar Server csdomain utility fails to delete a domain.

Workaround:

To delete a domain, use the either the Sun ONE Identity Server commadmin CLI utility or the Directory Server ldapmodify command.

icsCalendarDomain object class is not added to default domain. (4963221)

The Calendar Server Configuration program (csconfigurator.sh) does not add the icsCalendarDomain object class to the default domain, which causes problems if your site is configured for hosted (virtual) domains.

Workaround:

If your site is configured for hosted domains, add the required icsCalendarDomain object class for the default domain are follows:

 

Data loss and button problems occur after resizing windows on GNOME 2.0 desktops. (4957503)

If you are using Netscape Communicator 4.79 with a GNOME 2.0 desktop on a Solaris 8 server, and you try to create a group, search for or enter a name, or resize a window some of the buttons (Cancel, Apply, etc.) will stop working properly and any data you entered will be lost.

This problem does not occur on the CDE desktop.

Calendar Server 5.x to 6.0 migration failed to add master field for old recurring event. (4951065 and 4948511)

You must run the Calendar Server migration tool on a Solaris 8 system only. The migration tool does not work on Solaris 9 systems at this time.

Calendar Server 6.0 cannot export recurring events if they were migrated from 5.x without a master database entry. (4948519)

Recurring events migrated from Calendar Server 5.x to Calendar Server 6.0 cannot be exported to a file if they were migrated without a master database entry — the recurring data will be lost during the export.

Calendar Server configuration does not set up a dc tree in a Schema 1 configuration. (4947880)

Configuring virtual domains in Schema v.1 is not supported in Calendar Server deployments where Messaging Server is not installed. If you install Calendar Server using Schema v.2 in native mode, this problem does not occur. Consequently, Schema v.2 is recommended for virtual domains.

If you are installing Calendar Server for the first time and specify a Schema v.1 configuration, the program will not create the nodes on the dc tree that are required to look up the default domain. The Java Enterprise System install program creates a default domain and a comm_dssetup.pl suffix for the dc tree, but nothing further is created for the dc tree — including support for the default domain.

Workaround:

Before installing Calendar Server, install Messaging Server using the same hosted (virtual) domains you want for calendaring. For information, see “Using Domains Created by Messaging Server” in Chapter 8 of the Sun ONE Calendar Server 6.0 Administrators Guide. If you do not plan to install Messaging Server, use the Directory Server ldapmodify tool and ldif files to add the required nodes to the dc tree. See the iPlanet Messaging Server 5.2 Provisioning Guide for instructions about how to create dc tree domain nodes.

Calendar Server services do not start in a Solaris 8 end-user installation (4947544) and
Calendar Server requires SUNWzlib. (no bugid)

Calendar Server indirectly depends on SUNWzlib (/usr/lib/libz.so.1), to support IS SSO C SDK libraries.

Workaround:

If your deployment encounters a problem starting on a Solaris 8 installation, install the Calendar Server Patch 116557-01 or newer.

Invitation messages for recurring events are sent incorrectly. (4945126)

When you invite external users to a recurring event, Calendar Server sends two requests.
The first request displays all instances as RDATES, and the second request displays a single event on a single day.

When the recipient imports the event into their calendars, the first request creates the recurring series of events, while the second request creates a single event that conflicts with the first instance of the series—which can be very confusing for the user.

Outlook mode export button does not work. (4944130)

Do not use the Outlook Mode Export button provided by the Web user interface. You may not be able to import the exported data into Outlook.

Toolbar does not display properly. (4939219 and 4900115)

If you cannot read the labels on Calendar Server’s toolbar icons, try adjusting your Browser’s text size. For example,

The Medium setting in Internet Explorer and the 100-120% setting in Netscape 7/Mozilla should suffice for most users. For Korean users, some user interface text will be illegible by default and you may have to increase your text to a larger size, which will truncate the toolbar.

(Japanese Netscape7 only) ’TORIKESHI’ line does not display correctly. (4938658)

Multiple day events created in Outlook are displayed incorrectly in Calendar Express. (4930664)

Events created in Microsoft Outlook that span multiple days will not display correctly in Calendar Express. For example, if you create an event in Outlook with a start time of Tuesday at 8:00 a.m. and an end time of Friday at 8:00 a.m., the event displays correctly in Outlook. However, in Calendar Express month view, the event displays as a one-day event on Tuesday with a duration of 72 hours. The event also displays incorrectly in Calendar Express’ week view.

Leading white space in ics.conf causes fatal error when initializing configuration. (4927112)

Do not use white space at the beginning of lines in ics.conf or a fatal error will occur when you initialize the configuration.

Removing SUNWics5 causes error messages. (4927620)

If you use the Java Enterprise System uninstaller to remove Calendar Server packages without configuring them, the following error message will display in the Java Enterprise System uninstall log:

You can safely ignore this message.

Disabled Calendar accounts can be reactivated by the affected user. (4926864)

After an administrator disables a user’s Calendar account, the user can modify icsstatus and reactivate their disabled account.

Workaround:

To prevent users from reactivating their disabled Calendar accounts, the administrator must manually add access control information (ACI) to Directory Server as follows:

  1. Create the cn=Calendar Administrators,ou=Groups,o=acme.com group and add the calmaster user to this group.
  2. Create the following ACIs on o=acme.com:

    3. (targetattr="icsstatus||userpassword||icsallowedserviceaccess||
    icscalendar||icscalendarowned||icsdefaultset||icsdwphost||icsextended||
    icsextendeduserprefs||icsfirstday||icsfreebusy||icsgeo||icspartition||
    icspreferredhost||icsquota||icsset||icssubscribed||icstimezone")
    (targetfilter=(objectClass=icscalendaruser))(version 3.0; acl "Calendar User self modification - product =ics6.0,class=admin,num=1,version=1" ; deny (write) userdn = "ldap:///self";)(targetattr="icsstatus||
    userpassword||icsallowedserviceaccess||icscalendar||icscalendarowned||
    icsdefaultset||icsdwphost||icsextended||icsextendeduserprefs||
    icsfirstday||icsfreebusy||icsgeo||icspartition||icspreferredhost||
    icsquota||icsset||icssubscribed||icstimezone")(targetfilter=(objectClass=
    icscalendaruser))(version 3.0; acl "Calendar User administrator modification - product=ics6.0,class=admin,num=2,version=1"; allow (write) groupdn = "ldap:///cn=Calendar Administrators,ou=Groups,o=acme.com";)

Anonymous calendar is not localized. (4924982)

csdomain add command does not add Calendar Server attributes for a domain. (4920542 and 4922433)

Using the csdomain add command to add Calendar Server attributes for an existing domain causes an LDAP error.

Workaround:

Use the ldapmodify utility to add Calendar Server attributes for a domain. For information about ldapmodify, see the Sun ONE Directory Server Resource Kit Tools Reference.

Comparison page cannot be printed properly in ko/ja locale. (4916961)

Server does not support parsing cn with language tags. (4899053)

When searching for a user whose cn attribute contains a language tag, cshttpd halts and the user must restart the service to reconnect to the web server.

calid does not support non-7-bit characters in current release. (4898611)

Store WCAP commands fail with error numbers 10006 and 10003. (4865723)

When modifying a recurring event or todo, if a rid is not supplied with a Zulu time string, the storeevents and storetodos WCAP commands fail with error numbers 10006 and 10003.

Need message warning that a login is required when Time Zone is changed. (4719346)

When you change the time zone in Calendar Server, you must log out and log back in for the changes to take effect. Until you log in again, any new events will display in the times and dates of the original time zone.

Note that no message or pop-up window is provided to prompt you to log out and log in.

HAStoragePlus resource creation fails if order of FilesystemMountPoints is not correct. (4640848)

The creation of an HAStoragePlus resource fails if the order of the file-system mount points specified in the FilesystemMountPoints extension property is not the same as the order specified in the /etc/vfstab file.

Workaround

Specify file-system mount points in the FilesystemMountPoints extension property in the same order as their sequence in /etc/vfstab.

For example, if the /etc/vfstab file specifies file-system entries in the sequence /a, /b, and /c, the FilesystemMountPoints sequence can be either “/a, /b, /c” or “/a, /b” or “/a, /c”.

Connections aborted with TCP_IOC_ABORT_CONN in system log. (4616287)

If a failover occurs for an HA configuration running Sun Cluster 3.1 on the Solaris 8 U7 or Solaris 9 Operating System and active TCP connections are aborted with the TCP_IOC_ABORT_CONN ioctl, messages such as the following are logged on the console and to system logs.

Jul 24 16:41:15 shemp ip: TCP_IOC_ABORT_CONN: local = 192.018.076.081:0,
remote = 000.000.000.000:0, start = -2, end = 6
Jul 24 16:41:15 shemp ip: TCP_IOC_ABORT_CONN: aborted 0 connection

Workaround

None. These messages are informational only and should not show up in non-debug mode.

Cluster.PMF.pmfd: Error opening procfs control file. (4490877)

When you start HA services or switch HA services between nodes, the following harmless error message displays on the console and in /var/adm/messages:

Cluster.PMF.pmfd: Error opening procfs control file </proc/20700/ctl> for > tag <falcon,habanero_msg,4.svc>: No such file or directory

No fix is available for this Sun Cluster SC 3.0 U3.

Certain Calendar Server windows will not display if you have a Pop-Up blocker enabled. (no bugid)

Disable pop-up blockers for the Calendar URL to ensure all Calendar Server windows will display.

Note

Neither the Norton Inet Security AD_BLOCKER nor the Mozilla built-in POP_BLOCKER will affect Calendar Server windows.

Known Issues for User Management Utility for Sun ONE Messaging and Collaboration. (no bugid)

For a description of known issues in the User Management Utility for Sun ONE Messaging and Collaboration, refer to the “Known Issues” section of the Sun™ ONE Messaging Server 6.0 Release Notes, which are available at the following Internet location:

http://docs.sun.com/coll/S1_MsgServer_60

Known Localization Issues. (no bugid)

For a description of known issues related to Localization, refer to the “Known Issues” section of the Sun™ ONE Messaging Server 6.0 Release Notes, which are available at the following Internet location:

http://docs.sun.com/coll/S1_MsgServer_60

How to Report Problems and Provide Feedback

If you have problems with Sun ONE Calendar Server, contact Sun 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:

To assist in reporting problems, Sun provides the capture_environment.pl tool, a Perl script that captures the current Calendar Server environment, including the ics.conf file, log files, calendar database files, platform information, and core files (if available). These files can be useful to Calendar Server development to debug problems.

To run the capture_environment.pl tool:

  1. If necessary, download the capture_environment.pl tool from customer support.
  2. If necessary, install Perl and add it to your path. (If you cannot install Perl, see the instructions in the capture_environment.pl file that describe how to manually create a snapshot of your Calendar Server environment.)
  3. Log in as (or become) root.
  4. Run the capture_environment.pl tool. The tool copies the files to a directory named archive_directory. On UNIX systems, it places all files into a tar file named tar_file. On Windows 2000 systems, however, you must manually add the files in archive_directory to a Zip file.
  5. Send the tar_file or Zip file to customer support.

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:

docfeedback@sun.com

Please include the part number (816-6715-10) and title (Calendar Server 6.0 Release Notes) in the subject line of your email.

Additional Sun Resources

Useful Sun ONE information can be found at the following Internet locations:

 Copyright © 2003 Sun Microsystems, Inc. All rights reserved.

Sun, Sun Microsystems, the Sun logo, Solaris, Java and the Java Coffee Cup logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Use of Calendar Server is subject to the terms described in the license agreement accompanying it.