Printable Communications Suite 7 What's New

Skip to end of metadata
Go to start of metadata

What's New in This Release of Communications Suite 7

This document summarizes all features in Sun Java Communications Suite 7 that are new or have been enhanced since Sun Java Communications Suite 6 Update 2 was originally distributed in April 2009, for the following components:

Communications Suite 7 Products and Components
Product Version
Messaging Server 7 Update 3
Instant Messaging 8 Update 2
Convergence 1 Update 3
Calendar Server 7
Delegated Administrator 7 (latest patch)
Outlook Connector 7.3 Update 1 (latest patch)
Calendar Server 6.3 (latest patch)
Indexing and Search Service 1
Comms Sync 3.1 (latest patch)
Comms Installer 7
Messaging Server HA Agent (MS_SCHA) 7
Calendar Server HA Agent (CS_SCHA) 6.3
Instant Messaging HA Agent (IM_SCHA) 7.3
comm_dssetup 6.4 (latest patch 6.4p5)

This document contains the following sections:

What's New in Communications Suite 7

Communications Suite 7 includes the following changes and new features:

Upgrading to Communications Suite 7

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

System Virtualization Support

See System Virtualization Support in Sun Java System Products for a summary of Sun support for Sun Java System products and Sun Java suites, including Sun Java Communications Suite, when used in conjunction with system virtualization products and features.

What's New in Sun Convergence 1 Update 3

Convergence 1 Update 3 includes the following changes and new features:

POP Access to External Email

Sun Convergence enables you to collect emails from remote servers that allow POP access. You can compose, reply, and forward email by using Convergence without logging in to the site to manage your email. The Convergence client provides a wizard to set up the external accounts. Convergence authenticates the configured user against the remote server and collects emails in a designated folder (Inbox by default). To learn more about how to configure Convergence to collect external email, see Sun Convergence Online Help.

Sender Identities

Sun Convergence enables you to create and manage multiple identities. Each identity consists of its own sender name, reply-to email address, vCard, and a signature. Every identity is associated with a corresponding external account configured. The identity is created automatically with default values when a POP account is configured. See POP Access to External Mail. When sending emails, you can select the identity to use. When composing, replying, or forwarding an email, the Convergence client provides a drop-down list displaying the identities that you have configured. You can choose the identity you want to use when sending the email. To learn more about how to work with this feature, see the Sun Convergence Online Help.

Single Click Creation of Events

Sun Convergence enables you to create events in the Day, Week, Month, and Next 7 views by single clicking on the time slot at which you want to create the event. A call out appears when you single click on the time slot. To learn more about how to work with this feature, see the Sun Convergence Online Help.

Attachment Search

Sun Convergence enables you to search for attachments that you receive in your email. Using this feature you can search and view email attachments. This feature is available only when the search service is enabled by the administrator. Convergence uses Sun Java Indexing and Search Service to index email attachments. If enabled, a virtual folder named Attachments is displayed in the Convergence client. This feature provides different ways in which you can view your attachments and also provides an interface to apply filters to search for attachments. You can filter your search based on the sender of the attachment, a date range when you received the attachment, or the type of file that you are searching. To learn more about how to work with this feature, see the Sun Convergence Online Help.

Autocomplete Addresses from Corporate Directory

Sun Convergence provides the autocomplete feature of email addresses for Corporate Directory. The autocomplete feature enables you to select your contacts or groups without having to remember the name or email address. As you type the name or email address of your contact or group, a drop-down list displays the set of contacts that match the typed characters. The autocompletion of addresses is always enabled for Personal Address Books. For Convergence to provide autocompletion of corporate address book entries, a server-side parameter to enable corporate address book search must be set. For more information on how to work with this feature, see Sun Convergence Online Help. To know more about how to enable corporate directory searches in Convergence, see Sun Convergence Administration Guide.

Multiple Select in Address Book

Sun Convergence enables you to perform relevant group actions on multiple contacts in your address book. For example, to send an email to multiple contacts, select the contacts from the address book and select the option to send an email. The compose email window opens and the contacts are added as recipients of the email. Other actions include: creating events, exporting contacts, or deleting contacts. The actions that you can perform depend on the address book (personal or corporate) that you are using. For more information about this feature, see the Sun Convergence Online Help.

Support for Internet Explorer 8

Sun Convergence now supports Internet Explorer 8.

Single Click Selection of all Messages

