Wanted: A Few Good Communications Suite Examples

We in documentation hear what customers want: more examples. Communications Suite examples, especially for deployment, are unfortunately far and few between. Good news is that I'm updating the single-host deployment example for the upcoming Communications Suite 5 release.

And more good news: the document itself is shrinking by a number of pages. Does this mean that the Comms Suite stack (along with the Java ES components it requires) is getting easier to install? Well, maybe. Some changes in the Communications Suite 5 release that are reflected in this doc include:

  • Portal Server is no longer installed. (That alone probably accounts for the page reduction I mentioned above.)
  • Solaris Operating System (OS) 10 is used.
  • Hosted domains are now configured.
  • Proxy auth is now the way that Single Sign-On is accomplished. As a result, Access Manager is no longer required for Communications Express and there are fewer configuration settings that you have to enter. (Sigh of relief there.)

I should have this document ready at release time, unlike in the past, where we had some lag time between getting the release bits installed to be able to test the doc and get it out.

BTW, if you are looking for current Communications Suite (aka Communications Services) examples, check them out here:

Comments:

I'd love to see a "fully redundant" system config. One where you split everything out and then place things that can go behind load balancers on a pair of servers, and cluster things that cant (like the message store itself). I have some install cheat sheets, but always feel that i'm missing something along the way (like how one sets up all of the various components to use redundant ldap servers) Any chance of seeing that in the future? The docs on installing the stack on a T2000 system with the various parts in their own zones was a great help (since it explained how to point the bits and pieces to a remote server), but there are a number of issues when you are looking for a scalable and redundant system.

Posted by John on January 30, 2007 at 11:04 AM MST #

I thought I posted this, but looks like blogger ate it. Anyways, good feedback, thanks. I wish I could say we'll be serving up this kind of example soon, but the reality is, setting up and documenting a fully redudant deployment such as this is very time and resource intensive. And, like a lot of places these days, we're short on both. Nevertheless, slowly but surely, we do plan to improve the docs in this area. I did get some internal feedback on this topic, to wit: "I am not particularly in favor of redundant Directory Server configuration notations except in the simplest cases. Directory Server Complexes can be designed with very high availability by the use of architectural layering, isolation with load balancers, directory proxy server, and similar techniques."

Posted by Joe Sciallo on February 01, 2007 at 01:11 AM MST #

fwiw - the single host install was much more straightforward than the 2005q4 one which had too many opaque incantations for my taste. thanks.

Posted by david on April 03, 2007 at 01:30 AM MDT #

Thanks David, glad we're getting better at this. Also, don't know if you're interested, but we're starting work on a Linux version of this doc. Stay tuned.

Posted by Joe Sciallo on April 03, 2007 at 02:52 AM MDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

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

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today