Configuring the Tigase Server to Load a Component

Table of Contents

How it Works
Setup & Configuration
Use of the HTTP API
Browser interface walk-through
HTTP API Scripting
Admin UI Guide
Tigase Web Client
Message Archiving Component
Manual Activation
Automatic Activation of MUC messages
Searching for Messages
Message Tagging Support
Purging Information from Message Archive
Advanced Message Processing - AMP XEP-0079
First of all: plugins:
Secondly: component:
Optional parameters:
PubSub Component
Pubsub naming
Configure Roster Maxmimum size
AdHoc Commands
PubSub Node Presence Protocol
Store Full XML of Last Presence
Offline Message Sink
PubSub Schema Changes
Server Monitoring
Setting Up Remote Monitoring in the Server
Retrieving statistics from the server
Statistics description
How it Works
Available Tasks
Getting the Message
Mailer Extension
Server to Server Protocol Settings
Number of Concurrent Connections
Connection Throughput
Maximum Packet Waiting Time and Connection Inactivity Time
Custom Plugin: Selecting s2s Connection
Tigase MUC Component
Configuration Options
Tigase Load Balancing
Available Implementations
Configuration Options
Auxiliary setup options
External Component Configuration
Basic Configuration Options (External Component)
Tigase as an External Component
Load Balancing External Components in Cluster Mode
Client to Server Communication
Resumption timeout
Packet Redelivery
Socks 5 Component
Database Preparation
Database usage for specific settings
Example block
Virtual Hosts in Tigase Server
Specification for ad-hoc Commands Used to Manage Virtual Domains
Virtual Components for the Cluster Mode

A detailed description of all the configuration options is in the guide where you can also find information described below and much more. The purpose of this document is to give you a brief introduction on how to load a component into Tigase server without the need to dig through all the details.

I will show how to load 2 components into Tigase server using a configuration in the file: MUC and PubSub.

The only step is to tell the server what components to load, how to name them and optionally give some extra parameters. To do so open the file you use in your installation.

Let’s say you want to just add PubSub for now. All you need to do is add 2 lines to the properties file:


The first line contains the component name 'pubsub' and the main class for this component is: 'tigase.pubsub.PubSubClusterComponent'. It doesn’t really matter what the component name is, the only requirement is that it must be unique among other components names. Because you can load many components, it helps to provide descriptive names thus 'pubsub' is a good name for a 'PubSub' component.

You can of course add more components, even PubSub components to the same server. Just remember that each of them would need to have a different name then. For example:


Although this may be rare, it allows for wide compatibility and platform stability.

Normally, however we want to load few different components like PubSub, MUC, MSN Transport and so on…​. Therefore instead of the above second PubSub we can load the MUC component:


Changes to the file will take effect upon server restart.