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.
Unfortunately, our internal pubs processes are very weighty. That's not always a bad thing, we need to ensure quality, technical accuracy, and so on. But for some docs, it doesn't make sense to make you wait while the wheels of Sun Pubdom grind slowly on.
But I'm starting to look at this blog as the ultimate cheepo publishing system, for some information at least: a docs-to-go kind of place.
Bottom line: Customers want information quickly. So I'll experiment a bit with a doc that a support expert has readied: Deployment Example: Sun Java Communications Suite 5 on a Single Host (Linux). I know some of you have requested this already, (the doc is really an updated version of the same example on Solaris) and so I'm making a decision: rather than pipe this through the normal (slowww) pubs channels and wrap the info in near-Nirvanic Sun formatting, I'm redirecting it as is to this blog.
Doc Summary: This deployment example describes how to install Sun Java Communications Suite 5 software on one Linux 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.
As an experiment, I'll leave it up to this community to let me know if you find any corrections and I'll take the responsibility to keep the doc up-to-date if you find something that needs fixing. Who knows, perhaps this could become a new and faster way to get certain kinds of information into your hands.
I gather that you don't need any brains to be a spammer, as evidenced by the above email. Yeah, dealing with this crud is a fact of the Info Age. Coincidentally, I just came across a post to help. Check it out: Air's Blog has a nice step-by-step entry of installing SpamAssassin with Sun Java System Messaging Server.
A co-worker has correctly pointed out in the comments that I have this not quite right. It is the configurator.sh script itself that is causing the problem. You do not have the option while running the script to choose between IP address and hostname. The script basically choose the IP address rather than the hostname. But again, the fix is afterwards to manually update the ics.conf file for the parameter mentioned below.
- Factotum Management
4/6/07:
As I mentioned in a previous post this week, there's a Calendar Server 6.3 install issue that I want to make folks aware of.
When you use the configurator.sh script to configure your Calendar Server front end, in a front end/back end deployment, as described here, your are supposed to use a fully qualified domain name for the back-end host the front end is pointing to that you will use DWP to commmunicate with. If by mistake you put in an IP address of the host instead, which evidently the script lets you do, the configuration will not work. And then you'll have to manually go back and enter the FQDN of the host instead of the IP address for caldb.dwp.server.backend.ip in the ics.conf file.
And yes, we do have a bug (CR) filed for this.
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.
This blog copyright 2009 by mb
