test

Sun Java System Communications Services 2005Q4 Release Notes

Chapter 1 Sun Java System Calendar Server 6 2005Q4 Release Notes

Version 6 2005Q4

These Release Notes contain important information available at the time of the general release of Sun JavaTM System Calendar Server 6 2005Q4 including:

Note –

A patch is available at Sun Solve for this version of Calendar Server. For more information, see Important Patch Information.

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

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 This Release.

Calendar Server offers a graphical user interface, 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.

The deprecated graphical user interface, Calendar Express, is supported for backward compatibility only, but is no longer under development .

Release Notes Revision History

Table 1–1 Sun Java System Calendar Server Revision History

Date 

Description of Changes 

6/29/2005 

Beta Release Notes 

10/05/05 

General Release Calendar Server 6 2005Q4 

What's New in This Release

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

Requirements

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

Note –

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

More specifically, due to big-endian versus small-endian incompatibility, you can’t use both an x86 platform machine and a SPARC platform machine in the same Calendar Server deployment containing front-end and back-end machines.

Moreover, mixing Solaris x86 and Linux operating systems for front-end and back-end machines has not been tested and is not currently supported.

Hardware Requirements and Recommendations

Software Requirements and Recommendations

Supported Software Platforms

Recommended Browsers for Client Computers

See Supported Browsers in Chapter 5, Sun Java System Communications Express 6 2005Q4 Release Notes.

Important Patch Information

Platform 

Patch Number 

Solaris, SPARC 

116577 

x86 

116578 

Linux 

116851 

ProcedureHow to Find Patches on SunSolve

  1. For the current list of required patches for Sun Java System Calendar Server, go to:

    http://sunsolve.sun.com

  2. Select either “Patches” or “Patch Portal”.

  3. Follow the Sun Java System Calendar Server links.

    As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

Installation Notes

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

Caution – 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.

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.

More specifically, due to big-endian versus small-endian incompatibility, you can’t use both an x86 platform machine and a SPARC platform machine in the same Calendar Server deployment containing front-end and back-end machines.

Moreover, mixing Solaris x86 and Linux operating systems for front-end and back-end machines has not been tested and is not currently supported.

Linux Platform Support

Java Enterprise System runs on the Linux platform. The major differences in user experience will be the path names where product directories are installed. The Linux platform installs into a different directory than the Solaris platform.

The following table shows the default installation directory paths for Solaris and Linux:

Solaris Default Directories 

Linux Default Directories 

/opt/SUNWics5/cal/ (cal_svr_base)

/opt/sun/calendar (cal_svr_base)

/etc/opt/SUNWics5/config

/etc/opt/sun/calendar/config

/var/opt/SUNWics5/

/var/opt/sun/calendar

Tip –

In the documentation, the default installation directory for Calendar Server is referred to as cal_svr_base.

OS Patches

You must apply the required operating system patches before installing Calendar Server. Refer to the system release notes, Sun Java Enterprise System 2005Q4 Release Notes, for a list of required patches.

Required Privileges

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

Linux Package Names

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.

The following table lists the Linux package names for the various Calendar Server related components.

Component 

Package Name 

Calendar Server 

sun_calendar-core 

sun-calendar-api 

Localized Packages: 

Spanish 

sun-calendar-core-es 

Korean 

sun-calendar-core-ko 

French 

sun-calendar-core-fr 

Chinese 

sun-calendar-core-zh_CN 

German 

sun-calendar-core-de 

Japanese 

sun-calendar-core-ja 

Taiwanese 

sun-calendar-core-zh_TW 

Upgrading From an Earlier Version of Calendar Server 6

Do not attempt to upgrade Calendar Server using the Sun Java Enterprise System installer. You must use the patchadd process. Find instructions for upgrading from earlier Calendar Server releases in the Sun Java Enterprise System 2005Q4 Upgrade and Migration Guide. See also the Sun Java Enterprise System 2005Q4 Release Notes.

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.

Caution – Caution –

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.

Postinstallation Configuration

After installing or upgrading to Calendar Server 6 2005Q4 and before you can use Calendar Server, 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 (csconfigurator.sh ) 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 Program Files

The following table shows where to find various files and programs referred to in the documentation for both the Solaris and Linux platforms:

File Names 

Solaris Locations 

Linux 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

