<?xml version="1.0" encoding="iso-8859-1"?>
<module name="Ft.Server.Server.Commands" file="/work/a/ports/textproc/py-4suite/work/4Suite-1.0b1/build/lib.freebsd-8.0-RELEASE-p2-i386-2.4/Ft/Server/Server/Commands/__init__.py">
  <modification-date>2005-03-13 09:56:13</modification-date>
  <abstract>This command-line application allows a 4Suite repository administrator to perform management tasks on the repository as a whole, including setup, server control, backup, and other operations.</abstract>
  <description/>
  <modules>
    <module-reference public="yes" documented="yes" name="Backup" realname="Ft.Server.Server.Commands.Backup">
      <abstract>Create a low level system backup of the entire repository</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="CommandUtil" realname="Ft.Server.Server.Commands.CommandUtil">
      <abstract>Functions used by various commands</abstract>
      <description>Copyright 2003 Fourthought, Inc. (USA).
Detailed license and copyright information: http://4suite.org/COPYRIGHT
Project home, documentation, distributions: http://4suite.org/</description>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Init" realname="Ft.Server.Server.Commands.Init">
      <abstract>Initialize the repository.  This involves reformatting the storage back end (e.g. Postgres database or FlatFile root directory) and then adding the core data structures. You will LOSE ALL DATA when you execute the init, unless you use the --update option.  You can only init on the machine on which the command is executed.  You must have write access to where the back end stores its data (e.g., your userid must be able to write to the Postgres database if the back end is Postgres).  You may be prompted for additional information to complete the init.</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Log" realname="Ft.Server.Server.Commands.Log">
      <abstract>Manager commands to work with the log files</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Recompile" realname="Ft.Server.Server.Commands.Recompile">
      <abstract>The recompile command will walk the entire repository and 
recompile all stylesheets. It is useful when changes to the underling 
code base require that stylesheets be reinited in the system.</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Restart" realname="Ft.Server.Server.Commands.Restart">
      <abstract>Restart the 4Suite server (controller).</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Start" realname="Ft.Server.Server.Commands.Start">
      <abstract>The start command can be used to start any or all protocol servers.  To start
all of the servers, execute the start command with no paramters.  To bring up
individual servers, list them on the command line.</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Status" realname="Ft.Server.Server.Commands.Status">
      <abstract>This command lists the status of each server in a 4Suite repository (running or stopped) as well as the state of the repository itself (data store existence and initialization status).</abstract>
      <description/>
    </module-reference>
    <module-reference public="yes" documented="yes" name="Stop" realname="Ft.Server.Server.Commands.Stop">
      <abstract>The stop command is used to stop any or all of the 4SS servers.  To stop
all the servers, execute the stop command with out any arguments.  To stop
an individual server, specify their names as command line arguments.  You
will be prompted for authentication before you can stop the servers.</abstract>
      <description/>
    </module-reference>
  </modules>
  <classes>
    <class name="ManagerCommandLineApp" public="yes">
      <bases>
        <base documented="yes" class="CommandLineApp" module="Ft.Lib.CommandLine.CommandLineApp"/>
      </bases>
      <abstract/>
      <description/>
      <method-resolution-order>
        <base name="ManagerCommandLineApp" module="Ft.Server.Server.Commands"/>
        <base name="CommandLineApp" module="Ft.Lib.CommandLine.CommandLineApp"/>
        <base name="Command" module="Ft.Lib.CommandLine.Command"/>
      </method-resolution-order>
      <methods documented="yes" class="ManagerCommandLineApp" module="Ft.Server.Server.Commands" inherited="no">
        <method public="no" name="__init__" id="ManagerCommandLineApp-__init__">
          <abstract/>
          <description/>
          <arguments>
            <arg name="self"/>
          </arguments>
          <overrides name="CommandLineApp" module="Ft.Lib.CommandLine.CommandLineApp"/>
        </method>
        <method public="yes" name="run" id="ManagerCommandLineApp-run">
          <abstract/>
          <description/>
          <arguments>
            <var-args name="args"/>
            <var-keywords name="kwords"/>
          </arguments>
          <overrides name="CommandLineApp" module="Ft.Lib.CommandLine.CommandLineApp"/>
        </method>
      </methods>
      <methods documented="yes" class="CommandLineApp" module="Ft.Lib.CommandLine.CommandLineApp" inherited="yes">
        <member-reference name="gen_command_tree" public="yes"/>
        <member-reference name="gen_usage" public="yes"/>
        <member-reference name="get_help_doc_info" public="yes"/>
        <member-reference name="parse_command_line" public="yes"/>
        <member-reference name="validate_arguments" public="yes"/>
        <member-reference name="validate_options" public="yes"/>
      </methods>
      <fields documented="yes" class="CommandLineApp" module="Ft.Lib.CommandLine.CommandLineApp" inherited="yes">
        <member-reference name="global_options" public="yes"/>
      </fields>
      <methods documented="yes" class="Command" module="Ft.Lib.CommandLine.Command" inherited="yes">
        <member-reference name="break_parent_relationship" public="yes"/>
        <member-reference name="build_parent_relationship" public="yes"/>
        <member-reference name="flatten_command_tree" public="yes"/>
        <member-reference name="run_command" public="yes"/>
      </methods>
    </class>
  </classes>
  <fields>
    <field public="yes" name="g_commands" id="g_commands">
      <value>[&lt;module 'Ft.Server.Server.Commands.Init' from 'b...E-p2-i386-2.4/Ft/Server/Server/Commands/Init.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Backup' from ...p2-i386-2.4/Ft/Server/Server/Commands/Backup.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Recompile' fr...i386-2.4/Ft/Server/Server/Commands/Recompile.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Start' from '...-p2-i386-2.4/Ft/Server/Server/Commands/Start.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Stop' from 'b...E-p2-i386-2.4/Ft/Server/Server/Commands/Stop.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Restart' from...2-i386-2.4/Ft/Server/Server/Commands/Restart.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Status' from ...p2-i386-2.4/Ft/Server/Server/Commands/Status.py'&gt;, &lt;module 'Ft.Server.Server.Commands.Log' from 'bu...6-2.4/Ft/Server/Server/Commands/Log/__init__.py'&gt;]</value>
    </field>
    <field public="yes" name="g_options" id="g_options">
      <value>[[--username=&lt;USER&gt;], [--password=&lt;PASSWORD&gt;], [--core-id=&lt;CORE&gt;], [--config-file=&lt;FILEPATH&gt;]]</value>
    </field>
  </fields>
</module>
