Communications Suite 6 What's New

What's New in This Release of Communications Suite 6

This document summarizes all features in Sun Java Communications Suite 6 that are new or have been enhanced since Sun Java Communications Suite 5 was originally distributed in March 2007, for the following components:

  • Sun Java System Calendar Server 6.3
  • Sun Convergence 1.0
  • Sun Java System Messaging Server 7.0
  • Sun Java System Instant Messaging 7.3
  • Sun Java System Delegated Administrator 6.4
  • Sun Java System Communications Express 6.3
  • Sun Java System Connector for Microsoft Outlook 7.3

This document contains the following sections:

What's New in Communications Suite 6

Communications Suite 6 includes the following changes and new features:

New Installer for Communication Suite

Beginning with this release of Communications Suite 6, Communications product components are installed through a new Communications Suite installer. Communications product components continue to interoperate with Java Enterprise System components. Use the Java Enterprise System installer to install Java ES components, such as Sun Java System Directory Server and Sun Java System Access Manager.

You use the Communications Suite installer, commpkg, to install, uninstall, upgrade, and backout Communications product components. The commpkg installer exists only in CLI form, but also has a silent mode of installation. No GUI form is available.

For more information on installing Communications Suite 6, see the Sun Java Communications Suite 6 Installation Guide.

Upgrading to Communications Suite 6

If you choose to upgrade to Communications 6, see the Communications Suite 6 Upgrade Guide.

System Virtualization Support

System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems.

Communications Suite supports the VMware container (VMware ESX Server 3). As support for other virtulization platforms (LDOMs, xVM Server, etc.) becomes available we will update this document.

For information about Sun support for Sun Java System products in virtualized environments, see http://docs.sun.com/doc/820-4651.

What's New in Calendar Server 6.3

Calendar Server 6.3 includes the following changes and new features:

Passwords Removed From Calendar Server Configuration Files and Obfuscated

In the past, the Calendar Server configuration file stored some passwords in clear text. Though the ics.conf file has read permission restrictions, the passwords could be visible to someone else when the administrator edits the configuration file. In Calendar Server 6.3, the passwords have been moved to another file and obfuscated by base 64 encoding them. The base 64 encoding prevents someone from accidentally seeing the passwords. You must still protect the file with read permission restrictions, and keep the file secure so that no unauthorized user can get to it, to keep the passwords secure.

If you are installing Calendar Server for the first time, the configuration program encodes the passwords that you create during the configuration process, and stores them in a separate password configuration file.

If you are upgrading your existing Calendar Server software to the Calendar Server 6.3 version, the configuration program encodes the existing passwords found in the ics.conf file, and moves them to the password configuration file.

In both cases, the configuration program also adds a new ics.conf parameter to indicate the location of the password file, as shown in the following example:

local.passwordfile="/etc/opt/SUNWics5/config/icspassword.conf"

Do not change this configuration parameter.

Due to this change, the following configuration parameters have been moved out of the ics.conf file:

  • local.authldapbindcred
  • local.enduseradmincred
  • local.lookupldapbindcred
  • service.siteadmin.cred
Note

The LDAP bind passwords that are generated by the configurator are re-generated each time you run the configurator, once they are moved out of the ics.conf file.

Support in Calendar Server for Service Management Framework

Calendar Server 6.3 supports the Service Management Framework (SMF), for stopping and starting Calendar Server. For more information, see Using Service Management Framework with Calendar Server.

What's New in Convergence 1.0

Convergence is Sun's next-generation web client for email, calendar, address book, and instant messaging. It provides a rich and highly interactive user experience through compelling integration of the different communication services.

The following sections list new features available in the Convergence 1.0 initial release. Additional features are planned for release in upcoming versions.

General

  • Highly customizable user interface
  • Drag-n-drop of items, for example, dragging and dropping messages between folders
  • Drag and resize user interface panels
  • Quick/advanced search in mail
  • Localized user interface in Spanish, French, and Japanese
  • Context-sensitive actions (for some components; these will become available for additional components in future releases)

Mail

  • Typical email functionality
  • Auto-completion of email addresses
  • Rich text editing
  • Server-based mail filters
  • Mark as spam
  • Vacation/out of office messages

Calendar

  • Typical calendar functionality
  • Event and task management
  • Multiple calendars and calendar overlay
  • Calendar views: day, week, month

Address Book

  • Common address book
  • Create and manage contacts
  • Import or export contacts

