Chapter 44. --sm-plugins
Prev |  | Next

# Chapter 44. --sm-plugins

Default value: 'none'

Example: --sm-plugins = -jabber:iq:register, your-plugin

Possible values: 'comma separated list of plugins IDs.'

Description: The --sm-plugins property allows users to specify a list of plugins which should be loaded or disabled on the server. Normally you don’t have to specify this. Tigase server loads a default list of plugins automatically. The default list contains all available plugins. Sometimes however you might want to load only some plugins. Typical use case is when user accounts are managed on a third-party system that Tigase server is integrated with. Then you might not want to allow users to register new accounts via the XMPP service. You can then load a list of plugins without the user registration plugin. Another case when you usually have to use this option is when you have your own plugins which replace function of the Tigase default plugins like vCard, roster management, and so on…​.

To prevent the plugin from loading add '-' before its ID, to load the plugin add '+' (which is optional). For example, the following setting would switch user registration off, while adding a new plugin: 'your-plugin':

    --sm-plugins=-jabber:iq:register,+your-plugin

There is more. Each plugin is running in one or more separate threads. Most plugins which deal with databases have a number of threads equal to the number of CPUs or CPU cores. Sometimes this is not enough. If the database is slow or there is a specific kind of traffic at a high level you might want to adjust the number of threads for the plugin. To set a different number of threads, just add '=N' where 'N' is the number of threads you want. The previous example has been modified to assign 8 threads for your plugin and 16 threads for authentication plugin:

    --sm-plugins=-jabber:iq:register,+your-plugin=8,jabber:iq:auth=16

Available since: 3.0.0

Prev |  | Next
Chapter 43. --sm-cluster-strategy-class | Home | Chapter 45. --sm-threads-pool