Sun ONE Instant Messaging 6.1x Release Notes

These release notes contain important information available at the time of release of Sun™ Open Net Environment (Sun ONE) Instant Messaging versions 6.1x (all platforms) and 6.1 Patch 1 (Solaris). New features and enhancements, known limitations and problems, technical notes, and other information are addressed here. Read this document before you begin using Instant Messaging.


Note	Solaris Only. Install Sun ONE Instant Messaging 6.1 and then immediately install 6.1 Patch 1. On other platforms, the 6.1 software contains the fixes incorporated into the Instant Messaging 6.1 Patch 1 for Solaris. You can download 6.1 Patch 1 for Solaris from the following location: http://sunsolve.sun.com For Solaris 8 and 9 the patch IDs are as follows: Sparc: 115732 x86: 116645

Revision History

Table 1 Revision History
Date	Description of Changes
October 14, 2003	Initial draft of release notes.
November 14, 2003	Added 6.1p1 (Solaris).
December 1, 2003	Changed date to December, removed fixed bugs from bug list, modified several bugs to include workarounds.
December 4, 2003	Added documentation errata and localization information.
December 22, 2003	Added localization bugs and errata.
September 13, 2004	Added localization bugs.

About Instant Messaging

Sun ONE 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 ONE Identity Server or Sun ONE Portal Server.

Localized Versions of the Software

The English software distribution contains localization packages. However, use of these packages is not recommended. Instead, please use the download or CD distribution officially localized and labeled for your chosen language.

New Features in This Release

Documentation

All product documentation for Sun Microsystems can be found at the following location:

The most up-to-date version of these release notes can be found at the Sun ONE documentation web site http://docs.sun.com/prod/s1instmsg. 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 manuals.

In addition to these release notes, the Sun ONE Instant Messaging documentation set includes the following documents:

Hardware and Software Requirements

This section lists the requirements for installing the Sun ONE 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.

Server Operating System Requirements

Server Software Requirements

This version of Instant Messaging is compatible with the following versions of other components of JES:

Server Hardware Requirements

The minimum hardware requirements for installing Sun ONE Instant Messaging are as follows:

Client Operating System Requirements

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 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:

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:

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 such as Windows XP.

Table 2 Supported Operating System and Browser Combinations
Operating System	Browser
Solaris	Netscape Communicator 4.7x or later
Red Hat Linux 7.x	Netscape 4.7
Red Hat Linux 8.0 or later	Mozilla 1.2 or later
Windows 98/ME/NT/2000/XP	no restrictions
Mac OS X	no restrictions

New Information

This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:

Installation Notes

See Table 3 in the Known Issues section that follows for the known installation issues.

Compatibility Issues

6.0 Instant Messenger can communicate with the 6.1 release of the server; however, the 6.1 Instant Messenger requires the 6.1 server. Server-to-server communication is compatible between 6.1 and 6.0 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 section on upgrading in the Sun ONE Instant Messaging Installation Guide.

Errata and Instant Messaging Documentation Updates

Known Issues

This section contains a list of the more important known issues at the time of the Instant Messaging 6.1x release.

Patch updates are issued on a frequent basis. If you encounter a problem while installing or using Sun ONE 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:

