Monday Jun 11, 2007

Communications Suite: Just the FAQ's, Ma'am

I'm currently participating in a pilot project that I think will be a very cool addition to the Communications Suite knowledge base: a Sun-sponsored wiki that I'm using to create a Communications Suite FAQ, which will be able to be edited by you, the Comms Community.

Plan of record is to use the wiki internally for a few weeks then turn it loose for viewing externally. After a while at the view-only stage, we'll open it up for community participation. Looks like you'll need an SDN login/pwd to participate.

Right now, I'm organizing the FAQ by product (Messaging Server, Calendar Server, Instant Messaging, and so forth). Each product link takes you to the FAQ for that product, which is then organized by technology life-cycle, along the same lines as the Tasks tab on the Communications Suite BigAdmin Hub, for example:

  • Evaluating Messaging Server
  • Planning Your Messaging Server Deployment
  • Installing Messaging Server
  • Customizing Messaging Server
  • Managing Messaging Server
  • Upgrading Messaging Server
  • Troubleshooting Messaging Server
If you have ideas on how you'd like to see this FAQ organized, feel free to drop a line or add a comment. I'm open to suggestions.

Additionally, I'm adding a section called "Customer Supplied Solutions" for that type of Q/A where someone asks of the community, how have you implemented X, or what type of server have you used for Y.

Stay tuned for details.

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.
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