Introduction
  Installing
  Handling
  Virtual servers
  Modules
  Filesystems
  RXML tags
  Graphics
  Proxy
  Miscellaneous modules
  Security considerations
  Scripting
  Databases
  LDAP
  SiteBuilder
    Modules
    FTP
    Configuration
    File types
    Languages
    Roxen Application Launcher
    Work Areas
  Access Control
  IntraSeek
  LogView
  FrontPage
  Upgrading
  Third party extensions
  Portability
  Reporting bugs
  Appendix
 
SiteBuilder

SiteBuilder is installed by creating a SiteBuilder virtual server, with the New virtual server button on the top node of the Virtual Server tab.

The second step when installing SiteBuilder is to create the users that are to have access to the content editor. If you already have the users in the user database of the operating system you can do this by enabling and configuring the AC: OS user import module. Please see the Access Control chapter for information about how to manually create your users and give them the right permissions.

The third step is to make sure your users can edit files with the editor of their choice. This means using Roxen Application Launcher, which will enable the users to use a local editor running on their computer. On the server end some sort of file sharing between the web server and the user's computers need to be installed and SiteBuilder configured to use it. See the Roxen Application Launcher page for detailed information how to do this.

All files used by SiteBuilder are stored in a separate directory structure. When moving a SiteBuilder site between different servers all you have to do is to configure the SiteBuilder storage in the SiteBuilder module to point at this directory. The directory structure can be copied to another location, no absolute paths are used.

A SiteBuilder server may spawn several virtual servers. Work areas should be mounted in different virtual servers since the site might contain absolute paths and thus not work when mounted anywhere but "/". To be able to edit through FTP you have to use another virtual server, since all the modules of a normal SiteBuilder virtual server will otherwise show up in directory listings.

When using several virtual servers the SiteBuilder Work Area Filesystem and AC: User database modules must be enabled, and configured to connect to the appropriate SiteBuilder. The SiteBuilder, SiteBuilder Content Editor and any Access Control modules but AC: User database should not be enabled in such a virtual server. Other modules, like the SiteBuilder Tags module can be enabled if their functionality is wanted.

SiteBuilder uses an external program, cvs, for the version control functionality. The cvs binary is compiled and shipped with Roxen Platform, you need not notice it.