Administration Guide : Configuring Apache Web server : Appendix: Configuring a non-supported Web server

Appendix: Configuring a non-supported Web server
This functionality is no longer supported for Xinet 19.
This section is provided for experienced Web server administrators who want to configure a server that is not “supported.” If you do not understand the terminology in this section, we suggest you choose one of the “supported” servers for your platform.
Xinet requires the following server attributes to function:
The URL /webnative must reference /usr/etc/webnative on Unix systems. The server should allow CGIs (and only CGIs) to run from this directory.
The URL /webnativedoc must reference /var/adm/webnative on Unix systems. The server should allow only document access (no CGIs) from this directory, and it should not allow users to index the directory.
The /webnative should have user access control, and should use the authentication realm WebNative. It is up to you whether you share a user database with the rest of your server or maintain a separate one for Xinet.
You need to create any Xinet users you want. You at least need to create a nativeadmin user to allow Xinet administration to work.
After setting up this configuration and restarting your server, you will need to place a link to /webnative/listdir somewhere on your site. (If you want, you can copy the Xinet logo from /var/adm/webnative/images/logo.gif for use with the link.) Authenticate as nativeadmin and follow the configuration steps in the next chapter. Note, that since Xinet is unaware of your user list, anywhere the documentation shows a user pop-up, you will see a type-in field where you must specify the user. If you want to add, remove, or change the password of a user, you must do it through your server’s administrative interface rather than through the Xinet interface.