This section describes the following new features added to Instant Messaging in this release:
This release of Instant Messaging allows you to connect multiple Instant Messaging servers to provide the same service as a single server. This allows for horizontal scalability and increases availability through redundancy.
You can now configure the Instant Messaging server to send a copy of an instant message or conversations via email. This provides a natural way for end users to retrieve past conversations or alerts. You can also use it for compliance and auditing purposes.
On Windows, users can configure Instant Messenger to automatically start when the system boots. Improvements to client diagnostics are also included and vcard support is now available.
DNS resolution of Instant Messaging hosts is now supported by the API and the server. In previous releases, a Instant Messaging server used a logical domain unique to Instant Messaging instead of the DNS domain to identify itself and its users to other Instant Messaging servers. In this release, Instant Messaging server now use the fully-qualified domain name to identify itself on the network.
With this version you can now leverage the full power of log4j. This provides ways to control the format of log records, and logging destinations.
The configure utility now prompts you for information about Sun Java System Calendar Server and Sun Java System Access Manager. You no longer have to manually configure Instant Messaging to work with these servers.