This document summarizes the features in Oracle Communications Unified Communications Suite 7 Update 1 that are new or have been enhanced since Sun Java Communications Suite 7 was originally distributed in September 29, 2009, for the following components:
|Oracle Communications Messaging Exchange Server||7 Update 4|
|Oracle Communications Instant Messaging Server||8 Update 3|
|Oracle Communications Calendar Server for CALDAV Clients||7 Update 1|
|Delegated Administrator for Oracle Communications Unified Communications Suite||7 (latest patch)|
|Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite||7.3 Update 1 (latest patch)|
|Oracle Communications Calendar Server||6.3 (latest patch)|
|Indexing and Search Service for Oracle Communications Unified Communications Suite||1 Update 1|
|Sun Java System Communications Sync||Removed|
|Messaging Server HA Agent (MS_SCHA)||7|
|Calendar Server HA Agent (CS_SCHA)||6.3|
|Instant Messaging HA Agent (IM_SCHA)||7.3|
|Dssetup for Oracle Communications Unified Communications Suite (comm_dssetup)||6.4 (latest patch)|
This document contains the following sections:
- What's New in Communications Suite 7 Update 1
- What's New in Convergence 2
- What's New in Messaging Server 7 Update 4
- What's New in Calendar Server 7 Update 1
- What's New in Calendar Server 6.3
- What's New in Indexing and Search Service 1 Update 1
- What's New in Instant Messaging 8 Update 3
- What's New in Delegated Administrator 7
- What's New in Connector for Outlook 7.3 Update 1
- What's New in DSsetup 6.4p6
Communications Suite 7 Update 1 includes the following changes and new features:
If you choose to upgrade to Communications Suite 7 Update 1, see Communications Suite Upgrade Guide.
Certificate-based authentication is a new feature available in Oracle Communications Calendar Server, Convergence, and Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite.
Messaging Server has supported client certificate authentication since before version 5.2. This version of Messaging Server supports dynamic Certificate Revocation Lists (CRL) updates. The dynamic CRL updates feature is available as a set of patches that you can apply to Messaging Server 7 update 3. See Certificate Based Authentication for Messaging Server.
In previous releases, if the Communications Suite installer listed Oracle GlassFish Message Queue as a component to be upgraded, you needed to redo the configuration in your /etc/imq/imqbrokerd.conf file after the upgrade. This is no longer required, because now the Message Queue configuration is automatically retained during an upgrade.
Convergence 2 includes the following changes and new features:
- Customization Enhancements
- Calendar Server 7 Update 1 Support
- Dojo Port
- Improvements to Attachment Search and View
- Certificate-based Authentication
- Proxy Authentication Support
- New Icon Toolbars
- Create New Folder While Selecting Folder
- Schedule Calendar Resources
- New Calendar Event and Task Types
- Calendar print functionality in daily and weekly views has changed between Convergence 1.x and Convergence 2
- Check Box Next to Email in Message List
- Enabling and Disabling Message Preview
- Multi-user Chat
- Instant Messaging Conversations in Tabs
- Address Book Enhancements
To customize Convergence, be sure to install Convergence 2 Patch 1, which is now available. With the patch you are able to modify:
- the UI
To customize your Convergence UI, refer to Convergence Customization Guide.
While you were able to customize themes in Convergence 2, the method for theme customization has been modified in Convergence 2 Patch 1. If you have either already customized themes in Convergence 2, or you have yet to customize your themes, refer to the instructions in [CommSuite: Customizing Themes and Banner in Convergence 2].
In this release, themes have significantly changed. In addition, you no longer need to modify CSS files for basic customization, making the process more streamlined. For example, refer to the updated reference information for theme.json, the customization file for storing theme customizations.
Because of the differences between Convergence 1.x and Convergence 2 customizations, you cannot retain your Convergence 1.x when you upgrading to Convergence 2. Instead, you must recreate your customization in Convergence 2 following the steps described in [CommSuite: Customizing Themes and Banner in Convergence 2]. Upgrading from Convergence 2 is more straightforward: you can retain the customization information in the c11n directory. However, if in future releases, new variables are added to the dojo template file or to specific themes, you will need to add those values to your theme.json files as well as any new images.
To customize themes, see the newly updated [CommSuite: Customizing Themes and Banner in Convergence 2].
Support for an updated Web Calendar Access Protocol (WCAP) version 7.0 enables Calendar Server 7 Update 1 and Convergence integration. In the Convergence UI, Share Calendar and Privacy Settings can access either Calendar Server 6.3 or Calendar Server 7 Update 1 without client setting or option modifications.
To enable Calendar Server 7 Update 1 Support, see Enabling Calendar Server 7 Update 1 Support.
In this release, the Dojo version in the product was upgraded from .9 to 1.3.2.
See http://docs.dojocampus.org/ for Dojo documentation.
The attachment folder search allows users to find attachments in their mailbox. To enable attachment folder search, Indexing and Search Service (ISS) must also be enabled. The folder search interface has an icon style grid containing all the attachments from a user's mailbox. By selecting attachments, the end user can perform actions on the item. Additionally, the user can narrow down attachments by specific criteria with Filtering options.
To enable Attachment Search and View, see Enabling Indexing and Search Service.
Certificate-based authentication was introduced to enable end user authentication in Convergence. See Setting Up Certificate-based Authentication.
You can enable Proxy Authentication support in Convergence. See Configuring Convergence for Proxy Authentication.
New toolbars were created which contain icons for the following common Convergence tasks:
- Common icons (found above each component's toolbar): New Mail, New Event, New Task, and New Contact
- Address Book: New Address Book, New Contact, New Group, Rename Personal Address Book Group, Delete Group/Contact, and Import/Export Group/Contact
- Calendar: Create or Subscribe to Calendar, Calendar Properties, Delete or Unsubscribe Calendar, Toggle Mini Calendar, and Import/Export Calendar
- Mail: Create or Subscribe to a Folder, Folder Properties or Sharing, Rename Folder, and Delete Folder
End users can create new folders in the mail folder selection dialog. New folder functionality in mail folder selection occurs in the following locations:
- General Tab
- Copying Sent Messages
- Deleting Mail Messages
- Saving Drafts
- Mail Filters Tab
- Move message to and copy message to drop down
- New Account Tab
- POP account folder that collects messages
In addition to modifying the field organization and spacing in the New Event form, end users can schedule resources with a separate search field and text box for resource look-up. People and resources are invited separately from one another.
When end users create new events or tasks, they can mark events and tasks as public, private, or displaying only date and time. They can also select the type of event or task from a number of categories such as Business, Conference Call, Seminar, Personal, and so on.
Calendar print functionality in daily and weekly views has changed between Convergence 1.x and Convergence 2
If you print daily or weekly calendars, they print as an agenda-style format instead of a grid-style format. The agenda-style calendar is better at showing the details of an event, particularly when there are multiple events or overlapping events in a single day.
If you choose to print a month view calendar, it prints in a grid-style format.
You are still able to view daily and weekly calendars in Convergence in both grid-style as well as agenda-style formats.
Check boxes have been added to the message list in the mail window.
An end user can change preferences in Options to hide the preview pane in the message list. By default, message preview is enabled.
An administrator can also turn off the mail preview pane for all users on an entire site. This overrides any action by an end user to enable the preview pane. If the Administrator enables preview pane (the default), then the end user may override the preference to disable the preview pane.
See the mail.enablemsgpreview option for more information about enabling and disabling message preview.
Convergence 2 supports multi-user instant messaging conferences (chats). This functionality enables XMPP users to exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). Features of multi-user chat include:
- Conferencing tools, including room rosters, invitations, private conversations, and transcripts
See the online help packaged with the Convergence Client for Oracle Communications Unified Communications for information on enabling multi-user chat.
In previous versions of Convergence, Instant Messaging (IM) chats were opened in new browsers. Beginning with Convergence 2, end users can launch IM chats in different tabs within the same browser.
Beginning with this release, administrators can support multiple corporate directories. Unlike personal address books which are created by end users, corporate directories are configured by administrators. See Configuring Corporate Directories.
Additionally in this release, end users can manage multiple Personal Address Books. They can also select or delete multiple contact entries in their Personal Address Book through keyboard shortcuts and check boxes.
Messaging Server 7 Update 4 includes the following changes and new features:
- Third-Party Authentication Server Support
- Support for In-place Upgrade of 32-bit to 64-bit Messaging Server
- Support for Messaging Server 64-bit on Red Hat Linux 5
- Red Hat Linux 5 Update 3 64-bit Installation Requirements
- Sendmail Is Disabled on Solaris OS and Red Hat Linux
- IMAP IDLE Command
- ENS Security Improvements
- MeterMaid Improvements
- Sieve Date and Index Extensions
- SASL and High-Performance User Lookup and Authentication (HULA)
- Dynamic Certificate Revocation Lists (CRL) Updates
- New defragment Channel Options
- ignoremessageencoding and ignoremultipartencoding Channel Options
- LDAP Security Improvements
- Using IPv6 with Messaging Server
- Enhancements to the MTA's BURL Support
- nslog Provides Additional Log File Functionality for Dispatcher and Job Controller (CR 6185167 and CR 6191669)
- IMAP ID Command (CR 6339827)
- Support for IPv6 Data Type for MeterMaid Tables (CR 6823375)
- SMTP Server Rejects STARTTLS When Followed by Additional Commands
- MTA and MMP Minor Features
Beginning with version 7 Update 4 Patch 22, Messaging Server now provides support for third-party authentication servers by supporting a protocol designed to integrate third-party authentication services. For more information, see: Third-Party Authentication Server Support.
You can now do an in-place upgrade from 32-bit to 64-bit Messaging Server using commpkg upgrade. Previous versions of commpkg upgrade did not provide this option.
You can now upgrade a Red Hat Linux 5 installation to a more scalable 64-bit implementation. However, the Message Queue (MQ) library is not yet available for Red Hat Linux 5 64-bit, so Red Hat Linux 64-bit is not compatible with Indexing and Search Service for Oracle Communications Unified Communications Suite nor with other uses of Java MQ notifications. However, the Messaging Server's event notification system (ENS) is fully supported on this platform. Until a 64-bit version of MQ is available on Red Hat Linux 5, you can deploy on the Solaris operating system (OS), which is now 64-bit only, or you can use the deprecated Red Hat Linux 32-bit version of Messaging Server if Indexing and Search Service or Java MQ support is required.
Because it uses the default installation cluster for Red Hat Linux 5 Update 3 64-bit, Messaging Server does not require any additional RPMs to run. The %packages section of the kickstart file (anaconda-ks.cfg) for the default installation is as follows:
When you run configure, you are now informed that sendmail is disabled. This functionality can be disabled if you use the --ignoreSendmail option when running configure.
This version of Messaging Server enables IMAP IDLE by default, using the Event Notification Service (ENS). No configuration is required. In addition, IMAP IDLE now only works using ENS, because the ability to use IMAP IDLE with JMQ has been removed. For existing installations, customers should, at a minimum, ensure that the ENS server is enabled by setting the configutil parameter local.ens.enable to 1 and restarting the Messaging Server:
The following configutil parameters are now marked OBSOLETE and are no longer valid:
Customers may remove these obsolete parameters from their configuration, although the only impact is to maintain a clean configuration.
Options can be removed by using the -d switch with configutil. For example:
Customers who do not use ENS or JMQ for external notification systems can also delete local.store.notifyplugin, because an appropriate default value is now configured.
The new ENS server now supports two options to control TCP access to the ENS server (service.ens.domainallowed and service.ens.domainnotallowed). These options work the same way as the equivalent options for POP, IMAP, and HTTP. These options replace the functionality of the ENS_ACCESS environment variable that was included in the legacy ENS server.
MeterMaid has been enhanced to offer Greylisting support. Greylisting is a technique that you can use to help Messaging Server reduce spam. See Implementing Greylisting by Using MeterMaid for more information.
The Sieve Date and Index extensions RFC 5260 are now fully supported. See also Features Introduced in Messaging Server 7 Update 4 for other changes to sieve handling.
Messaging Server no longer depends on a Sun-private fork of CMU libsasl (SUNWsasl package) for authentication services. The entire Messaging Server product now uses the modern HULA library that has been used by the MMP for several releases for authentication. This change will enable faster implementation of consistent authentication-related features in the future, as well as some behavior changes:
- Improved logging and error text for authentication and authorization failures.
- After a user's password changes, authentication with the new password works immediately.
- The new option to simplify SMTP configuration that requires SSL/TLS prior to password login, service.smtp.plaintextmincipher, works like service.imap.plaintextmincipher).
- The new option for HTTP proxy authentication to IMAP server, local.http.replayformat, works like the MMP's replayformat setting. This enables configurations where the internal UID is not used for login 6404489.
- DIGEST-MD5, which was deprecated for several releases, has been removed.
- The undocumented backwards compatibility for PMDF's security.cnf was removed to make it easier to identify configuration errors. Equivalent functionality is provided with sasl.* configutil settings.
- The undocumented backward compatibility for the SIMS 4.0 inetSubscriberStatus and inetAuthorizedServices attributes was removed to simplify access control (these attributes are now ignored). The inetUserStatus, mailDomainAllowedServiceAccess, and mailAllowedServiceAccess attributes provide equivalent functionality.
- The undocumented backward compatibility for the NMS 4.x nsmsgDisallowAccess and mailAccessDomain attributes was removed to simplify access control (these attributes are now ignored). The mailDomainAllowedServiceAccess and mailAllowedServiceAccess attributes provide equivalent functionality.
- Support for the POP3 AUTH command with no arguments to list authentication mechanisms (a feature replaced by the POP3 CAPA command in RFC 2449, published in 1998) was removed to enable simpler support for new authentication mechanisms.
Messaging Server has supported client certificate authentication since before version 5.2. This version of Messaging Server supports dynamic Certificate Revocation Lists (CRL) updates. The dynamic CRL updates is available as a set of patches that you can apply to Messaging Server 7 Update 3.
The defragment channel now has a channel option called MAX_PARTS. MAX_PARTS determines the maximum number of parts that a message can have and still be reassembled. The maximum is 100,000; the default is 1000.
The ignoremessageencoding and ignoremultipartencoding channel options now affect MIME processing done by the conversion, SMS, calendar, and user-written channels.
To improve product security, the LDAP SSL client (enabled by local.ugldapusessl) now validates the LDAP server certificate by default and fails if the server's certificate cannot be validated. Use configutil -o local.ldapcheckcert -v 0 to turn off LDAP SSL certificate validation.
The configure utility now supports LDAP SSL. This is done by including the --ssl switch when configuring LDAP. You should store the LDAP server certificate or CA as a trusted peer or CA in cert8.db (using certutil) in the directory which will be used for Messaging Server product configuration (the default location is /var/opt/sun/comms/messaging64/config).
You can use IPv6 with Messaging Server. See Using IPv6 with Messaging Server for details.
BURL has been enhanced to support additional configuration regarding its behavior. See BURL Support for SMTP SUBMIT.
nslog Provides Additional Log File Functionality for Dispatcher and Job Controller (CR 6185167 and CR 6191669)
The capability of nslog to handle log file rollover can now be used with Dispatcher and Job Controller.
To enable this functionality, set the USE_NSLOG=1 option in the beginning of the dispatcher.cnf or job_controller.cnf file. You can then set up the logfile.dispatcher.x or logfile.job_controller.x configutil options to control the various logging characteristics. This uses the additional functionality provided by the logfile configutil options, including log file rotation and expiration.
When this functionality is enabled, the Dispatcher log file is named dispatcher by default instead of dispatcher.log-x. Similarly, the Job Controller log file is named job_controller by default instead of job_controller.log-x.
The ID extension to IMAP allows the server and client to exchange identification information on their implementation to make bug reports and usage statistics more complete. IMAP ID information is logged to the imapd log file at info level. This means the client ID information is not logged unless you use configutil -o logfile.imap.loglevel -v info (or a more verbose logging level). For more information about the ID extension, see RFC 2971.
IPv6 addresses can now be used as lookup keys in MeterMaid tables when you set the metermaid.table.*.data_type configutil parameter to ipv6.
In Messaging Server 7 Update 4 Path 21, the SMTP server rejects STARTTLS if there are additional commands piggybacked on it in the stream. The purpose of this is to avoid certain attacks.
A number of smaller features were also introduced in this release. See: MTA and MMP Minor Features.
Calendar Server 7 Update 1 includes the following changes and new features:
- Support for an Updated WCAP Protocol Version 7.0
- Implicit Scheduling
- Support for CalDAV and CardDAV Autodiscovery
- Invitation of LDAP Groups
- Access Control Support
- Document Store
- Support for Resource Calendars
- Calendar Subscription Support
- Property-based Search Filtering
- Enhancements and Changes to davadmin
- WebDAVSync Enhancements
- Secure LDAP Connection
- Migration From Sun Java System Calendar Server 6.3
- Public and Private Events and Tasks Filter
Web Calendar Access Protocol (WCAP) is a command-based system consisting of client requests and server responses for transmitting calendaring data. WCAP returns calendaring data using the HTTP protocol. In most cases, Calendar Server receives data through URL-encoded arguments to the commands.
WCAP commands consist of five general categories of usage:
- Creating calendars
- Storing, retrieving, and managing calendar properties
- Storing, retrieving, and managing calendar data
- Retrieving calendar information of other users
Calendar data is always stored in Standard iCal format in the calendar database. But you can retrieve this calendar data by using WCAP commands with the fmt-out parameter set to text/calendar, text/json, or text/xml. The default format is text/calendar which outputs in standard iCal format as defined in RFC5545.
WCAP is a command-based system consisting of client requests and server responses for transmitting calendaring data. WCAP returns calendaring data using the HTTP protocol. In most cases, Calendar Server receives data through URL-encoded arguments to the commands.
WCAP enables Calendar Server 7 Update 1 and Convergence 2 integration.
For more information, see Calendar Server WCAP Developer's Guide.
Calendar Server 7 Update 1 supports implicit scheduling, in which the server has the capability to add invitations that arrive in the calendar inbox to the user's default calendar without any client intervention. This implementation is based on the latest CalDAV scheduling draft. Invitations created by using the WCAP protocol always lead to implicit scheduling. Storing an event with attendees automatically triggers invitations to all attendees.
Calendar Server 7 Update 1 supports the .well-known URI concept as defined in Locating CalDAV and CardDAV services for CalDAV clients to access the Principal URI without having to specify the entire URI. That is, access to / (root) or /.well-known/caldav/ is redirected to the /dav/principals/ URI.
Calendar Server 7 Update 1 supports the ability to invite entire groups in the LDAP directory as one attendee. The group is maintained as one attendee in the organizer's calendar, but the Scheduling Service expands the group and adds each member as a recipient of the invitation. When storing the invitation in each recipients' calendar, that recipient is added as an ATTENDEE, which is referenced as a member of the group. When a recipient replies, that recipient is added as an individual ATTENDEE, also referenced as member of the initial group in the organizer's calendar. This feature can be used to invite both static and dynamic groups in LDAP.
Calendar Server 7 Update 1 enables you to set and make use of the access control list (ACL) feature to determine access control for scheduling, calendar properties, and calendar components such as events and "todo's" (tasks). An ACL consists of one or more access control entries (ACE), which are strings that collectively apply to the same calendar or component. In this release, access control management is restricted to the WCAP and davadmin interfaces.
Calendar Server 7 Update 1 introduces the document store, which is used for storing calendar attachments. The document store can be local or remote. Essentially, the document store is file-system-based storage with a built-in web server front-end that is used by the Calendar Server to store and retrieve documents.
Calendar Server 7 Update 1 supports special handling of resource calendars. A resource in the context of scheduling is any shared entity that can be scheduled by a calendar user but does not control its own attendance status. For example, you would use a resource calendar for such items as conference rooms and video equipment. Some of the related features are auto-acceptance of invitations, declining invitations that could result in conflicting multiple bookings for the same time slot, and so on.
The davcore.autocreate.calattendantresourceflags configuration options control the settings on a new resource calendar. You change the settings for a resource by using the davadmin account command and set_accountprops WCAP command.
Calendar Server 7 Update 1 provides the capability for one user to subscribe to other users' calendars on the server and maintain a subscription list, for easy access. The ability to subscribe, list subscriptions, and unsubscribe is limited to the WCAP access for this release, since a standard CalDAV way does not yet exist.
CalDAV clients can access other calendars to which a logged-in user has access by explicitly providing the URLs.
Certain calendar properties were indexed to enable faster search based on those filters. The WCAP filter parameter of the fetch command uses this feature. See Filter Parameter for more information.
- The calresource operation has been renamed to calcomponent.
- The migration operation has been added for migration of data from Calendar Server 6.3 to Calendar Server 7.
- The account operation has been added to enable listing, deletion, and properties modification of user accounts.
- The calendar operation has been enhanced to enable setting of more calendar properties.
The WebDAVSync support was enhanced to match the latest draft. An extension to the WebDAV spec, WebDAVSync defines a protocol for HTTP clients to query an overview of the data changes on the HTTP server, enabling the clients to efficiently synchronize their local data cache with the server.
You can configure Calendar Server 7 Update 1 to communicate with Directory Server over SSL. See the necessary configuration changes as described in Oracle Communications Calendar Server for CALDAV Clients Post Configuration.
The davadmin migration command enables you to migrate Calendar Server 6.3 data to Calendar Server 7 Update 1. See Migrating From Sun Java System Calendar Server 6 to Calendar Server 7 for more information on how to perform the actual data migration.
Calendar Server supports the iCal CLASS property and behaves as follows.
When creating a new event or task, a user can specify whether the event or task is Public, Private, or Time and Date Only (confidential):
- Public. Anyone with read permission to the user's calendar can view the event or task.
- Private. Only owners of the calendar can view the event or task.
- Time and Date Only. These are confidential events and tasks. Owners of the calendar can view the event or task. Other users see it just as a busy slot when requesting freebusy information.
In Calendar Server 6.3, you can set the calstore.filterprivateevents parameter to filter or not filter Private, and Time and Date Only (confidential) events and tasks. Calendar Server 7 does not provide a way of disabling filtering private and confidential events and tasks. That is, Calendar Server 7 always filters (recognizes) Private, and Time and Date Only (confidential) events and tasks.
This version of Calendar Server 6.3 includes bug fixes only.
Indexing and Search Service 1 Update 1 includes the following changes and new features:
- Scalability Improvements
- Office 2007 Open XML File Format Support
- Apple iWork File Format Support
- New Attachment Types: ataudio, atvideo, atcompress, atimage
- Attachment Search Available for All Attachment Types
- Attachments No Longer Saved to Attachment Store
- Search Timeout Can Be Client-Specified
- New issversion Utility
- Admin CLIs Are Now Symlinked Into and Executable From the iss-base /bin Directory
- issadmin.sh Now Has --threads and --continueonerror Options for --accountlist Actions
- issadmin.sh Now Has --listactiveservices and --stopservice Actions
- New indexSvcFork.sh Script to Replace indexSvcFork.pl
- svc_control.sh stop No Longer Persistent Across Reboots
- A commpkg upgrade Now Requires That postpatch_restart.sh Be Run Manually After the Upgrade
- Accounts Must Be Rebootstrapped After the Upgrade
Real-time event processing has been improved, allowing at least an order of magnitude higher indexing rate.
The Office 2007 Open XML File Format (docx, xlsx, pptx) is now supported. These attachments are categorized in the atdoc, atxls, and atppt attachment types along with the Word, Excel, and PowerPoint Binary File Format attachments (doc, xls, ppt) that were previously supported.
Apple iWork (Keynote, Pages and Numbers) files are now supported. These attachments are categorized into the new iwork attachment type.
To categorize more attachment types, new types have been added for audio, video, image, and compressed file formats.
All attachment types (for example, atplain, athtml, and new attachment types such as ataudio) can now be searched by type in attachment (contentFormat=attachmentOnly) searches. In Indexing and Search Service 1, only atjpeg, atpdf, atodf, atdoc, atppt, atxls, and atvsd were searchable by type in attachment searches.
Attachment files are no longer saved to the attachment store. Instead, search results include body part information for pointing back to the attachment file residing on the Messaging Server store.
A new search query parameter, timeoutmsec, allows a timeout to be set per search query.
The new iss-base/bin/issversion utility reports versioning information.
For convenience, the admin command line interfaces are now symlinked into and executable from the iss-base/bin directory.
The new --threads option enables issadmin.sh --accountlist actions to be performed in parallel across a set of threads. The new --continueonerror option enables issadmin.sh --accountlist actions to continue on error. (By default, the first account in an --accountlist action that finds an error terminates the remaining actions.)
The new command line options, --listactiveservices and --stopservice, enable services that are running to be listed and terminated if necessary.
The utility which supports bootstrapping a set of users in parallel has been rewritten for improved performance.
In Indexing and Search Service 1, if the services were stopped after a reboot, they would remain stopped. This behavior was changed in Indexing and Search Server 1 Update 1 to make svc_control.sh stop a temporary action, not persistent across reboots.
Because the postpatch process might be interactive, you must now manually run postpatch_restart.sh if you upgrade to this release by using commpkg upgrade.
Although Indexing and Search Service 1 indexes are backward-compatible with this release, you should rebootstrap all user accounts after upgrading to Indexing and Search Service 1 Update 1 to index the new attachment types and other changes in this release.
Instant Messaging 8 Update 3 includes the following changes and new features:
Instant Messaging 8 Update 3 enables the use of Shoal group messaging to broadcast conference messages across the server pool. You can now send conference messages across the server pool even if you have not used Shoal for auto-discovery or across subnets. For more information, see Using Shoal for Conferences Across Server Pools.
This protocol enables you to block communications with selected users in an instant messaging system. You can block communications from contacts using any XEP-0191-compliant client. For more information, see XEP 0191.
This version of Delegated Administrator 7 includes bug fixes only.
Connector for Outlook 7.3 Update 1 includes the following new features:
- Folder size and quota
- Support for Windows 7
- Support for Apple iPhone
This version of DSsetup contains the following new features and bug fixes:
- The sunMaxGroups is now correctly defined in the sunDelegatedOrganization objectclass, which is used by Delegated Administrator.
- A new search directory for LDAP utilities is available in the Directory Server 7 zipped version.
- The default schema type is now schema 2.
- The message pertaining to Access Manager has been removed. You can now use schema2 without Access Manager.