Implementation of Jabber server

One thing I forget to write.
I would like a client with good hebrew support.
Thanks.

Hey,

well, Openfire has a nice Webinterface but in my oppinion thats more or less all. Openfire is great for smaller deployments because it is that easy to use. Everything under 100 users, Openfire is great.

But for larger deployments I would recommend using Tigase or eJabberd.

We deploy both servers on large scale clusters, and are quite happy with them.

Greets,

Florian Jensen
Flosoft.biz

[quote]
But for larger deployments I would recommend using Tigase or eJabberd.

We deploy both servers on large scale clusters, and are quite happy with them.
[/quote]

As far as I know the Tigase XMPP Server does not support clustering functionality where all nodes serve the same XMPP domain. Is that right? Unfortunately, the tigase.org webpage seems to be not reachable ...

This is partially right. You can cluster Session Managers afaik. But full clustering support is on its way.

OpenFire may be a good candidate for you.

An openfire node can hold about 10 000 concurrent connections on a pentium 4 server, and if your organization has 2500 users, that would mean about 2000 users.

HOWEVER an openfire server without clustering is a single point of failure.

Clustering isn't cheap on it, however possible with an enterprise license.

I'm not sure if AD authentication works with ejabberd, but ejabberd can take a shellscript or anything similiar as an authentication mechanism, so it will probably do.

If there exists a java module for AD authentication then it's quite possible you can integrate it with tigase, but you should ask this tigase.org.

Think of what features do you need. If such features like web-based user management, easy, shared roster handling, monitoring, etc, and you can tolerate that there's only one server, or you can afford the enterprise license, then go for OpenFire.

If you don't want to touch anything, or you're OK with command-line tools, but you need scalability, a fault-tolerant distributed system, go for ejabberd.

if you still want to touch the code sometimes, perhaps extending it, and you have a knowledge of java (as opposed to erlang), choose Tigase.

You can also decide by the support of each community's forum :)

So I'd encourage you to ask each respective community, and then decide. Sites:

http://www.igniterealtime.org (OpenFire)
http://www.ejabberd.im/
http://www.tigase.org/

Its a bit late reply , but still... Thanks for all the replies ... I am starting my test with OpenFire ( I like the WEB interface ) and then will probably test the rest.

Thanks again,
Leonid Mishkind

Shalom Leonid,

I would like to clarify some outdated information about Openfire. Openfire can handle 250,000 concurrent connections in a single JVM when using a 64 bit OS. And half of that when using a 32 bit OS.

The enterprise plugin has been made open source except for the clustering feature that relies on a 3rd party commercial product. However, the open source version is prepared so that other clustering solutions could be hooked up. The existing clustering functionality will be available as a plugin and it just provides an implementation of clustering using Oracle Coherence.

Feel free to post any questions you might have in our support forums: http://www.igniterealtime.org/community/index.jspa

Shalom and Jag Sameaj,

-- Gato

Hi Gato,

It seems I remembered the number wrong then, I'm sorry... Trying not to do bad reputation for you, just simply remembered it wrong somehow.