This section includes the following topics:
The Instant Messaging server component is no longer supported on HP-UX or Windows platforms. For Instant Messenger supported platforms, see Instant Messaging Client Operating System Requirements.
The XMPP redirect server balances the load between servers in a server pool, increasing performance by decreasing the amount of communication required between servers in a single deployment. The XMPP redirect server increases the probability that two users who will likely share presence information and messages end up on the same node. You use a redirect service to optimize resource utilization. The redirect service directs client connections to specific hosts in the server pool.
This release of Instant Messaging supports version 2.0 of the monitoring framework. This monitoring framework provides information on the length of time for authentication, message delivery, the number of instant messages sent through the service, and other statistics.
The redeploy script used to
redeploy Instant Messenger resource files has been renamed to
(Issue Number: 6519754) This release of Instant Messaging does not support HA deployments with Sun Cluster.
In this release there are two notification services for Calendar pop-ups: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). In a future release, the Communications Services products (Instant Messaging, Calendar Server, and Messaging Server) will use JMQ exclusively and ENS will be removed. However, for this release, you can continue to use ENS.
TLS support was added to Instant Messaging in the previous release; however, the Sun Java System Instant Messaging 7 2006Q1 Administration Guide did not adequately cover instructions for setting up TLS. TLS is used for communication between the server and clients, other servers, and Instant Messaging components such as the XMPP/HTTP Gateway. Legacy SSL is still supported for communication between clients and the multiplexor. Legacy SSL is no longer supported by the server and is not supported by the gateway. The Sun Java System Instant Messaging 7.2 Administration Guide now provides detailed information about setting up security for your deployment.
As a result of the implementation of TLS in Instant Messaging, you are no longer prompted to enter an SSL port for the server when you run configure.
The following iim.conf parameters are no longer used:
iim_server.sslport – No separate port is required for TLS connections.
iim_server.usesslport – No separate SSL port.
iim_server.secconfigdir – No longer have NSS key and certificate database for the server.
iim_server.keydbprefix – No longer have NSS key and certificate database for the server.
iim_server.certdbprefix – No longer have NSS key and certificate database for the server.
iim_server.coserver1.usessl – This has been replaced with iim_server.coserver1.requiressl.
The following iim.conf parameters are new for this release:
Refer to the Sun Java System Instant Messaging 7.2 Administration Guide for information about using these parameters.
The Instant Messenger client uses imssl.html and imssl.jnlp only for legacy SSL connections. Instant Messenger supports TLS automatically when it connects to a server that is configured to use TLS.