Classes:
|
Fields:
|
Create a low level system backup of the entire repository
|
|
Functions used by various commands
|
|
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.
|
|
Manager commands to work with the log files
|
|
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.
|
|
Restart the 4Suite server (controller).
|
|
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.
|
|
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).
|
|
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.
|