Looks like this webinar could be of interest to the Comms Community.
Date/Time: Thursday, October 29, 2009 9:30 AM - 10:30 AM PDT
Register here:
Looks like this webinar could be of interest to the Comms Community.
Date/Time: Thursday, October 29, 2009 9:30 AM - 10:30 AM PDT
Register here:
Get the Communications Suite 7 software. Find out What's New in Communications Suite 7. Start a Communications Suite 7 installation.And read JimP's tribute to Comms.
Update:
Product info here.
Don't want to read, okay, watch the following video:
The next update to Sun Java Communications Suite is getting close to shipping. Communications Suite 7 includes both new products and feature enhancements to existing products. Here's a quick look at what's new:
Convergence 1 Update 3 includes the following changes and new features:
Messaging Server 7 Update 3 includes the following changes and new features:
Calendar Server 7 includes the following new features:
Calendar Server 7 provides support for the calendaring extension to WebDAV as defined in RFC 4791. The CalDAV draft extends the basic HTTP and WebDAV commands to enable all the functionality required for calendaring and scheduling activities. Included in Calendar Server 7 is support for the following:
Calendar Server 7 supports the iCalendar data format as defined in RFC2445bis. The following components are supported:
Recurring rules and exceptions are also supported.
Calendar Server 7 supports basic HTTP authentication and authentication over SSL. With HTTP authentication you can do the following:
Calendar Server 7 supports scheduling as defined in Version 04 of the CalDAV Scheduling draft. This specification defines explicit scheduling, where invitations and replies are placed in the recipient's inbox. It is then the client's responsibility to view and move them to the appropriate calendars. The latest version of the draft, which defines implicit scheduling, will be implemented in a future release.
The following list provides more information about scheduling support in Calendar Server 7:
Calendar Server 7 supports WebDAV Sync, an extension of the WebDAV protocol as described in the WebDAV Sync draft. WebDAV Sync defines a protocol for an HTTP client to query an overview of the data changes on the HTTP server. The result is that clients can efficiently synchronize their local data cache with the server.
Calendar Server 7 provides a free-busy servlet to enable non-CalDAV clients to at least check users' freebusy information by using the upcoming free-busy-read URL standard. This standard is compatible with the free-busy URLs used by Calendar Server 6.0 through Calendar Server 6.3.
You install Calendar Server software by using the Communications Suite installer. You then configure a Calendar Server instance by using the init-config configurator, which makes configuration settings for your Directory Server, GlassFish Enterprise Server, and Calendar Server (DAV server) hosts. In addition, Sun Service Tags are used solely to identify Sun products to Sun. Sun uses service tag information to better support you. Registration data is only collected when your system administrator requests gear discovery. Calendar Server 7 enables you to use the Service Tag Facility on Solaris OS 10.
The Calendar Server 7 logging service is a multilevel, configurable, logging module to help capture activity or debugging issues.
Calendar Server 7 provides Java Message Service (JMS) notifications and email notifications for database changes and event or task email alarms. You can configure the server to produce JMS notifications for every database change and every alarm. If you choose, you can write your own subscribers to these notifications. In addition, Calendar Server 7 provides a subscriber program, which you can configure, that consumes the JMS notifications and sends email for database changes and email alarms.
Calendar Server 7 contains an admin servlet, providing a web interface with which you view and even delete contents in your collections. You can also use the admin servlet to import iCal data to specific calendar collections.
By using the davadmin command, you can perform the following tasks:
You can use Jconsole to perform these tasks.
Calendar Server 7 also provides database utilities to back up and restore calendar collections.
A predefined Admin group in LDAP is created during initial configuration, to which you can can add users for proxy login and management of any user account. The default administrator user added during initial configuration is calmaster.
Calendar Server 7 uses Directory Server with the latest Communications Suite schema to store and manage user information in its LDAP database. Support includes:
Calendar Server 7 supports "Calendar Collection Entity Tag (CTag)," an extension to CalDAV that provides a fast way for a client to determine if the contents of a calendar collection have changed.
The Calendar Server 7 architecture enables you to deploy multiple front-end calendar servers and multiple back-end mySQL database servers to achieve horizontal scalability. See Calendar Server Logical Architecture for more information.
Like the rest the the Communications Suite products, Calendar Server 7 supports virtual domains, also called hosted domains, which is the ability to support users in more than one domain, on a single deployment. A default domain is configured during the initial configuration.
This version of Calendar Server 6.3 includes bug fixes only.
Indexing and Search Service 1 includes the following new features:
ISS integrates with Convergence through its existing search interface, that is, Convergence continues to execute searches by using the compact WMAP protocol with the mshttpd daemon. The mshttpd daemon continues to service these requests by using the IMAP protocol. Messaging Server integrates with ISS through an enhanced IMAP SEARCH functionality, and a subset of these search requests (particularly, body searches) go to ISS for fulfillment. Messaging Server consumes the ISS output and reformats it for the email client.
The result is that no changes are needed to Convergence or Thunderbird clients because ISS integrates with Messaging Server rather than the end-client.
The long-term plan for integrating Convergence and Thunderbird (through a plug-in) with ISS will be to have the clients communicate directly with ISS directly by using ISS's RESTful web service for search.
Instant Messaging 8 Update 2 includes the following changes and new features:
Delegated Administrator 7 includes the following changes and new features:
Delegated Administrator 7 now supports Calendar Server 6.x and
Calendar Server 7 provisioning.
This version of Connector for Outlook 7.3 Update 1 includes the following new features:
In the never-ending chore of tracking Communications Suite component patches, you'll want to bookmark the Communications Suite Component Patches page, which lists patches for both Communications Suite 5 and Communications Suite 6 releases.
Many thanks to Shane Hjorth for pulling this page together.
Anthony Waldron has released a new version of the EMRA toolkit. See his blog for details, or go directly to Go and download the toolkit.
For those unfamiliar with EMRA, here's the blurb: The EMRA Toolkit provides a powerful yet flexible framework to automate the deployment of the Communications Suite components in a reliable and repeatable manner. By leveraging Solaris silent install, and using a few shell scripts, you need to only obtain copies of the Communications Suite software (for the Communications components), the Java Enterprise System software (for the other non-Communications components, such as Directory Server), and Solaris OS to get started with a hands- and worry-free Communications Suite deployment.
More EMRA info here.
Just published: a white paper on designing tiered storage with Messaging Server, with the eye on cutting storage costs. Abstract:
Service providers face unrelenting pressure to increase storage for user mailboxes. This paper explains how using production products, such as Sun Communications Suite software, the Solaris ZFS file system, and a Sun Storage array, can cut storage costs by half, while performance (measured by messages per second) can be increased by more than 50 percent in environments with millions of users. Extensive load testing has shown that this single-rack solution provides a cost-effective message store for two million users. It is easily replicated and highly modular.
Have a look at the top twenty most frequently accessed pages on the Communications Suite wiki(s) for June. I see a noticeable uptick in access to Communications Suite 6 Update 2 information.
I've been collecting a few items of interest for the Communications Suite community. So, in no apparent order, here goes:
And in case you're wondering about the availability of VirtualBox and VMware images for Communications Suite 6 Update 1, yes, they are in the works. There is currently an issue with the Instant Messaging configurator that is being worked on.
In case you missed it, Communications Suite got an update and a new add-on:
Expect the release of Communications Suite 6 Update 1 in the very near future. For a summary of all features in Communications Suite 6 Update 1 that are new or have been enhanced, see the What's New document on the Communications Suite wiki.
According to a report to be published in October by the New York-based research firm Basex, interruptions such as spam, other unnecessary e-mail and instant-messages take up 28% of the average knowledge worker's day.On top of that is what Basex chief analyst Jonathan Spira refers to as recovery time -- the time to get back to where you were before you were interrupted, which Spira says is 10 to 20 times the duration of the interruption. These interruptions account for up to 2.1 hours per worker per day. Multiply that by 56 million knowledge workers in the U.S., he calculates, and the cost is $650 billion per year.
This blog copyright 2009 by mb