The configuration system is organized to reflect the operational structure of the server. Configuration information is organized into profiles, which contain distinct settings. Settings are organized into two levels; there are local settings and global settings. Local settings are available for individual virtual servers and affect each one seperately. Global settings affect the operation of all virtual servers.
For example, a configuration might be organized like the following:
Note: Most smaller installations of web servers will only need a single profile with one virtual (default) server so local and global settings will appear to have the same effect. This organization is enforced to allow scalability for large installation uses, like web presence providers.
Profiles allow separate copies of OmniHTTPd to run on different ports. For example, profile "Port81" could service requests on port 81 while the default profile handles port 80. To start OmniHTTPd with a profile other than the default, launch OHTTPD.EXE with the command line:
ohttpd.exe -p profile
Where profile is the name of the profile you wish to use. To configure a specific profile, start OADMIN.EXE with the command line:
Where profile is the name of the profile you wish to configure. If the profile doesn't exist, OmniHTTPd will create one with default values. Backing up and restoring the configuration with OADMIN.EXE will affect all profiles regardless of the command line.