Instant Messaging Doc Update: Federating Deployment of Multiple Instant Messaging Servers
By joesciallo on Jun 19, 2007
Deployment of the Star Trek Federation Fleet
Our Instant Messaging writer has just made available a new Sun Java System Instant Messaging doc titled Technical Article: Federating Deployment of Multiple Instant Messaging Servers.
If you have installed a patch for Instant Messaging after the 7.2 release, the contents of this article replace Chapter 8, "Federating Deployment of Multiple Instant Messaging Servers" in the Sun Java System Instant Messaging 7.2 Administration Guide released with Communications Suite 5.
Get the doc here.
From this doc:
When you federate multiple Instant Messaging deployments you form a larger Instant Messaging community by expanding the XMPP user base. End users from different servers can communicate with each other, use conference rooms on other domains, and subscribe to news channels on remote servers based on the access privileges.
In a deployment with Sun Java System Access Manager, a single Instant Messaging server can host multiple domains. You can designate a single domain as the default domain for a Instant Messaging server instance. End users in different domains hosted by the same server can interact with each other. When you federate multiple Instant Messaging deployments, end users in one domain can see the end users in the domains of other remote Instant Messaging servers.
Instant Messaging supports two methods of server federation; white list federation and open federation. A white list is a specific list of servers with which you want to allow communication. In contrast, open federation allows you to communicate with any other Instant Messaging server that also allows open federation, without having to explicitly define allowed servers. With open federation, the Instant Messaging server performs a DNS lookup instead of a white list to identify other servers with which it can communicate.