Sun Java System Calender Server Release Notes for Microsoft Windows

Sun Java™ System Calendar Server
Release Notes for Microsoft Windows

Version 6 2005Q1

Part Number 819-1578-10

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

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/app/docs/coll/CalendarServer_05q1

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

Date

Description of Changes

February, 2005

Initial release of Sun Java™ System Calendar Server Release Notes for Microsoft Windows.

July, 2005

Release of RR version of Sun Java™ System Calendar Server Release Notes for Microsoft Windows.

About Calendar Server 6 2005Q1

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 2005Q1.

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 2005Q1

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

Automatic Backups

This section covers the following topics:

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.

Tip

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 2005Q1 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 2005Q1 Administration Guide.

To make the Berkeley databases read-only:

  1. Edit the ics.conf file as follows:

    2. caldb.berkeleydb.readonly=”yes”

  2. Restart Calendar Server:

    3. start-cal

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.

Note

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 2005Q1 Administration Guide.

Installation Changes - Directory Server Preparation Script (comm_dssetup.pl)

The Directory Server Preparation Script (comm_dssetup.pl) 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 2005Q1 Developer’s Guide.

Old Deployment Guides Deprecated

The Sun Java System Calendar Server 6 2004Q2 Deployment Guide and the Sun Java 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

Windows 2000 Advanced Server, Service Pack 4

Recommended Browsers for Client Computers

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

Table 2  Recommended Browser Versions for Calendar Server 6

Browser

Windows 98

Windows XP

Windows 2000

Solaris

Red Hat Linux

Macintosh OS X

Netscape™ Communicator

7.2

7.2

7.2

7.2

7.2

7.2

Microsoft Internet Explorer

6.0 SP1 or later

6.0 SP2

6.0 SP1 or later

NA

N/A

N/A

Mozilla™

1.5+

1.5+

1.5+

1.4

1.5+

1.5+

Bugs Fixed in This Release

None.

Important Information

This section contains preinstallation information that you should know before you install Calendar Server 6 2005Q1, 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:

http://docs.sun.com/app/docs/doc/819-0024.pdf

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

<JESINSTALLDIR>\CalendarServer

Communications Express

The default installation location in Windows for Communications Express is:

<JESINSTALLDIR>\CommExpress

Delegated Administrator Utility (formerly User Management Utility)

The default installation location in Windows for Delegated Administrator is:

<JESINSTALLDIR>\DelegatedAdmin

Required Privileges

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

Sun Java Enterprise System Installer

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

Default Installation Directory

The default installation directory for Windows is:

<JESINSTALLDIR>\CalendarServer

Post-Installation Configuration Steps

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

  1. Run the Directory Server Setup Script (comm_dssetup.pl) 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 2005Q1 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 4  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

<JESINSTALLDIR>\CalendarServer\bin

Administrator utilities: csstart and csstop

<JESINSTALLDIR>\CalendarServer\bin

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

<JESINSTALLDIR>\CalendarServer\bin\config

These Ldif files are part of Directory preparation script.

Mail formatting (*.fmt) files

<JESINSTALLDIR>\CalendarServer\config\language

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

<JESINSTALLDIR>\CalendarServer\config\schema

These Ldif files are part of Directory preparation script.

Library files (*.dll)

SSL utilities: certutil and modutil

<JESINSTALLDIR>\CalendarServer\bin

<JESINSTALLDIR>\shared\\bin

Session database

<JESINSTALLDIR>\CalendarServer\bin\config

Counter statistics files: counter and counter.dbstat

<JESINSTALLDIR>\CalendarServer\counter

timezones.ics file

<JESINSTALLDIR>\CalendarServer\bin\data

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, comm_dssetup.pl, 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)

  2. 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 2005Q1 documentation at:

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

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:

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.

Note

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 2005Q1 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 2005Q1 documentation is available on the following Web site:

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

Known Issues and Limitations

This section describes the known issues and limitations of Calendar Server 6 2005Q1 for Windows. For a list of the known issues and limitations in the component, refer to the following Release Notes: http://docs.sun.com/app/docs/doc/819-0023.

This section covers the following topics:

Installation

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. (6293991)

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.

Workaround

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.

Redistributable Files

Sun Java System Calendar Server 6 2005Q1 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:

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

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:

authsdk

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

cgiauth.c

expapi.h

login.html

nsapiauth.c

bin

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

libcsapi_xpcom10.dl

libicsexp10.dl

classes

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

ens.jar

jms.jar

include

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

IIDS.h

nsIEnumerator.h

csIAccessControl.h

nsIEventQueueService.h

csIAuthentication.h

nsIFactory.h

csICalendarDatabase.h

nsIPtr.h

csICalendarLookup.h

nsIServiceManager.h

csICalendarServer.h

nsIServiceProvider.h

csIDBTranslator.h

nsISizeOfHandler.h

csIDataTranslator.h

nsISupports.h

csIMalloc.hpluginscsIPlugin.h

nsISupportsArray.h

csIQualifiedCalidLookup.h

nsMacRepository.h

csIUserAttributes.h

nsProxyEvent.h

mozIClassRegistry.h

nsRepository.h

mozIRegistry.h

nsString.h

nsAgg.h

nsTraceRefcnt.h

nsCOMPtr.h

nsVector.h

nsCRT.h

nsUnicharUtilCIID.h

nsCom.h

nsXPComCIID.h

nsDebug.h

nsXPComFactory.h

nsError.h

nscore.h

nsHashtable.h

pasdisp.h

nsIAtom.h

publisher.h

nsICaseConversion.h

subscriber.h

nsICollection.h

xcDll.h

nsID.h

xcDllStore.h

plugins

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

accesscontrol

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

csAccessControl.cpp

csAccessControl.h

csAccessControlFactory.cpp

authentication

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

csAuthentication.cpp

csAuthentication.h

csAuthenticationFactory.cpp

datatranslator

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

csDataTranslator.cpp

csDataTranslator.h

csDataTranslatorFactory.cpp

userattributes

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

csUserAttributes.cpp

csUserAttributes.h

csUserAttributesFactory.cpp

samples

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

authentication

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

authlogon.c

authlogon.h

authtest.c

csAuthenticationLocal.cpp

csAuthenticationLocal.h

csAuthenticationLocalFactory.cpp

datatranslator

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

csDataTranslatorCSV.cpp

csDataTranslatorCSV.h

csDataTranslatorCSVFactory.cpp

ens

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

apub.c

asub.c

rpub.c

rsub.c

userattributes

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

csUserAttributesDB.cpp

csUserAttributesDB.cpp

csUserAttributesDBFactory.cpp

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:

You might also find it useful to subscribe to the Sun Java System Communications products customer newsletter for periodic updates from the product team about products and upcoming events. Subscribe at http://subscriptions.sun.com/comms/mailinglist.html.

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

http://www.sun.com/hwdocs/feedback

Please include the part number (819-1578-10) and title (Sun Java System Calendar Server 6 2005Q1 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 � 2005 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 http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

SUN PROPRIETARY/CONFIDENTIAL.

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 � 2005 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 http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Propri�t� de SUN/CONFIDENTIEL.

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.