Create and Run a Server Component

1.0 Documentation

«  Sign in, Send a Message, and Disconnect   ::   Contents   ::   Manage Presence Subscriptions  »

Create and Run a Server Component


If you have any issues working through this quickstart guide or the other tutorials here, please either send a message to the mailing list or join the chat room at

If you have not yet installed SleekXMPP, do so now by either checking out a version from Github, or installing it using pip or easy_install.

pip install sleekxmpp  # Or: easy_install sleekxmpp

Many XMPP applications eventually graduate to requiring to run as a server component in order to meet scalability requirements. To demonstrate how to turn an XMPP client bot into a component, we’ll turn the echobot example (SleekXMPP Quickstart - Echo Bot) into a component version.

The first difference is that we will add an additional import statement:

from sleekxmpp.componentxmpp import ComponentXMPP

Likewise, we will change the bot’s class definition to match:

class EchoComponent(ComponentXMPP):

    def __init__(self, jid, secret, server, port):
        ComponentXMPP.__init__(self, jid, secret, server, port)

A component instance requires two extra parameters compared to a client instance: server and port. These specifiy the name and port of the XMPP server that will be accepting the component. For example, for a MUC component, the following could be used:

muc = ComponentXMPP('', '******', '', 5555)


The server value is NOT derived from the provided JID for the component, unlike with client connections.

One difference with the component version is that we do not have to handle the session_start event if we don’t wish to deal with presence.

The other, main difference with components is that the 'from' value for every stanza must be explicitly set, since components may send stanzas from multiple JIDs. To do so, the send_message() and send_presence() accept the parameters mfrom and pfrom, respectively. For any method that uses Iq stanzas, ifrom may be used.

Final Product

#!/usr/bin/env python
# -*- coding: utf-8 -*-

    SleekXMPP: The Sleek XMPP Library
    Copyright (C) 2010  Nathanael C. Fritz
    This file is part of SleekXMPP.

    See the file LICENSE for copying permission.

import sys
import logging
import getpass
from optparse import OptionParser

import sleekxmpp
from sleekxmpp.componentxmpp import ComponentXMPP

# Python versions before 3.0 do not use UTF-8 encoding
# by default. To ensure that Unicode is handled properly
# throughout SleekXMPP, we will set the default encoding
# ourselves to UTF-8.
if sys.version_info < (3, 0):
    raw_input = input

class EchoComponent(ComponentXMPP):

    A simple SleekXMPP component that echoes messages.

    def __init__(self, jid, secret, server, port):
        ComponentXMPP.__init__(self, jid, secret, server, port)

        # You don't need a session_start handler, but that is
        # where you would broadcast initial presence.

        # The message event is triggered whenever a message
        # stanza is received. Be aware that that includes
        # MUC messages and error messages.
        self.add_event_handler("message", self.message)

    def message(self, msg):
        Process incoming message stanzas. Be aware that this also
        includes MUC messages and error messages. It is usually
        a good idea to check the messages's type before processing
        or sending replies.

        Since a component may send messages from any number of JIDs,
        it is best to always include a from JID.

            msg -- The received message stanza. See the documentation
                   for stanza objects and the Message stanza to see
                   how it may be used.
        # The reply method will use the messages 'to' JID as the
        # outgoing reply's 'from' JID.
        msg.reply("Thanks for sending\n%(body)s" % msg).send()

if __name__ == '__main__':
    # Setup the command line arguments.
    optp = OptionParser()

    # Output verbosity options.
    optp.add_option('-q', '--quiet', help='set logging to ERROR',
                    action='store_const', dest='loglevel',
                    const=logging.ERROR, default=logging.INFO)
    optp.add_option('-d', '--debug', help='set logging to DEBUG',
                    action='store_const', dest='loglevel',
                    const=logging.DEBUG, default=logging.INFO)
    optp.add_option('-v', '--verbose', help='set logging to COMM',
                    action='store_const', dest='loglevel',
                    const=5, default=logging.INFO)

    # JID and password options.
    optp.add_option("-j", "--jid", dest="jid",
                    help="JID to use")
    optp.add_option("-p", "--password", dest="password",
                    help="password to use")
    optp.add_option("-s", "--server", dest="server",
                    help="server to connect to")
    optp.add_option("-P", "--port", dest="port",
                    help="port to connect to")

    opts, args = optp.parse_args()

    if opts.jid is None:
        opts.jid = raw_input("Component JID: ")
    if opts.password is None:
        opts.password = getpass.getpass("Password: ")
    if opts.server is None:
        opts.server = raw_input("Server: ")
    if opts.port is None:
        opts.port = int(raw_input("Port: "))

    # Setup logging.
                        format='%(levelname)-8s %(message)s')

    # Setup the EchoComponent and register plugins. Note that while plugins
    # may have interdependencies, the order in which you register them does
    # not matter.
    xmpp = EchoComponent(opts.jid, opts.password, opts.server, opts.port)
    xmpp.registerPlugin('xep_0030') # Service Discovery
    xmpp.registerPlugin('xep_0004') # Data Forms
    xmpp.registerPlugin('xep_0060') # PubSub
    xmpp.registerPlugin('xep_0199') # XMPP Ping

    # Connect to the XMPP server and start processing XMPP stanzas.
    if xmpp.connect():
        print("Unable to connect.")

«  Sign in, Send a Message, and Disconnect   ::   Contents   ::   Manage Presence Subscriptions  »

From &yet