Wednesday Oct 01, 2008

Communications Suite: Distributed Installs Just Got a Bit Easier

Installing a full Communications Suite deployment may still not be for the faint of heart, but things just got a bit easier thanks to the availability of the Enterprise Messaging Reference Architecture (EMRA) Toolkit. For more information, check out the Communications Suite Tools and Contributions page, where you can get the EMRA Toolkit software, Getting Started Guide, and other helpful information.

Thursday Apr 05, 2007

Communications Suite Odds and Ends

As usual, lots to scrape off the Comms windshield. Here are some interesting factoids that have turned up in the past few days:

  • Installing a Comms 5 Calendar Server deployment, front end and back end (where the front end is using the DWP protocol to communicate with the back end): when you use the csconfigurator.sh program on the front end to configure Calendar Server, you are prompted to use the IP address of the back end to point to. Unfortunately, this needs to be the host name, so you'll have to correct that manually. (Bug has been filed.)
  • When deploying Connector for Outlook with Calendar Server/Communications Express, realize that Connector needs to access calendar in WCAP (a calendar protocol encapsulated in HTTP) and communicate directly to a calendar process that 'speaks' WCAP (cshttpd). In a multi-tier deployment, that means installing a Calendar Server front-end on your host running Communications Express. This calendar front-end prowides the WCAP services necessary for Connector, and then communicates to the back-end host using the DWP protocol (port 57779 by default; thus, be carefull with you firewall rules between front-end and back-end host). For more information on this kind of deployment:

    http://docs.sun.com/app/docs/doc/4439/6n4udv3em?a=view
    http://docs.sun.com/app/docs/doc/4439/6n4udv3cg?a=view

  • I pushed a new tech note to docs.sun.com today, should be available by tomorrow: Using Sun StorageTek 53xx NAS with Messaging Server Message Store.
  • Our deployment team says that you need an expert to install Comms, and even then, don't expect a problem-free time. Question: Is this news to anyone? I do hope, at least, that our customers have been seeing some improvement in this area from at least the docs standpoint. If not, you know you can always drop me a line and let me know.
  • Found this interesting tech note from our Access Manager brethren: Sun Java System Access Manager ACI Guide. Personally, I'd rather have to eat peanut butter and crackers stranded in the desert without water than to have to deal with AM ACIs, but here you have a new peek into what the heck's going on there.

Wednesday Mar 14, 2007

Communications Suite 5 Doc Leak: Installing on a Single Host

I know we're not shipping Communications Suite 5 until March 23, but you can go ahead and grab a copy of single host deployment example now:

http://docs.sun.com/app/docs/doc/820-0086

This deployment example describes how to install Sun Java Communications Suite 5 software on one computer for a functioning deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components.

Now all you have to do is wait for the bits.

Update In the past, this example has documented how to install the Communications Channels (portlets) provided by our Portal Server product. That's a thing of the past. Looks like Portal is no longer providing these specific Comms Channels anymore, though the 'capability' to deploy these channels still exists. Heads-up to those of you who have used this out-of-the-box functionality in previous releases.

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