The Configuration hierachical menu is there to guide you, since some settings are inter-dependent. You can work randomly with any page, but initially it will be easier to work top down with the hierarchy shown in the Admin Root.

Configuration Trees

Configuration Trees, provide an Overview of the current status of settings, such as which directories are Resources and which Templates have been to define them, or even which Templates have inherited their settings from other Templates to show their inter-dependancies.

Refresh the Tree to see the results of changes made in any of the Configuration Editors. Reloading the page does not refresh the Tree, particularly if the Web Browser has that page cached in memory.

The Directory Tree is where you specify Resources.

You can see all your Drives, with a collapsed or Full Path view of directories. You can view Resources from within the Directory Tree, their Aliases, their physical locations and the affected sub-directories.

To Define, Add, Remove or Modify Resources, just point at the hyperlinked Directories you want and specify the Template and Alias Names to use for that Resource, within the Template Editor.

All Resources are shown in Bold and other directories are in a regular font style.

The Template Tree provides an overview of either used or all Templates and their affected Resources

To Define, Add, Remove or Modify Templates, just point at the hyperlinked Templates that you want and go into the Template Editor.

Templates are hyperlinked and Resources are not.

The Resource Tree shows a synopsis of directory resources, in a collapsed or Full Path view of directories.

You can view the Templates used by each Resource, their Aliases, their full path and the sub-directories affected by the definition of the Resources.

To Define, Add, Remove or Modify Resources, just point at the hyperlinked Resource you want and define the Resource within the Resource Editor.

Directories which are either sub-directories or Parent directories of Resources are shown in a regular font style to complete the hierarchy. All explicitly defined Resources are shown in Bold.

The Document Tree provides a view to all Documents which are accessible on that server. The Documents are subject to Security and Access control rules, so not all users will be able to see all Documents.

Documents URLs and their physical locations can be included.

To browse any Document within the Tree just point at the hyperlinked Document that you want.

Configuration Editors

Configuration Editors are the mechanism for Adding, Removing or Modifying Security and Access control Settings and API Hooks, as well as Document Settings and Directory Indexes.

Configuration Editors include:

The Template Editor

The Resource Editor

The Alias Editor

The User Database Editor.

Advanced Settings which are accessed by the Configuration Editors are automatically setup and optimised on startup to allow for ease of use and are seldom neccesary to change.

PowerWeb's Access Control Database
PowerWeb Server++ centrally manages access control in the database that contains flexible and powerful security rules through object-orientation.

Powerful Resource Document Objects
A resource is any object that can be accessed via the server. It is typically a collection of documents such as a directory or API and CGI scripts. All Resources are subject to security by means of access control and authentication.

PowerWeb Server++ can work with individual files, all files matching a given wildcard pattern, all directories matching a wildcard pattern, or simply an entire directory or an entire disk.

You can work randomly with any page, but it will be easier to work top down with the hierarchy shown in the Admin Root, because some settings are inter-dependent and prompt for the next settings with some fields filled in by the previous page.

For example: Resources rely heavily on using templates so that you do not have re-configure settings repetitively. So when selecting a resource from the Directory Tree, you are linked into the Resource Editor which prompts you for the name of the template to use, along with the optional directory alias to enable users to access resources outside of the document root directory hierarchy.

You must submit each page after modifying it, but do not have to fill in all settings across all pages. Only relevant settings need to be completed. For example you do not have to add an alias or a template everytime you add a resource.

You will need to Save and Restart the Server to bring your changes into production.