Wildfire Documentation

Posted on

 Objective: this documentation is intended to help administrator to setup the wildfire as and IM server, to configure the IM server to be integrated with the active directory and set up the group sharing contact list. Wildfire is a powerful instant messaging (IM) and chat server that implements the XMPP protocol. This document will guide you through installing Wildfire as a standalone application. For a full list of features and more information, please visit the Wildfire website: http://www.jivesoftware.org/wildfire



Run the Wildfire installer. The application will be installed to c:\Program Files\Wildfire by default.


Choose either the RPM or tar.gz build. If using the RPM, run it using your package manager to install Wildfire to /opt/wildfire: rpm -ivh wildfire_3_0_0.rpmIf using the .tar.gz, extract the archive to /opt or /usr/bin: tar -xzvf wildfire_3_0_0.tar.gz
mv wildfire /opt
Note: the .tar.gz build does 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.

Setup Overview

To complete the installation of Wildfire, you’ll need to perform each of the following steps:

  1. Database – if you choose to use an external database, you must prepare your database for Wildfire.
  2. Setup – Use the built-in web-based setup tool to setup and verify the server configuration.
  3. Admin Console – use the web-based admin tool to manage the server.

This document also includes information on:·                Running under Windows ·                Running under Unix/Linux ·                Installing and using plugins

Files in the Distribution

The files in your distribution should be as follows (some sub-directories omitted for brevity):

 |- readme.html
 |- license.html
 |- conf/
 |- bin/
 |- jre/
 |- lib/
 |- plugins/
     |- admin/
 |- resources/
 |- documentation/

·                The conf directory is where Wildfire stores configuration files. ·                The bin directory contains the server executables. Depending on which distribution you installed, different executables will be available. ·                The jre directory contains a Java 5 runtime that is bundled with the Windows and RPM versions of Wildfire. ·                The lib directory contains libraries necessary for running Wildfire. ·                The plugins directory contains server plugins. By default, Wildfire ships with a web-based admin console plugin. ·                The resources/database directory contains SQL schema files to create new Wildfire databases, as well as upgrade scripts for existing installations. ·                The resources/security directory is where Wildfire maintains keystores to support SSL connection security. ·                The documentation directory contains server documentation.

Setup the Database

Wildfire can store its data in an embedded database or you can choose to use an external database such as MySQL or Oracle. If you would like to use an external database, you must prepare it before proceeding with installation by running the appropriate database schema. View the database setup documentation for more information.

Setup the Server

A web-based, “wizard” driven setup and configuration tool is built into Wildfire. Simply launch Wildfire (platform-specific instructions below) and use a web browser to connect to the admin console. The default port for the web-based admin console is 9090. If you are on the same machine as Wildfire, the following URL will usually work:

Admin Console

After completing the above steps, Wildfire will be configured and you can use the web-based admin console to administer the server. The URL should be the same as you used to setup the server unless you changed the port during the setup.

Running Wildfire in Windows

If you used the Wildfire installer, a shortcut for starting the a graphical launcher is provided in your Start Menu. Otherwise, run wildfire.exe in the bin/ directory of your Wildfire installation. A button on the on the launcher allows you to automatically open your web browser to the correct URL to finish setting up the server:

Windows Service

If you’re running Wildfire on Windows, you will likely want to run Wildfire as a standard Windows service after initial setup. If you used the Windows installer, a wildfire-service.exe file will be in the bin directory of the installation. You can use this executable to install and control the Wildfire service. From a console window, you can run the following commands: ·                wildfire-service /install — installs the service. ·                wildfire-service /uninstall — uninstalls the service. ·                wildfire-service /start — starts the service ·                wildfire-service /stop — stops the service. You can also use the Services tool in the Windows Control Panel to start and stop the service.Note: the graphical launcher is not compatible with the Windows service at this time. If you install the service, you should use service controls as described above to control the server rather than the graphical launcher.

Custom Parameters

Advanced users may wish to pass in parameters to the Java virtual machine (VM) to customize the runtime environment of Wildfire. You can do this by creating vmoptions files in the bin/ directory of your Wildfire installation. For the Windows service, you’d create a new text file called wildfire-service.vmoptions. Each parameter to the VM should be on a new line of the file. For example, to set the minimum heap size to 512 MB and max VM heap size to 1024 MB, you’d use:


To create parameters for the normal launcher, create a file called wildfired.vmoptions (since the wildfire.exe launcher invokes the wildfired.exe executable to actually start the server).

Running Wildfire in Linux/Unix

You can start and stop Wildfire using the bin/wildfire script in your Wildfire installation: # ./wildfire
Usage: ./wildfire {start|stop}
# ./wildfire start
Starting wildfire
If you would like to install Wildfire as a service, two scripts are provided in the bin/extra directory: ·                redhat-postinstall.sh — automatically installs Wildfire as a service on Red Hat. It does so by creating a “jive” user and then copying the wildfired script to your init.d directory. This script must be run as root. Please see the comments in the script for additional information. ·                wildfired — script to run Wildfire as a service. You must manually configure this script. See the comments in the script for additional details.


