Sun Java System Calendar Server Release Notes for Microsoft Windows

Sun Java™ System Calendar Server Release Notes for Microsoft Windows

Version 6 2005Q4

Part Number 819-4265-10

These Release Notes contain important information available at the time of release of Sun Java System Calendar Server 6 2005Q4 for Microsoft Windows. Known issues and limitations, and other information are addressed here. Read this document before you begin using Calendar Server 6 2005Q4.

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: 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 product documentation.

These release notes contain the following sections:

Read these Release Notes before you install and configure Calendar Server.

Sun Java™ System Calendar Server was formerly Sun™ ONE Calendar Server.

Release Notes Revision History

Table 1  Revision History


Description of Changes

February 2006

Revenue release.

November 2005

Beta release.

About Calendar Server 6 2005Q4

Calendar Server is a scalable, web-based solution for centralized calendaring and scheduling for enterprises and service providers. Calendar Server supports user 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 6 2005Q4.

Calendar Server offers two graphical user interfaces, Calendar Express and Communications Express. It also offers customers the flexibility to use the Web Calendar Access Protocol (WCAP) to access calendar data directly in either text\calendar or text\xml format.

What’s New in Calendar Server 6 2005Q4

Calendar Server 6 2005Q4 includes the following changes and new features:

Automatic Backups

This section covers the following topics:


Make sure perl is already available in the host that is to be configured for hotbackup.

How to Recover from a Database Failure

If your current database ever fails and you need to replace it with a backup, the hotbackup copy can be used with a minimum of processing (and thus a minimum of downtime). To prepare the hotbackup copy, you need only copy the unapplied transactions to the hotbackup directory and run db_recover against it. That utility applies the final unapplied transaction logs, and checks for corruptions. Then, run db_verify to check the state of the database. If the database is OK, then the hotbackup copy is ready to be used as your new production copy.

For more information about the new autobackup feature and the procedures needed to configure and administer it, see the chapter on autobackups in the Sun Java System Calendar Server Administration Guide.

For more information about restoring one of your automatic backups, see the “Troubleshooting” chapter of the Sun Java System Calendar Server Administration Guide.

Until automatic backups are enabled, the service sends an error message every 24 hours to the calendar administrator saying it is unconfigured. Performing hotbackups is a best practice for Calendar Sever.


If you have automatic backups disabled, be sure to enable circular logging (caldb.berkeley.circularlogging=”yes”) so that old transaction logs do not fill up available diskspace. Circular logging must be disabled (caldb.berkeley.circularlogging=”no”) when doing automatic backups.

Configuring Automatic Backups in CSConfig.bat

The configuration program now asks you if you want to configure automatic backups. The configuration program will set up automatic backups (hotbackups) for you, or at a later date, you can configure automatic backups by following the instructions in the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Read-Only Database

Calendar Server uses Berkeley Database for its calendar databases (other than LDAP for the user and resource information). If your current Berkeley databases become corrupted and you need to continue to provide user access to them while you are recovering the data, Calendar Server 6 2005Q1 allows you to put the databases in read-only mode. In this mode, the server will not accept any update or delete transactions against any of the databases. Only read transactions are supported.

With automatic backups configured, the service runs db_verify against each new snapshot of the databases. If corruption is detected, it automatically sends a warning message to the administrator. The administrator can then put the databases into read-only mode.

However, you might detect corruption later on during the day, between snapshots. If this is the case, you can put your current databases into read-only mode while you are trying to recover. You can not selectively place individual Berkeley databases into read-only mode.

For more information about this, see the “Troubleshooting” chapter in the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

To make the Berkeley databases read-only:

  1. Edit the ics.conf file as follows:
  2. caldb.berkeleydb.readonly=”yes”

  3. Restart Calendar Server:
  4. start-cal.bat

Support for Rebuilding Alarm Database Separately