Instant Messaging

  • Presence management
  • Buddy list

What's New in Messaging Server 7.0

Messaging Server 7.0 includes the following changes and new features:

Messenger Express Interface Removed

The Messenger Express GUI has been deprecated and is being removed from the Messaging Server 7.0 release. For an in-place upgrade to Messaging Server 7.0, the installation process removes the existing, pre-Messaging Server 7.0 Messaging Express files, and saves the files in a backup directory. If you upgrade to Messaging Server 7.0 and then downgrade to a previous release, the downgrade process does not automatically restore the Messaging Express files. You would need to manually restore the Messenger Express files from the backup directory.

The default port for the mshttpd daemon (used by Messenger Express) has been changed to a well-known IANA-registered port, 8990. You also need to make a corresponding port change to your Communications Express configuration. The Messaging Server 6 release's default for the mshttpd port is 80, which is commonly used for web servers. Moving mshttpd to a different port signifies the removal of the web-page serving function of mshttpd (that is, Messenger Express).

Browsers will no longer connect to the mshttpd daemon as an HTTP web server, as mshttpd will no longer serve HTTP directed to end users, but instead will serve mail services to Convergence and Communications Express.

moveuser Support for Mail Servers That Do Not Support the NAMESPACE command.

Additional flags for the moveuser command provide support for moving user when the source mail server does not support the IMAP NAMESPACE command. See moveuser.

Messaging Server Message Store Supports Very Large Mailboxes

In Messaging Server 5 and 6, the store.idx files, which contain the message index and cache records, were limited to 2 Gbytes in size. Because of this limit on the store.idx file, the size of an actual mailbox was limited to about 1 million messages on average, depending on the header size and the complexity of the messages. Messaging Server 7.0 increases the number of messages a mailbox can contain to 4,294,967,295, creating in Messaging Server terms, a "very large" mailbox.

New configutil parameters have been added to Messaging Server to manage very large mailboxes. For more information, see Administering Very Large Mailboxes.

Message Store Maintenance Queue

In addition to support for large mailboxes, the way in which the message store purges mailboxes has changed, making the process more efficient when dealing with a large mailbox. In Messaging Server 7.0, only the index file is purged when a mailbox is expunged. The purging of cache records is deferred until the amount of expunged data has exceeded a configurable limit. In addition, the message store uses a maintenance queue to schedule mailbox purge and repair tasks. Mailbox corruptions detected by the message store are also queued for repair automatically. You use the impurge command to purge unused cache records and message files in mailboxes.

For more information, see Message Store Maintenance Queue.

Support for Lemonade Profile 1 and Future Release

Messaging Server 7.0 supports Lemonade Profile 1, defined by http://www.ietf.org/rfc/rfc4550.txt. Among other features, this includes an extension to the SMTP submission protocol for a client to indicate a future time for the message to be released for delivery. This extension permits a client to use server-based storage for a message that should be held in queue until an appointed time in the future. Clients that do not have local storage or are otherwise unable to release a message for delivery at an appointed time can leverage this functionality. In addition, you can use this functionality to send announcements to be read at the beginning of a work day, to send birthday greetings a day or so ahead, or to create a lightweight personal reminder service.

For more information, see http://www.ietf.org/rfc/rfc4865.txt. For more information on using Lemonade with Messaging Server, see Messaging Server Lemonade Profile 1 Support.

Support for BURL

Messaging Server 7.0 supports the BURL command, which extends the SMTP submission profile by adding a new command to fetch submission data from an IMAP server. This permits a mail client to inject content from an IMAP server into the SMTP infrastructure without downloading it to the client and uploading it back to the server. Thus, you could forward an email message without first downloading it to the client.

For more information, see http://www.ietf.org/rfc/rfc4468.txt.

IMAP URLAUTH Support

Messaging Server 7.0 supports the URLAUTH extension to IMAP and the IMAP URL Scheme (IMAPURL). This extension provides a means by which an IMAP client can use URLs carrying authorization to access limited message data on the IMAP server. An IMAP server that supports this extension indicates this with a capability name of "URLAUTH."

For more information, see http://www.ietf.org/rfc/rfc4467.txt.

IMAP CATENATE Support

Messaging Server 7.0 supports the CATENATE extension to IMAP, which extends the APPEND command to allow clients to create messages on the IMAP server that may contain a combination of new data along with parts of (or entire) messages already on the server. Using this extension, the client can catenate parts of an already existing message onto a new message without having to first download the data and then upload it back to the server.

