Using Sigma Web Framework with IIS or third-party HTTP servers

The Sigma Framework does not rely on any special features of the Apache server. The Sigma Framework can be used with other HTTP servers, in particular Microsoft IIS server.

In order to configure a third party server, the user creates two virtual directories (i.e. Virtual Web Folders), as follows:

• /s-cgi – This web folder corresponds to the "Sigma\s-cg" directory of the framework. The user must grant this web folder both read and execute permissions.
• /s-html – This web folder corresponds to the "Sigma\s-html" directory of the framework. The user can grant this web folder read-only permissions.

If the Sigma Administrator wishes to make use of IIS authentication (possibly to take advantage of Windows Directory Services), the username and password of any registered user must appear in the Sigma "Login" registry. (See later sections on how to configure user logins and other associated parameters for more information. (Note that this is required to take advantage of the permission features of the Sigma Framework.

After configuring IIS to work with the Sigma Framework, the user can disable the Apache server, or leave it running as an auxiliary interface. To disable the Apache service, the Sigma administrator edits the "Schedule" tab of Sigma, as discussed in a later section. The user can additionally simply remove or rename the "Sigma\apache\CO-apache.exe" file to disable the startup of this program.