In earlier releases of Calendar Server, when you ran csdb rebuild, all the Calendar Server databases were rebuilt. In Calendar Server 6 2005Q1, you can choose to rebuild only the alarms database. The reason for this is that analysis has shown that the alarms database was the most prone to corruption and was the quickest to rebuild. If you do not know which database is corrupt, you can run it for the alarm database only first to see if that catches the problem. If not, you can then run the full rebuild utility (csdb).

Automatic Database Verification in csdb rebuild

In earlier releases of Calendar Server, after rebuilding databases with csdb, you had to run db_verify manually to verify the rebuilt databases. Now, the csdb utility rebuild command automatically runs db_verify on the rebuilt database.

User Management Utility Name Change

The User Management Utility, a command-line only utility used for provisioning and management of users, resources and domains, has been renamed to the Delegated Administrator Utility and is still the only provisioning tool for Schema 2 that supports Calendar Server.

The Delegated Administrator graphical user interface released for 2005Q1 does not support Calendar Server.


This is not the same Delegated Administrator used by earlier versions of Messaging Server for Schema 1provisioning. (It never supported Calendar Server either.)

If you are still using Schema 1, use the Calendar Server command-line utilities described in the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Installation Changes - Directory Server Preparation Script (

The Directory Server Preparation Script ( is no longer bundled with the Calendar Server and Messaging Server products. It has become a separately installable component in the Java Enterprise System installer. On the component selection panel, you can select the Directory Server Preparation Script by itself. Or, it is selected automatically if you select Directory Server.

In general, due to product changes, you will need to install the new Directory Server Preparation Script and run it even if you have run earlier versions. Do not rerun an earlier version you may already have as it will not contain the necessary updates.

Web Calendar Access Protocol (WCAP) Changes

The following changes were made in WCAP:

Freebusy Redirect URL

This sections covers the following topics:

What is the Freebusy Redirect URL Feature?

For customers migrating from Microsoft Exchange to Calendar Server, a new feature was added to WCAP that allows both databases to be searched, first the Calendar Server database and then the Microsoft Exchange database. This enables customers to maintain calendar services during the transition. To accomplish this, two changes were made in WCAP:

How Does it Work?

When the server receives a free_busy command, it checks the Calendar Server calendar database. If the server can not find the calendar, the following steps take place:

  1. The server checks to see if the noredirect parameter was passed in the get_freebusy command.
  2. If the value of the noredirect parameter is 0, or was not passed in, the server looks for the value in the ics.conf file parameter service.wcap.freebusy.redirecturl.
  3. If the service.wcap.freebusy.redirecturl parameter exists and has a URL as its value, it passes the URL back to the requesting program. It is up to the requesting program to use the URL to look for the calendar in the Microsoft Exchange databases.
  4. If either of the following is true, the server returns an error.
    • The service.wcap.freebusy.redirecturl parameter either does not exist or has a blank value.
    • The get_freebusy command passed in the noredirect parameter with a value of 1.

Changes to Existing WCAP Commands

The following parameter changes were made to existing WCAP commands:

For further information about these parameters, see the Sun Java System Calendar Server 6 2005Q4 Developer’s Guide.

Old Deployment Guides Deprecated

The Sun Java System Calendar Server 6 2004Q2 Deployment Guide and the Sun Java System Communications Services 6 2004Q2 Enterprise Deployment Planning Guide have been deprecated in favor of the Sun Java System Communications Services 6 2005Q1 Deployment Planning Guide.

Hardware and Software Requirements

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

Microsoft Windows 2000 Advanced Server, Service Pack 4

Microsoft Windows 2003 Enterprise Server

Microsoft Windows XP SP1, SP2

Recommended Browsers for Client Computers

Sun Java System Calendar Express 6 2005Q4 requires a JavaScript-enabled browser. For optimal performance, the following browsers are recommended:

Table 2  Recommended Browser Versions for Calendar Server 6


Microsoft Windows 98

Microsoft Windows XP

Microsoft Windows 2000


Red Hat Linux

Macintosh OS X

Netscape™ Communicator







Microsoft Internet Explorer

6.0 SP1 or later

6.0 SP2

6.0 SP1 or later











Bugs Fixed in This Release


Important Information

This section contains pre installation information that you should know before you install Calendar Server 6 2005Q4, including:

Front-End and Back-End Machines and Operating Systems

For Calendar Server installations that separate functionality across front-end and back-end machines, the hardware platforms must be the same on each end.

For more information about installing Calendar Server on front-end and back-end machines, see the System Calendar Server 6 20005Q1 Administration Guide at:

Windows Platform Support

Sun Java Enterprise System runs on the Windows platform. The default installation locations are listed for the following:

Calendar Server

The following table provides the directory path details for Calendar Server:

Table 3  Directory Path details on Windows Platform

Windows Directory


Communications Express

The default installation location in Windows for Communications Express is:


Delegated Administrator Utility (formerly User Management Utility)

The default installation location in Windows for Delegated Administrator is:


Required Privileges

To run the Sun Java Enterprise System installer or the Calendar Server 6 2005Q4 configuration program on Windows Operating Systems, you must log in as administrator or user with administrator privileges.

Upgrading From an Earlier Version of Calendar Server 6

Do not attempt to upgrade Calendar Server using the Sun Java Enterprise System installer.

Patch Requirement Information

The following table gives the numbers and minimum versions for the alignment patches. All patches referred to in this section are the minimum version number required for upgrade. It is possible that a new version of the patch has been issued since this document was published. A newer version is indicated by a different version number at the end of the patch. For example: 123456-04 is a newer version of 123456-02 but they are the same patch ID. Refer to the README file for each patch listed for special instructions.

To access the patches, go to

Table 4  Calendar Server 6 2005Q4 Alignment Patches Required For Windows

Patch Number

Patch Description


Windows (MSI): Directory Preparation Tool


Windows (MSI): Shared Components


Windows (MSI): Sun Java™ System Calendar Server 6 2005Q4

For detailed information about Upgrade procedure of the Calendar Server from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for Microsoft Windows located at

Upgrading Your Calendar Database

If you have Calendar Server 6 installed, with Berkeley DB version 3.2.9, the conversion to the current 4.2 version will be done automatically. You do not need to run any other database migration programs.

If you have a Calendar Server 5 installation that uses Berkeley DB version 2.6, you must upgrade your calendar database to version 4.2. using the cs5migrate utility. The utility is available upon request from technical support.

If you have an existing Calendar Server 2 installation, you must upgrade to Calendar Server 5 before you can migrate to the current release.

The cs5migrate utility performs the following tasks:

In addition, if the -r option is specified, cs5migrate creates master and exception records for all recurring events and tasks. Going forward these records will be automatically generated by Calendar Server. If you need to migrate your database but do not plan to use the Connector for Microsoft Outlook, you do not need run cs5migrate with the -r option.

Contact technical support for the download location and documentation for either utility.


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

And, as always, never migrate your database without first performing a full backup

Sun Java Enterprise System Installer

Install Calendar Server 6 2005Q4 using the Sun Java Enterprise System installer. The Java Enterprise System installer installs the Sun component product packages, including Calendar Server 6 2005Q4, and the shared components that are used by the various products.

Default Installation Directory

The default installation directory for Windows is:


Post-Installation Configuration Steps

After installing Calendar Server 6 2005Q1, you must configure it as follows:

  1. Run the Directory Server Setup Script ( to configure Sun Java System Directory Server for Calendar Server schema.
  2. Run the Calendar Server Configuration Program (CSConfig.bat) to configure your site’s specific requirements.

For instructions, refer to the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Where to Find Calendar Server Data and Utilities

For Java Enterprise System Release 3, Calendar Server provides the links for Windows locations shown in the following table.

Table 5  Directory Locations 

File Names

Windows 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: csmig, csvdmig


Administrator utilities: csstart and csstop


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


These Ldif files are part of Directory preparation script.

Mail formatting (*.fmt) files


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


These Ldif files are part of Directory preparation script.

Library files (*.dll)

SSL utilities: certutil and modutil



Session database


Counter statistics files: counter and counter.dbstat


timezones.ics file


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 various attributes.

The configuration program,, will optionally do the indexing for you.

To see the performance difference indexing can give you, perform the following test:

  1. Enable calendar searches of the LDAP directory server by making sure the following parameter in the ics.conf file is set to “yes”:
  2. service.calendarsearch.ldap = "yes" (Default)

  3. Run the following LDAP command:

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 Java System Directory Server 5 2005Q4 documentation at:

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"

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:

Communications Express Using Schema 1

There is one issues with Schema 1 in Communications Express:

Provisioning Tools

There are two tools for provisioning users, groups and domains for Calendar Server: The Delegated Administrator Utility and Calendar Server utilities. For information on Delegated Administrator, see the Sun Java System Communications Services 6 2005Q1 Delegated Administrator Guide. For information on the Calendar Server utilities, see the Sun Java System Calendar Server 6 2005Q1 Administration Guide.


Do not attempt to provision users through the Access Manager Console. Though it is possible to create users and assign them a calendar service, do not use this method as results will be unpredictable and negatively impact your deployment.

Calendar Server 6 Documentation

Calendar Server 6 includes the following documentation. Part numbers are in parentheses.

Calendar Express 6 2005Q4 Online Help is available with the Calendar Express software. Communications Express 6 2005Q1 Online Help is available with the Communications Express software.

Calendar Server 6 2005Q4 documentation is available on the following Web site:

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at:

For information on Sun’s commitment to accessibility, visit

Compatibility Issues

The following table lists the known incompatibilities between Calendar Server 6 2005Q4 and earlier versions.

Table 6  Compatibility Issues




Access Manager now has two install types: Enhanced and Compatible.

At installation, you must choose Compatible as the install type on the following panel:

Access Manager: Administration (1 of 6)

If the wrong Access Manager is installed, you will not be able to run Delegated Administrator.

The Directory Preparation Tool ( is now in its own package

To install the package, be sure the Directory Preparation Tool is selected in the appropriate installer panel.

This release of Communications Express is incompatible with the 2004Q2 version of Calendar Server.

If you upgrade Communications Express, you must also upgrade Calendar Server.

This also applies to Messaging Server.

Known Issues and Limitations

This section describes the known issues and limitations of Calendar Server 6 2005Q4 for Microsoft Windows.

This section covers the following topics:


Removing all Instances of Multi-Valued User Preferences

Each set_userprefs command removes only one instance of a multi-valued preference.


To remove all instances of a multi-valued user preference, you must issue one set_userpref command per instance.

For example: Perform a get_userprefs to list all of the user preferences. If there are multiple values for a preference, such as icsSubscribed, then you must issue one set_userprefs command to delete the preference for each of the values listed.

Pop-up Blockers

Certain Calendar Server windows will not display if you have a pop-up blocker enabled.


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


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

Provisioning Users for Communications Express in Schema 1 Mode

The csuser utility does not enable users it creates for Address Book.


Enable the user using ldapmodify.

Multiple Domains (Hosted Domains)

The configuration program,, configures only a single domain.


If you need a multiple domain calendar environment (called either Virtual Domains or Hosted Domains), you must do two things:

Enable hosted domains.

Add the domains yourself using Delegated Administrator, or the csdomain utility if you are still using Sun LDAP Schema 1.

See “Setting up Hosted Domains” and “Administering Hosted Domains” in the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Reported Problems

The following is a list of problems reported on the product.

Table 7  Reported Problems

Bug ID



Calendar Server utility cscal will not add more than two owners to a calendar at a time, no matter how many are specified in the command.


When a user modifies an event and chooses the option to modify today’s event and all future events, all previous events are deleted and will no longer display in the UI.


SSL initialization fails in SSLv2 mode. Unable to make use of SSLv2 client.


If you start a process (such as enpd) and then disable it in the ics.conf file, when stop-cal is issued, the system will not stop the disabled process.


Re-enable the process in the ics.conf file and then issue the stop-cal command. After all processes are stopped, then disable any processes you do not want running before issuing start-cal.


Hot backup log file not being purged per ics.conf settings as other log files are. To keep file to a minimum, decrease verbosity. (verbosity level 3 is the default).


In Schema 1 mode with hosted domains, if the DC tree is missing or improperly provisioned, calendar utilities can fail. You must create the DC tree nodes prior to creating or otherwise managing calendars.


If DWP is disabled while the DWP process is running, stop-cal will not stop it. stop-cal should stop all services rather than just those enabled.


Vague error message. In a hosted domain environment, if the basednpassed tocsdomain does not exist. The actual message received is: “FAIL: icsLdapServer: Null argument to function.” This type of error message is vague because the error message originates several levels down and could be caused by many different circumstances. Rather than just passing the error through, the higher level program should interpret the error message before bubbling it up to the next higher level.


Leading white space stripped from description field when stored in calendar server.


In virtual domain mode, if maillookup is configured in the ics.conf file, a WCAP error is returned. Fixed in patch 1. Fix: In virtual domain mode, maillookup is ignored in favor of ugldap in the ics.conf file.


Comment out the maillookup parameters in the ics.conf file.


SSL can not be enabled or disabled on individual hosted domains. (RFE)


The error messages given by csdomain are vague and need to be more explicit.


Trusted circle SSO fails when authentication filter is configured in calendar.


csresource -k option defaults differently depending on if you include it blank or just omit it.


Incorrect default ACE listed for resources in csresource merge.


External organizers get one reply per instance for recurring events when the attendee accepts all.


Import command puts in wrong organizer email address if organizer is external.


cscal -v list does not work.

6275605 not reporting warnings when there are more than two log files in the live calendar database.


Need a way to turn off local.user.authfilter for proxy authentication.


CSHTTPS hangs without error message if local.ldap.cache.homedir.path folder is invalid.


Change the local.ldap.cache.homedir.path to a valid folder name in ics.conf file and restart the services.


func_events test shows difference in output. DTEND value is not shown in the output message of wcap command


Active Perl 5.8.3 is required to be pre-installed on the system if Instant Messaging, Messaging Server and Calendar Server are selected for installation.

Command Line Utilities

start-cal and stop-cal utilities does not work from command line (6252512)

Install and configure Calendar Server in Windows. From the installation folder of Calendar Server, if you try to start the calendar services using start-cal utility or stop the calendar services using stop-cal utility, it does not work.


Start the Calendar Server utility Services from Start>Control Panel>Administrative Tools>Services. Right-click on the service name and click Start from the popup menu. The calendar services should be started in this order: ENS, Notification, Admin, HTTP.

To stop the Calendar Services, right-click on the service name and click Stop from popup menu. Stop the services in this order: HTTP, Admin, Notification, ENS.

For starting and stopping Calendar services, command-line bat files (cs-start.bat and cs-stop.bat) are available.

Sun Java™ System Communications Express

These Release Notes contain important information available at the time of release of Sun Java System Communications Express 6 2005Q4 for Microsoft Windows. Known issues and limitations, and other information are addressed here.

These release notes contain the following sections:

About Communications Express 6 2005Q4

Sun Java System Communications Express Version 6 2005Q4 provides an integrated web-based communication and collaboration client that consists of three client modules - Calendar, Address Book and Mail. The Calendar and Address Book client modules are deployed as a single application on any web container and are collectively referred as the Unified Web Client (UWC). Messenger Express is the standalone web interface mail application that uses the HTTP service of the Messaging Server.

Communications Express Supported Browsers

Communications Express can be viewed using:

Communications Express Installation Notes

The following are the dependent services for Communications Express:

  1. Directory Server. Install Sun Java System Directory Server version 5.2.
  2. Calendar Server. Install Sun Java System Calendar Server Version 6.1.
  3. Web Server. Install Sun Java System Web Server version 6.1 SP4 with JDK version1.5.
  4. Messaging Server. Install Sun Java System Messaging Server 6.2.
  5. Access Manager. Install Sun Java System Access Manager 6.2.
  6. Application Server. Install Sun Java System Application Server 8.1.


    Communications Express has been tested and is supported only with the server versions mentioned above. The Communications Express for Sun Java Enterprise System 3 Release can be deployed only on Sun Java System Application Server 8.1. The Communications Express Configurator supports only the Domain Administration Server (DAS) deployment for Application Server 8.1.

Refer to Chapter 2, “Installing and Configuring Communications Express” of Sun Java System Communications Express Administration Guide for instructions on how to install and configure Communications Express.

Refer to Chapter 4, “Implementing Single Sign-On” of Sun Java System Communications Express Administration Guide for instructions on how to configure Communications Express when Access Manager is deployed.

Communications Express Known Issues and Limitations

This section contains a list of the known issues and limitations with Sun Java System Communications Express Version 6 2005Q4. The following topics are the known issues:

Deployment on Application Server is not supported

Deployment of Communications Express on Application Server is not supported.



Redistributable Files

Sun Java System Calendar Server 6 2005Q4 contains the following set of files for which Sun Microsystems, Inc. grants you a non-exclusive, non-transferable, limited license to reproduce and distribute in binary form.

In addition, you may copy and use but not modify the listed header files and class libraries solely to cause your resulting binaries to be able to interface with Sun’s software APIs.

Sample code is provided solely for reference purposes pursuant to creating the above mentioned binaries.

All the redistributable files for Calendar Server are for the plug-in API, known as CSAPI. The API is described in the Sun Java System Calendar Server 6 2005Q1 Developer’s Guide at:

In the following files, cal_svr_base is the directory into which Calendar Server was installed. The default for Windows is <JESINSTALLDIR>\CalendarServer, for Solaris is /opt/SUNWics5/cal, and for Linux is /opt/sun/calendar.

Redistributable files are found in various subdirectories of cal_svr_base\csapi:


The following are the redistributable files in this subdirectory (cal_svr_base\csapi\authsdk\):






The following are the redistributable files in this subdirectory (cal_svr_base\csapi\bin\):




The following are the redistributable files in this subdirectory (cal_svr_base\csapi\classes\):




The following are the redistributable files in this subdirectory (cal_svr_base\csapi\include\):


















































This directory (cal_svr_base\csapi\plugins\) has redistributable files in the following subdirectories:


The following redistributable files are found in this subdirectory (cal_svr_base\csapi\plugins\accesscontrol\):





The following redistributable files are found in this subdirectory (cal_svr_base\csapi\plugins\authentication\):





The following redistributable files are found in this subdirectory (cal_svr_base\csapi\plugins\datatranslator\):





The following redistributable files are found in this subdirectory (cal_svr_base\csapi\plugins\userattributes\):





This directory (cal_svr_base\csapi\samples\) has redistributable files in the following subdirectories:


The following redistributable files are found in this subdirectory (cal_svr_base\csapi\samples\authentication\):








The following redistributable files are found in this subdirectory (cal_svr_base\csapi\samples\datatranslator\):





The following redistributable files are found in this subdirectory (cal_svr_base\csapi\samples\ens\):






The following redistributable files are found in this subdirectory (cal_svr_base\csapi\samples\userattributes\):




How to Report Problems and Provide Feedback

If you have problems with Sun Java System 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 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 tool:

  1. If necessary, download the 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 file that describe how to manually create a snapshot of your Calendar Server environment.)
  3. Log in as (or become) root.
  4. Run the 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 URL

Please include the part number (819-4265-10) and title (Sun Java System Calendar Server 6 2005Q4 Release Notes for Microsoft Windows) in the subject line of your email.

Additional Sun Resources

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

Copyright � 2006 Sun Microsystems, Inc. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries.


U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Use is subject to license terms.

This distribution may include materials developed by third parties.

Portions may be derived from Berkeley BSD systems, licensed from U. of CA.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Copyright � 2006 Sun Microsystems, Inc. Tous droits r�serv�s.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.


L'utilisation est soumise aux termes du contrat de licence.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.