Chapter 61. Tigase as External Component

Table of Contents

A Simple Case - MUC as an External Component
More Components

Artur Hefczyc <> v2.0, June 2014: Reformatted for AsciiDoc. :toc: :numbered: :website: :Date: 2010-04-06 21:18

There are cases when you want to deploy one or more Tigase components separately from the main server or perhaps you want to run some Tigase components connecting to a different XMPP server or perhaps you work on a component and you do not want to restart the main server every time you make a change.

There is a way to run the Tigase server in "external component mode". In fact you can run any of Tigase components as an external component and connect them to the main XMPP server either via XEP-0114 or XEP-0225 connection.

Let’s look at the examples…​

A Simple Case - MUC as an External Component

A few assumptions:

  1. We want to run a MUC component for a domain: '' and password 'muc-pass'
  2. The main server works at an address: and for the same virtual domain
  3. We want to connect to the server using XEP-0114 protocol and port '5270'.

There is a special configuration type for this case which simplifies setting needed to run the Tigase as an external component:


This generates a configuration for the Tigase with only one component loaded by default - component used for external component connection. If you use this configuration type, your file may look like this:

config-type = --gen-config-comp
--debug = server
--user-db = derby
--admins =
--user-db-uri = jdbc:derby:/tigasedb
--virt-hosts =
--comp-name-1 = muc
--comp-class-1 = tigase.muc.MUCComponent
--external =

Please note, you do not need lines:

--comp-name-1 = ext
--comp-class-1 = tigase.server.ext.ComponentProtocol

as the


automatically includes them.