4.3. Provision and Configure for Berkeley Berkeley DB

Berkeley DB provides the easiest means to getting your Jabberd 2 server up and running quickly. Jabberd 2 requires a minimum version of 4.1.24 or higher.

4.3.1. Provisioning Berkeley DB

Complete this section if you are using Berkeley DB for storage and/or authorization. Provisioning your system to use Berkeley DB is quite simple. Berkeley DB only needs a directory in which to store data files, and this directory should be owned by the jabber user and group.

P Parameter: Data Directory
Create a directory and set permissions (using the user and group created above) for Berkeley DB. (as superuser): 
       mkdir -p /usr/local/var/jabberd/db
       chown -R jabber:jabber /usr/local/var/jabberd

Berkeley DB is now ready to be used with Jabberd.

4.3.2. Configure for Storage using Berkeley DB (sm.xml)

Complete this section if you are using Berkeley DB for storage. Jabberd 2 requires minimal configuration to use Berkeley DB for backend storage. Simply set the driver to use and specify the location for the database.

In sm.xml under the section labeled Storage database configuration, edit the driver to use db (Berkeley DB): 

      <!-- Storage database configuration -->
        <storage>
          <!-- By default, we use the MySQL driver for all storage -->
          <driver>db</driver>
P Parameter: Data Directory
In sm.xml under the section labeled Berkeley DB driver configuration, set the path (created in section 4.3.1. above) for your database: 
      <!-- Berkeley DB driver configuration -->
      <db>
        <!-- Directory to store database files under -->
        <path>/usr/local/var/jabberd/db</path>

        <!-- Synchronize the database to disk after each write. If you
             disable this, database accesses may be faster, but data may
             be lost if jabberd crashes. -->
        <sync/>
      </db>

Jabberd 2 is now configured to use Berkeley DB for storage.

If you wish to use an authentication package other than Berkeley DB, jump to your selection of authentication package:

Otherwise, continue on to 4.3.3. directly below to finish your Jabberd 2 configuration.

4.3.3. Configure for Authentication using Berkeley DB (c2s.xml)

Complete this section if you are using Berkeley DB for authentication. Jabberd 2 authentication configuration for Berkeley DB is the same as above, except that the information is contained in c2s.xml.

In c2s.xml under the section labeled Authentication/registration database configuration, edit the module to use db (Berkeley DB): 

      <!-- Authentication/registration database configuration -->
      <authreg>
        <!-- Backend module to use -->
        <module>db</module>
P Parameter: Data Directory
In c2s.xml under the section labeled Berkeley DB module configuration, set the path (created in section 4.3.1. above) for your database: 
      <!-- Berkeley DB module configuration -->
      <db>
        <!-- Directory to store database files under -->
        <path>/usr/local/var/jabberd/db</path>

        <!-- Synchronize the database to disk after each write. If you
             disable this, database accesses may be faster, but data may
             be lost if jabberd crashes. -->
        <sync/>
      </db>

Your Jabberd 2 configuration for storage and authentication is now complete. Jump to Test Server to begin testing your server before moving on other configuration tasks, such as configuring SSL, in Section 5.

 

Back

Up

Next

© 2003 Will Kamishlian and Robert Norris

This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.

Creative Commons License