Use this page to locate build and patch information for Calendar Server releases. If newer patch revisions become available, use the newer ones instead of those shown in the table.
As a workaround to learning about new patches, you can use the Confluence "watch" feature to monitor this page. When new patches are available, this page is updated with that information. You then receive an email message that this page has been updated. The "watch" feature is available under the Tools menu.
When you perform a fresh installation by using the Communications Suite installer (commpkg install), you install the current patch levels for Calendar Server. You use the commpkg upgrade command to upgrade to newer product releases. For more information, see the commpkg upgrade command, which is provided in the Communications Suite Installer zip file.
As newer patches become available between releases, you install them by using the patchadd command on Solaris, or the rpm command on Red Hat Linux. These patch commands run the related pre- and post-patch scripts to ensure proper patch installation.
If the patch installation fails during the pre-patch phase, you need to correct the problem and re-apply the patch. If the patch installation fails during the post-patch phase, you need to follow the instructions in the error message to manually resolve the problem.
The following table shows the patch history for Calendar Server 7.
Calendar Server 7 Patches
|Suite||Suite Release Date||Calendar Server Version Number||Oracle Solaris SPARC||Oracle Solaris x86||Red Hat Linux|
|Problems Fixed in Patch 15||2014-May-07||126.96.36.199.0|| 142785-15
|CommSuite 7 Update 5 New Features||2013-Oct-31||188.8.131.52.0|| 142785-14
|Problems Fixed in Patch 12||2013-Mar-08 (Patch released 2013-Aug-20)||7 Update 3 Patch 12||142785-12||142786-12||142787-12|
|Problems Fixed in Patch 10||2013-Mar-08 (Patch released 2013-Apr-14)||7 Update 3 Patch 10||142785-10||142786-10||142787-10|
|New Features in Patch 9||2013-Mar-08 (Patch released 2013-Jan-06)||7 Update 3 Patch 9||142785-09||142786-09||142787-09|
|New Features in Patch 8||(Patch released 2012-Oct-17)||7 Update 3 Patch 8||142785-08||142786-08||142787-08|
| Problems Fixed in Patch 7
||(Patch released 2012-Aug-10)||7 Update 2 Patch 7||142785-07||142786-07||142787-07|
|Problems Fixed in Patch 6||(Patch released 2012-Apr-10)||7 Update 2 Patch 6|| 142785-06
|CommSuite 7 Update 2 New Features in Patch 5||2011-Dec-15|| 7 Update 2 Patch 5
|CommSuite 7 Update 2 New Features|| 2011-Oct-06
|| 7 Update 2 (Patch 4)
|CommSuite 7 Update 1 New Features|| 2011-Apr-21
|| 7 Update 1 Patch 3
|CommSuite 7 Update 1 New Features||2010-Sep-02|| 7 Update 1 Patch 2
|CommSuite 7 Update 1 New Features||2010-Sep-02|| 7 Update 1 (Patch 1)
If you are upgrading from one Calendar Server update version to another, for example, from Calendar Server 7 Update 2 to Update 3, do not use these patch instructions. Instead refer to Calendar Server 184.108.40.206.0 Upgrade.
- Download the Calendar Server 7 patch.
- Back up your Calendar Server back-end database.
For example, you can use the davadmin db backup command.
- (Optional) To prevent users from connecting during the patch application, you might want to disable GlassFish Server from servicing incoming requests.
See Disabling GlassFish Server During Calendar Server Patch Application for more information.
- Run the platform-specific patch command.
- On Solaris, run patchadd.
- On Red Hat Linux, run rpm -F.
- Run the init-config command to enter the current deployment configuration values.
- Run the merge-config command to merge in any other changes that were done to the configuration after the initial configuration, and that are not controlled by the init-config program.
For example, you might have customized configuration parameters in the davserver.properties file.
- (Optional) Resolve any problems.
- If the patch installation detects a problem during the pre-patch phase, correct the problem and re-apply the patch.
- If the patch installation detects a problem during the post-patch phase with merging configuration files, reconcile the merged files.
- Restart GlassFish Server.