|
| |
| Sun Java Enterprise System 2005Q4 Upgrade Guide | |
Chapter 14
Calendar ServerThis chapter describes how to upgrade Calendar Server to Java ES 2005Q4 (Release 4): Sun Java System Calendar Server 6.2 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 upgrades on both the Solaris and Linux operating systems:
Overview of Calendar Server UpgradesThis section describes the following general aspects of Calendar Server that impact upgrading to Java ES 2005Q4 (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 14-1 shows the supported Calendar Server upgrade paths to Java ES Release 4. The table applies to both Solaris and Linux operating systems.
Calendar Server Data
The following table shows the type of data that could be impacted by an upgrade of Calendar Server software.
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.
Calendar Server has dependencies on the following Java ES components:
- 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 Administrator (optional). Delegated Administrator 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 3This section includes information about upgrading Calendar Server from Java ES 2005Q1 (Release 3) to Java ES 2005Q4 (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 Calendar Server has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Calendar Server requires only that SASL be upgraded to Release 4. Upgrade of other shared components is optional with respect to upgrade of Calendar Server.
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.
- Platform Issues. The general approach for upgrading Calendar Server is the same on both Solaris and Linux operating systems, however the patching technologies are different. The upgrade process therefore includes platform-specific procedures.
Release 3 Calendar Server Upgrade
This section describes how to perform an upgrade of Calendar Server from Java ES Release 3 to Java ES Release 4 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. 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:
Note: If the cshttpd command fails on the Solaris 10 platform, set the library path to null when running the command:
Apply Necessary Operating System Patches
On Solaris 10 operating system platforms, you need to apply an operating system patch to perform the Delegated Administrator upgrade procedure (see Required Operating System Patches).
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 4, "Directory Server and Administration Server".
- Access Manager (optional). Instructions for upgrading Access Manager to Release 4 are provided in Chapter 11, "Access Manager".
- 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 12, "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 superuser to perform the upgrade.
Upgrading Release 3 Calendar Server (Solaris)
This section discusses considerations that impact the upgrade procedure for Calendar Server followed by a description of the procedure itself.
Upgrade Considerations (Solaris)
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.
- In architectures in which different Calendar Server subcomponents reside on different computers, for example Calendar Server back-end store on one computer, and Calendar Server front-end processes (such as cshttpd) on another, the upgrade must be performed on all such computers.
- The Calendar Server upgrade applies to multiple subcomponents of Calendar Server on one computer using the same installed image.
- The Release 4 Calendar Server upgrade patches for Solaris OS are shown in the following table:
Table 14-4 Patches1 to Upgrade Calendar Server on Solaris
Description
SPARC
Solaris 8, 9, & 10
X86
Solaris 9 & 10
Calendar Server core
116577-24
116578-24
Calendar Server localization
117010 -23
117011 -23
1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table.
Upgrade Procedure (Solaris)
The procedure documented below applies to Calendar Server on the computer where the upgrade is taking place.
- Obtain the required patches, based on Table 14-4.
Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Log in as root or become superuser.
su -
- Stop Calendar Server if it is running.
CalendarServer-base/cal/sbin/stop-cal
- If you have not already done so, upgrade the SASL shared component to Release 4 and any other shared components you wish to upgrade.
See Upgrade Calendar Server Dependencies.
- Apply the appropriate Calendar Server patches in Table 14-4.
patchadd patch_ID
- Confirm that the patch upgrade was successful:
showrev -p | grep ics
The output should return the versions of patch IDs applied in Step 5.
- Restart the Calendar Server that was stopped in Step 3.
CalendarServer-base/cal/sbin/start-cal
Upgrading Release 3 Calendar Server (Linux)
This section discusses considerations that impact the upgrade procedure for Calendar Server followed by a description of the procedure itself.
Upgrade Considerations (Linux)
The upgrade of Calendar Server software to Java ES Release 4 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 4 upgrade patches differ from the Solaris patches.
The Release 4 Calendar Server upgrade patches for Linux OS are shown in the following table:
Table 14-5 Patches1 to Upgrade Calendar Server on Linux
Description
Patch ID and RPM names
Calendar Server core
117851-24
Calendar Server Locale
117852-23
1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table.
Upgrade Procedure (Linux)
The procedure documented below applies to Calendar Server on the computer where the upgrade is taking place.
- Obtain the required patches using the patch numbers and RPM names from Table 14-5. Use this information to obtain the version numbers for the RPM.
Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Log in as root or become superuser.
su -
- Stop Calendar Server if it is running.
CalendarServer-base/sbin/stop-cal
- If you have not already done so, upgrade the SASL shared component to Release 4 and any other shared components you wish to upgrade.
See Upgrade Calendar Server Dependencies.
- Apply the RPMs for Calendar Server in Table 14-5.
rpm -Fvh sun-calendar-core-Locale-6.2-10.3.i386.rpm
rpm -Fvh sun-calendar-core-6.2-10.7.i386.rpm
rpm -Fvh sun-calendar-api-6.2-10.7.i386.rpm- Confirm that the patch upgrade was successful:
rpm -qa | grep sun-calendar
The new version numbers of the RPMs should be returned.
- Restart the Calendar Server that was stopped in Step 3.
CalendarServer-base/sbin/start-cal
Verifying the Upgrade
The upgrade of Calendar Server to Release 4 is verified by confirming that the upgrade patches have been properly applied. The steps for this verification were included in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).
Post-Upgrade Tasks
There are no post-upgrade tasks beyond the steps described in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).
Rolling Back the Upgrade (Solaris)
This section describes considerations that impact the upgrade rollback procedure for Calendar Server followed by the procedure itself.
Rollback Considerations (Solaris)
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 (Solaris)
- Log in as root or become superuser.
su -
- Stop Calendar Server.
CalendarServer-base/cal/sbin/stop-cal
- Remove the patches in Table 14-4.
patchrm patch_ID
- Restart Calendar Server.
CalendarServer-base/cal/sbin/start-cal
Multiple Instance Upgrades
In some deployment architectures Calendar Server is deployed on multiple computer systems to provide for high availability. For example, you have the Calendar Server Store component running in a Sun Cluster environment to provide high availability.
For Calendar Server instances running in a cluster environment, those instances share the same configuration. You need to apply Calendar Server upgrade patches to each of the instances, and for a Release 3 to Release 4 upgrade there is no re-configuration required.
Upgrading Calendar Server from Java ES Release 2The procedure for upgrading Java ES 2004Q2 (Release 2) Calendar Server to Release 4 is very similar to that for upgrading Release 3 Calendar Server to Release 4, with the exception that the pre-upgrade tasks should include the upgrading to Release 4 of all shared components (see Table 1-6) and all locally-resident product components upon which Calendar Server depends:
- Shared Components. Instructions for upgrading Java ES shared components to Release 4 are provided in Chapter 2, "Upgrading Java ES Shared Components".
- Directory Server. Directory Server rarely resides on the same computer as Calendar Server, however, instructions for upgrading Directory Server to Release 4 are provided in Chapter 4, "Directory Server and Administration Server".
- Access Manager (optional). Instructions for upgrading Access Manager to Release 4 are provided in Chapter 11, "Access Manager".
- Directory Preparation Tool. Directory Preparation Tool rarely resides on the same computer as Calendar Server, however, instructions for upgrading Directory Preparation Tool and running it against Directory Server are provided in Chapter 12, "Directory Preparation Tool".
To upgrade Release 2 Calendar Server to Release 4, use the instructions in Upgrading Calendar Server from Java ES Release 3, except substitute Release 2 wherever Release 3 is referenced.
In addition, the Release 2 to Release 4 upgrade requires the post-upgrade task of configuring Calendar Server hot backup, accomplished by adding hotbackup parameters to the Calendar Server ics.conf configuration file. The instructions for this post-upgrade re-configuration can be found at the following location: http://docs.sun.com/doc/819-2433/6n4nlfjnq?a=view