/opt/SUNWics5/cal/sbin

/opt/sun/calendar/sbin

Migration utilities: csmig and csvdmig

/opt/SUNWics5/cal/sbin

/opt/sun/calendar/sbin

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

/opt/SUNWics5/cal/sbin

/opt/sun/calendar/sbin

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

After installation, files are located at: /opt/SUNWics5/cal/ config-template

During configuration, the various files from the above directory are moved to the locations specified by the configuration options you choose. 

After installation, the files are located at: /opt/sun/calendar/ config-template

During configuration, the various files from the above directory are moved to the locations specified by the configuration options you choose. 

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

After installation, the files are located at: 

/opt/SUNWics5/cal/ config/schema/ comm_dssetup.pl writes these files to the Directory Server.

After installation, the files are located at: 

/opt/sun/calendar/config/ schema/comm_dssetup.pl writes these files to the Directory Server.

Schema LDIF 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

After installation, the files are located at: 

/etc/opt/SUNWics5/ config/schema

comm_dssetup.pl writes these files to the Directory Server.

After installation, the files are located at: 

/etc/opt/sun/calendar/ config/schema

comm_dssetup.pl writes these files to the Directory Server.

Mail formatting (*.fmt) files

After installation, the files are located at: /opt/SUNWics5/cal/ config-template

After configuration, the files are located at: /etc/opt/SUNWics5/ config/language

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

After installation, the files are located at /opt/sun/calendar/ config-template

After configuration, the files are located at: /etc/opt/sun/calendar/config/ language

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

Library (.so) files 

SSL utilities: certutil and modutil

/opt/SUNWics5/cal/lib

/opt/sun/calendar/lib

Session database 

/opt/SUNWics5/cal/lib/ http

/opt/sun/calendar/lib/http

Counter statistics files: counter and counter.dbstat

/opt/SUNWics5/cal/lib/ counter

/opt/sun/calendar/lib/ counter

timezones.ics file

/opt/SUNWics5/cal/data

/opt/sun/calendar/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.

