|
| |
| Sun Java Enterprise System Upgrade Guide for HP-UX | |
Chapter 12
Calendar ServerThis chapter describes how to upgrade Calendar Server 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.
Overview of Calendar Server UpgradesThis 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.
Calendar Server Data
The following table shows the type of data that could be impacted by an upgrade
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.
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). Calendar Server upgrades might depend upon the upgraded versions of theses shared components.
- 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 3This 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 Calender Server has dependencies on a number of Java ES shared components (seeTable 1-6), Release 4 Calender Server 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.
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 HP-UX platform.
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
# /opt/sun/calendar/bin/cshttpd -#
Table 12-3 Calendar Server Version Verification Outputs
Java ES Release
Calendar Server Version Number
Release 3
2005Q1
Release 4
2005Q4
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".
- 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 10, "Directory Preparation Tool".
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 following path:
/var/opt/sun/calendar/csdb
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 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:
Table 12-4 Patches1 Upgrade Calendar Server
Component
Patch ID
Calendar Serve Core
121512-02
Calendar Server locale
121928-01
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 above table.
The procedure documented below applies to Calendar Server on the computer where the upgrade is taking place.
Upgrade Procedure
- Obtain the required patches, based on Table 12-4.
Patches can be downloaded from:
- Log in as superuser.
- Stop Calendar Server if it is running.
cal_svr_base/sbin/stop-cal
- If not already done, upgrade the SASL shared component to Release 4 and any other shared components you wish to upgrade.
- Apply the appropriate Calendar Server patches in Table 12-4.
# swinstall -s <patch_ID>
- Confirm that the patch upgrade was successful:
# swlist -v1 patch |grep <patch_ID>
The output should return the versions of patch IDs applied in Step a.
- Restart the Calendar Server that was stopped in Step a.
cal_svr_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.
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
- Obtain the required patches based on the Table 12-4.
Patches can be downloaded from:
- Log in as superuser.
- Stop Calendar Server.
cal_svr_base/sbin/stop-cal
- Remove the patches in Table 12-4.
# swremove <patch_ID>
- Restart Calendar Server.
cal_svr_base/sbin/start-cal