Plugins add additional features and protocol support to Wildfire. After setting up your Wildfire installation, you may want to download and install plugins to enhance your server. Plugins can be downloaded from the plugins page on jivesoftware.org.

Installing Plugins

Each plugin comes packaged as a .jar (JAR) file. After download the plugin, you can deploy it by copying the plugin file to the plugins/ directory of your Wildfire installation. A plugin monitor will automatically extract the plugin into a directory and install the plugin in Wildfire.

Managing Plugins

Plugins can be managed inside the Wildfire admin console. You can also manually delete a plugin at any time by deleting its JAR file (Wildfire will automatically remove the plugin from memory and delete it’s directory when you do so).   Setting Up the LDAP (Active directory) authentication You can integrate the Wildfire (Jabber Server) with the LDAP or active directory so that user need no more registration to the IM server.Here is the step:

  1. go to the wildfire program directory, then go to conf directory

$  cd /opt/wildfire$ cd conf 

  1. Open the wildfire.xml to do following configuration

$ vi wildfire.xml

    1. Add administrator to configure wildfire so that you can configure the web console (http://serverIP:9090), by adding the following line to the wildfire.xml

                                <admin>      <!– Use this section to define users that will have admin privileges. Below,          you will find two ways to specify which users are admins. Admins will          have access to the admin console (only local users) and may have also access          to other functionalities like ad-hoc commands. –>    <!– By default, only the user with the username “admin” can login         to the admin console. Alternatively, you can specify a comma-delimitted         list usernames that should be authorized to login to the admin console         by setting the <authorizedUsernames> field below. –>    <!– <authorizedUsernames></authorizedUsernames> –>    <!– Comma-delimitted list of bare JIDs. The JIDs may belong to local         or remote users. –>    <!– <authorizedJIDs></authorizedJIDs> –>    <authorizedUsernames>amat lim,administrator</authorizedUsernames>  </admin>  <locale>en</locale> 

    1. Setting up the database of wildfire

 <connectionProvider>  <className>org.jivesoftware.database.DefaultConnectionProvider</className>  </connectionProvider>  <database>    <defaultProvider>      <driver>com.mysql.jdbc.Driver</driver>      <serverURL>jdbc:mysql://</serverURL>      <username>initial</username>      <password>initial</password>      <minConnections>5</minConnections>      <maxConnections>15</maxConnections>      <connectionTimeout>1.0</connectionTimeout>    </defaultProvider>  </database>

    1. setting up the active directory configuration ( the following example is using id.ri-asia.ad)

 <ldap>    <host></host>    <port>389</port>    <baseDN>DC=id,DC=ri-asia,DC=ad</baseDN>    <adminDN>CN=administrator,CN=users,DC=id,DC=ri-asia,DC=ad</adminDN>    <adminPassword>r0mani4</adminPassword>    <connectionPoolEnabled>true</connectionPoolEnabled>    <sslEnabled>false</sslEnabled>    <debugEnabled>false</debugEnabled>    <autoFollowReferrals>false</autoFollowReferrals>    <usernameField>sAMAccountName</usernameField>    <groupNameField>cn</groupNameField>    <groupMemberField>member</groupMemberField>    <groupDescriptionField>description</groupDescriptionField>    <posixMode>false</posixMode>  </ldap> Save the file configuration, and then restart the wildfire server. $ /opt/wildfire/bin/wildfire stop$ /opt/wildfire/bin/wildfire startYou can try whether the integration has been working by going to the administration console, then enter the active directory user administrator username & password as following screen  Successful authentication will have the following screen: then try to connect from client. You can use spark (www.jivesoftware.com) or jabbin as the software client. In Indonesia we use spark, since it’s much more convenience than jabbin (despite jabbin can be used for VOIP).   How to group user In order to create group of users, so that when user log in to the IM, they don’t need to add/ authorize another user to their IM, following step define the steps:1.      go to the domain controller2.      open active directory user & computer3.      create a new group (security group), in indonesia we use group based on branch (eq: HO, Jakarta, Surabaya, etc).  4.      add users to that group  5.      go to the wildfire administration console (http://<serverip&gt;:9090), login with the domain administrator & password as follow: 6.      go to the users/group tabular:   7.      then click group summary, then search the group name (eq: Balikpapan), then type enter, and the group searching will display Balikpapan group   8.      click on the group, then you will see :  9.      click enable contact list group sharing to share the group to other users, then enter the contact list group name, then click save contact list settings. 10. after user login they will see the group you just setup in their IM, as follow:         


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s