Tip –

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

  1. Before indexing, time how long it takes to run 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.

  2. Run indexing for icsCalendarOwned.

  3. Again run the following LDAP command, and time it:


    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.

  4. Compare the times. There should be a measurable time difference.

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 ID*)
(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 ID is the value that an end user can enter in a calendar search dialog in Communications Express.

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 are two 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 and Calendar Server utilities. Delegated Administrator has two user interfaces: the Console, a graphical user interface, and the Utility, a command-line interface. For information on Delegated Administrator, see the Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide. Instructions on use of the Console can be found in the Delegated Administrator Console online help.

For information on the Calendar Server utilities, see the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Caution – Caution –

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.

Documentation Updates

Calender Server 6 2005Q4 includes the following documentation. Part numbers are in parentheses.

Communications Express Online Help is available on the interface.

Delegated Administrator Console Online Help is available on the interface.

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

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

Sun Java Enterprise System Technical Note: Sun Java System Calendar Frequently Asked Questions (819–2631) This FAQ document has not been updated for this release.

Compatibility Issues

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

Incompatibility 

Impact 

Comments 

Access Manager now has two install types: Legacy and Realm. 

At installation, you must choose Legacy 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 (comm_dssetup.pl) under /opt/SUNWics5 doesn't work.

comm_dssetup.pl is now in its own package installed in /opt/SUNcomds for Solaris, and /opt/sun/comms/dssetup for Linux

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

The configuration program for the Delegated Administrator has changed.  

Install Delegated Administrator and run the configuration program. The current program is located at: for Solaris, /opt/SUNWcomm/sbin/config-commda

for Linux /opt/sun/comms/config-commda

Upgrade to the new Delegated Administrator when installing this version of Calendar Server. 

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. 

Problems Fixed in This Release

The list that follows are problems reported for Calendar Server 2005Q1 that are fixed in this release:

4526765

Problem: 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.

4945126

ITIP message for recurring events is incorrect.

4963040

csdb rebuild appends default directories onto end of specified target directory.

5018344

search_calprops.wcap should use better LDAP search filter to return correct result.

5023720

Usage is incorrect for csclean -g option.

5044765

Calendar Server package uses question mark for group ID of top-level directory.

5044776

Calendar Server packages use parametric attributes instead of assigned owner.

5053566

Linux: Calendar Server files installed by default under /etc/opt/sun/config.

5088397

icsStatus is not honored at the domain level.

5105867

Calendar Server has private copies of shared components.

5110172

DWP daemon fails to start on Solaris x86 platform.

6173572

cshttpd crashes when LDAP cache is enabled.

6173712

When mail lookup is configured in virtual domain mode, Calendar Server error 29 is thrown. Mail lookup is not supported in virtual domain mode. Use user and group LDAP instead. In the revenue release, mail lookup settings in the ics.conf file are ignored in virtual domain mode.

6174162

Confusing error messages when running csrename.

6182625

WCAP change: add update as a method, otherwise after a first modification, Outlook gets error on subsequent modifications. Change WCAP version to 3.3.0.

6193286

Time zone from system not recognized.

6193665

When using virtual domains (hosted domains) in Schema 1, search_calprops.wcap with primaryOwner=1, does not return consistent results.

6197272

Problem: Setting service.http.ssl.port.enable=”yes” does not disable the regular HTTP port.

Fix: Documentation. HTTPS will only listen on the SSL Port if “yes” is specified. Both service.http.enable and service.http.ssl.port.enable must be set to “yes” on the back-end servers in order for SSL to work.

Workaround:There is no way to disable HTTP from listening on a port. However, an administrator can change the service.http.port to an undisclosed port number.

6197553

csdwpd causes cluster failover after using Outlook Connector.

6206703

Can't login as user on hosted domain.

6209863

csuser should not be allowed to use -c option with create.

6211629

Problem: csconfigurator.sh input area in GUI is too narrow to see in Japanese locale.

6211917

get_freebusy.wcap crashes cshttpd.

6215989

Calendar Server crashes with login.wcap request with specific arguments when browser.cache.enable is set to “yes”.

6219300

csrename doesn't update the deletelog, leaving orphaned entries in the deletelog.

6219332

In silent mode, still prompted to answer questions by csconfigurator.sh.

6219906

Problem: In virtual domain mode, if maillookup is configured in the ics.conffile, a WCAP error is returned.

Fix: In virtual domain mode, maillookup is ignored in favor of ugldap in the ics.conf file.

6220063

cshttpd crashes in getRemovedAttendees .

6224389

Saving a recurring event crashes cshttpd.

6224683

Fix up notification service. Multiple changes.

6226361

Events vanish from attendee calendars if organizer is changed by co-owner.

6227703

Possible cshttpd crash when LDAP cache is enabled.

6228400

System crash when issuing get_userprefs.wcap.

6230748

csadmind crashes in caldb_GetNextAlarmFromQueue.

6232493

get_freebusy.wcap crashes cshttpd if dtstart is set.

6232755

list.wcap, subscribe_users.wcap, and unsubscribe_users.wcap crash cshttpd

6233224

Can't install patch —18 on alternate root.

6234232

Daylight savings time for New Zealand starts and ends on wrong day.

6234868

cshttpd enters an infinite loop when calling storeevents.wcap from Outlook with a mailto: address containing a slash (/).

6239645

Making an exception with no change in date and time should not cause a doublebooking error.

6240039

csadmind crash in UpdateOrganizerPendingStatus.

6240332

Incorrect file ownership causing failure to start services.

6240579

csstored.pl has an error in the following line: if ($log_files_count > 1)(). It should be > 2().

6241683

Changing recurring to non-recurring events does not work.

6241916

csadmind crashes when processing a GSE entry (internal attendee replying to an external organizer.

6241941

csadmind crashes while processing recurring event but the stack is processing a recurring task (todo).

6246400

All-day event missing in week view.

6249180

Calendar Server does not return all calendars for user in alias domain.

6251866

WCAP should offer the ability not to send notification when meeting details are changed. This was implemented as the smtpNotify parameter added to the storeevents and several delete commands. For further information see What's New in This Release.

6262770

When importing a word document into Communications Express, cshttpd crashes.

6265287

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

6266149

Basic changes needed to transition from legacy mode to virtual domain mode (hosted domains).

6269282

System does not honor local.ldap.cache.cleanup.interval correctly.

6269721

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

6269822

Problem:Incorrect default ACE listed for resources in csresource merge.

6274603

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

6274607

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

6274639

Problem: Back-end processor problem in csdwpd causes front-end cshttpd to fail.

6274892

Problem: cscal -v list does not work.

6275605

Problem: csstored.pl not reporting warnings when there are more than two log files in the live calendar database.

6276294

Problem: Secure login parameter does not work.

Fix:Not implemented: Removed service.http.ssl.securelogin parameter from ics.conf file.

6277086

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

Fix: New parameter added to WCAP command, login.wcap. The parameter is applyauthfilter. This parameter is described in the WCAP Reference.

6277250

Problem: For Linux, Calendar Server will not start after upgrade. Wrong permissions on lib directory after upgrading with a patch.

Workaround: As root, issue the following commands:

  1. cd /opt/sun/calendar/lib

  2. mkdir lock

  3. chown -R icsuser:icsgroup lock

6278096

Problem: Email alarms are turned off when a user first adds comments to an invitation and then responds to it.

6278698

Problem: Incorrect copyright year on Calendar Express login page.

6279920

Problem: Program termination when attempt to display week view with “exclude sat & sun” setting.

6281536

Problem: Pre-patch script uses a method for checking required patches that does not work in Alternate Root.

6282727

Problem: Need ability to add X-Tokens to calprops. This is needed to support non-default calendars in the Connector for Microsoft Outlook.

6284100

Problem: RRULES being exported for individual instances, resulting in duplicate events.

6285029

Problem:Free in cshttpd caused program termination.

6286321

Problem: Pre-patch check looking for obsolete patch.

Known Issues and Limitations

This section contains tables that list of the more important known issues at the time of the Calendar Server 6 release:

Limitations

The following limitation is known at this time:

Removing all Instances of Multi-Valued User Preferences

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

Workaround: 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.

Finding Installed Patches in a Clustered Environment

Limitation: There is no cluster specific showrev command that will show what is installed on the individual nodes of the cluster. (This is a generic problem, not just Calendar Server specific. You would run into the same difficulty with any product installed on a global file system.)

This is a problem when you want to update Calendar Server. You need to apply the patch to every node where Calendar Server was already installed. In addition you can’t apply the patch to a node if Calendar Server hasn’t already been installed on it. If you don’t know which nodes have Calendar Server installed and which do not, at the least, it will be confusing and cost you time trying to discover where Calendar Server is installed.

Workaround: Run the following command to see all of the nodes where Calendar Server is installed: pkgparam -v SUNWics5 | grep ACTIVE_PATCH

Pop-up Blockers

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

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

Exception: 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

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

Workaround: Enable the user using ldapmodify.

Multiple Domains (Hosted Domains)

Limitation: The configuration program, csconfigurator.sh, configures only a single domain.

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

  1. Enable hosted domains.

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

See Chapter 11, Setting Up Hosted Domains, in Sun Java System Calendar Server 6 2005Q4 Administration Guide and Chapter 13, Administering Hosted Domains, in Sun Java System Calendar Server 6 2005Q4 Administration Guide in the Sun Java System Calendar Server6 2005Q4 Administration Guide.

Calendar Server Does Not Expire LDAP Cache Data

Limitation: (Also bug number 4777792) Cache can fill up, causing errors. Calendar Server does not expire the LDAP cache data.

Workaround: Periodically remove contents of file. Then restart Calendar Server.

Must Enter Both Fully Qualified and Non-fully Qualified Hostnames in Configuration File

Limitation: The configuration file asks for the hostname twice. Once fully qualified and the second time not fully qualified. For example:

caldb.dwp.server.skate.red.sesta.com.ip = "skate.red.sesta.com" 
caldb.dwp.server.skate.ip = "skate" 
caldb.dwp.server.test12.red.sesta.com.ip = "test12.red.sesta.com" 
caldb.dwp.server.test12.ip = "test12"

Non-RFC Compliant Data in X-Tokens Must be Quoted

Limitation: If there is non-RFC compliant data in an X-Token, it must be quoted. For example, a colon in an X-Token must appear as ":".

Reported Problems

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

4526772

Problem: The Calendar Server utility cscal does not validate users before adding them to the owners list as secondary owners.

4754661

Problem: The Calendar Server migration utility csmig does not update icsSubscribed with the owners calendars.

4777792

Problem: Lack of ability to automatically purge obsolete cached LDAP data.

Workaround: Manually remove old cached LDAP data.

4932211

Problem: enpd crashes when opening and closing connections rapidly and concurrently.

4958242

Problem: 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.

5019977

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

5027772

Problem: Configuration program “Get” does not get baseDN . It fetches the install root. You must specify the base DN by adding the part that comes after the root.

5060833

Problem: 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.

Workaround: 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.

6179278

Problem: Hot backup log files not purged according to configuration settings.

Workaround: To prevent disk full service interruptions, periodically copy the log files to another location and start a new log file.

6186298

Problem: 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.

6203605, 6245878, 6246230

Problem:Administrators can't delete a domain from LDAP. commadmin domain purge does not remove entries with deleted as their icsStatus. They must have removed as the status. The recommended Calendar Server utility, csclean, does not change the icsStatus to removed .

Workaround:Use ldapmodify to change icsStatus to removed before running commadmin domain purge.

6216869

Problem: 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.

6216877

Problem: 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.

6219126

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

6221009

Problem: Linux: On RedHat Linux 3.0 email notification is received with subject missing.

6221452

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

6221999

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

6244958

Problem: When csconfigurator.sh is called with the -saveState option and the state file specified doesn't include a path the state file is not created. For example: /opt/sun/calendar/sbin/csconfigurator.sh -saveState cs.state

Workaround: Always specify the full path name, where the state file should be created.

6273182

Problem: Using csclean to delete users in non-hosted domain mode fails to remove users from LDAP.

Workaround: In non-hosted domain mode, use csuser delete to delete users from LDAP.

6277008

Problem: On Linux systems, if Calendar Server is shut down incorrectly, can't restart Calendar Server after reboot.

Workaround: Delete the lock files from /opt/sun/calendar/lib/lock/__db.001.

6283756

Problem: For event notifications, long To: fields are sent as one long line without wrapping. This violates RFC 821. If the line contains over 1000 characters (SMTP line length limit is 1000 characters), Messaging Server truncates the line.

Workaround: Use wrapsmtp keyword for the relevant channel in Messaging Server.

6300906

Problem: Calendar Server process cshttpd crashes if logging into Calendar Express when service.http.calendarhostname is set. The default is null ("").

6308379

Problem: Calendar Server won't work in an HA environment with Sun Cluster on Solaris 10 without patch 120500.

Fix: Apply patch 120500.

6312605

Problem:Problem with recurring events. Sending in dtstart and dtend parameters with non-date-field modifications (using storeevents) causes data corruption.

6312869

Problem:If you upgrade Delegated Administrator from the Java Enterprise System 2005Q1 version to the Java Enterprise System 2005Q4 version, the Delegated Administrator configuration program ( config-commda) freezes.

Fix: There is a new patch available for Delegated Administrator. Do not use the one in the general release version of Java Enterprise System 2005Q4.

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 plugin API, known as CSAPI. The API is described in the Sun Java System Calendar Server 6 2005Q4 Developer’s Guide at:

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

In the following files, cal_svr_base is the directory into which Calendar Server was installed. The default for Solaris is /opt/SUNWics5/cal , for Linux it 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.so

libicsexp10.so

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

nsCom.h

nsMacRepository.h

csIAccessControl.h

nsDebug.h

nsProxyEvent.h

csIAuthentication.h

nsError.h

nsRepository.h

csICalendarDatabase.h

nsHashtable.h

nsString.h

csICalendarLookup.h

nsIAtom.h

nsTraceRefcnt.h

csICalendarServer.h

nsICaseConversion.h

nsVector.h

csIDBTranslator.h

nsICollection.h

nsUnicharUtilCIID.h

csIDataTranslator.h

nsID.h

nsXPComCIID.h

csIMalloc.hplugins

nsIEnumerator.h

nsXPComFactory.h

csIPlugin.h

nsIEventQueueService.h

nscore.h

csIQualifiedCalidLookup.h

nsIFactory.h

pasdisp.h

csIUserAttributes.h

nsIPtr.h

publisher.h

mozIClassRegistry.h

nsIServiceManager.h

subscriber.h

mozIRegistry.h

nsIServiceProvider.h

xcDll.h

nsAgg.h

nsISizeOfHandler.h

xcDllStore.h

nsCOMPtr.h

nsISupports.h

 

nsCRT.h

nsISupportsArray.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.h

csUserAttributesDBFactory.cpp