- ejabberd 2.0.0-beta1
+ ejabberd 2.0.0-rc1
Installation and Operation Guide
<HR SIZE=2><BR>
<BR>
-<TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=right NOWRAP> <FONT SIZE=6><B>ejabberd 2.0.0-beta1 </B></FONT></TD></TR>
+<TABLE CELLSPACING=6 CELLPADDING=0><TR><TD ALIGN=right NOWRAP> <FONT SIZE=6><B>ejabberd 2.0.0-rc1 </B></FONT></TD></TR>
<TR><TD ALIGN=right NOWRAP> </TD></TR>
<TR><TD ALIGN=right NOWRAP> <FONT SIZE=6>Installation and Operation Guide</FONT></TD></TR>
</TABLE><BR>
<A HREF="#htoc2">1.1  Key Features</A>
</LI><LI CLASS="li-toc"><A HREF="#htoc3">1.2  Additional Features</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc4">Chapter 2  Installing ejabberd</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc4">Chapter 2  Installing <TT>ejabberd</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc5">2.1  Installing ejabberd with Graphical Installer</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc6">2.2  Installing ejabberd with Operating System specific packages</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc7">2.3  Installing ejabberd with CEAN</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc8">2.4  Installing ejabberd from Source Code</A>
+<A HREF="#htoc5">2.1  Installing <TT>ejabberd</TT> with Binary Installer</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc6">2.2  Installing <TT>ejabberd</TT> with Operating System specific packages</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc7">2.3  Installing <TT>ejabberd</TT> with CEAN</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc8">2.4  Installing <TT>ejabberd</TT> from Source Code</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc9">2.4.1  Requirements</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc10">2.4.2  Download Source Sode</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc10">2.4.2  Download Source Code</A>
</LI><LI CLASS="li-toc"><A HREF="#htoc11">2.4.3  Compile</A>
</LI><LI CLASS="li-toc"><A HREF="#htoc12">2.4.4  Install</A>
</LI><LI CLASS="li-toc"><A HREF="#htoc13">2.4.5  Start</A>
</LI><LI CLASS="li-toc"><A HREF="#htoc15">2.4.7  Specific Notes for Microsoft Windows</A>
</LI></UL>
</LI><LI CLASS="li-toc"><A HREF="#htoc16">2.5  Create a Jabber Account for Administration</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc17">2.6  Upgrading <TT>ejabberd</TT></A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc17">Chapter 3  Configuring ejabberd</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc18">Chapter 3  Configuring <TT>ejabberd</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc18">3.1  Basic Configuration</A>
+<A HREF="#htoc19">3.1  Basic Configuration</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc19">3.1.1  Host Names</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc20">3.1.2  Virtual Hosting</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc21">3.1.3  Listening Ports</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc22">3.1.4  Authentication</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc23">3.1.5  Access Rules</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc24">3.1.6  Shapers</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc25">3.1.7  Default Language</A>
+<A HREF="#htoc20">3.1.1  Host Names</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc21">3.1.2  Virtual Hosting</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc22">3.1.3  Listening Ports</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc23">3.1.4  Authentication</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc24">3.1.5  Access Rules</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc25">3.1.6  Shapers</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc26">3.1.7  Default Language</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc26">3.2  Database and LDAP Configuration</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc27">3.2  Database and LDAP Configuration</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc27">3.2.1  MySQL</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc28">3.2.2  Microsoft SQL Server</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc29">3.2.3  PostgreSQL</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc30">3.2.4  ODBC Compatible</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc31">3.2.5  LDAP</A>
+<A HREF="#htoc28">3.2.1  MySQL</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc29">3.2.2  Microsoft SQL Server</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc30">3.2.3  PostgreSQL</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc31">3.2.4  ODBC Compatible</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc32">3.2.5  LDAP</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc32">3.3  Modules Configuration</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc33">3.3  Modules Configuration</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc33">3.3.1  Overview</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc34">3.3.2  Common Options</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc35">3.3.3  <TT>mod_announce</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc36">3.3.4  <TT>mod_disco</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc37">3.3.5  <TT>mod_echo</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc38">3.3.6  <TT>mod_irc</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc39">3.3.7  <TT>mod_last</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc40">3.3.8  <TT>mod_muc</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc41">3.3.9  <TT>mod_muc_log</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc42">3.3.10  <TT>mod_offline</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc43">3.3.11  <TT>mod_privacy</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc44">3.3.12  <TT>mod_private</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc45">3.3.13  <TT>mod_proxy65</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc46">3.3.14  <TT>mod_pubsub</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc47">3.3.15  <TT>mod_register</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc48">3.3.16  <TT>mod_roster</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc49">3.3.17  <TT>mod_service_log</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc50">3.3.18  <TT>mod_shared_roster</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc51">3.3.19  <TT>mod_stats</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc52">3.3.20  <TT>mod_time</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc53">3.3.21  <TT>mod_vcard</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc54">3.3.22  <TT>mod_vcard_ldap</TT></A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc55">3.3.23  <TT>mod_version</TT></A>
+<A HREF="#htoc34">3.3.1  Overview</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc35">3.3.2  Common Options</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc36">3.3.3  <TT>mod_announce</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc37">3.3.4  <TT>mod_disco</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc38">3.3.5  <TT>mod_echo</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc39">3.3.6  <TT>mod_irc</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc40">3.3.7  <TT>mod_last</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc41">3.3.8  <TT>mod_muc</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc42">3.3.9  <TT>mod_muc_log</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc43">3.3.10  <TT>mod_offline</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc44">3.3.11  <TT>mod_privacy</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc45">3.3.12  <TT>mod_private</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc46">3.3.13  <TT>mod_proxy65</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc47">3.3.14  <TT>mod_pubsub</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc48">3.3.15  <TT>mod_register</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc49">3.3.16  <TT>mod_roster</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc50">3.3.17  <TT>mod_service_log</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc51">3.3.18  <TT>mod_shared_roster</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc52">3.3.19  <TT>mod_stats</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc53">3.3.20  <TT>mod_time</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc54">3.3.21  <TT>mod_vcard</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc55">3.3.22  <TT>mod_vcard_ldap</TT></A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc56">3.3.23  <TT>mod_version</TT></A>
</LI></UL>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc56">Chapter 4  Managing an ejabberd server</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc57">Chapter 4  Managing an <TT>ejabberd</TT> server</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc57">4.1  <TT>ejabberdctl</TT></A>
+<A HREF="#htoc58">4.1  <TT>ejabberdctl</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc58">4.1.1  Commands</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc59">4.1.2  Erlang configuration</A>
+<A HREF="#htoc59">4.1.1  Commands</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc60">4.1.2  Erlang runtime system</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc60">4.2  Web Interface</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc61">4.3  Ad-hoc Commands</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc62">4.4  Change Computer Hostname</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc61">4.2  Web Admin</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc62">4.3  Ad-hoc Commands</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc63">4.4  Change Computer Hostname</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc63">Chapter 5  Securing ejabberd</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc64">Chapter 5  Securing <TT>ejabberd</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc64">5.1  Firewall Settings</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc65">5.2  epmd </A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc66">5.3  Erlang Cookie</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc67">5.4  Erlang node name</A>
+<A HREF="#htoc65">5.1  Firewall Settings</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc66">5.2  epmd </A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc67">5.3  Erlang Cookie</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc68">5.4  Erlang node name</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc68">Chapter 6  Clustering</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc69">Chapter 6  Clustering</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc69">6.1  How it Works</A>
+<A HREF="#htoc70">6.1  How it Works</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc70">6.1.1  Router</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc71">6.1.2  Local Router</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc72">6.1.3  Session Manager</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc73">6.1.4  s2s Manager</A>
+<A HREF="#htoc71">6.1.1  Router</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc72">6.1.2  Local Router</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc73">6.1.3  Session Manager</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc74">6.1.4  s2s Manager</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc74">6.2  Clustering Setup</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc75">6.3  Service Load-Balancing</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc75">6.2  Clustering Setup</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc76">6.3  Service Load-Balancing</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc76">6.3.1  Components Load-Balancing</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc77">6.3.2  Domain Load-Balancing Algorithm</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc78">6.3.3  Load-Balancing Buckets</A>
+<A HREF="#htoc77">6.3.1  Components Load-Balancing</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc78">6.3.2  Domain Load-Balancing Algorithm</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc79">6.3.3  Load-Balancing Buckets</A>
</LI></UL>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc79">Chapter 7  Debugging</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc80">Chapter 7  Debugging</A>
<UL CLASS="toc"><LI CLASS="li-toc">
-<A HREF="#htoc80">7.1  Watchdog Alerts</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc81">7.2  Log Files</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc82">7.3  Debug Console</A>
+<A HREF="#htoc81">7.1  Watchdog Alerts</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc82">7.2  Log Files</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc83">7.3  Debug Console</A>
</LI></UL>
-</LI><LI CLASS="li-toc"><A HREF="#htoc83">Appendix A  Internationalization and Localization</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc84">Appendix B  Release Notes</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc85">Appendix C  Acknowledgements</A>
-</LI><LI CLASS="li-toc"><A HREF="#htoc86">Appendix D  Copyright Information</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc84">Appendix A  Internationalization and Localization</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc85">Appendix B  Release Notes</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc86">Appendix C  Acknowledgements</A>
+</LI><LI CLASS="li-toc"><A HREF="#htoc87">Appendix D  Copyright Information</A>
</LI></UL><!--TOC chapter Introduction-->
<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc1">Chapter 1</A>  Introduction</H1><!--SEC END --><P>
<A NAME="intro"></A></P><P><TT>ejabberd</TT> is a free and open source instant messaging server written in <A HREF="http://www.erlang.org/">Erlang</A>.</P><P><TT>ejabberd</TT> is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.</P><P><TT>ejabberd</TT> is designed to be a rock-solid and feature rich XMPP server.</P><P><TT>ejabberd</TT> is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.</P><!--TOC section Key Features-->
Cross-platform: <TT>ejabberd</TT> runs under Microsoft Windows and Unix derived systems such as Linux, FreeBSD and NetBSD.</LI><LI CLASS="li-itemize">Distributed: You can run <TT>ejabberd</TT> on a cluster of machines and all of them will serve the same Jabber domain(s). When you need more capacity you can simply add a new cheap node to your cluster. Accordingly, you do not need to buy an expensive high-end machine to support tens of thousands concurrent users.</LI><LI CLASS="li-itemize">Fault-tolerant: You can deploy an <TT>ejabberd</TT> cluster so that all the information required for a properly working service will be replicated permanently on all nodes. This means that if one of the nodes crashes, the others will continue working without disruption. In addition, nodes also can be added or replaced ‘on the fly’.</LI><LI CLASS="li-itemize">Administrator Friendly: <TT>ejabberd</TT> is built on top of the Open Source Erlang. As a result you do not need to install an external database, an external web server, amongst others because everything is already included, and ready to run out of the box. Other administrator benefits include:
<UL CLASS="itemize"><LI CLASS="li-itemize">
Comprehensive documentation.
-</LI><LI CLASS="li-itemize">Straightforward installers for Linux, Mac OS X, and Windows. </LI><LI CLASS="li-itemize">Web interface for administration tasks.
+</LI><LI CLASS="li-itemize">Straightforward installers for Linux, Mac OS X, and Windows. </LI><LI CLASS="li-itemize">Web Administration.
</LI><LI CLASS="li-itemize">Shared Roster Groups.
</LI><LI CLASS="li-itemize">Command line administration tool. </LI><LI CLASS="li-itemize">Can integrate with existing authentication mechanisms.
</LI><LI CLASS="li-itemize">Capability to send announce messages.
</LI></UL></LI><LI CLASS="li-itemize">Internationalized: <TT>ejabberd</TT> leads in internationalization. Hence it is very well suited in a globalized world. Related features are:
<UL CLASS="itemize"><LI CLASS="li-itemize">
-Translated
in 17 languages. </LI><LI CLASS="li-itemize">Support for <A HREF="http://www.ietf.org/rfc/rfc3490.txt">IDNA</A>.
+Translated
to 22 languages. </LI><LI CLASS="li-itemize">Support for <A HREF="http://www.ietf.org/rfc/rfc3490.txt">IDNA</A>.
</LI></UL></LI><LI CLASS="li-itemize">Open Standards: <TT>ejabberd</TT> is the first Open Source Jabber server claiming to fully comply to the XMPP standard.
<UL CLASS="itemize"><LI CLASS="li-itemize">
Fully XMPP compliant.
<UL CLASS="itemize"><LI CLASS="li-itemize">
SASL and STARTTLS for c2s and s2s connections.
</LI><LI CLASS="li-itemize">STARTTLS and Dialback s2s connections.
-</LI><LI CLASS="li-itemize">Web interface accessible via HTTPS secure access.
+</LI><LI CLASS="li-itemize">Web Admin accessible via HTTPS secure access.
</LI></UL>
</LI><LI CLASS="li-itemize">Databases
<UL CLASS="itemize"><LI CLASS="li-itemize">
-Native MySQL support.
+Internal database for fast deployment (Mnesia).
+</LI><LI CLASS="li-itemize">Native MySQL support.
</LI><LI CLASS="li-itemize">Native PostgreSQL support.
-</LI><LI CLASS="li-itemize">Mnesia.
</LI><LI CLASS="li-itemize">ODBC data storage support.
</LI><LI CLASS="li-itemize">Microsoft SQL Server support. </LI></UL>
</LI><LI CLASS="li-itemize">Authentication
<UL CLASS="itemize"><LI CLASS="li-itemize">
-PAM, LDAP and ODBC. </LI><LI CLASS="li-itemize">External Authentication script.
-</LI><LI CLASS="li-itemize">Internal Authentication.
+Internal Authentication.
+</LI><LI CLASS="li-itemize">PAM, LDAP and ODBC. </LI><LI CLASS="li-itemize">External Authentication script.
</LI></UL>
</LI><LI CLASS="li-itemize">Others
<UL CLASS="itemize"><LI CLASS="li-itemize">
-Compressing XML streams with Stream Compression (<A HREF="http://www.xmpp.org/extensions/xep-0138.html">XEP-0138</A>).
-</LI><LI CLASS="li-itemize">Interface with networks such as AIM, ICQ and MSN.
+Support for virtual hosting.
+</LI><LI CLASS="li-itemize">Compressing XML streams with Stream Compression (<A HREF="http://www.xmpp.org/extensions/xep-0138.html">XEP-0138</A>).
</LI><LI CLASS="li-itemize">Statistics via Statistics Gathering (<A HREF="http://www.xmpp.org/extensions/xep-0039.html">XEP-0039</A>).
</LI><LI CLASS="li-itemize">IPv6 support both for c2s and s2s connections.
-</LI><LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0045.html">Multi-User Chat</A> module with logging. </LI><LI CLASS="li-itemize">Users Directory based on users vCards.
-</LI><LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0060.html">Publish-Subscribe</A> component.
-</LI><LI CLASS="li-itemize">Support for virtual hosting.
-</LI><LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0025.html">HTTP Polling</A> service.
+</LI><LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0045.html">Multi-User Chat</A> module with support for clustering and HTML logging. </LI><LI CLASS="li-itemize">Users Directory based on users vCards.
+</LI><LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0060.html">Publish-Subscribe</A> component with support for <A HREF="http://www.xmpp.org/extensions/xep-00163.html">Personal Eventing via Pubsub</A>.
+</LI><LI CLASS="li-itemize">Support for web clients: <A HREF="http://www.xmpp.org/extensions/xep-0025.html">HTTP Polling</A> and <A HREF="http://www.xmpp.org/extensions/xep-0206.html">HTTP Binding (BOSH)</A> services.
</LI><LI CLASS="li-itemize">IRC transport.
+</LI><LI CLASS="li-itemize">Component support: interface with networks such as AIM, ICQ and MSN installing special tranports.
</LI></UL>
-</LI></UL><!--TOC chapter Installing ejabberd-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc4">Chapter 2</A>  Installing ejabberd</H1><!--SEC END --><!--TOC section Installing ejabberd with Graphical Installer-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc5">2.1</A>  Installing ejabberd with Graphical Installer</H2><!--SEC END --><P>The easiest approach to install an ejabberd Instant Messaging server
-is to use the graphical installer. The installer is available in
-ejabberd Process-one
-<A HREF="http://www.process-one.net/en/ejabberd/downloads/">downloads page</A>.</P><P>The installer will deploy and configure a full featured ejabberd
-server and does not require any extra dependencies.</P><P>The installer must be set executable and started. Example:
-</P><PRE CLASS="verbatim"> wget http://www.process-one.net/downloads/ejabberd/1.1.4/ejabberd-1.1.4_2-linux-x86-installer.bin
- chmod +x ejabberd-1.1.4_2-linux-x86-installer.bin
- ./ejabberd-1.1.4_2-linux-x86-installer.bin
-</PRE><!--TOC section Installing ejabberd with Operating System specific packages-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6">2.2</A>  Installing ejabberd with Operating System specific packages</H2><!--SEC END --><P>Some Operating Systems provide a specific ejabberd package adapted to
-your system architecture and libraries, which also checks dependencies
+</LI></UL><!--TOC chapter Installing <TT>ejabberd</TT>-->
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc4">Chapter 2</A>  Installing <TT>ejabberd</TT></H1><!--SEC END --><!--TOC section Installing <TT>ejabberd</TT> with Binary Installer-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc5">2.1</A>  Installing <TT>ejabberd</TT> with Binary Installer</H2><!--SEC END --><P>Probably the easiest way to install an <TT>ejabberd</TT> instant messaging server
+is using the binary installer published by Process-one.
+The binary installers of released <TT>ejabberd</TT> versions
+are available in the Process-one <TT>ejabberd</TT> downloads page:
+<A HREF="http://www.process-one.net/en/ejabberd/downloads"><TT>http://www.process-one.net/en/ejabberd/downloads</TT></A></P><P>The installer will deploy and configure a full featured <TT>ejabberd</TT>
+server and does not require any extra dependencies.</P><P>In *nix systems, remember to set executable the binary installer before starting it. For example:
+</P><PRE CLASS="verbatim"> chmod +x ejabberd-2.0.0_1-linux-x86-installer.bin
+ ./ejabberd-2.0.0_1-linux-x86-installer.bin
+</PRE><P>The installer generates desktop shortcuts to start and stop ejabberd.</P><P>The Windows installer also adds ejabberd as a system service,
+and a shortcut to a debug console for experienced administrators.
+You can start ejabberd using the shortcut or the Windows service.
+If you want ejabberd to be started automatically at boot time,
+go to service settings and set ejabberd to be automatic started.</P><P>On a Linux system, if you want ejabberd to start as daemon at boot time,
+copy <TT>ejabberd.init</TT> from the bin directory to something like <TT>/etc/init.d/ejabberd</TT>
+(depending on your distribution) and call <TT>/etc/inid.d/ejabberd start</TT> to start it.</P><P>The <TT>ejabberdctl</TT> administration script is included in the <TT>bin</TT> directory.
+Please refer to the section <A HREF="#ejabberdctl">4.1</A> for details about <TT>ejabberdctl</TT>,
+and configurable options to fine tune the Erlang runtime system.</P><!--TOC section Installing <TT>ejabberd</TT> with Operating System specific packages-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6">2.2</A>  Installing <TT>ejabberd</TT> with Operating System specific packages</H2><!--SEC END --><P>Some Operating Systems provide a specific <TT>ejabberd</TT> package adapted to
+the system architecture and libraries.
+It usually also checks dependencies
and performs basic configuration tasks like creating the initial
administrator account. Some examples are Debian and Gentoo. Consult the
-resources provided by your Operating System for more information.</P><!--TOC section Installing ejabberd with CEAN-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc7">2.3</A>  Installing ejabberd with CEAN</H2><!--SEC END --><P><A HREF="http://cean.process-one.net/">CEAN</A>
+resources provided by your Operating System for more information.</P><P>Usually those packages create a script like <TT>/etc/init.d/ejabberd</TT>
+to start and stop <TT>ejabberd</TT> as a service at boot time.</P><!--TOC section Installing <TT>ejabberd</TT> with CEAN-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc7">2.3</A>  Installing <TT>ejabberd</TT> with CEAN</H2><!--SEC END --><P><A HREF="http://cean.process-one.net/">CEAN</A>
(Comprehensive Erlang Archive Network) is a repository that hosts binary
-packages from many Erlang programs, including ejabberd and all its dependencies.
+packages from many Erlang programs, including <TT>ejabberd</TT> and all its dependencies.
The binaries are available for many different system architectures, so this is an
-alternative to the binary installer and Operating System’s ejabberd packages.</P><!--TOC section Installing ejabberd from Source Code-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8">2.4</A>  Installing ejabberd from Source Code</H2><!--SEC END --><P>
+alternative to the binary installer and Operating System’s <TT>ejabberd</TT> packages.</P><P>You will have to create your own <TT>ejabberd</TT> start
+script depending of how you handle your CEAN installation.
+The default <TT>ejabberdctl</TT> script is located
+into <TT>ejabberd</TT>’s priv directory and can be used as an example.</P><!--TOC section Installing <TT>ejabberd</TT> from Source Code-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8">2.4</A>  Installing <TT>ejabberd</TT> from Source Code</H2><!--SEC END --><P>
<A NAME="installation"></A>
-</P><!--TOC subsection Requirements-->
+</P><P>The canonical form for distribution of <TT>ejabberd</TT> stable releases is the source code package.
+Compiling <TT>ejabberd</TT> from source code is quite easy in *nix systems,
+as long as your system have all the dependencies.</P><!--TOC subsection Requirements-->
<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc9">2.4.1</A>  Requirements</H3><!--SEC END --><P>
<A NAME="installreq"></A>
</P><P>To compile <TT>ejabberd</TT> on a ‘Unix-like’ operating system, you need:
</P><UL CLASS="itemize"><LI CLASS="li-itemize">
GNU Make
</LI><LI CLASS="li-itemize">GCC
-</LI><LI CLASS="li-itemize">libexpat 1.95 or higher
-</LI><LI CLASS="li-itemize">Erlang/OTP R9C-2 or higher
-</LI><LI CLASS="li-itemize">OpenSSL 0.9.6 or higher (optional)
-</LI><LI CLASS="li-itemize">Zlib 1.2.3 or higher (optional)
-</LI><LI CLASS="li-itemize">GNU Iconv 1.8 or higher (optional, not needed on systems with GNU libc)
-</LI></UL><!--TOC subsection Download Source Sode-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc10">2.4.2</A>  Download Source
Sode</H3><!--SEC END --><P>
+</LI><LI CLASS="li-itemize">Libexpat 1.95 or higher
+</LI><LI CLASS="li-itemize">Erlang/OTP R10B-9 up to R11B-5. Erlang R12 releases are not yet officially supported, and are not recommended for production servers.
+</LI><LI CLASS="li-itemize">OpenSSL 0.9.6 or higher, for STARTTLS, SASL and SSL encryption. Optional, highly recommended.
+</LI><LI CLASS="li-itemize">Zlib 1.2.3 or higher, for Stream Compression support (XEP-0138). Optional.
+</LI><LI CLASS="li-itemize">GNU Iconv 1.8 or higher, for the IRC Transport (mod_irc). Optional. Not needed on systems with GNU Libc.
+</LI></UL><!--TOC subsection Download Source Code-->
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc10">2.4.2</A>  Download Source
Code</H3><!--SEC END --><P>
<A NAME="download"></A>
-</P><P>Released versions of <TT>ejabberd</TT> can be obtained from<BR>
+</P><P>Released versions of <TT>ejabberd</TT> are available in the Process-one <TT>ejabberd</TT> downloads page:
<A HREF="http://www.process-one.net/en/ejabberd/downloads"><TT>http://www.process-one.net/en/ejabberd/downloads</TT></A></P><P>
-The latest development version can be retrieved from the Subversion repository using this command:
+Alternatively, the latest development version can be retrieved from the Subversion repository using this command:
</P><PRE CLASS="verbatim"> svn co http://svn.process-one.net/ejabberd/trunk ejabberd
</PRE><!--TOC subsection Compile-->
<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc11">2.4.3</A>  Compile</H3><!--SEC END --><P>
</P><P>To compile <TT>ejabberd</TT> execute the commands:
</P><PRE CLASS="verbatim"> ./configure
make
-</PRE><P>The compilation process may report several warnings related to unusued variables.
-This is common, and is not a problem.</P><P>The build configuration script provides several parameters.
+</PRE><P>The build configuration script provides several parameters.
To get the full list run the command:
</P><PRE CLASS="verbatim"> ./configure --help
</PRE><P>Some options that you may be interested in modifying:
</DD></DL><!--TOC subsection Install-->
<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc12">2.4.4</A>  Install</H3><!--SEC END --><P>
<A NAME="install"></A>
-</P><P>To install ejabberd in the destination directories, run the command:
+</P><P>To install <TT>ejabberd</TT> in the destination directories, run the command:
</P><PRE CLASS="verbatim"> make install
</PRE><P>Note that you may need to have administrative privileges in the system.</P><P>The files and directories created are, by default:
</P><DL CLASS="description"><DT CLASS="dt-description">
<B><TT>/etc/ejabberd/</TT></B></DT><DD CLASS="dd-description"> Configuration files:
<DL CLASS="description"><DT CLASS="dt-description">
<B><TT>ejabberd.cfg</TT></B></DT><DD CLASS="dd-description"> ejabberd configuration file
- </DD><DT CLASS="dt-description"><B><TT>ejabberd.inetrc</TT></B></DT><DD CLASS="dd-description"> Network DNS configuration
</DD><DT CLASS="dt-description"><B><TT>ejabberdctl.cfg</TT></B></DT><DD CLASS="dd-description"> Configuration file of the administration script
+ </DD><DT CLASS="dt-description"><B><TT>inetrc</TT></B></DT><DD CLASS="dd-description"> Network DNS configuration
</DD></DL>
</DD><DT CLASS="dt-description"><B><TT>/sbin/ejabberdctl</TT></B></DT><DD CLASS="dd-description"> Administration script
</DD><DT CLASS="dt-description"><B><TT>/var/lib/ejabberd/</TT></B></DT><DD CLASS="dd-description">
</DD><DT CLASS="dt-description"><B><TT>msgs</TT></B></DT><DD CLASS="dd-description"> Translated strings (*.msgs)
</DD></DL>
</DD></DL>
- </DD><DT CLASS="dt-description"><B><TT>/var/log/ejabberd/</TT></B></DT><DD CLASS="dd-description"> Log files (see section <A HREF="#logfiles">7.2</A>:
+ </DD><DT CLASS="dt-description"><B><TT>/var/log/ejabberd/</TT></B></DT><DD CLASS="dd-description"> Log files (see section <A HREF="#logfiles">7.2</A>):
<DL CLASS="description"><DT CLASS="dt-description">
<B><TT>ejabberd.log</TT></B></DT><DD CLASS="dd-description"> Messages reported by ejabberd code
</DD><DT CLASS="dt-description"><B><TT>sasl.log</TT></B></DT><DD CLASS="dd-description"> Messages reported by Erlang/OTP
</DD></DL><!--TOC subsection Start-->
<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc13">2.4.5</A>  Start</H3><!--SEC END --><P>
<A NAME="start"></A>
-</P><P>You can use the <TT>ejabberdctl</TT> command line administration script to start and stop ejabberd.
-This script is located into tools directory of sources archive. If you installed ejabberd from sources,
-<TT>ejabberdctl</TT> is located into destination sbin directory (default /usr/local/sbin). If you installed
-ejabberd with the installer, <TT>ejabberdctl</TT> is located into ejabberd’s bin directory.</P><P>Usage example:
+</P><P>You can use the <TT>ejabberdctl</TT> command line administration script to start and stop <TT>ejabberd</TT>.</P><P>Usage example:
</P><PRE CLASS="verbatim">$ ejabberdctl start
$ ejabberdctl status
$ ejabberdctl stop
</PRE><P>Please refer to the section <A HREF="#ejabberdctl">4.1</A> for details about <TT>ejabberdctl</TT>,
-and configurable options to fine tune the Erlang runtime system.</P><P>Note: if you installed ejabberd with your distribution packaging system, <TT>ejabberdctl</TT> should be called
-by an /etc/init.d/ejabberd script to allow you to start and stop ejabberd as a service at boot time.</P><P>If you installed ejabberd using CEAN package, you will have to create your own ejabberd start
-script depending of how you handle your CEAN installation. The default <TT>ejabberdctl</TT> script is located
-into ejabberd’s priv directory and can be used as an example.</P><!--TOC subsection Specific Notes for BSD-->
+and configurable options to fine tune the Erlang runtime system.</P><!--TOC subsection Specific Notes for BSD-->
<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc14">2.4.6</A>  Specific Notes for BSD</H3><!--SEC END --><P>
<A NAME="bsd"></A>
-</P><P>The command to compile ejabberd in BSD systems is:
+</P><P>The command to compile <TT>ejabberd</TT> in BSD systems is:
</P><PRE CLASS="verbatim"> gmake
</PRE><!--TOC subsection Specific Notes for Microsoft Windows-->
<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc15">2.4.7</A>  Specific Notes for Microsoft Windows</H3><!--SEC END --><P>
</LI><LI CLASS="li-itemize"><A HREF="http://www.zlib.net/">Zlib 1.2.3 or higher</A>
</LI></UL><!--TOC subsubsection Compilation-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR -->Compilation</H4><!--SEC END --><P>
-<A NAME="windowscom"></A></P><P>We assume that we will try to put as much library as possible into <CODE>C:\sdk\</CODE> to make it easier to track what is install for
ejabberd.</P><OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
+<A NAME="windowscom"></A></P><P>We assume that we will try to put as much library as possible into <CODE>C:\sdk\</CODE> to make it easier to track what is install for
<TT>ejabberd</TT>.</P><OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
Install Erlang emulator (for example, into <CODE>C:\sdk\erl5.5.5</CODE>).
</LI><LI CLASS="li-enumerate">Install Expat library into <CODE>C:\sdk\Expat-2.0.0</CODE>
directory.<P>Copy file <CODE>C:\sdk\Expat-2.0.0\Libs\libexpat.dll</CODE>
</PRE></LI></OL><!--TOC section Create a Jabber Account for Administration-->
<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc16">2.5</A>  Create a Jabber Account for Administration</H2><!--SEC END --><P>
<A NAME="initialadmin"></A></P><P>You need a Jabber account and grant him administrative privileges
-to enter the ejabberd web interface:
+to enter the <TT>ejabberd</TT> Web Admin:
</P><OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
Register a Jabber account on your <TT>ejabberd</TT> server, for example <TT>admin1@example.org</TT>.
There are two ways to register a Jabber account:
<PRE CLASS="verbatim">% ejabberdctl register admin1 example.org FgT5bk3
</PRE></LI><LI CLASS="li-enumerate">Using a Jabber client and In-Band Registration (see section <A HREF="#modregister">3.3.15</A>).
</LI></OL>
-</LI><LI CLASS="li-enumerate">Edit the ejabberd configuration file to give administration rights to the Jabber account you created:
+</LI><LI CLASS="li-enumerate">Edit the <TT>ejabberd</TT> configuration file to give administration rights to the Jabber account you created:
<PRE CLASS="verbatim"> {acl, admins, {user, "admin1", "example.org"}}.
{access, configure, [{allow, admins}]}.
</PRE>You can grant administrative privileges to many Jabber accounts,
and also to accounts in other Jabber servers.
</LI><LI CLASS="li-enumerate">Restart <TT>ejabberd</TT> to load the new configuration.
-</LI><LI CLASS="li-enumerate">Open the web interface (<CODE>http://server:port/admin/</CODE>) in your
+</LI><LI CLASS="li-enumerate">Open the Web Admin (<CODE>http://server:port/admin/</CODE>) in your
favourite browser. Make sure to enter the <EM>full</EM> JID as username (in this
example: <TT>admin1@example.org</TT>. The reason that you also need to enter the
suffix, is because <TT>ejabberd</TT>’s virtual hosting support.
-</LI></OL><!--TOC chapter Configuring ejabberd-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc17">Chapter 3</A>  Configuring ejabberd</H1><!--SEC END --><!--TOC section Basic Configuration-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc18">3.1</A>  Basic Configuration</H2><!--SEC END --><P>
+</LI></OL><!--TOC section Upgrading <TT>ejabberd</TT>-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc17">2.6</A>  Upgrading <TT>ejabberd</TT></H2><!--SEC END --><P>To upgrade an ejabberd installation to a new version,
+simply uninstall the old version, and then install the new one.
+Of course, it is important that the configuration file
+and Mnesia database spool directory are not removed.</P><P><TT>ejabberd</TT> automatically updates the Mnesia table definitions at startup when needed.
+If you also use an external database for storage of some modules,
+check if the release notes of the new ejabberd version
+indicates you need to also update those tables.</P><!--TOC chapter Configuring <TT>ejabberd</TT>-->
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc18">Chapter 3</A>  Configuring <TT>ejabberd</TT></H1><!--SEC END --><!--TOC section Basic Configuration-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc19">3.1</A>  Basic Configuration</H2><!--SEC END --><P>
<A NAME="basicconfig"></A>
</P><P>The configuration file will be loaded the first time you start <TT>ejabberd</TT>. The
-content from this file will be parsed and stored in the internal ejabberd database. Subsequently the
+content from this file will be parsed and stored in the internal <TT>ejabberd</TT> database. Subsequently the
configuration will be loaded from the database and any commands in the
-configuration file are appended to the entries in the database. </P><P>Note that ejabberd never edits the configuration file.
-So, the configuration changes done using the web interface
+configuration file are appended to the entries in the database. </P><P>Note that <TT>ejabberd</TT> never edits the configuration file.
+So, the configuration changes done using the Web Admin
are stored in the database, but are not reflected in the configuration file.
-If you want those changes to be use after ejabberd restart, you can either
+If you want those changes to be use after <TT>ejabberd</TT> restart, you can either
edit the configuration file, or remove all its content.</P><P>The configuration file contains a sequence of Erlang terms. Lines beginning with a
<TT>‘%’</TT> sign are ignored. Each term is a tuple of which the first element is
the name of an option, and any further elements are that option’s values. If the
</P><PRE CLASS="verbatim"> override_global.
override_local.
override_acls.
-</PRE><P>With these lines the old global options (shared between all ejabberd nodes in a
-cluster), local options (which are specific for this particular ejabberd node)
+</PRE><P>With these lines the old global options (shared between all <TT>ejabberd</TT> nodes in a
+cluster), local options (which are specific for this particular <TT>ejabberd</TT> node)
and ACLs will be removed before new ones are added.</P><!--TOC subsection Host Names-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
19">3.1.1</A>  Host Names</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
20">3.1.1</A>  Host Names</H3><!--SEC END --><P>
<A NAME="hostnames"></A>
</P><P>The option <TT>hosts</TT> defines a list containing one or more domains that
<TT>ejabberd</TT> will serve.</P><P>Examples:
</PRE></LI><LI CLASS="li-itemize">Serving two domains:
<PRE CLASS="verbatim"> {hosts, ["example.net", "example.com"]}.
</PRE></LI></UL><!--TOC subsection Virtual Hosting-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
0">3.1.2</A>  Virtual Hosting</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
1">3.1.2</A>  Virtual Hosting</H3><!--SEC END --><P>
<A NAME="virtualhost"></A>
</P><P>Options can be defined separately for every virtual host using the
<TT>host_config</TT> option. It has the following
{mod_echo, [{host, "mirror.two.example.org"}]}
]}]}.
</PRE></LI></UL><!--TOC subsection Listening Ports-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
1">3.1.3</A>  Listening Ports</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
2">3.1.3</A>  Listening Ports</H3><!--SEC END --><P>
<A NAME="listened"></A>
</P><P>The option <TT>listen</TT> defines for which addresses and ports <TT>ejabberd</TT>
will listen and what services will be run on them. Each element of the list is a
<TT>ip</TT>, <TT>shaper</TT></TD></TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP><TT>ejabberd_http</TT></TD><TD VALIGN=top ALIGN=left NOWRAP>Description</TD><TD VALIGN=top ALIGN=left>Handles incoming HTTP
connections.</TD></TR>
-<TR><TD VALIGN=top ALIGN=left NOWRAP> </TD><TD VALIGN=top ALIGN=left NOWRAP>Options</TD><TD VALIGN=top ALIGN=left><TT>certfile</TT>, <TT>http_poll</TT>,
+<TR><TD VALIGN=top ALIGN=left NOWRAP> </TD><TD VALIGN=top ALIGN=left NOWRAP>Options</TD><TD VALIGN=top ALIGN=left><TT>certfile</TT>, <TT>http_bind</TT>, <TT>http_poll</TT>,
<TT>inet6</TT>, <TT>ip</TT>, <TT>request_handlers</TT>, <TT>tls</TT>, <TT>web_admin</TT></TD></TR>
</TABLE>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE><P>This is a detailed description of each option allowed by the listening modules:
</DD><DT CLASS="dt-description"><B><TT>{hosts, [Hostnames], [HostOptions]}</TT></B></DT><DD CLASS="dd-description"> This option
defines one or more hostnames of connected services and enables you to
specify additional options including <TT>{password, Secret}</TT>.
-</DD><DT CLASS="dt-description"><B><TT>http_poll</TT></B></DT><DD CLASS="dd-description">
+</DD><DT CLASS="dt-description"><B><TT>http_bind</TT></B></DT><DD CLASS="dd-description">
+This option enables HTTP Binding (<A HREF="http://www.xmpp.org/extensions/xep-0124.html">XEP-0124</A> and <A HREF="http://www.xmpp.org/extensions/xep-0206.html">XEP-0206</A>) support. HTTP Bind
+enables access via HTTP requests to <TT>ejabberd</TT> from behind firewalls which
+do not allow outgoing sockets on port 5222.<P>Remember that you must also install and enable the module mod_http_bind.</P><P>If HTTP Bind is enabled, it will be available at
+<CODE>http://server:port/http-bind/</CODE>. Be aware that support for HTTP Bind
+is also needed in the Jabber client. Remark also that HTTP Bind can be
+interesting to host a web-based Jabber client such as
+<A HREF="http://jwchat.sourceforge.net/">JWChat</A> (there is a tutorial to
+<A HREF="http://www.ejabberd.im/jwchat">install JWChat</A> with
+instructions for <TT>ejabberd</TT>).
+</P></DD><DT CLASS="dt-description"><B><TT>http_poll</TT></B></DT><DD CLASS="dd-description">
This option enables HTTP Polling (<A HREF="http://www.xmpp.org/extensions/xep-0025.html">XEP-0025</A>) support. HTTP Polling
enables access via HTTP requests to <TT>ejabberd</TT> from behind firewalls which
do not allow outgoing sockets on port 5222.<P>If HTTP Polling is enabled, it will be available at
the port will be encrypted using SSL immediately after connecting. You
should also set the <TT>certfile</TT> option.
</DD><DT CLASS="dt-description"><B><TT>web_admin</TT></B></DT><DD CLASS="dd-description"> This option
-enables the web interface for <TT>ejabberd</TT> administration which is available
+enables the Web Admin for <TT>ejabberd</TT> administration which is available
at <CODE>http://server:port/admin/</CODE>. Login and password are the username and
password of one of the registered users who are granted access by the
‘configure’ access rule.
</LI><LI CLASS="li-itemize">Port 5223 listens for c2s connections with the old SSL.
</LI><LI CLASS="li-itemize">Port 5269 listens for s2s connections with STARTTLS.
</LI><LI CLASS="li-itemize">Port 5280 listens for HTTP requests, and serves the HTTP Poll service.
-</LI><LI CLASS="li-itemize">Port 5281 listens for HTTP requests, and serves the web interface using HTTPS as explained in
-section <A HREF="#webinterface">4.2</A>.
+</LI><LI CLASS="li-itemize">Port 5281 listens for HTTP requests, and serves the Web Admin using HTTPS as explained in
+section <A HREF="#webadmin">4.2</A>.
</LI></UL><PRE CLASS="verbatim">{hosts, ["example.com", "example.org", "example.net"]}.
{listen,
[
for the user called ‘<TT>bad</TT>’.
</LI><LI CLASS="li-itemize">s2s connections are listened for on port 5269 with STARTTLS for secured
traffic enabled.
-</LI><LI CLASS="li-itemize">Port 5280 is serving the web interface and the HTTP Polling service. Note
+</LI><LI CLASS="li-itemize">Port 5280 is serving the Web Admin and the HTTP Polling service. Note
that it is also possible to serve them on different ports. The second
-example in section <A HREF="#webinterface">4.2</A> shows how exactly this can be done.
+example in section <A HREF="#webinterface">??</A> shows how exactly this can be done.
</LI><LI CLASS="li-itemize">All users except for the administrators have a traffic of limit
1,000 Bytes/second
</LI><LI CLASS="li-itemize">The
</xdb_file>
</xdb>
</PRE><!--TOC subsection Authentication-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
2">3.1.4</A>  Authentication</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
3">3.1.4</A>  Authentication</H3><!--SEC END --><P>
<A NAME="auth"></A>
</P><P>The option <TT>auth_method</TT> defines the authentication method that is used
for user authentication:
</LI><LI CLASS="li-itemize">You may want to allow login access only for certain users. <TT>pam_listfile.so</TT>
module provides such functionality.
</LI></UL><!--TOC subsection Access Rules-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
3">3.1.5</A>  Access Rules</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
4">3.1.5</A>  Access Rules</H3><!--SEC END --><P>
<A NAME="accessrules"></A>
</P><!--TOC subsubsection ACL Definition-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR -->ACL Definition</H4><!--SEC END --><P>
To limit the number of sessions per user to 10 for all users:
<PRE CLASS="verbatim"> {access, max_user_sessions, [{10, all}]}.
</PRE></LI></UL><!--TOC subsection Shapers-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
4">3.1.6</A>  Shapers</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
5">3.1.6</A>  Shapers</H3><!--SEC END --><P>
<A NAME="shapers"></A>
</P><P>Shapers enable you to limit connection traffic. The syntax of
shapers is like this:
50,000 bytes/second:
<PRE CLASS="verbatim"> {shaper, fast, {maxrate, 50000}}.
</PRE></LI></UL><!--TOC subsection Default Language-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
5">3.1.7</A>  Default Language</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
6">3.1.7</A>  Default Language</H3><!--SEC END --><P>
<A NAME="language"></A>
</P><P>The option <TT>language</TT> defines the default language of server strings that
can be seen by Jabber clients. If a Jabber client do not support
</PRE></LI><LI CLASS="li-itemize">To set Spanish as default language:
<PRE CLASS="verbatim"> {language, "es"}.
</PRE></LI></UL><!--TOC section Database and LDAP Configuration-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc2
6">3.2</A>  Database and LDAP Configuration</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc2
7">3.2</A>  Database and LDAP Configuration</H2><!--SEC END --><P>
<A NAME="database"></A>
</P><P><TT>ejabberd</TT> uses its internal Mnesia database by default. However, it is
</LI><LI CLASS="li-itemize">Normally any LDAP compatible server should work; inform us about your
success with a not-listed server so that we can list it here.
</LI></UL><!--TOC subsection MySQL-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
7">3.2.1</A>  MySQL</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
8">3.2.1</A>  MySQL</H3><!--SEC END --><P>
<A NAME="mysql"></A>
</P><P>Although this section will describe <TT>ejabberd</TT>’s configuration when you want to
use the native MySQL driver, it does not describe MySQL’s installation and
database creation. Check the MySQL documentation and the tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> for information regarding these topics.
Note that the tutorial contains information about <TT>ejabberd</TT>’s configuration
which is duplicate to this section.</P><P>Moreover, the file mysql.sql in the directory src/odbc might be interesting for
-you. This file contains the ejabberd schema for MySQL. At the end of the file
+you. This file contains the <TT>ejabberd</TT> schema for MySQL. At the end of the file
you can find information to update your database schema.</P><!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR -->Driver Compilation</H4><!--SEC END --><P>
<A NAME="compilemysql"></A>
if the binary packages of <TT>ejabberd</TT> you are using include support for MySQL.</P><OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
First, install the <A HREF="http://support.process-one.net/doc/display/CONTRIBS/Yxa">Erlang
MySQL library</A>. Make sure the compiled files are in your Erlang path; you can
-put them for example in the same directory as your ejabberd .beam files.
+put them for example in the same directory as your <TT>ejabberd</TT> .beam files.
</LI><LI CLASS="li-enumerate">Then, configure and install <TT>ejabberd</TT> with ODBC support enabled (this is
also needed for native MySQL support!). This can be done, by using next
commands:
sure that your database is running well (see previous sections), and replace the
suffix-less or ldap module variant with the odbc module variant. Keep in mind
that you cannot have several variants of the same module loaded!</P><!--TOC subsection Microsoft SQL Server-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
8">3.2.2</A>  Microsoft SQL Server</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2
9">3.2.2</A>  Microsoft SQL Server</H3><!--SEC END --><P>
<A NAME="mssql"></A>
</P><P>Although this section will describe <TT>ejabberd</TT>’s configuration when you want to
use Microsoft SQL Server, it does not describe Microsoft SQL Server’s
tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> for information regarding these topics.
Note that the tutorial contains information about <TT>ejabberd</TT>’s configuration
which is duplicate to this section.</P><P>Moreover, the file mssql.sql in the directory src/odbc might be interesting for
-you. This file contains the ejabberd schema for Microsoft SQL Server. At the end
+you. This file contains the <TT>ejabberd</TT> schema for Microsoft SQL Server. At the end
of the file you can find information to update your database schema.</P><!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR -->Driver Compilation</H4><!--SEC END --><P>
<A NAME="compilemssql"></A>
sections), and replace the suffix-less or ldap module variant with the odbc
module variant. Keep in mind that you cannot have several variants of the same
module loaded!</P><!--TOC subsection PostgreSQL-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
29">3.2.3</A>  PostgreSQL</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
30">3.2.3</A>  PostgreSQL</H3><!--SEC END --><P>
<A NAME="pgsql"></A>
</P><P>Although this section will describe <TT>ejabberd</TT>’s configuration when you want to
use the native PostgreSQL driver, it does not describe PostgreSQL’s installation
and database creation. Check the PostgreSQL documentation and the tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> for information regarding these topics.
Note that the tutorial contains information about <TT>ejabberd</TT>’s configuration
which is duplicate to this section.</P><P>Also the file pg.sql in the directory src/odbc might be interesting for you.
-This file contains the ejabberd schema for PostgreSQL. At the end of the file
+This file contains the <TT>ejabberd</TT> schema for PostgreSQL. At the end of the file
you can find information to update your database schema.</P><!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR -->Driver Compilation</H4><!--SEC END --><P>
<A NAME="compilepgsql"></A>
First, install the Erlang PgSQL library from
<A HREF="http://jungerl.sourceforge.net/">Jungerl</A>. Make sure the compiled
files are in your Erlang path; you can put them for example in the same
-directory as your ejabberd .beam files.
+directory as your <TT>ejabberd</TT> .beam files.
</LI><LI CLASS="li-enumerate">Then, configure, compile and install <TT>ejabberd</TT> with ODBC support enabled
(this is also needed for native PostgreSQL support!). This can be done, by
using next commands:
make sure that your database is running well (see previous sections), and
replace the suffix-less or ldap module variant with the odbc module variant.
Keep in mind that you cannot have several variants of the same module loaded!</P><!--TOC subsection ODBC Compatible-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
0">3.2.4</A>  ODBC Compatible</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
1">3.2.4</A>  ODBC Compatible</H3><!--SEC END --><P>
<A NAME="odbc"></A>
</P><P>Although this section will describe <TT>ejabberd</TT>’s configuration when you want to
use the ODBC driver, it does not describe the installation and database creation
ODBC.</P><OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
First, install the <A HREF="http://support.process-one.net/doc/display/CONTRIBS/Yxa">Erlang
MySQL library</A>. Make sure the compiled files are in your Erlang path; you can
-put them for example in the same directory as your ejabberd .beam files.
+put them for example in the same directory as your <TT>ejabberd</TT> .beam files.
</LI><LI CLASS="li-enumerate">Then, configure, compile and install <TT>ejabberd</TT> with ODBC support
enabled. This can be done, by using next commands:
<PRE CLASS="verbatim">./configure --enable-odbc && make install
sections), and replace the suffix-less or ldap module variant with the odbc
module variant. Keep in mind that you cannot have several variants of the same
module loaded!</P><!--TOC subsection LDAP-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
1">3.2.5</A>  LDAP</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
2">3.2.5</A>  LDAP</H3><!--SEC END --><P>
<A NAME="ldap"></A>
</P><P><TT>ejabberd</TT> has built-in LDAP support. You can authenticate users against LDAP
server and use LDAP directory as vCard storage. Shared rosters are not supported
</DD><DT CLASS="dt-description"><B><TT>ldap_port</TT></B></DT><DD CLASS="dd-description"> Port to connect to your LDAP server.
The initial default value is 389, so it is used when nothing is set into the
configuration file.
-If you configure a value, it is stored in ejabberd’s database.
+If you configure a value, it is stored in <TT>ejabberd</TT>’s database.
Then, if you remove that value from the configuration file,
the value previously stored in the database will be used instead of the default 389.
</DD><DT CLASS="dt-description"><B><TT>ldap_rootdn</TT></B></DT><DD CLASS="dd-description"> Bind DN. The default value
...
}.
</PRE><!--TOC section Modules Configuration-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc3
2">3.3</A>  Modules Configuration</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc3
3">3.3</A>  Modules Configuration</H2><!--SEC END --><P>
<A NAME="modules"></A>
</P><P>The option <TT>modules</TT> defines the list of modules that will be loaded after
<TT>ejabberd</TT>’s startup. Each entry in the list is a tuple in which the first
{mod_version, []}
]}.
</PRE></LI></UL><!--TOC subsection Overview-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
3">3.3.1</A>  Overview</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
4">3.3.1</A>  Overview</H3><!--SEC END --><P>
<A NAME="modoverview"></A>
</P><P>The following table lists all modules included in <TT>ejabberd</TT>.</P><BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
<TABLE BORDER=1 CELLSPACING=0 CELLPADDING=1><TR><TD ALIGN=left NOWRAP>Module</TD><TD ALIGN=left NOWRAP>Feature</TD><TD ALIGN=left NOWRAP>Dependencies</TD><TD ALIGN=left NOWRAP>Needed for XMPP?</TD></TR>
<TT>ejabberd</TT> website. Please remember that these contributions might not work or
that they can contain severe bugs and security leaks. Therefore, use them at
your own risk!</P><!--TOC subsection Common Options-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
4">3.3.2</A>  Common Options</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
5">3.3.2</A>  Common Options</H3><!--SEC END --><P>
<A NAME="modcommonoptions"></A></P><P>The following options are used by many modules. Therefore, they are described in
this separate section.</P><!--TOC subsubsection <TT>iqdisc</TT>-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR --><TT>iqdisc</TT></H4><!--SEC END --><P>
</PRE><!--TOC subsubsection <TT>host</TT>-->
<H4 CLASS="subsubsection"><!--SEC ANCHOR --><TT>host</TT></H4><!--SEC END --><P>
<A NAME="modhostoption"></A>
-</P><P>This option defines the Jabber ID of a service provided by an ejabberd module.
+</P><P>This option defines the Jabber ID of a service provided by an <TT>ejabberd</TT> module.
The keyword "@HOST@" is replaced at start time with the real virtual host string.</P><P>This example configures
the echo module to provide its echoing service
in the Jabber ID <TT>mirror.example.org</TT>:
...
]}.
</PRE><!--TOC subsection <TT>mod_announce</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
5">3.3.3</A>  <TT>mod_announce</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
6">3.3.3</A>  <TT>mod_announce</TT></H3><!--SEC END --><P>
<A NAME="modannounce"></A>
</P><P>This module enables configured users to broadcast announcements and to set
the message of the day (MOTD). Configured users can do these actions with their
]}.
</PRE></LI></UL><P>Note that <TT>mod_announce</TT> can be resource intensive on large
deployments as it can broadcast lot of messages. This module should be
-disabled for instances of ejabberd with hundreds of thousands users.</P><!--TOC subsection <TT>mod_disco</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
6">3.3.4</A>  <TT>mod_disco</TT></H3><!--SEC END --><P>
+disabled for instances of <TT>ejabberd</TT> with hundreds of thousands users.</P><!--TOC subsection <TT>mod_disco</TT>-->
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
7">3.3.4</A>  <TT>mod_disco</TT></H3><!--SEC END --><P>
<A NAME="moddisco"></A>
</P><P>This module adds support for Service Discovery (<A HREF="http://www.xmpp.org/extensions/xep-0030.html">XEP-0030</A>). With
this module enabled, services on your server can be discovered by
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_echo</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
7">3.3.5</A>  <TT>mod_echo</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
8">3.3.5</A>  <TT>mod_echo</TT></H3><!--SEC END --><P>
<A NAME="modecho"></A>
</P><P>This module simply echoes any Jabber
packet back to the sender. This mirror can be of interest for
...
]}.
</PRE><!--TOC subsection <TT>mod_irc</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
8">3.3.6</A>  <TT>mod_irc</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc3
9">3.3.6</A>  <TT>mod_irc</TT></H3><!--SEC END --><P>
<A NAME="modirc"></A>
</P><P>This module is an IRC transport that can be used to join channels on IRC
servers.</P><P>End user information:
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_last</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
39">3.3.7</A>  <TT>mod_last</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
40">3.3.7</A>  <TT>mod_last</TT></H3><!--SEC END --><P>
<A NAME="modlast"></A>
</P><P>This module adds support for Last Activity (<A HREF="http://www.xmpp.org/extensions/xep-0012.html">XEP-0012</A>). It can be used to
discover when a disconnected user last accessed the server, to know when a
<B><TT>iqdisc</TT></B></DT><DD CLASS="dd-description"> This specifies
the processing discipline for Last activity (<TT>jabber:iq:last</TT>) IQ queries (see section <A HREF="#modiqdiscoption">3.3.2</A>).
</DD></DL><!--TOC subsection <TT>mod_muc</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
0">3.3.8</A>  <TT>mod_muc</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
1">3.3.8</A>  <TT>mod_muc</TT></H3><!--SEC END --><P>
<A NAME="modmuc"></A>
</P><P>With this module enabled, your server will support Multi-User Chat
(<A HREF="http://www.xmpp.org/extensions/xep-0045.html">XEP-0045</A>). End users will be able to join text conferences.</P><P>Some of the features of Multi-User Chat:
service for users abuses, as fastly changing a user presence will
result in possible large presence packet broadcast. If a user tries
to change its presence more often than the specified interval, the
-presence is cached by ejabberd and only the last presence is
+presence is cached by <TT>ejabberd</TT> and only the last presence is
broadcasted to all users in the room after expiration of the
interval delay. Intermediate presence packets are silently
discarded. A good value for this option is 4 seconds.</DD><DT CLASS="dt-description"><B><TT>default_room_opts</TT></B></DT><DD CLASS="dd-description"> This
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_muc_log</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
1">3.3.9</A>  <TT>mod_muc_log</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
2">3.3.9</A>  <TT>mod_muc_log</TT></H3><!--SEC END --><P>
<A NAME="modmuclog"></A>
</P><P>This module enables optional logging of Multi-User Chat (MUC) conversations to
HTML. Once you enable this module, users can join a chatroom using a MUC capable
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_offline</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
2">3.3.10</A>  <TT>mod_offline</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
3">3.3.10</A>  <TT>mod_offline</TT></H3><!--SEC END --><P>
<A NAME="modoffline"></A>
</P><P>This module implements offline message storage. This means that all messages
sent to an offline user will be stored on the server until that user comes
value can be either <TT>infinity</TT> or a strictly positive
integer. The default value is <TT>infinity</TT>.
</DD></DL><!--TOC subsection <TT>mod_privacy</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
3">3.3.11</A>  <TT>mod_privacy</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
4">3.3.11</A>  <TT>mod_privacy</TT></H3><!--SEC END --><P>
<A NAME="modprivacy"></A>
</P><P>This module implements Blocking Communication (also known as Privacy Rules)
as defined in section 10 from XMPP IM. If end users have support for it in
<B><TT>iqdisc</TT></B></DT><DD CLASS="dd-description"> This specifies
the processing discipline for Blocking Communication (<TT>jabber:iq:privacy</TT>) IQ queries (see section <A HREF="#modiqdiscoption">3.3.2</A>).
</DD></DL><!--TOC subsection <TT>mod_private</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
4">3.3.12</A>  <TT>mod_private</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
5">3.3.12</A>  <TT>mod_private</TT></H3><!--SEC END --><P>
<A NAME="modprivate"></A>
</P><P>This module adds support for Private XML Storage (<A HREF="http://www.xmpp.org/extensions/xep-0049.html">XEP-0049</A>):
</P><BLOCKQUOTE CLASS="quote">
<B><TT>iqdisc</TT></B></DT><DD CLASS="dd-description"> This specifies
the processing discipline for Private XML Storage (<TT>jabber:iq:private</TT>) IQ queries (see section <A HREF="#modiqdiscoption">3.3.2</A>).
</DD></DL><!--TOC subsection <TT>mod_proxy65</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
5">3.3.13</A>  <TT>mod_proxy65</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
6">3.3.13</A>  <TT>mod_proxy65</TT></H3><!--SEC END --><P>
<A NAME="modproxy"></A>
</P><P>This module implements SOCKS5 Bytestreams (<A HREF="http://www.xmpp.org/extensions/xep-0065.html">XEP-0065</A>).
It allows <TT>ejabberd</TT> to act as a file transfer proxy between two
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_pubsub</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
6">3.3.14</A>  <TT>mod_pubsub</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
7">3.3.14</A>  <TT>mod_pubsub</TT></H3><!--SEC END --><P>
<A NAME="modpubsub"></A>
</P><P>This module offers a Publish-Subscribe Service (<A HREF="http://www.xmpp.org/extensions/xep-0060.html">XEP-0060</A>).
The functionality in <TT>mod_pubsub</TT> can be extended using plugins.
...
]}.
</PRE><!--TOC subsection <TT>mod_register</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
7">3.3.15</A>  <TT>mod_register</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
8">3.3.15</A>  <TT>mod_register</TT></H3><!--SEC END --><P>
<A NAME="modregister"></A>
</P><P>This module adds support for In-Band Registration (<A HREF="http://www.xmpp.org/extensions/xep-0077.html">XEP-0077</A>). This protocol
enables end users to use a Jabber client to:
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_roster</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
8">3.3.16</A>  <TT>mod_roster</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc4
9">3.3.16</A>  <TT>mod_roster</TT></H3><!--SEC END --><P>
<A NAME="modroster"></A>
</P><P>This module implements roster management as defined in <A HREF="http://www.xmpp.org/specs/rfc3921.html#roster">RFC 3921: XMPP IM</A>.</P><P>Options:
</P><DL CLASS="description"><DT CLASS="dt-description">
<B><TT>iqdisc</TT></B></DT><DD CLASS="dd-description"> This specifies
the processing discipline for Roster Management (<TT>jabber:iq:roster</TT>) IQ queries (see section <A HREF="#modiqdiscoption">3.3.2</A>).
</DD></DL><!--TOC subsection <TT>mod_service_log</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
49">3.3.17</A>  <TT>mod_service_log</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc
50">3.3.17</A>  <TT>mod_service_log</TT></H3><!--SEC END --><P>
<A NAME="modservicelog"></A>
</P><P>This module adds support for logging end user packets via a Jabber message
auditing service such as
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_shared_roster</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
0">3.3.18</A>  <TT>mod_shared_roster</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
1">3.3.18</A>  <TT>mod_shared_roster</TT></H3><!--SEC END --><P>
<A NAME="modsharedroster"></A>
</P><P>This module enables you to create shared roster groups. This means that you can
create groups of people that can see members from (other) groups in their
users from the shared roster groups.
A shared roster group can have members from any Jabber server,
but the presence will only be available from and to members
-of the same virtual host where the group is created.</P><P>Shared roster groups can be edited <EM>only</EM> via the web interface. Each group
+of the same virtual host where the group is created.</P><P>Shared roster groups can be edited <EM>only</EM> via the Web Admin. Each group
has a unique identification and the following parameters:
</P><DL CLASS="description"><DT CLASS="dt-description">
<B>Name</B></DT><DD CLASS="dd-description"> The name of the group, which will be displayed in the roster.
</DD><DT CLASS="dt-description"><B>Description</B></DT><DD CLASS="dd-description"> The description of the group. This parameter does not affect
anything.
</DD><DT CLASS="dt-description"><B>Members</B></DT><DD CLASS="dd-description"> A list of full JIDs of group members, entered one per line in
-the web interface.
+the Web Admin.
To put as members all the registered users in the virtual hosts,
you can use the special directive: @all@.
Note that this directive is designed for a small server with just a few hundred users.
</TABLE>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
</LI></UL><!--TOC subsection <TT>mod_stats</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
1">3.3.19</A>  <TT>mod_stats</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
2">3.3.19</A>  <TT>mod_stats</TT></H3><!--SEC END --><P>
<A NAME="modstats"></A>
</P><P>This module adds support for Statistics Gathering (<A HREF="http://www.xmpp.org/extensions/xep-0039.html">XEP-0039</A>). This protocol
allows you to retrieve next statistics from your <TT>ejabberd</TT> deployment:
</query>
</iq>
</PRE></LI></UL><!--TOC subsection <TT>mod_time</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
2">3.3.20</A>  <TT>mod_time</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
3">3.3.20</A>  <TT>mod_time</TT></H3><!--SEC END --><P>
<A NAME="modtime"></A>
</P><P>This module features support for Entity Time (<A HREF="http://www.xmpp.org/extensions/xep-0090.html">XEP-0090</A>). By using this XEP,
you are able to discover the time at another entity’s location.</P><P>Options:
<B><TT>iqdisc</TT></B></DT><DD CLASS="dd-description"> This specifies
the processing discipline for Entity Time (<TT>jabber:iq:time</TT>) IQ queries (see section <A HREF="#modiqdiscoption">3.3.2</A>).
</DD></DL><!--TOC subsection <TT>mod_vcard</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
3">3.3.21</A>  <TT>mod_vcard</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
4">3.3.21</A>  <TT>mod_vcard</TT></H3><!--SEC END --><P>
<A NAME="modvcard"></A>
</P><P>This module allows end users to store and retrieve their vCard, and to retrieve
other users vCards, as defined in vcard-temp (<A HREF="http://www.xmpp.org/extensions/xep-0054.html">XEP-0054</A>). The module also
...
]}.
</PRE></LI></UL><!--TOC subsection <TT>mod_vcard_ldap</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
4">3.3.22</A>  <TT>mod_vcard_ldap</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
5">3.3.22</A>  <TT>mod_vcard_ldap</TT></H3><!--SEC END --><P>
<A NAME="modvcardldap"></A>
</P><P><TT>ejabberd</TT> can map LDAP attributes to vCard fields. This behaviour is
implemented in the <TT>mod_vcard_ldap</TT> module. This module does not depend on the
{"Nickname", "NICK"}
]},
</PRE></LI></UL><!--TOC subsection <TT>mod_version</TT>-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
5">3.3.23</A>  <TT>mod_version</TT></H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
6">3.3.23</A>  <TT>mod_version</TT></H3><!--SEC END --><P>
<A NAME="modversion"></A>
</P><P>This module implements Software Version (<A HREF="http://www.xmpp.org/extensions/xep-0092.html">XEP-0092</A>). Consequently, it
answers <TT>ejabberd</TT>’s version when queried.</P><P>Options:
The default value is <TT>true</TT>.
</DD><DT CLASS="dt-description"><B><TT>iqdisc</TT></B></DT><DD CLASS="dd-description"> This specifies
the processing discipline for Software Version (<TT>jabber:iq:version</TT>) IQ queries (see section <A HREF="#modiqdiscoption">3.3.2</A>).
-</DD></DL><!--TOC chapter Managing an ejabberd server-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc56">Chapter 4</A>  Managing an ejabberd server</H1><!--SEC END --><!--TOC section <TT>ejabberdctl</TT>-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc5
7">4.1</A>  <TT>ejabberdctl</TT></H2><!--SEC END --><P>
+</DD></DL><!--TOC chapter Managing an <TT>ejabberd</TT> server-->
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc57">Chapter 4</A>  Managing an <TT>ejabberd</TT> server</H1><!--SEC END --><!--TOC section <TT>ejabberdctl</TT>-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc5
8">4.1</A>  <TT>ejabberdctl</TT></H2><!--SEC END --><P>
<A NAME="ejabberdctl"></A></P><!--TOC subsection Commands-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
8">4.1.1</A>  Commands</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc5
9">4.1.1</A>  Commands</H3><!--SEC END --><P>
<A NAME="commands"></A></P><P>The <TT>ejabberdctl</TT> command line script allows to start, stop and perform
-many other administrative tasks in a local or remote
ejabberd server.</P><P>When <TT>ejabberdctl</TT> is executed without any parameter,
-it displays the available options. If there isn’t an ejabberd server running,
+many other administrative tasks in a local or remote
<TT>ejabberd</TT> server.</P><P>When <TT>ejabberdctl</TT> is executed without any parameter,
+it displays the available options. If there isn’t an <TT>ejabberd</TT> server running,
the available parameters are:
</P><DL CLASS="description"><DT CLASS="dt-description">
-<B><TT>start</TT></B></DT><DD CLASS="dd-description"> Start ejabberd in background mode. This is the default method.
-</DD><DT CLASS="dt-description"><B><TT>debug</TT></B></DT><DD CLASS="dd-description"> Attach an Erlang shell to an already existing ejabberd server. This allows to execute commands interactively in the ejabberd server.
-</DD><DT CLASS="dt-description"><B><TT>live</TT></B></DT><DD CLASS="dd-description"> Start ejabberd in live mode: the shell keeps attached to the started server, showing log messages and allowing to execute interactive commands.
-</DD></DL><P>If there is an ejabberd server running in the system,
+<B><TT>start</TT></B></DT><DD CLASS="dd-description"> Start <TT>ejabberd</TT> in background mode. This is the default method.
+</DD><DT CLASS="dt-description"><B><TT>debug</TT></B></DT><DD CLASS="dd-description"> Attach an Erlang shell to an already existing <TT>ejabberd</TT> server. This allows to execute commands interactively in the <TT>ejabberd</TT> server.
+</DD><DT CLASS="dt-description"><B><TT>live</TT></B></DT><DD CLASS="dd-description"> Start <TT>ejabberd</TT> in live mode: the shell keeps attached to the started server, showing log messages and allowing to execute interactive commands.
+</DD></DL><P>If there is an <TT>ejabberd</TT> server running in the system,
<TT>ejabberdctl</TT> shows all the available commands in that server.
The more interesting ones are:
</P><DL CLASS="description"><DT CLASS="dt-description">
-<B><TT>status</TT></B></DT><DD CLASS="dd-description"> Check the status of the ejabberd server.
-</DD><DT CLASS="dt-description"><B><TT>stop</TT></B></DT><DD CLASS="dd-description"> Stop the ejabberd server which is running in the machine.
+<B><TT>status</TT></B></DT><DD CLASS="dd-description"> Check the status of the <TT>ejabberd</TT> server.
+</DD><DT CLASS="dt-description"><B><TT>stop</TT></B></DT><DD CLASS="dd-description"> Stop the <TT>ejabberd</TT> server which is running in the machine.
</DD><DT CLASS="dt-description"><B><TT>reopen-log</TT></B></DT><DD CLASS="dd-description"> If you use a tool to rotate logs, you have to configure it
so that this command is executed after each rotation.
</DD><DT CLASS="dt-description"><B><TT>backup, restore, install-fallback, dump, load</TT></B></DT><DD CLASS="dd-description"> You can use these
is very high.
</DD></DL><P>The <TT>ejabberdctl</TT> script also allows the argument <TT>--node NODENAME</TT>.
This allows to administer a remote node.</P><P>The <TT>ejabberdctl</TT> administration script can be configured in the file ejabberdctl.cfg.
-This file provides detailed information about each configurable option.</P><!--TOC subsection Erlang configuration-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc59">4.1.2</A>  Erlang configuration</H3><!--SEC END --><P>
-<A NAME="erlangconfiguration"></A></P><P>The basic parameters used by <TT>ejabberdctl</TT> when starting the Erlang node:
+This file provides detailed information about each configurable option.</P><!--TOC subsection Erlang runtime system-->
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc60">4.1.2</A>  Erlang runtime system</H3><!--SEC END --><P>
+<A NAME="erlangconfiguration"></A></P><P><TT>ejabberd</TT> is an Erlang/OTP application that runs inside an Erlang runtime system.
+This system is configured using environment variables and command line parameters.
+The <TT>ejabberdctl</TT> administration script uses many of those possibilities.
+You can configure some of them with the file <TT>ejabberdctl.cfg</TT>,
+which includes detailed description about them.
+This section describes for reference purposes
+all the environment variables and command line parameters.</P><P>The environment variables:
+</P><DL CLASS="description"><DT CLASS="dt-description">
+<B><TT>EJABBERD_CONFIG_PATH</TT></B></DT><DD CLASS="dd-description">
+ Path to the ejabberd configuration file.
+</DD><DT CLASS="dt-description"><B><TT>EJABBERD_MSGS_PATH</TT></B></DT><DD CLASS="dd-description">
+ Path to the directory with translated strings.
+</DD><DT CLASS="dt-description"><B><TT>EJABBERD_LOG_PATH</TT></B></DT><DD CLASS="dd-description">
+ Path to the ejabberd log file.
+</DD><DT CLASS="dt-description"><B><TT>EJABBERD_SO_PATH</TT></B></DT><DD CLASS="dd-description">
+ Path to the directory with binary system libraries.
+</DD><DT CLASS="dt-description"><B><TT>HOME</TT></B></DT><DD CLASS="dd-description">
+ Path to the directory that is considered <TT>ejabberd</TT>’s home.
+ This path is used to read the file <TT>.erlang.cookie</TT>.
+</DD><DT CLASS="dt-description"><B><TT>ERL_CRASH_DUMP</TT></B></DT><DD CLASS="dd-description">
+ Path to the file where crash reports will be dumped.
+</DD><DT CLASS="dt-description"><B><TT>ERL_INETRC</TT></B></DT><DD CLASS="dd-description">
+ Indicates which IP name resolution to use. It is required if using <TT>-sname</TT>.
+</DD><DT CLASS="dt-description"><B><TT>ERL_MAX_PORTS</TT></B></DT><DD CLASS="dd-description">
+ Maximum number of simultaneously open Erlang ports.
+</DD><DT CLASS="dt-description"><B><TT>ERL_MAX_ETS_TABLES</TT></B></DT><DD CLASS="dd-description">
+ Maximum number of ETS and Mnesia tables.
+</DD></DL><P>The command line parameters:
</P><DL CLASS="description"><DT CLASS="dt-description">
<B><TT>-sname ejabberd</TT></B></DT><DD CLASS="dd-description">
The Erlang node will be identified using only the first part
this node. This is the preferable option in most cases.
</DD><DT CLASS="dt-description"><B><TT>-name ejabberd</TT></B></DT><DD CLASS="dd-description">
The Erlang node will be fully identified.
-This is only useful if you plan to setup an ejabberd cluster with nodes in different networks.
-</DD><DT CLASS="dt-description"><B><TT>-kernel inetrc "/etc/ejabberd/ejabberd.inetrc"</TT></B></DT><DD CLASS="dd-description">
+This is only useful if you plan to setup an <TT>ejabberd</TT> cluster with nodes in different networks.
+</DD><DT CLASS="dt-description"><B><TT>-kernel inetrc "/etc/ejabberd/inetrc"</TT></B></DT><DD CLASS="dd-description">
Indicates which IP name resolution to use. It is required if using <TT>-sname</TT>.
</DD><DT CLASS="dt-description"><B><TT>-detached</TT></B></DT><DD CLASS="dd-description">
Starts the Erlang system detached from the system console.
</DD><DT CLASS="dt-description"><B><TT>-pa /var/lib/ejabberd/ebin</TT></B></DT><DD CLASS="dd-description">
Specify the directory where Erlang binary files (*.beam) are located.
</DD><DT CLASS="dt-description"><B><TT>-s ejabberd</TT></B></DT><DD CLASS="dd-description">
- Tell Erlang runtime system to start the ejabberd application.
+ Tell Erlang runtime system to start the <TT>ejabberd</TT> application.
</DD><DT CLASS="dt-description"><B><TT>-mnesia dir "/var/lib/ejabberd/db/nodename"</TT></B></DT><DD CLASS="dd-description">
Specify the Mnesia database directory.
</DD><DT CLASS="dt-description"><B><TT>-sasl sasl_error_logger {file, "/var/log/ejabberd/sasl.log"}</TT></B></DT><DD CLASS="dd-description">
Specify the directory for the sasl.log file.
+</DD><DT CLASS="dt-description"><B><TT>+K [true|false]</TT></B></DT><DD CLASS="dd-description">
+ Kernel polling.
+</DD><DT CLASS="dt-description"><B><TT>-smp [auto|enable|disable]</TT></B></DT><DD CLASS="dd-description">
+ SMP support.
+</DD><DT CLASS="dt-description"><B><TT>+P 250000</TT></B></DT><DD CLASS="dd-description">
+ Maximum number of Erlang processes.
+</DD><DT CLASS="dt-description"><B><TT>-remsh ejabberd@localhost</TT></B></DT><DD CLASS="dd-description">
+ Open an Erlang shell in a remote Erlang node.
</DD></DL><P>
Note that some characters need to be escaped when used in shell scripts, for instance <CODE>"</CODE> and <CODE>{}</CODE>.
-You can find other options in the Erlang manual page (<TT>erl -man erl</TT>).</P><P>In addition, there are several configurable parameters
-in the file <TT>/etc/ejabberd/ejabberdctl.cfg</TT>
-to fine tune the Erlang runtime system.</P><!--TOC section Web Interface-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc60">4.2</A>  Web Interface</H2><!--SEC END --><P>
-<A NAME="webinterface"></A>
-</P><P>To perform online configuration of <TT>ejabberd</TT> you need to enable the
-<TT>ejabberd_http</TT> listener with the option <TT>web_admin</TT> (see
-section <A HREF="#listened">3.1.3</A>). Then you can open
+You can find other options in the Erlang manual page (<TT>erl -man erl</TT>).</P><!--TOC section Web Admin-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc61">4.2</A>  Web Admin</H2><!--SEC END --><P>
+<A NAME="webadmin"></A>
+</P><P>The <TT>ejabberd</TT> Web Admin allows to administer most of <TT>ejabberd</TT> using a web browser.</P><P>This feature is enabled by default:
+a <TT>ejabberd_http</TT> listener with the option <TT>web_admin</TT> (see
+section <A HREF="#listened">3.1.3</A>) is included in the listening ports. Then you can open
<CODE>http://server:port/admin/</CODE> in your favourite web browser. You
will be asked to enter the username (the <EM>full</EM> Jabber ID) and password
of an <TT>ejabberd</TT> user with administrator rights. After authentication
<IMG SRC="webadmmain.png" ALT="webadmmain.png">
-<DIV CLASS="caption"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD VALIGN=top ALIGN=left>Figure 4.1: Top page from the web interface</TD></TR>
+<DIV CLASS="caption"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD VALIGN=top ALIGN=left>Figure 4.1: Top page from the Web Admin</TD></TR>
</TABLE></DIV>
<A NAME="fig:webadmmain"></A>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE><P>
manage the database, enable/disable ports listened for, view server
statistics,…</P><P>Examples:
</P><UL CLASS="itemize"><LI CLASS="li-itemize">
-You can serve the web interface on the same port as the
+You can serve the Web Admin on the same port as the
HTTP Polling interface. In this example
you should point your web browser to <CODE>http://example.org:5280/admin/</CODE> to
administer all virtual hosts or to
<CODE>http://example.org:5280/admin/server/example.com/</CODE> to administer only
-the virtual host <TT>example.com</TT>. Before you get access to the web interface
+the virtual host <TT>example.com</TT>. Before you get access to the Web Admin
you need to enter as username, the JID and password from a registered user
that is allowed to configure <TT>ejabberd</TT>. In this example you can enter as
username ‘<TT>admin@example.net</TT>’ to administer all virtual hosts (first
...
]
}.
-</PRE></LI><LI CLASS="li-itemize">For security reasons, you can serve the web interface on a secured
+</PRE></LI><LI CLASS="li-itemize">For security reasons, you can serve the Web Admin on a secured
connection, on a port differing from the HTTP Polling interface, and bind it
-to the internal LAN IP. The web interface will be accessible by pointing your
+to the internal LAN IP. The Web Admin will be accessible by pointing your
web browser to <CODE>https://192.168.1.1:5280/admin/</CODE>:
<PRE CLASS="verbatim"> ...
{hosts, ["example.org"]}.
]
}.
</PRE></LI></UL><!--TOC section Ad-hoc Commands-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
1">4.3</A>  Ad-hoc Commands</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
2">4.3</A>  Ad-hoc Commands</H2><!--SEC END --><P>
<A NAME="adhoccommands"></A></P><P>If you enable <TT>mod_configure</TT> and <TT>mod_adhoc</TT>,
-you can perform several administrative tasks in ejabberd
+you can perform several administrative tasks in <TT>ejabberd</TT>
with a Jabber client.
The client must support Ad-Hoc Commands (<A HREF="http://www.xmpp.org/extensions/xep-0050.html">XEP-0050</A>),
and you must login in the Jabber server with
an account with proper privileges.</P><!--TOC section Change Computer Hostname-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
2">4.4</A>  Change Computer Hostname</H2><!--SEC END --><P>
-<A NAME="changeerlangnodename"></A></P><P>ejabberd uses the distributed Mnesia database.
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
3">4.4</A>  Change Computer Hostname</H2><!--SEC END --><P>
+<A NAME="changeerlangnodename"></A></P><P><TT>ejabberd</TT> uses the distributed Mnesia database.
Being distributed, Mnesia enforces consistency of its file,
so it stores the name of the Erlang node in it.
The name of an Erlang node includes the hostname of the computer.
So, the name of the Erlang node changes
-if you change the name of the machine in which ejabberd runs,
-or when you move ejabberd to a different machine.</P><P>So, if you want to change the computer hostname where ejabberd is installed,
+if you change the name of the machine in which <TT>ejabberd</TT> runs,
+or when you move <TT>ejabberd</TT> to a different machine.</P><P>So, if you want to change the computer hostname where <TT>ejabberd</TT> is installed,
you must follow these instructions:
</P><OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
- In the old server, backup the Mnesia database using the Web Interface or <TT>ejabberdctl</TT>.
+ In the old server, backup the Mnesia database using the Web Admin or <TT>ejabberdctl</TT>.
For example:
<PRE CLASS="verbatim">ejabberdctl backup /tmp/ejabberd-oldhost.backup
-</PRE> </LI><LI CLASS="li-enumerate">In the new server, restore the backup file using the Web Interface or <TT>ejabberdctl</TT>.
+</PRE> </LI><LI CLASS="li-enumerate">In the new server, restore the backup file using the Web Admin or <TT>ejabberdctl</TT>.
For example:
<PRE CLASS="verbatim">ejabberdctl restore /tmp/ejabberd-oldhost.backup
-</PRE></LI></OL><!--TOC chapter Securing ejabberd-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc63">Chapter 5</A>  Securing ejabberd</H1><!--SEC END --><!--TOC section Firewall Settings-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
4">5.1</A>  Firewall Settings</H2><!--SEC END --><P>
+</PRE></LI></OL><!--TOC chapter Securing <TT>ejabberd</TT>-->
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc64">Chapter 5</A>  Securing <TT>ejabberd</TT></H1><!--SEC END --><!--TOC section Firewall Settings-->
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
5">5.1</A>  Firewall Settings</H2><!--SEC END --><P>
<A NAME="firewall"></A>
</P><P>You need to take the following TCP ports in mind when configuring your firewall:
</P><BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
<TR><TD ALIGN=left NOWRAP>port range</TD><TD ALIGN=left NOWRAP>Used for connections between Erlang nodes. This range is configurable.</TD></TR>
</TABLE>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE><!--TOC section epmd -->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
5">5.2</A>  epmd </H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
6">5.2</A>  epmd </H2><!--SEC END --><P>
<A NAME="epmd"></A></P><P><A HREF="http://www.erlang.org/doc/man/epmd.html">epmd (Erlang Port Mapper Daemon)</A>
is a small name server included in Erlang/OTP
and used by Erlang programs when establishing distributed Erlang communications.
-ejabberd needs <TT>epmd</TT> to use <TT>ejabberdctl</TT> and also when clustering ejabberd nodes.
+<TT>ejabberd</TT> needs <TT>epmd</TT> to use <TT>ejabberdctl</TT> and also when clustering <TT>ejabberd</TT> nodes.
This small program is automatically started by Erlang, and is never stopped.
-If ejabberd is stopped, and there aren’t any other Erlang programs
-running in the system, you can safely stop <TT>epmd</TT> if you want.</P><P>ejabberd runs inside an Erlang node.
-To communicate with ejabberd, the script <TT>ejabberdctl</TT> starts a new Erlang node
-and connects to the Erlang node that holds ejabberd.
+If <TT>ejabberd</TT> is stopped, and there aren’t any other Erlang programs
+running in the system, you can safely stop <TT>epmd</TT> if you want.</P><P><TT>ejabberd</TT> runs inside an Erlang node.
+To communicate with <TT>ejabberd</TT>, the script <TT>ejabberdctl</TT> starts a new Erlang node
+and connects to the Erlang node that holds <TT>ejabberd</TT>.
In order for this communication to work,
<TT>epmd</TT> must be running and listening for name requests in the port 4369.
You should block the port 4369 in the firewall,
-so only the programs in your machine can access it.</P><P>If you build a cluster of several ejabberd instances,
-each ejabberd instance is called an ejabberd node.
-Those ejabberd nodes use a special Erlang communication method to
+so only the programs in your machine can access it.</P><P>If you build a cluster of several <TT>ejabberd</TT> instances,
+each <TT>ejabberd</TT> instance is called an <TT>ejabberd</TT> node.
+Those <TT>ejabberd</TT> nodes use a special Erlang communication method to
build the cluster, and EPMD is again needed listening in the port 4369.
-So, if you plan to build a cluster of ejabberd nodes
+So, if you plan to build a cluster of <TT>ejabberd</TT> nodes
you must open the port 4369 for the machines involved in the cluster.
Remember to block the port so Internet doesn’t have access to it.</P><P>Once an Erlang node solved the node name of another Erlang node using EPMD and port 4369,
the nodes communicate directly.
You can limit the range of ports when starting Erlang with a command-line parameter, for example:
</P><PRE CLASS="verbatim">erl ... -kernel inet_dist_listen_min 4370 inet_dist_listen_max 4375
</PRE><!--TOC section Erlang Cookie-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
6">5.3</A>  Erlang Cookie</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
7">5.3</A>  Erlang Cookie</H2><!--SEC END --><P>
<A NAME="cookie"></A></P><P>The Erlang cookie is a string with numbers and letters.
An Erlang node reads the cookie at startup from the command-line parameter <TT>-setcookie</TT>
or from a cookie file.
The communication between Erlang nodes are not encrypted,
so the cookie could be read sniffing the traffic on the network.
The recommended way to secure the Erlang node is to block the port 4369.</P><!--TOC section Erlang node name-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
7">5.4</A>  Erlang node name</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc6
8">5.4</A>  Erlang node name</H2><!--SEC END --><P>
<A NAME="nodename"></A></P><P>An Erlang node may have a node name.
The name can be short (if indicated with the command-line parameter <TT>-sname</TT>)
or long (if indicated with the parameter <TT>-name</TT>).
because it may be possible to fake the fact that you are on another network
using a modified version of Erlang <TT>epmd</TT>.
The recommended way to secure the Erlang node is to block the port 4369.</P><!--TOC chapter Clustering-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc6
8">Chapter 6</A>  Clustering</H1><!--SEC END --><P>
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc6
9">Chapter 6</A>  Clustering</H1><!--SEC END --><P>
<A NAME="clustering"></A>
</P><!--TOC section How it Works-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc
69">6.1</A>  How it Works</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc
70">6.1</A>  How it Works</H2><!--SEC END --><P>
<A NAME="howitworks"></A>
</P><P>A Jabber domain is served by one or more <TT>ejabberd</TT> nodes. These nodes can
be run on different machines that are connected via a network. They all
</LI><LI CLASS="li-itemize">session manager,
</LI><LI CLASS="li-itemize">s2s manager.
</LI></UL><!--TOC subsection Router-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
0">6.1.1</A>  Router</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
1">6.1.1</A>  Router</H3><!--SEC END --><P>
<A NAME="router"></A>
</P><P>This module is the main router of Jabber packets on each node. It
routes them based on their destination’s domains. It uses a global
routing table. The domain of the packet’s destination is searched in the
routing table, and if it is found, the packet is routed to the
appropriate process. If not, it is sent to the s2s manager.</P><!--TOC subsection Local Router-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
1">6.1.2</A>  Local Router</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
2">6.1.2</A>  Local Router</H3><!--SEC END --><P>
<A NAME="localrouter"></A>
</P><P>This module routes packets which have a destination domain equal to
one of this server’s host names. If the destination JID has a non-empty user
part, it is routed to the session manager, otherwise it is processed depending
on its content.</P><!--TOC subsection Session Manager-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
2">6.1.3</A>  Session Manager</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
3">6.1.3</A>  Session Manager</H3><!--SEC END --><P>
<A NAME="sessionmanager"></A>
</P><P>This module routes packets to local users. It looks up to which user
resource a packet must be sent via a presence table. Then the packet is
either routed to the appropriate c2s process, or stored in offline
storage, or bounced back.</P><!--TOC subsection s2s Manager-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
3">6.1.4</A>  s2s Manager</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
4">6.1.4</A>  s2s Manager</H3><!--SEC END --><P>
<A NAME="s2smanager"></A>
</P><P>This module routes packets to other Jabber servers. First, it
checks if an opened s2s connection from the domain of the packet’s
source to the domain of the packet’s destination exists. If that is the case,
the s2s manager routes the packet to the process
serving this connection, otherwise a new connection is opened.</P><!--TOC section Clustering Setup-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc7
4">6.2</A>  Clustering Setup</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc7
5">6.2</A>  Clustering Setup</H2><!--SEC END --><P>
<A NAME="cluster"></A>
</P><P>Suppose you already configured <TT>ejabberd</TT> on one machine named (<TT>first</TT>),
and you need to setup another one to make an <TT>ejabberd</TT> cluster. Then do
should see a lot of remote tables and a line like the following:</P><PRE CLASS="verbatim">running db nodes = [ejabberd@first, ejabberd@second]
</PRE></LI><LI CLASS="li-enumerate">Now run the following in the same ‘<TT>erl</TT>’ session:<PRE CLASS="verbatim">mnesia:change_table_copy_type(schema, node(), disc_copies).
</PRE><P>This will create local disc storage for the database.</P><P>(alt) Change storage type of the <TT>scheme</TT> table to ‘RAM and disc
-copy’ on the second node via the web interface.</P></LI><LI CLASS="li-enumerate">Now you can add replicas of various tables to this node with
+copy’ on the second node via the Web Admin.</P></LI><LI CLASS="li-enumerate">Now you can add replicas of various tables to this node with
‘<CODE>mnesia:add_table_copy</CODE>’ or
‘<CODE>mnesia:change_table_copy_type</CODE>’ as above (just replace
‘<CODE>schema</CODE>’ with another table name and ‘<CODE>disc_copies</CODE>’
enabled only on one machine in the cluster).
</LI></OL><P>You can repeat these steps for other machines supposed to serve this
domain.</P><!--TOC section Service Load-Balancing-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc75">6.3</A>  Service Load-Balancing</H2><!--SEC END --><!--TOC subsection Components Load-Balancing-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
6">6.3.1</A>  Components Load-Balancing</H3><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc76">6.3</A>  Service Load-Balancing</H2><!--SEC END --><!--TOC subsection Components Load-Balancing-->
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
7">6.3.1</A>  Components Load-Balancing</H3><!--SEC END --><P>
<A NAME="componentlb"></A>
</P><!--TOC subsection Domain Load-Balancing Algorithm-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
7">6.3.2</A>  Domain Load-Balancing Algorithm</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
8">6.3.2</A>  Domain Load-Balancing Algorithm</H3><!--SEC END --><P>
<A NAME="domainlb"></A>
-</P><P><TT>ejabberd</TT> includes an algorithm to load balance the components that are plugged on an
ejabberd cluster. It means that you can plug one or several instances of the same component on each ejabberd cluster and that the traffic will be automatically distributed.</P><P>The default distribution algorithm try to deliver to a local instance of a component. If several local instances are available, one instance is chosen randomly. If no instance is available locally, one instance is chosen randomly among the remote component instances.</P><P>If you need a different behaviour, you can change the load balancing behaviour with the option <TT>domain_balancing</TT>. The syntax of the option is the following:</P><PRE CLASS="verbatim"> {domain_balancing, "component.example.com", <balancing_criterium>}.
+</P><P><TT>ejabberd</TT> includes an algorithm to load balance the components that are plugged on an
<TT>ejabberd</TT> cluster. It means that you can plug one or several instances of the same component on each <TT>ejabberd</TT> cluster and that the traffic will be automatically distributed.</P><P>The default distribution algorithm try to deliver to a local instance of a component. If several local instances are available, one instance is chosen randomly. If no instance is available locally, one instance is chosen randomly among the remote component instances.</P><P>If you need a different behaviour, you can change the load balancing behaviour with the option <TT>domain_balancing</TT>. The syntax of the option is the following:</P><PRE CLASS="verbatim"> {domain_balancing, "component.example.com", <balancing_criterium>}.
</PRE><P>Several balancing criteria are available:
</P><UL CLASS="itemize"><LI CLASS="li-itemize">
<TT>destination</TT>: the full JID of the packet <TT>to</TT> attribute is used.
</LI><LI CLASS="li-itemize"><TT>bare_destination</TT>: the bare JID (without resource) of the packet <TT>to</TT> attribute is used.
</LI><LI CLASS="li-itemize"><TT>bare_source</TT>: the bare JID (without resource) of the packet <TT>from</TT> attribute is used.
</LI></UL><P>If the value corresponding to the criteria is the same, the same component instance in the cluster will be used.</P><!--TOC subsection Load-Balancing Buckets-->
-<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
8">6.3.3</A>  Load-Balancing Buckets</H3><!--SEC END --><P>
+<H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc7
9">6.3.3</A>  Load-Balancing Buckets</H3><!--SEC END --><P>
<A NAME="lbbuckets"></A>
</P><P>When there is a risk of failure for a given component, domain balancing can cause service trouble. If one component is failing the service will not work correctly unless the sessions are rebalanced.</P><P>In this case, it is best to limit the problem to the sessions handled by the failing component. This is what the <TT>domain_balancing_component_number</TT> option does, making the load balancing algorithm not dynamic, but sticky on a fix number of component instances.</P><P>The syntax is the following:
</P><PRE CLASS="verbatim"> {domain_balancing_component_number, "component.example.com", N}
</PRE><!--TOC chapter Debugging-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc
79">Chapter 7</A>  Debugging</H1><!--SEC END --><P>
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc
80">Chapter 7</A>  Debugging</H1><!--SEC END --><P>
<A NAME="debugging"></A>
</P><!--TOC section Watchdog Alerts-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8
0">7.1</A>  Watchdog Alerts</H2><!--SEC END --><P>
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8
1">7.1</A>  Watchdog Alerts</H2><!--SEC END --><P>
<A NAME="watchdog"></A>
-</P><P>ejabberd includes a watchdog mechanism.
-If a process in the ejabberd server consumes too much memory,
+</P><P><TT>ejabberd</TT> includes a watchdog mechanism.
+If a process in the <TT>ejabberd</TT> server consumes too much memory,
a message is sent to the Jabber accounts defined with the option
<TT>watchdog_admins</TT>
- in the ejabberd configuration file.
+ in the <TT>ejabberd</TT> configuration file.
Example configuration:
</P><PRE CLASS="verbatim">{watchdog_admins, ["admin2@localhost", "admin2@example.org"]}.
</PRE><!--TOC section Log Files-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8
1">7.2</A>  Log Files</H2><!--SEC END --><P>
-<A NAME="logfiles"></A></P><P>ejabberd writes messages in two log files:
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8
2">7.2</A>  Log Files</H2><!--SEC END --><P>
+<A NAME="logfiles"></A></P><P><TT>ejabberd</TT> writes messages in two log files:
</P><DL CLASS="description"><DT CLASS="dt-description">
- <B><TT>ejabberd.log</TT></B></DT><DD CLASS="dd-description"> Messages reported by ejabberd code
+ <B><TT>ejabberd.log</TT></B></DT><DD CLASS="dd-description"> Messages reported by <TT>ejabberd</TT> code
</DD><DT CLASS="dt-description"><B><TT>sasl.log</TT></B></DT><DD CLASS="dd-description"> Messages reported by Erlang/OTP using SASL (System Architecture Support Libraries)
</DD></DL><P>The option <TT>loglevel</TT> modifies the verbosity of the file ejabberd.log.
There possible levels are:
For example, the default configuration is:
</P><PRE CLASS="verbatim">{loglevel, 4}.
</PRE><!--TOC section Debug Console-->
-<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8
2">7.3</A>  Debug Console</H2><!--SEC END --><P>
-<A NAME="debugconsole"></A></P><P>The Debug Console is an Erlang shell attached to an already running ejabberd server.
-With this Erlang shell, an experienced administrator can perform complex tasks.</P><P>This shell gives complete control over the ejabberd server,
+<H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc8
3">7.3</A>  Debug Console</H2><!--SEC END --><P>
+<A NAME="debugconsole"></A></P><P>The Debug Console is an Erlang shell attached to an already running <TT>ejabberd</TT> server.
+With this Erlang shell, an experienced administrator can perform complex tasks.</P><P>This shell gives complete control over the <TT>ejabberd</TT> server,
so it is important to use it with extremely care.
There are some simple and safe examples in the article
<A HREF="http://www.ejabberd.im/interconnect-erl-nodes">Interconnecting Erlang Nodes</A></P><P>To exit the shell, close the window or press the keys: control+c control+c.</P><!--TOC chapter Internationalization and Localization-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
3">Appendix A</A>  Internationalization and Localization</H1><!--SEC END --><P>
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
4">Appendix A</A>  Internationalization and Localization</H1><!--SEC END --><P>
<A NAME="i18nl10n"></A>
</P><P>All built-in modules support the <TT>xml:lang</TT> attribute inside IQ queries.
Figure <A HREF="#fig:discorus">A.1</A>, for example, shows the reply to the following query:
<DIV CLASS="caption"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD VALIGN=top ALIGN=left>Figure A.1: Service Discovery when <TT>xml:lang=’ru’</TT></TD></TR>
</TABLE></DIV>
<A NAME="fig:discorus"></A>
-<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE><P>The web interface also supports the <CODE>Accept-Language</CODE> HTTP header (compare
+<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE><P>The Web Admin also supports the <CODE>Accept-Language</CODE> HTTP header (compare
figure <A HREF="#fig:webadmmainru">A.2</A> with figure <A HREF="#fig:webadmmain">4.1</A>)</P><BLOCKQUOTE CLASS="figure"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
<IMG SRC="webadmmainru.png" ALT="webadmmainru.png">
-<DIV CLASS="caption"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD VALIGN=top ALIGN=left>Figure A.2: Top page from the web interface with HTTP header
+<DIV CLASS="caption"><TABLE CELLSPACING=6 CELLPADDING=0><TR><TD VALIGN=top ALIGN=left>Figure A.2: Top page from the Web Admin with HTTP header
‘Accept-Language: ru’</TD></TR>
</TABLE></DIV>
<A NAME="fig:webadmmainru"></A>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE><!--TOC chapter Release Notes-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
4">Appendix B</A>  Release Notes</H1><!--SEC END --><P>
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
5">Appendix B</A>  Release Notes</H1><!--SEC END --><P>
<A NAME="releasenotes"></A>
</P><P>Release notes are available from <A HREF="http://www.process-one.net/en/ejabberd/release_notes/">ejabberd Home Page</A></P><!--TOC chapter Acknowledgements-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
5">Appendix C</A>  Acknowledgements</H1><!--SEC END --><P>
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
6">Appendix C</A>  Acknowledgements</H1><!--SEC END --><P>
<A NAME="acknowledgements"></A>
Thanks to all people who contributed to this guide:
</P><UL CLASS="itemize"><LI CLASS="li-itemize">
</LI><LI CLASS="li-itemize">Sergei Golovan (<A HREF="xmpp:sgolovan@nes.ru"><TT>xmpp:sgolovan@nes.ru</TT></A>)
</LI><LI CLASS="li-itemize">Vsevolod Pelipas (<A HREF="xmpp:vsevoload@jabber.ru"><TT>xmpp:vsevoload@jabber.ru</TT></A>)
</LI></UL><!--TOC chapter Copyright Information-->
-<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
6">Appendix D</A>  Copyright Information</H1><!--SEC END --><P>
+<H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc8
7">Appendix D</A>  Copyright Information</H1><!--SEC END --><P>
<A NAME="copyright"></A></P><P>Ejabberd Installation and Operation Guide.<BR>
-Copyright © 2003 — 200
7 Process-one</P><P>This document is free software; you can redistribute it and/or
+Copyright © 2003 — 200
8 Process-one</P><P>This document is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.</P><P>This document is distributed in the hope that it will be useful,
projects / ejabberd / commitdiff