The s2s.xml file handles configuration for the server-to-server Jabberd component. The s2s.xml file provides network settings for this component in addition to settings for communicating with the router component:
Below is an overview for the settings in the s2s.xml file.
The pid section specifies the location of the PID file. This section may be commented if a PID file is not needed.
The router section controls communication with the router component. The default ip and port should be fine for most installations, although note that if s2s is running on a separate server, an external IP address would be specified here.
The user and pass sub-sections specify the user name for connecting to the router. These must match against a pair specified in router-users.xml as explained in Section 9. Basic security procedures dictate that the default password should be changed for production systems.
The pemfile section specifies the certificate and private key to be used for communication with the router. See Section 5.2 and Appendix: Generating A Self-Signed SSL Key for more information about setting up SSL on Jabberd. Commenting this section has the effect of disabling SSL communication between s2s and router.
The retry section specifies how s2s should try to reconnect to the router if the connection cannot be established during startup or if the connection is lost during operation. The default settings prevent s2s from indefinitely attempting to reconnect if this connection cannot be made. These default settings will essentially cause s2s to die if the router dies or is killed.
Jabberd logging defaults to the syslog. If you prefer s2s to write its own log file, change the log type to file, and specify a location for the log.
The local section specifies network configuration for s2s in addition to the secret used for dialback keys. The default IP address and port should be fine for most installations (the 0.0.0.0 setting allows s2s to listen on all available IP addresses). The secret setting specifies the passphrase that s2s uses to generate dialback keys for other Jabber servers. The default setting of secret should be changed on production servers.
The check section handles checking of connections with other Jabber servers. By default, these checks are disabled (interval is set to 0). To enable checking, set an interval in seconds, and then set intervals for queue expiry, invalid route expiry and/or keep alives.
|| QUESTION: Under what conditions would connection checking be useful? ||
© 2003 Will Kamishlian and Robert Norris
This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.