Release Note ejabberd 0.9 - 18 Apr 2005

This document describes the major new features of and changes to ejabberd 0.9, compared to latest public release ejabber 0.7.5.

The code can be downloaded from the download page.

For more detailed information, please refer to ejabberd User Guide.

Virtual Hosting

ejabberd now can host several domain on the same instance. This option is enabled by using:

instead of the previous host directive.

Note that you are now using a list of hosts. The main one should be the first listed. See the migration section further in this release note for details.

Shared Roster

Shared roster is a new feature that allow the ejabberd administrator to add jabber user that will be present in the roster of every users on the server.

Shared roster are enabled by going through the following steps:

• Add {mod_shared_roster, []} at the end of your module list in your ejabberd.cfg file.
• Restart ejabberd.
• Go to the Webadmin. If the module is correctly enabled there'll be a link 'Shared Roster'. Normally, the URL should be something like: http://localhost:5280/admin/shared-roster/
• Create a new group with an identifier (for example: test).
• The group will be added to the list of groups. Click on it.
• Here you will configure that group, through the form:
  
  
  • Name: is the nice name of the group on the user's rosters (for example: Test Group).
  • Description: is a description (for example: This group is just for testing)
  • Members: list of members of the group, one Jabber ID per line. For example:

    user1@localhost
    user2@localhost
    user3@localhost

• Displayed Groups: Put here the group identification (for example: test).

PostgreSQL (ODBC) support

This feature is experimental and not yet properly documented. This feature is released for testing purpose.

You need to have Erlang/OTP R10 to compile with ODBC on various flavour of *nix. You should use Erlang/OTP R10B-4, as this task has became easier with this release. It comes already build in Erlang/OTP Microsoft Windows binary.

PostgreSQL support is enabled by using the following module in ejabberd.cfg instead of their standard counterpart:

• mod_last_odbc.erl
• mod_offline_odbc.erl
• mod_roster_odbc.erl

The database schema is located in the src/odbc/pq.sql file.

Look at the src/ejabberd.cfg.example file for more information on how to configure ejabberd with odbc support. You can get support on how to configure ejabberd with a relational database.

Migration from ejabberd 0.7.5

Migration is pretty straightforward as Mnesia database schema conversions is handled automatically. Remember however that you must backup your ejabberd database before migration. If you do not plan to use any new ejabberd 0.9 feature, you can keep your ejabberd 0.7.5 config file, as it is compatible with this new release.

Here are the following steps to proceed:

• Stop your instance of ejabberd.
• In ejabberd.cfg, define the host lists. Change the host directive to the hosts one: before migration:
  {host, "erlang-projects.org"}.

  and after migration:

  {hosts, ["erlang-projects.org", "erlang-fr.org"]}.

  Note that when you restart the server the existing users will be affected to the first virtual host, so the order is important. You should keep the previous hostname as the first virtual host.

• Restart ejabberd.

Bugfixes

This release contains several bugfixes and architectural changes. Please refer to the Changelog file supplied with this release for details of all improvements in the ejabberd code.