Instant Messaging Compatibility Issues

Versions ofInstant Messenger prior to 2006Q1 do not support XMPP redirection. 

(Issue Number: 6401743) If you intend to use the Instant Messaging redirect server with Instant Messenger, you must use version 2006Q1 or later of Instant Messenger. 

If you use a third party client, ensure that it supports XMPP redirection before deploying the Instant Messaging redirect server. 

The Instant Messaging SDK Java packages were renamed in Sun Java System Instant Messaging 7 2005Q4 in order to match the open source community's naming conventions (org.netbeans.lib.collab). 

In a future release, Instant Messaging will use the new naming scheme exclusively and the old scheme will be deprecated. 

Instant Messaging 7.2 is incompatible with the 7 2005Q4 versions of Access Manager. 

When installing Access Manager, select “Legacy Mode (version 6 style)” instead of “Realm Mode (version 7 style)” on the Java Enterprise System installer. 

Instant Messaging 7.2 is incompatible with the 2004Q2 versions of Portal Server and Messaging Server. 

Upgrade Portal Server and Messaging Server when upgrading Instant Messaging 7.2. 

Due to a protocol change the Instant Messaging 7.2 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 a protocol change the older versions of the client (2004Q2 and earlier) 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 7 2005Q4 and 2006Q1 are incompatible with shared components that ship with Sun Java System Instant Messaging 7.2. 

Instant Messaging has a hard dependency on the IM SDK. The IM SDK is installed with the shared components. 

You will need to upgrade shared components then upgrade Instant Messaging. See the Sun Java Communications Suite 5 Installation Guide for specific instructions.

The Instant Messaging SDK implementation of the Legacy Instant MessagingPresence 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 Instant Messaging 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 in Instant Messaging for instructions.

The Instant Messaging 7.2 multiplexor does not work with previous versions of the server. 

(Issue Number: 6396790) Due to a change in the internal protocol used between the multiplexor and the server, the multiplexor does not immediately detect when a previous version of the server goes down. Clients using a multiplexor connected to a previous version of the server that has gone down may not become aware of server failure within a reasonable amount of time. 

Use Instant Messaging 7.2 for both the multiplexor and server. You will need to upgrade or patch systems on which the server is installed and then upgrade systems on which only the multiplexor is enabled. 

Instant Messaging 7.2 server does not work with previous versions of the Instant Messaging SDK. 

(Issue Number: 6439781) You cannot start the Instant Messaging 7.2 server after upgrade if you do not also upgrade the Instant Messaging SDK. 

Use the 7.2 version of the server and the SDK. 

Changes to default codebase URL since release 6 2004Q2. 

(Issue Number: 6189921) The default URL for the codebase was changed from: 

http://server:port/iim

to: 

http://server:port/im

Changes to default port numbers since release 6 2004Q2 

(Issue Number: 6189921) The server port was changed from 49999 to 45222 and the multiplexor port changed from 49909 to 5222.