For more information, see http://www.ietf.org/rfc/rfc4469.txt.

IMAP ANNOTATE Support

Messaging Server 7.0 supports the ANNOTATE extension to IMAP, which permits clients and servers to maintain "meta data" for messages, or individual message parts, stored in a mailbox on the server. For example, you could use IMAP ANNOTATE to attach comments and other useful information to a message, or to attach annotations to specific parts of a message, marking them as seen or important, or a comment added.

For more information, see http://www.ietf.org/rfc/rfc5257.txt.

Message Store Database Rolling Backup

The message store has been enhanced to continuously recover archived log files into an up-to-date backup copy of the message store database. If the actual database becomes unusable, then the message store will automatically use this backup database. Having an up-to-date database backup provides the next level of recovery and stability for the message store.

Messaging Server and Service Tags

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. Messaging Server 7.0 enables you to use the Service Tag Facility on Solaris OS 10.

For more information, see Using Service Tags with Messaging Server.

Additional Support for Java Enterprise System Monitoring Framework

Additional integration of Messaging Server and Java Enterprise System Monitoring Framework (JESMF) has been added to this release. JESMF provides information on the length of time for authentication, message delivery, the number of instant messages sent through the service, and other statistics.

For information on the Sun Java Enterprise System Monitoring Framework, see: Sun Java Enterprise System 5 Monitoring Guide.

Support in Messaging Server for Service Management Framework

Messaging Server 7.0 supports the Service Management Framework (SMF), for stopping and starting Messaging Server. For more information, see Using Service Management Framework with Messaging Server.

Remote Administration

The self-contained remote administration shell (via the msgadm command) in Messaging Server 7.0 is intended to make management more appliance-like. For more information, see Administering Messaging Server Remotely.

Message Store Load Throttling

Occasionally, the message store DB experiences contention related performance issues when under very heavy activity. To ensure a graceful degradation of store performance under increased load, Messaging Server 7.0 throttles DB load based on a new contention metric. This metric is used to throttle (shrink pool) or accelerate (grow pool) DB operations to an optional DB load metric value. Note that storage I/O bandwidth is another contended resource that might require throttling. Messaging Server 6.3 already throttles, based on storage capacity.

Moving Messaging Server Users From One Mailhost to Another

The rehostuser utility enables you to move a Messaging Server user's mail from one mailhost or partition to another.

Message Store reconstruct Command Revised

The message store reconstruct command has been modified to handle new file formats in Messaging Server 7.0. In addition, changes have been made to reconstruct to address multiple CRs and RFEs, as well as how to perform to repair and recovery.

The reconstruct command was originally designed to address folders and users in a breadth first manner, one database at a time. (This approach got the message store running, but each user was not completely repaired.) Today, the store's self-repair techniques can already get the store running. Thus, it is now more appropriate for reconstruct to also have the capability to address a single user completely. This approach also moves towards automatic and complete repair of individual users.

imcheck Enhancements

The following options have been added to the imcheck command:

  • Print database statistics:

    imcheck -s subsystem...

    where subsystem is: mpool, lock, log, or txn

    If subsystem is not specified, all available information is printed.
  • Print mailbox data:

    imcheck -x dir

    -x dir prints metadata for the mailbox under the specified directory.
  • Print maintenance queue:

    imcheck -q

Delivering Bulk Mail to All Users

The deliver command has been enhanced to include a -p option to specify a user ID pattern. For example, to deliver a message to all users in the message store, use this command:

deliver -p "*" < msg_file

For more information on the deliver command, see Sun Java System Messaging Server 6.3 Administration Reference.

Restoring Mailboxes to a Specific Partition

The following -P partition option has been added to the imsrestore command, to specify the restored partition.

-P partition Restores all mailboxes to the specified partition (ignore -p and mailMessageStore)

Compact WMAP

Messaging Server JavaScript client code has been improved and optimized. This results in bandwidth savings, simpler code, and better client responsiveness.

Changes to the configutil Command

The initial configuration utility no longer generates initial settings for most configutil options. Running the configutil command with no arguments lists all options with settings (initial or otherwise). Due to the reduced number of initial settings, configutil with no arguments now lists far fewer options than in the past. The configutil -H command lists all documented configutil options along with their default and current values. The configutil -o command now returns either the current value, or if no value is currently set, the default value.

