Sun Java System Communications Services 2005Q4 Release Notes

Installation Notes

This section contains information you should know before you install Calendar Server 6 2005Q4, 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.

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:

Migrates Calendar Server 5.x data to Calendar Server 6
Updates the calendar database from Berkeley DB version 2.6 to version 4.2
Writes the migration status to a log named csmigrate.log
Writes errors to a log named csmigrateerror.log

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 –

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:

Run the Directory Server Setup Script (comm_dssetup.pl) to configure Sun Java System Directory Server for Calendar Server schema.
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:

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.
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 Express Subscribe \> 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.

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 –

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.