Installation guide

Jabber XCP Server Installation Guide Planning Your Connection Manager Deployment Page 14
Beta Version Only
Chapter 3. Planning Your Connection
Manager Deployment
The Connection Manager (CM) component enables IM clients and servers to connect to
your Jabber XCP server. You can configure multiple CM components to increase the
number of connections that your server can handle and to enable communication over
different protocols. Although you can run all of your CM components your primary Jabber
XCP server, you can also install and run CMs on systems that are external to your primary
server. Distributing the CMs in this manner can increase the scalability, security, and
performance of your Jabber XCP installation.
Instructions for installing remote CMs are provided on page 24 in this
guide. Configuration instructions are provided in the “Deploying
Remote Connection Managers” chapter in the Jabber XCP Server
Configuration Guide.
Figure 1 on page 16 illustrates the method that Jabber, Inc. recommends for configuring
CMs remotely. This method involves installing the core Jabber XCP server on each
remote system, and configuring a Router-to-Router connection on your primary server for
each remote CM. Otherwise, the figure is only an example of how your remote CM
configuration might look. In your environment, you may choose to run other types of CMs
remotely.
In the figure, note the following in particular:
• The primary Jabber XCP server has the default setup that is provided during core
server installation. This setup includes a Web CM (for accessing the Controller), JSM
and Logger plugins, and CM and Text Conferencing components. (If preferred, you
can remove the default CM from the primary server’s configuration, and run all of
your CMs remotely.)
• The core Jabber XCP server is installed on each remote system, the default Web CM,
and one or more specialized CMs.