Changes between Version 2 and Version 3 of FactoryManual/StandardFactory

06/26/09 15:29:16 (8 years ago)



  • FactoryManual/StandardFactory

    v2 v3  
    11= Factory Manual: Using the standard factory = 
    3 [../Setup << Previous: Setting up your account] | [../NewBackends Next: Creating new backends >>] 
     3[../Setup << Previous: Setting up your account] | [./OOOServer Next: OOOServer backend >>] 
    55This chapter details the installation and configuration of the standard factory that is distributed by If you are implementing your own factory from scratch you can skip this chapter, but if you want to develop a factory builds on the standard factory then you want to read this so you understand how configuration works.  
    8787Besides these standard configuration options each backend can have extra configuration options depending on the backend type. 
    89 === OOOServer === #OOOServer 
    91 The OOOServer backends implements ! running in headless mode. As such it is not able to produce screenshots but only ODF roundtrip and PDF export. To use the OOOServer backend you must have ! running in headless mode. See [#OOOHeadless Running in headless mode]. 
    93 Besides the standard configuration options, you can set the following options for the OOOServer backend. 
    95  ooo_host:: 
    96     The hostname of the machine that ! is running on in headless mode. Normally this should be localhost. 
    97     If you set this option then you should also set the ooo_port option.  
    98  ooo_port:: 
    99     The port number that ! is listening to. This should normally be 8100.  
    100  ooo_pipe:: 
    101     The name of the pipe that ! is listening to. If you set this option then you should not set the ooo_host and ooo_port options. 
    102     [[NoteBox(note, On Windows XP and Vista it is not possible to connect to ! using a socket with the ooo_host and ooo_port options. You should use a pipe instead.)]] 
    104 ==== Running ! in headless mode ==== #OOOHeadless 
    106 When ! is running in headless mode you cannot start it yourself anymore. The easiest thing to do is to create a new user on your computer and run ! in headless mode under that user account instead of your own. Linux users can start ! in headless mode using the following command:  
    108 {{{ 
    109 $> soffice -headless -nologo -norestore -accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager 
    110 }}} 
    112 For Windows users there is a simple batch file in the utils directory called utils/oooserver.bat. Simply edit that file, make sure that the OOOPATH is correct and that the OOOPIPE is the same as the pipe name in your configuration file. Then double-click the file to start ! in headless mode. If you want to start ! manually on Windows then you can execute the following command: 
    114 {{{ 
    115 $> soffice.exe -headless -nologo -norestore "-accept=pipe,name=officeshots;urp;StarOffice.ServiceManager" 
    116 }}} 
    118 [[NoteBox(note, Sometimes ! on Windows does not install the Python UNO bridge. You can re-install ! Make sure you choose Custom install  amd check the box that installs Python UNO.)]] 
    120 The oooserver init script in the utils directory can be used to automatically start and stop ! in headless mode on a Debian or Ubuntu machine. It uses xvbf, the X Virtual !FrameBuffer so it can even run on a machine that has no complete X Server installed such as most servers. Place this file in your /etc/init.d directory and make it executable. Then you need to add symlinks to it in the appropriate places. You can execute the following command (as root) to create these symlinks automatically: 
    122 {{{ 
    123 #> update-rc.d oooserver defaults 
    124 }}} 
    126 You will also need to configure the oooserver init script. By default oooserver will run as user ''nobody''  but on many systems this user does not have a valid home directory. ! does not start without a valid home directory. Either make sure user ''nobody'' exists and has a valid home directory, or change the USER parameter in the oooserver init script. 
    128 === CLI === 
    130 [../Setup << Previous: Setting up your account] | [../NewBackends Next: Creating new backends >>] 
     89[../Setup << Previous: Setting up your account] | [./OOOServer Next: OOOServer backend >>]