The following configutil parameter defaults have changed from Messaging Server 6.3. For more information, see configutil Parameters.

local.mfagent.connection_stats_interval Set how often, in seconds, to refresh the connection statistics.
local.mfagent.debug Set a bit mask for various types of debugging in the mfagent.
local.mfagent.host_stats_interval Set how often, in seconds, to refresh the hosts statistics.
local.mfagent.listenaddr Sets the bind address for the mfagent.
local.mfagent.max_report_hosts Sets the maximum number of hosts to be reported on for channel queues. Do not set higher than 12.
local.mfagent.monitor_level Sets the level of transaction monitoring. The range is 0 (least) to 7 (most).
local.mfagent.oldest_message_update Sets the frequency of updating the oldest message info. the oldest message info is updated every nth time the connection stats are updated, n being this parameter.
local.mfagent.port Sets the port on which the mfagent listens.
local.mfagent.secret The shared secret used to authenticate connections to the mfagent.
local.mfagent.timeout Timeout for how long components will try to connect to the mfagent.
local.purge.enable Enable purge server on start-msg startup.
local.schedule.snapshot imdbverify snapshot and verify, enabled with local.schedule.snapshot.enable. imdbverify will take a snapshot backup copy of the database and verify it for use during automatic recovery.
local.schedule.snapshot.enable Whether the snapshot / verify task should be scheduled.
local.store.deadlockaggressive A non zero integer N indicates aggressive deadlock resolution, combined by delaying transaction retries by N seconds.
local.store.rollingdbbackup Controls whether rolling store database backups are made. (yes/no).
logfile.tcp_lmtp_service.buffersize Size of LMTP log buffers in bytes.
logfile.tcp_lmtp_service.expirytime Maximum time an LMTP log file is kept (in seconds).
logfile.tcp_lmtp_service.flushinterval Time interval for flushing buffers to LMTP log files (in seconds).
logfile.tcp_lmtp_service.logdir Directory path for LMTP log files.
logfile.tcp_lmtp_service.loglevel Specify an LMTP log level. One of Nolog, Emergency, Alert, Critical, Error, Warning, Notice, Information, or Debug.
logfile.tcp_lmtp_service.logtype Ignored. Set to either NscpLog or syslog.
logfile.tcp_lmtp_service.maxlogfiles Maximum number of LMTP log files.
logfile.tcp_lmtp_service.maxlogfilesize Maximum size (bytes) of each LMTP log file.
logfile.tcp_lmtp_service.maxlogsize Maximum size of all LMTP log files.
logfile.tcp_lmtp_service.minfreediskspace Minimum amount of free disk space (bytes) that must be available for LMTP logging.
logfile.tcp_lmtp_service.rollovertime The frequency in which to rotate the LMTP log file (in seconds).
logfile.tcp_lmtp_service.syslogfacility Specifies whether or not LMTP logging goes to syslog. The values can be user, mail, daemon, local0 to local7, or none. If the value is set, messages are logged to the syslog facility corresponding to the set value and all other log file service options are ignored.
service.http.smtptls Whether to use TLS for SMTP connections.
service.imap.ensidle If set, use ENS for imkill without idle, if unset, use JMQ.
service.imap.idle Sets values for local.store.notifyplugin and local.store.notifyplugin.*.*.enable for IMAP IDLE to work.
service.imap.submituser Store userid used by the MTA when resolving submit IMAP URLs in BURL commands.
service.imap.withinresolution Interval (in minutes) between recalculations of Contexts involving the search options YOUNGER or OLDER. The value 0 means 30 seconds.
service.imap.capability.acl Advertise the ACL imap extension.
service.imap.capability.annotate Advertise the ANNOTATE-EXPERIMENT-1 imap extension.
service.imap.capability.binary Advertise the BINARY imap extension.
service.imap.capability.catenate Advertise the CATENATE imap extension.
service.imap.capability.children Advertise the CHILDREN imap extension.
service.imap.capability.context Advertise the CONTEXT imap extension.
service.imap.capability.esearch Advertise the ESEARCH imap extension.
service.imap.capability.idle Advertise the IDLE imap extension.
service.imap.capability.imap4 When set to yes, advertise the IMAP4 capability. The default is yes if local.obsoleteimap is set.
service.imap.capability.imap4rev1 When set to yes, advertise the IMAP4rev1 capability. The default is yes if local.obsoleteimap is set.
service.imap.capability.language Advertise the LANGUAGE imap extension.
service.imap.capability.literal_plus Advertise the LITERAL+ imap extension.
service.imap.capability.namespace Advertise the NAMESPACE imap extension.
service.imap.capability.qresync Advertise the QRESYNC imap extension.
service.imap.capability.quota Advertise the QUOTA imap extension.
service.imap.capability.sort Advertise the SORT imap extension.
service.imap.capability.starttls Advertise the STARTTLS imap extension.
service.imap.capability.thread_references Advertise the THREAD=REFERENCES imap extension.
service.imap.capability.thread_subject Advertise the THREAD=ORDEREDSUBJECT imap extension.
service.imap.capability.uidplus Advertise the UIDPLUS imap extension.
service.imap.capability.unselect Advertise the UNSELECT imap extension.
service.imap.capability.urlauth Advertise the URLAUTH imap extension.
service.imap.capability.within Advertise the WITHIN imap extension.
service.imap.capability.x_annotatemore Advertise the X-ANNOTATEMORE imap extension.
service.imap.capability.x_netscape Advertise the X-NETSCAPE imap extension.
service.imap.capability.x_sun_imap Advertise the X-SUN-IMAP imap extension.
service.imap.capability.x_sun_sort Advertise the X-SUN-SORT imap extension.
service.imap.capability.x_unauthenticate Advertise the X-UNAUTHENTICATE imap extension.
service.imap.capability.xrefresh Advertise the XREFRESH imap extension.
service.imap.capability.xsender Advertise the XSENDER imap extension.
service.imap.capability.xserverinfo Advertise the XSERVERINFO imap extension.
service.imap.capability.xum1 Advertise the XUM1 imap extension.
service.imap.idle.jmqhost The name or address of the host where the JMQ broker is to be found.
service.imap.idle.jmqpassword The JMQ password used to subscribe to messaging events.
service.imap.idle.jmqport The port number the JMQ broker is listening on.
service.imap.idle.jmqtopic The JMQ topic to which mail events are published.
service.imap.idle.jmquserid The JMQ userid used to subscribe to messaging events.
store.autorepair Repair damaged mailboxes automatically.
store.mailboxexpungesize Size (in bytes) of expired or expunged message before purge will permanently remove it. Minimum value is 1048576.
store.maxcachefilesize Maximum cache file size (in bytes). A new cache file is created when the current cache file size has exceeded this limit. Minimum value is 1048576.
store.purge.loglevel Specify a log level: 0: no log. 1: basic log. 2: verbose log.
store.purge.maxthreads Maximum number of threads.
Parameter 6.3 Default 7.0 Default
local.autorestart no yes
local.ens.enable <ensEnable> 0
local.store.listrecover NULL TestPartitionInsertFull
service.http.port 80 8990
service.http.sslport 443 8991

Running configutil -h displays two new options (-x and -a). These options are for a future enhancement that is not active for Messaging Server 7.0. These options do not affect the current configuration other than to issue a warning that they are ignored.

Sieve Filter Implementation

See http://msg.wikidoc.info/index.php/Sieve_Implementation.

Vacation Replies Can Be Sent to Forwarded Messages

Messaging Server 7.0 can now generate :addresses arguments to Sieve vacation using an LDAP autoreply attribute. The new MTA option LDAP_AUTOREPLY_ADDRESSES provides the name of the attribute to use. This option has no value by default. The attribute can be multivalued, with each value specifying a separate address to pass to the :addresses vacation parameter. The :addresses argument to Sieve vacation specifies other addresses which will be deemed to be the the same as the recipient. This allows vacation autoreply to be sent even when none of the header recipient addresses of the message match any valid address of the user. The attribute will need to be added to the directory server schema, this option specified in option.dat, and the attribute values added to users LDAP objects.

Changes to the nameservers channel keyword

When nameserver lookups are being performed, that is, unless the nsswitch.conf file selects no use of nameservers, then prior to Messaging Server 7.0 the nameservers channel keyword may be used to specify a list of nameservers to consult rather than consulting the TCP/IP stack's own choice of nameservers. This would affect the SMTP server and client and LMTP client, but not the LMTP server (which, if it needs to do any lookups, always relies on the TCP/IP stack's own choice of nameservers). Furthermore, as of Messaging Server 7.0, the nameservers keyword only affects MX record lookups, with all other lookups using the TCP/IP stack's choice of nameservers regardless of any nameservers keyword setting.

What's New in Instant Messaging 7.3

Instant Messaging 7.3 includes the following changes and new features:

Support for LDAP Failover

Support for LDAP failover in Instant Messaging 7.3 enables you to configure the Instant Messaging server to have multiple LDAP servers as back-end storage. If one LDAP server becomes unavailable, the Instant Messaging server is then able to fail over to another LDAP server.

LDAP failover works on a multi-master replication setup of LDAP servers. All the LDAP servers in the settings are masters and have permission to read and write data. The Instant Messaging server uses only one server at a time but fails over to another LDAP server when the current server becomes unavailable. The other LDAP server is expected to be in sync with the current server as far as data is concerned.

For more information, see the Sun Java System Instant Messaging Administration Guide.

Support for Voice Chat and Client-to-Client Chat

The previous releases of Instant Messaging did not have any audio capability. Instant Messaging 7.3 provides the capability for Instant Messaging users to talk to each other using PC-based audio hardware. The Instant Messaging client uses the Instant Messaging Server to only set up the call. Afterwards, the audio streams travel in a peer-to-peer fashion.

To enable voice chat, select the "Enable Audio" checkbox when deploying the Instant Messaging Client Resources.

For more information, see Configuring the Voice Chat.

Support for Instant Messaging and Presence Service Protocol

Instant Messaging 7.3 supports Instant Messaging and Presence Service (IMPS) protocol, which enables mobile instant messaging and presence services. You use IMPS to exchange messages and presence information between mobile devices, mobile services and Internet-based instant messaging services. IMPS access is provided via a web-application in the Instant Messaging server. The IMPS web-application can be deployed to a supported web container using the Instant Messaging configuration utility.

For more information, see the Sun Java System Instant Messaging Administration Guide.

Support for Service Management Framework

Instant Messaging 7.3 supports the Service Management Framework (SMF), for stopping and starting Instant Messaging. On supported platforms, an SMF service is registered when you install Instant Messaging server. You can use either the svcadm command or the Instant Messaging imadmin utility to start and stop Instant Messaging processes.

Side-by-side Upgrade Capability

Instant Messaging 7.3 enables you to perform a side-by-side upgrade. That is, the upgrade process supports a coexistence approach on the host being upgraded.

Hosted Domain Support with Schema 1 and Schema 2

Instant Messaging 7.3 enables support for hosted domain using LDAP specific tree without using Identity.

For more information, see the Sun Java System Instant Messaging Administration Guide.

Java Messaging Service Support for Calendar Server Alerts

Instant Messaging 7.3 uses Java Message Queue as the calendar agent for calendar reminders. In previous releases, the calendar agent was using ENS, which will be deprecated in a future release.

For more information, see the Sun Java System Instant Messaging Administration Guide.

Property Store Migration

Instant Messaging 7.3 provides property store migration that enables migration to and from the file propstore and from and to the LDAP propstore. The destination store must have the appropriate entries users configured. This migration does not create users; it only migrates the user data. It currently does not support mixed case entries, and flags them as errors.

For more information, see the Sun Java System Instant Messaging Administration Guide.

Support for the migratecert Command

Instant Messaging 7.3 enables migration of private key and Multiplexor certificate from the NSS database to JKS. A migration utility has been added for this purpose in the imadmin command.

Instant Messaging 7.3 no longer supports SSL through the Multiplexor using NSS-based certificates, however, you can now migrate the existing certificates from NSS store to JKS using the migratecert command.

For more information, see the Sun Java System Instant Messaging Administration Guide.

What's New in Delegated Administrator 6.4

The Delegated Administrator 6.4 released with Communications Suite 6 does not include any new features since the release of Delegated Administrator 6.4 with Communications Suite 5. See Problems Fixed in This Release of Delegated Administrator for a list of fixes to this release.

The following minor features were introduced in Delegated Administrator 6.4 with the Communications Suite 6 release:

The following new features were introduced in Delegated Administrator 6.4 with the Communications Suite 5 release:

Support for Calendar Groups

Delegated Administrator supports provisioning of calendar groups.

You can use Delegated Administrator to assign calendar service to a group. When the group is first invited to an event, Calendar Server creates a group calendar shared by the users who are members of the group. Invitations to the group appear on the group calendar and on the calendars of the individual members.

