Chapter 12 Calendar Server

This chapter describes how to upgrade Calendar Server from previous Java ES versions to Java ES Release 4: Calendar Server 6 2005Q4.

The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4. The chapter covers the following:



Note	File locations in this chapter are specified with respect to a directory path referred to as cal_svr_base. At least part of this path might have been specified as an installation directory when Calendar Server was initially installed. If not, the Java ES installer assigned a default value. The default value of cal_svr_base is C:\Sun\CalendarServer.

Overview of Calendar Server Upgrades

This section describes the following general aspects of Calendar Server that impact upgrading to Java ES Release 4:

About Java ES Release 4 Calendar Server

Java ES Release 4 Calendar Server mostly represents bug fixes. There is no major new functionality with respect to Release 3.

Calendar Server Upgrade Roadmap

Table 12-1 shows the supported Calendar Server upgrade paths to Java ES Release 4.

Table 12-1 Upgrade Paths to Java ES Release 4 Calendar Server 6 2005Q4
Java ES Release	Calendar Server Version	General Approach	Re-configuration Required
Release 3	Sun Java System Calendar Server 6 2005Q1	Direct Upgrade: Apply patches.	None

Calendar Server Data

The following table shows the type of data that could be impacted by an upgrade of Calendar Server software.

Table 12-2 Calendar Server Data Usage
Type of Data	Location	Usage
Configuration data	cal_svr_base\bin\config\ics.conf	Configuration of Calendar Server
Dynamic application data	Calendar Server database: cal_svr_base\csdb	Store calendar entries on behalf of users.
Directory schema	Directory Server user/group directory	For user attributes needed to support end users

Compatibility Issues

Release 4 Calendar Server does not introduce any interface changes. Calendar Server is backwardly compatible with earlier versions.

Calendar Server Dependencies

Calendar Server dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Calendar Server software. Changes in Calendar Server interfaces or functions, for example, could require upgraded version of components upon which Calendar Server depends. The need to upgrade such components depends upon the specific upgrade path.

Shared components. Calendar Server has dependencies on specific Java ES shared components (see Table 1-6).

Directory Server. Calendar Server accesses user data stored in Directory Server. As a result, Calendar Server upgrades might require extensions of directory schema.

Directory Preparation Tool. Calendar Server uses the Directory Preparation Tool to prepare the directory to support Calendar Server functions.

Access Manager (optional). For software solutions that support single user sign-on for web-based services, Calendar Server can be configured to use Access Manager single sign-on capability.

Messaging Server (optional). Calendar Server can be configured to use Messaging Server to provide messaging notifications of calendar events.

Delegated Admin (optional). Delegated Admin is the preferred utility to use for provisioning users in Directory Server so that Calendar Server has access to the user data needed to provide calendar services.

Upgrading Calendar Server from Java ES Release 3

This section includes information about upgrading Calendar Server from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Introduction

When upgrading Java ES Release 3 Calendar Server to Release 4, consider the following aspects of the upgrade process:

General Upgrade Approach. The upgrade is performed by applying patches to the Release 3 version.

Upgrade Dependencies. While Communications Express has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Communications Express requires only that SASL be upgraded to Release 4. Upgrade of other shared components is optional with respect to upgrade of Communications Express.

In addition, Release 4 Calendar Server is dependent upon Directory Server and optionally dependent on Access Manager, as described in Calendar Server Dependencies. However, these are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Calendar Server to Release 4.

However, Release 4 Calendar Server has a hard upgrade dependency on Directory Preparation Tool; Release 4 Directory Preparation Tool is required to prepare Directory Server for calendaring operations.

Backward Compatibility. Release 4 Calendar Server is backwardly compatible with the Release 3 version.

Upgrade Rollback. Rollback of the Release 4 upgrade of Calendar Server to Release 3 is achieved by removing the patches applied during the upgrade.

Calendar Server Upgrade

This section describes how to perform an upgrade of Calendar Server from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Calendar Server you should perform the tasks described below.

Verify Current Version Information

You can verify the current version of Calendar Server using the following command:

Table 12-3 Calendar Server Version Verification Outputs
Java ES Release	Calendar Server Version Number
Release 4	2005Q4
Release 3	2005Q1

Upgrade Calendar Server Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 4. However, Calendar Server has a hard upgrade dependency only on Directory Preparation Tool. Upgrading of other Java ES Release 3 components upon which Calendar Server depends is therefore optional.

However, if you choose to upgrade all Calendar Server dependencies, they should be upgraded in the following order, all before you upgrade Calendar Server. You can skip any that might already have been upgraded.

Shared Components. Instructions for upgrading Java ES shared components to Release 4 are provided in Chapter 2, "Upgrading Java ES Shared Components".

Directory Server. Instructions for upgrading Directory Server to Release 4 are provided in Chapter 3, "Directory Server and Administration Server".

Access Manager (optional).

Directory Preparation Tool. Release 4 Directory Preparation Tool needs to have been run against Directory Server before configuring Release 4 Calendar Server. If Release 4 Directory Preparation Tool has not already been run against Directory Server, upgrade Directory Preparation Tool to Release 4 and use it to modify and extend the schema of Directory Server (see Chapter 10, "Directory Preparation Tool" for procedures).

Back Up Calendar Server Data

The Calendar Server upgrade from Release 3 to Release 4 requires no re-configuration of Calendar Server. However, as a safety precaution, you might back up your Calendar Server store, located at

Obtain Required Configuration Information and Passwords

No special information about your currently installed version is needed. However you will have to log in as administrator to perform the upgrade.

Upgrading Calendar Server

This section discusses considerations that impact the upgrade procedure for Calendar Server followed by a description of the procedure itself.

Upgrade Considerations

The upgrade of Calendar Server software to Java ES Release 4 takes into account the following considerations:

Calendar Server should be shut down when patches are being applied to the installed image.

Patch files should be kept in the same drive where calendar server is installed. For example, if the calendar server is installed in C:\sun, then the patch files should be present in C drive like C:\sun\CSPatch.

The Release 4 upgrade patches are shown in Table 1-3.

Upgrade Procedure

The procedure documented below applies to Calendar Server on the computer where the upgrade is taking place.

Obtain the required patches, based on Table 1-3.

Patches can be downloaded from:

http://sunsolve.sun.com

Place the obtained patch in the same drive where Calendar Server is installed.

Stop Calendar Server if it is running.

cal_svr_base\bin\stop-cal.bat

Make sure you have upgraded any Java ES components upon which the Calendar Server have hard upgrade dependencies (see Calendar Server Dependencies)

If not already done, upgrade the required shared components to Release 4.

Run the prepatch.bat before executing the patch.

Apply the patch by double-clicking the <Patch-id>.exe

Run postpatch.bat after applying the patch.

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure.

Rolling Back the Upgrade

This section describes considerations that impact the upgrade rollback procedure for Calendar Server followed by the procedure itself.

Rollback Considerations

The procedure for rolling back the upgrade to Release 4 of Calendar Server is pretty much the reverse of the procedure for upgrading to Release 4.

Rollback Procedure

Stop Calendar Server.

cal_svr_base\bin\stop-cal.bat

Remove the respective patches as mentioned in Table 1-3. Execute:

Uninstall_<Patch-id>.bat

Restart Calendar Server.

cal_svr_base\bin\start-cal.bat

Previous Contents Index Next
Sun Java Enterprise System Upgrade Guide for Microsoft Windows