0 subscribers Search:
last edited 1 year ago by Will

Jabberd 2 Installation and Administration Guide

This is the Jabberd 2 Installation and Administration Guide. Use the Search Page or the box above if you are unable to find what you are looking for. Jump to the FAQ or the Quick Start Guide for quick answers.

View Entire Document (HTML)

View Entire Document (PDF)

Table of Contents

1. Introduction
1.1. Purpose and Scope
1.2. Required Background
1.3. How to Use This Document
1.4. Conventions Used in this Document
1.5. Further Reading
1.6. Legalese
1.7. Sources

2. Preparation for Jabberd 2
2.1. Gather Required Information
2.2. Create Jabber User and Group
2.3. Create Directories for PID's and Logs
2.4. Install Prerequisites

3. Installing Jabberd 2
3.1. Download Jabberd 2
3.2. Extract Jabberd Installation Files
3.3. Configure the Jabberd Build
3.4. Build Jabberd
3.5. Install Jabberd
3.6. Default File Locations
3.7. Set Ownership of Configuration Files

4. Basic Configuration
4.1. Set Host Name in sm.xml and c2s.xml
4.2. Provision and Configure for Storage and Authentication Package(s)
4.3. Provision and Configure for Berkeley DB
4.4. Provision and Configure for MySQL
4.5. Provision and Configure for PostgreSQL
4.6. Provision and Configure for PAM
4.7. Provision and Configure for OpenLDAP
4.8. Test Server

5. Common Configuration Tasks
5.1. Configuring Firewall for Internet Access
5.2. Configuring Jabberd 2 for SSL Connections
5.3. Changing Router Password
5.4. Creating an Administrative User
5.5. Disabling Public Registration
5.6. Enabling User Password Change
5.7. Setting DNS SRV Records
5.8. Using Jabberd 1.4 to Connect to Legacy Services
5.9. Using JCR to Jabberd 2 Components
5.10. Setting up a JUD Using Users-Agent
5.11. Integrating Users-Agent with vCard Data (private servers only)

6. Common Administrative Tasks
6.1. Starting and Stopping Jabberd 2
6.2. Converting from Jabberd 1.4
6.3. Adding Users
6.4. Removing Users
6.5. Sending MOTD's and Messages to All Online Users

7. Router.xml Configuration
7.1. ID, PID and Logging
7.2. Network
7.3. Input/Output Control
7.4. Aliases
7.5. Feature Access Controls

8. Router-users.xml Configuration

9. Sm.xml Configuration
9.1. Jabberd Identification
9.2. Communication with the Router
9.3. Logging
9.4. Database Connection and Configuration
9.5. Access Control for Administrative Functions
9.6. Modules that Are Called during Sessions
9.7. Static Discovery Settings for Legacy Components
9.8. User Options

10. Resolver.xml Configuration
10.1. PID File
10.2. Communication with the Router
10.3. Logging

11. S2s.xml Configuration
11.1. PID File
11.2. Communication with the Router
11.3. Logging
11.4. Network Configuration
11.5. S2S Connection Checking

12. c2s.xml Configuration
12.1. PID File
12.2. Communication with the Router
12.3. Logging
12.4. Network Configuration
12.5. Input/Output Contro
12.6. Client Authentication and Registration

13. Jabberd 2 Architecture (Draft)
13.1. Jabber Network Architecture
13.2. Jabberd 2 Component Architecture
13.3. Jabberd 2 Module Decomposition
13.4. Jabberd 2 Data Handling
13.5. Jabberd 2 Data Structure (for MySQL)

Appendices (including Quickstart Guide and FAQ):

A.1. Quick Start Guide

A.2. Installing OpenSSL for Jabberd 2

A.3. Installing Berkeley DB for Jabberd 2

A.4. Installing MySQL for Jabberd 2

A.5. Installing Libidn for Jabberd 2

A.6. Generating A Self-Signed SSL Key

A.7. Jabberd for Corporate Use

A.8. Automatic Startup and Shutdown Using an RC Script

A.9. Automatic Startup and Shutdown Using Daemontools

A.10. Using Jabber for Linux System Monitoring
A.10.1. Using the jabber_alert.pl Script
A.10.2. Using the job_mon.sh Script to Monitor Jobs
A.10.3. Using the sys_mon.sh Script to Monitor System Resources
A.10.4. Using the sys_debug.sh script for System Debugging
A.10.5. Using the email_alert.sh Script to Receive Time Sensitive Email
A.10.6. Using Jabber with Mon and Nagios

A.11. Primer on Transports and Jabberd 2

A.12. Troubleshooting Tips for Jabberd 2

A.12. Jabberd 2 FAQ

Change Log

We encourage visitors to use the box at the bottom of the page to comment on draft sections. Note that the draft document uses the convention of two pipes "||" to delimit comments within the draft. We would greatly appreciate any help with comments marked "QUESTION".

Comments about this Document

MySQL 4 Update --2004/07/28 10:14 PST
Section 2.4.2 - MySQL 4 Features: http://dev.mysql.com/doc/mysql/en/Charset-Unicode.html

11.5 Unicode Support

As of MySQL version 4.1, there are two new character sets for storing Unicode data:

ucs2, the UCS-2 Unicode character set.

utf8, the UTF8 encoding of the Unicode character set.

.PDF vs. single page HTML vs. multi-page HTML (Aren't the same versions) --2004/07/30 12:26 PST
FYI . . . The .PDF and single HTML versions of this Admin Guide are missing the Appendix entry on "Installing Libidn for Jabberd 2". In place of Libidn, there are instructions for creating a self-signed key for SSL. Just thought you'd like to know that the .PDF and single HTML versions don't match this multi-page HTML document identically.

Re .PDF vs. single page HTML... --2004/07/30 13:12 PST
Thanks for a good set of eyes! I had failed to update the files for the full versions when I added the libidn appendix.

Re: MySQL 4 Update --Will, 2004/07/30 13:55 PST
Thanks for the MySQL update. I've changed the note to reflect the newly supported character sets. I'll remove the note altogether when MySQL 4.1 is marked stable.

2004/08/04 08:49 PST
404 @ 2nd Jadmin: You can also try searching the Jadmin Archive for questions about jabber administration, or subscribe to the Jadmin Mailing List to post your own question.


full simple minimal   UserOptions ChangeLog   loginhelp
subject:
This is not a forum for resolving Jabberd 2 issues. Post Jabberd 2 specific questions to either the jadmin or jabberd mailing lists.
 

© 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.

Powered by Zope Valid HTML 4.01! Valid CSS! Creative Commons License