The following features implement support for calendar groups:

  • In the console, you can assign service packages with calendar service to groups. In the Create Group wizard, a Calendar Service Details panel allows you to specify Calendar attributes for the group. Calendar service details can be modified in the group properties page.

Web Server 7.x Deployment

Delegated Administrator can be deployed to Sun Java System Web Server 7.x.

When you run the configuration program, config-commda, you can configure the Delegated Administrator server and console to be deployed to Web Server 7.x.

Access to Instant Messaging

Users created in Delegated Administrator will have access to Instant Messaging (IM) service if IM is deployed on your site. Users are automatically assigned basic IM service during user creation.

You must use the Access Manager console to set and manage IM user-access levels. In this release of Delegated Administrator, the Delegated Administrator console does not provide access to IM service and does not provide an interface for managing IM user-access levels.

Debug Log Command for the Delegated Administrator Server

In the command-line utility, the commadmin debug log command creates a Delegated Administrator server log that contains debug statements generated by the Delegated Administrator servlets installed on the Web container. See commadmin debug log

The commadmin debug log command supersedes the use of the url to enable logging for the Delegated Administrator server. The url used in previous releases can no longer be used for this purpose.

What's New in Communications Express 6.3

Communications Express 6.3 does not include any new features. See Problems Fixed in This Release of Communications Express for a list of fixes to this release.

What's New in Connector for Outlook 7.3

Connector for Outlook 7.3 includes the following changes and new features:

Support for Large PST Files

Connector for Outlook 7.3 supports a larger PST file (20 Gbytes), which was introduced in Microsoft Outlook 2003. In the past, the PST file was limited to 2 Gbytes of data. Users using Microsoft Outlook 2003 and Microsoft Outlook 2007 will now use the large PST file as their local store for Connector for Outlook.

Service Tags and Connector for Outlook

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. For more information, see http://servicetags.central.

Support for Outlook 2007

Connector for Outlook 7.3 now supports Microsoft Outlook 2007.

Support for Microsoft Vista

Connector for Outlook 7.3 now supports Microsoft's Windows Vista operating system.

Ability to Disable Save Password Field

Connector for Outlook 7.3 now supports a security feature that enables administrators to restrict users from saving their passwords in profile.

New Deployment Tool Path

To conform with Sun's products installation paths, Connector for Outlook deployment tool now uses the following path:

Start \-> Programs \-> Sun Microsystems \-> Sun Java System Connector Deployment

Customizing the Location of the Personal Store (.pst) File

By default, Connector for Outlook 7.3 stores pst files at C:\Documents and Settings_username_\Local Settings\Sun\Outlook Connector. This feature enables administrators to decide the location of pst files on a user's machine.

Polling in Address Book

Connector for Outlook 7.3 enables you to set an option to run polling at certain time intervals. This feature ensures you keep your address book updated without any manual intervention.

Ability to Customize LDAP Attribute Mapping and GAL Display Order

