[Erp5-report] r10864 - /erp5/trunk/utils/ooodoc_server/README

[nobody at svn.erp5.org]

Author: bartek
Date: Fri Oct 20 16:48:05 2006
New Revision: 10864

URL: http://svn.erp5.org?rev=10864&view=rev
Log:
added more info on starting OOo instances

Modified:
    erp5/trunk/utils/ooodoc_server/README

Modified: erp5/trunk/utils/ooodoc_server/README
URL: http://svn.erp5.org/erp5/trunk/utils/ooodoc_server/README?rev=10864&r1=10863&r2=10864&view=diff
==============================================================================
--- erp5/trunk/utils/ooodoc_server/README (original)
+++ erp5/trunk/utils/ooodoc_server/README Fri Oct 20 16:48:05 2006
@@ -11,7 +11,7 @@
 Patch your SimpleXMLRPCServer.py with this:
 https://sourceforge.net/tracker/?func=detail&atid=305470&aid=893642&group_id=5470
 
-Install OOo 2.0.3 from RPMs.
+Download the source code from svn. Create a writable tmp directory under your ooodoc_server base dir.
 
 If you want to run it remotely on screen-less server, use Xvfb (start it by Xvfb -ac :1, set DISPLAY environment variable to :1, then run start.sh). To run smoothly it needs java-1.4.2-kaffe, which should be installed before intalling OOo rpms (otherwise you can probably activate it with command line switches).
 
@@ -21,9 +21,13 @@
 
 - paths to programs
 
-- loadtime - how long it takes for your machine to load an OOo instance; this is important because when it is restarted, a script spawns a new instance and then has to wait before trying to connect
+- loadtime - how long it takes for your machine to load an OOo instance; this is important because when it is restarted, a script spawns a new instance and then has to wait before trying to connect, and also because if another instance is started too soon (before the previous one loads completely) they are both merged into one.
 
 - timeout - when an OOo instance we called does not return for too long, we decide it has crashed; we kill it and start another one. This is the time after which we undertake this drastic action.
+
+SETTING UP OOo INSTANCES
+
+When run, the server starts a configured number of OOo instances as different users (user_0, user_1 etc), each having its own settings. By default, instances are run in "headless" mode (they don't produce visible windows). However, the first time every instance is run you have to go through the registration process, otherwise it won't start. For the first time you have therefore to start every instance in a "normal" mode (by removing "headless" parameter in start.py) and clicking through registration dialogs. It is also highly recommended that you set up Java path in OOo options in every instance - this reduces the required loadtime from about half a minute to a few seconds.
 
 USAGE: