Sun Java Communications Suite 5 Release Notes

Calendar Server Installation Notes

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

Caution –

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

Calendar Server 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. For a list of required patches, see the Sun Java Enterprise System 5 Release Notes for UNIX.

Required Privileges

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

Linux Package Names

Install Calendar Server 6.3 using the Sun Java Enterprise System installer. The Java Enterprise System installer installs the Sun component product packages, including Calendar Server 6.3, 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

You can't upgrade to Calendar Server version 6.3 using the Sun Java System Communications Suite installer. You must use the patchadd process.

For more information about upgrading Calendar Server 6.3, see Sun Java Communications Suite 5 Upgrade Guide.

Upgrading Your Calendar Database

After you have upgraded to Calendar Server 6.3, 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.

This section contains the following topics:

Upgrading from an Earlier Version of Calendar Server

If the version of your previous Calendar Server software predates version 5.1.1, first call technical support 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 technical support, you will be 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.

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.

csmig

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

csvdmig

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

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.

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.

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.

Calendar Server Postinstallation Configuration

After installing or upgrading to Calendar Server 6.3 and before you can use Calendar Server, you must configure it as follows:

Run the Directory Server Setup Script (comm_dssetup.pl) to configure Sun Java System Directory Server for Calendar Server schema. For instructions, refer to Chapter 8, Directory Preparation Tool (comm_dssetup.pl), in Sun Java Communications Suite 5 Installation Guide.
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.3 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`
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. The default location is: `/etc/opt/SunWics5/config`	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.
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/data/ http`	`/opt/sun/calendar/data/http`
Counter statistics files: `counter` and `counter.dbstat`	`/opt/SUNWics5/cal/lib/ counter`	`/opt/sun/calendar/lib/ counter`
`timezones.ics` file	`/opt/SUNWics5/cal/config`	`/opt/sun/calendar/config`

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:

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:

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 Search dialog.
Run indexing for icsCalendarOwned.
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 Search dialog.
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:

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.

Communications Express Using Schema 1

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:
```
dn: o=internet
 objectClass: organization
 o: internet
 description: Root level node in the Domain Component (DC) tree
```
The calendar 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.

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 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.3 Administration Guide.

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.