Sun Convergence provides a button that enables you to select all the email messages in a folder. Click the Select All button on the mail tool bar to select all messages. All messages in the current folder are selected. This is useful to perform specific actions on all messages in your email folder.

Exporting Selected Entries from Address Book

Sun Convergence now enables you to export selected entries from your address book. Starting this release, you can export a selected few entries from your address book in addition to exporting the entire address book. To learn more about this feature, see the Sun Convergence Online Help.

Toolbar Changes

The Convergence client now provides an improved user experience. The icons in the tool bar have been replaced with slimmer buttons with labels. Buttons associated with multiple actions are combined and displayed as combo buttons or drop-down lists. This has been done to avoid wrapping of icons in the tool bars.

The following are some of the changes:

  • Combo buttons are used where there are alternatives and where one alternative is likely to be more common. In the Mail module, Forward as Attachment and Forward Inline are presented on a combo button labeled Forward. Clicking the label portion of the combo button triggers the Forward as Attachment action. Clicking the drop-down arrow of the combo button displays a menu with the two forwarding actions as options.
  • Drop-down buttons are used when there are alternatives and where no alternative is likely to be more common. In the Address Book module, the printing actions to print the whole address book or group verses printing an individual entry, are presented on a drop-down list.
  • Less common actions are moved to the quick action tool bar to the left pane in the Convergence client. The Import/Export icon for Address Book is now available on the quick actions tool bar on the left pane.
  • Actions that are not applicable are hidden instead of being disabled. For example, when managing group address books, only the buttons that are relevant to groups are visible on the toolbar.
Calendar Toolbar Changes

In the Calendar module, the tool bar has undergone significant changes. In the previous releases, the Calendar user interface provided two kinds of buttons:

  • Those associated with actions. For example, New Event, New Task, and so on.
  • Those associated with controlling the view. For example, Day View, Week View, and so on.

In the new user interface, all buttons that are associated with actions are displayed on the toolbar. A new row has been added under the tool bar displaying the actions that are associated with controlling the display. The view controls are displayed as buttons.

Address Book Notifications

Sun Convergence provides a JMS (Java Messaging Service) based notification service for the Personal Address Book (PAB). The notification feature enables administrators to set up a framework where messages are published to a JMS broker, when a state change occurs in a users personal address book. The notification messages are published on a JMS topic or a Queue that can then be consumed by a client. To know more about the Address book notification feature, see Convergence Address Book JMQ Notification.

Group-wise Listing of Configuration Parameters

You can now list group-specific configuration parameters in Sun Convergence by using the iwcadmin command. The scope of the -l switch in the iwcadmin command is broadened. This command is useful when you want to see the values specific to a particular module, for example, mail, in your Convergence deployment. To learn more about this feature, see Using the Sun Convergence Administration Utility.

Support for Sun GlassFish Enterprise Server 2.1

Sun Convergence now supports Sun GlassFish Enterprise Server 2.1.

Anti-Spam Functionality

The anti-spam functionality in this release of Sun Convergence has undergone the following changes:

Sun Convergence provides new parameters to configure the anti-spam feature. To learn more about how to configure Convergence for action against spam messages, see Enabling Anti-Spam.

This release includes the following changes in the Convergence client for the anti-spam functionality:

  • If anti-spam action is configured, a new system folder is created based on the name given by the administrator as a designated spam folder.
  • All spam messages are moved to the designated spam folder when a mail is marked as spam.
  • When spam messages are deleted in the spam folder by clicking on the Delete button, the messages are permanently deleted.
  • The Not Spam button is displayed in the mail tool bar only when you select the spam folder.

What's New in Messaging Server 7 Update 3

Messaging Server 7 Update 3 includes the following changes and new features:

Red Hat Enterprise Linux 5 Support

This release of Messaging Server supports Red Hat Enterprise Linux 5 (Release 5.3 on x64). For more information, see the Messaging Server 7 Update 3 Release Notes.

Elimination of setuid binaries from Messaging Server pipe_master and l_master

To improve product security, Messaging Server no longer uses setuid binaries at all (pipe_master and l_master are no longer setuid as of this release). This should resolve linking problems that resulted in pipe_master breaking when NSS is upgraded to 3.12. For more information, see the Messaging Server 7 Update 3 Release Notes.

Running the Directory Server Setup Script (comm_dssetup.pl) Required

You must run the version of comm_dssetup.pl that is bundled with the Communications Suite 7 installer.

New Initial Configuration Tool

Some of the main changes to the initial configuration tool include the following:

The new configure tool Interactive mode asks fewer questions and they appear in a different order from previous releases.  If a valid domain already exists in directory, it will not be modified by initial configuration.  There is no prompt for the group if the UNIX user already exists.  It uses the group to which the user belongs.  There is no prompt for the default organization DN.  If the domain exists in LDAP, it uses the only correct value, otherwise it defaults to o=<domain>,<ugsuffix>.  The stateFile setting to override works if the domain does not exist.  There is no prompt for components to configure.  Configuration files for all components are always generated.  User can turn on/off desired components on or off easily with configutil.

What's New in Calendar Server 7

Calendar Server 7 includes the following new features:

CalDAV Support

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:

  • PUT, POST, GET, MULTIGET, REPORT, HEAD, OPTIONS, PROPFIND, and PROPPATCH methods
  • MKCALENDAR method, for creating multiple calendars per user
  • Enhanced query reports, to both return recurring events and tasks in expanded form (in UTC), and to return only requested properties or parameters

iCal Support

Calendar Server 7 supports the iCalendar data format as defined in RFC2445bis. The following components are supported:

  • VEVENT
  • VTODO
  • VFREEBUSY
  • VTIMEZONE
  • VALARM

Recurring rules and exceptions are also supported.

Authentication

Calendar Server 7 supports basic HTTP authentication and authentication over SSL. With HTTP authentication you can do the following:

  • Restrict access to authenticated users only
  • Provide userid and password and execute commands on a calendar

Scheduling Support

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:

  • Free-busy queries on attendees.
  • Calendar-outbox and calendar-inbox for every user, as well as the ability to use the POST command for invitations and replies.
  • iTIP and iMIP protocols, as defined in RFC 2446 and RFC2447. Invitation emails are sent out for recipients without accounts on the calendar server, with all event details.
  • iSchedule protocol, which enables Calendar Server to act as a client and perform scheduling with servers from other products that support iSchedule.

WebDAV Sync

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.

Free-Busy Servlet

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.

Installation and Configuration

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.

Logging Service

The Calendar Server 7 logging service is a multilevel, configurable, logging module to help capture activity or debugging issues.

Notifications

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.

Admin Servlet

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.

Administrative Utilities

By using the davadmin command, you can perform the following tasks:

  • Obtain server version information
  • Read and modify the server configuration
  • Obtain, modify, or delete information about user collections and resources

You can use Jconsole to perform these tasks.

Calendar Server 7 also provides database utilities to back up and restore calendar collections.

Administrators Group

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.

LDAP Integration

Calendar Server 7 uses Directory Server with the latest Communications Suite schema to store and manage user information in its LDAP database. Support includes:

  • Capability of obtaining principal information from LDAP
  • Capability of matching principals to their calendar collections
  • Use of LDAP information for auto-creation of basic calendars on login or invitation
  • Use of LDAP caching for faster lookup results
  • Use of LDAP rollover support to use a backup LDAP server if primary LDAP server is not available

Collection tag or ctag

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.

Support for Multiple Back-end and Front-end Servers to Achieve Horizontal Scalability

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.

Hosted Domains

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.

Future Enhancements

The following features are not available in the the first official release (Revenue Release, or RR) of Calendar Server 7 but are being developed for a future update:

  • Subscriptions
  • Public and shared calendars
    Note: Currently, Calendar Server 7 users can view freebusy information and invite others but cannot subscribe to other calendars. To read and manage a calendar, users need to be logged in.
  • WebDAV ACLs
  • Attachments
  • WCAPbis servlet, to enable support for Convergence and Connector for Outlook
    Note
    No support for Communications Express in Calendar Server 7 is planned, as Communications Express is a deprecated client. Calendar Server 7 will not support Communications Express even when WCAPbis support is available.
  • Migration tool, to migrate Calendar Server 6 date to Calendar Server 7
  • Support for resource calendars and group calendars

What's New in Calendar Server 6.3

This version of Calendar Server 6.3 includes bug fixes only.

What's New in Indexing and Search Service 1

Indexing and Search Service 1 includes the following new features:

Index

  • Rapid Indexing of Existing Email: Email messages in a user's mailbox can be indexed. During this operation content is tagged in various ways to enable sophisticated searches.
  • Real-time Indexing: As email messages are received, sent, and moved to various folders, the index is updated in real-time. This reduces to near zero the chances of a false search result based on stale index information.

Search

  • Attachment Search: Users can search the body of attachments for keywords or phrases. Attachments can be in a variety of formats such as PDF; Microsoft Word, Excel, PowerPoint, and Visio; StarOffice/Open Office; HTML; and more.
  • Body Search: Users can search the body of a message for any relevant content. With Indexing and Search Service, body search includes search of supported attachment types as well as the plain text body of a message.
  • Search Integration with Sun Convergence: Indexing and Search Service integrates with Convergence through its existing search interface. Body searches are much faster and more powerful because they now not only search message text but also attachment contents.
  • Search Integration with Messaging Server: Other email clients can leverage improved body search and expanded attachment body search by using Messaging Server's IMAP search integration with Indexing and Search Service. The underlying search mechanism is transparent to a Messaging Server client.
  • RESTful Search Web Service API: Based on the OpenSearch 1.1 specification, the RESTful Search Web Service API provides RSS 2.0, Atom 1.0 or JSON format output. This interface is used by Messaging Server when it redirects IMAP SEARCH requests to Indexing and Search Service and by the sample search user interface. It can also be used by developers to mash up their email search results with other applications if desired.

Indexing and Search Service and Convergence

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.

What's New in Instant Messaging 8 Update 2

Instant Messaging 8 Update 2 includes the following changes and new features:

Using Shoal for Automatic Discovery of Peer Servers in a Pool

The server pool had to be stopped for reconfiguration if more servers had to be added to the pool. Instant Messaging 8 Update 2 enables the use of Shoal clustering framework to automatically discover and add peer servers in a server pool. For more information, see Using Shoal for Server Pool Messaging.

Support for Red Hat Enterprise Linux 5

Instant Messaging 8 Update 2 now supports Red Hat Enterprise Linux version 5.

What's New in Delegated Administrator 7

Delegated Administrator 7 includes the following changes and new features:

Provisioning for Calendar Server Users

Delegated Administrator 7 now supports Calendar Server 6.x and Calendar Server 7 provisioning. While basic calendar user provisioning is the same for both servers, Calendar Server 7 makes use of the new davStore attribute and not icsdwphost to assign a specific back-end in a multi-backend scenario. You can add the davStore LDAP attribute to users' and resources' subject entries to associate those users and resources with a particular back-end Calendar Server store. The value of the davStore attribute is equal to one of the davStore IDs defined in the server configuration. davStore is single valued. When not present, a server configurable default davStore ID is used.

When a user or group is assigned a calendar service, the davEntity objectclass will be added along with icscalendaruser or icscalendargroup objectclass enabling you to provision the user or the group with a davStore attribute.

The new user wizard with the Calendar Service Details consists of the following fields:

where the Calendar Host and Timezone are applicable to Calendar Server 6.x and Calendar Store is applicable to Calendar Server 7.

The user properties section in the Calendar Service Details consists of the following fields:

where the Calendar Host, Default Calendar, Timezone, Owned Calendar, Subscribed Calendar are applicable to Calendar Server 6 and Calendar Store is applicable to Calendar Server 7. EmailAddress and Calendar Service Status are applicable to both servers.

A new field called Calendar Store is added for Calendar Server 7 users. When configuring a user in Delegated Administrator with Calendar services, a valid davstore ID has to be entered in the Calendar Store field instead of hostname.

What's New in Connector for Outlook 7.3 Update 1

This version of Connector for Outlook 7.3 Update 1 includes the following new features:

Viewing Quota and Size Information

Connector for Microsoft Outlook 7.3 Update 1 now enables you to view your mailbox quota and folder size information. The quota information is displayed in kilobytes and the storage information for the selected folder is displayed as percentage.

Saving File Attachments in Optimized Mode

Connector for Microsoft Outlook 7.3 Update 1 now enables you to save the file attachments outside the PST using the Optimized mode. In Normal mode, the complete message including attachments are stored in the PST file locally. The Optimized mode reduces the local PST file size by not storing the message attachments in the PST. This mode is useful for virtual desktop environments, where the desktop is being stored in a centralized location and is downloaded every time a user logs into the network. The desktop data size that includes the PST file associated with the logged in user, will be reduced in the Optimized mode.

Optimized mode is not recommended for normal desktop users because in this mode, the message and its attachments, when accessed, will be downloaded from the server in every login session. The administrator can configure to create a profile in either Normal mode or Optimized mode, default being Normal mode.

What's New in DSsetup 6.4p5

This version of DSsetup contains the following new features and bug fixes:

Bugid 6845336 update uwc schema ldif with an extension for AB notification in convergence update

The schema change was made to the 98ns-dummy-uwc.ldif file

  • Add attribute abEventNotificationDestination to sunUCPreferences objectclass for Convergence

Bugid 6845575 schema changes for CALDAV

The schema changes for the new CALDAV server (aka Calendar Server 7) are all in the 60iplanet-calendar.ldif file

  • New objectClass davEntity
  • New Attributes for davEntity
    • davStore
    • davAllowedServices
    • davTimezone
    • davEventNotification
    • davEventNotificationDestination
  • Make icsCalendarUser, icsCalendarResource, and icsCalendarDomain AUXILIARY classes of inetOrgPerson, inetResource, and inetDomain, respectively
  • Add davAllowedServices to icsCalendarDomain objectclass

Bugid 6851767 schema changes for mailserv (list management)

The schema changes for the mailserv Messaging Server feature are all in the 56ims-schema.ldif file.

  • New attributes for inetMailGroup objectclass
    • mgrpUniqueId
    • mgrpDescription
    • mgrpDelayNotifications
    • mgrpDigestInterval
    • mgrpMaxMessagesPerDay
    • mgrpAdvertised
    • mgrpPublicRoster
    • mgrpSubscribePolicy
    • mgrpUnsubscribePolicy
    • mgrpJettisonBroadcasters
    • mgrpJettisonDomain
    • mgrpTrustNewMembers
    • mgrpListTag
  • Added allowed attributes for inetMailGroup objectclass
    • mail
    • cn
  • New objectclass inetMailingListUser
  • New attributes for inetMailingListUser
    • mluserUniqueId (required attribute)
    • mluserPassword
    • mluserJoinDate
    • mluserJoinIPAddress
  • New objectclass inetMailingListSubscription
  • New attributes for inetMailingListSubscription
    • mlsubListIdentifier (required attribute)
    • mlsubMail
    • mlsubRole
    • mlsubDigest
    • mlsubReceiveMail
    • mlsubSuppressDuplicates
    • mlsubJoinDate
    • mlsubJoinIPAddress
    • mlsubTentativeEmail
    • mlsubTrack
    • mlsubActionKey

Bugid 6852299 add suffix for mailserv MS 7u3 feature

For the Messaging Server mailserv feature:

  • A new suffix is created: o=mlusers
  • index mail (for eq), mlsubListIdentifier (for eq) and mlsubMail (for eq) on o=mlusers suffix
  • index cn (for eq) and mgrpUniqueId (for eq) on the user/group suffix
  • Add mlsuffix=o=mlusers sunkeyvalue to dssetup info, i.e. the well-known DN cn=CommServers,o=comms-config

Bugid 6851768 need anonymous access to cn=CommsServers,o=comms-config to read dssetup version

Add an aci to allow anonymous access to cn=CommsServers,o=comms-config the well-known DN where dssetup info is stored. This allows products (like Messaging Server) to access the stored dssetup information without having to authenticate.

Bugid 6851773 do not install AM search templates if AM was not installed

The Access Manager (AM) search templates are not installed unless we detect that the DS was configured by AM.

Put all the dssetup generated files under a single subdirectory

All the dssetup generated files are now placed under a single subdirectory: /var/tmp/dssetup_<timestamp>

numeric oids for mailserv and cleanup of the following schema files: 50ns-msg.ldif 55ims-ical.ldif 56ims-schema.ldif

All the oids in the schema files 50ns-msg.ldif 55ims-ical.ldif and 56ims-schema.ldif have been converted to numeric oids. Eventually all oids will be converted to numeric oids.

save old schema files, log stored dssetup info

  • The old schema files are now saved in /var/tmp/dssetup_<timestamp>/save.
  • The stored dssetup information in the Directory Server is now printed to the dssetup log file

Bugid 6862979 comm_dssetup.pl reports DS version as 6.3 for 6.3.1 installations

The full version of Directory Server (DS) is now reported not just the major and minor numbers. In addition, a check is added to see if you are at DS 5.2 Patch 6 or later. This check is done due to the NSS incompatibility, see the NSS incompatibility information at this url: http://docs.sun.com/source/820-3003/index.html

Bugid 6862978 need to check for default indexes for DS6

The check for default indexes that are created automatically with every new suffix was not implemented properly for DS 6.x.


Copyright © 2012, 2013 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/).

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

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


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