This section provides a quick road map for the most basic configuration and testing of your Jabberd 2 installation. Basic setup for Jabberd 2 consists of these three steps:
Jabberd 2 is configured via its six XML files. For default installations,
these configuration files can be found in
/usr/local/etc/jabberd/, and they are accessible from
/etc/jabberd if you created the symlink for this directory.
Note that this section is easier to complete if you gather the required
information in Section 2 beforehand.
The first step in basic configuration consists of setting the hostname in
sm.xmlso that the ID provides a network resolvable reference for your server. In
c2s.xmlthis ID is found under the heading labeled
Local network configuration(approx. line 63), and in
sm.xmlthis ID is found under
Session manager configuration(line 1). Edit
c2s.xmlso that this ID references your server.
<!-- Session manager configuration --> <sm> <!-- Our ID on the network. Users will have this as the domain part of their JID. If you want your server to be accessible from other Jabber servers, this ID must be resolvable by DNS.s (default: localhost) --> <id>somemachine.somedomain.com</id>
<!-- Local network configuration --> <local> <!-- Who we identify ourselves as. This should correspond to the ID (host) that the session manager thinks it is. You can specify more than one to support virtual hosts, as long as you have additional session manager instances on the network to handle those hosts. The realm attribute specifies the auth/reg or SASL authentication realm for the host. If the attribute is not specified, the realm will be selected by the SASL mechanism, or will be the same as the ID itself. Be aware that users are assigned to a realm, not a host, so two hosts in the same realm will have the same users. If no realm is specified, it will be set to be the same as the ID. --> <id>somemachine.somedomain.com</id>
c2s.xml file notes, this is the hostname that will be
appended to your user names to create Jabber ID's, and it must be
resolvable via DNS for Jabberd to be accessible via the Internet.
somedomain.com) for your Jabberd 2 network ID if your DNS is configured properly to resolve that ID to your server. See Section 5.7. for information about setting up DNS SRV records for Jabberd 2.
Getting Jabberd 2 to work with your choice of external storage and authentication packages involves these steps:
sm.xmlfor your choice of storage package
c2s.xmlfor your choice of authentication package
Most Jabberd 2 installations rely on a single package, such as MySQL, to
provide both storage and authentication services. If your
installation relies on a single package, you will need to configure this
package for Jabberd 2 and then enter similar connection details in both
Start by jumping to your selection of external storage package:
You will then be guided to continue on to provision (if necessary) and configure your authentication package. Once your external packages are prepared, and Jabberd is configured to use them, you will guided to Server Testing.
|© 2003 Will Kamishlian and Robert Norris|
|This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.|