Differences

This shows you the differences between two versions of the page.

--- editing_config_files [2007/07/02 23:27] – bootstrap.conf is gone dbs
+++ editing_config_files [2010/09/06 13:10] (current) – Delete obsolete page dbs
@@ Line 1: / Line 1: @@
-[[user-comments:editing_config_files|User Comments]]
-=== A Few notes on Jabber Before Continuing ===
-You will see the names Chop Chop, jserver, and 'the opensrf custom
-jabber server' used interchangeably throughout the documentation.  They are
-indeed one and the same - an opensrf custom jabber server.  Chop Chop does
-not currently support real authentication, so if you are using Chop Chop,
-then any username/password set in a config file will suffice.  The only special username is
-'router' which should **only** be used by the router process.
-If you decide to use ejabberd (or some other jabber server) then it will be
-necessary to set up proper usernames and passwords to match the configuration files.
-No matter what Jabber server you do use, keep in mind that the OpenILS project will require a fairly large amount of user sessions to properly operate.  Whereas a normal Jabber server would only need a ''max_user_sessions'' of about 10, Evergreen requires the Jabber ILS user to have a larger number (depending on how busy the system will be drives this number...).  As such, it is suggested that you allow at least FIXME //This setting doesn't seem to exist in the PINES ejabberd.cfg, which would explain why we haven't seen this problem -- we're using ejabberd 1.11//
-=== Configuration file breakdown: ===
-  * [[opensrf_core.xml]] - Bootstrap, router, and ChopChop configuration. As of Evergreen 1.2.x, this file provides a unified bootstrap config layout so that Perl and C (and others) can share a single base system configuration file.
-  * [[openils.xml|opensrf.xml]] - Global application configuration file
-  * [[bootstrap.conf]] - **For Evergreen 1.0.x only**: Perl bootstrap configuration file