Table 3 Known Problems and Limitations
ID	Summary
4609599	Font customizations have no effect on Japanese or Chinese characters. When using the Messenger client, if the Bold, Italic or Underline button is pressed prior to entering Japanese or Chinese characters, the buttons have no effect on the displayed font of the characters. Workaround: Highlight the string first, then press Bold, Italic, or Underline.
4632723	Idle detection is not implemented on Mac OS. If a user leaves an Instant Messenger session, the user’s absence is not automatically detected. Workaround: Mac OS users need to explicitly set their presence status as AWAY, prior to leaving.
4684196	Cannot launch HTML file directly from an alert message on Mac OS. Workaround: In order for the link to work, users need to include the link in the message using the “include link” command instead of using “attach”.
4795970	On Solaris, when the Instant Messaging server is used with Sun ONE Identity Server, the Instant Messaging server will not run under a user other than root. Workaround: In this situation the Instant Messaging server must run with root privileges. If you installed the Instant Messaging server under a different user, modify the iim.conf configuration file to include the following lines: iim.user=root iim.group=other
4806791	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.
4810627	When using the command-line installation, navigation back to a previous page is not possible. During a command-line installation, a user should be able to return to their previous page of choices by entering a left-angle bracket (“<“) command. This does not work correctly. Workaround: Either use the GUI-based installer or restart the command-line installer and try again.
4822841	Presence access control does not work across federated Instant Messaging servers. If a user is logged onto one Instant Messaging server (allowing everyone to access their presence by default) and subsequently denies presence access to another user (who is logged in to another server), the first user’s presence is still available even though it has been denied.
4823015	Keyboard navigation of server combo box does not work on the login dialog boxes. Workaround: Use the mouse to select the desired server.
4846542	On MAC OS, trying to print from the Java Web Start client hangs Instant Messenger. Workaround: Copy the message and paste it in some other application, then print.
4849527	On Solaris, sometimes the multiplexor hangs during shutdown or refresh. Workaround: If this occurs, you need to kill the multiplexor process. Remove all files in the lock directory and restart the server. By default, the lock directory is as follows: /var/opt/SUNWiim/default/lock
4851386	If you backspace over the first character of a chat message, the entire message is deleted. Workaround: Use the delete key to remove the first character.
4852882	Instant Messenger Task Due Reminder has blank Reminder field if text/xml format is used. 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. Workaround: Set this field to "text/calendar".
4858320	Confusing behavior 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 receives the invitation.
4860906	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.
4862326	Messenger uses all swap space on SunRay server. In SunRay deployments, situations have arisen where a client session of one of the users consumed all the memory of the system. This problem is still under investigation, and a patch will be made available soon. Workaround: Run the messenger as an application. Modify the following script for your environment, for example change file paths and server names as necessary, then make it available to users through the web server: #!/bin/sh # Location of Instant Messaging resource files LIBDIR="./lib" # Java command. Modify if necessary. JAVA_CMD="/usr/j2se" # Instant Messaging server name and port and the URL of Instant Messaging resources SERVER=im.example.net:29909 CODEBASE=http://www.example.net:8080/im # Language if [ "$LANG" == "C" ] ; then $locale="en" else $locale=‘echo $LANG \| cut -d _ -f 1‘ fi LD_LIBRARY_PATH=${LIBDIR}:$LD_LIBRARY_PATH export LD_LIBRARY_PATH IM_CLASSPATH=${LIBDIR}/messenger.jar:${LIBDIR}/imnet.jar: ${LIBDIR}/${locale}/imbrand.jar:${LIBDIR}/${locale}/imres.jar: ${LIBDIR}/jcert.jar:${LIBDIR}/jnet.jar:${LIBDIR}/jsse.jar: ${LIBDIR}/imdesktop.jar:${LIBDIR}/icalendar.jar: ${LIBDIR}/javaws.jar:${LIBDIR}/imjni.jar echo "Starting Instant Messenger on $SERVER ..." $JAVA_CMD -classpath $IM_CLASSPATH com.iplanet.im.client.iIM server=${SERVER} help_codebase=${CODEBASE}/${locale}/imhelp > /dev/null 2>&1
4870433	Some Conference Rooms may not appear if you change the locale in which the server runs. Workaround: Set the locale before executing the imadmin script.
4871150	In Instant Messenger, you cannot print using the Print command from the File menu. Workaround: Save the chat text as HTML and then print the message.
4873096	Smile image is displayed when Japanese characters are entered in combination with a “)”.
4886774	Some Japanese characters cannot be displayed. Workaround: Use Java 1.4.2.
4896401	Uninstall can't delete the directory /opt/SUWiim. Workaround: Remove remaining files manually
4897762/4902642	Spaces between multi-byte characters are not displayed in chat windows.
4912429	Pressing the Control key while dragging and dropping a contact from one folder to another does not copy the contact as expected. Workaround: Select the folder to which you want to add the contact and manually add the contact to the folder using the Add Contacts command from the File menu.
4918238	Asian characters appear very small in some parts of the Instant Messenger client. Workaround: Provide custom values as required for the following optional look and feel classes in imbrand.properties: messenger.lookandfeel messenger.lookandfeel.SunOS messenger.lookandfeel.Linux messenger.lookandfeel.Windows messenger.lookandfeel.MacOS
4922347	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.
4929247	Users cannot send messages when a moderator has denied presence access for the user.
4929321	The client displays the wrong product version number in localized versions.
4937939	If you uncheck Enable Sounds in the Sounds panel of the Settings window, exit the Settings window and then reopen the Settings window, the Play Sound When checkboxes are not grayed out. However, the sounds are disabled.
4942415	On Solaris, you may receive an error message similar to the following while executing the configure script from the graphical user interface. An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0xF16B2684 Function=XCreateIC+0x6C Library=/usr/openwin/lib/libX11.so.4 Workaround: Configure Instant Messaging using the command-line. See the Sun ONE Instant Messaging Installation Guide for instructions.
4942613	Calendar reminder alert functionality does not work on Linux.
4944558	The Web Poll tab on the Alert window doesn’t display some web pages correctly. This is a limitation of the Java HTML renderer. Workaround: Send URLs using Message Creation tab instead of the Web Poll tab.
4949073	Running configure twice causes the configure utility to fail and generate errors. Workaround: Do not run the configure utility after your initial configuration is set up. Instead, modify your configuration as described in the Sun ONE Instant Messaging Administrator’s Guide.
4949358	Unable to configure Instant Messaging to work with BEA Web Container. Workaround: 1. Create a file named installation directory/SUNWiim/lib/imServiceConfigure. Where installation directory is the directory in which you installed Instant Messaging. 2. Add the following contents to the file: DS_DIRMGR_DN=Directory manager DN DS_DIRMGR_PASSWORD=Directory manager password DS_HOST=LDAP server hostname DS_PORT=LDAP server port DS_BASE_DN=LDAP server base dn 3. Add the following line in installation directory/SUNWiim/lib/imServiceConfigure: JAXP_HOME=/usr/share/lib 4. Run the configure utility as follows: installation directory/SUNWiim/lib/imServiceConfigure
4951518	Instant Messenger fails to launch in locales with explicit country/locale code. The following locales are supported by default: de, en, en_US, es, fr, ko, ja, zh, zh_TW. In order to support clients with locales that contain other explicit country specifications, such as de_AT, fr_CA, es_AR, you need to configure additional symbolic links on the server. You may receive a java.lang.NullPointerException if you do not set up additional symbolic links for these locales. Workaround: Create a symbolic link from the explicit locale to the more general locale in the directory where the Instant Messenger resources are installed. For example, you would create a symbolic link from de_DE to de as follows: cd messenger resource directory ln -s de de_DE
4956332	When a message is posted to the News channel, no sound is played.
4956554	Alert and Chat functions do not work with LDAP groups.
4962508	Configure fails when JRE instance is not installed in /usr/j2se. Instant Messaging uses the $JAVA_HOME environment variable to find the location of the version of the Java SDK that it requires. When you install Instant Messaging, the installation program installs Java 2 SDK 1.4.1 into /usr/jdk/.j2se1.4.1_06. If the $JAVA_HOME environment variable is set to some other path, configure will fail. Workaround: Modify the $JAVA_HOME environment variable to point to the Java 2 SDK 1.4.1 version installed with the product.
4962709	Red Hat Linux 7.3 user can not add Java Web Start plug-in. By default, the Red Hat Linux 7.3 package does not contain libgcc_s.so.1. You need to download this file from Red Hat’s website before you can run the Instant Messenger client using Java Web Start on a machine where Red Hat Linux 7.3 is installed. For more information, please see Red Hat’s website at: http://www.redhat.com
4963412	Uninstalling Help mentions a stop button, but no stop button available. The online help provides erroneous instructions for stopping the uninstallation of Instant Messaging. Specifically, the instructions tell you to click Stop to stop the uninstallation. In fact, there is no stop button, and no way to stop the uninstallation.
4963565	Multi-byte file names are displayed incorrectly when saving or attaching on Linux.
4963555	A misleading warning message appears when the multiplexor is started. Workaround: Change /root directory permission to 755. Change the top line of imadmin from "#!/bin/sh" to "#!/bin/sh -x". Use Java 1.4.2 or higher version and set the JAVA_HOME variable appropriately.
4964571 4964575	On Linux, when installing into some locales, the text in the graphical user interface may display incorrectly.
4970878	Code text appears in online help when using Netscape 4.7 browser. Workaround: Use Netscape 7.1.

How to Report Problems and Provide Feedback

If you have problems with Sun ONE Instant Messaging, contact Sun customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Additional Sun Resources

Sun, Sun Microsystems, the Sun logo, Solaris, Java and the Java Coffee Cup logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Use of Instant Messaging is subject to the terms described in the license agreement accompanying it.

Sun™ ONE Instant Messaging Release Notes

Version 6.1 (All Platforms)

Version 6.1 Patch 1 (Solaris)