Communications Suite 7: Installation Tips

Hat Tip David L.

I attended a webinar today on the Communications Suite 7 installer. Passing along some notes.

Installation Is a Two-Step Process

Remember that in the Comms world, "installation" consists of installing the software bits and then configuring them. The Communications Suite installer only lays down the software bits. It does not configure them. Each individual Communications Suite component product has its own configurator that you then run. We wanted to separate these two steps for robustness, as configuration is where the majority of the work actually occurs in a Comms installation.

32-Bit Versus 64-Bit

In Communications Suite 7 and going forward, Messaging Server on Solaris (SPARC and x86) is only available in 64-bit. Messaging Server is only in 32-bit for Red Hat Linux (no 64-bit support yet, this is forthcoming, but no timeframe). Also, Messaging Server has dropped support for Solaris OS 9, Solaris OS 10 32-bit, and Red Hat Linux 3.

Installation for Power Users

Power users: You can use --OSversionOverride switch to install some Communications Suite component products on Solaris OS 9 or other dropped platforms. See for more information. Note that you will only see the products that are runable on that OS platform. For example, you wouldn't see Indexing and Search Service 1 nor Calendar Server 7 on Red Hat Linux 4 32-bit, because those two new component products are not officially supported on that platform. On Solaris OS 9 SPARC, the Communications Suite installer would not show you you Messaging Server 7 Update 3. And so on.

Where's Communications Express 6.3?

Going forward, Communications Express is deprecated in favor of Convergence, so you will not see it in the Communications Suite 7 installer. Communications Express is still supported. If you are looking to install Communications Express now, I guess you'd need to get the Communications Suite 6 Update 2 bits.

New Component Products

Brand new in this release: Calendar Server 7 (our CalDAV product), and Indexing and Search Service 1 (gives you the ability to index and then search your email attachments). Note that you'll continue to see Calendar Server 6.3 in the Communications Suite 7 installer, as Calendar Server 7 is not yet supported by Convergence. Also of interest. You can have a coexistent deployment of Calendar Server 7 and Calendar  6.3. See for more information.

Calendar Server 7 uses MySQL as its backend, and the Communications Suite installer treats it as a shared component. The CI checks if there is an existing MySQL version but will not upgrade or uninstall MySQL. If that's your case, you'll need to refer to the MySQL docs on how to upgrade or uninstall.

Installing Just a Calendar Server 7 Back End

It's a bit tricky, but doable: See for more information. Basically, you preface the Calendar Server 7 component with a tilde (~) to just install its dependent component products, which in this case is just MySQL.


Can calendar server use SSO - can't find that info any where - would be useful to have.

Posted by kangcool on September 30, 2009 at 07:30 AM MDT #

Do you mean CS 6.3? Here:

Posted by Joseph Sciallo on September 30, 2009 at 09:39 AM MDT #

No CS7

beta seemed quite nice, not seen any thing on sso in current docs or planned features.

Posted by Kangcool on September 30, 2009 at 09:57 AM MDT #

I checked with the Sun engineers. Looks like it's not yet planned for CS7.

Posted by Joseph Sciallo on October 01, 2009 at 03:06 AM MDT #

I was hoping for atleast planned.

It does put a bit of a restriction on it's use. But that's probably why CS 6.3 is still about

Posted by Kangcool on October 01, 2009 at 07:03 AM MDT #

6.3 is for Convergence. Next update to 7 is planned to support Convergence.

Posted by Joseph Sciallo on October 01, 2009 at 07:17 AM MDT #

Post a Comment:
  • HTML Syntax: NOT allowed

Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.


« February 2016