Openfire: Pluggable Roster Support Guide

# Pluggable Roster Support Guide

## Introduction

This document provides instructions on how to configure Openfire's roster support to work with alternate sources of roster data rather than the provided database tables.

Consider the scenario where Openfire is integrated as the chat server solution for an existing 'social' application. In this application a user is linked to other users via a relationship of sorts, and the system of record for the relationship data is NOT the Openfire system. Using an XMPP server such as Openfire the applications benefit from the real-time nature of XMPP rosters and other subscription based features such as PEP, but with the caveat that the existing relationship information has to be duplicated in Openfire and could potentially become out of sync.

With the introduction of pluggable roster providers, Openfire can be instructed to retrieve and modify roster data that lives in alternative locations to the standard database tables. The options are limitless as to what this could be, e.g. an alternative database table(s), a web service, a NoSQL database etc.

## Background

This integration requires some Java knowledge in order to implement a custom roster provider for Openfire. The skill needed will vary depending on what you are trying to achieve. The extension approach is similar to the custom AuthProvider approach on which it is based.

## The RosterItemProvider extension point

As of Openfire 3.7.2, the class RosterItemProvider has changed from being a concrete class to an interface. The default implementation of this provider is the DefaultRosterItemProvider, which as the name suggests is the version of this provider Openfire will use if not overridden. The DefaultRosterItemProvider uses the Openfire database to retrieve roster information.

The steps to get Openfire using a custom RosterItemProvider are described below.

1. Write a class that implements RosterItemProvider, providing your own business logic.
2. Make the class available in a jar and make this available to Openfire by placing it in the lib directory. There are numerous ways to package a jar with this class inside it, popular build systems such as Gradle and Maven can make your life easier.
3. Set the property 'provider.roster.className' to be the full name of your class, e.g. 'com.foo.bar.MyRosterItemProvider'.
4. Restart Openfire. Your custom class should now be handling all the roster based operations.

## Frequently Asked Questions

1. Do I have to compile my custom class into the Openfire jar? No, the class only needs to be visible on the Openfire classpath.
2. How do I ensure my custom class is visible on the Openfire classpath? Just place your new custom library in the Openfire lib directory, this will ensure it is automatically available at startup.
3. Will I have a degradation in performance using a custom RosterItemProvider? It completely depends on your implementation. As with any Openfire customisation or plugin, badly written code has the potential to cause Openfire to perform slower. Use performance testing tools such as Tsung to ensure issues haven't been introduced.
4. How can I have my custom class connect to another DB/Web service/NoSQL store etc? This is outside of the scope of this documentation and is your choice as a developer. If you are looking to externalize properties like connection details, the Openfire properties mechanism and the JiveGlobals class are good places to start investigating.
5. Can I have multiple RosterItemProviders, in a similar vein to the HybridAuthProvider? No, this feature is currently not implemented. Get involved if you feel a need to have it!