Connection Manager lets XMPP servers scale to a greater number of concurrent users. This document will guide you through installing Connection Manager as a standalone application. For a full list of features and more information, please visit the Wildfire website: http://www.jivesoftware.org/wildfire
tar -xzvf cmanager_3_0_0.tar.gz
mv cmanager /opt
Note: the .tar.gz and .zip builds do not contain a bundled Java runtime (JRE). Therefore, you must have JDK or JRE 1.5.0 (Java 5) or later installed on your system. You can check your java version by typing "java -version" at the command line and (if necessary) upgrade your Java installation by visiting http://java.sun.com.
To complete the installation of Connection Manager, you'll need to perform each of the following steps:
This document also includes information on:
The files in your distribution should be as follows (some sub-directories omitted for brevity):
cmanager/ |- readme.html |- license.html |- conf/ |- bin/ |- lib/ |- resources/ |-security/ |- documentation/
Properties are stored in conf/manager.xml. Only two properties are required to be configured. The xmpp.domain property specifies the name of the target server that clients want to connect to. The server and connection managers have to share a common secret so that the server can let connection managers connect. Set the xmpp.sharedSecret property with the same shared secret that the server is using.
XMPP requires that when clients or servers want to connect to another server a DNS
SRV lookup must be performed to get the real IP address and port to use to connect.
Currently Connection Managers only handle client-to-server traffic while server-to-server
will go directly to the server. You will need to configure the DNS server so that client traffic
is routed to Connection Managers. Depending on your architecture you may want to use a load
balancer in front of a set of connection managers or just configure local DNS servers to
redirect clients to a specific connection manager.
Use the cmanager.bat batch file to start the connection manager. The file is located in the bin/ directory of your Connection Manager installation.
Advanced users may wish to pass in parameters to the Java virtual machine (VM) to customize the runtime environment of Connection Manager. You can do this by editing the bin/cmanager.bat or bin/cmanager.sh files and configuring the JVM_SETTINGS variable accordingly. For example, to set the minimum heap size to 512 MB and max VM heap size to 1024 MB, you'd use:
-Xms512m -Xmx1024m
You must make the ant script executable. From the build directory, type:
chmod u+x cmanager.sh
|
# ./cmanager