Some users will need the ability to administer the XMPP server remotely.
We’ll cover each relevant option in turn. The primary ejabberd configuration file is located at /etc/ejabberd/ejabberd.cfg, for this version. Thankfully, the modifications we need to make are relatively minor and straightforward.
EJABBERD ADD ADMIN ACCOUNT INSTALL
Issue the following command to install ejabberd: yum updateĮjabberd’s configuration files are written in Erlang syntax, which might be difficult to comprehend. Enable EPEL with the following command: rpm -Uvh
EJABBERD ADD ADMIN ACCOUNT SOFTWARE
EPEL, or “Extra Packages for Enterprise Linux,” is a product of the Fedora Project that attempts to provide Enterprise-grade software that’s more current than what is typically available in the CentOS repositories. As a result, in order to install ejabberd, we must install the “ĮPEL” system. The packages required to install ejabberd and it’s dependencies are not available in the standard CentOS repositories. Along with this, you will need to open the /etc/sysconfig/network file and change the HOSTNAME line to reflect your newly set hostname: In this case, the hostname will be set to “example”. Run the following commands the set the hostname of your Linode: echo "example" > /etc/hostname “SRV” DNS Records to support the resolution of domains to the servers which provide DNS records. For instance, to federate with Google’s “GTalk” XMPP network, server administrators need to have server-to-server (s2s) SSL/TLS encryption enabled, while other servers don’t always require this. In the XMPP system there is no single point of failure, however each server administrator can decide how their server is going to participate in the federated network. Without a centralized server, every XMPP server maintains the accounts and serves as the communication gateway for their own users. Users with accounts on one server–if the server administrators allow it–can communicate with users on other servers. resources), the resource adds a useful amount of specificity. the resource is optional although XMPP allows a single JID to be connected to the server from multiple machines (i.e. In following example, “username” is the username, “” is the hostname, and “/office” is the resource. The resource is optional, and is often safely omitted or ignored for most users. It often looks like an email address and contains the username that identifies a specific user on a server, the hostname that identifies the server, and a resource that identifies where a given user is logged in from. The JID or “Jabber ID” is the unique identifier for a user in the XMPP network. Though you can successfully run an XMPP server with only a passing familiarity of the way the XMPP network and system works, understanding the following basic concepts will be helpful: Once you’ve completed these requirements we can begin with the installation process. Setting Up and Securing a Compute Instance guide, and that you are connected to your Linode via SSH as the root user.
This installation process assumes that you have a working installation of CentOS 5.4, that you’ve followed the steps in the It even includes support for hosting multiple domains virtually. Although ejabberd is considered “heavyweight” by some, mostly due to the requirements of the Erlang runtimes, it is incredibly robust and can scale to support heavy loads. XMPP standards, ejabberd is an ideal general-use and multi-purpose XMPP server.
With a web-based interface and broad support for Ejabberd, the “Erlang Jabber Daemon,” is an extensible, flexible and very high performance XMPP server written in the Erlang programming language.
0 kommentar(er)