Outlook Connector maps the LDAP attributes to the corresponding display items in Outlook. You can now customize the LDAP attribute mapping and GAL display order from the Deployment Program.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (18)

 

  1. Jan 23, 2008

    SwethaRaj says:

    Few new features are missing with Instant Messaging,please add this, Virtual do...

    Few new features are missing with Instant Messaging,please add this,

    Virtual domain support with schema1 and schema2
    JMS support for calendar alerts
    Propstore Migration

    Also the details of configuring and setting up of all new features is missing,that should be updated

    1. Jan 25, 2008

      joesciallo says:

      Added placedholders for these topics. Please supply more information or pointer ...

      Added placedholders for these topics. Please supply more information or pointer to information you have.

  2. Jan 30, 2008

    magsd says:

    Nothing on SMF for me to review : "Support in Messaging Server for Solaris Manag...

    Nothing on SMF for me to review :
    "Support in Messaging Server for Solaris Management Framework

    Messaging Server 7.0 supports the Solaris Management Framework, for stopping and starting Messaging Server. For more information, see xref TBD."

    1. Jan 31, 2008

      joesciallo says:

      magsd - we should have more info at some point. Will let you know when.

      magsd - we should have more info at some point. Will let you know when.

      1. Apr 10, 2008

        shjorth_sun says:

        I wrote up a guide for calendar server & SMF here (per a request from a beta...

        I wrote up a guide for calendar server & SMF here (per a request from a beta customer):

        http://wikis.sun.com/display/CommSuite/Using+Service+Management+Framework+with+Calendar+Server

        I have also updated the messaging server SMF guide here:

        http://wikis.sun.com/display/CommSuite/Using+Service+Management+Framework+with+Messaging+Server

        Feel free to link these guides. We seem to also be missing a generic 'SMF with Comm-Suite' guide which could include a "troubleshooting SMF" guide, quick-guide on enabling SMF with directory server/app-server/web-server/IM server etc. so that all comm-suite and dependant products use SMF instead of /etc/init.d style scripts.

        If you want me to write something up please advise.

        Shane.

        1. Apr 11, 2008

          joesciallo says:

          Thanks Shane. Great work. Your suggestion for a Comms-wide guide makes sense. Wo...

          Thanks Shane. Great work. Your suggestion for a Comms-wide guide makes sense. Wonder how much is out there already from the other products that could just be linked to from one page.

          Joe

  3. Feb 26, 2008

    SwethaRaj says:

    "What's New" section for Instant Messaging is not complete,it still doesn't incl...

    "What's New" section for Instant Messaging is not complete,it still doesn't include any steps for configuring new features.

    Only VOIP as the configuration steps.The same should be updated for the other new features

    1. Feb 26, 2008

      joesciallo says:

      Purpose of the What's New is not to document how to configure, at least not in d...

      Purpose of the What's New is not to document how to configure, at least not in depth. That info needs to reside in an Admin Guide (or Admin pages on the wiki). We'll be constructing said guide/pages for IM going forward.

  4. Feb 27, 2008

    prakpa says:

    Since betarefresh is going to the customer and there should be information on ho...

    Since betarefresh is going to the customer and there should be information on how to configure the new features. There are extra config need to done for some of the features like imps etc..etc

    1. Feb 28, 2008

      joesciallo says:

      We are in the process of developing the IM admin information for these features.

      We are in the process of developing the IM admin information for these features.

  5. Mar 04, 2008

    SwethaRaj says:

    Doc on how to migrate cert is still missing

    Doc on how to migrate cert is still missing

  6. Mar 18, 2008

    mikelcu says:

    This looks great, but is this the release for 2008? Where are CalDAV , SyncML a...

    This looks great, but is this the release for 2008? Where are CalDAV , SyncML and some of the other rumored features...

    http://blogs.sun.com/jpblog/entry/communicate_suites_the_new_client

    1. Mar 18, 2008

      joesciallo says:

      The upcoming Comms 6 release (set for Q2 2008) will have a number of the feature...

      The upcoming Comms 6 release (set for Q2 2008) will have a number of the features that JimP's post mentioned.

      re: CalDAV and SyncML, I'm researching those features to see when you can expect them. Stay tuned.

  7. May 09, 2008

    SwethaRaj says:

    Kindly add this "SSL through multiplexor using NSS based certificates is no long...

    Kindly add this "SSL through multiplexor using NSS based certificates is no longer supported,but the existing certificates can now be migrated from NSS store to JKS using the migratecert utility" in "Support for migratecert Command-line Interface" section of IM - What's New

    1. May 09, 2008

      joesciallo says:

      Done.

      Done.

  8. May 10, 2008

    philkime says:

    Any news on CalDAV support? This is the one feature that I was waiting for.

    Any news on CalDAV support? This is the one feature that I was waiting for.

    1. May 12, 2008

      JAllison says:

      We're doing a CalDAV-based calendar server, so I would assume (dangerous) that O...

      We're doing a CalDAV-based calendar server, so I would assume (dangerous) that Outlook Connector will support CalDAV when that server is released. Current plan calls for the CalDAV-based server in Q1 of 2009.

  9. Dec 18, 2008

    Esther_Aguero says:

    The doc -http://docs.sun.com/source/816-6708-10/csag6.html#wp25013- indicates th...

    The doc -http://docs.sun.com/source/816-6708-10/csag6.html#wp25013- indicates the following:

    • - -
      To restore a specific calendar from a database that was saved to a backup directory using the csbackup utility, use the csrestore utility database command with the -c option.
    • - -
      But doc doesn't say anything about backup saved with Hot Backup or Archival Backup whereas this procedure is applicable to backup saved both Hot Backup and Archival Backup too. We have verified that using a backup saved with Hot Backup or Archival Backup and applying csrestore tool to restore a specific calendar works fine:

    csrestore -c <usercal> calendar <backupdir>

    The doc should say that backupdir can be any backup saved with csbackup utility,
    with Hot Backup or with Archival Backup.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact