Tigase.org is the website of the Tigase XMPP/Jabber Server

If you are interested in the Tigase project and want to participate in any way you can request an account on the website and Jabber server in domain tigase.org. Please use the contact form to request the account and describe your planed involvement in the project. You can report bugs or request new features on the project tracker.

If you are looking for a free, XMPP account offered from the Tigase based service you should check the Tigase.im Website. This is the place where the last development version of the Tigase server is running. Check the website for more details.

Our RSS feeds: Blog RSS, Forums RSS, Comments RSS.

Tigase XMPP Server 5.1.0 Beta4

Submitted by kobit on Thu, 2012-01-26 03:57

The final 5.1.0 for the Tigase XMPP Server is around the corner. While we are running the last tests you can grab Beta4 build which is most likely the same exact code we will publish as the final new version.....

Please note, the download section has been moved to our project tracking system which hosts all our projects and is based on Redmine.

As usually any comments are very welcomed.

Tigase Command Line Management Tool announcement

TCLMT is new utility to manage XMPP servers by execution of ad-hoc commands. It's designed to be simple and powerful in use and work in two modes:

  • non interactive
  • interactive

Currently it partially supports ad-hoc commands which are specified in XEP-0133 Service Administration and implemented by Tigase XMPP Server. As for it contains support for:

  • 4.1. Add user
  • 4.2. Delete user

Tigase Mobile Messenger announcement

Submitted by bartosz.malkowski on Thu, 2011-08-04 11:47

I'm happy to present first screenshots of Tigase Mobile Messenger for Android we are working on.

Project isn't public yet, because application is in very early development stage.

Tigase DB Schema Explained

Submitted by kobit on Mon, 2011-07-11 23:56

The schema basics, how it looks like and brief explanation to all rows can be found in the schema creation script. However, this is hardly enough to understand how it works and how access all the data. There are only 3 basic tables which actually keep all the Tigase server users' data: tig_users, tig_nodes and tig_pairs. Therefore it is not clear at first how the Tigase data is organised.

Before you can understand the Tigase XMPP Server database schema, how it works and how to use it, is it essential to know what were the goals and why it works that way. Let's start with the API as this gives you the best introduction.

Simplified access can be got through methods:

void setData(BareJID user, String key, String value);
String getData(BareJID user, String key);

And more complex version:

void setData(BareJID user, String subnode, String key, String value);
String getData(BareJID user, String subnode, String key, String def);

Even though, the API contanins more methods, the rest is more or less variation of presented above. Complete API description for all access methods is available in JavaDoc documentation to UserRepository interface. So we are not going into much details here except the main idea.

We are more or less operate on <key, value> pairs for the particular user. The idea befind this was to make the API very simple and also at the same time very flexible, so adding a new plugin or component would not require database schema change, adding new tables, conversion of the DB schema to a new version, etc....

As a result UserRepository interface is exposed to all the Tigase code, mainly components and plugins (let's call all of them modules), and these modules simply call set/get methods to store or access module specific data.