Version 7 2005Q4
These Release Notes contain important information available at the time of release of Sun JavaTM System Instant Messaging 7 2005Q4. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Instant Messaging 7 2005Q4.
To ensure the best deployment with Instant Messaging, you should download the latest patches for this version of the product from SunSolve Online.
The most up-to-date version of these release notes can be found at the Sun Java System documentation web site. 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.
Date |
Description of Changes |
Part Number |
---|---|---|
June 2005 |
Beta Release |
819-2568 |
October 2005 |
Final Release |
819–2568 |
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 Access Manager, or Sun Java System Portal Server.
This section includes the following topics:
The Instant Messaging Installation Guide has been discontinued. If you are installing Instant Messaging 7 2005Q4 for the first time, see the Sun Java Enterprise System Installation Guide for installation instructions. If you are upgrading from a previous version of Instant Messaging, see the Sun Java Enterprise System Upgrade Guide.
If you are using Access Manager with Instant Messaging you need to install the “Legacy (version 6.x style)” Access Manager using the Java Enterprise System installer. This version of Instant Messaging is not compatible with the “Realm (version 7.x style)” Access Manager.
This section describes the following new feature added to Instant Messaging in this release:
This release of Instant Messaging provides failover support for Solaris, using Sun Cluster. This increases Instant Messaging's availability and providing monitoring of and recovery from software and hardware failures.
See Configuring Instant Messaging for High Availability (Solaris Only) for more information about this feature.
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 SunSolve Online 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 hardware and software requirements for this release of Instant Messaging software are described in the following sections:
This release of Sun Java System Instant Messaging supports the following platforms:
SolarisTM 8 (5.8) Operating System (Solaris OS) (SPARC® Platform Edition)
Solaris 9 (5.9) OS (SPARC Platform Edition, x86 Platform Edition, and Opteron Platform Edition)
Solaris 10 OS (SPARC Platform Edition, x86 Platform Edition, 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 SunSolve Online.
This version of Instant Messaging is compatible with the following versions of other server software:
Sun Java System Access Manager 7 2005Q4
Sun Java System Application Server Enterprise Edition 8 2005Q4
Sun Java System Calendar Server 6 2005Q4
Sun Java System Directory Server 5 2005Q4
Sun Java System Messaging Server 6 2005Q4
Sun Java System Portal Server 6 2005Q4
Sun Java System Web Server 6.1 2005Q4 SP5
The minimum hardware requirements for installing Instant Messaging are as follows:
Approximately 300 MB of free disk space for the software.
Approximately 5K of disk space for each user.
At least 256 MB of RAM. The amount of RAM needed depends on the number of concurrent client connections, and whether the server and multiplexor are deployed on the same host.
This release supports the following client platforms:
Solaris 8, 9, and 10
Microsoft Windows 98, ME, NT (SP 6a), 2000, XP
Mac OS X, minimum 10.1
Red Hat Linux, minimum 7.2
On Windows, you can run Instant Messenger using the browser’s Java Plug-in from the following browsers:
NetscapeTM, minimum 4.79
MozillaTM, minimum 1.2
Internet Explorer, minimum 5.5
If the client machine has Java 1.4 or later 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. JDKTM 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 Java Technology website.
You can download and install Java Web Start from the Java Web Start Technology website.
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 3–2 lists supported operating system and browser combinations.
Table 3–2 Supported Client OS and Browser Combinations for Instant Messaging
Operating System |
Browser |
---|---|
Solaris |
Netscape Communicator, minimum 4.79 |
Red Hat Linux 7.x |
Netscape minimum 4.79 |
Red Hat Linux, minimum 8.0 |
Mozilla, minimum 1.2 |
Windows 98/ME/NT/2000/XP |
No restrictions |
Mac OS X |
No restrictions |
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.
If you choose to use Sun Java System Access Manager to store policies when configuring Instant Messaging, policies like the following are created:
Ability to administer Instant Messaging and Presence Services
Ability to change your own Instant Messaging settings
Ability to manage Instant Messaging Conference Rooms
Table 3–3 lists the known incompatibilities between Instant Messaging 7 2005Q4 and earlier versions.
Table 3–3 Instant Messaging 7 2005Q4 Compatibility Issues
Incompatibility |
Impact |
Comments |
---|---|---|
Instant Messaging 7 is incompatible with the 7.x (2005Q4) versions of Access Manager. |
When installing Access Manager, select “Legacy Mode (version 6.x style)” instead of “Realm Mode (version 7.x style)” on the Java Enterprise System installer. | |
Instant Messaging 7 is incompatible with the 2004Q2 versions of Portal Server and Messaging Server. |
Upgrade Portal Server and Messaging Server when upgrading Instant Messaging 7. | |
Due to a protocol change the Instant Messaging 7 2005Q4 server is not able to communicate with a server of an older version in federated deployments. |
Instant Messaging federated deployment sites will need to upgrade all the servers. The existing deployments who do not wish to upgrade the server will have to explicitly set the property of collaboration session factory object to use the legacy protocol implementation. |
You should coordinate the upgrade to limit the length of time during which servers will be unable to communicate with each other. |
Client - Server Communication |
Due to the protocol change the older versions of the client will not be able to communicate with the newer versions of the server and vice versa. |
You will need to upgrade both the client and server at the same time. |
Sun Java System Instant Messaging 6 2004Q2 is incompatible with shared components that ship with Sun Java Enterprise System 2005Q4. |
You will need to upgrade all Instant Messaging components. See the Sun Java System Access Manager release notes for further information about this incompatibility. | |
The Instant Messaging SDK implementation of the Legacy Instant Messaging/Presence protocol is now bundled. |
By default, the Instant Messaging SDK APIs use the implementation based on the XMPP protocol. Applications will have to explicitly set the property of collaboration session factory object to use the Legacy protocol implementation. | |
The SDK component includes additional jar files: The Instant Messaging SDK uses the JSO (JABBER Stream Objects) libraries. |
In order to take advantage of XMPP, you will need to modify the classpath for older applications using the Instant Messaging SDK. | |
The Instant Messaging 6 2004Q2 server is incompatible with the default behavior of the latest version of the SDK. |
In order to use the 6 2004Q2 server with the current IM SDK you need to set the property of the collaboration session factory object to use the legacy protocol implementation. See Issue Number 6200472 under Known Issues and Limitations for instructions. |
This section contains information about changes to and errors in the documentation in the following sections:
The 2005Q4 release of Instant Messaging uses the following version of the Administration Guide:
Sun Java System Instant Messaging 7 2005Q1 Administration Guide
This section lists the following changes to the Sun Java System Instant Messaging 7 2005Q1 Administration Guide.
Starting, Stopping, and Refreshing Components in an HA Environment
Additional Post-Installation Step for Deployments with Access Manager
Enabling the Instant Messenger Archive Control Component for Java Plug-in
To Enable Instant Messenger Archive Control for Java Plug-in
Storing Archived Messages in a Non-default Portal Server Search Database
Do not use the imadmin start, imadmin stop, or imadmin refresh commands in an HA environment with Sun Cluster. Instead, use the Sun Cluster administrative utilities.
(Issue Number: 6189148) If you install 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 Access Manager host. By default this directory is /opt/SUNWam/locale on Solaris and /opt/sun/identity/locale on Linux.
(Issue Number: 5102072) In this release, the default value of the iim_agent.enable parameter has been changed to false. This change is not reflected in the Administration Guide.
Step 1 of the procedure “To Configure Instant Messaging Server” is incorrect. No package named SUNWiimag exists. Skip this step.
The iim_server.msg_archive.auto configuration parameter is no longer supported although it is incorrectly included in the list of parameters in the Administration Guide.
(Issue Number: 6244099) The Administration Guide procedure for enabling the Instant Messenger Archive Control component for the Java Plug-in is incorrect. Use the procedure described in Changes for HTML applet pages and pluginLaunch.jsp files instead.
If you are using Java Plug-in to launch the Instant Messenger, perform the following steps to enable the Instant Messenger Archive Control feature in the Instant Messenger.
Go to the Instant Messenger documentation root directory and locate the im.html and imssl.html files
By default, the files are installed in the following location:
/etc/opt/SUNWps/desktop/default/IMProvider
Open the .html files in a text editor.
Add or edit the following line as required:
<PARAM NAME="archive_control" VALUE="true" /> <EMBED archive_control=true;/> |
An error occurs in the procedure. Specifically, the following directory:
/etc/opt/SUNWps/desktop/default/IMProvider/
should be:
/etc/opt/SUNWps/desktop/default_locale/IMProvider/
For example:
/etc/opt/SUNWps/desktop/default_ja/IMProvider/
The new user registration feature is not completely described in the Administration Guide. In addition to customizing Instant Messenger, you also need to configure the server to allow new user registration.
To do this, you need to add four configuration parameters to iim.conf then refresh the server configuration. Table 3–4 describes the configuration parameters.
Table 3–4 New User Registration Server Configuration Parameters
Parameter |
Description |
---|---|
iim.register.enable |
If TRUE, the server allows new Instant Messaging end users to register themselves (add themselves to the directory) using Instant Messenger. |
iim_ldap.register.enable |
If TRUE, the server allows new Instant Messaging end users to register themselves (add themselves to the directory) using Instant Messenger. |
iim_ldap.register.basedn |
If self-registration is enabled, the value of this parameter is the DN of the location in the LDAP directory in which person entries are stored. For example: "ou=people,dc=siroe,dc=com" |
iim_ldap.register.domain |
The domain to which new users will be added. For example: directory.siroe.com |
Open iim.conf in a text editor.
Add the configuration parameters and appropriate values as described in Table 3–4.
Save and close iim.conf.
Refresh the server configuration using the imadmin command-line utility.
imadmin refresh server
Do not use the imadmin start, imadmin stop , or imadmin refresh commands in an HA environment with Sun Cluster. Instead, use the Sun Cluster administrative utilities.
(Issue Number: 5070998) An additional undocumented logging parameter has been added to this release to collect XMPP messages in a separate log file.
Open iim.conf.
By default, the iim.conf file is installed in the configuration directory as follows:
On Solaris:
/etc/opt/SUNWiim/default/config/iim.conf
On Linux:
/etc/opt/sun/im/default/config/iim.conf
If you created multiple instances of Instant Messaging, the name of the /default directory will vary depending on the instance.
Enable the following line by removing the comment characters:
iim.log4j.config=log4j.conf |
If the line does not exist, add it.
Save and close iim.conf.
Create a file named log4j.conf and save it to the configuration directory.
Add the following to log4j.conf:
log4j.logger.xmppd=INFO, A1 # DEFAULT TO RollingFileAppender log4j.appender.A1=org.apache.log4j.RollingFileAppender log4j.appender.A1.file=${logdir}/xmppd.log log4j.appender.A1.append=true log4j.appender.A1.maxBackupIndex=7 log4j.appender.A1.maxFileSize=5mb # More example appenders.. # Straight to console.. # log4j.appender.A1=org.apache.log4j.ConsoleAppender # log4j.appender.A1.ImmediateFlush=true # Rollover at midnight.. # log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender # log4j.appender.A1.DatePattern='.'yyyy-MM-dd # log4j.appender.A1.file=${logdir}/xmppd.log # log4j.appender.A1.ImmediateFlush=true # log4j.appender.A1.append=true # Send to SMTP.. # log4j.appender.A1=org.apache.log4j.SMTPAppender # PATTERN LAYOUT AND OPTIONS # DEFAULT TO PatternLayout log4j.appender.A1.layout=org.apache.log4j.PatternLayout # For full dates.. log4j.appender.A1.layout.ConversionPattern=[%d{DATE}] %-5p %c [%t] %m%n # IM traditional output format.. #log4j.appender.A1.layout.ConversionPattern=%d{HH:mm:ss,SSS} %-5p %c [%t] %m%n # More example layouts # XMLLayout for chainsaw consumption # log4j.appender.A1.layout=org.apache.log4j.xml.XMLLayout # TTCCLayout for NDC information # log4j.appender.A1.layout=org.apache.log4j.xml.TTCCLayout # log4j.appender.A1.layout.DateFormat=ISO8601 # log4j.appender.A1.layout.TimeZoneID=GMT-8:00 # log4j.appender.A1.layout.CategoryPrefixing=false # log4j.appender.A1.layout.ThreadPrinting=false # log4j.appender.A1.layout.ContextPrinting=false # Now we list logger/appender/layout for the other default loggers, but # only the defaults.. log4j.logger.iim_wd=ERROR, A2 log4j.appender.A2=org.apache.log4j.RollingFileAppender log4j.appender.A2.file=${logdir}/iim_wd.log log4j.appender.A2.append=true log4j.appender.A2.maxBackupIndex=7 log4j.appender.A2.maxFileSize=5mb log4j.appender.A2.layout=org.apache.log4j.PatternLayout log4j.appender.A2.layout.ConversionPattern=[%d{DATE}] %-5p %c [%t] %m%n # For separate xmpp traffic log, disabled by default. log4j.logger.xmppd.xfer=DEBUG, A3 #log4j.appender.A3=org.apache.log4j.varia.NullAppender # Select next block instead of previous line to enable separate transfer log log4j.appender.A3=org.apache.log4j.RollingFileAppender # log4j.appender.A3.file=${logdir}/xfer.log # log4j.appender.A3.append=true # log4j.appender.A3.maxBackupIndex=7 # log4j.appender.A3.maxFileSize=5mb # log4j.appender.A3.layout=org.apache.log4j.PatternLayout # # Note, simpler default output than above 3 loggers: # log4j.appender.A3.layout.ConversionPattern=[%d{DATE}] %-5p %c [%t] %m%n log4j.logger.agent-calendar=ERROR, A4 log4j.appender.A4=org.apache.log4j.RollingFileAppender log4j.appender.A4.file=${logdir}/agent-calendar.log log4j.appender.A4.append=true log4j.appender.A4.maxBackupIndex=7 log4j.appender.A4.maxFileSize=5mb log4j.appender.A4.layout=org.apache.log4j.PatternLayout log4j.appender.A4.layout.ConversionPattern=[%d{DATE}] %-5p %c [%t] %m%n log4j.logger.net.outer_planes.jso.BasicStream=OFF, A5 log4j.appender.A5=org.apache.log4j.RollingFileAppender log4j.appender.A5.file=${logdir}/jso.log log4j.appender.A5.append=true log4j.appender.A5.maxBackupIndex=7 log4j.appender.A5.maxFileSize=5mb log4j.appender.A5.layout=org.apache.log4j.PatternLayout log4j.appender.A5.layout.ConversionPattern=[%d{DATE}] %-5p %c [%t] %m%n |
Save and close log4j.conf.
Refresh the server:
imadmin refresh server |
Do not use the imadmin start, imadmin stop , or imadmin refresh commands in an HA environment with Sun Cluster. Instead, use the Sun Cluster administrative utilities.
Disabling separate log file creation does not stop XMPP messages from being written to the server log.
Documentation for this feature is available in Configuring Instant Messaging for High Availability (Solaris Only).
The following information is 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), click the Java Plug-in button at the top of the screen. The Online Help and Quick Reference buttons display end user product help.
Table 3–5 describes problems fixed in this Instant Messaging 7 2005Q4 release.
Table 3–5 Fixed Issues in Instant Messaging 7 2005Q4
Issue Number |
Description |
---|---|
5076386 |
When an end user deletes an active privacy profile, the server still continues to apply the deleted active privacy profile even though Instant Messenger shows the privacy profile to be deleted. Workaround: When an end user deletes an active privacy profile Instant Messenger 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. |
6189338 |
Previously, for locales other than English, for example Japanese, you couldn't change access rights for a conference room to READ. Instead, when you saved, the access right was changed to NONE. This no longer occurs. |
6190366 |
When you add a user to your contact list, the Conference tab no longer gains the focus in the Instant Messenger client’s main window. |
6198525, 6207036 |
In Conference and News Channels, you need to set default access for users before granting special access. |
6206530 |
Previously, if you were using the French localized version of the resource files, you needed to add an escape character to the apostrophes in the resource files. You no longer need to do this. |
6211624 |
While running the configure utility in Japanese, some of the screen element titles were truncated. |
6212843 |
Email alerts that contain multibyte characters are now readable. |
6215222 |
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 or set the cache validity interval to a more appropriate number. To change this interval, add the iim.policy.cache.validity parameter and its desired value to iim.conf. |
This section contains a list of the more important known issues at the time of the Instant Messaging 7 2005Q4 release.
Patch updates are issued on a frequent basis. If you encounter a problem while installing or using Instant Messaging, contact Sun Support to enquire about the availability of a fix for this problem. Alternatively, you can consult SunSolve Online for patches.
Table 3–6 lists the known issues and limitations.
Table 3–6 Known Issues and Limitations
ID |
Summary |
|
---|---|---|
4609599 |
In order to use customize the font of multibyte characters, you need to type in your text first, then highlight the text and apply the font customization. |
|
4632723 |
Idle detection is not implemented on Mac OS. If a user leaves an Instant Messenger session, the absence is not automatically detected. Workaround: Mac OS users need to explicitly set their presence status as AWAY, prior to leaving. |
|
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. |
|
4841572 |
Custom statuses cannot be removed. Workaround: The least used statuses are eventually removed. To remove one immediately, add five new customized statuses and the oldest one will disappear. |
|
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. |
|
4852882 |
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 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. |
|
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. |
|
4871150 |
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. |
|
4922347 |
Read-only users and fully privileged users within a chat room are indistinguishable. This might 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. |
|
4929295 |
When multiple Instant Messaging policies are applied to a user, the policies can 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. Workaround: Edit the regular user policy by clearing the “Ability to manage conference rooms” checkbox. This will ensure that the two policies do not conflict. |
|
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. |
|
4960933 |
Windows task bar menu labels are not rendered properly in some locales with multibyte characters. The menu functionality is not affected. |
|
4978293 |
In zh_HK locales, Instant Messenger displays English. Workaround: In order to see traditional Chinese (zh_TW) messages on a machine that uses a zh_HK locale for login, you need to create a symbolic link to zh_TW. |
|
5004449, 5084745 |
On Linux, warning messages might be displayed on screen when you run the configure utility. Typically, these warning messages begin with the following text:
Configure should still work as expected, as no error really occurs. |
|
5042884 |
A problem with the archive provider enables end users to view archived data in search results. |
|
5050973 |
News message properties are not sent with news messages. As a result, the following client capabilities might be affected:
|
|
5051299 |
In server-to-server communications, news channel access rights might not work for end users. For example, a user whose access is set to NONE is able to have READ access. |
|
5051369 |
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. |
|
5051371 |
In server-to-server communications, access rights for end users, such as NONE, READ, and WRITE, do not function properly in conference rooms. |
|
5065241, 5080586 |
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. |
|
5071025 |
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. |
|
5082579 |
User status remains online even after the network connection is lost. |
|
5087303 |
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. Workaround:
|
|
5104840 |
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. |
|
6186465 |
An additional carriage return might be added when cutting and pasting text in Instant Messenger. |
|
6195180 |
The title and sender might not be displayed in the News window. |
|
6200472 |
If you intend to run the Sun Java System Instant Messaging 6 2004Q2 server with the SDK from this release, you will need to explicitly set the property of the collaboration session factory object to use the legacy protocol implementation. The SDK for this release supports the legacy protocol implementation; however, the default is to use the new protocol implementation (XMPP). To use the legacy protocol implementation, you need to use the following constructor to create a CollaborationSessionFactory in the API:
|
|
6203957 |
On Linux, if the openLDAP client RPM is not installed, imServiceConfigure might fail when trying to run ldapmodify. |
|
6205657 |
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. |
|
6213223, 6217766 |
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 the news channel. |
|
6213365 |
Instant Messaging service fails to start after upgrade. Workaround: Remove SUNWiimdv package before upgrading. |
|
6217627 |
On a machine with less than the required memory, the configure utility might 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: Solaris: /opt/SUNWiim/lib/imServiceConfigure Linux: /opt/sun/im/lib/imServiceConfigure |
|
6244099 |
The Administration Guide contains confusing information for enabling the Instant Messenger Archive Control component for the Java Plug-in. This component is not present in this release. |
|
6271708 |
Problems using SSL in a server-to-server environment. Workaround: Download the product patch from SunSolve Online. |
|
6282401 |
Sun Java System Instant Messaging 6 2004Q2 is not compatible with the shared components that ship with this release. Workaround: If you must upgrade the shared components, then upgrade all Instant Messaging components to the current version. |
|
6282887 |
On Windows 2000, in localized versions of Instant Messenger, the first item in the folder pop-up menu does not display correctly. The text should say “Collapse.” Workaround: On client systems, use JDK 1.4.2 instead of JDK 1.5 (5.0). |
|
6286776, 6288533 |
Problems running Instant Messenger in a server-to-server environment. Workaround: Download the product patch from SunSolve Online. |
|
6291159 |
Instant Messenger disconnects from the server after a time period different from the value set for the iim_server.clienttimeout parameter in iim.conf. Workaround: Specify the following system property using the -D option:
Set the value to the number of seconds after which you want Instant Messenger to start sending bytes to the server. These bytes are only used to prevent the time out and subsequent disconnect. |
|
6302273 |
In deployments with Access Manager, if Access Manager times out, Instant Messenger disconnects and cannot reconnect until the Instant Messaging server is restarted. Workaround: Download the product patch from SunSolve Online. |
|
6302312 |
If Instant Messenger becomes disconnected from the server, it may not function properly when it reconnects. For example, presence information may not be displayed correctly, and conference rooms will not work. Workaround: To join a conference room after a disconnect occurs, click the chat icon instead of double-clicking the conference on the Conferences tab. In addition, you can download the product patch from SunSolve Online. |
Configuring Instant Messaging for high availability (HA) provides for monitoring of and recovery from software and hardware failures. The high availability feature is implemented as a failover data service, not a scalable service, and is supported on Solaris only. This section describes an Instant MessagingHA configuration using Sun Cluster software. See HA Related Documentation for more information about data services provided by Sun Cluster.
This describes how to configure an Instant Messaging HA service, in the following sections:
You use Sun Cluster with Instant Messaging to create a highly available deployment. This section provides information about HA requirements, terms used in examples in this chapter, and permissions you need to configure HA in the following sections:
Before you begin, you should be familiar with general HA concepts, and Sun Cluster software in particular. For more information, see HA Related Documentation.
An Instant Messaging HA configuration requires the software shown in Table 3–7.
Table 3–7 Software Requirements for Instant Messaging HA Configuration
Software and Version |
Notes and Patches |
---|---|
Solaris 9 OS SPARC Platform only |
All versions of Solaris 9 OS are supported. Solaris 9 OS requires Sun Cluster 3.0 U3 or later. Solaris 9 OS includes Solaris Logical Volume Manager (LVM). |
Solaris 8 OS SPARC Platform only |
Solaris 8 Maintenance Update 7 (MU7) OS or later plus required patches. |
Sun Cluster 3.1 |
Sun Cluster software must be installed and configured on all nodes in the cluster. To install Sun Cluster 3.1, use the Java Enterprise System installer by following the installation process in the Sun Java Enterprise System 2005Q4 Installation Guide. After you install the Sun Cluster software, you must configure the cluster. For information, refer to the Sun Cluster System Administration Guide for Solaris OS. For related documentation, see HA Related Documentation. Sun Cluster Patches For Solaris 8 and 9, you can download patches from SunSolve Online. |
Solstice DiskSuite 4.x |
Solstice DiskSuite is available for Solaris 8 OS only. Solstice DiskSuite is not required for Solaris 9 OS, which includes the Logical Volume Manager (LVM). |
Veritas Volume Manager (VxVM) 3.x |
Solaris 8 OS requires version 3.2 or later plus required patches. Solaris 9 OS requires version 3.5 or later plus required patches. |
Veritas File System (VxFS) 3.x |
Solaris 8 OS requires version 3.4 or later plus required patches. Solaris 9 OS requires version 3.5 or later plus required patches. HAStoragePlus requires patch 110435-08 or later. |
To install and configure an Instant Messaging HA configuration, log in as or become superuser (root) and specify a console or window for viewing messages sent to /dev/console.
Table 3–8 describes the variable terms used in the examples in this chapter for configuration examples. In addition, you will need to gather the information before you configure HA for Instant Messaging. You will be prompted for this information during configuration. Use this checklist in conjunction with the checklist in Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide.
Table 3–8 HA Configuration Checklist
The following is a high-level list of the steps necessary to install and configure an Instant Messaging HA configuration with two nodes:
Before you begin, you need to decide which of the following deployments best suits your needs. In both environments, shared components are installed locally on every node in the cluster. In addition, in both environments, runtime files are installed on a shared disk.
Using a local disk for configuration files and binaries. The advantage to this setup is that upgrading Instant Messaging requires minimal downtime because you can upgrade on nodes where Instant Messaging is offline. The disadvantage is that you need to ensure that the same configuration and version of Instant Messaging exists on all nodes in the cluster.
In addition, if you choose this option, you need to determine whether you will be using HAStoragePlus to mount a file system from a shared disk on each node when Instant Messaging data services are brought online, or if you will be using the cluster file system for global runtime files.
Using a shared disk for configuration files and binaries. This setup is easier to administer, but you need to bring Instant Messaging down on all nodes in the cluster before upgrading.
On each node in the cluster, you need to create the Instant Messaging runtime user and group under which the components will run. The UID and GID numbers must be the same on all nodes in the cluster.
Runtime User ID. The user name under which Instant Messaging server runs. This name should not be root. The default is inetuser.
Runtime Group ID. The group under which Instant Messaging server runs. The default is inetgroup.
Although the configure utility can create these names for you, you can create them before you run the configuration program, as part of the preparation of each node as described in this chapter. In addition, depending on whether you are using a local or shared disk, you may not run configure on a particular node and must manually create the runtime user and group ID.
The runtime user and group ID names must be in the following files:
inetuser, or the name you select, in /etc/passwd on all nodes in the cluster
inetgroup, or the name you select, in /etc/group on all nodes in the cluster
See the Sun Java System Instant Messaging 7 2005Q1 Administration Guide for instructions. Refer to your operating system documentation for detailed information about users and groups.
For Instant Messaging, the Java Enterprise System installer uses /opt/SUNWiim on Solaris as the default installation directory (im_svr_base ). However, if you are using a shared disk for configuration files and binaries, you must specify a global (shared) installation directory. For example: /global/im/opt/SUNWiim.
If you are using a local disk, you can install Instant Messaging to the default directory. However, you should Install Instant Messaging in the same directory on each machine in the node.
You install products and packages using the Sun Java Enterprise System installer program. For more information about the installer, refer to the Sun Java Enterprise System 2005Q4 Installation Guide.
Table 3–9 lists the products or packages required for a multiple node cluster configuration.
Table 3–9 Products and Packages Required for a Multiple Node Instant Messaging HA Configuration
Product or Package |
Node 1 |
Node n |
Sun Cluster Software |
Yes |
Yes |
Instant Messaging 7 2005Q4 Server |
Yes |
Yes, if you are using a local disk for configuration files and binaries. No, if you are using a shared disk for configuration files and binaries. |
Sun Cluster Agent for Instant Messaging (SUNWiimsc) |
Yes |
Yes, if you are using a local disk for configuration files and binaries. No, if you are using a shared disk for configuration files and binaries. |
Shared components If you are using HAStoragePlus, you must also install SUNWscu |
Yes |
Yes |
The steps you need to perform vary depending on whether or not you are using a local or shared disk for configuration files and binaries.
If you are using a local disk for configuration files and binaries, follow the steps in the following two procedures:
To Configure HA on Node 1 Using a Local Disk for Configuration Files and Binaries
To Configure HA on Node n Using a Local Disk for Configuration Files and Binaries
If you are using a shared disk for configuration files and binaries, follow the steps in the following two procedures:
To Configure HA on Node 1 Using a Shared Disk for Configuration Files and Binaries
To Configure HA on Node n Using a Shared Disk for Configuration Files and Binaries
Fill out the checklists in Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide and Table 3–8 and have your answers readily available.
Install products and packages using the Java Enterprise System installer.
See Selecting the Installation Directory (im_svr_base ) for specific instructions on choosing an installation directory.
See Table 3–9 for a list of required products and packages for HA. Refer to the Sun Java Enterprise System 2005Q4 Installation Guide for specific instructions.
If you are using HAStoragePlus for the runtime files, mount a shared disk to a local directory, otherwise skip to Step 3.
For example:
Create the mount point (/local/ im/im_runtime_base/) if it does not already exist.
When prompted during configuration in Step 4 you will specify this directory (/local /im/im_runtime_base/ ) as the Instant Messaging Server Runtime Files Directory.
Use the mount command to mount the disk on /local/im/im_runtime_base.
Run the configure utility.
See the Sun Java System Instant Messaging 7 2005Q1 Administration Guide for instructions.
When prompted for the Instant Messaging Server Runtime Files Directory, enter one of the following:
If you are using an HAStoragePlus for the runtime files, enter /local/im/im_runtime_base /.
If you are using a cluster file system for the runtime files, enter /global/im/im_runtime_base /. Where /global/ im is the global directory in the cluster file system.
When prompted for the Instant Messaging host name, enter the logical host.
Choose to accept the logical host even if the configure utility cannot connect to the specified host. The logical host resource may be offline at the time you run the configure utility.
Do not choose to start Instant Messaging after configuration or on system startup.
In an HA configuration, the Instant Messaging service also requires the logical host to be online for Instant Messaging to work properly.
If you are using HAStoragePlus for runtime files, unmount the shared disk.
Ensure that you have completed HA configuration on Node 1 as described in the previous procedure (To Configure HA on Node 1 Using a Local Disk for Configuration Files and Binaries).
Have your answers for the checklists in Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide and Table 3–8 readily available.
Install products and packages using the Java Enterprise System installer.
Choose the same path you used when you installed Instant Messaging on node 1 for each subsequent node in the cluster. See Selecting the Installation Directory (im_svr_base ) for specific instructions.
See Table 3–9 for a list of required products and packages for HA. Refer to the Sun Java Enterprise System 2005Q4 Installation Guide for specific instructions.
Run the configure utility.
See Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide for instructions.
When prompted for the Instant Messaging Server Runtime Files Directory, enter the same value that you provided for Node 1.
When prompted for the Instant Messaging host name, enter the same logical host you provided for Node 1.
Choose to accept the logical host even if the configure utility cannot connect to the specified host. The logical host resource may be offline at the time you run the configure utility.
When prompted for the user and group, enter the same value that you provided for Node 1.
Do not choose to start Instant Messaging after configuration or on system startup.
In an HA configuration, the Instant Messaging service also requires the logical host to be online for Instant Messaging to work properly.
Fill out the checklists in Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide and Table 3–8 and have your answers readily available.
You must use a cluster file system if you are using a shared disk for configuration files and binaries, not HAStoragePlus.
Install products and packages in a directory in the cluster file system using the Java Enterprise System installer.
When you install Instant Messaging, you must specify a directory other than the default directory. See Selecting the Installation Directory (im_svr_base ) for specific instructions.
See Table 3–9 for a list of required products and packages for HA. Refer to the Sun Java Enterprise System 2005Q4 Installation Guide for specific instructions.
Create a soft link from /etc/opt/SUNWiim that points to /global/im/etc/opt/SUNWiim .
Run the configure utility from the global directory where you installed Instant Messaging (/global/ im/im_svr_base/configure ).
See Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide for instructions.
When prompted for the Instant Messaging Server Runtime Files Directory, enter the value for /global/im/ im_runtime_base.
When prompted for the Instant Messaging host name, enter the logical host.
Choose to accept the logical host even if the configure utility cannot connect to the specified host. The logical host resource may be offline at the time you run the configure utility.
Do not choose to start Instant Messaging after configuration or on system startup.
In an HA configuration, the Instant Messaging service also requires the logical host to be online for Instant Messaging to work properly.
Ensure that you have completed HA configuration on Node 1 as described in the previous procedure (To Configure HA on Node 1 Using a Shared Disk for Configuration Files and Binaries).
Have your answers for the checklists in Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide and Table 3–8 readily available.
Create a soft link from /etc/opt/SUNWiim that points to /global/im/etc/opt/SUNWiim .
Create a soft link for the resource type registration (RTR) file:
ln -s /global/im/ im_svr_base/cluster/SUNW.iim \ /usr/cluster/lib/rgm/rtreg/SUNW.iim |
Before starting Instant Messaging, you need to create a resource group, add the logical host, and bring the resource group online.
Create an Instant Messaging failover resource group named im_resource_group:
# scrgadm -a -g im_resource_group -h im-node-2,im-node-1 |
Add the logical host name im_logical_host to the resource group.
Instant Messaging will listen on this host name.
# scrgadm -a -L -g im_resource_group -l im_logical_host |
Bring the resource group online:
# scswitch -Z -g im_resource_group |
Before you can bring the Instant Messaging data service online, you need to register and activate the storage resource as described in this section.
Register the storage resource.
If you are using HAStoragePlus with a global file system (GFS), set the mount point as the value for the FileSystemMountPoints property. For example:
# scrgadm -a -j im_resource_group_store -g im_resource_group -t SUNW.HAStorage \ -x FileSystemMountPoints=/global/ im -x AffinityOn=True |
Otherwise, specify the mount point as the value for the ServicePaths property. For example:
# scrgadm -a -j im-resource-group-store -g im-resource-group -t SUNW.HAStorage \ -x ServicePaths=/global/im -x AffinityOn=True |
Enable the storage resource:
# scswitch -e -j im_resource_group_store |
Before you start the HA Instant Messaging server or multiplexor, you need to register the resource type SUNWiimsc with Sun Cluster and create a resource.
Register the resource type.
# scrgadm -a -t SUNW.iim |
Create the resource.
Enter the following command on a single line:
# scrgadm -a -j im_resource -g im_resource_group -t SUNW.iim -x Confdir_list=/global/im/ im_resource_group -y Resource_dependencies=im_resource_group_store -y Port_list=80/tcp |
Enable the resource:
# scswitch -e -j im_resource |
Start Instant Messaging components.
Do not use the imadmin start, imadmin stop , or imadmin refresh commands in an HA environment with Sun Cluster. Instead, use the Sun Cluster administrative utilities.
After you start Instant Messaging, you need to verify the HA configuration as described in this section.
Check that all required processes are running.
Conduct a switchover of the service to the backup node to ensure the high availability.
For example, if the service is running on im_node_1, issue the following command to switch the service to im_node_2.
# scswitch -z -g im_resource_group -h im_node_2 |
Check that all required processes are started on im_node_2 .
To help with troubleshooting, error messages are written to the error log. The logs are controlled by the syslog facility. For information about using the logging facility, refer to the HA Related Documentation and to the man page for syslog.conf.
To start and stop the Instant Messaging HA service, use the Sun Cluster scswitch command.
Do not use the imadmin start, imadmin stop , or imadmin refresh commands in an HA environment with Sun Cluster. Instead, use the Sun Cluster administrative utilities.
For more information about the Sun Cluster scswitch command, refer to the Sun Cluster Reference Manual for Solaris OS.
Type the following at the command line:
# scswitch -e -j im_resource |
Type the following at the command line:
# scswitch -n -j im_resource |
Type the following at the command line:
# scswitch -R -j im_resource |
The resource type registration (RTR) file is an ASCII text file that describes a highly-available resource type that runs under the control of the Resource Group Manager (RGM). The RTR file is used as an input file by the scrgadm command to register the resource type into the cluster configuration. The Instant Messaging RTR file, SUNW.iim, is created when you install the SUNWiimsc package during HA configuration.
This section provides information about managing this file in the following sections:
The following table lists the extension properties in the Instant Messaging RTR file (SUNW.iim) that are specific to Instant Messaging.
Table 3–10 SUNW.iim Extension Properties
Extension Property |
Default |
Description |
---|---|---|
Server_Root |
If you are using a local disk to store configuration files and binaries: im_svr_base If you are using a shared directory to store configuration files and binaries: /global/im/im_svr_base |
Defines the absolute path to the Instant Messaging server installation directory. By default, im_svr_base is /opt/SUNWiim on Solaris. |
Confdir_list |
None |
Defines the absolute path to the Instant Messaging configuration. This value is set during the installation of SUNWiimsc. |
Monitor_retry_count |
4 |
Defines how many times you want the process monitor facility (PMF) to attempt to restart the fault monitor if it determines it is not running. |
Monitor_retry_interval |
2 (minutes) |
Time, in minutes, between restart attempts made by the PMF on the fault monitor. |
Probe_timeout |
30 (seconds) |
Time, in seconds, that the Sun Cluster probe will wait for a successful connection to Instant Messaging. |
Failover_enabled |
True |
Determines whether or not to failover to another node if the configured number of retries (retry_count) is exceeded during the configured retry interval (retry_interval). See the Sun Cluster Reference Manual for Solaris OS for more information on retry and other parameters. |
You can modify the values for several of the extension properties in the Instant Messaging RTR file (SUNW.iim) to configure your HA environment. Extension properties are properties that are specific to the resource type. These properties are inherited by every resource of the same type. Instant Messaging extension properties are described in Instant Messaging RTR File Parameters.
See the documentation for rt_reg and property_attributes in the Sun Cluster Reference Manual for Solaris OS for more information on the contents of resource type registration files and instructions on customizing values for extension properties.
In order to remove Instant Messaging from an HA environment, you need to remove the Instant Messaging cluster agent SUNWiimsc as described in this section.
When you remove the SUNWiimsc package as described in this procedure, any customizations you made to the RTR file SUNW.iim are lost. If you want to restore them at a later time, you need to create a backup copy of SUNW.iim before removing the SUNWiimsc package.
Bring down the Instant Messaging data service:
scswitch -F -g im_resource_group |
Disable all resources in the Instant Messaging resource group ( im_resource_group):
# scswitch -n -j im_resource # scswitch -n -j im_logical_host # scswitch -n -j im_resource_group_store |
Remove the resources from the Instant Messaging resource group:
# scrgadm -r -j im_resource # scrgadm -r -j im_logical_host # scrgadm -r -j im_resource_group_store |
Remove the Instant Messaging resource group:
# scrgadm -r -g im_resource_group |
Remove the Instant Messaging resource type:
# scrgadm -r -t SUNW.iim |
Remove the SUNWiimsc package using the Java Enterprise System installer or manually as follows:
pkgrm SUNWiimsc |
When you remove the package, any customizations you made to the RTR file are lost.
If you are using a shared directory for configuration files and binaries, remove any soft links created during HA configuration.
On Node 1:
rm /etc/opt/SUNWiim |
On all other nodes:
rm /usr/cluster/lib/rgm/rtreg/SUNW.iim |
Sun Java System Instant Messaging 7 2005Q1 Administration Guide
Sun Java Enterprise System 2005Q4 Technical Overview
Sun Java Enterprise System 2005Q4 Installation Guide for UNIX describes the Java Enterprise System installer (and uninstaller) and the supported installation scenarios.
Sun Java Enterprise System 2005Q4 Release Notes provide current information about the Sun Java Enterprise System product.
Sun Cluster Concepts Guide for Solaris OS provides a general background about Sun Cluster software, data services, and terminology resource types, resources, and resource groups.
Sun Cluster Data Services Planning and Administration Guide for Solaris OS provides general information on planning and administration of data services.
Sun Cluster System Administration Guide for Solaris OS provides the software procedures for administering a Sun Cluster configuration.
Sun Cluster Reference Manual for Solaris OS describes the commands and utilities available with the Sun Cluster software, including commands found only in the SUNWscman and SUNWccon packages.
Sun Java System Communications Services 6 2005Q4 Deployment Planning Guide provides further information about how HA is implemented in Instant Messaging.
Sun Java System Instant Messaging 7 2005Q4 does not contain any files which you can redistribute.