Sun Java System Instant Messaging 7 2005Q1 Release Notes
Sun Java System Instant Messaging Release Notes
Version 7 2005Q1
Part Number 819-0428-10
These Release Notes contain important information available at the time of release of Sun Java System Instant Messaging 7 2005Q1. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Instant Messaging 7 2005Q1.
To ensure the best deployment with Instant Messaging, you should download the latest patches for this version of the product from http://sunsolve.sun.com. For a complete list of bugs fixed in the patch, please refer to the patch README file.
The patch numbers are as follows:
The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation. These release notes contain the following sections:
Third-party URLs are referenced in this document and provide additional, related information.
Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
About Instant Messaging 7 2005Q1
Sun Java System Instant Messaging delivers secure presence and extended real-time messaging, enabling communities of users to communicate and collaborate instantly and securely. It combines instant messaging capabilities with conferences, alerts, news, polling and file transfer to create a rich collaborative environment. It leverages an existing community, managed using LDAP, Sun Java System Identity Server or Sun Java System Portal Server.
This section includes:
What’s New in This Release
This section includes the following topics:
The Instant Messaging Installation Guide has been discontinued. If you are installing Instant Messaging 7 2005Q1 for the first time, see the Sun Java System Enterprise System Installation Guide for installation instructions. If you are upgrading from a previous release of Instant Messaging, see the Sun Java System Upgrade and Migration Guide for instructions.
This section describes the following new features added to Instant Messaging in this release:
Updated and Improved Instant Messaging Client
New icons, streamlined features, and new XMPP functions, like multiple Instant Messaging sessions, presence features, subscription authorization, roster management, and logging capabilities.
The IETF eXtensible Messaging and Presence Protocol (XMPP)
With XMPP, Instant Messaging interoperates with the public networks through open source gateways. A user can aggregate contacts for all services on a client that supports XMPP (for example, GAIM and Exodus). In addition, XMPP support facilitates the integration of other third party applications as well as extensions of the existing functionality.
Enhanced Monitoring Features
The watchdog feature monitors if Instant Messaging is up or down, and it restarts the service if it is down. The Java Enterprise Service monitoring framework provides performance metrics on length of time for authentication, message delivery, and the number of instant messages sent through the service.
Re-architected Calendar Server Integration Support
How calendar notification is relayed as an instant message has changed from previous releases. New features include:
Troubleshooting Diagnostics for the Client
The About dialog box describes product copyright information. Additionally, the Details tab lists system, client, server, and session information that, in the event of a problem, end users can copy and paste into an email and send to their administrator or technical support center.
Multidomain functionality in News Channels and Conferences
News channels and conferences now support users from multiple domains.
New User Registration
You can now customize Instant Messenger to allow users to add themselves to the directory.
Simplified Sun Java System Access Manager Schema
The attributes sunPresenceDefaultAccess, sunPresenceEntityDefaultAccess, sunPresenceAccessDenied, sunPresenceEntityAccessDenied, sunPresenceAccessPermitted, and sunPresenceEntityAccessPermitted are obsolete. These attributes have been replaced by the attributes sunPresencePrivacy and sunPresenceUserPrivacy. The obsolete attributes are still in the schema, but are not visible from the Sun Java System Access Manager console, and are not used.
Hardware and Software Requirements
This section lists the requirements for installing Instant Messaging software. Before you install, ensure you have met the minimum hardware and operating system requirements. JRE 1.4 is supported by both server and client. In addition, check for any product patches before you install.
For the current list of required patches for Sun Java System Instant Messaging go to http://sunsolve.sun.com and select either “Patches” or “Patch Portal”. Follow the Sun Java System Instant Messaging links. As 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.
The following hardware and software are required for this release of Instant Messaging software.
Server Operating System Requirements
This release of Sun Java System Instant Messaging supports the following platforms:
- Solaris 8 (5.8) Operating System (SPARC� Platform Edition)
- Solaris 9 (5.9) Operating System (SPARC� Platform Edition)
- Solaris 9 (5.9) Operating System (x86 Platform Edition)
- Solaris 9 (5.9) Operating System (Opteron Platform Edition)
- Solaris 10 Operating System (SPARC� Platform Edition)
- Solaris 10 x86 Operating System (x86 Platform Edition)
- Solaris 10 Operating System (Opteron Platform Edition)
- Red Hat Enterprise Linux AS 2.1 and AS 3.0.
A list of recommended patches for Solaris can be found at the following location:
Server Software Requirements
This version of Instant Messaging is compatible with the following versions of other server software:
- Sun Java System Access Manager 6 2005Q1
- Sun Java System Application Server Enterprise Edition 8 2005Q1
- Sun Java System Calendar Server 6 2005Q1
- Sun Java System Directory Server 5 2005Q1
- Sun Java System Messaging Server 6 2005Q1
- Sun Java System Portal Server 6 2005Q1
- Sun Java System Web Server 6.1 2005Q1 SP4
Server Hardware Requirements
The minimum hardware requirements for installing Sun Java System Instant Messaging are as follows:
Client Operating System Requirements
This release supports the following client platforms:
Client Software Requirements
On Windows, you can run Instant Messenger using the browser’s java plug-in from the following browsers:
If the client machine has Java 1.4 or a higher version installed, there are no additional requirements to use either Java Plug-in or Java Web Start. Netscape Navigator v7 as well as the recent versions of the Mozilla browser include Java v1.4 or higher. Internet Explorer does not include the latest version of Java. If you experience problems using the client with Java 1.4, upgrade to 5.0. JDK 5.0 is included with Sun Java System Instant Messaging.
If the client machine does not have Java v1.4 or a higher version installed, you need to install Java Web Start. You can download and install Java v1.4. from the following location:
You can download and install Java Web Start from the following location:
HTML links can be exchanged over Instant Messenger and activated from the messenger by clicking them. When a link is activated, the messenger invokes a browser. Table 2 lists supported operating system and browser combinations:
Table 1 Supported Client OS and Browser Combinations
Netscape Communicator 4.7x or later
Red Hat Linux 7.x
Red Hat Linux 8.0 or later
Mozilla 1.2 or later
Mac OS X
Client Hardware Requirements
Instant Messenger uses between 20 and 40 MB of memory on most platforms. You should estimate the memory requirement by including the requirements of other applications (including operating systems) used on the client machine. In most cases, at least 128 MB RAM is recommended in order to run Instant Messenger and other applications comfortably. This number becomes higher when using memory-intensive operating systems.
Bug Fixed in This Release
The following table describes a bug fixed in Instant Messaging 7 2005Q1 since the Early Access release.
Table 2 Fixed Bugs in Instant Messaging 7 2005Q1
Previously on Linux, the monitoring agent was not enabled by default when you installed Instant Messaging. This no longer occurs.
This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:
7 2005Q1 Instant Messenger requires the 7 2005Q1 server. Server-to-server communication is compatible between 6 2004Q2 and 7 2005Q1 releases of the server. No changes are required to the server configuration (in iim.conf) and no migration of other server-related data is required. Refer also to the Sun Java Enterprise System 2005Q1 Upgrade and Migration Guide.
Documentation Updates for Instant Messaging 7 2005Q1
The following documents have been deprecated. The information they contain has been incorporated into the Sun Java System Communications Services 6 2005Q1 Deployment Planning Guide:
In addition, the Sun Java System Instant Messaging 6 2004Q2 Installation Guide material has been deprecated. The information previously found in that book is now available from the following sources:
The rest of this section describes errors and omissions in the documentation.
These features are not described in either the product online help or the quick reference.
The Start Screen launches Instant Messenger. If you are using Java Web Start, press the Start button in the middle of the screen. If you are using Java Plug-in (for Windows users only), press the Java Plug-in button at the top of the screen. The Online Help and Quick Reference buttons display end user product help.
About Dialog Box
The About dialog box describes product copyright information. Additionally, the Details tab lists system, client, server, and session information that, in the event of a problem, end users can copy and paste into an email and send to their administrator or technical support center.
Manage Contact Authorizations
With this feature, you can view the Users Who Can See My Status window. If you delete someone from your list you will still be on the other person's list. This command allows you to revoke contact authorization from users who previously had you in their contact lists. Previously, you could only view this window from the Privacy tab of the Settings window; you can now invoke it through the Tools menu.
Add Recipients Screen
The Add Recipient dialog box and the Search for a User dialog box have been combined into a single dialog box for searching and for adding users.
Session IDs and Priority Settings
“Priority Settings for the Current Session” on the Advanced tab in the Settings window has been removed. Instead, end users select a checkbox to adjust the priority when the status changes (enabled by default). When the checkbox is selected, a user can automatically lower session priority with Idle, Away, and Do Not Disturb statuses.
(Bug #: 6182662) Some new emoticons are not documented in the online help. describes the missing emoticons and their corresponding keyboard shortcuts.
Table 3 Instant Messenger Emoticons
Can of Worms
Mug of Beer
In addition, the online help mistakenly calls the Happy emoticon “Smiley” and the Sleep emoticon “Sleeping”.
Manage Contact Authorizations Menu Item
Selecting Tools|Manage Contact Authorizations displays the Users Who Can See My Status dialog box. See Users Who Can See My Status Dialog Box for more information.
Users Who Can See My Status Dialog Box
(Bug #: 6183638) You can access this dialog box by selecting Tools|Manage Contact Authorizations. This dialog box allows end users to see a list of users on whose contact list they appear, but are not in their own contact list. For example, if User A authorized User B to include User A in User B’s contact list, but did not in turn place User B on their own contact list, User B would appear on the Users Who Can See My Status dialog box for User A. In Instant Messenger, User B is referred to as a watcher of User A. Using the options on this dialog box, User A can then add User B to their own contact list or remove themselves from User B’s contact list.
To Add a Watcher to Your Contact List
- In Instant Messenger, select Tools|Manage Contact Authorizations.
The Users Who Can See My Status dialog box appears.
- Select the name of the watcher you want to add from the list and click Add to Contacts List.
The watcher is added to your contact list with a status of “Approval pending” and an authorization request is sent to the watcher.
To Remove Yourself from a Watcher’s Contact List
User Status Watch Indicator
The online help states that Instant Messenger appends an asterisk (*) to the name of a contact in the contact list when you are watching that user’s status. On some platforms, an exclamation point (!) is used instead of an asterisk.
New User Registration Dialog Box
If you customize Instant Messenger to allow new user registration as described in the Administration Guide, a button is added to the Login dialog box that allows users to access the New User Registration dialog box. Instructions on using this dialog are not included in the online help. The information is available in the Sun Java System Instant Messaging Administration Guide.
Known Issues and Limitations
This section contains a list of the more important known issues at the time of the Instant Messaging 7 2005Q1 release.
Patch updates are issued on a frequent basis. If you encounter a problem while installing or using Sun Java System Instant Messaging, contact Sun Support to enquire about the availability of a fix for this problem. Alternatively, you may consult the Sun web site for patches:
lists the known problems and limitations.
Table 4 Known Problems and Limitations
In order to use font customizations on multibyte characters, you need to type in your text first, then highlight the text and apply the font customizations.
Idle detection is not implemented on Mac OS.
If a user leaves an Instant Messenger session, the user’s absence is not automatically detected.
Mac OS users need to explicitly set their presence status as AWAY, prior to leaving.
Alerts with embedded images are not rendered faithfully.
When a recipient receives an alert with embedded images, the images are not centered and font information present in the accompanying text is lost.
Custom statuses cannot be removed.
The least used statuses are eventually removed. To remove one immediately, add five new customized statuses; the oldest one will disappear.
On MAC OS, trying to print from the Java Web Start client hangs Instant Messenger.
Copy the message and paste it in some other application, then print.
In order to use the client’s drag and drop functionality on Mac OS, you need to use Java 1.4.2 Update 2 which is available in OS X 10.3.
If the Calendar server alarm type is set to text/xml, that is:
caldb.serveralarms.contenttype = "text/xml"
The Reminder field in the Instant Messenger Task Due Reminder alert window is blank.
Set this field to "text/calendar".
Confusing behavior occurs when inviting a user to a conference when that user does not have the correct permissions to join the conference. It appears as if you invited the user, when in fact, the user never received the invitation.
Can’t create conf_room/news using certain gb18030 characters
Since conference and news ACL file names are written using names fed from Instant Messenger, there is a problem creating ACLs when the names contain Tibetan or Arabic characters.
Printing errors occur with Instant Messenger in some locales.
Workaround: Cut and paste the text you want to print to another application that can print.
4893304, 6190592 *
Image files sent as attachments may become corrupted during file transfer.
The scrollbar on Instant Messenger twitches when a new message arrives.
There is no way to discern a read-only from a fully privileged user within a chat room. This may be confusing if a user attempts to send a message to a user with read-only privileges. The read-only user will not receive the message.
Users cannot send messages when a moderator has denied presence access for the user.
When multiple IM Policies are applied to a user, the policies may contradict one another. For example, when the “Regular” and “Conference Room Administrator” policies are attributed to a user, the user is unable to manage conference rooms.
Edit the regular user policy by clearing the “Ability to manage conference rooms” checkbox. This will ensure that the two policies do not conflict.
The Web Poll tab on the Alert window doesn’t display some web pages correctly. This is a limitation of the Java HTML renderer.
Send URLs using Message Creation tab instead of the Web Poll tab.
Windows task bar menu labels are not rendered properly in some locales with multibyte characters. The menu functionality is not affected.
In zh_HK locales, Instant Messenger displays English. The zh_HK locale functionality is unavailable at this time.
On Linux, warning messages may be displayed on screen when you run the configure utility. Typically, these warning messages begin with the following text:
WARNING: Cannot parse rpm files by running "/bin/rpm -qp --queryformat
Configure should still work as expected, as no error really occurs.
The NOTICE log level has been deprecated but is still installed as the default log level for Instant Messaging. To resolve this, the server treats NOTICE as INFO and all information typically logged for INFO is also logged.
On Solaris and Linux, attachments to Instant Messaging messages that would normally be viewed in a web browser, such as .jpg files, cannot be opened. The path given to the web browser is incorrect.
An end user is able to view archived data in search results; this is a problem with the archive provider.
It appears that users can set conference room or news channel access rights without first selecting a conference room or news channel. This is misleading.
News message properties are not sent with news messages. As a result, the following client capabilities may be affected:
In server-to-server communications, news channel access rights may not work for end users. For example, a user whose access is set to NONE is able to have READ access.
In server-to-server communications, an end user subscribed to a news channel on a different server is unable to chat with the message creator of the news channel.
In server-to-server communications, access rights for end users, such as NONE, READ, and WRITE, do not function properly in conference rooms.
Users are given the option to change presence status while Instant Messenger is not connected to the server. Any modifications made to status while disconnected do not take effect.
If you create a new contact group in Instant Messenger but do not assign any contacts to the group, then logout and log back in, the contact group no longer appears in the contact list.
Workaround: Add a contact to the contact group before logging out of Instant Messenger.
When an end user deletes an active privacy profile, the server still continues to apply the deleted active privacy profile even though the Instant Messenger client shows the privacy profile to be deleted.
Workaround: When an end user deletes an active privacy profile the Instant Messenger client now automatically activates the “Visible to All” privacy profile. End users need to make a different privacy list active and then reactivate the “Visible to all” profile.
User status remains online even after the network connection is lost.
The Instant Messenger Login dialog box does not necessarily display the server the end user last successfully logged into. This behavior is inconsistent with the behavior for username, where the last successfully used username is displayed in the Login dialog box.
Instant Messenger does not warn users of the potential risk of accepting an invalid certificate.
Unable to register a new user with a server that does not mandate a password field. This is because Instant Messenger views the password field as required even if the server does not.
If you delete a folder from your contact list that is not empty, you also delete the contacts within that folder. However, in doing so, you also remove yourself from the contact list of any contacts that were present in that folder. For example, if:
The following occur:
User B needs to manually re-add User A as a contact.
5097769, 6186250, 6199158 *
Formatting errors occur in multiline messages from Gaim clients, such as breaks between the lines.
5099172, 6187165 *
Web browsers do not always load the online help or URLs sent in chat messages.
Workaround: For URLs sent in chat messages, copy the URL and paste it in the web browser. For online help, bring up the Instant Messenger home page in the web browser and click the Online Help link on that page.
The presence status is displayed as idle while displaying the online icon in the status bar.
By default, no Calendar agent parameters are listed in iim.conf. However, when invoked, imadmin looks for the iim_agent.enable parameter in the configuration file and if it is not present, imadmin proceeds as though the parameter is set to true (enabled). As a result, the watchdog will start the Calendar agent periodically even if you have omitted it from the iim.conf file.
A presence status mismatch between the contact list and the status bar occurs when a user changes their status to Invisible and then relaunches Instant Messenger.
Changes users make on the Settings dialog box Privacy tab are saved as the changes are made, not when the user clicks OK. For this reason, if you click Cancel after making changes on this tab, the changes are saved anyway.
On Windows machines running JDK 1.4.2, if the network connection goes down while the client is running, the client’s Java process may suddenly consume 90% or more of the CPU usage for the system. This does not occur if the Instant Messaging server is shut down, only if the network connection is lost.
Upgrade to JDK 5.0 on client systems running Windows.
Sometimes, attachments larger than 20 KB, that are sent through Instant Messenger may cause a Java out of memory error. When this happens, the attachment is not sent.
Sometimes a few initial chat messages are lost while Instant Messenger loads the chat window.
The online help does not describe the Users Who Can See My Status dialog box. See Users Who Can See My Status Dialog Box for a description and for procedures associated with this dialog box.
If a user attempts to create a conference room using a name that already exists, the user is added to the existing conference instead of being warned that the conference name is already in use.
Workaround: Exit the conference and choose a new name for the new conference.
An additional carriage return may be added when cutting and pasting text in Instant Messenger.
If you install the Sun Java System Access Manager on a different host from the Instant Messaging server, you need to manually copy the imServices files from the Instant Messaging server host to the Access Manager host after you run the configure utility.
To do this:
- Locate the imService_*.properties files on the Instant Messaging server host. By default, these files are located under /opt/SUNWiim/lib/ on Solaris and /opt/sun/im/lib/ on Linux.
- Copy the files to the locale directory on the Sun Java System Access Manager host. By default this directory is /opt/SUNWam/locale on Solaris and /opt/sun/identity/locale on Linux.
For locales other than English, for example Japanese, you can't change access rights for conference room to READ. Instead, when you save, the access right is changed to NONE.
You cannot send a message to a conference when the conference name contains multibyte characters.
Workaround: Use English for conference names.
When you add a user to your contact list, the Conference tab gains the focus in the Instant Messenger client’s main window instead of the Contacts tab.
Sometimes when network connectivity is lost, the Instant Messenger client hangs. When this happens, you need to terminate the Instant Messenger Java process:
You cannot search for conference names that contain multibyte characters.
Workaround: Use English for conference names.
Instant Messenger draws the window size too small causing the “input” block to be below the bottom of window on MAC OSX.
The title and sender may not be displayed in the News window.
Cancelling out of the Registration dialog box throws an exception and may prevent other Instant Messenger functionality from working correctly.
By default, you cannot send multiline messages from the chat window.
Workaround: Press Ctrl+Enter instead of Enter to type a second line before sending a message.
Restarting the Calendar server can cause the Calendar agent to experience an out of memory error.
Selected recipients do not show up in poll recipient lists.
In Conference and News Channels, you need to set default access for users before granting special access.
The multiplexor does not gracefully shut down all client connections when it stops. This may lead to presence inconsistencies such as Instant Messenger displaying online status when it is no longer connected.
You cannot send a single multibyte character message.
Workaround: Send more than one multibyte character at a time.
If you type some Japanese characters in the chat window and then copy and paste the characters again in the chat window, you will not be able to see the pre-edit strings in the chat window.
Workaround: Close and re-enter the chat or conference window.
In some locales that use multibyte characters, you cannot invoke Instant Messenger using Java Web Start in a deployment with Sun Java System Portal Server.
If you log out and log back into Instant Messenger some presence information about users in the contact list may be lost. The presence information for those users should be updated when the client receives a presence update from the server. This may take some time.
The first time a user sends a file to another user with Instant Messenger, the file is lost
Workaround: Resend the file.
Migration from IM 6 2004Q2 to IM 7 2005Q1 results in loss of some of the contact list information.
On Linux, if the openLDAP client RPM is not installed, imServiceConfigure may fail when trying to run ldapmodify.
Sometimes when you invite another user into a conference, several tabs appear in the conference window.
If you change access permissions for users already in a conference room, the changes do not take effect until you relaunch the conference room window.
Workaround: Close and relaunch the conference room window to update access permissions.
If you are using the French localized version of the resource files, you need to add an escape character to the apostrophes in the following resource files:
Change l'aide to l\'aide in the following lines:
onmouseover="window.status='Lancer Messenger r l'aide du plug-in Java'; return true"
onfocus="window.status='Lancer Messenger r l'aide du plug-in Java'; return true"
onmouseover="window.status='Lancer les rubriques de l'aide en ligne'; return true"
If you rename a contact in the contact list, then add the user to another group in the contact list using the original name, the renaming is lost.
In a deployment with Sun Java System Access Manager, after an upgrade, you may receive configuration errors that suggest that the upgrade failed to find amconfig.properties under /etc/opt/SUNWam. There is no amconfig.properties file in that directory, however the upgrade completes as expected.
While running the configure utility in Japanese, some of the screen element titles are truncated.
Workaround: Expand the window to view all the text.
Email alerts that contain multibyte characters may be unreadable. The subject is readable, but the body of the message is not.
If you post a message to a news channel then log out without viewing the message you just posted, the message appears to be lost. The messages are there, just not visible.
Workaround: View any messages you post to news channels before logging out of Instant Messenger, or unsubscribe and resubscribe to that news channel.
Instant Messaging service fails to start after upgrade.
Workaround: Remove SUNWiimdv package before upgrading.
The news channel administrator does not get notification of new messages posted.
Changes made to a user entry in the LDAP directory are not reflected in Instant Messaging until the cache is revalidated. By default this happens every 10 minutes or every time the Instant Messaging server is started.
Workaround: Restart the Instant Messaging server.
On a machine with less than the required memory, the configure utility may complete configuration of Instant Messaging, but also throw exceptions.
Workaround: Ensure that your system meets the minimum memory requirements before installing or running the configure utility. If you still encounter this problem, run the following:
* Indicates defects that will be addressed in a patch shortly after release. Refer to the beginning of these Release Notes for a list of upcoming patches.
Sun Java System Instant Messaging 7 2005Q1 does not contain any files which you can redistribute.
How to Report Problems and Provide Feedback
If you have problems with Sun Java System Instant Messaging, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at:
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
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title of this document is Sun Java System Instant Messaging 7 2005Q1 Release Notes, and the part number is 819-0428-10.
Additional Sun Resources
Useful Sun Java System information can be found at the following Internet locations:
- Documentation for Instant Messaging
- Sun Java System Documentation
- Sun Java System Consulting and Professional Services
- Sun Java System Software Products and Service
- Sun Java System Software Support Services and Knowledge Base
- Sun Support and Training Services
- Sun Java System Developer Information
- Sun Developer Support Services
- Sun Software Data Sheets
Copyright � 2005 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.
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 � 2005 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 plusieurs des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou des brevets des 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.