|
Sun Java System Calendar Server 6 2005Q1 Release Notes |
Sun Java™ System Calendar Server Release Notes
Version 6 2005Q1
Part Number 819-0023-10
Note
A patch is available at Sun Solve for this version of Calendar Server. For more information, see Important Patch Information.
These Release Notes contain important information available at the time of the general release of Sun Java System Calendar Server 6 2005Q1, including:
Read these Release Notes before you install and configure Calendar Server.
About Calendar Server, Version 6 2005Q1Calendar Server is a scalable, web-based solution for centralized calendaring and scheduling for enterprises and service providers. Calendar Server supports user calendars for both events and tasks as well as calendars for resources, such as conference rooms and equipment. For a list of new features, see the following section, What’s New in Calendar Server 6 2005Q1.
Calendar Server offers two graphical user interfaces, Calendar Express and Communications Express. It also offers customers the flexibility to use the Web Calendar Access Protocol (WCAP) to access calendar data directly in either text/calendar or text/xml format.
What’s New in Calendar Server 6 2005Q1Calendar Server 6 2005Q1 includes the following changes and new features:
Automatic Backups
This section covers the following topics:
Overview of the Old csstored.pl
In earlier versions of Calendar Server, one of the utilities bundled with the product was csstored.pl, which could be invoked to perform an online (hot) archival operation for calendar databases and log files (that is, it took a snapshot of the databases and log files). It performed the following functions:
- Copied the database files and current log files to a backup archive directory and a “hot” backup directory.
- Copied the log files returned by the Berkeley database db_archive utility to a backup archive directory and a “hot” backup directory.
- Removed all log files returned by the Berkeley database db_archive utility from the current database directory, except the last file. This identifies all the log files that have already been applied to the current databases.
- Ran the Berkeley database db_verify on the database files in the “hot” backup directory.
Overview of the New csstored Service
With the release of Calendar Server 6 2005Q1, this Perl script has been changed into a service (csstored) that starts automatically when you issue start-cal. However, the service does not perform a backup until it is configured and enabled. You can configure Calendar Server for automatic backups at the following times:
The new csstored service performs the following functions:
- At configured intervals, takes a snapshot of the database files. (Copies the database files and current log files to an archive directory, or a “hot” backup directory, or both, depending on how it is configured.)
- Runs db_verify against the snapshot.
- If the verify step fails (the database is corrupted), the service notifies the administrator. The administrator can put the current database into read-only mode . While the database is in read-only mode, no modify or delete transactions are accepted. It notifies the calendar administrator of the corruption. The administrator can run this step manually if database corruption is detected before the next snapshot.
- If db_verify verifies the snapshot, the current database continues to run during the interval period. In real time throughout the interval, the service moves already applied transaction log files from the current database directory to the archive or hotbackup (or both) directory.
- Asynchronously applies the log files to the hotbackup copy of the databases. This assures that the hotbackup copy is as current as the last transaction log applied to it.
How to Recover from a Database Failure
If your current database ever fails and you need to replace it with a backup, the hotbackup copy can be used with a minimum of processing (and thus a minimum of downtime). To prepare the hotbackup copy, you need only copy the unapplied transactions to the hotbackup directory and run db_recover against it. That utility applies the final unapplied transaction logs, and checks for corruptions. Then, run db_verify to check the state of the database. If the database is OK, then the hotbackup copy is ready to be used as your new production copy.
For more information about the new autobackup feature and the procedures needed to configure and administer it, see the chapter on autobackups in the Sun Java System Calendar Server Administration Guide.
For more information about restoring one of your automatic backups, see the “Troubleshooting” chapter of the Sun Java System Calendar Server Administration Guide.
Until automatic backups are enabled, the service sends an error message every 24 hours to the calendar administrator saying it is unconfigured. Performing hotbackups is a best practice for Calendar Sever.
Configuring Automatic Backups in csconfigurator.sh
The configuration program now asks you if you want to configure automatic backups. The configuration program will set up automatic backups (hotbackups) for you, or at a later date, you can configure automatic backups by following the instructions in the Sun Java System Calendar Server 6 2005Q1 Administration Guide.
Read-Only Database
Calendar Server uses Berkeley Database for its calendar databases (other than LDAP for the user and resource information). If your current Berkeley databases become corrupted and you need to continue to provide user access to them while you are recovering the data, Calendar Server 6 2005Q1 allows you to put the databases in read-only mode. In this mode, the server will not accept any update or delete transactions against any of the databases. Only read transactions are supported.
With automatic backups configured, the service runs db_verify against each new snapshot of the databases. If corruption is detected, it automatically sends a warning message to the administrator. The administrator can then put the databases into read-only mode.
However, you might detect corruption later on during the day, between snapshots. If this is the case, you can put your current databases into read-only mode while you are trying to recover. You can not selectively place individual Berkeley databases into read-only mode.
For more information about this, see the “Troubleshooting” chapter in the Sun Java System Calendar Server 6 2005Q1 Administration Guide.
To make the Berkeley databases read-only:
Support for Rebuilding Alarm Database Separately
In earlier releases of Calendar Server, when you ran csdb rebuild, all the Calendar Server databases were rebuilt. In Calendar Server 6 2005Q1, you can choose to rebuild only the alarms database. The reason for this is that analysis has shown that the alarms database was the most prone to corruption and was the quickest to rebuild. If you do not know which database is corrupt, you can run it for the alarm database only first to see if that catches the problem. If not, you can then run the full rebuild utility (csdb).
Automatic Database Verification in csdb rebuild
In earlier releases of Calendar Server, after rebuilding databases with csdb, you had to run db_verify manually to verify the rebuilt databases. Now, the csdb utility rebuild command automatically runs db_verify on the rebuilt database.
User Management Utility Name Change
The User Management Utility, a command-line only utility used for provisioning and management of users, resources and domains, has been renamed to the Delegated Administrator Utility and is still the only provisioning tool for Schema 2 that supports Calendar Server.
The Delegated Administrator graphical user interface released for 2005Q1 does not support Calendar Server.
Installation Changes - Directory Server Preparation Script (comm_dssetup.pl)
The Directory Server Preparation Script (comm_dssetup.pl) is no longer bundled with the Calendar Server and Messaging Server products. It has become a separately installable component in the Java Enterprise System installer. On the component selection panel, you can select the Directory Server Preparation Script by itself. Or, it is selected automatically if you select Directory Server.
In general, due to product changes, you will need to install the new Directory Server Preparation Script and run it even if you have run earlier versions. Do not rerun an earlier version you may already have as it will not contain the necessary updates.
Web Calendar Access Protocol (WCAP) Changes
The following changes were made in WCAP:
Freebusy Redirect URL
This sections covers the following topics:
What is the Freebusy Redirect URL Feature?
For customers migrating from Microsoft Exchange to Calendar Server, a new feature was added to WCAP that allows both databases to be searched, first the Calendar Server database and then the Microsoft Exchange database. This enables customers to maintain calendar services during the transition. To accomplish this, two changes were made in WCAP:
noredirect
This parameter is an integer with two values, 0 and 1. The default is 0, which causes the server to use the free_busy redirect URL if it exists in the ics.conf file.
When the value is set to 1, the server will neither look for, nor use the redirect URL, even if it exists in the ics.conf file.
How Does it Work?
When the server receives a free_busy command, it checks the Calendar Server calendar database. If the server can not find the calendar, the following steps take place:
- The server checks to see if the noredirect parameter was passed in the get_freebusy command.
- If the value of the noredirect parameter is 0, or was not passed in, the server looks for the value in the ics.conf file parameter service.wcap.freebusy.redirecturl.
- If the service.wcap.freebusy.redirecturl parameter exists and has a URL as its value, it passes the URL back to the requesting program. It is up to the requesting program to use the URL to look for the calendar in the Microsoft Exchange databases.
- If either of the following is true, the server returns an error.
Changes to Existing WCAP Commands
The following parameter changes were made to existing WCAP commands:
- notify–The notify parameter was removed from the following commands:
- smtp–The smtp parameter was added to replace the notify parameter.
- noredirect–The noredirect parameter was added to the free_busy command. It tells the server not to return the redirect URL in case the requested calendar can’t be found.
- fetchorder–This parameter was added to all fetch*_by commands. It allows you to choose in which order events and todos are returned. The choices are ascending order, descending order, or a special (legacy) order that is mostly ascending.
- excludedtstart–This parameter was added to the storeevents and storetodos commands. It specifies whether or not the dtstart date will be included in a recurring series even if the date falls outside the set of dates generated by the rrules.
For further information about these parameters, see the Sun Java System Calendar Server 6 2005Q1 Developer’s Guide.
New Error Message
One new error message was added: error 81: RECURRING_COMPONENT_NOT_FOUND–Recurring component not found. This only happens when recurring=1 is passed in by a fetch command. This code is returned if part of a recurring series is missing (either the master or an exception).
This error can be caused by a recurring series being truncated by a limit in the maximum number of transactions fetched, or by a date range limitation.
Old Deployment Guides DeprecatedThe Sun Java System Calendar Server 6 2004Q2 Deployment Guide and the Sun Java Communications Services 6 2004Q2 Enterprise Deployment Planning Guide have been deprecated in favor of the Sun Java System Communications Services 6 2005Q1 Deployment Planning Guide.
Hardware/Software Requirements and RecommendationsThis section describes the hardware and software required and recommended for this release of Calendar Server.
Hardware Requirements and Recommendations
Software Requirements and Recommendations
Supported Software Platforms
Recommended Browsers for Client Computers
Sun Java System Communications Express 6 2005Q1 requires a JavaScript-enabled browser. For optimal performance, the following browsers are recommended:
Important Patch Information
A patch is availble for Calendar Server 6 2005Q1. It is recommended that you add the patch before attempting to run Calendar Server. The patch number for each platform shows in that follows:
Table 2 Patch Numbers for Calendar Server 6 2005Q1
Platform
Patch Number
Solaris, SPARC
116577-17
x86
116578-17
Linux
117851-17
- For the current list of required patches for Sun Java System Calendar Server, go to:
- Select either “Patches” or “Patch Portal”.
- Follow the Sun Java System Calendar Server links.
As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.
Pre-Installation NotesThis section contains information you should know before you install Calendar Server 6 2005Q1, including:
Front-End and Back-End Machines and Operating Systems
For Calendar Server installations that separate functionality across front-end and back-end machines, the hardware platforms must be the same on each end.
More specifically, due to big-endian versus small-endian incompatibility, you can’t use both an x86 platform machine and a Sparc platform machine in the same Calendar Server deployment containing front-end and back-end machines.
Moreover, mixing Solaris x86 and Linux operating systems for front-end and back-end machines has not been tested and is not currently supported.
For more information about installing Calendar Server on front-end and back-end machines, see the Sun Java System Calendar Server 6 20005Q1 Administration Guide at:
http://docs.sun.com/coll/CalendarServer_05q1
Linux Platform Support
Java Enterprise System runs on the Linux platform. The major differences in user experience will be the path names where product directories are installed. The Linux platform installs into a different directory than the Solaris platform.
The default installation locations are listed for the following:
Calendar Server
The following table compares the directory paths of both platforms for Calendar Server:
Communications Express
The default installation location in Linux for Communications Express is:
/opt/sun/uwc
Delgated Administrator Utility (formerly User Management Utility)
/opt/sun/comms/commcli
OS Patches
You must apply the required operating system patches before installing Calendar Server 6 2005Q1. Refer to the Sun Java Enterprise System 2005Q1 Release Notes for a list of required patches.
Required Privileges
To run the Sun Java™ Enterprise System installer or the Calendar Server 6 2005Q1 configuration program on Solaris Systems, you must log in as or become the superuser (root).
Java Enterprise System Installer
Install Calendar Server 6 2005Q1 using the Sun Java™ Enterprise System installer. The Java Enterprise System installer installs the Sun component product packages, including Calendar Server 6 2005Q1, and the shared components that are used by the various products.
This section covers the following topics:
Default Installation Directory
The default installation directory (cal_svr_base) for Solaris packages (SUNWics5 and SUNWica5) is:
/opt
After installation, Solaris Calendar Server files are found in /opt/SUNWics5/cal.
The default installation directory (cal_svr_base) for Linux packages (for core and API) is:
/opt
After installation, Linux Calendar Server files are found in /opt/sun/calendar.
Linux Package Names
lists the Linux package names for the various Calendar Server related components.
Upgrading From an Earlier Version of Calendar Server 6
Do not attempt to upgrade Calendar Server using the Sun Java Enterprise System installer. You must use the patchadd process. Find instructions for upgrading from Calendar Server 2003Q4 or 2004Q4 to the current release 2005Q1 in the Sun Java Enterprise System 2005Q1 Upgrade and Migration Guide. See also the Sun Java Enterprise System 2005Q1 Release Notes.
These and other related documents can be found at:
http://docs.sun.com/coll/entsys_05q1
Upgrading Your Calendar Database
If you have Calendar Server 6.0 installed, with Berkeley DB version 3.2.9, the conversion to the current 4.2 version will be done automatically. You do not need to run any other database migration programs.
If you have a Calendar Server 5.x installation that uses Berkeley DB version 2.6, you must upgrade your calendar database to version 4.2. using the cs5migrate or the cs5migrate_recurring utility. The utilities are available upon request from technical support.
If you have an existing Calendar Server 2.x installation, you must upgrade to Calendar Server 5.x before you can migrate to the current release.
For information about migration, see the Sun Java System Calendar Server 6 2005Q1 Administration Guide at:
http://docs.sun.com/coll/CalendarServer_05q1
Post-Installation Configuration Steps
After installing or upgrading to Calendar Server 6 2005Q1, you must configure it as follows:
For instructions, refer to the Sun Java System Calendar Server 6 2005Q1 Administration Guide.
Where to Find Calendar Server Data and Utilities
For Java Enterprise System Release 2, Calendar Server provides the links shown in .
Directory Server Performance
To improve the performance of your LDAP directory server, especially if you are using calendar searches of the LDAP directory consider the following items:
Indexing the LDAP Directory Server Attributes
To improve performance when Calendar Server accesses the LDAP directory server, add indexes to the LDAP configuration file for various attributes.
The configuration program, comm_dssetup.pl, will optionally do the indexing for you.
To see the performance difference indexing can give you, perform the following test:
ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Express Subscribe > Calendar Search dialog.
Tests have shown that with 60,000 entries, the above search took about 50-55 seconds without indexing icsCalendarOwned. After indexing, the above search took only about 1-2 seconds.
For more information about adding directory server indexes, refer to the Sun Java System Directory Server 5 2005Q1 documentation at:
http://docs.sun.com/coll/DirectoryServer_05q1
Checking and Setting the Size Limit and the Look Through Limit Parameters
To determine if the Look Through Limit (nsslapd-lookthroughlimit) and Size Limit (nsslapd-sizelimit) parameters are set to appropriate values, try the following command:
ldapsearch -b "base"
"(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))"where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Express Subscribe > Calendar Search dialog.
If the LDAP server returns an error, the nsslapd-sizelimit or the nsslapd-lookthroughlimit parameter might not be large enough. Follow these guidelines to set these parameters:
- Ensure that the value for the nsslapd-sizelimit parameter in the slapd.conf or equivalent file is large enough to return all the desired results; otherwise, truncation can occur, and no results will be displayed.
- Ensure that the value for the nsslapd-lookthroughlimit parameter in the slapd.ldbm.conf or equivalent file is large enough to complete a search of all the users and resources in the LDAP directory. If possible set nsslapd-lookthroughlimit to -1, which causes no limit to be used.
Communications Express Using Schema 1
There are two issues with Schema 1 in Communications Express:
Provisioning Tools
There are two tools for provisioning users, groups and domains for Calendar Server: The Delegated Administrator Utility and Calendar Server utilities. For information on Delegated Administrator, see the Sun Java System Communications Services 6 2005Q1 Delegated Administrator Guide. For information on the Calendar Server utilities, see the Sun Java System Calendar Server 6 2005Q1 Administration Guide.
New Migration Utility for Recurring Events
Some applications, such as Sun Java System Connector for Microsoft Outlook require recurring events and tasks to be presented as a master component with exceptions. Calendar Server versions prior to 6 2004Q2 did not offer this format for recurring events. Therefore, a new version of the cs5migrate utility, cs5mgrate_recurring, was introduced in Calendar Server 6 2004Q2.
The cs5migrate utility performs the following tasks:
In addition, the cs5migrate_recurring utility creates master and exception records for all recurring events and tasks. Going forward these records will be automatically generated by Calendar Server.
If you need to migrate your database but do not plan to use the Connector for Microsoft Outlook, you do not need run cs5migrate_recurring; run cs5migrate instead.
Contact technical support for the download location and documentation for either utility. Be sure to specify whether you are migrating recurring events and plan to use the Connector for Microsoft Outlook.
Calendar Server 6 Documentation
Calender Server 6 includes the following documentation. Part numbers are in parentheses.
- Sun Java System Calendar Server 6 2005Q1 Release Notes (819-0023)
- Sun Java System Calendar Server 6 2005Q1 Administration Guide (819-0024)
- Sun Java System Calendar Server 6 2005Q1 Developer’s Guide (819-0025)
- Sun Java System Communications Express 6 2005Q1 Administration Guide (819-0115)
- Sun Java System Communications Express 6 2005Q1 Customization Guide (819-0116)
- Sun Java System Communications Services 6 2005Q1 User Management Utility Administration Guide (819-0114)
- Sun Java System Communications Services 6 2005Q1 Schema Reference (819-0113)
- Sun Java System Communications Services 6 2005Q1 Schema Migration Guide (819-0112)
- Sun Java System Communications Services 6 2005Q1 Event Notification Service Guide (819-0109)
Calendar Express 6 2005Q1 Online Help is available with the Calendar Express software. Communications Express 6 2005Q1 Online Help is available with the Communications Express software.
Calendar Server 6 2005Q1 documentation is available on the following Web site:
http://docs.sun.com/coll/CalendarServer_05q1
Problems Fixed Since Beta
lists the problems that were reported in the 2005Q1 Beta that are fixed in the general release:
Known Issues and LimitationsThis section contains tables that list of the more important known issues at the time of the Calendar Server 6 release:
Limitations
The following limitation is known at this time:
Removing all Instances of Multi-Valued User Preferences
Limitation: Each set_userprefs command removes only one instance of a multi-valued preference.
Workaround: To remove all instances of a multi-valued user preference, you must issue one set_userpref command per instance.
For example: Perform a get_userprefs to list all of the user preferences. If there are multiple values for a preference, such as icsSubscribed, then you must issue one set_userprefs command to delete the preference for each of the values listed.
Finding Installed Patches in a Clustered Environment
Limitation: There is no cluster specific showrev command that will show what is installed on the individual nodes of the cluster. (This is a generic problem, not just Calendar Server specific. You would run into the same difficulty with any product installed on a global file system.)
This is a problem when you want to update Calendar Server. You need to apply the patch to every node where Calendar Server was already installed. In addition you can’t apply the patch to a node if Calendar Server hasn’t already been installed on it. If you don’t know which nodes have Calendar Server installed and which do not, at the least, it will be confusing and cost you time trying to discover where Calendar Server is installed.
Workaround: Run the following command to see all of the nodes where Calendar Server is installed: pkgparam -v SUNWics5 | grep ACTIVE_PATCH
Pop-up Blockers
Limitation: Certain Calendar Server windows will not display if you have a pop-up blocker enabled.
Workaround: Disable pop-up blockers for the Calendar URL to ensure all Calendar Server windows will display.
Exception: Neither the Norton Inet Security AD_BLOCKER nor the Mozilla built-in POP_BLOCKER will affect Calendar Server windows.
Provisioning Users for Communications Express in Schema 1 Mode
Limitation: The csuser utility does not enable users it creates for Address Book.
Workaround: Enable the user using ldapmodify.
Multiple Domains (Hosted Domains)
Limitation: The configuration program, csconfigurator.sh, configures only a single domain.
Workaround: If you need a multiple domain calendar environment (called either Virtual Domains or Hosted Domains), you must add the domains yourself using the Delegated Administrator Utility (formerly called the User Management Utility), or the csdomain utility if you are still using Sun LDAP Schema 1. See “Setting up Hosted Domains” and “Administering Hosted Domains” in the Sun Java System Calendar Server 6 2005Q1 Administration Guide.
Reported Problems
lists problems reported on the product.
Redistributable FilesSun Java System Calendar Server 6 2005Q1 contains the following set of files for which Sun Microsystems, Inc. grants you a non-exclusive, non-transferable, limited license to reproduce and distribute in binary form.
In addition, you may copy and use but not modify the listed header files and class libraries solely to cause your resulting binaries to be able to interface with Sun’s software APIs.
Sample code is provided solely for reference purposes pursuant to creating the above mentioned binaries.
All the redistributable files for Calendar Server are for the plugin API, known as CSAPI. The API is described in the Sun Java System Calendar Server 6 2005Q1 Developer’s Guide at:
http://docs.sun.com/coll/CalendarServer_04q2
In the following files, cal_svr_base is the directory into which Calendar Server was installed. The default for Solaris is /opt/SUNWics5/cal, for Linux it is /opt/sun/calendar
Redistributable files are found in various subdirectories of cal_svr_base/csapi:
authsdk
The following are the redistributable files in this subdirectory (cal_svr_base/csapi/authsdk/):
bin
The following are the redistributable files in this subdirectory (cal_svr_base/csapi/bin/):
classes
The following are the redistributable files in this subdirectory (cal_svr_base/csapi/classes/):
include
The following are the redistributable files in this subdirectory (cal_svr_base/csapi/include/):
plugins
This directory (cal_svr_base/csapi/plugins/) has redistributable files in the following subdirectories:
accesscontrol
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/plugins/accesscontrol/):
authentication
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/plugins/authentication/):
datatranslator
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/plugins/datatranslator/):
userattributes
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/plugins/userattributes/):
samples
This directory (cal_svr_base/csapi/samples/) has redistributable files in the following subdirectories:
authentication
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/samples/authentication/):
authlogon.c
authlogon.h
authtest.c
csAuthenticationLocal.cpp
csAuthenticationLocal.h
csAuthenticationLocalFactory.cpp
datatranslator
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/samples/datatranslator/):
ens
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/samples/ens/):
userattributes
The following redistributable files are found in this subdirectory (cal_svr_base/csapi/samples/userattributes/):
Communications ExpressSun Java™ System Communications Express Version 6 2005Q1 provides an integrated web-based communication and collaboration client that consists of three client modules - Calendar, Address Book and Mail. The Calendar and Address Book client modules are deployed as a single application on any web container and are collectively referred to as Unified Web Client (UWC). Messenger Express is the standalone web interface mail application that uses the HTTP service of the Messaging Server.
This section contains the following topics:
Supported Browsers
See Recommended Browsers for Client Computers under Hardware and Software Recommendations.
Installation Notes
The following are the dependent services for Communications Express:
- Directory Server - Install Sun Java™ System Directory Server version 5.2.
- Calendar Server - Install Sun Java™ System Calendar Server Version 6.2.
- Web Server - Install Sun Java™ System Web Server version 6.1 SP4.
- Messaging Server - Install Sun Java™ System Messaging Server 6.2.
- Access Manager - Install Sun Java™ System Access Manager 6.2.
- Application Server - Install Sun Java™ System Application Server 8.1.
Refer to chapter 2, “Installing and Configuring Communications Express” of Sun Java™ Systems Communications Express Administration Guide for instructions on how to install and configure Sun Java System Communications Express.
Known Issues and Limitations
This section contains a list of the known issues with Communications Express 6 2005Q1. The following product areas are covered:
Generic Issues
Login page displays an incorrect version. (6213879)
When you click on the version link in Login page, the version is displayed as Sun Java System Communications Express 6 2004Q4 instead of Sun Java System Communications Express 6 2005Q1.
The user does not have an option to choose a view after logging into Communications Express (6195844)
The option to select a default view has been removed from Global Options. The Online Help does not reflect this change.
Communications Express displays a wrong error message while traversing from Options to Address Book. (6179023)
While traversing from Options to Address Book, Communications Express displays a wrong error message. The error message points out that the preferred language has been changed. This error message is wrong, since no changes have been made to language settings. This message can be safely ignored.
Communications Express does not generate logs if the white space is missing in uwc.logging.enable. (5060300)
Communications Express does not generate logs if you type uwc.logging.enable=yes(without a space after =). It generates logs only when you enter uwc.logging.enable= yes(with a space after =)
FQHN required in URL even when the user is authenticated. (5008104)
Communications Express cannot be fully configured if a fully qualified host name is not provided. The domain name is not set in the cookie if the URL is not with FQHN even when the user is authenticated.
Workaround
Always access the application using a fully qualified host name.
Configurator Tool Issues
This section contains a list of known issues in the configurator tool for Communications Express.
Wrong warning messages are displayed during configuration. (6206941)
Communications Express displays wrong warning messages during configuration. These warning messages point out that some shared components for Communications Express have not been installed. These are wrong warning messages and can be safely ignored.
DISPLAY variable must be set even if the configuration is done using CLI mode for the Communications Express Configurator. (6199114)
While configuring with the CLI mode, the Communications Express Configurator throws an exception if the DISPLAY variable is not set in non-GUI mode.
The Communications Express configurator throws exception if no DISPLAY variable is set with jdk1.5 (6197740)
The Communications Express configurator throws exception if the DISPLAY variable is not set with jdk 1.5 even with -nodisplay option enabled. This is due to a bug in jdk1.5.
The Configurator Tool for Communications Express does not Support Unconfiguring. (5104756)
The Communications Express Configurator does not allow you to undeploy, remove files at the time of configuration, and remove files created during run-time.
Workaround
To unconfigure Communications Express:
Silent configuration does not work. (5008791)
Communications Express allows configuration to be executed only interactively, and does not allow silent configuration. When you try to configure in a silent mode, the following error is displayed, “The Directory name cannot be left blank. This is a mandatory field. Please enter again.”
Communications Express Configurator: devinstall is dumping core if host aliases are not resolved. (5028906)
Communications Express configurator fails to complete the configuration process if your system is not configured for host name aliases.
Workaround
Ensure that you have configured one or more host name aliases for your system.
To configure one or more host name aliases on UNIX systems:
- Provide the configuration for the hosts in /etc/nsswitch.conf file:
hosts: files dns nis
This configuration indicates to the name service the lookup order it should use to resolve host names and host aliases. The name service lookup order is: files, dns, and nis.
- Ensure that the /etc/hosts file contains two or more host names defined against your machine’s IP address.
For example, if your system IP address is 129.158.230.64, then in /etc/hosts file, you can configure the IP address as:
129.158.230.64 budgie.siroe.varrius.com budgie
or
129.158.230.64 budgie.siroe.varrius.com budgie loghost
Example of an incorrect IP address:
129.158.230.64 budgie
GUI configuration input fields should not be right aligned. (4996723)
The field names and browser buttons are truncated or not visible when the configuration wizard is invoked in a language other than English.
Workaround
Resize the configuration panels to view its contents properly.
The components for Communications Express are shown to be zero bytes. (4982590)
The configurator tool for Communications Express shows the component size as 0 bytes while displaying the Mail and Calendar components for Communications Express.
Calendar Issues
Imported events and tasks in to calendar cannot be edited. (6199583)
Imported tasks and events cannot be edited even when the user has created them in his or her own calendar.
View Calendar Details online help is not consistent with application behavior. (6149493)
Selecting a calendar and clicking View will not show View Calendar Details window. Instead, it will open the selected calendar.
Calendar does not allow users to select any year beyond 2006 in all the views. (5086083)
Communications Express allows users to select any year only till the year 2006. It does not allow selection of any other year after 2006 in all the views.
Modifying the number of instances of a recurring event changes the start date of the event series. (5078220)
When you create two recurring events in Communications Express, and modify the number of instances in the second/later event, the start date for the event series gets shifted to the new start date.
The Day and Year formats in the calendar view are not translated to Simplified Chinese. (5025449)
The Day and Year View formats in the calendar view are not translated to the Simplified Chinese language. However the ‘Month’ view is correctly translated to Simplified Chinese.
Mail Issues
Addresses selected from the Address Book are not shown in the Compose Window of Mail (6208731)
Select some addresses from the address book and choose an option to send an email from the address book. The ‘To’ Field in the Compose Window that pops up does not contain any of the addresses that were selected in address book.
If the User or Domain status is set to ‘overquota’, mails cannot be accessed (6207018)
If you set the mailDomainStatus attribute for a domain or the mailUserStatus attribute to ‘overquota’ then the ‘Mail’ tab in Communications Express is not displayed.
Adding too large of an attachment will result in a "Page Not Found" error. (6193396)
You will see this error if you attempt to attach a file larger than the default maximum (5 MB).
User cannot edit in RTF Mode with Mozilla and Netscape. (6183540)
When you open the Compose Window, the text area is in the RTF Mode by default. If Communications Express is run on any other port apart from port 80, the user cannot edit anything in the text area. If Communications Express is running in port 80 then you will lose the composed text if you switch between the plain text mode and rich text mode.
Using Spell Check in plain text mode appends junk characters. (6179771)
Compose a mail with some spelling mistakes in plain text format, and click ‘Spell Check’. Correct the spelling mistakes, and further click ‘Edit’ to get back to the ‘Compose Mail’ window. You can notice that ‘ ’ has been appended to every corrected word.
Clicking on ‘Compose Mail’ window displays a blank window. (6178354)
Click a group from Address Book and further select a user from a group. When you click ‘Show Details’ and and further select ‘Compose Mail’, a blank window is displayed.
HTML content is displayed when you click spell check. (5100222)
Type some text in the ‘Compose Mail’ window and indent it to the right. If you click on Spell check now, the entire HTML content is displayed.
Download external mail pop-up window is too small to accommodate all User Interface elements for a localized User Interface. (5058226)
You are unable to see "Download", "Cancel" and "Help" buttons.
Users are not added when you add recipients from the New Message Window of Mail with Netscape 7.1 on Windows 2000 (5041977)
Click the ‘To’ icon in the New Message Window and enter a valid address book user to search for. When you enable the ‘To’ checkbox and click ‘Add Recipients’, a Javascript error "inputObj is null" is displayed and the user is not added to the email message. This bug is noticed only with Netscape 7.1 on Windows 2000.
Mail filters: Settings not saved properly. (5032888)
The “File message to folder:” and “Forward to email address:” settings are not saved properly when the Mail Filter details are viewed in the Edit mode.
Mail filters: An application error is displayed a mail filter is created with certain conditions. (5032833)
Communications Express displays and error page with the following error when you create Mail Filter with certain conditions:
Application Error
com.iplanet.jato.NavigationException: Exception encountered during forward
Root cause = [java.lang.StackOverflowError]
Address Book Issues
Authentication from Address Book from Outlook fails when Communications Express is deployed on Sun Java System Application Server 8.1 Enterprise Edition. (6189264)
Deploy Communications Express on Sun Java System Application Server 8.1 Enterprise Edition, and create a new profile in Outlook Connector. When you try to login to the profile, the login to Address Book fails and the user is asked for the password. The Address Book login fails yet again. However, the user is able to login to Address Book through Web UI.
Group import in CSV format is not supported in Address Book. (6182437)
Groups import is only supported in LDIF format. No other format has a standard format (or a format that other applications may export) to export groups. The message for the successful import of contacts is displayed in red.
Address Book does not use LDAP VLV control even when vlv_paging=true (5052474)
Even when vlv_paging=true is set in db_config.properties, Address Book does not use the Virtual List View Control while doing an LDAP search. This may affect the performance of Directory Deployments which have VLV indexes setup.
The address book Name cannot be localized by defaultps/dictionary-<lang>.xml for every session. (4995472)
The address book name cannot be localized because the localized value which is based on the resolved session language and the domain specific defaultps/dictionary-<lang>.xml is assigned when the address book is accessed for the first time.
The “Name” and “Description” entered in the Address Book Options page are also not displayed in the current Address Book drop-down list that appears on the Address Book tab page.
Options Issues
The online help for Option/General contains the following information under ‘Default View after login’ - “Select the default page to be displayed after you login from the drop-down list. The options available are: Email, Calendar, and Address Book”. The Options Page does not provide the user with the option to select the default application. However the online help does not reflect this change.
Localization Issues
The following known issues are not necessarily localization-specific.
A Javascript error is displayed when trying to add a user into address book from a mail in the French locale. (6216191)
Login to Communications Express with the preferred language set to French. Open any mail, and click the sender’s e-mail address. A Javascript error is shown and the user cannot be added to address book.
Apostrophes and accented characters are sometimes corrupted in the French locale. (6207966)
Apostrophes and accented characters are corrupted for the strings in French locale.
Some strings are displayed in English in the ‘Compose Mail’ window. (6204672)
In the ‘Compose Mail’ window, some strings like ‘Compose title’, ‘to’,’’cc’, ‘bcc’,’Attachments’,’Subject’,’Plain text’, ‘Rich Text’ are displayed in English. This happens when using Mozilla 1.x, Netscape 7.x, Mozilla FireFox for Japanese, Korean, Simplified Chinese and Traditional Chinese locales.
Mail sent using large Japanese/French data appears garbled. (6201676)
When a large email message is received, users must click an attachment link (text/html or text/plain) within the message. If the content of this attachment includes non-ASCII characters, users may see corrupted data in the newly opened browser pane. This issue will be fixed in the next available patch.
Workaround:
Manually select the appropriate encoding from the browser menu.
Some strings are displayed in English in the Compose window on Mozilla1.x, Netscape7.x, Firefox when the preferred language is set to Japanese, Korean, Simplified Chinese or Traditional Chinese. (6200222)
The Compose title, To, CC, BCC, Attachments, Subject, Plain Text, and Rich Text are displayed in English instead of the preferred language.
The localized version of the Communications Express online help is not the latest version (6199833)
The English version of the Communications Express online help is the latest version of the help tool.
Importing contacts in the CSV format from localized Outlook does not work (6186520)
When you try to import contacts in the CSV format from localized Outlook, the address book displays an error as follows. “Encountered an error while trying to import csvus entry types in _Personal Address Book. The file you have submitted may be of an incorrect type, corrupted or contains data that exists already.”
Incorrect translation for "Sent" folder name in Korean. (6182987)
The folder name "Sent" is translated to "Sent Date" instead of "Sent folder" in Korean.
Messenger Express: Messenger Express sometimes shows blank page due to Javascript error on Internet Explorer (6181721)
With non-English languages, Communication Express sometimes displays blank page and Javascript error when you use Internet Explorer.
Workaround:
Put the following meta tag in the Communications Express HTML files which are usually installed in:/opt/SUNWmsgsr/config/html/lang (before doing configuration) and /var/opt/SUNWmsgsr/config/html/lang (after configuration).
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Day and Year formats in calendar view are not translated to Simplified Chinese. (5025449)
Day and Year View formats in Calendar view are not translated to Simplified Chinese. However, the ‘Month’ view is correctly translated to Simplified Chinese.
Delgated Administrator UtilityThis section describes known issues in Communications Services Delegated Administrator Utility, formerly the Communications Services User Management Utility.
Note
The Delegated Administrator Console (GUI) does not support Calendar Server. You must use the Delegated Administrator Utility (command-line utility).
Manual steps are required to enable the commadmin utility to run against an LDAP directory in Schema 2 compatibility mode. (5042801)
To enable commadmin to work on an LDAP directory in Schema 2 compatibility mode, you must manually take the steps described below.
Workaround
Take the following six steps:1. Add the following ACIs to the OSI root. (Be sure to replace ugldapbasedn with your usergroup suffix.)
#
# acis to limit Org Admin Role
#
########################################
# dn: <local.ugldapbasedn>
########################################
dn: <ugldapbasedn>
changetype: modify
add: aci
aci: (target="ldap:///($dn),<ugldapbasedn>")(targetattr="*")
(version 3.0; acl "Organization Admin Role access deny to org node"; deny (write,add,delete) roledn = "ldap:///cn=Organization Admin Role,($dn),<ugldapbasedn>";)dn: <ugldapbasedn>
changetype: modify
add: aci
aci: (target="ldap:///($dn),<ugldapbasedn>")(targetattr="*") (version 3.0; acl "Organization Admin Role access allow read to org node"; allow (read,search) roledn = "ldap:///cn=Organization Admin Role,($dn),<ugldapbasedn>";)2. Add the following ACIs to the DC Tree root suffix. (Be sure to replace dctreebasedn with your DC Tree root suffix and ugldapbasedn with your usergroup suffix.)
#
# acis to limit Org Admin Role
#
########################################
# dn: <dctreebasedn>
########################################
dn: <dctreebasedn>
changetype: modify
add: aci
aci: (target="ldap:///($dn),<dctreebasedn>")(targetattr="*")
(version 3.0; acl "Organization Admin Role access deny to dc node";
deny (write,add,delete) roledn = "ldap:///cn=Organization Admin Role,($dn),<ugldapbasedn>";)dn: <dctreebasedn>
changetype: modify
add: aci
aci: (target="ldap:///($dn),<dctreebasedn>")(targetattr="*")
(version 3.0; acl "Organization Admin Role access allow read to dc node"; allow (read,search) roledn = "ldap:///cn=Organization Admin Role,($dn),<ugldapbasedn>";)dn:<dctreebasedn>
changetype:modify
add:aci
aci: (target="ldap:///<dctreebasedn>")(targetattr="*")
(version 3.0; acl "S1IS Proxy user rights"; allow (proxy)
userdn = "ldap:///cn=puser,ou=DSAME Users,<ugldapbasedn>";)dn:<dctreebasedn>
changetype:modify
add:aci
aci: (target="ldap:///<dctreebasedn>")(targetattr="*")
(version 3.0; acl "S1IS special dsame user rights for all under the root suffix"; allow (all) userdn ="ldap:///cn=dsameuser,ou=DSAME Users,<ugldapbasedn>";)dn:<dctreebasedn>
changetype:modify
add:aci
aci: (target="ldap:///<dctreebasedn>")(targetattr="*")
(version 3.0; acl "S1IS Top-level admin rights";
allow (all) roledn = "ldap:///cn=Top-level Admin Role,<ugldapbasedn>";)3. Set the com.iplanet.am.domaincomponent property in the AMConfig.properties file to your DC Tree root suffix. For example, modify the following lines in the <IS_base_directory>/lib/AMConfig.properties file:
from
com.iplanet.am.domaincomponent=o=isp
to
com.iplanet.am.domaincomponent=o=internet4. Enable Access Manager to use compatibility mode. In the Access Manager Console, in the Administration Console Service page, check (enable) the Domain Component Tree Enabled check box.
5. Add the inetdomain object class to all the DC Tree nodes (such as dc=com,o=internet), as in following example:
/var/mps/serverroot/shared/bin 298% ./ldapmodify -D "cn=Directory Manager" -
w password
dn: dc=com,o=internet
changetype: modify
add: objectclass
objectclass: inetdomain6. Restart the Web container.
If you upgrade the User Management Utility (commadmin) from version 6 2003Q4 to version 6 2004Q2, the domain administrator can add and delete services to the domain and can modify domain attributes. (5026945)
The domain administrator should not have the authority to change domain attributes.
This situation occurs when you upgrade the User Management Utility (commadmin) from version 6 2003Q4 to version 6 2004Q2. If you do a fresh installation of the upgraded version of commadmin (bundled with Access Manager 6 2004Q2), the proper usergroup.ldif files are added automatically when you configure commadmin with the config-iscli program.
Workaround
To obtain the ACIs to properly restrict the privileges of the domain administrator, take the following steps:1. Open the usergroup.ldif, located in the msg_svr_base/lib/config-templates directory, and replace ugldapbasedn in the template ldif with your usergroup suffix.
2. Add the edited usergroup.ldif into the LDAP directory.
The commadmin configuration process does not detect the default web container (Application Server). (5015063)
When the commadmin is configured, the configuration utility does not detect the default web container. (The default web container for Access Manager is Application Server.) Instead, the utility asks for the Web Server instance directory. At the end of the configuration, the utility asks you to manually deploy the war file to the web container used by Access Manager and modify the classpath.
Workaround
To configure commadmin properly, using Application Server as the web container, take the following steps:1. When you perform the commadmin configuration, when asked for the Web Server Instance Directory, enter the Application Server instance directory instead of the web server instance directory. By default, the Application Server instance directory should be in the following directory:
/var/opt/SUNWappserver7/domains/domain1/server1
2. After you complete the commadmin configuration, find the server.xml file in the Application Server configuration directory. By default, the server.xml file should be in the following directory:
/var/opt/SUNWappserver7/domains/domain1/server1/config
Search for server-classpath and add the following to server-classpath:
app-server-root/domains/domain1/server1/applications/j2ee-modules/commcli_1/WEB-INF/classes
3. Deploy the war file as:
cd /opt/SUNWappserver7/bin
./asadmin deploy --user "admin user name" --password "admin user password"
--host hostname --port 4848 --name commcli --contextroot
commcli /opt/SUNWcomm/lib/jars/commcli-server.war4. Restart Application Server as follows:
cd /var/opt/SUNWappserver7/domains/domain1/server1/bin
./stopserv ; ./startservcommadmin configuration fails during the config-wbsvr task. (5011077)
In rare cases, the config-wbsvr task fails during the configuration of commadmin (after Messaging Server has been installed and configured).
Workaround
Do not install Portal Server before you configure commadmin. Install Portal Server after you have completed configuring commadmin.Cannot modify non-ASCII groups. (4934768)
If a group is created with a group name that contains non-ASCII characters, it cannot be modified with the commadmin group modify command.
For example, if a group with the non-ASCII characters XYZ is specified with the -G option in the commadmin group create command, an email address of XYZ is automatically added to the group’s LDAP entry. Since non-ASCII characters are not allowed in email addresses, modifying the group with commadmin group modfiy fails.
Workaround:
Use the -E email option when creating a group. This option will specify the group’s email address. For example: commadmin group create -D admin -w password -d siroe.com -G XYZ -S mail \ -E testgroup@siroe.com.Creating a group with multiple -f options adds only one attribute. (4931958)
If you specify multiple -f options for creating dynamic groups in the commadmin group create command, only the value specified with the last -f option is added to the LDAP entry. The other values are not added.
Workaround:
Do not specify the -f option multiple times when using the commadmin group create command.External members cannot be added to or removed from groups passing the -M option to the group modify command. (effect of 4930618)
You cannot use the -M option with the commadmin group modify command to add or remove external group members from groups.
Workaround:
Use the -A option to pass the attribute name mgrpRFC822MailMember and its desired value to the group modify command, as in the following examples:./commadmin group modify -D admin -w password -G Group1 -A +mgrpRFC822MailMember:usr100@iplanet.com
./commadmin group modify -D admin -w password -G Group1 -A
\\-mgrpRFC822MailMember:usr100@sun.com
Connector for Microsoft OutlookThis section contains the latest information that is not contained in the product documentation and is missing from the Release Notes for the Connector for Microsoft Outlook
Under the heading “Shared Calendar LDAP Lookup Configuration”, the example of how to set the calmaster ACI for proxy authentication is out of date.
The following example shows the correct ACI for the root suffix (node):
dn: o=usergroup
changetype: modify
add: aci
aci: (targetattr="icscalendar || cn || givenName || sn || uid ||
mail")(targetfilter=(objectClass=icscalendaruser))(version 3.0; acl
"Allow calendar administrators to proxy -
product=ics,class=admin,num=2,version=1"; allow (proxy) groupdn =
"ldap:///cn=Calendar Administrators,ou=Groups,o=usergroup";)For the domain basedn node, the following example shows the correct ACI:
dn: o=sesta.com,o=usergroup
changetype: modify
add: aci
aci:(targetattr="icscalendar || cn || givenName || sn || uid || mail")(targetfilter=(objectClass=icscalendaruser))(version 3.0; acl "Allow calendar users to read and search other users - product=ics,class=admin,num=3,version=1"; allow (search,read) userdn = "ldap:///uid=*, ou=People, o=sesta.com, o=usergroup";)If there is no domain, add this ACI to the root suffix itself by removing the o=sesta.com part on the dn: line.
The Calendar Server configuration program, csconfigurator.sh, adds these ACIs. If you are upgrading from Java Enterprise System Release 1, you must rerun the configuration program to get these updated ACIs.
How to Report Problems and Provide FeedbackIf you have problems with Sun Java System Calendar Server, contact Sun customer support using one of the following mechanisms:
http://sunsolve.sun.com/pub-cgi/show.pl?target=help/collections
This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.
So that we can best assist you in resolving problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
To assist in reporting problems, Sun provides the capture_environment.pl tool, a Perl script that captures the current Calendar Server environment, including the ics.conf file, log files, calendar database files, platform information, and core files (if available). These files can be useful to Calendar Server development to debug problems.
To run the capture_environment.pl tool:
- If necessary, download the capture_environment.pl tool from customer support.
- If necessary, install Perl and add it to your path. (If you cannot install Perl, see the instructions in the capture_environment.pl file that describe how to manually create a snapshot of your Calendar Server environment.)
- Log in as (or become) root.
- Run the capture_environment.pl tool. The tool copies the files to a directory named archive_directory. On UNIX systems, it places all files into a tar file named tar_file. On Windows 2000 systems, however, you must manually add the files in archive_directory to a Zip file.
- Send the tar_file or Zip file to customer support.
Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this URL
http://www.sun.com/hwdocs/feedback
Please include the part number (819-0023-10) and title (Sun Java System Calendar Server 6 2005Q1 Release Notes) in the subject line of your email.
Additional Sun ResourcesUseful Sun Java System information can be found at the following Internet locations:
- Documentation for Sun Java System Calendar Server 6
http://docs.sun.com/coll/CalendarServer_04q2- Sun Java System Documentation
http://docs.sun.com/prod/entsys_04q2- Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Software Products and Service
http://www.sun.com/software- Sun Java System Software Support Services
http://sunsolve.sun.com/pub-cgi/show.pl?target=help/collections- Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software- Sun Support and Training Services
http://www.sun.com/supportraining- Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Developer Information
http://developers.sun.com/prodtech/index.html- Sun Developer Support Services
http://www.sun.com/developers/support- Sun Java System Software Training
http://www.sun.com/software/training- Sun Software Data Sheets
http://wwws.sun.com/software
Copyright © 2004 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright © 2004 Sun Microsystems, Inc. Tous droits réservés.
Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plus des brevets américains listés à l'adresse http://www.sun.com/patents et un ou les brevets supplémentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propriété de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants développés par des tierces parties.
Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.