www.archive-org-2013.com » ORG » J » JABBERDOC

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 45 . Archive date: 2013-09.

  • Title: Jabberd 2 Documentation Project
    Descriptive info: .. Jabberd 2 Documentation Project.. Home.. Welcome to the Jabberd 2 Documentation Wiki.. About This Site.. This site is dedicated to fully documenting the Jabberd 2 server.. Jabber is the set of standards that provides for an open instant messaging (IM) platform that offers a rich feature set, including encryption, asynchronous messaging, and connectivity with proprietary IM platforms.. The Jabberd server is the original implementation of the Jabber protocols, which are now known as Extensible Messaging and Presence Protocol (XMPP).. Jabberd 2 is the successor to the widely-used Jabberd 1.. 4 server.. Onsite Documentation.. Jabberd 2  ...   Archives.. XMPP Standards Foundation.. XMPP Protocols.. XMPP FAQ.. Jabber.. org.. Jabber/XMPP Mail Lists.. Books and Publications.. Protocole Jabber/XMPP.. (2011).. Professional XMPP Programming with JavaScript and jQuery.. (2010).. XMPP: The Definitive Guide.. (2009).. U.. S.. Joint Forces Command licenses Jabber.. (2005).. Jabber Developer's Handbook.. (2003).. Instant Messaging in Java: The Jabber Protocol.. (2002).. Programming Jabber.. 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..

    Original link path: /
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Up.. Next.. Jabberd 2 Installation and Administration Guide.. This is the full.. Jump to the.. FAQ.. or the.. Quick Start Guide.. for quick answers.. Table of Contents.. Introduction.. 1.. 1.. Purpose and Scope.. 2.. Required Background.. 3.. How to Use This Document.. 4.. Conventions Used in this Document.. 5.. Further Reading.. 6.. Legalese.. 7.. Sources.. Preparation for Jabberd 2.. 2.. Gather Required Information.. Create Jabber User and Group.. Create Directories for PID's and Logs.. Install Prerequisites.. Installing Jabberd 2.. 3.. Download Jabberd 2.. Extract Jabberd Installation Files.. Configure the Jabberd Build.. Build Jabberd.. Install Jabberd.. Default File Locations.. Set Ownership of Configuration Files.. Basic Configuration.. 4.. Set Host Name in sm.. xml and c2s.. xml.. Provision and Configure for Storage and Authentication Package(s).. Provision and Configure for Berkeley DB.. Provision and Configure for MySQL.. Provision and Configure for PostgreSQL.. Provision and Configure for PAM.. Provision and Configure for OpenLDAP.. 8.. Test Server.. Common Configuration Tasks.. 5.. Configuring Firewall for Internet Access.. Configuring Jabberd 2 for SSL Connections.. Changing Router Password.. Creating an Administrative User.. Disabling Public Registration.. Enabling User Password Change.. Setting DNS SRV Records.. Using Jabberd 1.. 4 to Connect to  ...   Sm.. 9.. Jabberd Identification.. Communication with the Router.. Logging.. Database Connection and Configuration.. Access Control for Administrative Functions.. Modules that Are Called during Sessions.. Static Discovery Settings for Legacy Components.. User Options.. Resolver.. 10.. PID File.. S2s.. 11.. Network Configuration.. S2S Connection Checking.. c2s.. 12.. Input/Output Contro.. Client Authentication and Registration.. Jabberd 2 Architecture (Draft).. 13.. Jabber Network Architecture.. Jabberd 2 Component Architecture.. Jabberd 2 Module Decomposition.. Jabberd 2 Data Handling.. Jabberd 2 Data Structure (for MySQL).. Appendices (including Quickstart Guide and FAQ):.. A.. Installing OpenSSL for Jabberd 2.. Installing Berkeley DB for Jabberd 2.. Installing MySQL for Jabberd 2.. Installing Libidn for Jabberd 2.. Generating A Self-Signed SSL Key.. Jabberd for Corporate Use.. Automatic Startup and Shutdown Using an RC Script.. Automatic Startup and Shutdown Using Daemontools.. Using Jabber for Linux System Monitoring.. Using the jabber_alert.. pl Script.. Using the job_mon.. sh Script to Monitor Jobs.. Using the sys_mon.. sh Script to Monitor System Resources.. Using the sys_debug.. sh script for System Debugging.. Using the email_alert.. sh Script to Receive Time Sensitive Email.. Using Jabber with Mon and Nagios.. Primer on Transports and Jabberd 2.. 12.. Troubleshooting Tips for Jabberd 2..

    Original link path: /admin_guide.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Appendices.. Quickstart Guide.. Back.. Jabberd 2 Quick Start Guide.. This guide is intended to get Jabberd 2 installed and running as quickly as possible:.. 1).. Install OpenSSL.. 2).. Install Berkeley DB.. 3).. Install Libidn.. 4).. 5).. Create Directories for Data and Logging.. 6).. Install Jabberd 2.. 7).. Configure Server.. 8).. Jabberd 2 can use MySQL, PostgreSQL or Berkeley DB to store its data.. MySQL is the recommended database for Jabberd 2; however, this guide suggests using Berkeley DB because it requires the least amount of configuration for Jabberd 2 data storage.. See the.. Jabberd 2 Installation and Administrative Guide.. for a detailed guide to installing and configuring Jabberd 2.. Install OpenSSL.. Jabberd 2 requires that OpenSSL (version 0.. 6b or higher) be installed prior to installing Jabberd 2.. If OpenSSL version 0.. 6b is not installed on your system, see the.. OpenSSL.. site or.. Installing OpenSSL for Jabberd.. Install Berkeley DB.. Jabberd 2 requires Berkeley DB version 4.. 24 or higher; if this is not installed on your system, see the.. Berkeley DB.. Consideration should be exercised when choosing a data store for a Jabberd 2 production server because converting from one database to another may be difficult.. Install Libidn.. Jabberd 2 requires Libidn version 0.. 0 or higher; if this is not installed on your system, see the.. GNU Libidn.. Create Jabber User and Group.. You should create a specific.. jabber.. user and group to run the server:.. su groupadd jabber useradd -g jabber jabber.. Note that the above commands are intended as an example.. The commands and parameters for adding a user and group may vary for your system.. Consult your manuals if you have any doubt about these commands.. Create Directories Data, Logging and PID's.. You should create directories for data, logging and PID's, and your jabber user will need read and write permissions on these directories.. Create Data Directory.. Create a directory to store the Jabberd database files (as superuser):.. mkdir -p /usr/local/var/jabberd/db.. Create Log Directory.. Create a directory to store Jabberd log files (as superuser):.. mkdir -p /usr/local/var/jabberd/log.. 3 Create PID Directory.. Create a directory to store Jabberd PID files (as superuser):.. mkdir -p /usr/local/var/jabberd/pid.. Set Ownership for Data and Log Directories.. Change the ownership of the directories created above (as superuser).. If you used the locations specified above, enter the command:.. chown -R jabber:jabber /usr/local/var/jabberd.. Install Jabberd 2.. This section describes how to download, configure, build and install Jabberd 2 on your system.. Download Jabberd.. Download the file.. jabberd-2.. n.. tar.. gz.. from the.. xiaoka.. com.. , where "2.. n" is the latest stable version of Jabberd 2.. Download the file referenced above into a convenient directory for building the installation files.. At the time of writing, Jabberd 2 stable 3 is the latest version and is used in the examples below.. Extract Jabberd Installation Files.. Change to the directory where you downloaded the  ...   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.. com /id.. Note that this.. must be resolvable by the clients that will be connecting to your Jabberd server.. Using an IP address as the.. should work; however, this is strongly discouraged.. Set authreg module to use in.. Further down in.. is a section labeled.. Authentication/registration database configuration.. This is where the.. authreg.. data module is specified.. Edit the.. module.. tag so that Berkeley DB is specified as the.. Backend module to use.. Throughout Jabberd configuration, Berkely DB is abbreviated to.. db.. Therefore, you should edit the.. tag as below:.. !-- Authentication/registration database configuration -- authreg !-- Backend module to use -- module db /module.. At the top of.. is the.. setting for hostname.. tag with the same hostname specified in section A.. 1 above:.. 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.. Set storage module to use in.. Storage database configuration.. storage.. Edit this section as below so that Berkely DB is specified as the.. data driver to use:.. !-- Storage database configuration -- storage !-- By default, we use the MySQL driver for all storage -- driver db /driver.. Test Server.. If you have created the logging and data directories specified above, you should be able to start your Jabberd 2 server and connect to it.. Starting Jabberd 2.. Start your Jabberd 2 server by using the start up script:.. su su jabber /usr/local/bin/jabberd.. If your server fails to start, you can start Jabberd 2 with the debug option (note that this requires building Jabberd 2 with the debug option see section A.. 3 above):.. /usr/local/bin/jabberd -D.. Connecting to your Jabberd Server.. You should now be able to connect to your Jabberd server, and create a new account.. Your account name should be something like.. someuser@somemachine.. If you are unable to connect, make certain that the hostname used (sections A.. 1 and A.. 3) is resolvable from the machine on which the client is running.. Further Configuration.. Once your server is running, you may wish to configure it further.. See especially Section 5,.. , for further information about Jabberd configuration..

    Original link path: /quickstart.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Jabberd 2 FAQ.. General.. I've read the guide and the FAQ; however, I still have a question.. Where can I search for answers?.. Where is the Jabberd 2 homepage?.. There's a feature that I'd like to see included with Jabberd 2.. Where should I post my suggestion?.. I think I've found a bug in Jabberd 2.. Where should I post this information?.. How does Jabberd 2 handle multiple domains?.. When will components be available for Jabberd 2?.. How do I get existing components to work with Jabberd 2?.. Client-Side Issues.. I just created a user in the database.. Why can't I login as the user I just created?.. Building and Installation.. Why does configuration fail to find my MySQL installation?.. Where can I find packages (RPM's, Debian, etc.. ) for Jabberd 2?.. When configuring Jabberd 2 stable 3, why does configure say it cannot find Libidn?.. When configuring Jabberd 2 Stable 3, why can't configure find MySQL (or other package) that worked fine with a previous release?.. Why does Jabberd 2 stable 3 crash after a successful configure and build?.. Database Specific.. Why do login and user-create fail on my installation using PostgreSQL?.. Why does.. /configure fail to find my Berkeley DB installation?.. When working in the MySQL console, why can't I query table names that are hyphenated?.. I just installed Jabberd 2 stable 3.. Why do I get errors stating that the database connection to MySQL failed?.. System Specific.. On Redhat, why does.. /configure fail to find MySQL?.. On Redhat 9, why does the build crash after a successful configure?.. /configure fail to find Berkeley DB even when I specify a path to it?.. On Mandrake, why does.. /configure fail with the error that mysql (or pgsql)cannot be found?.. On a clean Debian install, why does.. Q.. There are several good sources for answers.. The Jabber FAQ's cover general Jabber questions:.. Jabberd 2 Homepage.. XMPP Wiki.. You can also try searching the.. Jabberd 2 Mailing List Archives.. for questions about jabber administration, or subscribe to the.. Jabberd 2 Mailing List.. or one of the.. Jabber Mailing Lists.. to post your own question.. You may also want to check out.. If you are confident that you've found a bug, you can post it to the.. Jabberd 2 Bug List.. You can add multiple ID's to the Client to Server (C2S) configuration; however, you have to setup individual instances of the session manager (SM) for each domain.. A: Existing components can all be made to work with Jabberd 2.. Jabberd 2 does not have an internal component API, so shared object components are impossible.. "External" components (ie components that connect to a Jabber server over TCP using the "jabber:component:accept" protocol will work as-is.. Simply configure the component to connect to the router using the port and secret specified in router.. "Internal" or "library load" components that load at runtime into a jabberd 1.. 4 instance can be used by placing the 1.. 4 instance into "uplink" mode.. An appropriate "linker" alias needs to be added to router.. xml to support this.. Jabberd 2  ...   with the Jabberd 2 distribution.. This is due to a licensing conflict.. Users must install Libidn themselves.. See.. Section 2.. and.. Appendix 5.. The configure script and options have changed with Jabberd 2 stable 3.. The.. --with-package=path.. has been replaced with.. --with-extra-include-path path.. --with-extra-library-path path.. The paths searched also changed with stable 3; therefore, it may be necessary to specify a path(s) to a package that was automatically found by a previous release.. Section 3.. --enable-authreg=package.. --enable-storage=package.. have been replaced with a simpler.. --enable-package.. option.. Thus to enable MySQL for authreg and/or storage, one would use the option.. --enable-mysql.. Because the configure script does not report invalid options, using an option such as.. --enable-authreg=mysql.. would cause neither the configure nor the build to crash; however, the MySQL driver would not be compiled in.. If you then set the XML configuration files to use MySQL, Jabberd 2 would crash.. PostgreSQL.. In order for PostgreSQL to work with Jabberd 2, PostgreSQL must be setup to accept TCP/IP connections.. Verify that PostgreSQL is listening on an inet socket (.. netstat -l |grep postgres.. If not, modify.. postgresql.. conf.. , setting.. tcpip_socket = true.. and restart.. If problems still exist, check the.. pg_hba.. conf file.. and check if TCP/IP connections are authorized (i.. e.. an appropriate host record exists).. Berkeley DB.. /configure.. script searches several locations; however, if the script cannot find your Berkeley DB installation, you should specify the location as a parameter when running.. For example, if you are running Berkeley DB version 4.. 2, you may need to run.. as below:.. /configure --with-berkeley-db=/usr/local/BerkeleyDB.. 2/.. MySQL.. In MySQL statements, you need to enclose hyphenated names with back ticks as shown below:.. select `collection-owner`, `object-sequence`, `jid`, `group` from `roster-groups`;.. Jabberd 2 stable 3 connects to the MySQL server socket at.. /tmp/mysql.. sock.. The default socket when installing MySQL from source is.. /var/lib/mysql/mysql.. You will need to create a symlink to.. if it does not exist:.. ln -s /var/lib/mysql/mysql.. sock /tmp/mysql.. sock.. Redhat.. The most likely reason for.. to fail on Redhat is that Redhat ships with a MySQL installation that does not include the development libraries required by Jabberd 2.. See the MySQL question under.. Building and Installation.. above.. The second reason that.. might fail is that Redhat stores the MySQL libraries and include files separately.. Run.. with both paths (as below) to identify both locations:.. /configure --with-mysql=/usr/include/mysql:/usr/lib/mysql.. The most likely reason for the build to crash on Redhat 9 is that RH 9 ships with its own version of Kerberos.. The OpenSSL libraries are found when.. is run.. However, Kerberos references cause the Jabberd 2 build to crash.. There is an easy work around for this problem.. Execute the command below before running.. :.. export CFLAGS="-I/usr/kerberos/include".. If.. cannot find Berkeley DB, it may be because libpthreads is not linked.. as below to fix this:.. /configure [options] LDFLAGS=-lpthread.. Mandrake.. Either the database include files or library files cannot be found by.. To fix this, run.. with the paths to both as below (replacing "mysql" with "pgsql" for PostgreSQL installations):.. Debian.. On Debian, zlib must be installed..

    Original link path: /app_faq.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Introduction.. This document comprises the installation and administrative guide for the.. Jabberd 2 Server.. (Jabberd), the latest release of the popular open source messaging system based on the.. The goal of Jabber/XMPP is to provide an XML protocol for synchronous and asynchronous communication for client to client, client to server, and server to server messaging, although the primary use for Jabber is instant messaging (IM).. The Jabberd server is the original open-source server implementation of the Jabber protocol, and it remains the most popular software for deploying Jabber either inside a company or as a public IM service.. Jeremie Miller initiated the Jabber Project in 1998 as a free and open alternative to proprietary IM services.. The Jabberd server continues to be the core of the Jabber Project, and Jabberd 2 is the successor to the widely used Jabberd 1.. Jabberd 2 is based on a completely new code base with a new architecture, additional features and improved adherence to the Jabber protocol.. The creation of a common messaging protocol, now known as.. XMPP.. (Extensible Messaging and Presence Protocol), has allowed for the creation of numerous Jabber server implementations in addition to the Jabberd server.. Among these are many open source projects as well as several commercial offerings.. Purpose and Scope.. The authors of this document intend to provide a complete guide for jabberd 2 installation, administration and development:.. System Preparation.. Server Installation.. Server Configuration.. Architecture Overview.. The intended audience are people who wish to install and/or maintain a jabberd 2 server on Unix, or one of its variants.. As such, this document covers jabberd installation on Unix operating systems only.. Required Background.. The authors have made every attempt to make this a step-by-step guide; however, some familiarity with a Unix or Linux operating system is assumed:.. Ability to use a Linux command-prompt console.. Familiarity with the file system on which your server is to be installed.. Familiarity with a text editor, such as vi, Nano or NEdit.. Basic ability to edit XML files.. It is assumed that the reader has a basic familiarity with using a Jabber client.. Additionally, it is assumed that the reader is familiar with hardware and software, such as a firewall, router or modem, that the jabber server will use to connect to the Internet if any such hardware is used.. Configuration of these secondary programs and devices is beyond the scope of this guide.. How to Use This Document.. This guide is organized into sections grouped according to intended use by the user:.. Installing and Configuring Jabberd 2.. (Sections 2-4).. Common Configuration and Administration Tasks.. (Sections 5-6).. Overview  ...   about your setup (Parameters) that you will need during the installation steps.. You can gather all this information before you start installing Jabberd, and then you can refer back to your list for every step that displays a.. The installation guide is organized into numbered steps and sub-steps, etc.. Users are encouraged to use the guide as a check list.. When all of the sub-steps of a step are completed, then the parent step itself is also completed.. Note that all children (sub-steps) of an "Optional Step" are optional also.. Note that the "Optional Step" designation provides information about the conditions and/or requirements under which the optional step should be performed.. Steps labeled with "External System" provide the user with information about set up that may need to be performed on a system external to jabberd.. These systems include routers, firewalls, DNS servers, etc.. "External System" notes are intended to be informational rather than comprehensive.. The remaining conventions are self-explanatory.. Note that each command listed in this guide refers to a command entered at a command prompt or at a command prompt shell, such as X-term or E-term.. Note also that in this document, the term "Jabberd" refers to the Jabberd 2 server, except where noted.. The term "Jabber" refers to Jabber-based system or systems, and "XMPP" refers to the protocol over which Jabber systems run.. This document was created using.. Structured Text.. Structured Text uses standard text formatting conventions, such as underscores, to represent formatted text.. Efforts have been made to keep the text and HTML representations close.. One exception is the use of a bang character ("!") in the text version to escape unwanted formatting in the HTML version.. "Bangs" appear at the beginning of some lines in the text version, and these can be ignored.. They do not appear in the HTML version.. Further Reading.. Jabberd 2 development information can be found in the.. are the best source of current information about the Jabberd 2 server.. Users can.. subscribe.. to receive the most up to date information.. org maintains a variety of.. Jabber/XMPP mail lists.. Of these, the.. Jadmin.. Jdev.. Juser.. lists may be useful; however, they do not seem to be well-used.. Visit the.. and the.. for information about the Jabber/XMPP Protocol.. answers basic questions about Jabber/XMPP.. Readers are encouraged to visit the.. Jadmin Archive.. for questions about jabber administration.. Legalese.. The Jabber Installation and Administration Guide is copyright (c) 2003 by Will Kamishlian and Robert Norris.. Sources.. Robert Norris, who was the initial primary Jabberd 2 developer, and the posters on the Jabberd List provided technical information for this document..

    Original link path: /section01.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Preparation for Jabberd 2.. This section will prepare you and your system to install Jabberd 2:.. Create Directories for Logging and PID's.. The table in Section 2.. lists information required for Jabberd 2 installation.. Collecting this information at this point is optional; however, completing this table now will make installation easier.. Gather Required Information.. The table below lists information that will be required during the installation process.. Information is provided for each parameter below:.. Required.. Section.. Your Information.. "Parameter" is the name of the piece of information.. Throughout this guide, specific parameters are referenced with the.. convention.. "Required is either "Y" (yes), "N" (no), or.. Option Name.. refers to the option for which the parameter is necessary.. Some entries have suggested entries for "Your Information.. " These entries represent either limited choices or default values.. Where default values are given, they are used in the examples in this guide.. For a minimal installation, complete all the required parameters.. For more information about the conditions under which an optional parameter is required, see the referenced section.. "Description" is a short description.. Again, see the referenced section for more detailed information.. Important: Table Contains Passwords.. The table below contains passwords.. If you write your passwords in the table below, store this document (or page) in a secure location.. Table 2.. Required Information for Jabberd 2 Installation.. Section(s).. Jabberd User and Group.. Y.. 2.. The Linux (or other OS) user and group that will be used to run Jabberd.. user:.. jabber.. group:.. PID Directory.. 3.. Directory in which Jabberd stores PID Files.. /usr/local/var/jabberd/pid.. Log Directory.. N.. Directory for Jabberd logs.. If not specified in configuration files, logging defaults to syslog.. /usr/local/var/jabberd/log.. Authentication Package.. 3 3.. 3,.. Third party package to be used for Jabberd authentication management.. MySQL, PostgreSQL, Berkeley DB, OpenLDAP or PAM.. Data Storage Package.. 4 4.. Third party package to be used for storage of Jabberd data.. MySQL, PostgreSQL or Berkeley DB.. Data Directory.. 1, 4.. 1,.. Directory for Berkeley DB data files.. /usr/local/var/jabberd/db.. MySQL User and Password.. 2, 4.. 2,.. MySQL user and password that Jabberd uses to connect to MySQL.. jabberd2.. password:.. secret.. PostgreSQL User and Password.. 1, 1 3, 4.. PostgreSQL user and password that Jabberd uses to connect to PostgreSQL.. OpenLDAP Connection Settings.. OpenLDAP.. 2 5.. Connection settings for your OpenLDAP server: FQDN for LDAP server (or IP), port, and LDAP version used (either v2 or v3).. OpenLDAP User and Password.. 5.. User and password needed to connect to your OpenLDAP server.. Required only if your OpenLDAP server does not permit anonymous binding (access).. OpenLDAP Query Settings.. Base DN (distinguished name) and User ID attribute used to build queries for the OpenLDAP server.. Base DN can be either the server root DN or an RDN (relative distinguished name) under which User ID's are found.. Hostname.. 4.. Hostname on which your Jabberd server is to be installed.. For Internet accessible servers, this would be something like.. somedomain.. SSL Key Location.. 1, 5.. Location of OpenSSL pemfile.. Required for SSL-encrypted communication.. /usr/local/etc/jabberd/server.. pem.. Router User and Password.. User and password used for component connections with the Jabberd Router component.. You  ...   to server communication for Jabber.. The XMPP Protocol requires that Jabber servers support TLS (Transport Security Layer).. TLS is the successor to SSL.. Note: Minimum OpenSSL Version.. Jabberd 2 relies on OpenSSL versions 0.. 6b or higher.. Important: OpenSSL Upgrade Issues.. If you upgrade OpenSSL, you may need to recompile installed software that currently relies on an older version of OpenSSL.. This warning is provided because many utilities rely on OpenSSL, and these may cease to function after OpenSSL is upgraded.. Caution is recommended when upgrading OpenSSL, and detailed instructions for upgrading OpenSSL are beyond the scope of this manual.. site for more information.. OpenSSL downloads can be found on the.. OpenSSL Source.. page.. Instructions for installing OpenSSL for Jabberd 2 are included in the appendix to this guide.. 2 Libidn.. Libidn provides necessary string manipulation functionality for Jabberd 2.. Prior to Jabberd 2 stable 3, libidn was included with the Jabberd 2 distribution; however, a licensing conflict makes it necessary that libidn be installed separately.. Note Minimum libidn Version.. Jabberd 2 relies on libidn version 0.. 0 or higher.. Libidn downloads can be found on the.. Libidn Source.. Instructions for installing libidn are included in the appendix to this guide.. Jabberd 2 has better database integration than was previously supported, and Jabberd 2 can use one of three free databases to provide data storage:.. MySQL.. Berkeley DB (4.. 24 or higher).. PostgreSQL.. MySQL is the recommended and default data store.. A file may be used for storing Jabberd 2 data; however, this is not recommended.. Note: MySQL and Unicode Support.. MySQL versions 4.. 1 and above support Unicode (UCS-2 and UTF8) character encoding.. If your installation requires support for multiple alphabet encodings, and you wish to use MySQL, choose a version 4.. 1 or above.. If you have one of these databases installed, you may configure it to work with Jabberd.. Otherwise, you should choose one of these databases and install it prior to continuing with Jabberd installation.. MySQL is the recommended database; however, Berkeley DB requires the least installation and administration effort.. Thus, Berkeley DB may be ideal for an installation with a relatively small number of users.. Important: MySQL Requires Development Libraries and Headers.. Note that Jabberd requires more than a minimal MySQL installation.. It may be necessary to uninstall your current MySQL installation in order to install the additional libraries.. Appendices to this document contain instructions for installing either MySQL or Berkeley DB for Jabberd 2.. or.. Jabberd 2 can use one of five free third-party authentication data packages to handle user authentication:.. Berkeley DB (version 4.. OpenLDAP (version 2.. PAM.. Note that the three supported application data packages can also be used to manage authentication information.. Therefore, installing one of MySQL, Berkeley DB or PostgreSQL satisfies both Jabberd data package requirements.. A file may be used to store authentication data; however, this is not recommended.. The recommended and default package is MySQL.. If you have one of the above five authentication data packages installed, you may configure it for use with Jabberd 2.. If not, you should install one or more of the above five packages..

    Original link path: /section02.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: This section describes how to build and install Jabberd 2.. Download Jabberd 2.. Required File.. Download the file referenced above into a directory in.. /home.. for building the installation files.. At the time of writing, Jabberd 2 stable release 3 is the latest version and is used in the examples below.. Configure the Jabberd Build.. Optional: View Configuration Options.. Prior to configuring Jabberd, you can view all configuration options by running the command:.. /configure --help.. This will provide a listing and syntax for setting configuration options.. For example, you may choose to install Jabberd into a specific directory by using the.. --prefix=PREFIX.. By providing a.. PREFIX.. path, all Jabberd files will be installed under this directory.. This may be useful if you are testing a new Jabberd installation.. Another useful option is.. This option allows Jabberd to provide detailed debugging information; however, it should be used carefully on production systems.. Important: Configuration Options Have Changed with Stable Release 3.. Jabberd 2 stable 3 introduced changes in the parameters for the.. configuration.. script.. The information below pertains to Jabberd 2 stable 3 and above.. Important: Use Explicit Options for OpenSSL and Libidn.. It is recommended that Jabberd 2 be configured with explicit options for OpenSSL and Libidn.. These packages are technically optional.. Therefore,.. configure.. may build Jabberd 2 without them if their libraries and headers are not found when.. us run.. Parameters: Application Data Package and Authentication Data Package.. The authentication and storage packages should be specified with the.. --enable-.. Options are.. --enable-pgsql.. --enable-db.. --enable-pam.. --enable-ldap.. Although.. is the default, it is recommended that this be specified  ...   Ignored.. Jabberd ignores incorrect configuration parameters.. Thus, an incorrectly entered configuration parameter might lead to a successful, however incorrect, Jabberd configuration.. if in doubt.. Important: Redhat 9 Configuration.. Building Jabberd 2 on Redhat 9 requires special configuration because Redhat 9 ships with its own version of Kerberos.. For more details, see the.. about Redhat 9.. If you wish to use the default configuration, simply run the configuration command:.. /configure.. This will configure Jabberd to use MySQL and to install to.. If you receive errors, you may wish to check the.. where you will find several system-specific work arounds.. Build Jabberd by running the command:.. /usr/local/etc/jabberd Jabberd Configuration Files /usr/local/bin Jabberd Binaries (jabberd, c2s, resolver, router, s2s, sm).. Set Ownership of Configuration Files.. Jabberd configuration files contain passwords; therefore, you should set ownership and permissions on these files so that they are only readable by your.. user and writable by root only.. Using the location of your configuration files and your.. user, set ownership of these files:.. chown -R root:jabber /usr/local/etc/jabberd/*.. Then, set permissions on these files so that others can neither read from- or write to them:.. chmod -R 640 /usr/local/etc/jabberd/*.. Now, only your.. user and super-user will be able to read and edit your configuration files.. Optional: Create Symlink for Configuration Files.. If you used the default file locations when installing Jabberd, you may wish to create a symlink (as superuser) in.. /etc.. for the configuration files.. This will make it easier to find and edit them:.. ln -s /usr/local/etc/jabberd/ /etc/jabberd.. Jabberd 2 is now installed.. Continue to the next section to being configuring your installation..

    Original link path: /section03.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Basic Configuration.. 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:.. Set Host Name (sm.. xml).. 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.. beforehand.. Set Host Name in.. The first step in basic configuration consists of setting the hostname in.. Parameter: Hostname.. Your server hostname (network ID) must be set in both.. so that the ID provides a network resolvable reference for your server.. this ID is found under the heading labeled.. Local network configuration.. (approx.. line 63), and in.. this ID is found under.. Session manager configuration.. (line 1).. Edit.. so that this ID references your server.. !-- Session manager configuration -- sm !-- Our ID on the network.. !-- Local network configuration -- local !-- Who we identify ourselves  ...   Section 5.. for information about setting up DNS SRV records for Jabberd 2.. Provision and Configure for Storage and Authentication Package(s).. Getting Jabberd 2 to work with your choice of external.. packages involves these steps:.. Provision external package(s) to work with Jabberd 2.. Configure.. for your choice of.. package.. Most Jabberd 2 installations rely on a single package, such as MySQL, to provide both.. 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.. Parameters: Data Storage and Authentication Packages.. Follow the guide to complete relevant subsections for your choice(s) of.. packages.. (Berkeley DB, MySQL or PostgreSQL for storage.. Berkeley DB, MySQL, PostgreSQL, PAM or OpenLDAP for authentication.. Start by jumping to your selection of external.. package:.. Provisioning and Configuring for Berkeley DB.. Provisioning and Configuring for MySQL.. Provisioning and Configuring for PostgreSQL.. You will then be guided to continue on to provision (if necessary) and configure your.. package.. Once your external packages are prepared, and Jabberd is configured to use them, you will guided to.. Server Testing..

    Original link path: /section04.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Provision and Configure for Berkeley Berkeley DB.. provides the easiest means to getting your Jabberd 2 server up and running quickly.. Jabberd 2 requires a minimum version of 4.. 24 or higher.. Provisioning Berkeley DB.. Complete this section if you are using Berkeley DB for storage and/or authorization.. Provisioning your system to use Berkeley DB is quite simple.. Berkeley DB only needs a directory in which to store data files, and this directory should be owned by the jabber user and group.. Parameter: Data Directory.. Create a directory and set permissions (using the user and group created above) for Berkeley DB.. (as superuser):.. mkdir -p /usr/local/var/jabberd/db chown -R jabber:jabber /usr/local/var/jabberd.. Berkeley DB is now ready to be used with Jabberd.. Configure for Storage using Berkeley DB (.. ).. Complete this section if you are using Berkeley DB for storage.. Jabberd 2 requires minimal configuration to use Berkeley DB for backend storage.. Simply set the driver to use and specify  ...   disk after each write.. If you disable this, database accesses may be faster, but data may be lost if jabberd crashes.. -- sync/ /db.. Jabberd 2 is now configured to use Berkeley DB for.. If you wish to use an.. package other than Berkeley DB, jump to your selection of.. Otherwise, continue on to 4.. directly below to finish your Jabberd 2 configuration.. Configure for Authentication using Berkeley DB (.. Complete this section if you are using Berkeley DB for authentication.. Jabberd 2 authentication configuration for Berkeley DB is the same as above, except that the information is contained in.. Berkeley DB module configuration.. !-- Berkeley DB module configuration -- db !-- Directory to store database files under -- path /usr/local/var/jabberd/db /path !-- Synchronize the database to disk after each write.. Your Jabberd 2 configuration for storage and authentication is now complete.. Jump to.. to begin testing your server before moving on other configuration tasks, such as configuring SSL, in..

    Original link path: /section04_3.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Provision and Configure for MySQL.. is the default Jabberd 2 package for storage and authentication.. Provision for MySQL.. Complete this section if you are using MySQL for storage and/or authorization.. In order to set up MySQL for Jabberd, you must run the setup script included in the Jabberd 2 distribution.. After the script is run, you should create a user and then grant that user access to the database.. First, run the MySQL setup script.. This script is located in '[Jabberd Source Files]/tools'.. Switch to the.. tools.. directory and start the MySQL console (the MySQL server should already be running).. Then, run the.. db-setup.. mysql.. script from the MySQL console:.. mysql -u root -p mysql \.. mysql.. Now that a database for Jabberd exists in the MySQL data directory, create a MySQL user that Jabberd can use to connect to the MySQL server.. Parameter: MySQL User and Password.. From the MySQL console, run the SQL statement below, replacing.. secret.. with the password you have chosen for your Jabberd MySQL user:.. GRANT select,insert,delete,update ON jabberd2.. * to jabberd2@localhost IDENTIFIED by 'secret';.. Note that the password.. is the default password used in the Jabberd configuration files for MySQL.. MySQL is now ready to be used with Jabberd.. Note: Default MySQL Socket.. If you are unsure as to where your MySQL server socket is, consult your MySQL configuration file (usually located in.. /etc/my.. cnf.. /etc/mysql/my.. Configure for  ...   -- dbname jabberd2 /dbname !-- Database username and password -- user jabberd2 /user pass secret /pass !-- Transaction support.. If this is commented out, transactions will be disabled.. This might make database accesses faster, but data may be lost if jabberd crashes.. This will need to be disabled if you are using a MySQL earlier than v3.. 23.. xx, as transaction support did not appear until this version.. -- transactions/ /mysql.. Note that you should change the host setting only if your MySQL server is running on a different host.. You should change the port setting only if your MySQL server is running on a non-standard port (port 3306 is the default for MySQL installations).. The transaction support section is self-explanatory.. Jabberd 2 is now configured to use MySQL for.. package other than MySQL, jump to your selection of.. Configure for Authentication using MySQL (.. Complete this section if you are using MySQL for authentication.. Jabberd 2 authentication configuration for MySQL is the same as above, except that the information is contained in.. Parameter: Authentication Data Package.. !-- Authentication/registration database configuration -- authreg !-- Backend module to use -- module mysql /module.. MySQL module configuration.. !-- MySQL module configuration -- mysql !-- Database server host and port -- host localhost /host port 3306 /port !-- Database name -- dbname jabberd2 /dbname !-- Database username and password -- user jabberd2 /user pass secret /pass /mysql..

    Original link path: /section04_4.html
    Open archive

  • Title: Jabberd 2 Documentation Project
    Descriptive info: Provision and Configure for PostgreSQL.. , like MySQL provides a very manageable backend for storage and authentication.. Unlike MySQL, PostgreSQL provides better unicode support.. Provision PostgreSQL.. Complete this section if you are using PostgreSQL for storage and/or authorization.. In order to set up PostgreSQL for Jabberd, you must create a database, create a PostgreSQL user and then run the PostgreSQL script included in the Jabberd 2 distribution.. Create the database for Jabberd.. (The PostgreSQL server should already be running):.. createdb -U postgres jabberd2.. The command above will create a database from which you will be able to run the script for setting up the Jabberd PostgreSQL database.. Note: Unicode Support.. If you want to enable Unicode support for your PostgreSQL database, change the command above to the following:.. createdb -U postgres -E UNICODE jabberd2.. Now that your database is created, create a PostgreSQL user for the database.. Parameter: PostgreSQL User and Password.. To create your Jabberd database user, enter the command below:.. createuser -P -U postgres jabberd2.. This command will initiate an interactive user creation script.. When prompted, enter the password that Jabberd will use to connect to your PostgreSQL database:.. Enter password for user "jabberd2": Enter it again: Shall the new user be allowed to create databases? (y/n) n Shall the new user be allowed to create more  ...   !-- By default, we use the MySQL driver for all storage -- driver pgsql /driver.. PostgreSQL driver configuration.. with your PostgreSQL password.. !-- PostgreSQL driver configuration -- pgsql !-- Database server host and port -- host localhost /host port 5432 /port !-- Database name -- dbname jabberd2 /dbname !-- Database username and password -- user jabberd2 /user pass secret /pass !-- Transaction support.. -- transactions/ /pgsql.. Note that you should change the host setting only if your PostgreSQL server is running on a different host.. You should change the port setting only if your PostgreSQL server is running on a non-standard port (port 5432 is the default for PostgreSQL installations).. Jabberd 2 is now configured to use PostgreSQL for.. package other than PostgreSQL, jump to your selection of.. Configure for Authentication using PostgreSQL (.. Complete this section if you are using PostgreSQL for authentication.. Jabberd 2 authentication configuration for PostgreSQL is the same as above, except that the information is contained in.. !-- Authentication/registration database configuration -- authreg !-- Backend module to use -- module pgsql /module.. PostgreSQL module configuration.. !-- PostgreSQL module configuration -- pgsql !-- Database server host and port -- host localhost /host port 5432 /port !-- Database name -- dbname jabberd2 /dbname !-- Database username and password -- user jabberd2 /user pass secret /pass /pgsql..

    Original link path: /section04_5.html
    Open archive


  • Archived pages: 45