Programming Jabber

Starting the satellite server

It’s time to start up the satellite server, from the same directory in this example:

yak:~/jabber-1.4.1$ ./jabberd/jabberd -c jabber_conf.xml &

The satellite server should make a connection to the socket listening on 127.0.0.1:9001.

At this stage, you should have Jabber server services split between a main process and a separate process that runs a Conferencing component.

At the risk of stating the obvious, it is worth pointing out that this example shows that simply starting jabberd does not mean that any process will bind to and start listening on port 5222. It is the c2s component that makes this happen. So starting a second jabberd on the same host did not cause any socket listening problems because this second jabberd doesn’t have a c2s component (because there’s no JSM for clients to want to connect to) and so doesn’t try to bind to port 5222.