Comms Suite 5 Docs: Mea Culpa

An astute reader has pointed out the following:
I was reading Comms 5 (March 2007) Deployment planning guide and came across a section that talks about deploying Comms Express, chapter 24 page 291. I believe the deployment scenario described is not accurate and does not represent the architectural change that took place between versions 6.2 and 6.3. There is no longer a requirement for Access Manager SDK and also Messaging Express Multiplexor is no longer used.
Link in question is here: Communications Express on Remote Host Architecture

Sure enough, the doc is wrong on both counts. I will correct these errors, and update Figure 24-2, as soon as I can. In the meantime, what should have appeared was something along these lines:

Figure 24-2 shows a Communications Express architecture where both intranet and Internet users log on to Communications Express on the front-end host, which accesses the back-end host on their behalf. You can enable SSO on the front-end host such that Communications Express validates the session in Access Manager.

You install the front-end host with the following components:

  • Messaging Server (Webmail Server)
  • Calendar Server
  • Web container
  • (Optional) Access Manager SDK
  • Communications Express

You install the back-end with the following components:

  • Directory Server
  • Messaging Server (Mail Store)
  • Calendar Server
  • (Optional) Web Container and Access Manager

The new figure should look something like this (prettied up, 'natch, thanks to our illustrator):

Thanks again to that careful reader.

Comments:

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