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 Mar 15, 2007

Communications Suite 5 Q&A: Access Manager, Delegated Admin, and Schema

There continues to be a fair amount of confusion (or miscommunication on our part) around Access Manager, Delegated Administrator, and schema choice. And the same confusion potentially could exist when it comes to deploying Comms Suite 5. So, here in a nutshell, are what I think are the basic questions and answers surrounding these products. I'll try and keep track of these issues going forward and continue to post them.

  1. In Communications Suite 5, does Delegated Administrator 6.4 still require you to deploy Access Manager?
    Yes, Delegated Administrator 6.4 still requires you to deploy Access Manager.
  2. In Communications Suite 5, does Communications Express 6.3 require you to deploy Access Manager?
    Starting with the Communications Suite 5 release, this dependency on Access Manager for Schema 2 has been removed.

    In previous releases, Communications Express used the following APIs and libraries to establish connections and fetch information from an LDAP store:

    • Domain MAP API (which a part of Communications Express) if Communications Express was deployed using Schema 1 mode.
    • Access Manager SDK if Communications Express was deployed using Schema 2

    This made Communications Express dependent on Access Manager in Schema 2 mode even though Access Manager is not mandatory for it to work apart from just connecting and fetching information from the LDAP store.

  3. When do I need to deploy Schema 2? Do I only need Schema 2 in an Access Manager/Delegated Administrator situation?
    Delegated Administrator currently supports only Schema 2. Other situations requiring Schema 2 include integration with Portal Server, and with Access Manager (for SSO).
For more information on these topics, see my previous entry.

Monday Jan 22, 2007

Communications Suite - Overlooking the Obvious?

I get lots of email concerning all kinds of aspects of our Communications Suite products. As a writer, part of my job is to sift and dig through this constant heaping of information, and ultimately help determine what to do with it.

Here's a quick grab bag of facts that seemed perhaps obvious and then again, perhaps not. If we had a Frequently Asked Questions document, this is where I would locate such information. (Note: I am investigating a means to do this on a Sun external site, such that the FAQ would be editable by anyone. Stay tuned for details.)

PDA Access to Communications Express?

You need Sun Java System Communications Sync, which syncs PalmOS and Windows Mobile 5.0 PDAs to Sun calendar and contacts.

Communications Express Without Access Manager?

It's a current requirement, when running Communications Express 6 2005Q4 to have to use Schema 2 and Access Manager. The Access Manager requirement is evidentally removed in the upcoming release (Communications Suite 5, Communications Express 6.3). The Communications Express 6.3 Administration Guide will have the details.

Will a New Messaging Server 6.x MTA Function with a 5.2 Message Store?

It depends on your setup. You cannot mix Messaging Store 5.2 store executables with 6.x MTA executables. However, you may deploy a 6.x MTA running on one host delivering mail to a 5.2 Message Store running on another host. In such a deployment, you'll also need a 5.2 MTA on the store machine because LMTP isn't supported in Messaging Server 5.2, but such a setup will function.

ACLs Missing from Messaging Server 5.2 imsbackup?

The imsbackup utility in Messaging Server 5.2 does not back up the ACLs. This is a known issue. Unfortunately, this could impact maibox migrations. As a workaround, you can get the ACL list from the old store with the following command:

mboxutil -l -p pattern -x

then set it with readership -s after the migration.

Adding New Spelling Dictionaries to Communications Express?

The dictionaries in Communications Express are from ispell, which can be downloaded here:

See the Communications Express Customization Guide for details on installing the new dictionaries.

Calendar Server: Linux or x86 Front-end with a Solaris SPARC Back-end?

Beginning with Calendar Server 6.3, mixing different architectures for front-end and back-end machines is now supported. The hardware platforms no longer must be the same on each end. The big-endian vs.small-endian incompatibility no longer applies and you can now use both an x86 platform machine and a SPARC platform machine in the same Calendar Server deployment containing front-end and back-end machines. You can also mix Linux and Solaris x86 systems for front-end and back-end machines.

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


« July 2016