Calendar Server 6.3 Release Notes

h1. Sun Java System Calendar Server 6.3 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Calendar Server 6.3 including:
{toc:minLevel=2|maxLevel=2}

h2. About Calendar Server 6.3

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.

Calendar Server offers two graphical user interfaces, Convergence 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.

h2. What's New in This Release of Calendar Server

For details, see the [What's New document|Communications Suite 6 Update 1 What's New#WhatsNewCalSvr].

h2. Deprecated and Removed Features for Calendar Server 6.3

For Sun Java System Calendar Server 6.3, the following features have been deprecated:
* The Calendar Express graphical user interface (GUI) has been deprecated and will be removed from the distribution in the the next major feature release.
* The WCAP {{attachments}} parameter, used by both {{storeevents}} and {{storetodo}}, has been deprecated. For backward compatibility, this parameter is still honored. But in a future release this parameter will no longer be recognized. Change any scripts you have using this parameter.
* The {{cstool}} utility that you use for monitoring Calendar Server activity has been removed in the Calendar Server 6.3 release.
* Calendar Server software is no longer available for Windows and HP-UX platforms.

h2. Requirements for Calendar Server 6.3

See [Requirements for Communications Suite 6|Communications Suite 6 Update 1 Component Products Release Notes].

h2. {anchor:patches}Important Upgrade Patch Information for Calendar Server 6.3

The Calendar Server 6.3 in Communications Suite 6 Update 1 is the equivalent of the following patches:

*Table 3-1 Calendar Server 6.3 Upgrade Patches (for Communications Suite 6 Update 1)*
|| Platform || Patch Number (English and Localized Languages) ||
| Solaris OS, SPARC | 121657-32|
| x86 |121658-32|
| Linux |121659-32|

The most recent Calendar Server patch version can be found on: [CommSuite:Communications Suite Component Patches].

You can get the most current product patches at Sun Solve. For how to get patches from Sun Solve, use the following procedure:

*How to Get Patches on SunSolve*
# For the current list of required patches for Sun Java System Calendar Server, go to:
[http://sunsolve.sun.com]
# Select either "Patches" or "Patch Portal".
# 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.

h2. Calendar Server Installation Notes

This section contains information you should know before you install Calendar Server 6.3. This section contains the following subsections:

{toc-zone:minLevel=3|maxLevel=3|location=top|type=list}

{note:title=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.
{note}

h3. Default Calendar Server Installation Directories on Solaris and Linux Platforms

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

*Table 3-2 Default Calendar Server Installation Directories*

||Solaris Default Directories||
|{{_cal-svr-base_=/opt/sun/comms/calendar/}} |
|{{/etc/_cal-svr-base_/SUNWics5/config}}|
|{{/var/_cal-svr-base_/SUNWics5}}|

||Linux Default Directories||
|{{_cal-svr-base_=/opt/sun/comms/calendar/}} |
|{{/etc/_cal-svr-base_/config}}|
|{{/var/_cal-svr-base_/}}|


{tip:title=Tip}
In the documentation, the default installation directory for Calendar Server is referred to as {{_cal-svr-base_}}.
{tip}

h3. OS Patches

You must apply the required operating system patches before installing Calendar Server. The Communications Suite installer checks for required platform patches. You must install all required patches or the installation process does not continue.

h3. Required Privileges

To run the Communications Suite 6 installer or the Calendar Server 6.3 configuration program on a Solaris OS system, log in as or become the superuser ({{root}}).

h3. Upgrading From an Earlier Version of Calendar Server 6

Upgrade to the latest Calendar Server 6.3 patch by using {{patchadd}} process.

For more information about upgrading to Calendar Server 6.3 from previous Calendar Server versions, see [_Sun Java Communications Suite 5 Upgrade Guide_|http://docs.sun.com/app/docs/doc/819-7561].

h3. Upgrading Your Calendar Database

If you are upgrading from a Calendar Server version prior to 6.3 to the current 6.3 version, you must upgrade your databases also, using various database tools named in this section. More information about the migration tools can be found in the [_Sun Java System Calendar Server 6.3 Administration Guide_|http://docs.sun.com/app/docs/doc/819-4654].

h4. Upgrading from an Earlier Version of Calendar Server

If the version of your previous Calendar Server software predates version 5.1.1, first call Sun Support Services for assistance in migrating your databases to be Calendar Server 5.1.1 compatible. You can not migrate directly to any of the Calendar Server version 6 releases. In the process recommended by Sun Support Services, you are required to install Calendar Server 5.1.1. After your database files are Calendar Server 5.1.1 compatible, install Calendar Server 6.3 and run the following database tools in the order listed.

h5. cs5migrate

Run this utility to upgrade your databases from version 5.1.1 to version 6.2 level. This is an intermediate step that is required before you run the {{csmigrate}} utility to bring it up to version 6.3 level. The {{cs5migrate}} utility can be found in the {{sbin}} directory after you install Calendar Server 6.3.

You must specify the {{-r}} option. The cs5migrate utility then creates master and exception records for all recurring events and tasks. Going forward these records will be automatically generated by Calendar Server.

This utility performs the following changes to your databases:

* Migrates your Calendar Server 5.1.1 LDAP database to be Calendar Server 6.2 compatible
* Migrates your Berkeley Data Base to version 4.2
* Writes the migration status to {{csmigrate.log}} log file
* Writes errors to {{csmigrateerror.log}} log file

h5. csmig

Run this utility so the LDAP CLD plug-in works properly.

h5. csvdmig

Run this utility to convert your non-domain calendar databases to single domain databases compatible with a multiple domain environment.

h5. csmigrate

Now that your Calendar Server Databases are in version 6.2 mode, run the {{csmigrate}} utility to migrate your Calendar Server 6.2 databases to be compatible with Calendar Server version 6.3.

You can find the {{csmigrate}} utility, along with other administrative tools, in the {{sbin}} directory of your newly installed Calendar Server 6.3 software. For more information on {{csmigrate}}, see [_Sun Java System Calendar Server 6.3 Administration Guide_|http://docs.sun.com/app/docs/doc/819-4654].

{note:title=Caution}
If you are upgrading from a much older version of Calendar Server that was 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.*
{note}

h4. Upgrading Your Calendar Server Version 6.0, 6.1, or 6.2 Databases to be Calendar Server Version 6.3 Compatible

Run {{csmigrate}} to upgrade your calendar databases to version 6.3 level.

You can find the {{csmigrate}} utility, along with other administrative tools, in the {{sbin}} directory of your newly installed Calendar Server 6.3 software. For more information on {{csmigrate}}, see [_Sun Java System Calendar Server 6.3 Administration Guide_|http://docs.sun.com/app/docs/doc/819-4654].

{note:title=Caution}
If you already have a Calendar Server 6.3 installation and you just upgraded to the latest patch, no migration utilities need to be run.
{note}

h3. Upgrading to Calendar Server 6.3 Patch 121658-20 or Later on Solaris x86 Platforms

*Data created in the Solaris x86 version of Calendar Server 6.3 patch 121658-19 or earlier is corrupted when you upgrade to patch 121658-20 or later. This issue occurs on Solaris x86 platforms only (CR 6642958).*

With patch 121658-20 and later, Calendar Server uses the new Berkeley Database library, which is incompatible with the database created by earlier versions. In order to use the database created by patch 121658-19 (or prior) with this patch, you must update the database.

Follow this procedure:

{anchor:CSprocedure}
# Make sure the Calendar Server installation is patch 121658-19 or prior.
# Important: Take a copy of the current database.
# Check to make sure the database is in good condition by running {{db_verify}} and {{csdb check}}.
# Dump the data using {{db_dump}}.
a. Set {{LD_LIBRARY_PATH}} to {{_cal-svr-base_/SUNWics5/cal/lib}}.
For example: {{./db_dump -r -f /var/opt/SUNWics5/dump/ics50alarms.db.txt /var/opt/SUNWics5/csdb/ics50alarms.db}}
b. Do the same for all the databases.
This dumps the {{ics50alarms.db}} to {{ics50alarms.db.txt}} (text file) and is placed in the "dump" directory.
# Apply this patch (121658-24 or later).
# Load the data dumped in the preceding step to the database files using the {{cs_dbload}} utility provided in this patch.
a. Set {{LD_LIBRARY_PATH}} to {{_cal-svr-base_/SUNWics5/cal/lib}}.
b. Run {{cs_dbload}} to load files dumped in step *4*.
For example: {{./cs_dbload -f /var/opt/SUNWics5/dump/ics50alarms.db.txt /var/opt/SUNWics5/dbload/ics50alarms.db}}
c. Do the same for all the databases.
This loads the records present in {{ics50alarms.db.txt}} to the {{ics50alarms.db}} in the "dbload" directory. A new "dbload" directory is chosen in order not to overwrite the original database.
# Run {{csdb check}} or {{csdb rebuild}} on the database files created in the preceding step.

h4. FAQ: Solaris x86 Upgrade to Calendar Server 6.3 Patch 121658-20 or Later.

*Question:* Is this a problem only for Solaris x86?
*Answer:* Yes, this is problem only for Solaris x86. SPARC and Linux platforms are not affected.

*Question:* Do you have to perform this task for every patch? Or only one time?
*Answer:* This is a one-time only task. Once you convert the database to work with this patch, you do not have to repeat these steps for future patches. You can just perform a {{patchadd}}.

*Question:* If I have patch -17 or -18, what should I do?
*Answer:* Follow the [previous procedure|#CSprocedure].

*Question:* If I have patch -21, -22, or -23, and I have not previously done a dump/load, what should I do?
*Answer:* We don't expect Calendar Server to run without crashes on these patch levels if the dump/load procedure is not performed. If you have these patches installed and do not see any issue, then please contact technical support on how to move forward with the patches.

*Question:* If I have already applied patch -24, and I've already done a dump/load, and I want patch -25 or the Communications Suite 6 software, what should I do?
*Answer:* Perform a {{patchadd}} of patch -25. No additional steps are required.

*Question:* If I have Communications Suite 5 (Calendar Server 6.3) and I want to be a Beta customer, what should I do?
*Answer:* If you want to move data from your existing database to the new database, you will have to perform the dump/load procedure described in patch -24.

h3. Calendar Server Postinstallation Configuration

After installing or upgrading to Calendar Server 6.3 and before you can use Calendar Server, you must configure it according to the instructions in [Calendar Server 6.3 Initial Configuration].

h3. Automatic Base 64 Encoding of Passwords
In the past, the Calendar Server configuration file stored some passwords in clear text. Though the {{ics.conf}} file has read permission restrictions, the passwords could be visible to someone else when the administrator edits the configuration file. In Calendar Server 6.3, the passwords have been moved to another file and obfuscated by base 64 encoding them. The base 64 encoding prevents someone from accidentally seeing the passwords. You must still protect the file with read permission restrictions, and keep the file secure so that no unauthorized user can get to it, to keep the passwords secure.

If you are installing Calendar Server for the first time, the configuration program encodes the passwords that you create during the configuration process, and stores them in a separate password configuration file.

If you are upgrading your existing Calendar Server software to the Calendar Server 6.3 version, the configuration program encodes the existing passwords found in the {{ics.conf}} file, and moves them to the password configuration file.

In both cases, the configuration program also adds a new {{ics.conf}} parameter to indicate the location of the password file, as shown in the following example:

{{local.passwordfile="/etc/opt/SUNWics5/config/icspassword.conf"}}

Do not change this configuration parameter.

Due to this change, the following configuration parameters have been moved out of the {{ics.conf}} file:
* {{local.authldapbindcred}}
* {{local.enduseradmincred}}
* {{local.lookupldapbindcred}}
* {{service.siteadmin.cred}}

{info:title=Note}
The LDAP bind passwords that are generated by the configurator are re-generated each time you run the configurator, once they are moved out of the {{ics.conf}} file.
{info}

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

*Table 3-4 Location of Calendar Server Files*
||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}}|{{_cal-svr-base_/SUNWics5/cal/lsbin}}|{{_cal-svr-base_/sbin}}
|Migration utilities: {{csmig}} and {{csvdmig}}|{{_cal-svr-base_/SUNWics5/cal/sbin}}|{{_cal-svr-base_/sbin}}
|Configuration files: {{ics.conf, version.conf, counter.conf,}} and {{sslpassword.conf}}|After installation, files are located at: {{_cal-svr-base_/SUNWics5/cal/lib/_config-template_}}\\ \\During configuration, the various files from the above directory are moved to the locations specified by the configuration options you choose. The default location is: {{/etc/_cal-svr-base_/SUNWics5/config}}|After installation, the files are located at: {{_cal-svr-base_/lib/_config-template_}}\\ \\During configuration, the various files from the above directory are moved to the locations specified by the configuration options you choose. The default location is: {{/etc/_cal-svr-base_/config}}
|Mail formatting ({{*.fmt}}) files|After installation, the files are located at: {{_cal-svr-base_/SUNWics5/cal/lib/_config-template_}}\\ \\After configuration, the files are located at: {{/etc/_cal-svr-base_/SUNWics5/config/_language_}}\\ \\where _language_ is en, de, es, fr, ja, ko, zh-TW, or zh-CN.|After installation, the files are located at {{_cal-svr-base_/lib/_config-template_}}\\ \\After configuration, the files are located at: {{/etc/_cal-svr-base_/config/_language_}}\\ \\where language is en, de, es, fr, ja, ko, zh-TW, or zh-CN.
|Library ({{.so}}) files\\ \\SSL utilities: {{certutil}} and {{modutil}}|{{/var/_cal-svr-base_/SUNWics5/cal/lib/}}|{{_cal-svr-base_/lib}}
|Session database|{{/var/_cal-svr-base_/SUNWics5/data/http}}|{{/var/_cal-svr-base_/data/http}}
|Counter statistics files: {{counter}} and {{counter.dbstat}}|{{_cal-svr-base_/SUNWics5/cal/lib/counter}}|{{_cal-svr-base_/lib/counter}}
|{{timezones.ics}} file|{{/etc/_cal-svr-base_/SUNWics5/config}}|{{/etc/_cal-svr-base_/config}}

h3. Tuning Directory Server Performance for Calendar Server

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

{toc-zone:minLevel=4|maxLevel=4|location=top|type=list}

h4. 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:title=Tip}
To see the performance difference indexing can give you, perform the following test:

# Before indexing, time how long it takes to run the following LDAP command:
{code:xml}
ldapsearch -b "base" "(&(icscalendarowned=*
user*)(objectclass=icsCalendarUser))"{code}\\
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 Search dialog.
# Run indexing for icsCalendarOwned.
# Again run the following LDAP command, and time it:
{code:xml}ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"{code}\\
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 Search dialog.
# Compare the times. There should be a measurable time difference.
{tip}

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

{code:xml}ldapsearch -b "base" "(&(icscalendarowned=*
user ID*)
(objectclass=icsCalendarUser))"
{code}

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:

* Ensure that the value for the nsslapd-sizelimit parameter in the slapd.conf or equivalent file is large enough to return all the desired results; otherwise, truncation can occur, and no results will be displayed.

* Ensure that the value for the nsslapd-lookthroughlimit parameter in the slapd.ldbm.conf or equivalent file is large enough to complete a search of all the users and resources in the LDAP directory. If possible set nsslapd-lookthroughlimit to -1, which causes no limit to be used.

{toc-zone}

h3. Using Schema 1 with Calendar Server and Communications Express

There are two issues with Schema 1 in Communications Express:

* If you are running Communications Express with Sun LDAP Schema 1, before running the Communications Express configuration program, you must add the DC root node to your LDAP using ldapmodify. The entry should look like this:

{noformat}
dn: o=internet
objectClass: organization
o: internet
description: Root level node in the Domain Component (DC) tree
{noformat}

* The Calendar Server utility used to provision users in Schema 1, {{csuser}}, was designed for Calendar Express and does not enable a user for Address Book service as is needed for Communications Express.

h3. Calendar Server 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 Delegated Administrator 6.4 Administration Guide|http://docs.sun.com/app/docs/doc/819-4438]. 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.3 Administration Guide_|http://docs.sun.com/app/docs/doc/819-4654].

{note:title=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 will negatively impact your deployment.
{note}


h2. Calendar Server Documentation Updates

h6. Restoring Backups

As of Calendar Server 6.0, you can restore a specific calendar using {{csrestore}} from any backup including backups saved with Hot Backup or Archival Backup. To do so, issue the following command:

{code}
csrestore -c <usercal> calendar <backupdir>

The Sun StorEdge Enterprise Backup software (formerly Solstice Backup) and Legato Networker ({{legbackup.sh}} and {{legrestore.sh}}) are no longer distributed with Calendar Server 6.3. The [_Sun Java System Calendar Server 6.3 Administration Guide_|http://docs.sun.com/app/docs/doc/819-4654] still documents these utilities in section "17.3 Using Sun StorEdge Enterprise Backup or Legato Networker," in "Chapter 17: Backing Up and Restoring Calendar Server Data." Ignore this information, as it is out of date.

h2. Calendar Server Compatibility Issues

The following table lists the known incompatibilities between Calendar Server 6.3 and earlier versions.

*Table 3-5 Calendar Server Incompatibilities*
||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\\
\\Existing scripts that specify the old path need to be updated.|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 previous version of Calendar Server.|If you upgrade Communications Express, you must also upgrade Calendar Server.|This also applies to Messaging Server.|
|Due to a change in the way packaging is done, Calendar Express must do string substitution at runtime.|Significant Performance Degradation|Call technical support to receive a script you can run before starting Calendar Server operations. The script performs all the required string substitutions.\\
\\Calendar Express is deprecated and will not be included in a future release of Calendar Server. This problem will not be fixed.|
|Due to a program code change in SSL processing, the following parameter no longer works:\\
\\ {{service.http.ssl.certdb.path}}|Scripts and configuration files still using the old parameter to point to the SSL directory will not work. SSL is not enabled.|A new parameter was added to the {{ics.conf}} file:\\
\\ {{local.ssldbpath = "/etc/opt/SUNWics5/config"}}|
|Password to certificate database is no longer held in {{ics.conf}} parameter:\\
\\ {{service.http.ssl. certdb.password}}|SSL password can't be found. Error message:\\
\\ {{General Error: http_ssl_init(): SSL initialization failed.}}|Password to certificate database is now found in the following file located in the {{config}} directory:\\
\\ {{sslpassword.conf}}\\
\\Format of password is:\\
\\Internal (Software) Token:_password_|
|Non-domain environments no longer allowed.|Scripts that modify LDAP entries must now include a default domain. |When Calendar Server is installed and configured, it runs a silent conversion program on all LDAP entries to add the default domain you specified.\\
\\Requests that come in (WCAP commands) without the domain will be automatically assumed to be for the default domain.\\
\\But any scripts you run that directly modify LDAP entries must include the new default domain.|
|The {{service.admin.calmaster.userid}} and {{service.admin.calmaster.cred}} parameters in the {{ics.conf}} file are not used anymore.|You cannot set the Calendar user preferences and credentials using these old parameters.|The {{service.admin.calmaster.userid}} parameter is changed to {{service.siteadmin.userid}} and {{service.admin.calmaster.cred}} parameter is changed to {{service.siteadmin.cred}}. In case of an upgrade these parameters are migrated by the patch scripts.|
|Windows and HP-UX versions of Calendar Server are no longer available.|The only operating system platforms supported by server-side Calendar Server software are Solaris and Linux.|This does not effect client-side software, such as the Connector for Microsoft Outlook. See the individual client component Release Notes for a list of supported operating systems.|

h2. {anchor:ACECP} Problems Fixed in This Release of Calendar Server

The list that follows are problems reported fixed for this patch of Calendar Server 6.3:

h4. *6697835*
*A "freebusy" failure should not cause http error to be returned for XML/JSON output*
Calendar Server returns http error 404 when doing a "freebusy" lookup on a non-existing calendar.

h4. *6683707*
*{{get_freebusy.wcap}} crashes {{cshttpd}}*

h4. *6681812*
*{{csdb rebuild}} should not change the modified timestamp*

h4. *6680028*
*cshttpd crashes when a "freebusy" lookup is done on ldapgroup*

h4. *6677838*
*Unauthorized WCAP request should return response with http code 401-Unauthorized for JSON payload*

h4. *6676306*
*Time zone names are wrong for daylight times in Australia*

h4. *6674186*
*Implement handling of SMS reminders*

h4. *6673980*
*Calendar Server fails to stay running in Sun Cluster HA when configured in read-only mode*

h4. *6662778*
*Event Accepted Notification emails are not sent if multiple calendar ID's are invited*

h4. *6662417*
*Integration of localization files into core patch for Communications Suite 5 and 6*

h4. *6659624*
*JSON syntax error returned when "freebusylist" is empty in {{getfreebusy.wcap}}*

h4. *6657860*
*JSON format error returned in {{get_freebusy.wcap}}*

h4. *6657246*
*There is a memory leak for every login if the authentication filter is configured*

h4. *6657242*
*There is a memory leak when fetching a multivalued attribute from ldap*

h4. *6656154*
*Calendar Server needs to implement the Communications Suite Installer upgrade interfaces*

h4. *6651348*
*SMF needs to have unique names for Messaging Server and Calendar Server watcher services*

h4. *6650915*
*Can't start Calendar Server using SMF*

h4. *6650391*
*SMF: watcher fails to start (path to binaries is incorrect in {{calexe}})*

h4. *6650270*
*SMF : {{watcher.xml}} references Messaging Server*

h4. *6649304*
*Passwords are put back (twice in the {{ics.conf}} with empty value after using removing the latest cs631 patch*

h4. *6649300*
*{{patchadd}} produces error "cannot access {{/opt/SUNWics5/cal/lib/com.sun.cmm.cs.xml.new}}*

h4. *6649297*
*Linux only: Old password related fields left in {{ics.conf}}*

h4. *6646891*
*Calendar Express cannot modify time format if {{service.http.numprocesses}} is greater than 1*

h4. *6642958*
*Bad data representation with patch 121658-19 for the x86 version of Calendar Server 6.3*

h4. *6642312*
*The {{csversion}} utility is missing on Linux*

h4. *6642081*
*Anonymous login to calendar is not working*

h4. *6731764*
*Anonymous access occurs when login screen should appear (when login timeout occurs or URL with old session is used)*

h4. *6641750*
*{{fetchattachment.wcap}} returns incorrect mime output*

h4. *6640527*
*{{csadmind}} crashes when accessing an attachment with an encoded file size that is an exact multiple of the page size*

h4. *6640009*
*There is no SMF support in the Calendar Server build*

h4. *6635743*
*Configuring CS fails with a java exception error*

h4. *6629318*
*{{cspassword}} reveals passwords to all*

h4. *6626685*
*There is a memory leak every time an attachment is fetched*

h4. *6626674*
*There is a {{cshttpd}} memory leak under stress*

h4. *6626006*
*{{csdb rebuild}} and {{csrestore}} from backup fails due to {{sbin}} directory ownership issue*

h4. *6625765*
*Calendar Server import process causes attachments to be truncated*

h4. *6624889*
Calendar Server encoding session id makes Outlook Connector unstable*

h4. *6624747*
*{{cshttp}} thread lock issue in {{ASock_Recv}}*

h4. *6623038*
*Build failure with Sun Studio 12*

h4. *6622866*
*{{PROPFIND}} causes a denial of service of the Calendar Server*

h4. *6622081*
*{{csexport}} should have the ability to export events including the attachment data*

h4. *6622015*
*{{get_calprops.wcap}} not sending the correct response if {{calid}} parameter is of a calendar group*

h4. *6621290*
*JSON syntax error: {{storeevents.wcap} with {{alarmpop}}*

h4. *6621234*
*JSON syntax error: {{list_subscribed.wcap}}*

h4. *6621213*
*JSON syntax error: {{list.wcap}}*

h4. *6621128*
*JSON syntax error: {{get_freebusy.wcap}}*

h4. *6620937*
*Calendar Server is returning incorrect ICAL output when an event contains an attachment*

h4. *6620263* *
*{{cscomponent}} command is missing for the Communications Suite 5 Linux installation*

h4. *6620139*
*JSON syntax error: {{set_userprefs.wcap}}*

h4. *6620122*
*JSON syntax error: {{get_userprefs.wcap}}*

h4. *6620046*
*JSON syntax error: {{search_calprops.wcap}}*

h4. *6619357*
*{{cshttpd{{ crashes with memory corruption*

h4. *6618932*
*{{patchadd}} error message*

h4. *6618247*
*{{patchrm}} error message*

h4. *6618196*
*JSON syntax error: {{storeevents.wcap}} with timezone ID*

h4. *6617799*
*JSON syntax error: {{get_all_timezones.wcap}}*

h4. *6617787*
*JSON syntax error: {{deletecomponents_by_range.wcap}}*

h4. *6617784*
*JSON syntax error: {{deletetodos_by_range.wcap}}*

h4. *6617782*
*JSON: {{deletetodos_by_id.wcap}} syntax error*

h4. *6616433*
*{{config-servicetags}} exits abnormally on Linux*

h4. *6615480*
*JSON output has syntax errors*

h4. *6615475*
*Calendar Server needs to locate correct product path when the Communications installer is used with {{altroot}}*

h4. *6615440*
*Calendar Server needs to create {{/var/opt/sun/install}} on Linux*

h4. *6612742*
*There is a {{cshttpd}} crash in {{print_event_detail}}*

h4. *6612651*
*{{nswcalCALID}} should be removed from Calendar Server 6.3 LDAP update code*

h4. *6611728*
*While creating an event if you invite a resource, it shows the RSVP status as "Accepted" if {{autoaccept}} is enabled*

h4. *6609386*
{{config-mfwk}} and {{config-servicetag}} scripts are needed for Uniformity in Documentation for Calendar Server and Messaging Server*

h4. *6607940*
*New calendar creation mail feature causes functional test failures*

h4. *6607478*
*{{com.sun.cmm.cs.xml}} has hard-coded values*

h4. *6605715*
*Update {{timezones.ics}} file with the Venezuela time zone change*

h4. *6604662*
*You cannot add more invitees to an event when another existing user is removed from LDAP*

h4. *6603427*
Calendar Server emits malformed XML if an event contains an attachment*

h4. *6602903*
*{{csrename}} causes a core dump while renaming the calendars*

h4. *6597809*
*Double-booking restrictions are ignored when importing an event*

h4. *6596706*
*The {{cshttpd}} process is crashes when you try to update the attachment information for a recurring series*

h4. *6596628*
*Implement {{getVersion}} for Calendar Server*

h4. *6592804*
The {{cshttpd}} process crashes in the DWP setup due to memory corruption when fetching the attachment*

h4. *6592448*
*A {{cshttpd}} crash occured in {{loginincorrect_negative}}*

h4. *6591407*
The {{cshttpd}} process crashes if the master copy of the recurring event is missing*

h4. *6590680*
{{cshttpd}} may crash in attachment-related functions for the events created with patch-17 in DWP setup*

h4. *6589856*
*{{cshttpd}} is crashing in {{shtml_command}} when {{browser.cache.enabled}} is set to "yes"*

h4. *6588744*
*Inviting resources to an event shows wrong RSVP status if {{autoaccept}} is enabled*

h4. *6588737*
*Calendar Server emits broken XML if the email field contains quotes*

h4. *6588557*
*Error 81 is returned when an attendee is removed from a single instance of a recurring event*

h4. *6585886*
*Recurring events are not shown in Outlook Connector after running {{csrename}}*

h4. *6583657*
*Change output from "error" to "debug" for {{caldb_pvt_ScanDeleteLog: Resurrected entry}}*

h4. *6580129*
*{{fetchcomponents_by_id.wcap}} could cause {{cshttpd}} to crash when it returns error 81*

h4. *6578849*
*Emit calendar data in JSON format*

h4. *6577773*
*Sun Java Enterprise System Monitoring Framework product identifying tag needs to be fixed*

h4. *6572538*
*There is no {{jmqclient}} bundled in Calendar Server 6.3.1 on Linux*

h4. *6571479*
*{{admind.log}} shows confusing log message for {{jmqInit}}*

h4. *6569278*
*Creating an event by inviting a resource calendar fails with "Unknown Error 80"*

h4. *6568622*
*{{httpd}} does not start with Message Queue 3.7 on Linux*

h4. *6567265*
*Make number of Berkeley database locks configurable*

h4. *6565532*
*{{csdwpd}} crashes if there are any errors while reading the calendar properties*

h4. *6564744*
*{{cshttpd}} crashes with {{fetchcomponents.wcap}} when run under {{libumem}}*

h4. *6563558*
*The {{cshttpd}} process memory grows very quickly if many events or to do's are fetched in a single request*

h4. *6563284*
*{{dbstore_is_archivebackup_enabled}} contains an incorrect return value*

h4. *6561930*
*Update {{timezones.ics}} file with the new DST changes in New Zealand*

h4. *6559166*
*{{hotbackup}} and {{archive}} should copy all {{*.db}} files*

h4. *6558709*
*The front-end system receives a "backup failed" error email even when {{archive}} and {{hotbackup}} are disabled.

h4. *6555671*
*The copyright for Calendar Express is still 2006*

h4. *6554012*
*{{httpd}} crash on {{freebusy}} query uses mail if redirect is on*

h4. *6548178*
*Alarm retry feature may result in thousands of event reminders*

h4. *6546804*
*The {{icsSubscribed}} attribute is not removed from LDAP by {{cscal}} when deleting a calendar created by Communications Express*

h4. *6546620*
*{{fetchattachment.wcap}} over DWP may return a corrupted file*

h4. *6546549*
*A memory leak occurs when an event with attachment is saved*

h4. *6546541*
*Uploaded files are not getting deleted after the attachment is saved*

*6546535*
*The {{cshttpd}} process crashes in {{ac_fetchattachment()}} if the event in the database does not have an {{attachid}}*

h4. *6546532*
*{{csimport}} crashes when you try to import an event with an attachment*

h4. *6545488*
*There is a crash in {{wcap_login}} on Linux*

h4. *6545035*
*{{attachid}} is missing in {{fetchcomponents_by_*.wcap}} in DWP setup*

h4. *6542989*
*{{csconfigurator.sh}} creates an invalid DWP configuration*

h4. *6541912*
*{{fetchcomponents}} returns a malformed WCAP response for calendar events having an LDAP group as an attendee*

h4. *6541320*
*The Calendar Express window title shows incorrect version 6 5*

h4. *6540503*
*Attachment store needs to open with a hash flag to maintain only a single copy for each back end*

h4. *6538972*
* Notification and reminder timings are off by an hour with the new DST dates*

h4. *6537923* \
*The copy file utility function fails silently with large files*

h4. *6537359*
*In Calendar Server 2005Q4, the {{timezones.ics}} file does not account for 2007 DST differences in Mexico*

h4. *6531658*
*{{csrename}} returns a segmentation fault and crashes in {{csadm_rename_in_ldap()}}*

h4. *6530207*
*{{csrestore}} is unable to restore a calendar from the backup database. It cannot connect to the watcher process.*

h4. *6525791*
*{{csrename}} stops abruptly without renaming the LDAP database*

h4. *6524804*
*Calendar creation begins to degrade as the number of calendars increases for a single user when using bulk load*

h4. *6522147*
*Users can log in with {{icsstatus=inactive}}*

h4. *6520001*
*Hide passwords*

h4. *6516438*
*You cannot login to Calendar Server after an upgrade. You will see "Backend Host Unresolvable" on the login page*

h4. *6509780*
*Follow new versioning policy*

h4. *6505280*
*Introduce daylight savings for Western Australia*

h4. *6500444*
*There is an HTTP Request Smuggling security issue in {{cshttpd}}

h4. *6498903* There is a {{cshttpd}} crash in {{caldb_pvt_ReadLinkedComponent()}}*

h4. *6498212*
*The configurator throws a java exception when you choose which server to use as a back end in DWP setup*

h4. *6497774*
*{{csmigrate}} should create the target directory with the owner {{icsuser:icsgroup}} if it is run by root*

h4. *6497116*
*The configurator window's title shows Sun Java System Calendar Server Version 6 5*

h4. *6496627*
*Changing the calendar event case in Calendar Express with no spaces added or removed fails the first time*

h4. *6496601*
*Deleting the secondary calendar does not remove it from the database*

h4. *6496586*
*When switching from December to January using the monthly view, Calendar Express displays January of current year*

h4. *6496353*
*There are memory leaks in {{cshttpd}}*

h4. *6494811*
*{{admind}} dumps core when JMQ is enabled*

h4. *6494557*
*There is a WCAP problem replacing X-properties on recurring components*

h4. *6494514*
*All-day events are shifted by one day after importing a {{*.ics}} file*

h4. *6489729*
*Calendar Server's HTTP server crashes while accepting invitations*

h4. *6486422*
*Calendar Express does not display all-day events in some views (Day/Overview)*

h4. *6480935*
*Recovery function for databases failed*

h4. *6479810*
*There are session database issues*

h4. *6475187*
*WCAP {{deleteevents_by_id}} returns non-published {{iErr -5010}}*

h4. *6475106*
*{{cshttpd}} uses too much memory*

h4. *6474557*
*Database handles remain open during environment close*

h4. *6472348*
*The {{csadmind}} process is spinning and using 100% CPU*

h4. *6461762*
*Change the absolute path to relative path in the post install script*

h4. *6456901*
*{{watcher.log}} date/time stamp diverge from the standard used in other log files*

h4. *6442769*
*Calendar Server should add the {{X-Sun-calendar-msg: _ITIP Method_}} in calendar notifications*

h4. *6442476*
*User calendars automatically created at login have auto-provisioning turned off resulting in calendars not being created on the server*

h4. *6422917*
*Notification of an event contains garbled multi-byte characters*

h4. *6407790*
*Use the output "This command is not valid for schema 2" message for {{csattribute}}, {{csuser}}, and {{csdomain}} with any option*

h4. *6406628*
*JMQ notifications are not triggered for advanced options*

h4. *6391858*
{{csstats}} is no longer reporting authentication, alarm, disk, or response statistics*

h4. *6378975*
*Online Help is not available for new panels in the Calendar Server configurator*

h4. *6331404*
*Exception invitations do not show up in Outlook using the connector*

h4. *6289810*
*By default, invitations should be "Accepted" for resource calendars*

h4. *6282134*
*Some strings need to be translated in event notifications in zh-CN and zh-TW versions of Communications Express*

h4. *6280808*
*The title of the tasks List in the Spanish version is corrupted.

h4. *6280710*
*Month names should begin with lower case letters in the Spanish version*

h4. *6279597*
*The text for introducing the time in the new-task dialog in the Spanish version is incorrect*

h4. *6279591*
The initials for the days in the Calendar Server web client are incorrect in the German, Spanish, and possibly the French versions*

h4. *6278714*
*There is an unnecessary tilde in the message warning about deletion of repeating tasks*

h4. *6278698*
*The copyright year 2003 on the Calendar Express login page is incorrect*

h4. *6275914*
*The Calendar Server configurator online help is out of sync with the Spanish GUI*

h4. *6236637*
*The version of the administration tools displays the wrong build date*

h4. *6214765*
*The string in the Spanish versio of the "Create Group" window is corrupted*

h4. *5109953*
*The {{createcalendar.wcap}} command writes errors to the directory server logs*

h4. *5069988*
*{{cscomponents -e _date_}} removes all tasks after the end date*

h4. *4924536*
*HTML is not rendered under the "Preview" tab of "Edit Event" dialog*



{anchor:CalSvrKnownIssues}
h2. {anchor:ACECQ} Known Issues and Limitations in Calendar Server

This section contains known issues at the time of this Calendar Server 6.3 release:

* [#Calendar Server Issues]
* [#Documentation Issues in Calendar Server]

h3. Calendar Server Issues

h4. Calendar Server Upgrade on x86 Platforms Using the Installer is Not Supported

Upgrading Calendar Server using Communications Suite 6 installer (specifically {{commpkg upgrade}}) is not supported on x86 platforms. Instead follow the manual steps to upgrade Calendar Server on x86 platforms.

h4. 6780694
*There are missing apostrophes in the French OLH*

h4. 6688858
*There are some issues when upgrading Calendar Server HA and SC_SCHA via the Communications Installer."
*Workaround:* After the upgrade, mount the config directory and run {{csconfigurator.sh -nodisplay -noconsole -novalidate}}.

h4. 6695856
*{{./csconfigurator}} fails to create the values from {{ics.conf}} to the {{cspassword}} file during upgrade from Calendar Server 6.2 to 6.3*

h4. 6568622
*{{httpd}} does not start when running Message Queue 3.7 on Linux*

h4. {anchor:6722736}Calendar Server Doesn't Start After Patchadd Because New Parameters Are Added to {{ics.conf}} With value {{UNKNOWN}} (CR 6722736)

At some sites, the calendar server might not start during a patch process. If this problem occurs, use the following procedure. This procedure needs to be performed only once.

1. Set the {{configutil}} parameters below to valid values in {{ics.conf}}. For example:

{{caldb.berkeleydb.archive.maxdays="6"}}
{{caldb.berkeleydb.archive.mindays="3"}}
{{caldb.berkeleydb.hotbackup.maxdays="6"}}
{{caldb.berkeleydb.hotbackup.mindays="3"}}

2. Run the following:

{{./csconfigurator.sh -noconsole -nodisplay -novalidate}}

Contact regular support channels if this procedure does not solve the problem.

h3. Documentation Issues in Calendar Server

h4. Incorrect Description of icsAllowedRights Values

This issue occurs in the _Sun Java System Calendar Server 6.3 Administration Guide_, in the following section: [D.9.3.1 icsAllowRights Attribute: csdomain Utility|http://docs.sun.com/app/docs/doc/819-4654/fuugb?l=en&a=view].

This section describes the {{icsAllowRights}} attribute and properties that you can set with the {{csdomain}} utility. The following statement is incorrect:

"If a bit corresponding to a specific right is set (value=1), the right is not allowed. If the bit is not set (value=0), the right is allowed."

The correct statement is as follows:

"If a bit corresponding to a specific right is set (value=1), the right is explicitly allowed. If the bit is not set (value=0), the right is determined by the corresponding {{ics.conf}} parameter value."

In addition, in Table D-15, {{icsAllowRights}} LDAP Directory Attribute and Properties, the values documented for the individual attribute bits are incorrect.

For example, this statement is incorrect: "{{allowCalendarCreation:}} If set (bit 0=1), do not allow calendars to be created."

This statement should read as follows: "{{allowCalendarCreation:}} If set (bit 0=1), allow calendars to be created."

h2. {anchor:ACECY} Redistributable Files for Calendar Server

Sun Java System Calendar Server 6.3 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&rsquo;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 2005Q4 Developer's Guide_|http://docs.sun.com/app/docs/doc/819-2434].\\
\\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 Redistributable Files|#ACECZ]
* [bin Redistributable Files|#ACEDA]
* [classes Redistributable Files|#ACEDB]
* [include Redistributable Files|#ACEDC]
* [plugins Redistributable Files|#ACEDD]
* [samples Redistributable Files|#ACEDI]

h3. {anchor:ACECZ} authsdk Redistributable Files
The following are the redistributable files in this subdirectory ( {{cal-svr-base/csapi/authsdk/}}):
{{cgiauth.c}}\\
{{expapi.h}}\\
{{login.html}}\\
{{nsapiauth.c}}


h3. {anchor:ACEDA} bin Redistributable Files
The following are the redistributable files in this subdirectory ( {{cal-svr-base/csapi/bin/}}):
{{libcsapi_xpcom10.so}}\\
{{libicsexp10.so}}


h3. {anchor:ACEDB} classes Redistributable Files
The following are the redistributable files in this subdirectory ( {{cal-svr-base/csapi/classes/}}):
{{ens.jar}}\\
{{jms.jar}}


h3. {anchor:ACEDC} include Redistributable Files
The following are the redistributable files in this subdirectory ( {{cal-svr-base/csapi/include/}}):
{{IIDS.h}}\\
{{csIAccessControl.h}}\\
{{csIAuthentication.h}}\\

{{csICalendarDatabase.h}}\\
{{csICalendarLookup.h}}\\
{{csICalendarServer.h}}\\
{{csIDBTranslator.h}}\\
{{csIDataTranslator.h}}\\
{{csIMalloc.hplugins}}\\
{{csIPlugin.h}}\\
{{csIQualifiedCalidLookup.h}}\\
{{csIUserAttributes.h}}\\
{{mozIClassRegistry.h}}\\
{{mozIRegistry.h}}\\
{{nsAgg.h}}\\
{{nsCOMPtr.h}}\\
{{nsCRT.h}}\\
{{nsCom.h}}\\
{{nsDebug.h}}\\
{{nsError.h}}\\
{{nsHashtable.h}}\\
{{nsIAtom.h}}\\
{{nsICaseConversion.h}}\\
{{nsICollection.h}}\\
{{nsID.h}}\\
{{nsIEnumerator.h}}\\
{{nsIEventQueueService.h}}\\
{{nsIFactory.h}}\\
{{nsIPtr.h}}\\
{{nsIServiceManager.h}}\\
{{nsIServiceProvider.h}}\\
{{nsISizeOfHandler.h}}\\
{{nsISupports.h}}\\
{{nsISupportsArray.h}}\\
{{nsMacRepository.h}}\\
{{nsProxyEvent.h}}\\
{{nsRepository.h}}\\
{{nsString.h}}\\
{{nsTraceRefcnt.h}}\\
{{nsVector.h}}\\
{{nsUnicharUtilCIID.h}}\\
{{nsXPComCIID.h}}\\
{{nsXPComFactory.h}}\\
{{nscore.h}}\\
{{pasdisp.h}}\\
{{publisher.h}}\\
{{subscriber.h}}\\
{{xcDll.h}}\\
{{xcDllStore.h}}


h3. {anchor:ACEDD} plugins Redistributable Files
This directory ({{cal-svr-base/csapi/plugins/}}) has redistributable files in the following subdirectories:
* [accesscontrol Redistributable Files|#ACEDE]
* [authentication Redistributable Files|#ACEDF]
* [datatranslator Redistributable Files|#ACEDG]
* [userattributes Redistributable Files|#ACEDH]

h4. {anchor:ACEDE} accesscontrol Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/plugins/accesscontrol/}} ):
{{csAccessControl.cpp}}\\
{{csAccessControl.h}}\\
{{csAccessControlFactory.cpp}}


h4. {anchor:ACEDF} authentication Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/plugins/authentication/}} ):
{{csAuthentication.cpp}}\\
{{csAuthentication.h}}\\
{{csAuthenticationFactory.cpp}}


h4. {anchor:ACEDG} datatranslator Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/plugins/datatranslator/}} ):
{{csDataTranslator.cpp}}\\
{{csDataTranslator.h}}\\
{{csDataTranslatorFactory.cpp}}


h4. {anchor:ACEDH} userattributes Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/plugins/userattributes/}} ):
{{csUserAttributes.cpp}}\\
{{csUserAttributes.h}}\\
{{csUserAttributesFactory.cpp}}


h3. {anchor:ACEDI} samples Redistributable Files
This directory ({{cal-svr-base/csapi/samples/}}) has redistributable files in the following subdirectories:
* [samples/authentication Redistributable Files|#ACEDJ]
* [samples/datatranslator Redistributable Files|#ACEDK]
* [samples/ens Redistributable Files|#ACEDL]
* [samples/userattributes Redistributable Files|#ACEDM]

h4. {anchor:ACEDJ} samples/authentication Redistributable Files
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}}


h4. {anchor:ACEDK} samples/datatranslator Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/samples/datatranslator/}} ):
{{csDataTranslatorCSV.cpp}}\\
{{csDataTranslatorCSV.h}}\\
{{csDataTranslatorCSVFactory.cpp}}


h4. {anchor:ACEDL} samples/ens Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/samples/ens/}}):
{{apub.c}}\\
{{asub.c}}\\
{{rpub.c}}\\
{{rsub.c}}


h4. {anchor:ACEDM} samples/userattributes Redistributable Files
The following redistributable files are found in this subdirectory ( {{cal-svr-base/csapi/samples/userattributes/}} ):
{{csUserAttributesDB.cpp}}\\
{{csUserAttributesDB.h}}\\
{{csUserAttributesDBFactory.cpp}}